Dear all,
A new version of this draft has been submitted that attempts to lay out
a more clear argument for the use of both TCP and IP options, with
references to other efforts in the same arena.
Comments are welcome.
Cheers,
--Brandon
-------- Original Message --------
Subject: New Version Notification for
draft-williams-overlaypath-ip-tcp-rfc-03.txt
Date: Thu, 20 Dec 2012 11:55:33 -0500
From: [email protected] <[email protected]>
To: Williams, Brandon <[email protected]>
A new version of I-D, draft-williams-overlaypath-ip-tcp-rfc-03.txt
has been successfully submitted by Brandon Williams and posted to the
IETF repository.
Filename: draft-williams-overlaypath-ip-tcp-rfc
Revision: 03
Title: Overlay Path Option for IP and TCP
Creation date: 2012-12-20
WG ID: Individual Submission
Number of pages: 15
URL:
http://www.ietf.org/internet-drafts/draft-williams-overlaypath-ip-tcp-rfc-03.txt
Status:
http://datatracker.ietf.org/doc/draft-williams-overlaypath-ip-tcp-rfc
Htmlized:
http://tools.ietf.org/html/draft-williams-overlaypath-ip-tcp-rfc-03
Diff:
http://www.ietf.org/rfcdiff?url2=draft-williams-overlaypath-ip-tcp-rfc-03
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.
The IETF Secretariat
_______________________________________________
Int-area mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/int-area
