[IPsec] RFC 9347 on Aggregation and Fragmentation Mode for Encapsulating Security Payload (ESP) and Its Use for IP Traffic Flow Security (IP-TFS)
rfc-editor@rfc-editor.org Wed, 01 February 2023 05:34 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49EF1C136149; Tue, 31 Jan 2023 21:34:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.947
X-Spam-Level:
X-Spam-Status: No, score=-3.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Fv50z1aimcm; Tue, 31 Jan 2023 21:34:50 -0800 (PST)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1251BC13B438; Tue, 31 Jan 2023 21:34:50 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id DA30E55A3F; Tue, 31 Jan 2023 21:34:49 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ipsec@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230201053449.DA30E55A3F@rfcpa.amsl.com>
Date: Tue, 31 Jan 2023 21:34:49 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/qzEt314a7eVr-jqfOYLuudCY9Uk>
Subject: [IPsec] RFC 9347 on Aggregation and Fragmentation Mode for Encapsulating Security Payload (ESP) and Its Use for IP Traffic Flow Security (IP-TFS)
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipsec/>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2023 05:34:54 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9347
Title: Aggregation and Fragmentation Mode for
Encapsulating Security Payload (ESP) and
Its Use for IP Traffic Flow Security (IP-TFS)
Author: C. Hopps
Status: Standards Track
Stream: IETF
Date: January 2023
Mailbox: chopps@chopps.org
Pages: 31
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ipsecme-iptfs-19.txt
URL: https://www.rfc-editor.org/info/rfc9347
DOI: 10.17487/RFC9347
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.
This document is a product of the IP Security Maintenance and Extensions Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC