Aggregation and Fragmentation Mode for Encapsulating Security Payload (ESP) and Its Use for IP Traffic Flow Security (IP-TFS)
RFC 9347
Revision differences
Document history
Date | By | Action |
---|---|---|
2023-02-02
|
(System) | IANA registries were updated to include RFC9347 |
2023-01-31
|
(System) | Received changes through RFC Editor sync (created alias RFC 9347, changed title to 'Aggregation and Fragmentation Mode for Encapsulating Security Payload (ESP) and Its … Received changes through RFC Editor sync (created alias RFC 9347, changed title to 'Aggregation and Fragmentation Mode for Encapsulating Security Payload (ESP) and Its Use for IP Traffic Flow Security (IP-TFS)', changed abstract to '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.', changed pages to 31, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2023-01-31, changed IESG state to RFC Published) |
2023-01-31
|
(System) | RFC published |