draft-ietf-idr-reserved-extended-communities-08.txt   draft-ietf-idr-reserved-extended-communities-09.txt 
Network Working Group B. Decraene Network Working Group B. Decraene
Internet-Draft Orange Internet-Draft Orange
Intended status: Standards Track P. Francois Intended status: Standards Track P. Francois
Expires: July 17, 2015 IMDEA Networks Expires: January 8, 2017 Cisco Systems, Inc.
January 13, 2015 July 7, 2016
Assigned BGP extended communities Assigned BGP extended communities
draft-ietf-idr-reserved-extended-communities-08 draft-ietf-idr-reserved-extended-communities-09
Abstract Abstract
This document defines an IANA registry in order to assign non- This document defines an IANA registry in order to assign non-
transitive extended communities from. These are similar to the transitive extended communities from. These are similar to the
existing well-known BGP communities defined in RFC 1997 but provide a existing well-known BGP communities defined in RFC 1997 but provide a
control over inter-AS community advertisement as, per RFC RFC 4360, control over inter-AS community advertisement as, per RFC RFC 4360,
they are not transitive across Autonomous System boundaries. they are not transitive across Autonomous System boundaries.
For that purpose, this document defines the use of the reserved For that purpose, this document defines the use of the reserved
skipping to change at page 1, line 45 skipping to change at page 1, line 45
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 July 17, 2015. This Internet-Draft will expire on January 8, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2015 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
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 10 skipping to change at page 5, line 10
6. Acknowledgements 6. Acknowledgements
We would like to acknowledge John Scudder, Jeffrey Haas and Yakov We would like to acknowledge John Scudder, Jeffrey Haas and Yakov
Rekhter for their contribution to this document. Rekhter for their contribution to this document.
7. Normative References 7. Normative References
[I-D.ietf-idr-as4octet-extcomm-generic-subtype] [I-D.ietf-idr-as4octet-extcomm-generic-subtype]
Rao, D., Mohapatra, P., and J. Haas, "Generic Subtype for Rao, D., Mohapatra, P., and J. Haas, "Generic Subtype for
BGP Four-octet AS specific extended community", draft- BGP Four-octet AS specific extended community", draft-
ietf-idr-as4octet-extcomm-generic-subtype-07 (work in ietf-idr-as4octet-extcomm-generic-subtype-08 (work in
progress), July 2014. progress), June 2015.
[RFC1997] Chandrasekeran, R., Traina, P., and T. Li, "BGP [RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities
Communities Attribute", RFC 1997, August 1996. Attribute", RFC 1997, DOI 10.17487/RFC1997, August 1996,
<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
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended [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, <http://www.rfc-editor.org/info/rfc4360>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>.
[RFC6793] Vohra, Q. and E. Chen, "BGP Support for Four-Octet [RFC6793] Vohra, Q. and E. Chen, "BGP Support for Four-Octet
Autonomous System (AS) Number Space", RFC 6793, December Autonomous System (AS) Number Space", RFC 6793,
2012. DOI 10.17487/RFC6793, December 2012,
<http://www.rfc-editor.org/info/rfc6793>.
Appendix A. Appendix A. Changes / Author Notes Appendix A. Appendix A. Changes / Author Notes
[RFC Editor: Please remove this section before publication ] [RFC Editor: Please remove this section before publication ]
Changes -01: Changes -01:
o Name changed from 'Reserved BGP extended communities' to 'Assigned o Name changed from 'Reserved BGP extended communities' to 'Assigned
BGP extended communities' BGP extended communities'
skipping to change at page 6, line 9 skipping to change at page 6, line 14
o Remove the transitive flavor of assigned extended communities. o Remove the transitive flavor of assigned extended communities.
RFC 1997 well-known standard communities to be used instead. RFC 1997 well-known standard communities to be used instead.
Changes -04: no change, refresh only. Changes -04: no change, refresh only.
Changes -05: minor editorial change (RFC 4893 obsoleted by 6793). Changes -05: minor editorial change (RFC 4893 obsoleted by 6793).
Changes -06: typo fixed, minor editorial change. Changes -06: typo fixed, minor editorial change.
Changes -07, 08: no change, refresh only. Changes -07, 08, 09: no change, refresh only.
Authors' Addresses Authors' Addresses
Bruno Decraene Bruno Decraene
Orange Orange
38 rue du General Leclerc
Issy Moulineaux cedex 9 92794
France
Email: bruno.decraene@orange.com Email: bruno.decraene@orange.com
Pierre Francois Pierre Francois
IMDEA Networks Cisco Systems, Inc.
Avda. del Mar Mediterraneo, 22
Leganese 28918
ES
Email: pierre.francois@imdea.org Email: pifranco@cisco.com
 End of changes. 14 change blocks. 
22 lines changed or deleted 22 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/