idnits 2.17.1 draft-ietf-mboned-mcast-arpa-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 (Using the creation date from RFC5771, updated by this document, for RFC5378 checks: 2003-11-24) -- The document seems to contain a disclaimer for pre-RFC5378 work, and may have content which was first submitted before 10 November 2008. The disclaimer is necessary when there are original authors that you have been unable to contact, or if some do not wish to grant the BCP78 rights to the IETF Trust. If you are able to get all authors (current and original) to grant those rights, you can and should remove the disclaimer; otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (July 5, 2011) is 4680 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC1034' is defined on line 248, but no explicit reference was found in the text == Unused Reference: 'RFC1035' is defined on line 251, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-mboned-addrarch' is defined on line 286, but no explicit reference was found in the text == Unused Reference: 'RFC2780' is defined on line 294, but no explicit reference was found in the text == Unused Reference: 'RFC2908' is defined on line 298, but no explicit reference was found in the text ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) ** Downref: Normative reference to an Informational RFC: RFC 6308 -- Obsolete informational reference (is this intentional?): RFC 2672 (Obsoleted by RFC 6672) -- Obsolete informational reference (is this intentional?): RFC 2908 (Obsoleted by RFC 6308) Summary: 2 errors (**), 0 flaws (~~), 6 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group P. Koch 3 Internet-Draft DENIC eG 4 Updates: 5771 (if approved) L. Vegoda 5 Intended status: BCP ICANN 6 Expires: January 6, 2012 July 5, 2011 8 Moving MCAST.NET into the ARPA infrastructure top level domain 9 draft-ietf-mboned-mcast-arpa-03 11 Abstract 13 This document proposes to migrate the MCAST.NET domain into the ARPA 14 top level domain, which is dedicated to infrastructure support. It 15 also provides a maintenance policy for the new MCAST.ARPA domain, 16 related registrations in IN-ADDR.ARPA and describes the migration 17 process. This document updates RFC 5771 and forms part of BCP 51. 19 Status of this Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on January 6, 2012. 36 Copyright Notice 38 Copyright (c) 2011 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 This document may contain material from IETF Documents or IETF 52 Contributions published or made publicly available before November 53 10, 2008. The person(s) controlling the copyright in some of this 54 material may not have granted the IETF Trust the right to allow 55 modifications of such material outside the IETF Standards Process. 56 Without obtaining an adequate license from the person(s) controlling 57 the copyright in such materials, this document may not be modified 58 outside the IETF Standards Process, and derivative works of it may 59 not be created outside the IETF Standards Process, except to format 60 it for publication as an RFC or to translate it into languages other 61 than English. 63 Table of Contents 65 1. Introduction . . . . . . . . . . . . . . . . . . . . . 3 66 2. Terminology . . . . . . . . . . . . . . . . . . . . . . 3 67 3. The ARPA top level domain . . . . . . . . . . . . . . . 3 68 4. Current Use . . . . . . . . . . . . . . . . . . . . . . 3 69 5. Registration Policy . . . . . . . . . . . . . . . . . . 3 70 5.1. Names and Addresses eligible for Registration in 71 MCAST.ARPA . . . . . . . . . . . . . . . . . . . . . . 4 72 5.2. Subdomains of MCAST.ARPA . . . . . . . . . . . . . . . 4 73 5.3. Corresponding Reverse Mapping . . . . . . . . . . . . . 4 74 5.3.1. Reverse Mapping for 224/4 . . . . . . . . . . . . . . . 4 75 5.3.2. Reverse Mapping for ff00::/8 . . . . . . . . . . . . . 4 76 6. Migration Issues . . . . . . . . . . . . . . . . . . . 5 77 6.1. Migration Strategies . . . . . . . . . . . . . . . . . 5 78 6.1.1. Freeze . . . . . . . . . . . . . . . . . . . . . . . . 5 79 6.1.2. Removing Registrations from MCAST.NET while 80 maintaining operational stability . . . . . . . . . . . 5 81 7. Security Considerations . . . . . . . . . . . . . . . . 5 82 8. IANA Considerations . . . . . . . . . . . . . . . . . . 6 83 9. Acknowledgements . . . . . . . . . . . . . . . . . . . 6 84 10. References . . . . . . . . . . . . . . . . . . . . . . 6 85 10.1. Normative References . . . . . . . . . . . . . . . . . 6 86 10.2. Informative References . . . . . . . . . . . . . . . . 7 87 Appendix A. Document Revision History . . . . . . . . . . . . . . . 7 88 A.1. Changes from -2 to -03 . . . . . . . . . . . . . . . . 7 89 A.2. Changes from -01 to -02 . . . . . . . . . . . . . . . . 8 90 A.3. Changes from -00 to -01 . . . . . . . . . . . . . . . . 8 91 A.4. Initial Document . . . . . . . . . . . . . . . . . . . 8 92 Authors' Addresses . . . . . . . . . . . . . . . . . . 8 94 1. Introduction 96 This document describes the migration strategy from the MCAST.NET 97 domain to MCAST.ARPA, which MUST contains DNS names for a subset of 98 the multicast groups assigned by the IANA. It also specifies a 99 maintenance policy for the MCAST.ARPA domain. 101 2. Terminology 103 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 104 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 105 document are to be interpreted as described in BCP 14, [RFC2119]. 107 3. The ARPA top level domain 109 [RFC3172] designates the ARPA top level domain as "Address and 110 Routing Parameters Area" to be used for infrastructure applications. 112 The MCAST.NET second level domain fulfills the criteria set out in 113 section 2.1 of [RFC3172]. However, there is no standards track 114 document explicitly designating this domain to a multicast group name 115 to multicast group address mapping. 117 The assignment of IPv4 multicast addresses is governed by BCP51 118 [RFC5771]. IPv6 multicast address assignment is dealt with in 119 [RFC3307] and section 2.7 of [RFC4291]. 121 4. Current Use 123 Currently the zone MCAST.NET reflects the contents of parts the IANA 124 IPv4 multicast address registry. However, some names are missing 125 from the DNS zone and some names used differ from the description 126 that appears in the registry file. Entries in the IPv6 multicast 127 address registry are not reflected in the MCAST.NET zone. 129 With few exceptions, only multicast group addresses from 224.0.0/24 130 and 224.0.1/24 are listed in MCAST.NET. Addresses outside 224/8 do 131 not appear at all. 133 5. Registration Policy 135 Names within MCAST.ARPA will consist of one additional label and MUST 136 adhere to the hostname syntax requirements of [RFC1123]. These names 137 MUST own a single A RR, a single AAAA RR, or both. Addresses will be 138 in the IPv4 or IPv6 multicast address space and recorded in the 139 registry. 141 5.1. Names and Addresses eligible for Registration in MCAST.ARPA 143 Only IANA multicast address registrations are eligible for being 144 listed in MCAST.ARPA. 146 For IPv4, only multicast groups from 224.0.0/24 (Local Network 147 Control Block) and 224.0.1/24 (Internetwork Control Block) will have 148 names assigned. 150 For IPv6, only multicast groups from FF01::/16 (Node-Local Scope 151 Multicast Addresses) and FF02::/16 (Link-Local Scope Multicast 152 Addresses) will have names assigned. 154 5.2. Subdomains of MCAST.ARPA 156 The namespace under MCAST.ARPA is considered flat, i.e., all direct 157 descendants of MCAST.ARPA are leaves in the DNS tree. Future 158 extensions might want to define subdomains that serve special 159 purposes. Any such designation needs IETF consensus [RFC5226]. 161 5.3. Corresponding Reverse Mapping 163 The DNS Reverse Mapping for those multicast groups that appear as 164 addresses in MCAST.ARPA MUST remain consistent with the forward 165 namespace. 167 5.3.1. Reverse Mapping for 224/4 169 A single DNS PTR record will be entered at the corresponding owner 170 within the 224.IN-ADDR.ARPA domain that points to the multicast group 171 name within MCAST.ARPA. 173 The zones 225.IN-ADDR.ARPA through 239.IN-ADDR.ARPA will be delegated 174 but MUST remain empty except for necessary infrastructure RRs. The 175 one exception is 233.IN-ADDR.ARPA. A mechanism for the delegation of 176 reverse mapping for GLOP space [RFC3180] will be specified and 177 documented on the IANA web site. 179 5.3.2. Reverse Mapping for ff00::/8 181 Directions for this will be published as a separate document. 183 6. Migration Issues 185 As described below, the current content of the MCAST.NET zone MUST be 186 brought in line with the multicast address registry. 188 Since legacy systems are likely to use MCAST.NET for quite some time, 189 there needs to be a mapping/forwarding solution to answer those 190 queries in a useful manner without discouraging migration. 192 RFCs mentioning MCAST.NET are [RFC3261] and [RFC3678]. 194 An updated multicast address architecture appears in [RFC6308]. 196 6.1. Migration Strategies 198 After the move, several options are available for the future handling 199 of MCAST.NET. 201 [[The working group needs to choose one of the options.]] 203 6.1.1. Freeze 205 The current MCAST.NET zone could be frozen, so that no additions, 206 deletions or changes to the content (apart from those necessary for 207 maintenance, e.g. SOA and NS RRs) would be performed. New 208 registrations would only be available in MCAST.ARPA, so this could be 209 an incentive for querying clients to alter their behavior as well. 211 6.1.2. Removing Registrations from MCAST.NET while maintaining 212 operational stability 214 MCAST.NET will only see deletions but even after the last record has 215 been deleted, the domain MUST be kept registered by the IANA. and 216 should be operated in parallel using a DNAME RR, as described in 217 [RFC2672]. 219 7. Security Considerations 221 The usual Security Considerations for the DNS [RFC3833] apply. 223 The MCAST.ARPA., MCAST.NET., and the Reverse mapping zones mentioned 224 in this document MUST be DNSSEC signed by the IANA under direction 225 from the IAB. 227 There is no security problem associated with the migration itself. 229 {This section needs more work.} 231 8. IANA Considerations 233 This document amends [RFC5771] to add a mandatory entry in the 234 MCAST.ARPA domain and a corresponding reverse mapping entry, with 235 relevant DNS names published in the registry. The officially 236 registered multicast group name is made subject to DNS hostname 237 syntax rules. 239 9. Acknowledgements 241 The authors would like to thank David Conrad and Joe Abley for their 242 input. 244 10. References 246 10.1. Normative References 248 [RFC1034] Mockapetris, P., "Domain names - concepts and facilities", 249 STD 13, RFC 1034, November 1987. 251 [RFC1035] Mockapetris, P., "Domain names - implementation and 252 specification", STD 13, RFC 1035, November 1987. 254 [RFC1123] Braden, R., "Requirements for Internet Hosts - Application 255 and Support", STD 3, RFC 1123, October 1989. 257 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 258 Requirement Levels", BCP 14, RFC 2119, March 1997. 260 [RFC3172] Huston, G., "Management Guidelines & Operational 261 Requirements for the Address and Routing Parameter Area 262 Domain ("arpa")", BCP 52, RFC 3172, September 2001. 264 [RFC3180] Meyer, D. and P. Lothberg, "GLOP Addressing in 233/8", 265 BCP 53, RFC 3180, September 2001. 267 [RFC3307] Haberman, B., "Allocation Guidelines for IPv6 Multicast 268 Addresses", RFC 3307, August 2002. 270 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 271 Architecture", RFC 4291, February 2006. 273 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 274 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 275 May 2008. 277 [RFC5771] Cotton, M., Vegoda, L., and D. Meyer, "IANA Guidelines for 278 IPv4 Multicast Address Assignments", BCP 51, RFC 5771, 279 March 2010. 281 [RFC6308] Savola, P., "Overview of the Internet Multicast Addressing 282 Architecture", RFC 6308, June 2011. 284 10.2. Informative References 286 [I-D.ietf-mboned-addrarch] 287 Savola, P., "Overview of the Internet Multicast Addressing 288 Architecture", draft-ietf-mboned-addrarch-07 (work in 289 progress), October 2010. 291 [RFC2672] Crawford, M., "Non-Terminal DNS Name Redirection", 292 RFC 2672, August 1999. 294 [RFC2780] Bradner, S. and V. Paxson, "IANA Allocation Guidelines For 295 Values In the Internet Protocol and Related Headers", 296 BCP 37, RFC 2780, March 2000. 298 [RFC2908] Thaler, D., Handley, M., and D. Estrin, "The Internet 299 Multicast Address Allocation Architecture", RFC 2908, 300 September 2000. 302 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 303 A., Peterson, J., Sparks, R., Handley, M., and E. 304 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 305 June 2002. 307 [RFC3678] Thaler, D., Fenner, B., and B. Quinn, "Socket Interface 308 Extensions for Multicast Source Filters", RFC 3678, 309 January 2004. 311 [RFC3833] Atkins, D. and R. Austein, "Threat Analysis of the Domain 312 Name System (DNS)", RFC 3833, August 2004. 314 Appendix A. Document Revision History 316 This section is to be removed should the draft be published. 318 A.1. Changes from -2 to -03 320 Added text on reverse delegation to the abstract 322 Updated the order of text in the introduction 323 Added a requirements to publish DNS names in the assignment registry 324 in section 5 326 Consigned ff0::/12 reverse delegation issues to a separate document 328 Merged 6.1.2 and 6.1.3 with updated text 330 A.2. Changes from -01 to -02 332 Added text about v6 multicast. 334 Added text about GLOP space 336 Added terminology section and RFC 2119 language 338 A.3. Changes from -00 to -01 340 Added text about DNS reverse mapping. Eligibility for an MCAST.ARPA 341 name now restricted to 224.0.0/24 and 224.0.1/24. Stronger 342 requirement for MCAST.ARPA subdomains. 344 A.4. Initial Document 346 First draft, taking over with only little changes from 347 draft-koch-mboned-mcast-arpa-00.txt 349 Authors' Addresses 351 Peter Koch 352 DENIC eG 353 Kaiserstrasse 75-77 354 Frankfurt 60329 355 DE 357 Phone: +49 69 27235 0 358 Email: pk@DENIC.DE 359 Leo Vegoda 360 Internet Corporation for Assigned Names and Numbers 361 4676 Admiralty Way, Suite 330 362 Marina del Rey 90292 363 United States of America 365 Phone: +1-310-823-9358 366 Email: leo.vegoda@icann.org 367 URI: http://www.iana.org/