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

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/