Assigned BGP extended communities
draft-ietf-idr-reserved-extended-communities-09
| Document | Type | Expired Internet-Draft (idr WG) | |
|---|---|---|---|
| Last updated | 2017-01-08 (latest revision 2016-07-07) | ||
| Replaces | draft-decraene-idr-reserved-extended-communities | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
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-reserved-extended-communities-09.txt
Abstract
This document defines an IANA registry in order to assign non- transitive extended communities from. These are similar to the existing well-known BGP communities defined in RFC 1997 but provide a control over inter-AS community advertisement as, per RFC RFC 4360, they are not transitive across Autonomous System boundaries. For that purpose, this document defines the use of the reserved Autonomous System number 0.65535 in the non-transitive generic four- octet AS specific extended community type.
Authors
Bruno Decraene
(bruno.decraene@orange.com)
Pierre Francois
(pifranco@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)