Signaling AFI-SAFI scope for Constrained Route Distribution
draft-ray-idr-route-constrain-scope-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Saikat Ray , Arjun Sreekantiah | ||
| Last updated | 2014-08-18 (Latest revision 2014-02-14) | ||
| 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
The Route Constrain address family can be used by a BGP speaker to signal a neighbor its interest in receiving only the routes with a matching route target (RT) extended community. This signaling is afi-safi agnostic; the sender of a route constrain NLRI with an RT expresses its interest in receiving routes with that RT for all afi- safi. The ability to further scope a given RT to a list of afi-safi would simplify network operations; then optimal route filtering would no longer require that the set of RTs used for different afi-safi be disjoint. This document proposes a simple extended community based backward compatible method to associate the list of afi-safi of interest to a route constrain NLRI and discusses the operational procedure.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)