IPv6 Tunneling for Embedded Systems (6bed4)
draft-vanrein-v6ops-6bed4-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Author | Rick van Rein | ||
| Last updated | 2011-07-25 | ||
| RFC stream | (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
Given the limited resources available to a lot of embedded systems, dual-stack solutions are not always feasible for such hosts. A mechanism that supports a direct transition from IPv4-only to IPv6-only may prove beneficial in getting the smallest hosts to make a transition to IPv6 at a much earlier stage than would otherwise be possible. This calls for tunnels, but no current tunnel technique appears to be optimal for embedded systems. This specification details an IPv6 tunneling technique over UDP and IPv4. The technique is specifically designed to benefit embedded systems, and to work without end user configuration. The working principle for obtaining a routable IPv6 address is through stateless autoconfiguration from an anycast tunnel service.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)