idnits 2.17.1 draft-venaas-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 : ---------------------------------------------------------------------------- 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 (October 25, 2010) is 4930 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC3307' is defined on line 155, 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 M. Eubanks 3 Internet-Draft Iformata Communications 4 Intended status: Informational R. Parekh 5 Expires: April 28, 2011 S. Venaas 6 cisco Systems 7 October 25, 2010 9 Multicast Addresses for Documentation 10 draft-venaas-mboned-mcaddrdoc-02.txt 12 Abstract 14 This document discusses which multicast addresses should be used for 15 documentation purposes and reserves IPv6 multicast addresses for such 16 use. Some multicast addresses are derived from AS numbers or unicast 17 addresses. This document also explains how these can be used for 18 documentation purposes by deriving them from AS numbers and unicast 19 addresses that are reserved for such purposes. 21 Status of this Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on April 28, 2011. 38 Copyright Notice 40 Copyright (c) 2010 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 2. Documentation IPv4 and IPv6 multicast addresses . . . . . . . 4 57 3. Administratively scoped IPv4 multicast addresses . . . . . . . 5 58 4. GLOP multicast addresses . . . . . . . . . . . . . . . . . . . 6 59 5. Unicast prefix based multicast addresses . . . . . . . . . . . 7 60 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8 61 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 62 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 63 9. Informative References . . . . . . . . . . . . . . . . . . . . 11 64 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 66 1. Introduction 68 It is often useful in documentation, IETF documents, etc., to provide 69 examples containing IP multicast addresses. To prevent conflicts or 70 confusion, one should avoid using multicast addresses that may be in 71 actual use. For unicast there are both IPv4 and IPv6 addresses 72 reserved for this purpose, see [RFC5737] and [RFC3849] respectively. 73 There are IPv4 multicast addresses reserved for this purpose, and 74 this document reserves such IPv6 multicast addresses. 76 There are also some multicast addresses that are derived from AS 77 numbers or unicast addresses. For examples where such addresses are 78 desired, one should derive them from the AS numbers and unicast 79 addresses reserved for documentation purposes. This document also 80 discusses the use of these. 82 2. Documentation IPv4 and IPv6 multicast addresses 84 For documentation where examples of general purpose multicast 85 addresses are needed, one should use multicast addresses that never 86 will be assigned or in actual use. There is a risk that addresses 87 used in examples may accidentally be used. It is then important that 88 the same addresses are not used by other multicast applications or 89 services. It may also be beneficial to filter out such addresses 90 from multicast signalling and multicast data sent to such addresses. 92 The IPv4 multicast addresses allocated for documentation purposes are 93 233.252.0.0 - 233.252.0.255 (233.252.0.0/24). The IPv6 multicast 94 addresses allocated for documentation purposes are TBD. 96 3. Administratively scoped IPv4 multicast addresses 98 Administratively scoped IPv4 multicast addresses [RFC2365] are 99 reserved for scoped multicast. They can be used within a site or an 100 organization. Apart from a small set of scope relative addresses, 101 these addresses are not assigned. There are no specific scoped 102 addresses available for documentation purposes. Except for examples 103 detailing the use of scoped multicast, one should avoid using them. 105 4. GLOP multicast addresses 107 GLOP [RFC3180] is a method for deriving IPv4 multicast group 108 addresses from 16 bit AS numbers. For examples where GLOP addresses 109 are desired, the addresses should be derived from the AS numbers 110 reserved for documentation use. See [RFC5398]. 112 5. Unicast prefix based multicast addresses 114 IPv6 multicast addresses can be derived from IPv6 unicast prefixes. 115 The two ways currently defined are unicast-prefix based addresses 116 [RFC3306] and Embedded-RP addresses [RFC3956]. There is also a 117 proposal for doing this with IPv4 118 [I-D.ietf-mboned-ipv4-uni-based-mcast]. For examples where these 119 types of addresses are desired, the addresses should be derived from 120 the unicast addresses reserved for documentation purposes. For IPv4, 121 see [RFC5737]. For IPv6, see [RFC3849]. 123 6. Security Considerations 125 The use of specific multicast addresses for documentation purposes 126 has no impact on security. 128 7. IANA Considerations 130 IANA is requested to assign a set of IPv6 multicast addresses of 131 "variable scope" for documentation purposes. The set should be a /96 132 prefix of the form FF0X:... 134 8. Acknowledgments 136 The authors thank Roberta Maglione for providing comments on this 137 document. 139 9. Informative References 141 [I-D.ietf-mboned-ipv4-uni-based-mcast] 142 Thaler, D., "Unicast-Prefix-based IPv4 Multicast 143 Addresses", draft-ietf-mboned-ipv4-uni-based-mcast-06 144 (work in progress), April 2010. 146 [RFC2365] Meyer, D., "Administratively Scoped IP Multicast", BCP 23, 147 RFC 2365, July 1998. 149 [RFC3180] Meyer, D. and P. Lothberg, "GLOP Addressing in 233/8", 150 BCP 53, RFC 3180, September 2001. 152 [RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 153 Multicast Addresses", RFC 3306, August 2002. 155 [RFC3307] Haberman, B., "Allocation Guidelines for IPv6 Multicast 156 Addresses", RFC 3307, August 2002. 158 [RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix 159 Reserved for Documentation", RFC 3849, July 2004. 161 [RFC3956] Savola, P. and B. Haberman, "Embedding the Rendezvous 162 Point (RP) Address in an IPv6 Multicast Address", 163 RFC 3956, November 2004. 165 [RFC5398] Huston, G., "Autonomous System (AS) Number Reservation for 166 Documentation Use", RFC 5398, December 2008. 168 [RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks 169 Reserved for Documentation", RFC 5737, January 2010. 171 Authors' Addresses 173 Marshall Eubanks 174 Iformata Communications 175 130 W. Second Street 176 Dayton, Ohio 45402 177 US 179 Phone: +1 703 501 4376 180 Email: marshall.eubanks@iformata.com 181 URI: http://www.iformata.com/ 183 Rishabh Parekh 184 cisco Systems 185 Tasman Drive 186 San Jose, CA 95134 187 USA 189 Email: riparekh@cisco.com 191 Stig Venaas 192 cisco Systems 193 Tasman Drive 194 San Jose, CA 95134 195 USA 197 Email: stig@cisco.com