6969
PROPOSED STANDARD
OSPFv3 Instance ID Registry Update
Authors: A. Retana, D. Cheng
Date: July 2013
Area: rtg
Working Group: ospf
Stream: IETF
Updates:
RFC 5838
Abstract
This document modifies the "Unassigned" number space in the IANA "OSPFv3 Instance ID Address Family Values" registry by dividing it in two halves -- one half Unassigned but managed via Standards Action, and the other Reserved for Private Use. It updates RFC 5838.
RFC 6969
PROPOSED STANDARD
Errata Exist
Internet Engineering Task Force (IETF) A. Retana
Request for Comments: 6969 Cisco Systems, Inc.
Updates: <a href="./rfc5838">5838</a> D. Cheng
Category: Standards Track Huawei Technologies
ISSN: 2070-1721 July 2013
<span class="h1">OSPFv3 Instance ID Registry Update</span>
Abstract
This document modifies the "Unassigned" number space in the IANA
"OSPFv3 Instance ID Address Family Values" registry by dividing it in
two halves -- one half Unassigned but managed via Standards Action,
and the other Reserved for Private Use. It updates <a href="./rfc5838">RFC 5838</a>.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="https://www.rfc-editor.org/info/rfc6969">http://www.rfc-editor.org/info/rfc6969</a>.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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.
<span class="grey">Retana & Cheng Standards Track [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc6969">RFC 6969</a> OSPFv3 Instance ID Registry Update July 2013</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. OSPFv3 Instance ID Address Family Values Registry Update . . . <a href="#page-3">3</a>
<a href="#section-3">3</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-4">4</a>. Security Considerations . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-5">5</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-6">6</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-6.1">6.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-6.2">6.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
[<a id="ref-RFC5838">RFC5838</a>] 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 that
were allocated for [<a href="./rfc5838" title=""Support of Address Families in OSPFv3"">RFC5838</a>] and Unassigned.
+---------+---------------------------------------------+-----------+
| Value | Description | Reference |
+---------+---------------------------------------------+-----------+
| 0 | IPv6 unicast AF | [<a href="./rfc5838" title=""Support of Address Families in OSPFv3"">RFC5838</a>] |
| 1 - 31 | Base IPv6 Unicast AF dependent on local | [<a href="./rfc5838" title=""Support of Address Families in OSPFv3"">RFC5838</a>] |
| | policy | |
| 32 | Base IPv6 Multicast | [<a href="./rfc5838" title=""Support of Address Families in OSPFv3"">RFC5838</a>] |
| 33-63 | IPv6 Multicast AFs dependent on local | [<a href="./rfc5838" title=""Support of Address Families in OSPFv3"">RFC5838</a>] |
| | policy | |
| 64 | Base IPv4 Unicast AF | [<a href="./rfc5838" title=""Support of Address Families in OSPFv3"">RFC5838</a>] |
| 65-95 | IPv4 Unicast AFs dependent on local policy | [<a href="./rfc5838" title=""Support of Address Families in OSPFv3"">RFC5838</a>] |
| 96 | Base IPv4 Multicast | [<a href="./rfc5838" title=""Support of Address Families in OSPFv3"">RFC5838</a>] |
| 97-127 | IPv4 Multicast AFs dependent on local | [<a href="./rfc5838" title=""Support of Address Families in OSPFv3"">RFC5838</a>] |
| | policy | |
| 128-255 | Unassigned | [<a href="./rfc5838" title=""Support of Address Families in OSPFv3"">RFC5838</a>] |
+---------+---------------------------------------------+-----------+
In some networks, additional OSPFv3 instances may be required to
operationally identify specific applications. This need requires a
pool of Instance IDs that the operator may locally assign for that
purpose.
For example, [<a href="#ref-OSPF-EMBED" title=""Routing for IPv4-embedded IPv6 Packets"">OSPF-EMBED</a>] describes an application in which IPv4-
embedded IPv6 addresses [<a href="./rfc6052" title=""IPv6 Addressing of IPv4/IPv6 Translators"">RFC6052</a>] 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
beneficial to be able to easily identify the specific application by
having a separate space to do so. This benefit is enabled by the
allocation of a range of Private Use Instance IDs.
<span class="grey">Retana & Cheng Standards Track [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc6969">RFC 6969</a> OSPFv3 Instance ID Registry Update July 2013</span>
This document modifies the IANA "OSPFv3 Instance ID Address Family
Values" registry by designating a range as Reserved for Private Use.
For the remaining unassigned values, the registration procedure is
Standards Action.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. OSPFv3 Instance ID Address Family Values Registry Update</span>
The IANA "OSPFv3 Instance ID Address Family Values" registry has been
updated so that Instance IDs from 192-255 are Reserved for Private
Use [<a href="./rfc5226" title="">RFC5226</a>]. For the remaining unassigned values (128-191), the
registration procedure is Standards Action. The registry now shows:
+--------------------------+---------------+-----------------------+
| Value | Description | Reference |
+--------------------------+---------------+-----------------------+
| 128-191 | Unassigned | 192-255 |
| Reserved for Private Use | this document | Private Use [<a href="./rfc5226" title="">RFC5226</a>] |
+--------------------------+---------------+-----------------------+
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IANA Considerations</span>
This document requests the modification of the "OSPFv3 Instance ID
Address Family Values" registry as described in <a href="#section-2">Section 2</a>. The
reference to [<a href="./rfc5838" title=""Support of Address Families in OSPFv3"">RFC5838</a>] has been removed from the registry for the
modified ranges.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
This document modifies an IANA registry defined in [<a href="./rfc5838" title=""Support of Address Families in OSPFv3"">RFC5838</a>]. It
does not introduce any new security issues.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgements</span>
Many thanks to Acee Lindem, Stewart Bryant, Nevil Brownlee, Pearl
Liang, Ben Campbell, Adrian Farrel, and Richard Barnes for their
review and input.
<span class="grey">Retana & Cheng Standards Track [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc6969">RFC 6969</a> OSPFv3 Instance ID Registry Update July 2013</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing
an IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>,
<a href="./rfc5226">RFC 5226</a>, May 2008.
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
[<a id="ref-OSPF-EMBED">OSPF-EMBED</a>] Cheng, D., Boucadair, M., and A. Retana, "Routing for
IPv4-embedded IPv6 Packets", Work in Progress,
June 2013.
[<a id="ref-RFC5838">RFC5838</a>] Lindem, A., Mirtorabi, S., Roy, A., Barnes, M., and R.
Aggarwal, "Support of Address Families in OSPFv3",
<a href="./rfc5838">RFC 5838</a>, April 2010.
[<a id="ref-RFC6052">RFC6052</a>] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and
X. Li, "IPv6 Addressing of IPv4/IPv6 Translators",
<a href="./rfc6052">RFC 6052</a>, October 2010.
Authors' Addresses
Alvaro Retana
Cisco Systems, Inc.
7025 Kit Creek Rd.
Research Triangle Park, NC 27709
USA
EMail: [email protected]
Dean Cheng
Huawei Technologies
2330 Central Expressway
Santa Clara, California 95050
USA
EMail: [email protected]
Retana & Cheng Standards Track [Page 4]
Annotations
Select text to annotate