Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 9
- Abstract
- The IPsec series of protocols makes use of various cryptographic algorithms in order to provide security services. The Encapsulating Security Payload (ESP) and the Authentication Header (AH) provide two mechanisms for protecting data being sent over an IPsec Security Association (SA). To ensure interoperability between disparate implementations, it is necessary to specify a set of mandatory-to-implement algorithms to ensure that there is at least one algorithm that all implementations will have available. This document defines the current set of mandatory-to-implement algorithms for ESP and AH as well as specifying algorithms that should be implemented because they may be promoted to mandatory at some future time. [STANDARDS-TRACK]
- Publication Date
- 2005-12-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC4305- Link
- https://doi.org/10.17487/RFC4305
- Author(s)
- Donald E. Eastlake 3rd
- Keyword(s)
- ESP, IPSEC, Authentication, Security, Architecture, IP, IPv4, IPv6
Latest version of IETF RFC 4305
Document Versions — IETF RFC 4305
-
▶ IETF RFC 4305 (2005-12-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 2403 [Active*]
- IETF RFC 2404 [Active*]
- IETF RFC 2405 [Active*]
- IETF RFC 3566 [Active*]
- IETF RFC 3602 [Active*]
- IETF RFC 3686 [Active*]
- IETF RFC 4301 [Active, Amended*]
- IETF RFC 4302 [Active*]
- IETF RFC 4303 [Active*]
Bibliographic Reference(s)
- IEEE.STD802.11I.2004 — IEEE802.11i EXTERNAL
- IETF RFC 791 [Active*]
- IETF RFC 2402 [Superseded*]
- IETF RFC 2406 [Superseded*]
- IETF RFC 2407 [Superseded*]
- IETF RFC 2409 [Superseded*]
- IETF RFC 4306 [Superseded*]
- IETF RFC 4307 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC4305.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 4305, Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH). Available at https://doi.org/10.17487/RFC4305
Snippet:
IETF RFC 4305, Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH). Available at https://doi.org/10.17487/RFC4305
HTML (ISO 690 compliant)
Preview:
IETF RFC 4305, Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH). Available at https://doi.org/10.17487/RFC4305
Snippet:
<span class="citation"><cite>IETF RFC 4305</cite>, Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH). Available at <a href="https://doi.org/10.17487/RFC4305" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4305</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 4305, Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)
doi: 10.17487/RFC4305
url: https://doi.org/10.17487/RFC4305
doi: 10.17487/RFC4305
url: https://doi.org/10.17487/RFC4305
Snippet:
<li> <cite id="bib-rfc4305">IETF RFC 4305</cite>, Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH) <span class="doi">10.17487/RFC4305</span> </li>
Referenced By
- IETF RFC 4294 [Superseded*]
- IETF RFC 4301 [Active, Amended*]
- IETF RFC 4302 [Active*]
- IETF RFC 4303 [Active*]
- IETF RFC 4346 [Superseded*]
- IETF RFC 4835 [Superseded*]
- IETF RFC 6071 [Active*]