idnits 2.17.1 draft-venaas-mboned-mcaddrdoc-00.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 3, 2010) is 5040 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 M. Eubanks 3 Internet-Draft Iformata Communications 4 Intended status: Informational R. Parekh 5 Expires: January 4, 2011 S. Venaas 6 cisco Systems 7 July 3, 2010 9 Multicast Addresses for Documentation 10 draft-venaas-mboned-mcaddrdoc-00.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 4, 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 Often it is 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, see 70 [RFC5737] and [RFC3849] respectively. There are however no multicast 71 addresses available for such purposes. This document reserves such 72 addresses. 74 There are also some multicast addresses that are derived from AS 75 numbers of unicast addresses. For examples where such addresses are 76 desired, one should derive them from AS numbers and unicast addresses 77 reserved for documentation purposes. This document also lists these. 79 2. Documentation IPv4 and IPv6 multicast addresses 81 For documentation where examples of general purpose multicast 82 addresses are needed, one should use multicast addresses that never 83 will be in actual use. 85 The IPv4 multicast address allocated for documentation purposes is 86 TBD. The IPv6 multicast address allocated for documentation purposes 87 is TBD. 89 3. GLOP multicast addresses 91 GLOP [RFC3180] is a method for deriving IPv4 multicast group 92 addresses from 16 bit AS numbers. For examples where GLOP addresses 93 are desired, the addresses should be derived from the AS numbers 94 reserved for documentation use. See [RFC5398]. 96 4. Unicast prefix based multicast addresses 98 IPv6 multicast addresses can be derived from IPv6 unicast prefixes. 99 The two ways currently defined are unicast-prefix based addresses 100 [RFC3306] and Embedded-RP addresses [RFC3956]. There is also a 101 proposal for doing this with IPv4 102 [I-D.ietf-mboned-ipv4-uni-based-mcast]. For examples where these 103 types of addresses are desired, the addresses should be derived from 104 unicast addresses reserved for documentation purposes. For IPv4, see 105 [RFC5737]. For IPv6, see [RFC3849]. 107 5. Other multicast addresses 109 For both IPv4 and IPv6, multicast address ranges have been defined 110 for link-local, SSM, admin scoped etc. It may be considered to 111 reserve a multicast address from these ranges for the purpose of 112 documentation. For IPv6 this can be done by assigning a Group ID, 113 see [RFC3307]. 115 6. Security Considerations 117 The use of specific multicast addresses for documentation purposes 118 has no impact on security. 120 7. IANA Considerations 122 IANA is requested to assign both an IPv4 multicast address and an 123 IPv6 multicast address for documentation purposes. 125 8. Informative References 127 [I-D.ietf-mboned-ipv4-uni-based-mcast] 128 Thaler, D., "Unicast-Prefix-based IPv4 Multicast 129 Addresses", draft-ietf-mboned-ipv4-uni-based-mcast-06 130 (work in progress), April 2010. 132 [RFC3180] Meyer, D. and P. Lothberg, "GLOP Addressing in 233/8", 133 BCP 53, RFC 3180, September 2001. 135 [RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 136 Multicast Addresses", RFC 3306, August 2002. 138 [RFC3307] Haberman, B., "Allocation Guidelines for IPv6 Multicast 139 Addresses", RFC 3307, August 2002. 141 [RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix 142 Reserved for Documentation", RFC 3849, July 2004. 144 [RFC3956] Savola, P. and B. Haberman, "Embedding the Rendezvous 145 Point (RP) Address in an IPv6 Multicast Address", 146 RFC 3956, November 2004. 148 [RFC5398] Huston, G., "Autonomous System (AS) Number Reservation for 149 Documentation Use", RFC 5398, December 2008. 151 [RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks 152 Reserved for Documentation", RFC 5737, January 2010. 154 Authors' Addresses 156 Marshall Eubanks 157 Iformata Communications 159 Email: tme@multicasttech.com 161 Rishabh Parekh 162 cisco Systems 163 Tasman Drive 164 San Jose, CA 95134 165 USA 167 Email: riparekh@cisco.com 169 Stig Venaas 170 cisco Systems 171 Tasman Drive 172 San Jose, CA 95134 173 USA 175 Email: stig@cisco.com