Extensions to RT-Constrain in Hierarchical Route Reflection Scenarios
draft-ietf-idr-rtc-hierarchical-rr-03
| Document | Type | Expired Internet-Draft (idr WG) | |
|---|---|---|---|
| Last updated | 2018-01-04 (latest revision 2017-07-03) | ||
| Replaces | draft-dong-idr-rtc-hierarchical-rr | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
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-rtc-hierarchical-rr-03.txt
Abstract
The Route Target (RT) Constrain mechanism specified in RFC 4684 is used to build a route distribution graph in order to restrict the propagation of Virtual Private Network (VPN) routes. In network scenarios where hierarchical route reflection (RR) is used, the existing RT-Constrain mechanism cannot guarantee a correct route distribution graph. This document describes the problem scenario and proposes a solution to address the RT-Constrain issue in hierarchical RR scenarios.
Authors
Jie Dong
(jie.dong@huawei.com)
Mach Chen
(mach.chen@huawei.com)
Robert Raszuk
(robert@raszuk.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)