draft-ietf-idr-large-community-11.txt   draft-ietf-idr-large-community-12.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: June 5, 2017 NTT Expires: July 9, 2017 NTT
K. Patel K. Patel
Arrcus Arrcus
I. Bagdonas I. Bagdonas
Equinix Equinix
N. Hilliard N. Hilliard
INEX INEX
December 2, 2016 January 5, 2017
BGP Large Communities BGP Large Communities
draft-ietf-idr-large-community-11 draft-ietf-idr-large-community-12
Abstract Abstract
This document describes the BGP Large Communities attribute, an This document describes the BGP Large 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 with four-octet management. The attribute is suitable for use with all Autonomous
Autonomous System Numbers. System Numbers including four-octet Autonomous System Numbers.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 47 skipping to change at page 1, line 47
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 June 5, 2017. This Internet-Draft will expire on July 9, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 5, line 16 skipping to change at page 5, line 16
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 BGP Large Communities Global Administrator field may contain any The BGP Large Communities Global Administrator field may contain any
value, and a BGP Large Communities attribute MUST NOT be considered value, and a BGP Large 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. unassigned or reserved ASN.
6. Security Considerations 6. Security Considerations
This extension to BGP has similar security implications as BGP
Communities [RFC1997].
This document does not change any underlying security issues This document does not change any underlying security issues
associated with any other BGP Communities mechanism. Specifically, associated with any other BGP Communities mechanism. Specifically,
an AS relying on the BGP Large Communities attribute carried in BGP an AS relying on the BGP Large Communities attribute carried in BGP
must have trust in every other AS in the path, as any intermediate must have trust in every other AS in the path, as any intermediate
Autonomous System in the path may have added, deleted, or altered the Autonomous System in the path may have added, deleted, or altered the
BGP Large Communities attribute. Specifying the mechanism to provide BGP Large Communities attribute. Specifying the mechanism to provide
such trust is beyond the scope of this document. such trust is beyond the scope of this document.
BGP Large Communities do not protect the integrity of each community BGP Large Communities do not protect the integrity of each community
value. Operators should be aware that it is possible for a BGP value. Operators should be aware that it is possible for a BGP
skipping to change at page 5, line 42 skipping to change at page 5, line 39
expressed BGP routing policies falls within the broader scope of expressed BGP routing policies falls within the broader scope of
securing BGP, and is not specifically addressed here. securing BGP, and is not specifically addressed here.
Network administrators should note the recommendations in Section 11 Network administrators should note the recommendations in Section 11
of BGP Operations and Security [RFC7454]. of BGP Operations and Security [RFC7454].
7. Implementation status - RFC EDITOR: REMOVE BEFORE PUBLICATION 7. Implementation status - RFC EDITOR: REMOVE BEFORE PUBLICATION
This section records the status of known implementations of the This section records the status of known implementations of the
protocol defined by this specification at the time of posting of this protocol defined by this specification at the time of posting of this
Internet-Draft, and is based on a proposal described in [RFC7942]. Internet-Draft, and is based on a proposal described in RFC7942. The
The description of implementations in this section is intended to description of implementations in this section is intended to assist
assist the IETF in its decision processes in progressing drafts to the IETF in its decision processes in progressing drafts to RFCs.
RFCs. Please note that the listing of any individual implementation Please note that the listing of any individual implementation here
here does not imply endorsement by the IETF. Furthermore, no effort does not imply endorsement by the IETF. Furthermore, no effort has
has been spent to verify the information presented here that was been spent to verify the information presented here that was supplied
supplied by IETF contributors. This is not intended as, and must not by IETF contributors. This is not intended as, and must not be
be construed to be, a catalog of available implementations or their construed to be, a catalog of available implementations or their
features. Readers are advised to note that other implementations may features. Readers are advised to note that other implementations may
exist. exist.
As of today these vendors have produced an implementation of BGP As of today these vendors have produced an implementation of BGP
Large Communities: Large Communities:
o Cisco IOS XR o Cisco IOS XR
o ExaBGP o ExaBGP
skipping to change at page 8, line 19 skipping to change at page 8, line 14
[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, [RFC7607] Kumari, W., Bush, R., Schiller, H., and K. Patel,
"Codification of AS 0 Processing", RFC 7607, "Codification of AS 0 Processing", RFC 7607,
DOI 10.17487/RFC7607, August 2015, DOI 10.17487/RFC7607, August 2015,
<http://www.rfc-editor.org/info/rfc7607>. <http://www.rfc-editor.org/info/rfc7607>.
[RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
Code: The Implementation Status Section", BCP 205,
RFC 7942, DOI 10.17487/RFC7942, July 2016,
<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
Jakob Heitz (editor) Jakob Heitz (editor)
Cisco Cisco
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95054 San Jose, CA 95054
 End of changes. 9 change blocks. 
23 lines changed or deleted 15 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/