Skip to main content

BGP Extra Extended Community
draft-heitz-idr-extra-extended-community-02

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Jakob Heitz , Ali Sajassi , Ignas Bagdonas
Last updated 2019-07-22 (Latest revision 2019-01-14)
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

Auto-derived identifiers are used by applications to enable zero configuration features. Such identifiers are often a combination of primitive identifiers and are thus longer. In addition, existing identifiers have grown longer. IP addresses have grown from 4 octets to 16. AS numbers have grown from 2 octets to 4. In order to accommodate such longer identifiers in BGP extended communities, this document defines a new BGP path attribute, the Extra Extended Communities attribute. It is similar to the Extended Community, but is 24 octets long. Communities are mostly used within ASes under a single administration or between neighboring ASes. Limiting the spread of communities beyond their intended reach and polluting the internet at large is complex and error prone. To simplify this, enhanced transitivity options are provided.

Authors

Jakob Heitz
Ali Sajassi
Ignas Bagdonas

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