
BGP Well-known Communities per [RFC1997]

(last updated 12 April 2004)

The following communities have global significance and their
operations shall be implemented in any community-attribute-aware BGP
speaker.

NO_EXPORT (0xFFFFFF01)
    All routes received carrying a communities attribute
    containing this value MUST NOT be advertised outside a BGP
    confederation boundary (a stand-alone autonomous system that
    is not part of a confederation should be considered a
    confederation itself).

NO_ADVERTISE (0xFFFFFF02)
    All routes received carrying a communities attribute
    containing this value MUST NOT be advertised to other BGP
    peers.

NO_EXPORT_SUBCONFED (0xFFFFFF03)
    All routes received carrying a communities attribute
    containing this value MUST NOT be advertised to external BGP
    peers (this includes peers in other members autonomous
    systems inside a BGP confederation).
	
NOPEER (0xFFFFFF04)
    This is an advisory qualification to readvertisement of a route
    prefix, permitting an AS not to readvertise the route prefix to all
    external bilateral peer neighbour AS's. It is consistent with these
    semantics that an AS may filter received prefixes that are received
    across a peering session that the receiver regards as a bilateral
    peer sessions

References
----------
[RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities
          Attribute", RFC 1997, August 1996.

[RFC3765] G. Huston, "NOPEER community for BGP route scope control",
          RFC 3765, April 2004.

(created 2004-01-16)

[]












