ISATAP Updates
draft-templin-isupdate-04
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Fred Templin | ||
| Last updated | 2012-11-10 (Latest revision 2012-05-09) | ||
| 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
Many end user sites in the Internet today still have predominantly IPv4 internal infrastructures. These sites range in size from small home/office networks to large corporate enterprise networks, but share the commonality that IPv4 continues to provide operational internal routing and addressing services for most applications. As more and more IPv6-only services are deployed, however, end user devices within such sites will increasingly require at least basic IPv6 functionality. This document therefore discusses updates to the Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) to better accommodate these needs.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)