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
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
|
<pre>Internet Engineering Task Force (IETF) S. Venaas
Request for Comments: 6676 R. Parekh
Category: Informational G. Van de Velde
ISSN: 2070-1721 Cisco Systems
T. Chown
University of Southampton
M. Eubanks
Iformata Communications
August 2012
<span class="h1">Multicast Addresses for Documentation</span>
Abstract
This document discusses which multicast addresses should be used for
documentation purposes and reserves multicast addresses for such use.
Some multicast addresses are derived from AS numbers or unicast
addresses. This document also explains how these can be used for
documentation purposes.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
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). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see <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/rfc6676">http://www.rfc-editor.org/info/rfc6676</a>.
<span class="grey">Venaas, et al. Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6676">RFC 6676</a> Multicast Addresses for Documentation August 2012</span>
Copyright Notice
Copyright (c) 2012 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.
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. IPv4 Multicast Documentation Addresses ..........................<a href="#page-3">3</a>
<a href="#section-2.1">2.1</a>. Administratively Scoped IPv4 Multicast Addresses ...........<a href="#page-3">3</a>
<a href="#section-2.2">2.2</a>. GLOP Multicast Addresses ...................................<a href="#page-3">3</a>
<a href="#section-2.3">2.3</a>. Unicast Prefix-Based IPv4 Multicast Addresses ..............<a href="#page-4">4</a>
<a href="#section-3">3</a>. IPv6 Multicast Documentation Addresses ..........................<a href="#page-4">4</a>
<a href="#section-3.1">3.1</a>. Unicast Prefix-Based IPv6 Multicast Addresses ..............<a href="#page-5">5</a>
<a href="#section-3.2">3.2</a>. Embedded-RP IPv6 Multicast Addresses .......................<a href="#page-5">5</a>
<a href="#section-4">4</a>. Security Considerations .........................................<a href="#page-5">5</a>
<a href="#section-5">5</a>. IANA Considerations .............................................<a href="#page-5">5</a>
<a href="#section-6">6</a>. Acknowledgments .................................................<a href="#page-6">6</a>
<a href="#section-7">7</a>. Informative References ..........................................<a href="#page-6">6</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
It is often useful in documentation, IETF documents, etc., to provide
examples containing IP multicast addresses. For documentation where
examples of general purpose multicast addresses are needed, one
should use multicast addresses that will never be assigned or in
actual use. There is a risk that addresses used in examples may
accidentally be used. It is then important that the same addresses
not be used by other multicast applications or services. It may also
be beneficial to filter out such addresses from multicast signalling
and to filter out multicast data sent to such addresses.
For unicast, there are both IPv4 and IPv6 addresses reserved for this
purpose; see [<a href="./rfc5737" title=""IPv4 Address Blocks Reserved for Documentation"">RFC5737</a>] and [<a href="./rfc3849" title=""IPv6 Address Prefix Reserved for Documentation"">RFC3849</a>], respectively. This document
reserves multicast addresses for this same purpose.
<span class="grey">Venaas, et al. Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6676">RFC 6676</a> Multicast Addresses for Documentation August 2012</span>
There are also some multicast addresses that are derived from AS
numbers or unicast addresses. For examples where such addresses are
desired, one should derive them from the AS numbers and unicast
addresses reserved for documentation purposes. This document also
discusses the use of these.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. IPv4 Multicast Documentation Addresses</span>
For Any-Source Multicast (ASM), the IPv4 multicast addresses
allocated for documentation purposes are 233.252.0.0 - 233.252.0.255
(233.252.0.0/24).
For Source-Specific Multicast (SSM), it is less important which
multicast addresses are used, since a host/application joins a
channel identified by both source and group. Any source addresses
used in SSM examples should be unicast addresses reserved for
documentation purposes. There are three unicast address ranges
provided for documentation use in [<a href="./rfc5737" title=""IPv4 Address Blocks Reserved for Documentation"">RFC5737</a>]. The ranges are
192.0.2.0/24, 198.51.100.0/24 and 203.0.113.0/24.
Sometimes one wants to give examples where a specific type of address
is desired. For example, for text about multicast scoping, one might
want the examples to use addresses that are to be used for
administrative scoping. See below for guidance on how to construct
specific types of example addresses.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Administratively Scoped IPv4 Multicast Addresses</span>
Administratively scoped IPv4 multicast addresses [<a href="./rfc2365" title=""Administratively Scoped IP Multicast"">RFC2365</a>] are
reserved for scoped multicast. They can be used within a site or an
organization. Apart from a small set of scope-relative addresses,
these addresses are not assigned. The high order /24 in every scope
is reserved for relative assignments. A relative assignment is an
integer offset from the highest address in the scope and represents
an IPv4 address. For documentation purposes, the integer offset is
10. This provides one multicast address per scope.
For example in the Local Scope 239.255.0.0/16, the multicast address
for documentation purposes is 239.255.255.245.
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. GLOP Multicast Addresses</span>
GLOP [<a href="./rfc3180" title=""GLOP Addressing in 233/8"">RFC3180</a>] is a method for deriving IPv4 multicast group
addresses from 16-bit AS numbers. For examples where GLOP addresses
are desired, the addresses should be derived from the AS numbers
reserved for documentation use.
<span class="grey">Venaas, et al. Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6676">RFC 6676</a> Multicast Addresses for Documentation August 2012</span>
The 16-bit AS numbers reserved for documentation use in [<a href="./rfc5398" title=""Autonomous System (AS) Number Reservation for Documentation Use"">RFC5398</a>] are
64496 - 64511. By use of [<a href="./rfc3180" title=""GLOP Addressing in 233/8"">RFC3180</a>], we then get 16 /24 multicast
prefixes for documentation use. The first one is 233.251.240.0/24,
and the last one is 233.251.255.0/24.
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Unicast Prefix-Based IPv4 Multicast Addresses</span>
IPv4 multicast addresses can be derived from IPv4 unicast prefixes,
see [<a href="./rfc6034" title=""Unicast-Prefix-Based IPv4 Multicast Addresses"">RFC6034</a>]. For examples where this type of address is desired,
the addresses should be derived from the unicast addresses reserved
for documentation purposes, see [<a href="./rfc5737" title=""IPv4 Address Blocks Reserved for Documentation"">RFC5737</a>].
There are three unicast address ranges provided for documentation use
in [<a href="./rfc5737" title=""IPv4 Address Blocks Reserved for Documentation"">RFC5737</a>]. The ranges are 192.0.2.0/24, 198.51.100.0/24, and
203.0.113.0/24. Using [<a href="./rfc6034" title=""Unicast-Prefix-Based IPv4 Multicast Addresses"">RFC6034</a>], this leaves the unicast prefix-
based IPv4 multicast addresses 234.192.0.2, 234.198.51.100, and
234.203.0.113.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IPv6 Multicast Documentation Addresses</span>
For Any-Source Multicast (ASM), the IPv6 multicast addresses
allocated for documentation purposes are FF0X::DB8:0:0/96. This is a
/96 prefix so that it can be used with group IDs, according to the
allocation guidelines in [<a href="./rfc3307" title=""Allocation Guidelines for IPv6 Multicast Addresses"">RFC3307</a>]. Also note that for these
addresses, the transient flag, or "T-flag" as defined in [<a href="./rfc4291" title=""IP Version 6 Addressing Architecture"">RFC4291</a>],
is zero. This is because they are permanently assigned. There can
be no permanently assigned addresses for documentation purposes with
the transient flag set to one, since the flag set to one means that
they are not permanently assigned.
For Source-Specific Multicast (SSM), it is less important which
multicast addresses are used, since a host/application joins a
channel identified by both source and group. Any source addresses
used in SSM examples should be unicast addresses reserved for
documentation purposes. The IPv6 unicast prefix reserved for
documentation purposes is 2001:DB8::/32, see [<a href="./rfc3849" title=""IPv6 Address Prefix Reserved for Documentation"">RFC3849</a>].
Sometimes one wants to give examples where a specific type of address
is desired. For example, for text about multicast scoping, one might
want the examples to use addresses that are to be used for
administrative scoping. See below for guidance on how to construct
specific types of example addresses.
<span class="grey">Venaas, et al. Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6676">RFC 6676</a> Multicast Addresses for Documentation August 2012</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Unicast Prefix-Based IPv6 Multicast Addresses</span>
IPv6 multicast addresses can be derived from IPv6 unicast prefixes,
see [<a href="./rfc3306" title=""Unicast-Prefix-based IPv6 Multicast Addresses"">RFC3306</a>]. For examples where this type of address is desired,
the addresses should be derived from the unicast addresses reserved
for documentation purposes.
The IPv6 unicast prefix reserved for documentation purposes is 2001:
DB8::/32, see [<a href="./rfc3849" title=""IPv6 Address Prefix Reserved for Documentation"">RFC3849</a>]. This allows a wide range of different IPv6
multicast addresses. Using just the base /32 prefix, one gets the
IPv6 multicast prefixes FF3X:20:2001:DB8::/64 -- one for each
available scope X. One can also produce longer prefixes from this.
Just as an example, one can pick a /64 prefix 2001:DB8:DEAD:
BEEF::/64, which gives the multicast prefixes FF3X:40:2001:DB8:DEAD:
BEEF::/96 -- one for each available scope X.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Embedded-RP IPv6 Multicast Addresses</span>
There is a type of IPv6 multicast address called an "Embedded-RP"
address, where the IPv6 address of a Rendezvous-Point (RP) is
embedded inside the multicast address, see [<a href="./rfc3956" title=""Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address"">RFC3956</a>]. For examples
where this type of address is desired, the addresses should be
derived from the unicast addresses reserved for documentation
purposes, see [<a href="./rfc3849" title=""IPv6 Address Prefix Reserved for Documentation"">RFC3849</a>].
For documentation purposes, the RP address can be any address from
the range 2001:DB8::/32 that follows the constraints specified in
[<a href="./rfc3956" title=""Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address"">RFC3956</a>]. One example address could be 2001:DB8::1. The
Embedded-RP multicast prefixes might then be FF7X:120:2001:DB8::/96.
Another example could be the RP address 2001:DB8:BEEF:FEED::7, which
gives the prefixes FF7X:740:2001:DB8:BEEF:FEED::/96. See also the
examples in [<a href="./rfc3956" title=""Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address"">RFC3956</a>].
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
The use of specific multicast addresses for documentation purposes
has no negative impact on security.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
IANA has added a reference to this document for the IPv4 MCAST-TEST-
NET allocation so that all the different documentation multicast
assignments reference this document.
IANA has assigned a scope-relative IPv4 address for documentation
purposes.
<span class="grey">Venaas, et al. Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6676">RFC 6676</a> Multicast Addresses for Documentation August 2012</span>
IANA has assigned "variable-scope" IPv6 multicast addresses for
documentation purposes. This is a /96 prefix.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgments</span>
The authors thank Roberta Maglione, Leonard Giuliano and Dave Thaler
for providing comments on this document.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Informative References</span>
[<a id="ref-RFC2365">RFC2365</a>] Meyer, D., "Administratively Scoped IP Multicast", <a href="https://www.rfc-editor.org/bcp/bcp23">BCP 23</a>,
<a href="./rfc2365">RFC 2365</a>, July 1998.
[<a id="ref-RFC3180">RFC3180</a>] Meyer, D. and P. Lothberg, "GLOP Addressing in 233/8",
<a href="https://www.rfc-editor.org/bcp/bcp53">BCP 53</a>, <a href="./rfc3180">RFC 3180</a>, September 2001.
[<a id="ref-RFC3306">RFC3306</a>] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6
Multicast Addresses", <a href="./rfc3306">RFC 3306</a>, August 2002.
[<a id="ref-RFC3307">RFC3307</a>] Haberman, B., "Allocation Guidelines for IPv6 Multicast
Addresses", <a href="./rfc3307">RFC 3307</a>, August 2002.
[<a id="ref-RFC3849">RFC3849</a>] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix
Reserved for Documentation", <a href="./rfc3849">RFC 3849</a>, July 2004.
[<a id="ref-RFC3956">RFC3956</a>] Savola, P. and B. Haberman, "Embedding the Rendezvous
Point (RP) Address in an IPv6 Multicast Address",
<a href="./rfc3956">RFC 3956</a>, November 2004.
[<a id="ref-RFC4291">RFC4291</a>] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", <a href="./rfc4291">RFC 4291</a>, February 2006.
[<a id="ref-RFC5398">RFC5398</a>] Huston, G., "Autonomous System (AS) Number Reservation for
Documentation Use", <a href="./rfc5398">RFC 5398</a>, December 2008.
[<a id="ref-RFC5737">RFC5737</a>] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks
Reserved for Documentation", <a href="./rfc5737">RFC 5737</a>, January 2010.
[<a id="ref-RFC6034">RFC6034</a>] Thaler, D., "Unicast-Prefix-Based IPv4 Multicast
Addresses", <a href="./rfc6034">RFC 6034</a>, October 2010.
<span class="grey">Venaas, et al. Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc6676">RFC 6676</a> Multicast Addresses for Documentation August 2012</span>
Authors' Addresses
Stig Venaas
Cisco Systems
Tasman Drive
San Jose, CA 95134
USA
EMail: stig@cisco.com
Rishabh Parekh
Cisco Systems
Tasman Drive
San Jose, CA 95134
USA
EMail: riparekh@cisco.com
Gunter Van de Velde
Cisco Systems
De Kleetlaan 6a
Diegem 1831
Belgium
Phone: +32 476 476 022
EMail: gvandeve@cisco.com
Tim Chown
University of Southampton
Highfield
Southampton, Hampshire SO17 1BJ
United Kingdom
EMail: tjc@ecs.soton.ac.uk
Marshall Eubanks
Iformata Communications
130 W. Second Street
Dayton, Ohio 45402
US
Phone: +1 703 501 4376
EMail: marshall.eubanks@iformata.com
URI: <a href="http://www.iformata.com/">http://www.iformata.com/</a>
Venaas, et al. Informational [Page 7]
</pre>
|
