Skip to main content

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

Revision differences

Document history

Date By Action
2021-07-14
(System)
Received changes through RFC Editor sync (created alias RFC 9065, changed abstract to 'To protect user data and privacy, Internet transport protocols have supported …
Received changes through RFC Editor sync (created alias RFC 9065, changed abstract to '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.', changed pages to 37, changed standardization level to Informational, changed state to RFC, added RFC published event at 2021-07-14, changed IESG state to RFC Published)
2021-07-14
(System) RFC published