Automatic Route Target Filtering for legacy PEs
draft-ietf-idr-legacy-rtc-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Prodosh Mohapatra , Arjun Sreekantiah , Keyur Patel , Burjiz , Alton Lo | ||
| Last updated | 2012-07-30 (Latest revision 2012-01-18) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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
Burjiz
Alton Lo
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)