1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
|
<pre>Internet Engineering Task Force (IETF) S. Venaas
Request for Comments: 6166 Cisco Systems
Category: Standards Track April 2011
ISSN: 2070-1721
<span class="h1">A Registry for PIM Message Types</span>
Abstract
This document provides instructions to IANA for the creation of a
registry for PIM message types. It specifies the initial content of
the registry, based on existing RFCs specifying PIM message types.
It also specifies a procedure for registering new types.
In addition to this, one message type is reserved, and may be used
for a future extension of the message type space.
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="http://www.rfc-editor.org/info/rfc6166">http://www.rfc-editor.org/info/rfc6166</a>.
Copyright Notice
Copyright (c) 2011 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">Venaas Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6166">RFC 6166</a> A Registry for PIM Message Types April 2011</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Security Considerations .........................................<a href="#page-2">2</a>
<a href="#section-3">3</a>. IANA Considerations .............................................<a href="#page-2">2</a>
<a href="#section-3.1">3.1</a>. Initial Registry ...........................................<a href="#page-3">3</a>
<a href="#section-3.2">3.2</a>. Assignment of New Message Types ............................<a href="#page-3">3</a>
<a href="#section-4">4</a>. Acknowledgements ................................................<a href="#page-3">3</a>
<a href="#section-5">5</a>. Informative References ..........................................<a href="#page-3">3</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
Apart from this document, there is no existing document specifying a
registry for PIM message types. PIM version 1 made use of IGMP
[<a href="./rfc1112" title=""Host extensions for IP multicasting"">RFC1112</a>], and there is an IGMP registry [<a href="#ref-IGMPREG" title=""Internet Group Management Protocol (IGMP) Type Numbers - per [RFC3228], [BCP57]"">IGMPREG</a>] listing the
message types used by PIM version 1. PIM version 2, however, is not
based on IGMP, and a separate PIM message type registry is needed.
There are currently several RFCs specifying new PIM version 2 message
types that should be in this new registry. They are the RFCs for PIM
Dense Mode [<a href="./rfc3973" title=""Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised)"">RFC3973</a>], PIM Sparse Mode [<a href="./rfc4601" title=""Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)"">RFC4601</a>], and Bidirectional
PIM [<a href="./rfc5015" title=""Bidirectional Protocol Independent Multicast (BIDIR- PIM)"">RFC5015</a>].
This document specifies the initial content of the new PIM message
type registry, based on those existing RFCs. This document also
specifies a procedure for registering new PIM message types.
In addition to this, this document reserves one message type. This
type may be used for a future extension of the message type space.
The current message type space is only 4 bits, so it is not unlikely
that this will be needed. How exactly the extension should be done
is left to a future document.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Security Considerations</span>
This document only creates an IANA registry. There may be a security
benefit in a well-known place for finding information on which PIM
message types are valid and how they are used. Apart from that,
there are no security considerations.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IANA Considerations</span>
IANA has created a PIM message type registry. It has been placed in
the "Protocol Independent Multicast (PIM)" branch of the tree. Each
entry in the registry consists of a message type, a message name, and
references to the documents defining the type. The message type is a
4-bit integer with possible values from 0 to 15.
<span class="grey">Venaas Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6166">RFC 6166</a> A Registry for PIM Message Types April 2011</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Initial Registry</span>
The initial content of the registry should be as follows.
Type Name Reference
------ ---------------------------------------- -------------------
0 Hello [<a href="./rfc3973" title=""Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised)"">RFC3973</a>] [<a href="./rfc4601" title=""Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)"">RFC4601</a>]
1 Register [<a href="./rfc4601" title=""Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)"">RFC4601</a>]
2 Register Stop [<a href="./rfc4601" title=""Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)"">RFC4601</a>]
3 Join/Prune [<a href="./rfc3973" title=""Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised)"">RFC3973</a>] [<a href="./rfc4601" title=""Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)"">RFC4601</a>]
4 Bootstrap [<a href="./rfc4601" title=""Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)"">RFC4601</a>]
5 Assert [<a href="./rfc3973" title=""Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised)"">RFC3973</a>] [<a href="./rfc4601" title=""Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)"">RFC4601</a>]
6 Graft [<a href="./rfc3973" title=""Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised)"">RFC3973</a>]
7 Graft-Ack [<a href="./rfc3973" title=""Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised)"">RFC3973</a>]
8 Candidate RP Advertisement [<a href="./rfc4601" title=""Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)"">RFC4601</a>]
9 State Refresh [<a href="./rfc3973" title=""Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised)"">RFC3973</a>]
10 DF Election [<a href="./rfc5015" title=""Bidirectional Protocol Independent Multicast (BIDIR- PIM)"">RFC5015</a>]
11-14 Unassigned
15 Reserved (for extension of type space) this document
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Assignment of New Message Types</span>
Assignment of new message types is done according to the "IETF
Review" model; see [<a href="./rfc5226" title="">RFC5226</a>].
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Acknowledgements</span>
Thanks to Toerless Eckert for his suggestion to reserve a type for
future extension of the message type space. Also thanks to Mykyta
Yevstifeyev for reviewing the document and proposing improvements to
the text.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Informative References</span>
[<a id="ref-IGMPREG">IGMPREG</a>] IANA, "Internet Group Management Protocol (IGMP) Type
Numbers - per [<a href="./rfc3228">RFC3228</a>], [BCP57]", <<a href="http://www.iana.org/">http://www.iana.org/</a>>.
[<a id="ref-RFC1112">RFC1112</a>] Deering, S., "Host extensions for IP multicasting", STD 5,
<a href="./rfc1112">RFC 1112</a>, August 1989.
[<a id="ref-RFC3973">RFC3973</a>] Adams, A., Nicholas, J., and W. Siadak, "Protocol
Independent Multicast - Dense Mode (PIM-DM): Protocol
Specification (Revised)", <a href="./rfc3973">RFC 3973</a>, January 2005.
[<a id="ref-RFC4601">RFC4601</a>] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,
"Protocol Independent Multicast - Sparse Mode (PIM-SM):
Protocol Specification (Revised)", <a href="./rfc4601">RFC 4601</a>, August 2006.
<span class="grey">Venaas Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6166">RFC 6166</a> A Registry for PIM Message Types April 2011</span>
[<a id="ref-RFC5015">RFC5015</a>] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano,
"Bidirectional Protocol Independent Multicast (BIDIR-
PIM)", <a href="./rfc5015">RFC 5015</a>, October 2007.
[<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.
Author's Address
Stig Venaas
Cisco Systems
Tasman Drive
San Jose, CA 95134
USA
EMail: stig@cisco.com
Venaas Standards Track [Page 4]
</pre>
|
