Debian Codegraph @

rfc2365.html

raw
1 <pre>Network Working Group D. Meyer
2 Request for Comments: 2365 University of Oregon
3 BCP: 23 July 1998
4 Category: Best Current Practice
5
6
7 <span class="h1">Administratively Scoped IP Multicast</span>
8
9 Status of this Memo
10
11 This document specifies an Internet Best Current Practices for the
12 Internet Community, and requests discussion and suggestions for
13 improvements. Distribution of this memo is unlimited.
14
15 Copyright Notice
16
17 Copyright (C) The Internet Society (1998). All Rights Reserved.
18
19 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Abstract</span>
20
21 This document defines the "administratively scoped IPv4 multicast
22 space" to be the range 239.0.0.0 to 239.255.255.255. In addition, it
23 describes a simple set of semantics for the implementation of
24 Administratively Scoped IP Multicast. Finally, it provides a mapping
25 between the IPv6 multicast address classes [<a href="./rfc1884" title="&quot;IP Version 6 Addressing Architecture&quot;">RFC1884</a>] and IPv4
26 multicast address classes.
27
28 This memo is a product of the MBONE Deployment Working Group (MBONED)
29 in the Operations and Management Area of the Internet Engineering
30 Task Force. Submit comments to &lt;[email protected]&gt; or the author.
31
32 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Acknowledgments</span>
33
34 Much of this memo is taken from "Administratively Scoped IP
35 Multicast", Van Jacobson and Steve Deering, presented at the 30th
36 IETF, Toronto, Canada, 25 July 1994. Steve Casner, Mark Handley and
37 Dave Thaler have also provided insightful comments on earlier
38 versions of this document.
39
40 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Introduction</span>
41
42 Most current IP multicast implementations achieve some level of
43 scoping by using the TTL field in the IP header. Typical MBONE
44 (Multicast Backbone) usage has been to engineer TTL thresholds that
45 confine traffic to some administratively defined topological region.
46 The basic forwarding rule for interfaces with configured TTL
47 thresholds is that a packet is not forwarded across the interface
48 unless its remaining TTL is greater than the threshold.
49
50
51
52 <span class="grey">Meyer Best Current Practice [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc2365">RFC 2365</a> Administratively Scoped IP Multicast July 1998</span>
55
56
57 TTL scoping has been used to control the distribution of multicast
58 traffic with the objective of easing stress on scarce resources
59 (e.g., bandwidth), or to achieve some kind of improved privacy or
60 scaling properties. In addition, the TTL is also used in its
61 traditional role to limit datagram lifetime. Given these often
62 conflicting roles, TTL scoping has proven difficult to implement
63 reliably, and the resulting schemes have often been complex and
64 difficult to understand.
65
66 A more serious architectural problem concerns the interaction of TTL
67 scoping with broadcast and prune protocols (e.g., DVMRP [<a href="#ref-DVMRP" title="&quot;Distance Vector Multicast Routing Protocol&quot;">DVMRP</a>]). The
68 particular problem is that in many common cases, TTL scoping can
69 prevent pruning from being effective. Consider the case in which a
70 packet has either had its TTL expire or failed a TTL threshold. The
71 router which discards the packet will not be capable of pruning any
72 upstream sources, and thus will sink all multicast traffic (whether
73 or not there are downstream receivers). Note that while it might seem
74 possible to send prunes upstream from the point at which a packet is
75 discarded, this strategy can result in legitimate traffic being
76 discarded, since subsequent packets could take a different path and
77 arrive at the same point with a larger TTL.
78
79 On the other hand, administratively scoped IP multicast can provide
80 clear and simple semantics for scoped IP multicast. The key
81 properties of administratively scoped IP multicast are that (i).
82 packets addressed to administratively scoped multicast addresses do
83 not cross configured administrative boundaries, and (ii).
84 administratively scoped multicast addresses are locally assigned, and
85 hence are not required to be unique across administrative boundaries.
86
87 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Definition of the Administratively Scoped IPv4 Multicast Space</span>
88
89 The administratively scoped IPv4 multicast address space is defined
90 to be the range 239.0.0.0 to 239.255.255.255.
91
92 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Discussion</span>
93
94 In order to support administratively scoped IP multicast, a router
95 should support the configuration of per-interface scoped IP multicast
96 boundaries. Such a router, called a boundary router, does not forward
97 packets matching an interface's boundary definition in either
98 direction (the bi-directional check prevents problems with multi-
99 access networks). In addition, a boundary router always prunes the
100 boundary for dense-mode groups [<a href="#ref-PIMDM" title="&quot;Protocol Independent Multicast Version 2, Dense Mode Specification&quot;">PIMDM</a>], and doesn't accept joins for
101 sparse-mode groups [<a href="#ref-PIMSM" title="&quot;Protocol Independent Multicast Sparse Mode (PIM-SM): Protocol Specification&quot;">PIMSM</a>] in the administratively scoped range.
102
103
104
105
106
107
108 <span class="grey">Meyer Best Current Practice [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc2365">RFC 2365</a> Administratively Scoped IP Multicast July 1998</span>
111
112
113 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. The Structure of the Administratively Scoped Multicast Space</span>
114
115 The structure of the IP version 4 administratively scoped multicast
116 space is loosely based on the IP Version 6 Addressing Architecture
117 described in <a href="./rfc1884">RFC 1884</a> [<a href="./rfc1884" title="&quot;IP Version 6 Addressing Architecture&quot;">RFC1884</a>]. This document defines two important
118 scopes: the IPv4 Local Scope and IPv4 Organization Local Scope. These
119 scopes are described below.
120
121 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. The IPv4 Local Scope -- 239.255.0.0/16</span>
122
123 239.255.0.0/16 is defined to be the IPv4 Local Scope. The Local
124 Scope is the minimal enclosing scope, and hence is not further
125 divisible. Although the exact extent of a Local Scope is site
126 dependent, locally scoped regions must obey certain topological
127 constraints. In particular, a Local Scope must not span any other
128 scope boundary. Further, a Local Scope must be completely contained
129 within or equal to any larger scope. In the event that scope regions
130 overlap in area, the area of overlap must be in its own local scope.
131 This implies that any scope boundary is also a boundary for the Local
132 Scope. The more general topological requirements for administratively
133 scoped regions are discussed below.
134
135 6.1.1. Expansion of the IPv4 Local Scope
136
137 The IPv4 Local Scope space grows "downward". As such, the IPv4 Local
138 Scope may grow downward from 239.255.0.0/16 into the reserved ranges
139 239.254.0.0/16 and 239.253.0.0/16. However, these ranges should not
140 be utilized until the 239.255.0.0/16 space is no longer sufficient.
141
142 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. The IPv4 Organization Local Scope -- 239.192.0.0/14</span>
143
144 239.192.0.0/14 is defined to be the IPv4 Organization Local Scope,
145 and is the space from which an organization should allocate sub-
146 ranges when defining scopes for private use.
147
148 <span class="h4"><a class="selflink" id="section-6.2.1" href="#section-6.2.1">6.2.1</a>. Expansion of the IPv4 Organization Local Scope</span>
149
150 The ranges 239.0.0.0/10, 239.64.0.0/10 and 239.128.0.0/10 are
151 unassigned and available for expansion of this space. These ranges
152 should be left unassigned until the 239.192.0.0/14 space is no longer
153 sufficient. This is to allow for the possibility that future
154 revisions of this document may define additional scopes on a scale
155 larger than organizations.
156
157 <span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. Other IPv4 Scopes of Interest</span>
158
159 The other two scope classes of interest, statically assigned link-
160 local scope and global scope already exist in IPv4 multicast space.
161
162
163
164 <span class="grey">Meyer Best Current Practice [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc2365">RFC 2365</a> Administratively Scoped IP Multicast July 1998</span>
167
168
169 The statically assigned link-local scope is 224.0.0.0/24. The
170 existing static global scope allocations are somewhat more granular,
171 and include
172
173 224.1.0.0-224.1.255.255 ST Multicast Groups
174 224.2.0.0-224.2.127.253 Multimedia Conference Calls
175 224.2.127.254 SAPv1 Announcements
176 224.2.127.255 SAPv0 Announcements (deprecated)
177 224.2.128.0-224.2.255.255 SAP Dynamic Assignments
178 224.252.0.0-224.255.255.255 DIS transient groups
179 232.0.0.0-232.255.255.255 VMTP transient groups
180
181 See [<a href="./rfc1700" title="&quot;Assigned Numbers&quot;">RFC1700</a>] for current multicast address assignments (this list
182 can also be found, possibly in a more current form, on
183 <a href="ftp://ftp.isi.edu/in-notes/iana/assignments/multicast-addresses">ftp://ftp.isi.edu/in-notes/iana/assignments/multicast-addresses</a>).
184
185 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Topological Requirements for Administrative Boundaries</span>
186
187 An administratively scoped IP multicast region is defined to be a
188 topological region in which there are one or more boundary routers
189 with common boundary definitions. Such a router is said to be a
190 boundary for scoped addresses in the range defined in its
191 configuration.
192
193 Network administrators may configure a scope region whenever
194 constrained multicast scope is required. In addition, an
195 administrator may configure overlapping scope regions (networks can
196 be in multiple scope regions) where convenient, with the only
197 limitations being that a scope region must be connected (there must
198 be a path between any two nodes within a scope region that doesn't
199 leave that region), and convex (i.e., no path between any two points
200 in the region can cross a region boundary). However, it is important
201 to note that if administratively scoped areas intersect
202 topologically, then the outer scope must consist of its address space
203 minus the address spaces of any intersecting scopes. This requirement
204 prevents the problem that would arise when a path between two points
205 in a convex region crosses the boundary of an intersecting region.
206 For this reason, it is recommended that administrative scopes that
207 intersect topologically should not intersect in address range.
208
209 Finally, note that any scope boundary is a boundary for the Local
210 Scope. This implies that packets sent to groups covered by
211 239.255.0.0/16 must not be forwarded across any link for which a
212 scoped boundary is defined.
213
214
215
216
217
218
219
220 <span class="grey">Meyer Best Current Practice [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc2365">RFC 2365</a> Administratively Scoped IP Multicast July 1998</span>
223
224
225 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Partitioning of the Administratively Scoped Multicast Space</span>
226
227 The following table outlines the partitioning of the IPv4 multicast
228 space, and gives the mapping from IPv4 multicast prefixes to IPv6
229 SCOP values:
230
231 IPv6 SCOP <a href="./rfc1884">RFC 1884</a> Description IPv4 Prefix
232 ===============================================================
233 0 reserved
234 1 node-local scope
235 2 link-local scope 224.0.0.0/24
236 3 (unassigned) 239.255.0.0/16
237 4 (unassigned)
238 5 site-local scope
239 6 (unassigned)
240 7 (unassigned)
241 8 organization-local scope 239.192.0.0/14
242 A (unassigned)
243 B (unassigned)
244 C (unassigned)
245 D (unassigned)
246 E global scope 224.0.1.0-238.255.255.255
247 F reserved
248 (unassigned) 239.0.0.0/10
249 (unassigned) 239.64.0.0/10
250 (unassigned) 239.128.0.0/10
251
252 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Structure and Use of a Scoped Region</span>
253
254 The high order /24 in every scoped region is reserved for relative
255 assignments. A relative assignment is an integer offset from highest
256 address in the scope and represents a 32-bit address (for IPv4). For
257 example, in the Local Scope defined above, 239.255.255.0/24 is
258 reserved for relative allocations. The de-facto relative assignment
259 "0", (i.e., 239.255.255.255 in the Local Scope) currently exists for
260 SAP [<a href="#ref-SAP" title="&quot;SAP: Session Announcement Protocol&quot;">SAP</a>]. The next relative assignment, "1", corresponds to the
261 address 239.255.255.254 in the Local Scope. The rest of a scoped
262 region below the reserved /24 is available for dynamic assignment
263 (presumably by an address allocation protocol).
264
265 In is important to note that a scope discovery protocol [<a href="#ref-MZAP" title="&quot;Multicast-Scope Zone Announcement Protocol (MZAP)&quot;">MZAP</a>] will
266 have to be developed to make practical use of scopes other than the
267 Local Scope. In addition, since any use of any administratively
268 scoped region, including the Local Scope, requires dynamically
269 assigned addressing, an Address Allocation Protocol (AAP) will need
270 to be developed to make administrative scoping generally useful.
271
272
273
274
275
276 <span class="grey">Meyer Best Current Practice [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc2365">RFC 2365</a> Administratively Scoped IP Multicast July 1998</span>
279
280
281 <span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Relative Assignment Guidelines</span>
282
283 Requests for relative assignments should be directed to the IANA. The
284 IANA will be advised by an area expert when making relative address
285 assignments. The area expert will be appointed by the relevant Area
286 Director.
287
288 In general, relative addresses will be used only for bootstrapping to
289 dynamic address assignments from within the scope. As such, relative
290 assignments should only be made to those services that cannot use a
291 dynamic address assignment protocol to find the address used by that
292 service within the desired scope, such as a dynamic address
293 assignment service itself.
294
295 10. Security Considerations
296
297 It is recommended that organizations using the administratively
298 scoped IP Multicast addresses not rely on them to prevent sensitive
299 data from being transmitted outside the organization. Should a
300 multicast router on an administrative boundary be mis-configured,
301 have a bug in the administrative scoping code, or have other problems
302 that would cause that router to forward an administratively scoped IP
303 multicast packet outside of the proper scope, the organizations data
304 would leave its intended transmission region.
305
306 Organizations using administratively scoped IP Multicasting to
307 transmit sensitive data should use some confidentiality mechanism
308 (e.g. encryption) to protect that data. In the case of many existing
309 video-conferencing applications (e.g. vat), encryption is available
310 as an application feature and merely needs to be enabled (and
311 appropriate cryptographic keys securely distributed). For many other
312 applications, the use of the IP Encapsulating Security Payload (ESP)
313 [RFC-1825, <a href="./rfc1827">RFC-1827</a>] can provide IP-layer confidentiality though
314 encryption.
315
316 Within the context of an administratively scoped IP multicast group,
317 the use of manual key distribution might well be feasible. While
318 dynamic key management for IP Security is a research area at the time
319 this note is written, it is expected that the IETF will be extending
320 the ISAKMP key management protocol to support scalable multicast key
321 distribution in the future.
322
323 It is important to note that the "boundary router" described in this
324 note is not necessarily providing any kind of firewall capability.
325
326
327
328
329
330
331
332 <span class="grey">Meyer Best Current Practice [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc2365">RFC 2365</a> Administratively Scoped IP Multicast July 1998</span>
335
336
337 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. References</span>
338
339 [<a id="ref-ASMA">ASMA</a>] V. Jacobson, S. Deering, "Administratively Scoped IP
340 Multicast", presented at the 30th IETF, Toronto, Canada, 25
341 July 1994.
342
343 [<a id="ref-DVMRP">DVMRP</a>] Pusateri, T., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&amp;q=inurl:draft-+%22Distance+Vector+Multicast+Routing+Protocol%22'>"Distance Vector Multicast Routing Protocol"</a>,
344 Work in Progress.
345
346 [<a id="ref-MZAP">MZAP</a>] Handley, M., "Multicast-Scope Zone Announcement Protocol
347 (MZAP)", Work in Progress.
348
349 [<a id="ref-PIMDM">PIMDM</a>] Deering, S, et. al., "Protocol Independent Multicast
350 Version 2, Dense Mode Specification", Work in Progress.
351
352 [<a id="ref-PIMSM">PIMSM</a>] Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering,
353 S., Handley, M., Jacobson, V., Liu, C., Sharma, P., and L.
354 Wei, "Protocol Independent Multicast Sparse Mode (PIM-SM):
355 Protocol Specification", <a href="./rfc2362">RFC 2362</a>, June 1998.
356
357 [<a id="ref-RFC1700">RFC1700</a>] Reynolds, J., and J. Postel, "Assigned Numbers", STD 2, <a href="./rfc1700">RFC</a>
358 <a href="./rfc1700">1700</a>, October 1994.
359
360 [<a id="ref-RFC1884">RFC1884</a>] Hinden. R., and S. Deering, "IP Version 6 Addressing
361 Architecture", <a href="./rfc1884">RFC1884</a>, December 1995.
362
363 [<a id="ref-SAP">SAP</a>] Handley, M., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&amp;q=inurl:draft-+%22SAP%3A+Session+Announcement+Protocol%22'>"SAP: Session Announcement Protocol"</a>, Work in
364 Progress.
365
366 <span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. Author's Address</span>
367
368 David Meyer
369 Cisco Systems
370 San Jose, CA
371
372 EMail: [email protected]
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388 <span class="grey">Meyer Best Current Practice [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc2365">RFC 2365</a> Administratively Scoped IP Multicast July 1998</span>
391
392
393 <span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>. Full Copyright Statement</span>
394
395 Copyright (C) The Internet Society (1998). All Rights Reserved.
396
397 This document and translations of it may be copied and furnished to
398 others, and derivative works that comment on or otherwise explain it
399 or assist in its implementation may be prepared, copied, published
400 and distributed, in whole or in part, without restriction of any
401 kind, provided that the above copyright notice and this paragraph are
402 included on all such copies and derivative works. However, this
403 document itself may not be modified in any way, such as by removing
404 the copyright notice or references to the Internet Society or other
405 Internet organizations, except as needed for the purpose of
406 developing Internet standards in which case the procedures for
407 copyrights defined in the Internet Standards process must be
408 followed, or as required to translate it into languages other than
409 English.
410
411 The limited permissions granted above are perpetual and will not be
412 revoked by the Internet Society or its successors or assigns.
413
414 This document and the information contained herein is provided on an
415 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
416 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
417 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
418 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
419 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
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 Meyer Best Current Practice [Page 8]
445 </pre>