draft-ietf-ospf-ospfv3-iid-registry-update-00.txt   draft-ietf-ospf-ospfv3-iid-registry-update-01.txt 
Network Working Group A. Retana Network Working Group A. Retana
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended status: Standards Track D. Cheng Intended status: Standards Track D. Cheng
Expires: April 4, 2013 Huawei Technologies Expires: July 26, 2013 Huawei Technologies
October 1, 2012 January 22, 2013
OSPFv3 Instance ID Registry Update OSPFv3 Instance ID Registry Update
draft-ietf-ospf-ospfv3-iid-registry-update-00 draft-ietf-ospf-ospfv3-iid-registry-update-01
Abstract Abstract
This document modifies the "Unassigned" number space in the IANA This document modifies the "Unassigned" number space in the IANA
"OSPFv3 Instance ID Address Family Values" registry. "OSPFv3 Instance ID Address Family Values" registry.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 32 skipping to change at page 1, line 32
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 4, 2013. This Internet-Draft will expire on July 26, 2013.
Copyright Notice 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. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . . 3 2. OSPFv3 Instance ID Address Family Values Registry Update . . . 3
3. OSPFv3 Instance ID Address Family Values Registry Update . . . 3 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 6.1. Normative References . . . . . . . . . . . . . . . . . . . 4
7.1. Normative References . . . . . . . . . . . . . . . . . . . 4 6.2. Informative References . . . . . . . . . . . . . . . . . . 4
7.2. Informative References . . . . . . . . . . . . . . . . . . 4 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . . 4
A.1. Changes between the -00 and -01 versions. . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction 1. Introduction
[RFC5838] defined the "OSPFv3 Instance ID Address Family Values" [RFC5838] defined the "OSPFv3 Instance ID Address Family Values"
registry for the purpose of mapping OSPFv3 Instance IDs to different registry for the purpose of mapping OSPFv3 Instance IDs to different
address families. The following table lists the value ranges as address families. The following table lists the value ranges as
currently allocated. currently allocated.
+---------------------------+-------------------+-------------------+ +---------------------------+-------------------+-------------------+
skipping to change at page 3, line 25 skipping to change at page 3, line 25
| Instance ID # 0 - # 31 | IPv6 unicast AF | Already Assigned | | Instance ID # 0 - # 31 | IPv6 unicast AF | Already Assigned |
| Instance ID # 32 - # 63 | IPv6 multicast AF | Already Assigned | | Instance ID # 32 - # 63 | IPv6 multicast AF | Already Assigned |
| Instance ID # 64 - # 95 | IPv4 unicast AF | Already Assigned | | Instance ID # 64 - # 95 | IPv4 unicast AF | Already Assigned |
| Instance ID # 96 - # 127 | IPv4 multicast AF | Already Assigned | | Instance ID # 96 - # 127 | IPv4 multicast AF | Already Assigned |
| Instance ID # 128 - # 255 | Unassigned | Standards Action | | Instance ID # 128 - # 255 | Unassigned | Standards Action |
+---------------------------+-------------------+-------------------+ +---------------------------+-------------------+-------------------+
In some networks additional OSPFv3 instances may be required to In some networks additional OSPFv3 instances may be required to
operationally identify specific applications. operationally identify specific applications.
2. Requirements Language 2. OSPFv3 Instance ID Address Family Values Registry Update
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 The IANA "OSPFv3 Instance ID Address Family Values" registry must be
updated as follows: updated as follows:
+---------------------------+-------------+-----------------------+ +---------------------------+-------------+-----------------------+
| Instance ID Range | Description | Assignment Policy | | Instance ID Range | Description | Assignment Policy |
+---------------------------+-------------+-----------------------+ +---------------------------+-------------+-----------------------+
| Instance ID # 128 - # 191 | Unassigned | Standards Action | | Instance ID # 128 - # 191 | Unassigned | Standards Action |
| Instance ID # 192 - # 255 | Unassigned | Private Use [RFC5226] | | Instance ID # 192 - # 255 | Unassigned | Private Use [RFC5226] |
+---------------------------+-------------+-----------------------+ +---------------------------+-------------+-----------------------+
4. IANA Considerations 3. IANA Considerations
This document requests the modification of the "OSPFv3 Instance ID This document requests the modification of the "OSPFv3 Instance ID
Address Family Values" registry as described in Section 3. Address Family Values" registry as described in Section 2.
5. Security Considerations 4. Security Considerations
This document modifies the assignment policy of an IANA registry This document modifies the assignment policy of an IANA registry
defined in [RFC5838]. It does not introduce any new security issues. defined in [RFC5838]. It does not introduce any new security issues.
6. Acknowledgements 5. Acknowledgements
Many thanks to Acee Lindem and Stewart Bryant for their input.
7. References Many thanks to Acee Lindem, Stewart Bryant and Nevil Brownlee for
their review and input.
7.1. Normative References 6. References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 6.1. Normative References
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
7.2. Informative References 6.2. Informative References
[RFC5838] Lindem, A., Mirtorabi, S., Roy, A., Barnes, M., and R. [RFC5838] Lindem, A., Mirtorabi, S., Roy, A., Barnes, M., and R.
Aggarwal, "Support of Address Families in OSPFv3", Aggarwal, "Support of Address Families in OSPFv3",
RFC 5838, April 2010. RFC 5838, April 2010.
Appendix A. Change Log
A.1. Changes between the -00 and -01 versions.
o Eliminated rfc2119 keywords, section about Requirements Language
and corrsponding reference.
o Updated acks.
Authors' Addresses Authors' Addresses
Alvaro Retana Alvaro Retana
Cisco Systems, Inc. Cisco Systems, Inc.
7025 Kit Creek Rd. 7025 Kit Creek Rd.
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
USA USA
Email: aretana@cisco.com Email: aretana@cisco.com
Dean Cheng Dean Cheng
Huawei Technologies Huawei Technologies
2330 Central Expressway 2330 Central Expressway
Santa Clara, California 95050 Santa Clara, California 95050
USA USA
Email: dean.cheng@huawei.com Email: dean.cheng@huawei.com
 End of changes. 17 change blocks. 
33 lines changed or deleted 34 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/