Shipworm: Tunneling IPv6 over UDP through NATs
draft-huitema-shipworm-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Christian Huitema | ||
| Last updated | 2001-07-17 | ||
| 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
We propose here a service that would enable nodes located behind one or several IPv4 NATs to obtain IPv6 connectivity by tunneling packets over UDP; we call this the Shipworm service. The establishment of the tunnel is automatic, and does not require any configuration parameters on the client. Running the service requires the help of 'Shipworm servers' and 'Shipworm relays'; the Shipworm servers are stateless, and only have to manage a small fraction of the traffic between Shipworm clients; the Shipworm relays act as IPv6 routers between the Shipworm service and the 'native' IPv6 Internet.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)