Recategorization of Extended Communities 0x8006-0x800a
draft-kothari-extcomm-codepoints-02.txt

Abstract

This document requests IANA to recategorize several entries in the Border Gateway Protocol (BGP) Extended Communities registry from "Experimental Use" to non-experimental.

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 December 03, 2011.

Copyright Notice

Copyright (c) 2011 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.

1. Introduction

The Border Gateway Protocol (BGP) Extended Communities registry lists Extended Communities 0x8000-0x8fff as Experimental Use, in keeping with [RFC4360]. In practice, the use of Extended Communities 0x8006-0x8009, defined in [RFC5575] and 0x800a, defined in [RFC4761] is not Experimental. The most straightforward solution to this problem is to recategorize those code points as Standards Action.

2. Discussion

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.

3. Acknowledgements

Thanks to Andy Malis for his contribution.

4. IANA Considerations

This document requests IANA recategorize Extended Communities 0x8006-0x800a as Standards Action. It is noted that the relevant specifications are already Standards Track RFCs.

5. Security Considerations

No security considerations arise from this document.

6. References

6.1. Normative References

6.2. Informative References

Authors' Addresses

Table of Contents

• 1. Introduction
• 2. Discussion
• 3. Acknowledgements
• 4. IANA Considerations
• 5. Security Considerations
• 6. References
• 6.1. Normative References
• 6.2. Informative References
• Authors' Addresses