RFC 9347: Aggregation and Fragmentation Mode for Encapsulating Security Payload (ESP) and Its Use for IP Traffic Flow Security (IP-TFS)
In plain English — editorial summary, not part of the RFC
This document describes a mechanism for aggregation and fragmentation of IP packets when they are being encapsulated in Encapsulating Security Payload (ESP). This new payload type can be used for various purposes, such as decreasing encapsulation overhead for small IP packets; however, the focus in this document is to enhance IP Traffic Flow Security (IP-TFS) by adding Traffic Flow Confidentiality (TFC) to encrypted IP-encapsulated traffic. TFC is provided by obscuring the size and frequency of IP traffic using a fixed-size, constant-send-rate IPsec tunnel. The solution allows for congestion control, as well as nonconstant send-rate usage.
Document record
- Document ID
- RFC9347
- Published
- January 2023
- Authors
- C. Hopps
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 31
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9348A YANG Data Model for IP Traffic Flow SecurityCurrent
January 2023
- RFC 9345Delegated Credentials for TLS and DTLSCurrent
July 2023
- RFC 9349Definitions of Managed Objects for IP Traffic Flow SecurityCurrent
January 2023
- RFC 9338CBOR Object Signing and Encryption (COSE): CountersignaturesCurrent
December 2022
- RFC 9336X.509 Certificate General-Purpose Extended Key Usage (EKU) for Document SigningCurrent
December 2022
- RFC 9334Remote ATtestation procedureS (RATS) ArchitectureCurrent
January 2023
- RFC 9360CBOR Object Signing and Encryption (COSE): Header Parameters for Carrying and Referencing X.509 CertificatesCurrent
February 2023
- RFC 9362Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Configuration Attributes for Robust Block TransmissionCurrent
February 2023
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?