idnits 2.17.1 draft-ietf-mboned-mcaddrdoc-01.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 3 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 (July 8, 2011) is 4677 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC3307' is defined on line 202, 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 T. Chown 3 Internet-Draft University of Southampton 4 Intended status: Informational M. Eubanks 5 Expires: January 9, 2012 Iformata Communications 6 R. Parekh 7 G. Van de Velde 8 S. Venaas 9 cisco Systems 10 July 8, 2011 12 Multicast Addresses for Documentation 13 draft-ietf-mboned-mcaddrdoc-01.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 January 9, 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 . . . . . . . . . . . . 5 63 3.1. Unicast prefix based IPv6 multicast addresses . . . . . . 5 64 3.2. Embedded-RP IPv6 multicast addresses . . . . . . . . . . . 5 65 4. Security Considerations . . . . . . . . . . . . . . . . . . . 6 66 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 67 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8 68 7. Informative References . . . . . . . . . . . . . . . . . . . . 9 69 Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 10 70 A.1. GLOP multicast addresses . . . . . . . . . . . . . . . . . 10 71 A.2. Unicast prefix based IPv4 multicast addresses . . . . . . 10 72 A.3. Unicast prefix based IPv6 multicast addresses . . . . . . 10 73 A.4. Embedded-RP IPv6 multicast addresses . . . . . . . . . . . 10 74 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 76 1. Introduction 78 It is often useful in documentation, IETF documents, etc., to provide 79 examples containing IP multicast addresses. For documentation where 80 examples of general purpose multicast addresses are needed, one 81 should use multicast addresses that never will be assigned or in 82 actual use. There is a risk that addresses used in examples may 83 accidentally be used. It is then important that the same addresses 84 are not used by other multicast applications or services. It may 85 also be beneficial to filter out such addresses from multicast 86 signalling and multicast data sent to such addresses. 88 For unicast there are both IPv4 and IPv6 addresses reserved for this 89 purpose, see [RFC5737] and [RFC3849] respectively. This document 90 reserves multicast addresses for this purpose. 92 There are also some multicast addresses that are derived from AS 93 numbers or unicast addresses. For examples where such addresses are 94 desired, one should derive them from the AS numbers and unicast 95 addresses reserved for documentation purposes. This document also 96 discusses the use of these. 98 2. IPv4 multicast documentation addresses 100 The type of multicast addresses most commonly used today, are 101 addresses used for so-called ASM (Any-Source Multicast). For ASM, 102 the IPv4 multicast addresses allocated for documentation purposes are 103 233.252.0.0 - 233.252.0.255 (233.252.0.0/24). 105 Another type of multicast is SSM (Source-Specific Multicast). For 106 SSM it is less important which multicast addresses are used, since a 107 host/application joins a channel identified by both source and group. 108 Any source addresses used in SSM examples should be unicast addresses 109 reserved for documentation purposes, see [RFC5737]. 111 Sometimes one wants to give examples where a specific type of address 112 is desired. E.g. for text about multicast scoping, one might want 113 the examples to use addresses that are to be used for administrative 114 scoping. See below for guidance on how to construct specific types 115 of example addresses. 117 2.1. Administratively scoped IPv4 multicast addresses 119 Administratively scoped IPv4 multicast addresses [RFC2365] are 120 reserved for scoped multicast. They can be used within a site or an 121 organization. Apart from a small set of scope relative addresses, 122 these addresses are not assigned. There are no specific scoped 123 addresses available for documentation purposes. Except for examples 124 detailing the use of scoped multicast, one should avoid using them. 126 2.2. GLOP multicast addresses 128 GLOP [RFC3180] is a method for deriving IPv4 multicast group 129 addresses from 16 bit AS numbers. For examples where GLOP addresses 130 are desired, the addresses should be derived from the AS numbers 131 reserved for documentation use. See [RFC5398]. 133 2.3. Unicast prefix based IPv4 multicast addresses 135 IPv4 multicast addresses can be derived from IPv4 unicast prefixes, 136 see [RFC6034]. For examples where this type of addresses are 137 desired, the addresses should be derived from the unicast addresses 138 reserved for documentation purposes, see [RFC5737]. 140 3. IPv6 multicast documentation addresses 142 The type of multicast addresses most commonly used today, are 143 addresses used for so-called ASM (Any-Source Multicast). For ASM, 144 the IPv6 multicast addresses allocated for documentation purposes are 145 TBD. 147 Another type of multicast is SSM (Source-Specific Multicast). For 148 SSM it is less important which multicast addresses are used, since a 149 host/application joins a channel identified by both source and group. 150 Any source addresses used in SSM examples should be unicast addresses 151 reserved for documentation purposes, see [RFC3849]. 153 Sometimes one wants to give examples where a specific type of address 154 is desired. E.g. for text about multicast scoping, one might want 155 the examples to use addresses that are to be used for administrative 156 scoping. See below for guidance on how to construct specific types 157 of example addresses. 159 3.1. Unicast prefix based IPv6 multicast addresses 161 IPv6 multicast addresses can be derived from IPv6 unicast prefixes, 162 see [RFC3306]. For examples where this type of addresses is desired, 163 the addresses should be derived from the unicast addresses reserved 164 for documentation purposes, see [RFC3849]. 166 3.2. Embedded-RP IPv6 multicast addresses 168 There is a type of IPv6 multicast addresses called Embedded-RP 169 addresses where the IPv6 address of a Rendezvous-Point is embedded 170 inside the multicast address, see [RFC3956]. For examples where this 171 type of addresses is desired, the addresses should be derived from 172 the unicast addresses reserved for documentation purposes, see see 173 [RFC3849]. 175 4. Security Considerations 177 The use of specific multicast addresses for documentation purposes 178 has no impact on security. 180 5. IANA Considerations 182 IANA is requested to assign "variable scope" IPv6 multicast addresses 183 for documentation purposes. This should be a /96 prefix of the form 184 FF0X:... 186 6. Acknowledgments 188 The authors thank Roberta Maglione for providing comments on this 189 document. 191 7. Informative References 193 [RFC2365] Meyer, D., "Administratively Scoped IP Multicast", BCP 23, 194 RFC 2365, July 1998. 196 [RFC3180] Meyer, D. and P. Lothberg, "GLOP Addressing in 233/8", 197 BCP 53, RFC 3180, September 2001. 199 [RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 200 Multicast Addresses", RFC 3306, August 2002. 202 [RFC3307] Haberman, B., "Allocation Guidelines for IPv6 Multicast 203 Addresses", RFC 3307, August 2002. 205 [RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix 206 Reserved for Documentation", RFC 3849, July 2004. 208 [RFC3956] Savola, P. and B. Haberman, "Embedding the Rendezvous 209 Point (RP) Address in an IPv6 Multicast Address", 210 RFC 3956, November 2004. 212 [RFC5398] Huston, G., "Autonomous System (AS) Number Reservation for 213 Documentation Use", RFC 5398, December 2008. 215 [RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks 216 Reserved for Documentation", RFC 5737, January 2010. 218 [RFC6034] Thaler, D., "Unicast-Prefix-Based IPv4 Multicast 219 Addresses", RFC 6034, October 2010. 221 Appendix A. Examples 223 Usually addresses for documentation can simply be selected from the 224 addresses reserved for such. But as we discuss in this document, 225 there are cases where one wants to use multicast addresses derived 226 from AS numbers (GLOP) or from unicast addresses. In this appendix 227 we will just provide some examples for how such addresses can be 228 derived. 230 A.1. GLOP multicast addresses 232 GLOP [RFC3180] is a method for deriving IPv4 multicast group 233 addresses from 16 bit AS numbers. The 16 bit AS numbers reserved for 234 documentation use in [RFC5398] are 64496 - 64511. By use of 235 [RFC3180], we then get 16 /24 multicast prefixes for documentation 236 use. The first one 233.251.240.0/24, and the last 233.251.255.0/24. 238 A.2. Unicast prefix based IPv4 multicast addresses 240 IPv4 multicast addresses can be derived from IPv4 unicast prefixes, 241 see [RFC6034]. There are three unicast address ranges provided for 242 documentation use in [RFC5737]. The ranges are 192.0.2.0/24, 243 198.51.100.0/24 and 203.0.113.0/24. Using [RFC6034] this leaves us 244 with the unicast prefix based IPv4 multicast addresses 234.192.0.2, 245 234.198.51.100 and 234.203.0.113. 247 A.3. Unicast prefix based IPv6 multicast addresses 249 IPv6 multicast addresses can be derived from IPv6 unicast prefixes, 250 see [RFC3306]. The IPv6 unicast prefix reserved for documentation 251 purposes is 2001:DB8::/32, see [RFC3849]. This allows a wide range 252 of different IPv6 multicast addresses. Using just the base /32 253 prefix, one get the IPv6 multicast prefixes FF3X:20:2001:DB8::/64, 254 one for each available scope X. But also, from 2001:DB8::/32 one can 255 pick say a /64 prefix 2001:DB8:DEAD:BEEF::/64 which gives us the 256 multicast prefixes FF3X:40:2001:DB8:DEAD:BEEF::/96, one for each 257 available scope X. 259 A.4. Embedded-RP IPv6 multicast addresses 261 For Embedded-RP IPv6 multicast addresses, the the IPv6 address of a 262 Rendezvous-Point is embedded inside the multicast address, see 263 [RFC3956]. For documentation purposes, the RP address can be any 264 address from the range 2001:DB8::/32, see [RFC3849], that follows the 265 constraints specified in [RFC3956]. One example address could be 266 2001:DB8::1. The embedded-RP multicast prefixes might then be FF7X: 267 120:2001:DB8::/96. Another example could be the RP address 2001:DB8: 268 BEEF:FEED::7 which gives the prefixes FF7X:740:2001:DB8:BEEF: 270 FEED::/96. See also the examples in [RFC3956]. 272 Authors' Addresses 274 Tim Chown 275 University of Southampton 276 Highfield 277 Southampton, Hampshire SO17 1BJ 278 United Kingdom 280 Email: tjc@ecs.soton.ac.uk 282 Marshall Eubanks 283 Iformata Communications 284 130 W. Second Street 285 Dayton, Ohio 45402 286 US 288 Phone: +1 703 501 4376 289 Email: marshall.eubanks@iformata.com 290 URI: http://www.iformata.com/ 292 Rishabh Parekh 293 cisco Systems 294 Tasman Drive 295 San Jose, CA 95134 296 USA 298 Email: riparekh@cisco.com 300 Gunter Van de Velde 301 cisco Systems 302 De Kleetlaan 6a 303 Diegem 1831 304 Belgium 306 Phone: +32 476 476 022 307 Email: gvandeve@cisco.com 308 Stig Venaas 309 cisco Systems 310 Tasman Drive 311 San Jose, CA 95134 312 USA 314 Email: stig@cisco.com