Identification of IPv6 Routes that need Tunneling - Use of BGP Extended Community Attribute
draft-tsenevir-ipv6-bgp-tun-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Tissa Senevirathne | ||
| Last updated | 2002-06-11 | ||
| 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
In this document we provide methods to discover and connect native IPV6 clouds that are separated by IPV4 Internet. BGP-MP [2] is used as protocol to discover IPV6 relay routers. BGP-MP(BGP4+) [3] is used to distribute IPV6 routes. Encapsulation of IPV6 presented in [4] is used to tunnel IPv6 traffic across IPV4 Internet. The method presented here is known as 6in4 as opposed to 6to4 [4] or 6over4[5].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)