--- 1/draft-ietf-idr-reserved-extended-communities-04.txt 2013-05-21 10:14:18.905709129 +0100 +++ 2/draft-ietf-idr-reserved-extended-communities-05.txt 2013-05-21 10:14:18.921709530 +0100 @@ -1,58 +1,57 @@ Network Working Group B. Decraene Internet-Draft France Telecom - Orange Intended status: Standards Track P. Francois -Expires: May 23, 2013 IMDEA Networks - November 19, 2012 +Expires: November 22, 2013 IMDEA Networks + May 21, 2013 Assigned BGP extended communities - draft-ietf-idr-reserved-extended-communities-04 + draft-ietf-idr-reserved-extended-communities-05 Abstract This document defines an IANA registry in order to assign non- transitive extended communities from. These are similar to the existing well-known BGP communities defined in RFC 1997 but provide a control over inter-AS community advertisement as, per RFC RFC 4360, they are not transitive across Autonomous System boundaries. For that purpose, this document defines the use of the reserved Autonomous System number 0.65535 in the non-transitive generic four- octet AS specific extended community type. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. -Status of this Memo +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 May 23, 2013. + This Internet-Draft will expire on November 22, 2013. Copyright Notice - - Copyright (c) 2012 IETF Trust and the persons identified as the + Copyright (c) 2013 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 carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as @@ -124,21 +123,21 @@ significance. The lists of those communities are maintained by the IANA in the registry "Assigned non-transitive extended communities". Note that this use of the reserved AS number 0.65535 in the AS field of the communities is similar to the one defined by [RFC1997] for the BGP Well-Known communities. In particular, [RFC1997] also uses the reserved AS number 65535. 3. Assigned transitive extended communities - As per [RFC4893], a 2-octet Autonomous System number can be converted + As per [RFC6793], a 2-octet Autonomous System number can be converted into a 4-octet Autonomous System number by setting the two high-order octets of the 4-octet field to zero. This applies to the reserved 2-octet Autonous System number 65535 which could use either a standard community or the 4-octet AS specific generic extended community. As noted in [I-D.ietf-idr-as4octet-extcomm-generic-subtype], this is undesirable as they would be treated as different communities, even if they had the same values. Therefore, this document does not define a non-transitive extended @@ -180,63 +179,66 @@ 6. Acknowledgements We would like to acknowledge John Scudder and Jeffrey Haas for their contribution to this document. 7. Normative References [I-D.ietf-idr-as4octet-extcomm-generic-subtype] Rao, D., Mohapatra, P., and J. Haas, "Generic Subtype for - BGP Four-octet AS specific extended community", - draft-ietf-idr-as4octet-extcomm-generic-subtype-06 (work - in progress), October 2012. + BGP Four-octet AS specific extended community", draft- + ietf-idr-as4octet-extcomm-generic-subtype-06 (work in + progress), October 2012. [RFC1997] Chandrasekeran, R., Traina, P., and T. Li, "BGP Communities Attribute", RFC 1997, August 1996. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended Communities Attribute", RFC 4360, February 2006. - [RFC4893] Vohra, Q. and E. Chen, "BGP Support for Four-octet AS - Number Space", RFC 4893, May 2007. - [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008. + [RFC6793] Vohra, Q. and E. Chen, "BGP Support for Four-Octet + Autonomous System (AS) Number Space", RFC 6793, December + 2012. + Appendix A. Appendix A. Changes / Author Notes [RFC Editor: Please remove this section before publication ] - Changes -01 + Changes -01: o Name changed from 'Reserved BGP extended communities' to 'Assigned BGP extended communities' o Addition of section 'Assigned extended communities' Changes -02: no change, refresh only. - Changes -03 + Changes -03: o Use of AS number 0.65535 (0x0000FFFF) instead of AS 0. This is better aligned with RFC 1997 which also uses AS 65535. o Remove the transitive flavor of assigned extended communities. RFC 1997 well-known standard communities to be used instead. Changes -04: no change, refresh only. + Changes -05: minor editorial change (RFC 4893 obsoleted by 6793). + Authors' Addresses Bruno Decraene France Telecom - Orange 38 rue du General Leclerc Issy Moulineaux cedex 9 92794 France Email: bruno.decraene@orange.com