Overlay Path Option for IP and TCP
draft-williams-overlaypath-ip-tcp-rfc-04
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2013-12-21 (latest revision 2013-06-19) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| 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) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-williams-overlaypath-ip-tcp-rfc-04.txt
https://www.ietf.org/archive/id/draft-williams-overlaypath-ip-tcp-rfc-04.txt
Abstract
Data transport through overlay networks often uses either connection termination or network address translation (NAT) in such a way that the public IP addresses of the true endpoint machines involved in the data transport are invisible to each other. This document describes IPv4, IPv6, and TCP options for communicating this information from the overlay network to the endpoint machines.
Authors
Brandon Williams (brandon.williams@akamai.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)