draft-ietf-idr-large-community-03.txt   draft-ietf-idr-large-community-04.txt 
IDR J. Heitz, Ed. IDR J. Heitz, Ed.
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Standards Track J. Snijders, Ed. Intended status: Standards Track J. Snijders, Ed.
Expires: April 19, 2017 NTT Expires: April 27, 2017 NTT
K. Patel K. Patel
Arrcus Arrcus
I. Bagdonas I. Bagdonas
Equinix Equinix
A. Simpson A. Simpson
Nokia Nokia
N. Hilliard N. Hilliard
INEX INEX
October 16, 2016 October 24, 2016
Large BGP Communities Large BGP Communities
draft-ietf-idr-large-community-03 draft-ietf-idr-large-community-04
Abstract Abstract
This document describes the Large BGP Communities attribute, an This document describes the Large BGP Communities attribute, an
extension to BGP-4. This attribute provides a mechanism to signal extension to BGP-4. This attribute provides a mechanism to signal
opaque information within separate namespaces to aid in routing opaque information within separate namespaces to aid in routing
management. The attribute is suitable for use in four-octet ASNs. management. The attribute is suitable for use in four-octet ASNs.
Requirements Language Requirements Language
skipping to change at page 1, line 48 skipping to change at page 1, line 48
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 19, 2017. This Internet-Draft will expire on April 27, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 36 skipping to change at page 2, line 36
5. Reserved Large BGP Community values . . . . . . . . . . . . . 4 5. Reserved Large BGP Community values . . . . . . . . . . . . . 4
6. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 4 6. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 4
7. Security Considerations . . . . . . . . . . . . . . . . . . . 5 7. Security Considerations . . . . . . . . . . . . . . . . . . . 5
8. Implementation status - RFC EDITOR: REMOVE BEFORE PUBLICATION 5 8. Implementation status - RFC EDITOR: REMOVE BEFORE PUBLICATION 5
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
11.1. Normative References . . . . . . . . . . . . . . . . . . 6 11.1. Normative References . . . . . . . . . . . . . . . . . . 6
11.2. Informative References . . . . . . . . . . . . . . . . . 7 11.2. Informative References . . . . . . . . . . . . . . . . . 7
11.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 7 11.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
BGP implementations typically support a routing policy language to BGP implementations typically support a routing policy language to
control the distribution of routing information. Network operators control the distribution of routing information. Network operators
attach BGP communities to routes to identify intrinsic properties of attach BGP communities to routes to identify intrinsic properties of
these routes. These properties may include information such as the these routes. These properties may include information such as the
route origin location, or specification of a routing policy action to route origin location, or specification of a routing policy action to
be taken, or one that has been taken, and may apply to an individual be taken, or one that has been taken, and may apply to an individual
route or to a group of routes. Because BGP communities are optional route or to a group of routes. Because BGP communities are optional
transitive BGP attributes, BGP communities may be acted upon or transitive BGP attributes, BGP communities may be acted upon or
otherwise used by routing policies in other Autonomous Systems (ASes) otherwise used by routing policies in other Autonomous Systems (ASes)
on the Internet. on the Internet.
[RFC1997] BGP Communities attributes are four-octet values split into [RFC1997] BGP Communities attributes are four-octet values split into
two two-octet words. The most significant word is usually two two-octet words. The most significant word is interpreted as an
interpreted as an Autonomous System Number (ASN) and the least Autonomous System Number (ASN) and the least significant word is a
significant word is a locally defined value whose meaning is assigned locally defined value whose meaning is assigned by the operator of
by the operator of the Autonomous System in the most significant the Autonomous System in the most significant word.
word.
Since the adoption of four-octet ASNs [RFC6793], the BGP Communities Since the adoption of four-octet ASNs [RFC6793], the BGP Communities
attribute can no longer accommodate the above encoding, as a two- attribute can no longer accommodate the above encoding, as a two-
octet word cannot fit a four-octet ASN. The BGP Extended Communities octet word cannot fit a four-octet ASN. The BGP Extended Communities
attribute [RFC4360] is also unsuitable, as the protocol limit of six attribute [RFC4360] is also unsuitable, as the protocol limit of six
octets cannot accommodate both a four-octet Global Administrator octets cannot accommodate both a four-octet Global Administrator
value and a four-octet Local Administrator value, which precludes the value and a four-octet Local Administrator value, which precludes the
common operational practice of encoding a target ASN in the Local common operational practice of encoding a target ASN in the Local
Administrator field. Administrator field.
skipping to change at page 4, line 11 skipping to change at page 4, line 11
Local Data Part 1: A four-octet operator-defined value. Local Data Part 1: A four-octet operator-defined value.
Local Data Part 2: A four-octet operator-defined value. Local Data Part 2: A four-octet operator-defined value.
The Global Administrator field is intended to allow different The Global Administrator field is intended to allow different
Autonomous Systems to define Large BGP Communities without collision. Autonomous Systems to define Large BGP Communities without collision.
Implementations MUST allow the operator to specify any value for the Implementations MUST allow the operator to specify any value for the
Global Administrator field. Global Administrator field.
There is no significance to the order in which Large BGP Communities There is no significance to the order in which Large BGP Communities
are encoded in a path attributes field and a receiving speaker MAY are encoded in the BGP path attribute payload. A BGP speaker can
retransmit them in an order different from which it received them. transmit them in any order.
Duplicate Large BGP Communities SHOULD NOT be transmitted. A Duplicate Large BGP Communities SHOULD NOT be transmitted. A
receiving speaker SHOULD silently remove duplicate Large BGP receiving speaker SHOULD silently remove duplicate Large BGP
Communities from a BGP UPDATE message. Communities from a BGP UPDATE message.
3. Aggregation 3. Aggregation
If a range of routes is aggregated, then the resulting aggregate If a range of routes is aggregated, then the resulting aggregate
should have a Large BGP Communities attribute which contains all of should have a Large BGP Communities attribute which contains all of
the Large BGP Communities attributes from all of the aggregated the Large BGP Communities attributes from all of the aggregated
routes. routes.
4. Canonical Representation 4. Canonical Representation
Large BGP Communities MUST be represented as three separate unsigned Large BGP Communities MUST be represented as three separate unsigned
decimal numbers, without leading zeros, in the following order: integers in decimal notation, without leading zeros, in the following
Global Administrator, Local Data 1, Local Data 2. Numbers MUST not order: Global Administrator, Local Data 1, Local Data 2. Numbers
be omitted, even when zero. For example: 64496:4294967295:2 or MUST not be omitted, even when zero. For example: 64496:4294967295:2
64496:0:0 or (64496, 111, 222). or 64496:0:0 or (64496, 111, 222).
5. Reserved Large BGP Community values 5. Reserved Large BGP Community values
The Large BGP Community attribute values in the following ranges are The following Global Administrator values are reserved: 0 (the first
reserved: ASN) [RFC7607], 65535 (UINT_MAX) and 4294967295 (the last ASN)
[RFC7300]. Operators SHOULD NOT use these Global Administrator
values.
0:0:0 - 0:4294967295:4294967295 Although this document does not define any Special-Use Large BGP
65535:0:0 - 65535:4294967295:4294967295 Communities, the Global Administrator values specified above could be
4294967295:0:0 - 4294967295:4294967295:4294967295 used if there is a future need for them.
6. Error Handling 6. Error Handling
The error handling of Large BGP Communities is as follows: The error handling of Large BGP Communities is as follows:
o A Large BGP Communities attribute with a length of zero MUST be o A Large BGP Communities attribute with a length of zero MUST be
ignored upon receipt and removed when sending. ignored upon receipt and removed when sending.
o A Large BGP Communities attribute SHALL be considered malformed if o A Large BGP Communities attribute SHALL be considered malformed if
its length is not a non-zero multiple of 12 bytes. its length is not a non-zero multiple of 12.
o A BGP UPDATE message with a malformed Large BGP Communities o A BGP UPDATE message with a malformed Large BGP Communities
attribute SHALL be handled using the approach of "treat-as- attribute SHALL be handled using the approach of "treat-as-
withdraw" as described in section 2 [RFC7606]. withdraw" as described in section 2 [RFC7606].
The Large BGP Communities Global Administrator field may contain any The Large BGP Communities Global Administrator field may contain any
value, and a Large BGP Communities attribute MUST NOT be considered value, and a Large BGP Communities attribute MUST NOT be considered
malformed if the Global Administrator field contains an unallocated, malformed if the Global Administrator field contains an unallocated,
unassigned or reserved ASN or is set to one of the reserved Large BGP unassigned or reserved ASN or is set to one of the reserved Large BGP
Community values defined in Section 5. Community values defined in Section 5.
skipping to change at page 6, line 28 skipping to change at page 6, line 28
in the "BGP Path Attributes" registry under the "Border Gateway in the "BGP Path Attributes" registry under the "Border Gateway
Protocol (BGP) Parameters" group and is now asked to make that Protocol (BGP) Parameters" group and is now asked to make that
Permanent. Permanent.
10. Acknowledgments 10. Acknowledgments
The authors would like to thank Ruediger Volk, Russ White, Acee The authors would like to thank Ruediger Volk, Russ White, Acee
Lindem, Shyam Sethuram, Jared Mauch, Joel M. Halpern, Jeffrey Haas, Lindem, Shyam Sethuram, Jared Mauch, Joel M. Halpern, Jeffrey Haas,
John Heasley, Gunter van de Velde, Marco Marzetti, Eduardo Ascenco John Heasley, Gunter van de Velde, Marco Marzetti, Eduardo Ascenco
Reis, Mark Schouten, Paul Hoogsteder, Martijn Schmidt, Greg Hankins, Reis, Mark Schouten, Paul Hoogsteder, Martijn Schmidt, Greg Hankins,
Acee Lindem, Bertrand Duvivier, Barry O'Donovan, Grzegorz Janoszka, Bertrand Duvivier, Barry O'Donovan, Grzegorz Janoszka, Linda Dunbar,
Linda Dunbar, Marco Davids, Gaurab Raj Upadhaya, Jeff Tantsura, Teun Marco Davids, Gaurab Raj Upadhaya, Jeff Tantsura, Teun Vink, Adam
Vink, Adam Davenport, Theodore Baschak, Pier Carlo Chiodi, Nabeel Davenport, Theodore Baschak, Pier Carlo Chiodi, Nabeel Cocker, Ian
Cocker, Ian Dickinson, Jan Baggen, Duncan Lockwood, David Farmer, Dickinson, Jan Baggen, Duncan Lockwood, David Farmer, Randy Bush, Wim
Randy Bush, Wim Henderickx, Stefan Plug, Kay Rechthien, Rob Shakir, Henderickx, Stefan Plug, Kay Rechthien, Rob Shakir, Warren Kumari,
Warren Kumari, Gert Doering, Thomas King, Mikael Abrahamsson, Wesley Gert Doering, Thomas King, Mikael Abrahamsson, Wesley Steehouwer,
Steehouwer, Sander Steffann, Brad Dreisbach, Martin Millnert, Sander Steffann, Brad Dreisbach, Martin Millnert, Christopher Morrow,
Christopher Morrow, Jay Borkenhagen, Arnold Nipper, Joe Provo, Niels Jay Borkenhagen, Arnold Nipper, Joe Provo, Niels Bakker, Bill Fenner,
Bakker, Bill Fenner, Tom Daly, Ben Maddison, Alexander Azimov, Brian Tom Daly, Ben Maddison, Alexander Azimov, Brian Dickson, Peter van
Dickson, Peter van Dijk, Julian Seifert, Tom Petch, Tom Scholl, Arjen Dijk, Julian Seifert, Tom Petch, Tom Scholl, Arjen Zonneveld, Remco
Zonneveld, and Remco van Mook for their support, insightful review van Mook, Adam Chappell, Jussi Peltola, Kristian Larsson, and Markus
and comments. Hauschild for their support, insightful review and comments.
11. References 11. References
11.1. Normative References 11.1. Normative References
[RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities [RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities
Attribute", RFC 1997, DOI 10.17487/RFC1997, August 1996, Attribute", RFC 1997, DOI 10.17487/RFC1997, August 1996,
<http://www.rfc-editor.org/info/rfc1997>. <http://www.rfc-editor.org/info/rfc1997>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
skipping to change at page 7, line 26 skipping to change at page 7, line 26
Patel, "Revised Error Handling for BGP UPDATE Messages", Patel, "Revised Error Handling for BGP UPDATE Messages",
RFC 7606, DOI 10.17487/RFC7606, August 2015, RFC 7606, DOI 10.17487/RFC7606, August 2015,
<http://www.rfc-editor.org/info/rfc7606>. <http://www.rfc-editor.org/info/rfc7606>.
11.2. Informative References 11.2. Informative References
[RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended [RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended
Communities Attribute", RFC 4360, DOI 10.17487/RFC4360, Communities Attribute", RFC 4360, DOI 10.17487/RFC4360,
February 2006, <http://www.rfc-editor.org/info/rfc4360>. February 2006, <http://www.rfc-editor.org/info/rfc4360>.
[RFC7300] Haas, J. and J. Mitchell, "Reservation of Last Autonomous
System (AS) Numbers", BCP 6, RFC 7300,
DOI 10.17487/RFC7300, July 2014,
<http://www.rfc-editor.org/info/rfc7300>.
[RFC7454] Durand, J., Pepelnjak, I., and G. Doering, "BGP Operations [RFC7454] Durand, J., Pepelnjak, I., and G. Doering, "BGP Operations
and Security", BCP 194, RFC 7454, DOI 10.17487/RFC7454, and Security", BCP 194, RFC 7454, DOI 10.17487/RFC7454,
February 2015, <http://www.rfc-editor.org/info/rfc7454>. February 2015, <http://www.rfc-editor.org/info/rfc7454>.
[RFC7607] Kumari, W., Bush, R., Schiller, H., and K. Patel,
"Codification of AS 0 Processing", RFC 7607,
DOI 10.17487/RFC7607, August 2015,
<http://www.rfc-editor.org/info/rfc7607>.
[RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
Code: The Implementation Status Section", BCP 205, Code: The Implementation Status Section", BCP 205,
RFC 7942, DOI 10.17487/RFC7942, July 2016, RFC 7942, DOI 10.17487/RFC7942, July 2016,
<http://www.rfc-editor.org/info/rfc7942>. <http://www.rfc-editor.org/info/rfc7942>.
11.3. URIs 11.3. URIs
[1] http://largebgpcommunities.net [1] http://largebgpcommunities.net
Authors' Addresses Authors' Addresses
skipping to change at page 8, line 4 skipping to change at page 8, line 14
Authors' Addresses Authors' Addresses
Jakob Heitz (editor) Jakob Heitz (editor)
Cisco Cisco
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95054 San Jose, CA 95054
USA USA
Email: jheitz@cisco.com Email: jheitz@cisco.com
Job Snijders (editor) Job Snijders (editor)
NTT Communications NTT Communications
Theodorus Majofskistraat 100 Theodorus Majofskistraat 100
Amsterdam 1065 SZ Amsterdam 1065 SZ
NL The Netherlands
Email: job@ntt.net Email: job@ntt.net
Keyur Patel Keyur Patel
Arrcus, Inc Arrcus, Inc
Email: keyur@arrcus.com Email: keyur@arrcus.com
Ignas Bagdonas Ignas Bagdonas
Equinix Equinix
 End of changes. 16 change blocks. 
35 lines changed or deleted 47 lines changed or added

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