Revealing hosts sharing an IP address using TCP option
draft-wing-nat-reveal-option-03
This document is an Internet-Draft (I-D). Anyone may submit an I-D to the IETF. This I-D is not endorsed by the IETF and has no formal standing in the IETF standards process.
| Document | Type | Expired Internet-Draft (individual) Expired & archived | |
|---|---|---|---|
| Authors | Andrew Yourtchenko , Dan Wing | ||
| Last updated | 2012-06-10 (Latest revision 2011-12-08) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
When an IP address is shared among several subscribers -- with a NAT or with an application-level proxy -- it is impossible for the server to differentiate between different clients. Such differentiation is valuable in several scenarios. This memo describes a technique to differentiate TCP clients sharing an IP address. The proposed method uses a TCP option, which avoids altering the application-level payload and works well with SSL-protected connections.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)