Automatic Route Target Filtering for legacy PEs
draft-ietf-idr-legacy-rtc-04
| The information below is for an old version of the document | |||
|---|---|---|---|
| Document | Type | Expired Internet-Draft (idr WG) | |
| Last updated | 2015-04-11 (latest revision 2014-10-08) | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-idr-legacy-rtc-04.txt
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 [RFC4684]. The intention of the proposed technique is to help in partial deployment scenarios and is not meant to replace [RFC4684].
Authors
Prodosh Mohapatra
(mpradosh@yahoo.com)
Arjun Sreekantiah
(asreekan@cisco.com)
Keyur Patel
(keyupate@cisco.com)
Burjiz
(bpithaw@cisco.com)
Alton Lo
(altonlo@aristanetworks.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)