HMAC-MD5 IP Authentication with Replay Prevention

Metadata

Publisher: IETF
Doc Type: Standard
Pages: 6
Abstract: This document describes a keyed-MD5 transform to be used in conjunction with the IP Authentication Header [RFC-1826]. The particular transform is based on [HMAC-MD5]. An option is also specified to guard against replay attacks. [STANDARDS-TRACK]
Publication Date: 1997-02-01
Status Note: Proposed Standard
DOI: 10.17487/RFC2085
Link: https://doi.org/10.17487/RFC2085
Author(s): Michael Oehler
K. Robert Glenn
Keyword(s): HMAC-MD5, IPSEC, Message Digest, Security, IP, Encryption

Latest version of IETF RFC 2085

Document Versions — IETF RFC 2085

▶ IETF RFC 2085 (1997-02-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Bibliographic Reference(s)

IETF RFC 1825 [Superseded*]
IETF RFC 2104 [Active, Amended*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC2085.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 2085, HMAC-MD5 IP Authentication with Replay Prevention. Available at https://doi.org/10.17487/RFC2085

Snippet:

IETF RFC 2085, HMAC-MD5 IP Authentication with Replay Prevention. Available at https://doi.org/10.17487/RFC2085

HTML (ISO 690 compliant)

Preview:

IETF RFC 2085, HMAC-MD5 IP Authentication with Replay Prevention. Available at https://doi.org/10.17487/RFC2085

Snippet:

<span class="citation"><cite>IETF RFC 2085</cite>, HMAC-MD5 IP Authentication with Replay Prevention. Available at <a href="https://doi.org/10.17487/RFC2085" target="_blank" rel="noopener">https://doi.org/10.17487/RFC2085</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 2085, HMAC-MD5 IP Authentication with Replay Prevention
doi: 10.17487/RFC2085
url: https://doi.org/10.17487/RFC2085

Snippet:

<li>
<cite id="bib-rfc2085">IETF RFC 2085</cite>, HMAC-MD5 IP Authentication with Replay Prevention
<span class="doi">10.17487/RFC2085</span>
</li>

Referenced By

IETF RFC 2202 [Active*]
IETF RFC 4251 [Active*]