RFC 6969

OSPFv3 Instance ID Registry Update

📅 published July 2013, from ietf

RFC 6969: OSPFv3 Instance ID Registry Update 🎀

okay bestie, so this is RFC 6969 📜✨. It's a Standards Track doc from July 2013, written by Alvaro Retana (Cisco Systems, Inc.) and Dean Cheng (Huawei Technologies). It's ISSN 2070-1721, and it updates RFC 5838. It doesn't obsolete anything 💅

The IETF put it out, so it's a real protocol-level standard, not just vibes 🌈

Abstract

this doc glow-ups the "Unassigned" number space in the IANA "OSPFv3 Instance ID Address Family Values" registry 🦋 It splits that space into two halves: one half stays Unassigned but is managed through Standards Action, and the other half becomes Reserved for Private Use 🔒 It updates RFC 5838.

Status of This Memo

ngl this part is kinda formal but important 🫶 This is an Internet Standards Track document.

It's a product of the Internet Engineering Task Force (IETF), it represents the consensus of the IETF community, it got public review, and the Internet Engineering Steering Group (IESG) approved it for publication 🎉 More info on Internet Standards is in Section 2 of RFC 5741.

For the current status, any errata, and how to send feedback, check http://www.rfc-editor.org/info/rfc6969 💜

Copyright (c) 2013 IETF Trust and the people listed 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) as they stood on the publication date. Read those carefully, because they spell out your rights and restrictions for this doc. If you pull Code Components out of this document, they have to include the Simplified BSD License text, as described in Section 4.e of the Trust Legal Provisions. They come with no warranty, per the Simplified BSD License 🙈

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 2
   2.  OSPFv3 Instance ID Address Family Values Registry Update  . . . 3
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 3
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 3
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . . . 4
     6.2.  Informative References  . . . . . . . . . . . . . . . . . . 4

1. Introduction 🧚

okay so [RFC5838] is the one that made the "OSPFv3 Instance ID Address Family Values" registry, and its whole job is mapping OSPFv3 Instance IDs to different address families 🍓 Here's the table of the value ranges that got allocated for [RFC5838] and what's still Unassigned:

+---------+---------------------------------------------+-----------+
| Value   | Description                                 | Reference |
+---------+---------------------------------------------+-----------+
| 0       | IPv6 unicast AF                             | [RFC5838] |
| 1 - 31  | Base IPv6 Unicast AF dependent on local     | [RFC5838] |
|         | policy                                      |           |
| 32      | Base IPv6 Multicast                         | [RFC5838] |
| 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, operators need extra OSPFv3 instances to figure out which specific applications are running 🔍 That means they need a pool of Instance IDs they can assign locally for that exact purpose 💅

For example, [OSPF-EMBED] covers an app where IPv4-embedded IPv6 addresses [RFC6052] carry IPv4 packets across an IPv6 network 🌈 Those addresses really are IPv6 destinations, but it'd be super helpful to tell this specific app apart by giving it its own space. Allocating a range of Private Use Instance IDs makes that possible ✨

This doc changes the IANA "OSPFv3 Instance ID Address Family Values" registry by marking a range as Reserved for Private Use. For the rest of the unassigned values, the registration procedure is Standards Action 🫶

2. OSPFv3 Instance ID Address Family Values Registry Update 👑

the registry has been updated so 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 looks like this:

+--------------------------+---------------+-----------------------+
| Value                    | Description   | Reference             |
+--------------------------+---------------+-----------------------+
| 128-191                  | Unassigned    | 192-255               |
| Reserved for Private Use | this document | Private Use [RFC5226] |
+--------------------------+---------------+-----------------------+

3. IANA Considerations 📋

This doc asks IANA to modify the "OSPFv3 Instance ID Address Family Values" registry as described in Section 2 🎀 The reference to [RFC5838] has been removed from the registry for the modified ranges.

4. Security Considerations 🔐

⚠️ okay bestie, I'm taking this one seriously.

This doc modifies an IANA registry defined in [RFC5838]. It does not introduce any new security issues 🛡️

5. Acknowledgements 🫶

Huge thanks to Acee Lindem, Stewart Bryant, Nevil Brownlee, Pearl Liang, Ben Campbell, Adrian Farrel, and Richard Barnes for reviewing and giving input 💖 you all are iconic 👑

6. References 📚

6.1. Normative References

[RFC5226] is the one you need for the rules:

   [RFC5226]     Narten, T. and H. Alvestrand, "Guidelines for Writing
                 an IANA Considerations Section in RFCs", BCP 26,
                 RFC 5226, May 2008.

6.2. Informative References

   [OSPF-EMBED]  Cheng, D., Boucadair, M., and A. Retana, "Routing for
                 IPv4-embedded IPv6 Packets", Work in Progress,
                 June 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.

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

that's the whole tea ☕💜 periodt 💅

📦 where this page comes from