RFC 1828: IP Authentication using Keyed MD5
In plain English — editorial summary, not part of the RFC
This document describes the use of keyed MD5 with the IP Authentication Header. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1828
- Published
- August 1995
- Authors
- P. Metzger; W. Simpson
- Status
- HISTORIC
- Stream
- IETF
- Area
- sec
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4302IP Authentication HeaderCurrent
December 2005
- RFC 2085HMAC-MD5 IP Authentication with Replay PreventionCurrent
February 1997
- RFC 2104HMAC: Keyed-Hashing for Message AuthenticationUpdated
February 1997
- RFC 4303IP Encapsulating Security Payload (ESP)Current
December 2005
- RFC 4305Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)Obsoleted
December 2005
- RFC 4835Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)Obsoleted
April 2007
- RFC 1826IP Authentication HeaderObsoleted
August 1995
- RFC 2402IP Authentication HeaderObsoleted
November 1998
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?