--- 1/draft-ietf-grow-collection-communities-01.txt 2006-02-04 23:23:55.000000000 +0100 +++ 2/draft-ietf-grow-collection-communities-02.txt 2006-02-04 23:23:55.000000000 +0100 @@ -1,18 +1,18 @@ INTERNET-DRAFT D. Meyer -draft-ietf-grow-collection-communities-01.txt +draft-ietf-grow-collection-communities-02.txt Category Best Current Practice -Expires: June 2004 December 2003 +Expires: July 2004 January 2004 BGP Communities for Data Collection - + Status of this Document This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. @@ -31,21 +31,21 @@ 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 RFC 2119 [RFC 2119]. This document is a product of the GROW WG. Comments should be addressed to the authors, or the mailing list at grow@lists.uoregon.edu. Copyright Notice - Copyright (C) The Internet Society (2003). All Rights Reserved. + Copyright (C) The Internet Society (2004). All Rights Reserved. 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 scope of redistribution of routes within a provider's network, and to its peers and customers. With the advent of large scale BGP data collection (and associated research), it has become clear that the information carried in such communities is essential for a deeper @@ -228,42 +228,42 @@ Category Value =============================================================== Reserved :0000000000000000 Customer Routes :0000000000000001 Peer Routes :0000000000000010 Internal Routes :0000000000000011 Internal More Specific Routes :0000000000000100 Special Purpose Routes :0000000000000101 Upstream Routes :0000000000000110 - Reserved :0000000000000110- + Reserved :0000000000000011- :0000111111111111 National and Regional Routes :0001000000000000- :1111111111111111 Africa (AF) :0001 Oceania (OC) :0010 Asia (AS) :0011 Antarctica (AQ) :0100 Europe (EU) :0101 Latin America/Caribbean islands (LAC) :0110 North America (NA) :0111 Reserved :1000000000000000- :1111111111111111 In the above table, is the 16-bit AS is the 5-bit Region is 1-bit satellite link indication (1 if satellite link, 0 otherwise) is the 10-bit ISO-3166-2 country code - that is: + That is: 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | |X| | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ For example, the encoding for a national route over a terrestrial link in AS 10876 from the Fiji Islands would be: @@ -489,21 +490,21 @@ April, 2002. 10. Author's Addresses D. Meyer Email: dmm@1-4-5.net 11. Full Copyright Statement - Copyright (C) The Internet Society (2003). All Rights Reserved. + Copyright (C) The Internet Society (2004). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of