RFC 9065: Considerations around Transport Header Confidentiality, Network Operations, and the Evolution of Internet Transport Protocols
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9065
- Published
- July 2021
- Authors
- G. Fairhurst; C. Perkins
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 37
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5416Control and Provisioning of Wireless Access Points (CAPWAP) Protocol Binding for IEEE 802.11Current
March 2009
- RFC 9071RTP-Mixer Formatting of Multiparty Real-Time TextCurrent
July 2021
- RFC 9040TCP Control Block InterdependenceCurrent
July 2021
- RFC 9039Uniform Resource Names for Device IdentifiersCurrent
June 2021
- RFC 9100Sensor Measurement Lists (SenML) Features and VersionsCurrent
August 2021
- RFC 9110HTTP SemanticsCurrent
June 2022
- RFC 9111HTTP CachingCurrent
June 2022
- RFC 9112HTTP/1.1Updated
June 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?