Internet DRAFT - draft-retana-ospf-ospfv3-iid-registry-update
draft-retana-ospf-ospfv3-iid-registry-update
Network Working Group A. Retana
Internet-Draft Cisco Systems, Inc.
Intended status: Standards Track D. Cheng
Expires: March 30, 2013 Huawei Technologies
September 26, 2012
OSPFv3 Instance ID Registry Update
draft-retana-ospf-ospfv3-iid-registry-update-00
Abstract
This document modifies the "Unassigned" number space in the IANA
"OSPFv3 Instance ID Address Family Values" registry.
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 March 30, 2013.
Copyright Notice
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
described in the Simplified BSD License.
Retana & Cheng Expires March 30, 2013 [Page 1]
Internet-Draft OSPFv3 Instance ID Registry Update September 2012
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . . 3
3. OSPFv3 Instance ID Address Family Values Registry Update . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4
7.1. Normative References . . . . . . . . . . . . . . . . . . . 4
7.2. Informative References . . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4
Retana & Cheng Expires March 30, 2013 [Page 2]
Internet-Draft OSPFv3 Instance ID Registry Update September 2012
1. Introduction
[RFC5838] defined the "OSPFv3 Instance ID Address Family Values"
registry for the purpose of mapping OSPFv3 Instance IDs to different
address families. The following table lists the value ranges as
currently allocated.
+---------------------------+-------------------+-------------------+
| Instance ID Range | Description | Assignment Policy |
+---------------------------+-------------------+-------------------+
| Instance ID # 0 - # 31 | IPv6 unicast AF | Already Assigned |
| Instance ID # 32 - # 63 | IPv6 multicast AF | Already Assigned |
| Instance ID # 64 - # 95 | IPv4 unicast AF | Already Assigned |
| Instance ID # 96 - # 127 | IPv4 multicast AF | Already Assigned |
| Instance ID # 128 - # 255 | Unassigned | Standards Action |
+---------------------------+-------------------+-------------------+
In some networks additional OSPFv3 instances may be required to
operationally identify specific applications.
2. 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 [RFC2119].
3. OSPFv3 Instance ID Address Family Values Registry Update
The IANA "OSPFv3 Instance ID Address Family Values" registry MUST be
updated as follows:
+---------------------------+-------------+-----------------------+
| Instance ID Range | Description | Assignment Policy |
+---------------------------+-------------+-----------------------+
| Instance ID # 128 - # 191 | Unassigned | Standards Action |
| Instance ID # 192 - # 255 | Unassigned | Private Use [RFC5226] |
+---------------------------+-------------+-----------------------+
4. IANA Considerations
This document requests the modification of the "OSPFv3 Instance ID
Address Family Values" registry as described in Section 3.
Retana & Cheng Expires March 30, 2013 [Page 3]
Internet-Draft OSPFv3 Instance ID Registry Update September 2012
5. Security Considerations
This document modifies the assignment policy of an IANA registry
defined in [RFC5838]. It does not introduce any new security issues.
6. Acknowledgements
Many thanks to Acee Lindem and Stewart Bryant for their input.
7. References
7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
7.2. Informative References
[RFC5838] Lindem, A., Mirtorabi, S., Roy, A., Barnes, M., and R.
Aggarwal, "Support of Address Families in OSPFv3",
RFC 5838, April 2010.
Authors' Addresses
Alvaro Retana
Cisco Systems, Inc.
7025 Kit Creek Rd.
Research Triangle Park, NC 27709
USA
Email: aretana@cisco.com
Dean Cheng
Huawei Technologies
2330 Central Expressway
Santa Clara, California 95050
USA
Email: dean.cheng@huawei.com
Retana & Cheng Expires March 30, 2013 [Page 4]
