draft-ietf-idr-large-community-04.txt   draft-ietf-idr-large-community-05.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 27, 2017 NTT Expires: April 29, 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 24, 2016 October 26, 2016
Large BGP Communities Large BGP Communities
draft-ietf-idr-large-community-04 draft-ietf-idr-large-community-05
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 27, 2017. This Internet-Draft will expire on April 29, 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 4, line 36 skipping to change at page 4, line 36
Large BGP Communities MUST be represented as three separate unsigned Large BGP Communities MUST be represented as three separate unsigned
integers in decimal notation, without leading zeros, in the following integers in decimal notation, without leading zeros, in the following
order: Global Administrator, Local Data 1, Local Data 2. Numbers order: Global Administrator, Local Data 1, Local Data 2. Numbers
MUST not be omitted, even when zero. For example: 64496:4294967295:2 MUST not be omitted, even when zero. For example: 64496:4294967295:2
or 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 following Global Administrator values are reserved: 0 (the first The following Global Administrator values are reserved: 0 (the first
ASN) [RFC7607], 65535 (UINT_MAX) and 4294967295 (the last ASN) ASN) [RFC7607], 65535 (UINT16_MAX) and 4294967295 (the last ASN)
[RFC7300]. Operators SHOULD NOT use these Global Administrator [RFC7300]. Operators SHOULD NOT use these Global Administrator
values. values.
Although this document does not define any Special-Use Large BGP Although this document does not define any Special-Use Large BGP
Communities, the Global Administrator values specified above could be Communities, the Global Administrator values specified above could be
used if there is a future need for them. 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
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. 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,
skipping to change at page 6, line 17 skipping to change at page 6, line 17
o OpenBGPD o OpenBGPD
o pmacct o pmacct
The latest implementation news is tracked at The latest implementation news is tracked at
http://largebgpcommunities.net/ [1]. http://largebgpcommunities.net/ [1].
9. IANA Considerations 9. IANA Considerations
IANA has made an Early Allocation of the value 30 (LARGE_COMMUNITY) IANA has made an Early Allocation of the value 32 (LARGE_COMMUNITY)
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,
Bertrand Duvivier, Barry O'Donovan, Grzegorz Janoszka, Linda Dunbar, Bertrand Duvivier, Barry O'Donovan, Grzegorz Janoszka, Linda Dunbar,
Marco Davids, Gaurab Raj Upadhaya, Jeff Tantsura, Teun Vink, Adam Marco Davids, Gaurab Raj Upadhaya, Jeff Tantsura, Teun Vink, Adam
Davenport, Theodore Baschak, Pier Carlo Chiodi, Nabeel Cocker, Ian Davenport, Theodore Baschak, Pier Carlo Chiodi, Nabeel Cocker, Ian
Dickinson, Jan Baggen, Duncan Lockwood, David Farmer, Randy Bush, Wim Dickinson, Jan Baggen, Duncan Lockwood, David Farmer, Randy Bush, Wim
Henderickx, Stefan Plug, Kay Rechthien, Rob Shakir, Warren Kumari, Henderickx, Stefan Plug, Kay Rechthien, Rob Shakir, Warren Kumari,
Gert Doering, Thomas King, Mikael Abrahamsson, Wesley Steehouwer, Gert Doering, Thomas King, Mikael Abrahamsson, Wesley Steehouwer,
Sander Steffann, Brad Dreisbach, Martin Millnert, Christopher Morrow, Sander Steffann, Brad Dreisbach, Martin Millnert, Christopher Morrow,
Jay Borkenhagen, Arnold Nipper, Joe Provo, Niels Bakker, Bill Fenner, Jay Borkenhagen, Arnold Nipper, Joe Provo, Niels Bakker, Bill Fenner,
Tom Daly, Ben Maddison, Alexander Azimov, Brian Dickson, Peter van Tom Daly, Ben Maddison, Alexander Azimov, Brian Dickson, Peter van
Dijk, Julian Seifert, Tom Petch, Tom Scholl, Arjen Zonneveld, Remco Dijk, Julian Seifert, Tom Petch, Tom Scholl, Arjen Zonneveld, Remco
van Mook, Adam Chappell, Jussi Peltola, Kristian Larsson, and Markus van Mook, Adam Chappell, Jussi Peltola, Kristian Larsson, Markus
Hauschild for their support, insightful review and comments. Hauschild, Richard Steenbergen, and David Freedman 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
 End of changes. 8 change blocks. 
11 lines changed or deleted 9 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/