RFC 9065 on Considerations around Transport Header Confidentiality, Network Operations, and the Evolution of Internet Transport Protocols

rfc-editor@rfc-editor.org Thu, 15 July 2021 06:44 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 97A0A3A1F11; Wed, 14 Jul 2021 23:44:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 3zIIVT9Epptt; Wed, 14 Jul 2021 23:44:01 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB7983A1F0D; Wed, 14 Jul 2021 23:44:01 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id BF655F40709; Wed, 14 Jul 2021 23:43:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDkwNjUgb24gQ29uc2lkZXJhdGlvbnMgYXJvdW5kIFRyYW5zcG9ydCBIZWFkZXIgQ29uZmlkZW50aWFsaXR5LCBOZXR3b3JrIE9wZXJhdGlvbnMsIGFuZCB0aGUgRXZvbHV0aW9uIG9mIEludGVybmV0IFRyYW5zcG9ydCBQcm90b2NvbHM=?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, tsvwg@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210715064356.BF655F40709@rfc-editor.org>
Date: Wed, 14 Jul 2021 23:43:56 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/UB4z-knpGU_WkOoOZ3mGsnTfJKA>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jul 2021 06:44:07 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 9065

        Title:      Considerations around Transport Header Confidentiality, 
                    Network Operations, and the Evolution of 
                    Internet Transport Protocols 
        Author:     G. Fairhurst,
                    C. Perkins
        Status:     Informational
        Stream:     IETF
        Date:       July 2021
        Mailbox:    gorry@erg.abdn.ac.uk,
        Pages:      37
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tsvwg-transport-encrypt-21.txt

        URL:        https://www.rfc-editor.org/info/rfc9065

        DOI:        10.17487/RFC9065

To protect user data and privacy, Internet transport protocols have
supported payload encryption and authentication for some time. Such
encryption and authentication are now also starting to be applied to
the transport protocol headers. This helps avoid transport protocol
ossification by middleboxes, mitigate attacks against the transport
protocol, and protect metadata about the communication. Current
operational practice in some networks inspect transport header
information within the network, but this is no longer possible when
those transport headers are encrypted.

This document discusses the possible impact when network traffic uses
a protocol with an encrypted transport header. It suggests issues to
consider when designing new transport protocols or features.

This document is a product of the Transport Area Working Group Working Group of the IETF.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

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