RFC 8165: Design Considerations for Metadata Insertion
In plain English — editorial summary, not part of the RFC
The IAB published RFC 7624 in response to several revelations of pervasive attacks on Internet communications. This document considers the implications of protocol designs that associate metadata with encrypted flows. In particular, it asserts that designs that share metadata only by explicit actions at the host are preferable to designs in which middleboxes insert metadata.
Document record
- Document ID
- RFC8165
- Published
- May 2017
- Authors
- T. Hardie
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8041Use Cases and Operational Experience with Multipath TCPCurrent
January 2017
- RFC 8302Transparent Interconnection of Lots of Links (TRILL): ARP and Neighbor Discovery (ND) OptimizationCurrent
January 2018
- RFC 7844Anonymity Profiles for DHCP ClientsCurrent
May 2016
- RFC 8828WebRTC IP Address Handling RequirementsCurrent
January 2021
- RFC 7239Forwarded HTTP ExtensionCurrent
June 2014
- RFC 9209The Proxy-Status HTTP Response Header FieldCurrent
June 2022
- RFC 9298Proxying UDP in HTTPUpdated
August 2022
- RFC 6935IPv6 and UDP Checksums for Tunneled PacketsCurrent
April 2013
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?