--- 1/draft-ietf-grow-large-communities-usage-05.txt 2017-04-14 17:13:32.196482533 -0700 +++ 2/draft-ietf-grow-large-communities-usage-06.txt 2017-04-14 17:13:32.228483294 -0700 @@ -1,41 +1,41 @@ Global Routing Operations J. Snijders Internet-Draft J. Heasley Intended status: Informational NTT -Expires: September 28, 2017 M. Schmidt +Expires: October 16, 2017 M. Schmidt i3D.net - March 27, 2017 + April 14, 2017 Use of BGP Large Communities - draft-ietf-grow-large-communities-usage-05 + draft-ietf-grow-large-communities-usage-06 Abstract Examples and inspiration for operators to use BGP Large Communities. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. 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 September 28, 2017. + This Internet-Draft will expire on October 16, 2017. Copyright Notice Copyright (c) 2017 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 @@ -69,29 +69,31 @@ 4.3.2. Region Based Manipulation of LOCAL_PREF . . . . . . . 10 4.3.3. Note of Caution for LOCAL_PREF Functions . . . . . . 11 4.4. Route Server Prefix Distribution Control . . . . . . . . 11 5. Security Considerations . . . . . . . . . . . . . . . . . . . 12 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 8.1. Normative References . . . . . . . . . . . . . . . . . . 13 8.2. Informative References . . . . . . . . . . . . . . . . . 13 8.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 13 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 1. Introduction BGP Large Communities [RFC8092] provide a mechanism to signal opaque - information between Autonomous Systems (ASs). This document presents - examples of how operators might utilize BGP Large Communities to - achieve various goals. This document draws on the experience of - operator communities such as NANOG [1] and NLNOG [2]. + information between Autonomous Systems (ASs). In very much the same + way that [RFC1998] provides a concrete real-world application for + [RFC1997] communities, this document presents examples of how + operators might utilize BGP Large Communities to achieve various + goals. This document draws on the experience of operator communities + such as NANOG [1] and NLNOG [2]. 2. The Design Overview BGP Large Communities are composed of three 4-octet fields. The first is the Global Administrator (GA) field, whose value is the Autonomous System Number (ASN) of the AS that has defined the meaning of the remaining two 4-octet fields, known as "Local Data Part 1" and "Local Data Part 2". This document describes an approach where the "Local Data Part 1" field contains a function identifier and the "Local Data Part 2" contains a parameter value. Using the canonical @@ -539,41 +541,46 @@ 6. IANA Considerations None. 7. Acknowledgments The authors would like to gratefully acknowledge the insightful comments, contributions, critique and support from Adam Chappell, Jonathan Stewart, Greg Hankins, Nick Hilliard, Will Hargrave, Randy - Bush and Shawn Morris. + Bush, Shawn Morris and Jay Borkenhagen. 8. References 8.1. Normative References [RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities Attribute", RFC 1997, DOI 10.17487/RFC1997, August 1996, . [RFC7454] Durand, J., Pepelnjak, I., and G. Doering, "BGP Operations and Security", BCP 194, RFC 7454, DOI 10.17487/RFC7454, February 2015, . [RFC8092] Heitz, J., Ed., Snijders, J., Ed., Patel, K., Bagdonas, I., and N. Hilliard, "BGP Large Communities Attribute", RFC 8092, DOI 10.17487/RFC8092, February 2017, . 8.2. Informative References + [RFC1998] Chen, E. and T. Bates, "An Application of the BGP + Community Attribute in Multi-home Routing", RFC 1998, + DOI 10.17487/RFC1998, August 1996, + . + [RFC4264] Griffin, T. and G. Huston, "BGP Wedgies", RFC 4264, DOI 10.17487/RFC4264, November 2005, . [RFC7947] Jasinska, E., Hilliard, N., Raszuk, R., and N. Bakker, "Internet Exchange BGP Route Server", RFC 7947, DOI 10.17487/RFC7947, September 2016, . [RFC7948] Hilliard, N., Jasinska, E., Raszuk, R., and N. Bakker,