RFC 2857: The Use of HMAC-RIPEMD-160-96 within ESP and AH
In plain English — editorial summary, not part of the RFC
This memo describes the use of the HMAC algorithm in conjunction with the RIPEMD-160 algorithm as an authentication mechanism within the revised IPSEC Encapsulating Security Payload (ESP) and the revised IPSEC Authentication Header (AH). [STANDARDS-TRACK]
Document record
- Document ID
- RFC2857
- Published
- June 2000
- Authors
- A. Keromytis; N. Provos
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2403The Use of HMAC-MD5-96 within ESP and AHCurrent
November 1998
- RFC 4301Security Architecture for the Internet ProtocolUpdated
December 2005
- RFC 4302IP Authentication HeaderCurrent
December 2005
- RFC 2451The ESP CBC-Mode Cipher AlgorithmsCurrent
November 1998
- RFC 2410The NULL Encryption Algorithm and Its Use With IPsecCurrent
November 1998
- RFC 2405The ESP DES-CBC Cipher Algorithm With Explicit IVCurrent
November 1998
- RFC 3948UDP Encapsulation of IPsec ESP PacketsCurrent
January 2005
- RFC 4303IP Encapsulating Security Payload (ESP)Current
December 2005
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?