Constrained Route Distribution for BGP based Virtual Private Networks(VPNs)
draft-dong-idr-vpn-route-constrain-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jie Dong , Hui Ni , Guiyan Liu , Zhenqiang Li | ||
| Last updated | 2010-09-27 | ||
| 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 are some problems with current RT-Constrain mechanism defined in RFC 4684. Firstly, the IPv6 address specific Route Target defined in [RFC5701] cannot be accommodated in current RT membership NLRI. Secondly, the distribution of RT-Constrain information cannot build correct VPN distribution graph when hierarchical route reflection (RR) is used. Thirdly, current RT-Constrain mechanism is used for filtering of all kinds of VPN services and can result in imprecise VPN route distribution when multiple VPN services are deployed in the network. This document describes the above problems in detail and proposes solutions for these problems. A generalized RT-Constrain mechanism is defined to accommodate the IPv6 address specific Route Target and to precisely control propagation of different kinds of VPN routing information. The proposed solution avoids unnecessary advertising and receiving of VPN routes when multiple VPN services are deployed. This document also proposes modifications of advertisement rules of RT- Constrain information to ensure the integrity of VPN distribution graph.
Authors
Jie Dong
Hui Ni
Guiyan Liu
Zhenqiang Li
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)