--- 1/draft-ietf-idr-as4octet-extcomm-generic-subtype-04.txt 2012-03-11 11:14:01.598699622 +0100 +++ 2/draft-ietf-idr-as4octet-extcomm-generic-subtype-05.txt 2012-03-11 11:14:01.610672270 +0100 @@ -1,50 +1,50 @@ Network Working Group D. Rao Internet-Draft P. Mohapatra Intended status: Standards Track Cisco Systems -Expires: January 12, 2012 J. Haas +Expires: September 12, 2012 J. Haas Juniper Networks - July 11, 2011 + March 11, 2012 Generic Subtype for BGP Four-octet AS specific extended community - draft-ietf-idr-as4octet-extcomm-generic-subtype-04.txt + draft-ietf-idr-as4octet-extcomm-generic-subtype-05.txt Abstract Maintaining the current best practices with communities, ISPs and enterprises that are assigned a 4-octet AS number may want the BGP UPDATE messages they receive from their customers or peers to include - a 4-octet AS specific extended community. This document defines a - new sub-type within the four-octet AS specific extended community to - facilitate this practice. + a 4-octet AS specific BGP extended community. This document defines + a new sub-type within the four-octet AS specific extended community + to facilitate this practice. Status of this Memo This Internet-Draft is submitted to IETF 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 January 12, 2012. + This Internet-Draft will expire on September 12, 2012. Copyright Notice - Copyright (c) 2011 IETF Trust and the persons identified as the + Copyright (c) 2012 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 @@ -52,21 +52,23 @@ Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . . 3 2. Generic Sub-type Definition . . . . . . . . . . . . . . . . . . 3 3. Deployment Considerations . . . . . . . . . . . . . . . . . . . 4 4. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 - 7. Normative References . . . . . . . . . . . . . . . . . . . . . 5 + 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 + 7.1. Normative References . . . . . . . . . . . . . . . . . . . 5 + 7.2. Informative References . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 1. Introduction Maintaining the current best practices with communities, ISPs and enterprises that are assigned a 4-octet AS number may want the BGP UPDATE messages they receive from their customers or peers to include a 4-octet AS specific extended community. This document defines a new sub-type within the four-octet AS specific extended community to facilitate this practice. @@ -176,45 +178,42 @@ Name Value ---- ----- transitive generic four-octet AS specific 0x0204 non-transitive generic four-octet AS specific 0x4204 6. Security Considerations There are no additional security risks introduced by this design. -7. Normative References +7. References + +7.1. Normative References [RFC1997] Chandrasekeran, R., Traina, P., and T. Li, "BGP Communities Attribute", RFC 1997, August 1996. - [RFC1998] Chen, E. and T. Bates, "An Application of the BGP - Community Attribute in Multi-home Routing", RFC 1998, - 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. - [RFC5668] Rekhter, Y., Sangli, S., and D. Tappan, "4-Octet AS Specific BGP Extended Community", RFC 5668, October 2009. +7.2. Informative References + + [RFC1998] Chen, E. and T. Bates, "An Application of the BGP + Community Attribute in Multi-home Routing", RFC 1998, + August 1996. + Authors' Addresses Dhananjaya Rao Cisco Systems 170 W. Tasman Drive San Jose, CA 95134 USA Email: dhrao@cisco.com