Implicit Initialization Vector (IV) for Counter-Based Ciphers in Encapsulating Security Payload (ESP)
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 8
- Abstract
- Encapsulating Security Payload (ESP) sends an initialization vector (IV) in each packet. The size of the IV depends on the applied transform and is usually 8 or 16 octets for the transforms defined at the time this document was written. When used with IPsec, some algorithms, such as AES-GCM, AES-CCM, and ChaCha20-Poly1305, take the IV to generate a nonce that is used as an input parameter for encrypting and decrypting. This IV must be unique but can be predictable. As a result, the value provided in the ESP Sequence Number (SN) can be used instead to generate the nonce. This avoids sending the IV itself and saves 8 octets per packet in the case of AES-GCM, AES-CCM, and ChaCha20-Poly1305. This document describes how to do this.
- Publication Date
- 2020-03-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC8750- Link
- https://doi.org/10.17487/RFC8750
- Author(s)
- Daniel MigaultTobias GuggemosYoav Nir
- Keyword(s)
- IKE, IPSEC, GCM, CCM, ChaCha20
Latest version of IETF RFC 8750
Document Versions — IETF RFC 8750
-
▶ IETF RFC 8750 (2020-03-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 3602 [Active*]
- IETF RFC 3686 [Active*]
- IETF RFC 4106 [Active*]
- IETF RFC 4303 [Active*]
- IETF RFC 4309 [Active*]
- IETF RFC 5374 [Active*]
- IETF RFC 6311 [Active*]
- IETF RFC 6407 [Superseded*]
- IETF RFC 7296 [Active*]
- IETF RFC 7383 [Active*]
- IETF RFC 7634 [Active*]
- IETF RFC 8174 [Active*]
- IETF RFC 8221 [Active*]
Bibliographic Reference(s)
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC8750.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 8750, Implicit Initialization Vector (IV) for Counter-Based Ciphers in Encapsulating Security Payload (ESP). Available at https://doi.org/10.17487/RFC8750
Snippet:
IETF RFC 8750, Implicit Initialization Vector (IV) for Counter-Based Ciphers in Encapsulating Security Payload (ESP). Available at https://doi.org/10.17487/RFC8750
HTML (ISO 690 compliant)
Preview:
IETF RFC 8750, Implicit Initialization Vector (IV) for Counter-Based Ciphers in Encapsulating Security Payload (ESP). Available at https://doi.org/10.17487/RFC8750
Snippet:
<span class="citation"><cite>IETF RFC 8750</cite>, Implicit Initialization Vector (IV) for Counter-Based Ciphers in Encapsulating Security Payload (ESP). Available at <a href="https://doi.org/10.17487/RFC8750" target="_blank" rel="noopener">https://doi.org/10.17487/RFC8750</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 8750, Implicit Initialization Vector (IV) for Counter-Based Ciphers in Encapsulating Security Payload (ESP)
doi: 10.17487/RFC8750
url: https://doi.org/10.17487/RFC8750
doi: 10.17487/RFC8750
url: https://doi.org/10.17487/RFC8750
Snippet:
<li> <cite id="bib-rfc8750">IETF RFC 8750</cite>, Implicit Initialization Vector (IV) for Counter-Based Ciphers in Encapsulating Security Payload (ESP) <span class="doi">10.17487/RFC8750</span> </li>
Referenced By
- IETF RFC 9028 [Active*]
- IETF RFC 9827 [Active*]
- IETF RFC 9838 [Active*]