Procedures to handle duplicate Route Targets (RT) received by a BGP Speaker

Document Type Expired Internet-Draft (individual)
Last updated 2017-11-26 (latest revision 2017-05-25)
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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


Anup T (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)