BGP Tunnel SAFI
draft-nalawade-kapoor-tunnel-safi-05
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Gargi Nalawade | ||
Last updated | 2006-06-29 | ||
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
There is a growing requirement for network operators to support multi-address familiy routing and forwarding services across their backbone networks. In general this is accomplished by constructing a mesh of tunnels between the backbbone provider edge routers and then advertising reachability to prefixes through specific tunnels. This document defines a new subsequence address family identifier associated with a tunnel end-point information. This enables a single egress provider edge router to use the border gateway protocol as a scalable and efficient means to distribute its tunnel end-point information to many ingress provider edge routers. The result is that the mesh of tunnels is in place and packets can be forwarded through these tunnels based on advertised reachability.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)