draft-ietf-ospf-ospfv3-iid-registry-update-04.txt   rfc6969.txt 
Network Working Group A. Retana Internet Engineering Task Force (IETF) A. Retana
Internet-Draft Cisco Systems, Inc. Request for Comments: 6969 Cisco Systems, Inc.
Updates: 5838 (if approved) D. Cheng Updates: 5838 D. Cheng
Intended status: Standards Track Huawei Technologies Category: Standards Track Huawei Technologies
Expires: October 28, 2013 April 26, 2013 ISSN: 2070-1721 July 2013
OSPFv3 Instance ID Registry Update OSPFv3 Instance ID Registry Update
draft-ietf-ospf-ospfv3-iid-registry-update-04
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 by dividing it in "OSPFv3 Instance ID Address Family Values" registry by dividing it in
two halves, one half Unassigned but managed via Standards Action, and two halves -- one half Unassigned but managed via Standards Action,
the other Reserved for Private Use. It updates [RFC5838]. and the other Reserved for Private Use. It updates RFC 5838.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
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 This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on October 28, 2013. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6969.
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 . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. OSPFv3 Instance ID Address Family Values Registry Update . . 3 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 . . . . . . . . . . . . . . . . . . . . . . . 3
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.1. Normative References . . . . . . . . . . . . . . . . . . 4 6.1. Normative References . . . . . . . . . . . . . . . . . . . 4
6.2. Informative References . . . . . . . . . . . . . . . . . 4 6.2. Informative References . . . . . . . . . . . . . . . . . . 4
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 4
A.1. Changes between the -00 and -01 versions. . . . . . . . . 4
A.2. Changes between the -01 and -02 versions. . . . . . . . . 4
A.3. Changes between the -02 and -03 versions. . . . . . . . . 4
A.4. Changes between the -03 and -04 versions. . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
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 that
allocated for [RFC5838]. were allocated for [RFC5838] and Unassigned.
+---------------------------+-------------------+-------------------+ +---------+---------------------------------------------+-----------+
| Instance ID Range | Description | Assignment Policy | | Value | Description | Reference |
+---------------------------+-------------------+-------------------+ +---------+---------------------------------------------+-----------+
| Instance ID # 0 - # 31 | IPv6 unicast AF | Already Assigned | | 0 | IPv6 unicast AF | [RFC5838] |
| Instance ID # 32 - # 63 | IPv6 multicast AF | Already Assigned | | 1 - 31 | Base IPv6 Unicast AF dependent on local | [RFC5838] |
| Instance ID # 64 - # 95 | IPv4 unicast AF | Already Assigned | | | policy | |
| Instance ID # 96 - # 127 | IPv4 multicast AF | Already Assigned | | 32 | Base IPv6 Multicast | [RFC5838] |
| Instance ID # 128 - # 255 | Unassigned | Standards Action | | 33-63 | IPv6 Multicast AFs dependent on local | [RFC5838] |
+---------------------------+-------------------+-------------------+ | | policy | |
| 64 | Base IPv4 Unicast AF | [RFC5838] |
| 65-95 | IPv4 Unicast AFs dependent on local policy | [RFC5838] |
| 96 | Base IPv4 Multicast | [RFC5838] |
| 97-127 | IPv4 Multicast AFs dependent on local | [RFC5838] |
| | policy | |
| 128-255 | Unassigned | [RFC5838] |
+---------+---------------------------------------------+-----------+
In some networks additional OSPFv3 instances may be required to In some networks, additional OSPFv3 instances may be required to
operationally identify specific applications. This need requires a operationally identify specific applications. This need requires a
pool of Instance IDs that the operator may locally assign for that pool of Instance IDs that the operator may locally assign for that
purpose. purpose.
For example, [I-D.ietf-ospf-ipv4-embedded-ipv6-routing] describes an For example, [OSPF-EMBED] describes an application in which IPv4-
application in which IPv4-embedded IPv6 addresses [RFC6052] are used embedded IPv6 addresses [RFC6052] are used to transport IPv4 packets
to transport IPv4 packets over an IPv6 network. While the over an IPv6 network. While the IPv4-embedded IPv6 addresses do in
IPv4-embedded IPv6 addresses do in fact represent IPv6 destinations, fact represent IPv6 destinations, it would be operationally
it would be operationally benefitial to be able to easily identify beneficial to be able to easily identify the specific application by
the the specific application by having a separate space to do so. having a separate space to do so. This benefit is enabled by the
This benefit is enabled by the allocation of a range of Private Use allocation of a range of Private Use Instance IDs.
Instance IDs.
This document updates [RFC5838] by modifying the "OSPFv3 Instance ID This document modifies the IANA "OSPFv3 Instance ID Address Family
Address Family Values" registry. If divides the original Unassinged Values" registry by designating a range as Reserved for Private Use.
space in two halves, one half Unassigned but managed via Standards For the remaining unassigned values, the registration procedure is
Action, and the other Reserved for Private Use. Standards Action.
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 has been
updated as follows: updated so that Instance IDs from 192-255 are Reserved for Private
Use [RFC5226]. For the remaining unassigned values (128-191), the
registration procedure is Standards Action. The registry now shows:
+---------------------------+-------------+-----------------------+ +--------------------------+---------------+-----------------------+
| Instance ID Range | Description | Assignment Policy | | Value | Description | Reference |
+---------------------------+-------------+-----------------------+ +--------------------------+---------------+-----------------------+
| Instance ID # 128 - # 191 | Unassigned | Standards Action | | 128-191 | Unassigned | 192-255 |
| Instance ID # 192 - # 255 | Reserved | Private Use [RFC5226] | | Reserved for Private Use | this document | Private Use [RFC5226] |
+---------------------------+-------------+-----------------------+ +--------------------------+---------------+-----------------------+
3. 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 2. The Address Family Values" registry as described in Section 2. The
reference to [RFC5838] should be removed from the registry for the reference to [RFC5838] has been 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 an IANA registry defined in [RFC5838]. It
defined in [RFC5838]. It does not introduce any new security issues. does not introduce any new security issues.
5. Acknowledgements 5. Acknowledgements
Many thanks to Acee Lindem, Stewart Bryant, Nevil Brownlee, Pearl Many thanks to Acee Lindem, Stewart Bryant, Nevil Brownlee, Pearl
Liang, Ben Campbell, Adrian Farrel and Richard Barnes for their Liang, Ben Campbell, Adrian Farrel, and Richard Barnes for their
review and input. 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
IANA Considerations Section in RFCs", BCP 26, RFC 5226, an IANA Considerations Section in RFCs", BCP 26,
May 2008. RFC 5226, May 2008.
6.2. Informative References 6.2. Informative References
[I-D.ietf-ospf-ipv4-embedded-ipv6-routing] [OSPF-EMBED] Cheng, D., Boucadair, M., and A. Retana, "Routing for
Cheng, D., Boucadair, M., and A. Retana, "Routing for IPv4-embedded IPv6 Packets", Work in Progress,
IPv4-embedded IPv6 Packets", draft-ietf-ospf-ipv4 June 2013.
-embedded-ipv6-routing-11 (work in progress), April 2013.
[RFC5838] Lindem, A., Mirtorabi, S., Roy, A., Barnes, M., and R.
Aggarwal, "Support of Address Families in OSPFv3", RFC
5838, April 2010.
[RFC6052] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X.
Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052,
October 2010.
Appendix A. Change Log
This section to be removed by the RFC Editor before publication.
A.1. Changes between the -00 and -01 versions.
o Eliminated rfc2119 keywords, section about Requirements Language
and corresponding reference.
o Updated acks.
A.2. Changes between the -01 and -02 versions.
o Added indicated that this draft updates rfc5838.
o Clarified the description of the 'Private Use' range to
'Reserved'.
o Added the need to remove the reference to rfc5838 from the updated
registry fields.
o Updated acks.
A.3. Changes between the -02 and -03 versions.
o Inserted example of the motivation.
o Updated acks.
A.4. Changes between the -03 and -04 versions.
o Added an explanation of the update to RFC5838 (Abstract and
Introduction).
o In the Introduction, clarified that the table represents the
allocation made in RFC5838.
o Added text to clarify the reason we need a Private Use space.
o Updated acks. [RFC5838] Lindem, A., Mirtorabi, S., Roy, A., Barnes, M., and R.
Aggarwal, "Support of Address Families in OSPFv3",
RFC 5838, April 2010.
o Added a reference to RFC6052. [RFC6052] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and
X. Li, "IPv6 Addressing of IPv4/IPv6 Translators",
RFC 6052, October 2010.
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. 24 change blocks. 
127 lines changed or deleted 82 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/