Reserved BGP extended communities
draft-decraene-idr-reserved-extended-communities-00
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Bruno Decraene , Pierre Francois | ||
Last updated | 2012-04-18 (Latest revision 2010-10-18) | ||
Replaced by | draft-ietf-idr-reserved-extended-communities | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-idr-reserved-extended-communities | |
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 assigns two BGP extended community types, one transitive and one non-transitive. It also defines two IANA registries in order to allow the allocation of reserved transitive and non-transitive extended communities. These are similar to the existing reserved (formerly Well-known) BGP communities defined in RFC 1997 but provides an easier control of inter-AS community advertissement as a community could be chosen as transitive or non- transitive across ASes.
Authors
Bruno Decraene
Pierre Francois
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)