Connecting IPV6 islands within a same IPV4 AS
draft-many-ngtrans-connect-ipv6-igp-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Geoffrey Cristallo | ||
| Last updated | 2002-03-01 | ||
| 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
This draft proposes a mechanism that allows an incremental deployment of IPv6 inside an IPv4 AS. It aims at automatically set up tunnels, using EGP standard capabilities, in order to gradually introduce IPv6 connectivity within an initially IPv4 AS. From a scope point of view, this technique must be considered as an intermediary between ISATAP and interdomain techniques ([6to4], [BGP-tunnel]).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)