Experimental Option for TCP Host Identification

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2016-05-08 (latest revision 2015-11-05)
Stream (None)
Intended RFC status Experimental
Expired & archived
pdf htmlized (tools) htmlized bibtex
IETF conflict review conflict-review-williams-exp-tcp-host-id-opt
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)
IANA IANA review state IANA OK - Actions Needed

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


Recent proposals discussed in the IETF have identified benefits to more distinctly identifying the hosts that are hidden behind a shared address/prefix sharing device or application-layer proxy. Analysis indicates that the use of a TCP option for this purpose can be successfully applied to some use cases. This document discusses design, deployment, and privacy considerations for such a TCP option that is in operational use on the Internet today.


Brandon Williams (brandon.williams@akamai.com)
Mohamed Boucadair (mohamed.boucadair@orange.com)
Dan Wing (dwing@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)