draft-ietf-idr-communities-00.txt   rfc1997.txt 
Internet Engineering Task Force Ravi Chandra Network Working Group R. Chandra
INTERNET DRAFT Paul Traina Request for Comments: 1997 P. Traina
<draft-ietf-idr-communities-00.txt> cisco Systems Category: Standards Track cisco Systems
Tony Li T. Li
April 10, 1996 August 1996
BGP communities attribute
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard. Distribution of this memo is
unlimited.
This document is an Internet Draft. Internet Drafts are working BGP Communities Attribute
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.
Internet Drafts are draft documents valid for a maximum of six Status of This Memo
months. Internet Drafts may be updated, replaced, or obsoleted by
other documents at any time. It is not appropriate to use Internet
Drafts as reference material or to cite them other than as a "working
draft" or "work in progress".
Please check the I-D abstract listing contained in each Internet This document specifies an Internet standards track protocol for the
Draft directory to learn the current status of this or any other Internet community, and requests discussion and suggestions for
Internet Draft. improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Abstract Abstract
Border Gateway Protocol [1] is an inter-autonomous system routing Border Gateway Protocol [1] is an inter-autonomous system routing
protocol designed for TCP/IP internets. protocol designed for TCP/IP internets.
This document describes an extension to BGP which may be used to pass This document describes an extension to BGP which may be used to pass
additional information to both neighboring and remote BGP peers. additional information to both neighboring and remote BGP peers.
The intention of the proposed technique is to aid in policy The intention of the proposed technique is to aid in policy
skipping to change at page 3, line 39 skipping to change at page 3, line 24
690 may define research, educational and commercial community values 690 may define research, educational and commercial community values
that may be used for policy routing as defined by the operators of that may be used for policy routing as defined by the operators of
that AS using community attribute values 0x02B20000 through that AS using community attribute values 0x02B20000 through
0x02B2FFFF). 0x02B2FFFF).
Well-known Communities Well-known Communities
The following communities have global significance and their The following communities have global significance and their
operations shall be implemented in any community-attribute-aware BGP operations shall be implemented in any community-attribute-aware BGP
speaker. speaker.
NO_EXPORT (0xFFFFFF01) NO_EXPORT (0xFFFFFF01)
All routes received carrying a communities attribute containing All routes received carrying a communities attribute
this value MUST NOT be advertised outside a BGP confederation containing this value MUST NOT be advertised outside a BGP
boundary (a stand-alone autonomous system that is not part of a confederation boundary (a stand-alone autonomous system that
confederation should be considered a confederation itself). is not part of a confederation should be considered a
confederation itself).
NO_ADVERTISE (0xFFFFFF02) NO_ADVERTISE (0xFFFFFF02)
All routes received carrying a communities attribute containing All routes received carrying a communities attribute
this value MUST NOT be advertised to other BGP peers. containing this value MUST NOT be advertised to other BGP
peers.
NO_EXPORT_SUBCONFED (0xFFFFFF03) NO_EXPORT_SUBCONFED (0xFFFFFF03)
All routes received carrying a communities attribute containing All routes received carrying a communities attribute
this value MUST NOT be advertised to external BGP peers (this containing this value MUST NOT be advertised to external BGP
includes peers in other members autonomous systems inside a BGP peers (this includes peers in other members autonomous
confederation). systems inside a BGP confederation).
Operation Operation
A BGP speaker may use this attribute to control which routing A BGP speaker may use this attribute to control which routing
information it accepts, prefers or distributes to other neighbors. information it accepts, prefers or distributes to other neighbors.
A BGP speaker receiving a route that does not have the COMMUNITIES A BGP speaker receiving a route that does not have the COMMUNITIES
path attribute may append this attribute to the route when path attribute may append this attribute to the route when
propagating it to its peers. propagating it to its peers.
skipping to change at page 4, line 33 skipping to change at page 4, line 19
the resulting aggregate should have a COMMUNITIES path attribute the resulting aggregate should have a COMMUNITIES path attribute
which contains all communities from all of the aggregated routes. which contains all communities from all of the aggregated routes.
Applicability Applicability
The COMMUNITIES path attribute may be used with BGP version 2 and all The COMMUNITIES path attribute may be used with BGP version 2 and all
subsequent versions of BGP unless specifically noted otherwise. subsequent versions of BGP unless specifically noted otherwise.
Security Considerations Security Considerations
Security considerations are not discussed in this memo. Security issues are not discussed in this memo.
Acknowledgments Acknowledgments
We'd like to thank Vince Fuller, Sean Doran, and Andrew Partan for We'd like to thank Vince Fuller, Sean Doran, and Andrew Partan for
bringing to our attention the problems that we believe the BGP bringing to our attention the problems that we believe the BGP
communities attribute will help solve. We'd also like to thank Yakov communities attribute will help solve. We'd also like to thank Yakov
Rekhter his review of this document as well as his constructive and Rekhter his review of this document as well as his constructive and
valuable comments. valuable comments.
Author's Addresses: Authors' Addresses
Paul Traina Paul Traina
cisco Systems, Inc. cisco Systems, Inc.
170 W. Tasman Dr. 170 W. Tasman Dr.
San Jose, CA 95134 San Jose, CA 95134
pst@cisco.com
EMail: pst@cisco.com
Ravishanker Chandrasekeran Ravishanker Chandrasekeran
(Ravi Chandra) (Ravi Chandra)
cisco Systems, Inc. cisco Systems, Inc.
170 W. Tasman Dr. 170 W. Tasman Dr.
San Jose, CA 95134 San Jose, CA 95134
rchandra@cisco.com
EMail: rchandra@cisco.com
Tony Li Tony Li
tli@skat.usc.edu EMail: tli@skat.usc.edu
References References
[1] RFC1771 [1] RFC 1771
Rekhter, Y., and Li, T., "A Border Gateway Protocol 4 (BGP-4)", March Rekhter, Y., and T. Li, "A Border Gateway Protocol 4 (BGP-4)",
1995. March 1995.
[2] draft-ietf-idr-bgp-confed-00.txt [2] RFC 1965
Traina, P. "Autonomous System Confederations for BGP", December Traina, P., "Autonomous System Confederations for BGP", June 1996.
1995, Internet Draft: work in progress.
 End of changes. 15 change blocks. 
43 lines changed or deleted 35 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/