draft-ietf-ospf-ospfv3-iid-registry-update-02.txt   draft-ietf-ospf-ospfv3-iid-registry-update-03.txt 
Network Working Group A. Retana Network Working Group A. Retana
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Updates: 5838 (if approved) D. Cheng Updates: 5838 (if approved) D. Cheng
Intended status: Standards Track Huawei Technologies Intended status: Standards Track Huawei Technologies
Expires: August 15, 2013 February 11, 2013 Expires: October 19, 2013 April 17, 2013
OSPFv3 Instance ID Registry Update OSPFv3 Instance ID Registry Update
draft-ietf-ospf-ospfv3-iid-registry-update-02 draft-ietf-ospf-ospfv3-iid-registry-update-03
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.
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 August 15, 2013. This Internet-Draft will expire on October 19, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 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 . . . . . . . . . . . . . . . . . . . . . . . . 2
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. OSPFv3 Instance ID Address Family Values Registry Update . . 2
2. OSPFv3 Instance ID Address Family Values Registry Update . . . 3 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 3
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 6.1. Normative References . . . . . . . . . . . . . . . . . . 3
6.1. Normative References . . . . . . . . . . . . . . . . . . . 4 6.2. Informative References . . . . . . . . . . . . . . . . . 3
6.2. Informative References . . . . . . . . . . . . . . . . . . 4 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 3
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . . 4 A.1. Changes between the -00 and -01 versions. . . . . . . . . 3
A.1. Changes between the -00 and -01 versions. . . . . . . . . . 4 A.2. Changes between the -01 and -02 versions. . . . . . . . . 4
A.2. Changes between the -01 and -02 versions. . . . . . . . . . 4 A.3. Changes between the -02 and -03 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.
+---------------------------+-------------------+-------------------+ +---------------------------+-------------------+-------------------+
| Instance ID Range | Description | Assignment Policy | | Instance ID Range | Description | Assignment Policy |
+---------------------------+-------------------+-------------------+ +---------------------------+-------------------+-------------------+
| 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. For example,
[I-D.ietf-ospf-ipv4-embedded-ipv6-routing] describes an application
in which IPv4-embedded IPv6 addresses are used to transport IPv4
packets over an IPv6 network. While the IPv4-embedded IPv6 addresses
do in fact represent IPv6 destinations, it would be operationally
benefitial to be able to easily identify the the specific application
by having a separate space to do so.
2. OSPFv3 Instance ID Address Family Values Registry Update 2. 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 |
skipping to change at page 4, line 7 skipping to change at page 3, line 26
reference to [RFC5838] should be removed from the registry for the reference to [RFC5838] should be removed from the registry for the
modified ranges. modified ranges.
4. 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.
5. Acknowledgements 5. Acknowledgements
Many thanks to Acee Lindem, Stewart Bryant, Nevil Brownlee and Pearl Many thanks to Acee Lindem, Stewart Bryant, Nevil Brownlee, Pearl
Liang for their review and input. Liang and Ben Campbell for their review and input.
6. References 6. References
6.1. Normative References 6.1. Normative References
[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.
6.2. Informative References 6.2. Informative References
[I-D.ietf-ospf-ipv4-embedded-ipv6-routing]
Cheng, D., Boucadair, M., and A. Retana, "Routing for
IPv4-embedded IPv6 Packets", draft-ietf-ospf-ipv4
-embedded-ipv6-routing-10 (work in progress), April 2013.
[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
RFC 5838, April 2010. 5838, April 2010.
Appendix A. Change Log Appendix A. Change Log
A.1. Changes between the -00 and -01 versions. A.1. Changes between the -00 and -01 versions.
o Eliminated rfc2119 keywords, section about Requirements Language o Eliminated rfc2119 keywords, section about Requirements Language
and corresponding reference. and corresponding reference.
o Updated acks. o Updated acks.
skipping to change at page 5, line 5 skipping to change at page 4, line 22
o Added indicated that this draft updates rfc5838. o Added indicated that this draft updates rfc5838.
o Clarified the description of the 'Private Use' range to o Clarified the description of the 'Private Use' range to
'Reserved'. 'Reserved'.
o Added the need to remove the reference to rfc5838 from the updated o Added the need to remove the reference to rfc5838 from the updated
registry fields. registry fields.
o Updated acks. o Updated acks.
A.3. Changes between the -02 and -03 versions.
o Inserted example of the motivation.
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
 End of changes. 10 change blocks. 
22 lines changed or deleted 39 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/