--- 1/draft-ietf-grow-collection-communities-07.txt 2006-02-04 17:27:01.000000000 +0100 +++ 2/draft-ietf-grow-collection-communities-08.txt 2006-02-04 17:27:01.000000000 +0100 @@ -1,17 +1,17 @@ GROW WG D. Meyer -Expires: February 18, 2006 +Expires: February 23, 2006 BGP Communities for Data Collection - draft-ietf-grow-collection-communities-07 + draft-ietf-grow-collection-communities-08 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that @@ -22,21 +22,21 @@ and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. - This Internet-Draft will expire on February 18, 2006. + This Internet-Draft will expire on February 23, 2006. Copyright Notice Copyright (C) The Internet Society (2005). Abstract BGP communities (RFC 1997) are used by service providers for many purposes, including tagging of customer, peer, and geographically originated routes. Such tagging is typically used to control the @@ -320,46 +320,46 @@ | 0x00 | Sub-Type | Global Administrator | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Local Administrator | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The two-octet AS specific extended community attribute encodes the service provider's two octet Autonomous System number (as assigned by a Regional Internet Registry, or RIR) in the Global Administrator field, and the Local Administrator field may encode any information. - This memo assigns Sub-Type 0x0006 for BGP data collection, and + This memo assigns Sub-Type 0x0008 for BGP data collection, and specifies that the field, as defined in section 3.1, is carried in the low order octets of the Local Administrator field. The two high order octets of the Local Administrator field are reserved, and are set to 0x00 when sending and ignored upon receipt. For example, the extended community encoding for 10876:4338 (representing a terrestrial national route in AS 10876 from the Fiji Islands) would be: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | 0x00 | 0x0006 | 0x2A7C | + | 0x00 | 0x0008 | 0x2A7C | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 0x00 | 0x00 | 0x10F2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 4.2. Four-octet AS specific extended communities The four-octet AS specific extended community is encoded as follows: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | 0x02 | 0x0006 | Global Administrator | + | 0x02 | 0x0008 | Global Administrator | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Global Administrator (cont.) | 0x10F2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ In this case, the 4 octet Global Administrator sub-field contains a 4-octets Autonomous System number assigned by the IANA. 5. Note on BGP UPDATE Packing Note that data collection communities have the potential of making @@ -413,21 +413,21 @@ behavior of an implementation when the attribute space overflows is crucial. Among other behaviors, an implementation might usurp the intended attribute data or otherwise cause indeterminate failures. These behaviors can result in unanticipated community attribute sets, and hence result in unintended policy implications. 8. IANA Considerations This memo assigns a new Sub-Type for the AS specific extended community type in the First Come First Served extended transitive - category. In particular, the IANA should assign Sub-type 0x0006 as + category. In particular, the IANA should assign Sub-type 0x0008 as defined in Section 4.1. In addition, this memo instructs the IANA to create two registries for BGP Data Collection Communities, one for standard communities and one for extended communities. Both of these registries should initially be populated by the values described in Section 4. IETF Consensus, usually through the Global Routing Operations Working Group (grow) is required for the assignment of new values in these registries (in particular, for or ), as described in Figure 2 [RFC2434].