Large BGP CommunityCisco170 West Tasman DriveSan JoseCA95054USAjheitz@cisco.comCisco170 West Tasman DriveSan JoseCA95054USAkeyupate@cisco.comNTT Communications, Inc.Theodorus Majofskistraat 1001065 SZAmsterdamNLjob@ntt.netEquinixLondonUKibagdona.ietf@gmail.com
Routing
IDRBGPcommunitiesA new type of BGP community attribute that contains communities that each hold a 4-octet AS number and a 8-octet opaque field is defined.The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in .A BGP Community attribute is defined that encodes 12 byte communities, suitable for 4-Octet Autonomous System Numbers that require 8 octets of locally significant opaque data.To ensure rapid and smooth adoption of the new community attribute, it must be as similar to the community as possible, only bigger.The Large Community Attribute is a transitive optional BGP attribute, with the Type Code (suggested 41) to be assigned by IANA. The attribute consists of a set of "Large Communities". All routes with the Large Community attribute belong to the communities listed in the attribute.Each Large Community is encoded as a 12-octet quantity, as follows:
The textual representation of the Large BGP Community is A:B:C,
where A is the Autonomous System number, B is the Local Data
part 1 and C is the Local Data part 2. A ranges from 0 to
4294967295. B ranges from 0 to 4294967295. C ranges from 0 to
4294967295. A, B and C are plain decimal non-negative integers
without leading zeroes. Each number must appear, even if it is
0. For example, "0:1:2" cannot be written as ":1:2". The string
is expected to match the following regular expression:
^[0-9]+:[0-9]+:[0-9]+$ TBDIANA is requested to assign a BGP path attribute value for the Large community attribute.Thanks to Russ White, Acee Lindem, Shyam Sethuram and Jared Mauch for insightful review and comments.