|
This document requests IANA to recategorize several entries in the Border Gateway Protocol (BGP) Extended Communities registry from "Experimental Use" to non-experimental.
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 April 21, 2011.
Copyright (c) 2010 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 described in the Simplified BSD License.
The Border Gateway Protocol (BGP) Extended Communities registry lists Extended Communities 0x8000-0x8fff as Experimental Use, in keeping with [RFC4360] (Sangli, S., Tappan, D., and Y. Rekhter, “BGP Extended Communities Attribute,” February 2006.). In practice, the use of Extended Communities 0x8006-0x8009, defined in [RFC5575] (Marques, P., Sheth, N., Raszuk, R., Greene, B., Mauch, J., and D. McPherson, “Dissemination of Flow Specification Rules,” August 2009.) and 0x800a, defined in [RFC4761] (Kompella, K. and Y. Rekhter, “Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling,” January 2007.) is not Experimental. The most straightforward solution to this problem is to recategorize those code points as Standards Action.
The other solution to this issue would be to update the relevant specifications to use code points from the currently defined Standards Action space. Given that there is deployment of the currently-allocated code points, there would be non-negligible development, testing and operational expense to migrate to new code points, without any significant benefit being derived. Given that there is no evident disadvantage to simply recategorizing the current code points, that solution is to be preferred.
Thanks to Andy Malis for his contribution.
This document requests IANA recategorize Extended Communities 0x8006-0x800a as Standards Action. It is noted that the relevant specifications are already Standards Track RFCs.
No security considerations arise from this document.
[RFC4360] | Sangli, S., Tappan, D., and Y. Rekhter, “BGP Extended Communities Attribute,” RFC 4360, February 2006 (TXT). |
[RFC4761] | Kompella, K. and Y. Rekhter, “Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling,” RFC 4761, January 2007 (TXT). |
[RFC5575] | Marques, P., Sheth, N., Raszuk, R., Greene, B., Mauch, J., and D. McPherson, “Dissemination of Flow Specification Rules,” RFC 5575, August 2009 (TXT). |
Bhupesh Kothari | |
Cisco Systems | |
3750 Cisco Way | |
San Jose, CA 95134 | |
USA | |
Email: | bhupesh@cisco.com |
Kireeti Kompella | |
Juniper Networks | |
1194 N. Mathilda Ave | |
Sunnyvale, CA 94089 | |
USA | |
Email: | kireeti@juniper.net |