idnits 2.17.1 draft-venaas-mboned-mcaddrdoc-03.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 14, 2011) is 4793 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC3307' is defined on line 206, but no explicit reference was found in the text Summary: 0 errors (**), 0 flaws (~~), 2 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: September 15, 2011 Iformata Communications 6 R. Parekh 7 G. Van de Velde 8 S. Venaas 9 cisco Systems 10 March 14, 2011 12 Multicast Addresses for Documentation 13 draft-venaas-mboned-mcaddrdoc-03.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 September 15, 2011. 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 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 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, the IPv4 multicast addresses allocated for documentation 102 purposes are TBD. Note that for SSM examples, one will often also 103 want to specify source addresses. In that case the unicast addresses 104 should be addresses reserved for documentation purposes, see 105 [RFC5737]. 107 Sometimes one wants to give examples where a specific type of address 108 is desired. E.g. for text about multicast scoping, one might want 109 the examples to use addresses that are to be used for administrative 110 scoping. See below for guidance on how to construct specific types 111 of example addresses. 113 2.1. Administratively scoped IPv4 multicast addresses 115 Administratively scoped IPv4 multicast addresses [RFC2365] are 116 reserved for scoped multicast. They can be used within a site or an 117 organization. Apart from a small set of scope relative addresses, 118 these addresses are not assigned. There are no specific scoped 119 addresses available for documentation purposes. Except for examples 120 detailing the use of scoped multicast, one should avoid using them. 122 2.2. GLOP multicast addresses 124 GLOP [RFC3180] is a method for deriving IPv4 multicast group 125 addresses from 16 bit AS numbers. For examples where GLOP addresses 126 are desired, the addresses should be derived from the AS numbers 127 reserved for documentation use. See [RFC5398]. 129 2.3. Unicast prefix based IPv4 multicast addresses 131 IPv4 multicast addresses can be derived from IPv4 unicast prefixes, 132 see [RFC6034]. For examples where this type of addresses are 133 desired, the addresses should be derived from the unicast addresses 134 reserved for documentation purposes, see [RFC5737]. 136 3. IPv6 multicast documentation addresses 138 The type of multicast addresses most commonly used today, are 139 addresses used for so-called ASM (Any-Source Multicast). For ASM, 140 the IPv6 multicast addresses allocated for documentation purposes are 141 TBD. 143 Another type of multicast is SSM (Source-Specific Multicast). For 144 SSM, the IPv6 multicast addresses allocated for documentation 145 purposes are TBD. Note that for SSM examples, one will often also 146 want to specify source addresses. In that case the unicast addresses 147 should be addresses reserved for documentation purposes, see 148 [RFC5737]. 150 Sometimes one wants to give examples where a specific type of address 151 is desired. E.g. for text about multicast scoping, one might want 152 the examples to use addresses that are to be used for administrative 153 scoping. See below for guidance on how to construct specific types 154 of example addresses. 156 3.1. Unicast prefix based IPv6 multicast addresses 158 IPv6 multicast addresses can be derived from IPv6 unicast prefixes, 159 see [RFC3306]. For examples where this type of addresses is desired, 160 the addresses should be derived from the unicast addresses reserved 161 for documentation purposes, see [RFC3849]. 163 3.2. Embedded-RP IPv6 multicast addresses 165 There is a type of IPv6 multicast addresses called Embedded-RP 166 addresses where the IPv6 address of a Rendezvous-Point is embedded 167 inside the multicast address, see [RFC3956]. For examples where this 168 type of addresses is desired, the addresses should be derived from 169 the unicast addresses reserved for documentation purposes, see see 170 [RFC3849]. 172 4. Security Considerations 174 The use of specific multicast addresses for documentation purposes 175 has no impact on security. 177 5. IANA Considerations 179 IANA is requested to assign multicast addresses for documentation 180 purposes as follows: 182 2 IPv4 SSM addresses in the Source-Specific Multicast Block 232/8. 184 A set of IPv6 multicast addresses of "variable scope". The set 185 should be a /96 prefix of the form FF0X:... 187 A set of IPv6 SSM addresses in the Source-Specific Multicast Block 188 FF3X:0000:/32. The set should be a /124 prefix. 190 6. Acknowledgments 192 The authors thank Roberta Maglione for providing comments on this 193 document. 195 7. Informative References 197 [RFC2365] Meyer, D., "Administratively Scoped IP Multicast", BCP 23, 198 RFC 2365, July 1998. 200 [RFC3180] Meyer, D. and P. Lothberg, "GLOP Addressing in 233/8", 201 BCP 53, RFC 3180, September 2001. 203 [RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 204 Multicast Addresses", RFC 3306, August 2002. 206 [RFC3307] Haberman, B., "Allocation Guidelines for IPv6 Multicast 207 Addresses", RFC 3307, August 2002. 209 [RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix 210 Reserved for Documentation", RFC 3849, July 2004. 212 [RFC3956] Savola, P. and B. Haberman, "Embedding the Rendezvous 213 Point (RP) Address in an IPv6 Multicast Address", 214 RFC 3956, November 2004. 216 [RFC5398] Huston, G., "Autonomous System (AS) Number Reservation for 217 Documentation Use", RFC 5398, December 2008. 219 [RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks 220 Reserved for Documentation", RFC 5737, January 2010. 222 [RFC6034] Thaler, D., "Unicast-Prefix-Based IPv4 Multicast 223 Addresses", RFC 6034, October 2010. 225 Authors' Addresses 227 Tim Chown 228 University of Southampton 229 Highfield 230 Southampton, Hampshire SO17 1BJ 231 United Kingdom 233 Email: tjc@ecs.soton.ac.uk 235 Marshall Eubanks 236 Iformata Communications 237 130 W. Second Street 238 Dayton, Ohio 45402 239 US 241 Phone: +1 703 501 4376 242 Email: marshall.eubanks@iformata.com 243 URI: http://www.iformata.com/ 245 Rishabh Parekh 246 cisco Systems 247 Tasman Drive 248 San Jose, CA 95134 249 USA 251 Email: riparekh@cisco.com 253 Gunter Van de Velde 254 cisco Systems 255 De Kleetlaan 6a 256 Diegem 1831 257 Belgium 259 Phone: +32 476 476 022 260 Email: gvandeve@cisco.com 261 Stig Venaas 262 cisco Systems 263 Tasman Drive 264 San Jose, CA 95134 265 USA 267 Email: stig@cisco.com