idnits 2.17.1 draft-ietf-mboned-mcaddrdoc-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 4 instances of lines with multicast IPv4 addresses in the document. If these are generic example addresses, they should be changed to use the 233.252.0.x range defined in RFC 5771 Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 25, 2011) is 4565 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC3307' is defined on line 230, but no explicit reference was found in the text Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group S. Venaas 3 Internet-Draft R. Parekh 4 Intended status: Informational G. Van de Velde 5 Expires: April 27, 2012 cisco Systems 6 T. Chown 7 University of Southampton 8 M. Eubanks 9 Iformata Communications 10 October 25, 2011 12 Multicast Addresses for Documentation 13 draft-ietf-mboned-mcaddrdoc-02.txt 15 Abstract 17 This document discusses which multicast addresses should be used for 18 documentation purposes and reserves multicast addresses for such use. 19 Some multicast addresses are derived from AS numbers or unicast 20 addresses. This document also explains how these can be used for 21 documentation purposes. 23 Status of this Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at http://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on April 27, 2012. 40 Copyright Notice 42 Copyright (c) 2011 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 2. IPv4 multicast documentation addresses . . . . . . . . . . . . 4 59 2.1. Administratively scoped IPv4 multicast addresses . . . . . 4 60 2.2. GLOP multicast addresses . . . . . . . . . . . . . . . . . 4 61 2.3. Unicast prefix based IPv4 multicast addresses . . . . . . 4 62 3. IPv6 multicast documentation addresses . . . . . . . . . . . . 6 63 3.1. Unicast prefix based IPv6 multicast addresses . . . . . . 6 64 3.2. Embedded-RP IPv6 multicast addresses . . . . . . . . . . . 6 65 4. Security Considerations . . . . . . . . . . . . . . . . . . . 8 66 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 67 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 68 7. Informative References . . . . . . . . . . . . . . . . . . . . 11 69 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 71 1. Introduction 73 It is often useful in documentation, IETF documents, etc., to provide 74 examples containing IP multicast addresses. For documentation where 75 examples of general purpose multicast addresses are needed, one 76 should use multicast addresses that never will be assigned or in 77 actual use. There is a risk that addresses used in examples may 78 accidentally be used. It is then important that the same addresses 79 are not used by other multicast applications or services. It may 80 also be beneficial to filter out such addresses from multicast 81 signalling and multicast data sent to such addresses. 83 For unicast there are both IPv4 and IPv6 addresses reserved for this 84 purpose, see [RFC5737] and [RFC3849] respectively. This document 85 reserves multicast addresses for this purpose. 87 There are also some multicast addresses that are derived from AS 88 numbers or unicast addresses. For examples where such addresses are 89 desired, one should derive them from the AS numbers and unicast 90 addresses reserved for documentation purposes. This document also 91 discusses the use of these. 93 2. IPv4 multicast documentation addresses 95 The type of multicast addresses most commonly used today, are 96 addresses used for so-called ASM (Any-Source Multicast). For ASM, 97 the IPv4 multicast addresses allocated for documentation purposes are 98 233.252.0.0 - 233.252.0.255 (233.252.0.0/24). 100 Another type of multicast is SSM (Source-Specific Multicast). For 101 SSM it is less important which multicast addresses are used, since a 102 host/application joins a channel identified by both source and group. 103 Any source addresses used in SSM examples should be unicast addresses 104 reserved for documentation purposes. There are three unicast address 105 ranges provided for documentation use in [RFC5737]. The ranges are 106 192.0.2.0/24, 198.51.100.0/24 and 203.0.113.0/24. 108 Sometimes one wants to give examples where a specific type of address 109 is desired. E.g. for text about multicast scoping, one might want 110 the examples to use addresses that are to be used for administrative 111 scoping. See below for guidance on how to construct specific types 112 of example addresses. 114 2.1. Administratively scoped IPv4 multicast addresses 116 Administratively scoped IPv4 multicast addresses [RFC2365] are 117 reserved for scoped multicast. They can be used within a site or an 118 organization. Apart from a small set of scope relative addresses, 119 these addresses are not assigned. There are no specific scoped 120 addresses available for documentation purposes. Except for examples 121 detailing the use of scoped multicast, one should avoid using them. 123 2.2. GLOP multicast addresses 125 GLOP [RFC3180] is a method for deriving IPv4 multicast group 126 addresses from 16 bit AS numbers. For examples where GLOP addresses 127 are desired, the addresses should be derived from the AS numbers 128 reserved for documentation use. 130 The 16 bit AS numbers reserved for documentation use in [RFC5398] are 131 64496 - 64511. By use of [RFC3180], we then get 16 /24 multicast 132 prefixes for documentation use. The first one 233.251.240.0/24, and 133 the last 233.251.255.0/24. 135 2.3. Unicast prefix based IPv4 multicast addresses 137 IPv4 multicast addresses can be derived from IPv4 unicast prefixes, 138 see [RFC6034]. For examples where this type of addresses are 139 desired, the addresses should be derived from the unicast addresses 140 reserved for documentation purposes, see [RFC5737]. 142 There are three unicast address ranges provided for documentation use 143 in [RFC5737]. The ranges are 192.0.2.0/24, 198.51.100.0/24 and 144 203.0.113.0/24. Using [RFC6034] this leaves us with the unicast 145 prefix based IPv4 multicast addresses 234.192.0.2, 234.198.51.100 and 146 234.203.0.113. 148 3. IPv6 multicast documentation addresses 150 The type of multicast addresses most commonly used today, are 151 addresses used for so-called ASM (Any-Source Multicast). For ASM, 152 the IPv6 multicast addresses allocated for documentation purposes are 153 TBD. 155 Another type of multicast is SSM (Source-Specific Multicast). For 156 SSM it is less important which multicast addresses are used, since a 157 host/application joins a channel identified by both source and group. 158 Any source addresses used in SSM examples should be unicast addresses 159 reserved for documentation purposes. The IPv6 unicast prefix 160 reserved for documentation purposes is 2001:DB8::/32, see [RFC3849]. 162 Sometimes one wants to give examples where a specific type of address 163 is desired. E.g. for text about multicast scoping, one might want 164 the examples to use addresses that are to be used for administrative 165 scoping. See below for guidance on how to construct specific types 166 of example addresses. 168 3.1. Unicast prefix based IPv6 multicast addresses 170 IPv6 multicast addresses can be derived from IPv6 unicast prefixes, 171 see [RFC3306]. For examples where this type of addresses is desired, 172 the addresses should be derived from the unicast addresses reserved 173 for documentation purposes. 175 The IPv6 unicast prefix reserved for documentation purposes is 2001: 176 DB8::/32, see [RFC3849]. This allows a wide range of different IPv6 177 multicast addresses. Using just the base /32 prefix, one get the 178 IPv6 multicast prefixes FF3X:20:2001:DB8::/64, one for each available 179 scope X. One can also produce longer prefixes from this. Just as an 180 example, one can pick say a /64 prefix 2001:DB8:DEAD:BEEF::/64 which 181 gives the multicast prefixes FF3X:40:2001:DB8:DEAD:BEEF::/96, one for 182 each available scope X. 184 3.2. Embedded-RP IPv6 multicast addresses 186 There is a type of IPv6 multicast addresses called Embedded-RP 187 addresses where the IPv6 address of a Rendezvous-Point is embedded 188 inside the multicast address, see [RFC3956]. For examples where this 189 type of addresses is desired, the addresses should be derived from 190 the unicast addresses reserved for documentation purposes, see see 191 [RFC3849]. 193 For documentation purposes, the RP address can be any address from 194 the range 2001:DB8::/32 that follows the constraints specified in 195 [RFC3956]. One example address could be 2001:DB8::1. The 196 embedded-RP multicast prefixes might then be FF7X:120:2001:DB8::/96. 197 Another example could be the RP address 2001:DB8:BEEF:FEED::7 which 198 gives the prefixes FF7X:740:2001:DB8:BEEF:FEED::/96. See also the 199 examples in [RFC3956]. 201 4. Security Considerations 203 The use of specific multicast addresses for documentation purposes 204 has no impact on security. 206 5. IANA Considerations 208 IANA is requested to assign "variable scope" IPv6 multicast addresses 209 for documentation purposes. This should be a /96 prefix of the form 210 FF0X:... The word TBD in this text should be replaced with the 211 assigned prefix, and this sentence should be deleted before 212 publishing. 214 6. Acknowledgments 216 The authors thank Roberta Maglione and Leonard Giuliano for providing 217 comments on this document. 219 7. Informative References 221 [RFC2365] Meyer, D., "Administratively Scoped IP Multicast", BCP 23, 222 RFC 2365, July 1998. 224 [RFC3180] Meyer, D. and P. Lothberg, "GLOP Addressing in 233/8", 225 BCP 53, RFC 3180, September 2001. 227 [RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 228 Multicast Addresses", RFC 3306, August 2002. 230 [RFC3307] Haberman, B., "Allocation Guidelines for IPv6 Multicast 231 Addresses", RFC 3307, August 2002. 233 [RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix 234 Reserved for Documentation", RFC 3849, July 2004. 236 [RFC3956] Savola, P. and B. Haberman, "Embedding the Rendezvous 237 Point (RP) Address in an IPv6 Multicast Address", 238 RFC 3956, November 2004. 240 [RFC5398] Huston, G., "Autonomous System (AS) Number Reservation for 241 Documentation Use", RFC 5398, December 2008. 243 [RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks 244 Reserved for Documentation", RFC 5737, January 2010. 246 [RFC6034] Thaler, D., "Unicast-Prefix-Based IPv4 Multicast 247 Addresses", RFC 6034, October 2010. 249 Authors' Addresses 251 Stig Venaas 252 cisco Systems 253 Tasman Drive 254 San Jose, CA 95134 255 USA 257 Email: stig@cisco.com 259 Rishabh Parekh 260 cisco Systems 261 Tasman Drive 262 San Jose, CA 95134 263 USA 265 Email: riparekh@cisco.com 267 Gunter Van de Velde 268 cisco Systems 269 De Kleetlaan 6a 270 Diegem 1831 271 Belgium 273 Phone: +32 476 476 022 274 Email: gvandeve@cisco.com 276 Tim Chown 277 University of Southampton 278 Highfield 279 Southampton, Hampshire SO17 1BJ 280 United Kingdom 282 Email: tjc@ecs.soton.ac.uk 283 Marshall Eubanks 284 Iformata Communications 285 130 W. Second Street 286 Dayton, Ohio 45402 287 US 289 Phone: +1 703 501 4376 290 Email: marshall.eubanks@iformata.com 291 URI: http://www.iformata.com/