Automatic Route Target Filtering for legacy PEs
draft-l3vpn-legacy-rtc-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Prodosh Mohapatra , Arjun Sreekantiah , Keyur Patel , Alton Lo | ||
| Last updated | 2011-03-04 | ||
| Replaced by | draft-ietf-idr-legacy-rtc | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-idr-legacy-rtc | |
| 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 document describes a simple procedure that allows "legacy" BGP speakers to exchange route target membership information in BGP without using mechanisms specified in RFC 4684. The intention of the proposed technique is to help in partial deployment scenarios and is not meant to replace RFC 4684.
Authors
Prodosh Mohapatra
Arjun Sreekantiah
Keyur Patel
Alton Lo
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)