idnits 2.17.1 draft-venaas-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 : ---------------------------------------------------------------------------- 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 (July 13, 2010) is 5036 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group T. Eubanks 3 Internet-Draft Iformata Communications 4 Intended status: Informational R. Parekh 5 Expires: January 14, 2011 S. Venaas 6 cisco Systems 7 July 13, 2010 9 Multicast Addresses for Documentation 10 draft-venaas-mboned-mcaddrdoc-01.txt 12 Abstract 14 This document reserves IPv4 and IPv6 multicast addresses for use in 15 documentation, RFCs etc. Some multicast addresses are derived from 16 AS numbers or unicast addresses. This document also explains how 17 these can be used for documentation purposes by deriving them from AS 18 numbers and unicast addresses that are reserved for such purposes. 20 Status of this Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on January 14, 2011. 37 Copyright Notice 39 Copyright (c) 2010 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 2. Documentation IPv4 and IPv6 multicast addresses . . . . . . . 4 56 3. GLOP multicast addresses . . . . . . . . . . . . . . . . . . . 5 57 4. Unicast prefix based multicast addresses . . . . . . . . . . . 6 58 5. Other multicast addresses . . . . . . . . . . . . . . . . . . 7 59 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8 60 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 61 8. Informative References . . . . . . . . . . . . . . . . . . . . 10 62 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 64 1. Introduction 66 It is often useful in documentation to give examples containing IP 67 multicast addresses. To prevent conflicts or confusion, one should 68 avoid using multicast addresses that may be in actual use. For 69 unicast there are both IPv4 and IPv6 addresses reserved for this 70 purpose, see [RFC5737] and [RFC3849] respectively. There are however 71 no multicast addresses available for such purposes. This document 72 reserves such addresses. 74 There are also some multicast addresses that are derived from AS 75 numbers or unicast addresses. For examples where such addresses are 76 desired, one should derive them from the AS numbers and unicast 77 addresses reserved for documentation purposes. This document also 78 discusses the use of these. 80 2. Documentation IPv4 and IPv6 multicast addresses 82 For documentation where examples of general purpose multicast 83 addresses are needed, one should use multicast addresses that never 84 will be assigned or in actual use. There is a risk that addresses 85 used in examples may accidentally be used. It is then important that 86 the same addresses are not used by other multicast applications or 87 services. It may also be beneficial to filter out such addresses 88 from multicast signalling and multicast data sent to such addresses. 90 The IPv4 multicast address allocated for documentation purposes is 91 TBD. The IPv6 multicast address allocated for documentation purposes 92 is TBD. 94 3. GLOP multicast addresses 96 GLOP [RFC3180] is a method for deriving IPv4 multicast group 97 addresses from 16 bit AS numbers. For examples where GLOP addresses 98 are desired, the addresses should be derived from the AS numbers 99 reserved for documentation use. See [RFC5398]. 101 4. Unicast prefix based multicast addresses 103 IPv6 multicast addresses can be derived from IPv6 unicast prefixes. 104 The two ways currently defined are unicast-prefix based addresses 105 [RFC3306] and Embedded-RP addresses [RFC3956]. There is also a 106 proposal for doing this with IPv4 107 [I-D.ietf-mboned-ipv4-uni-based-mcast]. For examples where these 108 types of addresses are desired, the addresses should be derived from 109 the unicast addresses reserved for documentation purposes. For IPv4, 110 see [RFC5737]. For IPv6, see [RFC3849]. 112 5. Other multicast addresses 114 For both IPv4 and IPv6, multicast address ranges have been defined 115 for link-local, SSM, admin scoped etc. It may be considered to 116 reserve a multicast address from these ranges for the purpose of 117 documentation. For IPv6 this can be done by assigning a Group ID, 118 see [RFC3307]. The question here is how common it is that examples 119 require a multicast address of a particular non-global scope. 121 6. Security Considerations 123 The use of specific multicast addresses for documentation purposes 124 has no impact on security. 126 7. IANA Considerations 128 IANA is requested to assign both an IPv4 multicast address and an 129 IPv6 multicast address for documentation purposes. 131 8. Informative References 133 [I-D.ietf-mboned-ipv4-uni-based-mcast] 134 Thaler, D., "Unicast-Prefix-based IPv4 Multicast 135 Addresses", draft-ietf-mboned-ipv4-uni-based-mcast-06 136 (work in progress), April 2010. 138 [RFC3180] Meyer, D. and P. Lothberg, "GLOP Addressing in 233/8", 139 BCP 53, RFC 3180, September 2001. 141 [RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 142 Multicast Addresses", RFC 3306, August 2002. 144 [RFC3307] Haberman, B., "Allocation Guidelines for IPv6 Multicast 145 Addresses", RFC 3307, August 2002. 147 [RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix 148 Reserved for Documentation", RFC 3849, July 2004. 150 [RFC3956] Savola, P. and B. Haberman, "Embedding the Rendezvous 151 Point (RP) Address in an IPv6 Multicast Address", 152 RFC 3956, November 2004. 154 [RFC5398] Huston, G., "Autonomous System (AS) Number Reservation for 155 Documentation Use", RFC 5398, December 2008. 157 [RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks 158 Reserved for Documentation", RFC 5737, January 2010. 160 Authors' Addresses 162 T.M. Eubanks 163 Iformata Communications 164 130 W. Second Street 165 Dayton, Ohio 45402 166 US 168 Phone: +1 703 501 4376 169 Email: marshall.eubanks@iformata.com 170 URI: http://www.iformata.com/ 172 Rishabh Parekh 173 cisco Systems 174 Tasman Drive 175 San Jose, CA 95134 176 USA 178 Email: riparekh@cisco.com 180 Stig Venaas 181 cisco Systems 182 Tasman Drive 183 San Jose, CA 95134 184 USA 186 Email: stig@cisco.com