RFC 6166
A Registry for PIM Message Types
RFC 6166: A Registry for PIM Message Types 🦋
bestie, here's the deets 💖
- Number: RFC 6166
- Title: A Registry for PIM Message Types
- Author: S. Venaas, Cisco Systems 💅
- Category: Standards Track ✨
- Date: April 2011 🌸
- ISSN: 2070-1721
- Obsoletes / Updates: neither is listed, so it doesn't replace or change any older RFC 🫶
Abstract ✨
okay so this doc tells IANA how to set up a registry for PIM message types 📋 It lists the starting entries, which come from the RFCs that already define PIM message types, and it explains how to add new ones later 🧚
there's also one message type that's reserved 🔒 It's saved for a future extension of the message type space, so it's basically a spot held open for later 💜
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 Section 2 of RFC 5741.
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/rfc6166.
Copyright Notice 💜
Copyright (c) 2011 IETF Trust and the persons identified 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) 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.
Table of Contents 📑
1. Introduction ....................................................2
2. Security Considerations .........................................2
3. IANA Considerations .............................................2
3.1. Initial Registry ...........................................3
3.2. Assignment of New Message Types ............................3
4. Acknowledgements ................................................3
5. Informative References ..........................................31. Introduction 🎀
okay so, before this doc, there was no existing spec for a PIM message type registry 🙈 PIM version 1 used IGMP [RFC1112], and there's an IGMP registry [IGMPREG] that lists the message types PIM version 1 uses.
PIM version 2 is not built on IGMP, though, so it needs its own registry 💅 A few RFCs already define new PIM version 2 message types that should go into it: PIM Dense Mode [RFC3973], PIM Sparse Mode [RFC4601], and Bidirectional PIM [RFC5015].
This doc sets up the starting content of the new PIM message type registry based on those RFCs, and it also explains how to register new PIM message types 🦋
one message type gets reserved here too 🔒 It's for a future extension of the message type space. The current space is only 4 bits, so it's not unlikely that this will be needed, lowkey. How exactly that extension happens gets left to a future document 🧚
2. Security Considerations 🔐
this doc only creates an IANA registry. There may be a security benefit to having a well-known place to find out which PIM message types are valid and how they're used 👑 Apart from that, there are no security considerations.
3. IANA Considerations 📋
IANA has created a PIM message type registry, and it's been placed in the "Protocol Independent Multicast (PIM)" branch of the tree 🌳 Each entry has a message type, a message name, and references to the documents that define the type. The message type is a 4-bit integer with possible values from 0 to 15 ✨
3.1. Initial Registry 🍓
the initial content of the registry should be as follows:
Type Name Reference
------ ---------------------------------------- -------------------
0 Hello [RFC3973] [RFC4601]
1 Register [RFC4601]
2 Register Stop [RFC4601]
3 Join/Prune [RFC3973] [RFC4601]
4 Bootstrap [RFC4601]
5 Assert [RFC3973] [RFC4601]
6 Graft [RFC3973]
7 Graft-Ack [RFC3973]
8 Candidate RP Advertisement [RFC4601]
9 State Refresh [RFC3973]
10 DF Election [RFC5015]
11-14 Unassigned
15 Reserved (for extension of type space) this document3.2. Assignment of New Message Types 🧚
new message types are assigned using the "IETF Review" model. See [RFC5226] for the details 💅
4. Acknowledgements 🫶
big thank you to Toerless Eckert for suggesting we reserve a type for future extensions of the message type space ✨ Also huge thanks to Mykyta Yevstifeyev for reviewing the document and suggesting improvements to the text 💖
5. Informative References 📚
[IGMPREG] IANA, "Internet Group Management Protocol (IGMP) Type
Numbers - per [RFC3228], [BCP57]", <http://www.iana.org/>.
[RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5,
RFC 1112, August 1989.
[RFC3973] Adams, A., Nicholas, J., and W. Siadak, "Protocol
Independent Multicast - Dense Mode (PIM-DM): Protocol
Specification (Revised)", RFC 3973, January 2005.
[RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,
"Protocol Independent Multicast - Sparse Mode (PIM-SM):
Protocol Specification (Revised)", RFC 4601, August 2006.
[RFC5015] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano,
"Bidirectional Protocol Independent Multicast (BIDIR-
PIM)", RFC 5015, October 2007.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.Author's Address 🎀
Stig Venaas
Cisco Systems
Tasman Drive
San Jose, CA 95134
USA
EMail: stig@cisco.com📦 where this page comes from
- ietf: rfc6166 2011-04
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms