RFC 9333: Minimal IP Encapsulating Security Payload (ESP)
In plain English — editorial summary, not part of the RFC
This document describes the minimal properties that an IP Encapsulating Security Payload (ESP) implementation needs to meet to remain interoperable with the standard ESP as defined in RFC 4303. Such a minimal version of ESP is not intended to become a replacement of ESP in RFC 4303. Instead, a minimal implementation is expected to be optimized for constrained environments while remaining interoperable with implementations of ESP. In addition, this document provides some considerations for implementing minimal ESP in a constrained environment, such as limiting the number of flash writes, handling frequent wakeup and sleep states, limiting wakeup time, and reducing the use of random generation. This document does not update or modify RFC 4303. It provides a compact description of how to implement the minimal version of that protocol. RFC 4303 remains the authoritative description.
Document record
- Document ID
- RFC9333
- Published
- January 2023
- Authors
- D. Migault; T. Guggemos
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 13
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9327Control Messages Protocol for Use with Network Time Protocol Version 4Current
November 2022
- RFC 9343IPv6 Application of the Alternate-Marking MethodCurrent
December 2022
- RFC 9354Transmission of IPv6 Packets over Power Line Communication (PLC) NetworksCurrent
January 2023
- RFC 9363A YANG Data Model for Static Context Header Compression (SCHC)Updated
March 2023
- RFC 9365IPv6 Wireless Access in Vehicular Environments (IPWAVE): Problem Statement and Use CasesCurrent
March 2023
- RFC 9374DRIP Entity Tag (DET) for Unmanned Aircraft System Remote ID (UAS RID)Current
March 2023
- RFC 9391Static Context Header Compression over Narrowband Internet of ThingsCurrent
April 2023
- RFC 9268IPv6 Minimum Path MTU Hop-by-Hop OptionCurrent
August 2022
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?