--- 1/draft-ietf-idr-registered-wide-bgp-communities-00.txt 2015-11-22 20:15:06.864898341 -0800 +++ 2/draft-ietf-idr-registered-wide-bgp-communities-01.txt 2015-11-22 20:15:06.900899216 -0800 @@ -1,19 +1,19 @@ IDR Working Group R. Raszuk, Ed. -Internet-Draft Mirantis Inc. +Internet-Draft Bloomberg LP Intended status: Standards Track J. Haas -Expires: December 27, 2015 Juniper Networks - June 25, 2015 +Expires: May 23, 2016 Juniper Networks + November 20, 2015 Registered Wide BGP Community Values - draft-ietf-idr-registered-wide-bgp-communities-00 + draft-ietf-idr-registered-wide-bgp-communities-01 Abstract Communicating various routing policies via route tagging plays an important role in external BGP peering relations. The most common tool used today to attach various information about routes is realized with the use of BGP communities. Such information is important for the peering AS to perform some mutually agreed actions without the need to maintain a separate offline database for each pair of prefix and an associated with it requested set of action @@ -33,21 +33,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months 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." - This Internet-Draft will expire on December 27, 2015. + This Internet-Draft will expire on May 23, 2016. Copyright Notice Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -74,21 +74,21 @@ 2.2.8. GEO-LOCATION Registered Community . . . . . . . . . . 12 3. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 4. ECMP Hint Registered Community . . . . . . . . . . . . . . . 14 5. Security considerations . . . . . . . . . . . . . . . . . . . 14 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 16 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 17 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 9.1. Normative References . . . . . . . . . . . . . . . . . . 17 9.2. Informative References . . . . . . . . . . . . . . . . . 17 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 1. Introduction RFC 1997 [RFC1997] defines a BGP Community Attribute to be used as a tool to contain in BGP update message various additional information about routes which may help to automate peering administration. As defined in RFC 1997 [RFC1997] BGP Communities attribute consists of one or more sets of four octet values, where each one of them specifies a different community. Except two reserved ranges the encoding of community values mandates that first two octets are to @@ -727,51 +727,63 @@ 8. Acknowledgments Authors would like to thank Enke Chen, Pedro Marques, Alton Lo and Jeff Wheeler for their valuable input. 9. References 9.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate - Requirement Levels", BCP 14, RFC 2119, March 1997. + Requirement Levels", BCP 14, RFC 2119, + DOI 10.17487/RFC2119, March 1997, + . - [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway - Protocol 4 (BGP-4)", RFC 4271, January 2006. + [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A + Border Gateway Protocol 4 (BGP-4)", RFC 4271, + DOI 10.17487/RFC4271, January 2006, + . [RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended - Communities Attribute", RFC 4360, February 2006. + Communities Attribute", RFC 4360, DOI 10.17487/RFC4360, + February 2006, . 9.2. Informative References - [RFC1997] Chandrasekeran, R., Traina, P., and T. Li, "BGP - Communities Attribute", RFC 1997, August 1996. + [RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities + Attribute", RFC 1997, DOI 10.17487/RFC1997, August 1996, + . [RFC1998] Chen, E. and T. Bates, "An Application of the BGP Community Attribute in Multi-home Routing", RFC 1998, - August 1996. + DOI 10.17487/RFC1998, August 1996, + . [RFC4384] Meyer, D., "BGP Communities for Data Collection", BCP 114, - RFC 4384, February 2006. + RFC 4384, DOI 10.17487/RFC4384, February 2006, + . [RFC4893] Vohra, Q. and E. Chen, "BGP Support for Four-octet AS - Number Space", RFC 4893, May 2007. + Number Space", RFC 4893, DOI 10.17487/RFC4893, May 2007, + . [RFC5668] Rekhter, Y., Sangli, S., and D. Tappan, "4-Octet AS - Specific BGP Extended Community", RFC 5668, October 2009. + Specific BGP Extended Community", RFC 5668, + DOI 10.17487/RFC5668, October 2009, + . Authors' Addresses + Robert Raszuk (editor) - Mirantis Inc. - 615 National Ave. #100 - Mt View, CA 94043 + Bloomberg LP + 731 Lexington Ave + New York City, NY 10022 USA Email: robert@raszuk.net Jeffrey Haas Juniper Networks 1194 N.Mathilda Ave Sunnyvale, CA 94089 US