Controlling VPN Routes More Precisely by ORF Extension
draft-sun-bess-vpn-orf-extension-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Chunxia Sun , Yaokun Zhang , Donald E. Eastlake 3rd | ||
| Last updated | 2019-04-25 (Latest revision 2018-10-22) | ||
| 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
RFC 4684 defines Multi-Protocol BGP (MP-BGP) procedures that allow BGP speakers to exchange Route Target reachability information which can be used to build a route distribution graph in order to limit the propagation of Virtual Private Network (VPN) Network Layer Reachability Information (NLRI) between different autonomous systems or distinct clusters of the same autonomous system. However, according to RFC 4684, in some scenarios, more routes will be sent than need to be sent. This document extends RFC 4684. This extension allows a BGP speaker to advertise VPN routes more precisely.
Authors
Chunxia Sun
Yaokun Zhang
Donald E. Eastlake 3rd
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)