idnits 2.17.1 draft-venaas-mboned-mcaddrdoc-04.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 (April 6, 2011) is 4767 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC3307' is defined on line 197, 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: October 8, 2011 Iformata Communications 6 R. Parekh 7 G. Van de Velde 8 S. Venaas 9 cisco Systems 10 April 6, 2011 12 Multicast Addresses for Documentation 13 draft-venaas-mboned-mcaddrdoc-04.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 October 8, 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 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, see [RFC5737]. 106 Sometimes one wants to give examples where a specific type of address 107 is desired. E.g. for text about multicast scoping, one might want 108 the examples to use addresses that are to be used for administrative 109 scoping. See below for guidance on how to construct specific types 110 of example addresses. 112 2.1. Administratively scoped IPv4 multicast addresses 114 Administratively scoped IPv4 multicast addresses [RFC2365] are 115 reserved for scoped multicast. They can be used within a site or an 116 organization. Apart from a small set of scope relative addresses, 117 these addresses are not assigned. There are no specific scoped 118 addresses available for documentation purposes. Except for examples 119 detailing the use of scoped multicast, one should avoid using them. 121 2.2. GLOP multicast addresses 123 GLOP [RFC3180] is a method for deriving IPv4 multicast group 124 addresses from 16 bit AS numbers. For examples where GLOP addresses 125 are desired, the addresses should be derived from the AS numbers 126 reserved for documentation use. See [RFC5398]. 128 2.3. Unicast prefix based IPv4 multicast addresses 130 IPv4 multicast addresses can be derived from IPv4 unicast prefixes, 131 see [RFC6034]. For examples where this type of addresses are 132 desired, the addresses should be derived from the unicast addresses 133 reserved for documentation purposes, see [RFC5737]. 135 3. IPv6 multicast documentation addresses 137 The type of multicast addresses most commonly used today, are 138 addresses used for so-called ASM (Any-Source Multicast). For ASM, 139 the IPv6 multicast addresses allocated for documentation purposes are 140 TBD. 142 Another type of multicast is SSM (Source-Specific Multicast). For 143 SSM it is less important which multicast addresses are used, since a 144 host/application joins a channel identified by both source and group. 145 Any source addresses used in SSM examples should be unicast addresses 146 reserved for documentation purposes, see [RFC3849]. 148 Sometimes one wants to give examples where a specific type of address 149 is desired. E.g. for text about multicast scoping, one might want 150 the examples to use addresses that are to be used for administrative 151 scoping. See below for guidance on how to construct specific types 152 of example addresses. 154 3.1. Unicast prefix based IPv6 multicast addresses 156 IPv6 multicast addresses can be derived from IPv6 unicast prefixes, 157 see [RFC3306]. For examples where this type of addresses is desired, 158 the addresses should be derived from the unicast addresses reserved 159 for documentation purposes, see [RFC3849]. 161 3.2. Embedded-RP IPv6 multicast addresses 163 There is a type of IPv6 multicast addresses called Embedded-RP 164 addresses where the IPv6 address of a Rendezvous-Point is embedded 165 inside the multicast address, see [RFC3956]. For examples where this 166 type of addresses is desired, the addresses should be derived from 167 the unicast addresses reserved for documentation purposes, see see 168 [RFC3849]. 170 4. Security Considerations 172 The use of specific multicast addresses for documentation purposes 173 has no impact on security. 175 5. IANA Considerations 177 IANA is requested to assign "variable scope" IPv6 multicast addresses 178 for documentation purposes. This should be a /96 prefix of the form 179 FF0X:... 181 6. Acknowledgments 183 The authors thank Roberta Maglione for providing comments on this 184 document. 186 7. Informative References 188 [RFC2365] Meyer, D., "Administratively Scoped IP Multicast", BCP 23, 189 RFC 2365, July 1998. 191 [RFC3180] Meyer, D. and P. Lothberg, "GLOP Addressing in 233/8", 192 BCP 53, RFC 3180, September 2001. 194 [RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 195 Multicast Addresses", RFC 3306, August 2002. 197 [RFC3307] Haberman, B., "Allocation Guidelines for IPv6 Multicast 198 Addresses", RFC 3307, August 2002. 200 [RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix 201 Reserved for Documentation", RFC 3849, July 2004. 203 [RFC3956] Savola, P. and B. Haberman, "Embedding the Rendezvous 204 Point (RP) Address in an IPv6 Multicast Address", 205 RFC 3956, November 2004. 207 [RFC5398] Huston, G., "Autonomous System (AS) Number Reservation for 208 Documentation Use", RFC 5398, December 2008. 210 [RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks 211 Reserved for Documentation", RFC 5737, January 2010. 213 [RFC6034] Thaler, D., "Unicast-Prefix-Based IPv4 Multicast 214 Addresses", RFC 6034, October 2010. 216 Authors' Addresses 218 Tim Chown 219 University of Southampton 220 Highfield 221 Southampton, Hampshire SO17 1BJ 222 United Kingdom 224 Email: tjc@ecs.soton.ac.uk 226 Marshall Eubanks 227 Iformata Communications 228 130 W. Second Street 229 Dayton, Ohio 45402 230 US 232 Phone: +1 703 501 4376 233 Email: marshall.eubanks@iformata.com 234 URI: http://www.iformata.com/ 236 Rishabh Parekh 237 cisco Systems 238 Tasman Drive 239 San Jose, CA 95134 240 USA 242 Email: riparekh@cisco.com 244 Gunter Van de Velde 245 cisco Systems 246 De Kleetlaan 6a 247 Diegem 1831 248 Belgium 250 Phone: +32 476 476 022 251 Email: gvandeve@cisco.com 252 Stig Venaas 253 cisco Systems 254 Tasman Drive 255 San Jose, CA 95134 256 USA 258 Email: stig@cisco.com