Debian Codegraph @

rfc7887.html

raw
1 <pre>Internet Engineering Task Force (IETF) S. Venaas
2 Request for Comments: 7887 J. Arango
3 Updates: <a href="./rfc5384">5384</a> Cisco Systems
4 Category: Standards Track I. Kouvelas
5 ISSN: 2070-1721 Arista Networks
6 June 2016
7
8
9 <span class="h1">Hierarchical Join/Prune Attributes</span>
10
11 Abstract
12
13 This document defines a hierarchical method of encoding Join/Prune
14 attributes that provides a more efficient encoding when the same
15 attribute values need to be specified for multiple sources in a PIM
16 Join/Prune message. This document updates <a href="./rfc5384">RFC 5384</a> by renaming the
17 encoding type registry specified there.
18
19 Status of This Memo
20
21 This is an Internet Standards Track document.
22
23 This document is a product of the Internet Engineering Task Force
24 (IETF). It represents the consensus of the IETF community. It has
25 received public review and has been approved for publication by the
26 Internet Engineering Steering Group (IESG). Further information on
27 Internet Standards is available in <a href="./rfc7841#section-2">Section&nbsp;2 of RFC 7841</a>.
28
29 Information about the current status of this document, any errata,
30 and how to provide feedback on it may be obtained at
31 <a href="http://www.rfc-editor.org/info/rfc7887">http://www.rfc-editor.org/info/rfc7887</a>.
32
33 Copyright Notice
34
35 Copyright (c) 2016 IETF Trust and the persons identified as the
36 document authors. All rights reserved.
37
38 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
39 Provisions Relating to IETF Documents
40 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
41 publication of this document. Please review these documents
42 carefully, as they describe your rights and restrictions with respect
43 to this document. Code Components extracted from this document must
44 include Simplified BSD License text as described in Section 4.e of
45 the Trust Legal Provisions and are provided without warranty as
46 described in the Simplified BSD License.
47
48
49
50
51
52 <span class="grey">Venaas, et al. Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc7887">RFC 7887</a> Hierarchical Join/Prune Attributes June 2016</span>
55
56
57 Table of Contents
58
59 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
60 <a href="#section-2">2</a>. Requirements Notation . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
61 <a href="#section-3">3</a>. Hierarchical Join/Prune Attribute Definition . . . . . . . . <a href="#page-3">3</a>
62 <a href="#section-4">4</a>. PIM Address Encoding Types . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
63 <a href="#section-5">5</a>. Hierarchical Join/Prune Attribute Hello Option . . . . . . . <a href="#page-6">6</a>
64 <a href="#section-6">6</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
65 <a href="#section-7">7</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
66 <a href="#section-8">8</a>. Normative References . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
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 <span class="grey">Venaas, et al. Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc7887">RFC 7887</a> Hierarchical Join/Prune Attributes June 2016</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
114
115 PIM Join attributes as defined in [<a href="./rfc5384" title="&quot;The Protocol Independent Multicast (PIM) Join Attribute Format&quot;">RFC5384</a>] allow for specifying a
116 set of attributes for each of the joined or pruned sources in a PIM
117 Join/Prune message. Attributes must be separately specified for each
118 individual source in the message. However, in some cases, the same
119 attributes and values need to be specified for some, or even all, the
120 sources in the message. The attributes and their values then need to
121 be repeated for each of the sources where they apply.
122
123 This document provides a hierarchical way of encoding attributes and
124 their values in a Join/Prune message so that if the same attribute
125 and value is to apply for all the sources, it only needs to be
126 specified once in the message. Similarly, if all the sources in a
127 specific group set share a specific attribute and value, it only
128 needs to be specified once for the entire group set.
129
130 This document extends [<a href="./rfc5384" title="&quot;The Protocol Independent Multicast (PIM) Join Attribute Format&quot;">RFC5384</a>] by specifying that the encoding type
131 defined there also applies to Encoded-Unicast and Encoded-Group
132 formats. This document also updates [<a href="./rfc5384" title="&quot;The Protocol Independent Multicast (PIM) Join Attribute Format&quot;">RFC5384</a>] by renaming the "PIM
133 Encoded-Source Address Encoding Type Field" registry to "PIM Address
134 Encoding Types". The content of the registry remains the same. The
135 encoding type used for Join attributes is, however, still limited to
136 use in Join/Prune messages. Note that Join attributes, as they are
137 referred to in [<a href="./rfc5384" title="&quot;The Protocol Independent Multicast (PIM) Join Attribute Format&quot;">RFC5384</a>], also apply to pruned sources in a Join/
138 Prune message. Thus, the more correct name "Join/Prune attributes"
139 will be used throughout the rest of this document.
140
141 This document allows Join/Prune attributes to be specified in the
142 Upstream Neighbor Address field, and also in the Multicast Group
143 Address field, of a Join/Prune message. It defines how this is used
144 to specify the same Join/Prune attribute and value for multiple
145 sources. This document also defines a new Hello Option to indicate
146 support for the hierarchical encoding specified.
147
148 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Requirements Notation</span>
149
150 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
151 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
152 document are to be interpreted as described in [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
153
154 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Hierarchical Join/Prune Attribute Definition</span>
155
156 The format of a PIM Join/Prune message is defined in [<a href="./rfc7761" title="&quot;Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)&quot;">RFC7761</a>] as
157 follows:
158
159
160
161
162
163
164 <span class="grey">Venaas, et al. Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc7887">RFC 7887</a> Hierarchical Join/Prune Attributes June 2016</span>
167
168
169 0 1 2 3
170 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
171 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
172 |PIM Ver| Type | Reserved | Checksum |
173 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
174 | Upstream Neighbor Address (Encoded-Unicast format) |
175 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
176 | Reserved | Num groups | Holdtime |
177 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
178 | Multicast Group Address 1 (Encoded-Group format) |
179 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
180 | Number of Joined Sources | Number of Pruned Sources |
181 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
182 | Joined Source Address 1 (Encoded-Source format) |
183 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
184 | . |
185 | . |
186 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
187 | Joined Source Address n (Encoded-Source format) |
188 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
189 | Pruned Source Address 1 (Encoded-Source format) |
190 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
191 | . |
192 | . |
193 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
194 | Pruned Source Address n (Encoded-Source format) |
195 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
196 | . |
197 | . |
198 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
199 | Multicast Group Address m (Encoded-Group format) |
200 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
201 | Number of Joined Sources | Number of Pruned Sources |
202 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
203 | Joined Source Address 1 (Encoded-Source format) |
204 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
205 | . |
206 | . |
207 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
208 | Joined Source Address n (Encoded-Source format) |
209 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
210 | Pruned Source Address 1 (Encoded-Source format) |
211 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
212 | . |
213 | . |
214 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
215 | Pruned Source Address n (Encoded-Source format) |
216 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
217
218
219
220 <span class="grey">Venaas, et al. Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc7887">RFC 7887</a> Hierarchical Join/Prune Attributes June 2016</span>
223
224
225 The message contains a single Upstream Neighbor Address and one or
226 more group sets. Each group set contains a Group Address and two
227 source lists: the Joined Sources and the Pruned Sources. The
228 Upstream Neighbor Address, the group addresses, and the source
229 addresses are encoded in Encoded-Unicast format, Encoded-Group
230 format, and Encoded-Source format, respectively. This document
231 extends the use of the source address encoding defined in [<a href="./rfc5384" title="&quot;The Protocol Independent Multicast (PIM) Join Attribute Format&quot;">RFC5384</a>]
232 to also apply to the Upstream Neighbor Address and the Group Address
233 fields (see <a href="#section-4">Section 4</a>).
234
235 For a Join/Prune message, a hierarchy of Join/Prune attributes is
236 defined. Attributes at the highest level, which is the least
237 specific, apply to every source in the message. These are encoded in
238 the Upstream Neighbor Address. Attributes at the next, more-specific
239 level apply to every source in a group set. They are encoded in a
240 Group Address. And finally, there are attributes that apply to a
241 single source and are encoded in the source address as defined in
242 [<a href="./rfc5384" title="&quot;The Protocol Independent Multicast (PIM) Join Attribute Format&quot;">RFC5384</a>].
243
244 The complete set of attributes that apply to a given source is
245 obtained by combining the message-wide attributes, the attributes of
246 the group set that the source belongs to, and the source-specific
247 attributes. However, if the same attribute is specified at multiple
248 levels, then the one at the most specific level overrides the other
249 instances of the attribute. Note that the set of attributes and
250 their values is formed before processing the attributes. Hence, a
251 value that is invalid for a given type might override a valid value
252 at a higher level.
253
254 As an example, say that for a given source, we have attributes T_1
255 with value V_1, T_2 with value V_2, and T_3 with value V_3. Also
256 assume that in the Group Address of the source's group set, we have
257 attributes T_1 with value V_6 and T_4 with value V_4. And assume
258 that we in the Upstream Neighbor Address have encoded the attributes
259 T_1 with value V_7, T_4 with value V_8, and T_5 with value V_5. The
260 attributes applied to the given source will be T_1 with value V_1,
261 T_2 with value V_2, T_3 with value V_3, T_4 with value V_4, and T_5
262 with value V_5. Here we have T_1 with different values at each
263 level, so we use the value specified at the source level. Also, we
264 have T_4 with different values at the group and message levels, so we
265 use the value at the group level. Here it could be that V_1 is not a
266 valid value for T_1, but it still overrides the values at the higher
267 levels as we do not process the attributes until after forming the
268 set.
269
270 Note that Join/Prune attributes are still applied to sources as
271 specified in [<a href="./rfc5384" title="&quot;The Protocol Independent Multicast (PIM) Join Attribute Format&quot;">RFC5384</a>]. This document does not change the meaning of
272 any attributes; it is simply a more compact way of encoding an
273
274
275
276 <span class="grey">Venaas, et al. Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc7887">RFC 7887</a> Hierarchical Join/Prune Attributes June 2016</span>
279
280
281 attribute when the same attribute and value applies to multiple
282 sources, e.g., with the example above, we would have the exact same
283 meaning if we instead had encoded all the attributes T1, ..., T5 with
284 the respective values V1, ..., V5 in the source address.
285
286 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. PIM Address Encoding Types</span>
287
288 Addresses in PIM messages are specified together with an address
289 family and an encoding type. This applies to Encoded-Unicast,
290 Encoded-Group, and Encoded-Source addresses. The encoding types
291 allow the address to be encoded according to different schemes. An
292 encoding type indicates how an address is encoded irrespective of
293 address type, Encoded-Unicast, Encoded-Group, or Encoded-Source. It
294 is possible that there will be future encoding types that do not
295 apply to all address types though. This means that as currently
296 defined, 0 is native encoding [<a href="./rfc7761" title="&quot;Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)&quot;">RFC7761</a>], and 1 is Join/Prune
297 attributes encoding [<a href="./rfc5384" title="&quot;The Protocol Independent Multicast (PIM) Join Attribute Format&quot;">RFC5384</a>]. Note that as specified in [<a href="./rfc5384" title="&quot;The Protocol Independent Multicast (PIM) Join Attribute Format&quot;">RFC5384</a>],
298 a type 1 Encoded Address MUST contain at least one Join/Prune
299 attribute.
300
301 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Hierarchical Join/Prune Attribute Hello Option</span>
302
303 A PIM router indicates that it supports the mechanism specified in
304 this document by including the Hierarchical Join/Prune Attribute
305 Hello Option in its PIM Hello message. When this new Hello Option is
306 included, it MUST also include the Join Attribute Hello Option as
307 specified in [<a href="./rfc5384" title="&quot;The Protocol Independent Multicast (PIM) Join Attribute Format&quot;">RFC5384</a>]. The format of the Hierarchical Join/Prune
308 Attribute Hello Option is defined to be:
309
310 0 1 2 3
311 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
312 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
313 | OptionType = 36 | OptionLength = 0 |
314 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
315
316 OptionType = 36, OptionLength = 0. Note that there is no option
317 value included.
318
319 A PIM router MUST NOT send a Join/Prune message with Join/Prune
320 attributes encoded in the Upstream Neighbor Address or any of the
321 group addresses out of any interface on which there is a PIM neighbor
322 that has not included this option in its Hellos. Even a router that
323 is not the upstream neighbor must be able to parse the message in
324 order to perform Join suppression and Prune override.
325
326
327
328
329
330
331
332 <span class="grey">Venaas, et al. Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc7887">RFC 7887</a> Hierarchical Join/Prune Attributes June 2016</span>
335
336
337 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
338
339 This document specifies a more compact encoding of Join/Prune
340 attributes. Use of the encoding has no impact on security aside from
341 using the encoding in [<a href="./rfc5384" title="&quot;The Protocol Independent Multicast (PIM) Join Attribute Format&quot;">RFC5384</a>]. For instance, an attack with a
342 forged message with certain attribute values is equally difficult
343 independent of which encoding is used. If an attribute that applies
344 to the entire message is wrong, then that may cause an issue for all
345 the sources in the message. But without this encoding, one would
346 instead include that attribute for every single source, and that
347 would also cause an issue for all the sources in the message.
348
349 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IANA Considerations</span>
350
351 IANA has renamed the "PIM Encoded-Source Address Encoding Type Field"
352 registry to "PIM Address Encoding Types".
353
354 The Hierarchical Join/Prune Attribute (36) has been added to the
355 "PIM-Hello Options" registry.
356
357 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Normative References</span>
358
359 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
360 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>,
361 DOI 10.17487/RFC2119, March 1997,
362 &lt;<a href="http://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>&gt;.
363
364 [<a id="ref-RFC5384">RFC5384</a>] Boers, A., Wijnands, I., and E. Rosen, "The Protocol
365 Independent Multicast (PIM) Join Attribute Format",
366 <a href="./rfc5384">RFC 5384</a>, DOI 10.17487/RFC5384, November 2008,
367 &lt;<a href="http://www.rfc-editor.org/info/rfc5384">http://www.rfc-editor.org/info/rfc5384</a>&gt;.
368
369 [<a id="ref-RFC7761">RFC7761</a>] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I.,
370 Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent
371 Multicast - Sparse Mode (PIM-SM): Protocol Specification
372 (Revised)", STD 83, <a href="./rfc7761">RFC 7761</a>, DOI 10.17487/RFC7761, March
373 2016, &lt;<a href="http://www.rfc-editor.org/info/rfc7761">http://www.rfc-editor.org/info/rfc7761</a>&gt;.
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388 <span class="grey">Venaas, et al. Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc7887">RFC 7887</a> Hierarchical Join/Prune Attributes June 2016</span>
391
392
393 Authors' Addresses
394
395 Stig Venaas
396 Cisco Systems
397 Tasman Drive
398 San Jose, CA 95134
399 United States
400
401 Email: [email protected]
402
403
404 Jesus Arango
405 Cisco Systems
406 Tasman Drive
407 San Jose, CA 95134
408 United States
409
410 Email: [email protected]
411
412
413 Isidor Kouvelas
414 Arista Networks
415 5453 Great America Parkway
416 Santa Clara, CA 95054
417 United States
418
419 Email: [email protected]
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444 Venaas, et al. Standards Track [Page 8]
445 </pre>