Procedures to handle duplicate Route Targets (RT) received by a BGP Speaker
draft-anup-idr-bgp-duplicate-rt-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Anup Kumar T | ||
| Last updated | 2017-11-26 (Latest revision 2017-05-25) | ||
| 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
This document describes why duplicate suppression should not be applied to BGP Route Target (RT) Address Family. It also explains the problems incurred if duplicate suppression is applied to BGP route constraints AF
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)