Anycast-based replacement for Teredo
draft-rosenau-anycast-teredo-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Martin Rosenau | ||
| Last updated | 2018-08-08 (Latest revision 2018-02-04) | ||
| 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
Because of the shortage of remaining IPv4 addresses you have to expect that in a near time there will be IPv6-only services in the internet (such as web servers). Because many internet service providers do not support IPv6, yet, there is the need of a reliable translation mechanism so customers only having access to IPv4 only can access IPv6 services. This document describes a translation mechanism which is similar to the Teredo protocol [RFC4380]. However this protocol is based on anycast addressing and should also work with symmetric NATs.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)