idnits 2.17.1 draft-ietf-mboned-mcast-arpa-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 16. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 288. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 299. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 306. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 312. 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 : ---------------------------------------------------------------------------- -- The abstract seems to indicate that this document updates RFC3171, but the header doesn't have an 'Updates:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (July 9, 2007) is 6130 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 203, but no explicit reference was found in the text == Unused Reference: 'RFC1035' is defined on line 206, but no explicit reference was found in the text == Unused Reference: 'RFC2780' is defined on line 231, but no explicit reference was found in the text == Unused Reference: 'RFC2908' is defined on line 235, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2434 (Obsoleted by RFC 5226) ** Obsolete normative reference: RFC 3171 (Obsoleted by RFC 5771) == Outdated reference: A later version (-07) exists of draft-ietf-mboned-addrarch-05 -- Obsolete informational reference (is this intentional?): RFC 2908 (Obsoleted by RFC 6308) Summary: 3 errors (**), 0 flaws (~~), 6 warnings (==), 9 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 Intended status: Best Current July 9, 2007 5 Practice 6 Expires: January 10, 2008 8 Moving MCAST.NET into the ARPA infrastructure top level domain 9 draft-ietf-mboned-mcast-arpa-01 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on January 10, 2008. 36 Copyright Notice 38 Copyright (C) The IETF Trust (2007). 40 Abstract 42 This document proposes to migrate the MCAST.NET domain into the ARPA 43 top level domain that is dedicated to infrastructure support. It 44 also provides for a maintenance policy and covers migration issues 45 and caveats. This document updates RFC 3171. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . 3 50 1.1. The ARPA top level domain . . . . . . . . . . . . . . . 3 51 2. Current Use . . . . . . . . . . . . . . . . . . . . . . 3 52 3. Registration Policy . . . . . . . . . . . . . . . . . . 3 53 3.1. Names and Addresses eligible for Registration in 54 MCAST.ARPA . . . . . . . . . . . . . . . . . . . . . . 3 55 3.2. Subdomains of MCAST.ARPA . . . . . . . . . . . . . . . 4 56 3.3. Corresponding Reverse Mapping . . . . . . . . . . . . . 4 57 4. Migration Issues . . . . . . . . . . . . . . . . . . . 4 58 4.1. Migration Strategies . . . . . . . . . . . . . . . . . 4 59 4.1.1. Freeze . . . . . . . . . . . . . . . . . . . . . . . . 4 60 4.1.2. Phase Out . . . . . . . . . . . . . . . . . . . . . . . 5 61 4.1.3. Continue . . . . . . . . . . . . . . . . . . . . . . . 5 62 5. Security Considerations . . . . . . . . . . . . . . . . 5 63 6. IANA Considerations . . . . . . . . . . . . . . . . . . 5 64 7. Acknowledgements . . . . . . . . . . . . . . . . . . . 5 65 8. References . . . . . . . . . . . . . . . . . . . . . . 5 66 8.1. Normative References . . . . . . . . . . . . . . . . . 5 67 8.2. Informative References . . . . . . . . . . . . . . . . 6 68 Appendix A. Document Revision History . . . . . . . . . . . . . . . 6 69 A.1. Changes from -00 to -01 . . . . . . . . . . . . . . . . 6 70 A.2. Initial Document . . . . . . . . . . . . . . . . . . . 7 71 Author's Address . . . . . . . . . . . . . . . . . . . 7 72 Intellectual Property and Copyright Statements . . . . 8 74 1. Introduction 76 This document describes a maintenance policy and migration strategy 77 for the MCAST.NET (MCAST.ARPA) domain that contains names for a 78 subset of the multicast groups assigned by the IANA. 80 Comments should be sent to the mboned working group. 82 1.1. The ARPA top level domain 84 [RFC3172] designates the ARPA top level domain as "Address and 85 Routing Parameters Area" to be used for infrastructure applications. 87 The MCAST.NET second level domain fulfills the criteria layed out in 88 section 2.1 of [RFC3172]. However, there is no standards track 89 document explicitly designating this domain to a multicast group name 90 to multicast group address mapping. 92 [RFC3171] defines the multicast address assignment policy. 94 2. Current Use 96 Currently the zone MCAST.NET reflects the contents of the IANA 97 multicast address registry. However, some names are missing from the 98 DNS zone and some names used differ from the description that appears 99 in the registry file. 101 With few exceptions, only multicast group addresses from 224.0.0/24 102 and 224.0.1/24 are listed in MCAST.NET. Addresses outside 224/8 do 103 not appear at all. 105 3. Registration Policy 107 Names within MCAST.ARPA will consist of one additional label and will 108 adhere to the hostname syntax requirements of [RFC1123]. These names 109 will own a single A RR, a single AAAA RR, or both. Addresses will be 110 in the IPv4 or IPv6 multicast address space. 112 3.1. Names and Addresses eligible for Registration in MCAST.ARPA 114 Only IANA multicast address registrations are eligible for being 115 listed in MCAST.ARPA. 117 For IPv4, only multicast groups from 224.0.0/24 (Local Network 118 Control Block) and 224.0.1/24 (Internetwork Control Block) will have 119 names assigned. 121 3.2. Subdomains of MCAST.ARPA 123 The namespace under MCAST.ARPA is considered flat, i.e., all direct 124 descendants of MCAST.ARPA are leaves in the DNS tree. Future 125 extensions might want to define subdomains that serve special 126 purposes. Any such designation needs IETF consensus [RFC2434]. 128 3.3. Corresponding Reverse Mapping 130 The DNS Reverse Mapping for those multicast groups that appear as 131 addresses in MCAST.ARPA is to be kept consistent with the forward 132 namespace. A single DNS PTR record will be entered at the 133 corresponding owner within the 224.IN-ADDR.ARPA domain that points to 134 the multicast group name name within MCAST.ARPA. 136 The zones 225.IN-ADDR.ARPA through 239.IN-ADDR.ARPA will be delegated 137 but shall remain empty (except necessary infrastructure RRs). 139 [How to deal with IPv6 multicast reverse mapping is TBD.] 141 4. Migration Issues 143 The current content of the MCAST.NET zone shall be brought in line 144 with the multicast address registry. 146 Since legacy systems may use MCAST.NET for quite some time, there 147 needs to be a mapping/forwarding solution to answer those queries in 148 a useful manner without discouraging migration. 150 RFCs mentioning MCAST.NET are [RFC3261] and [RFC3678]. 152 An updated multicast address assignment policy appears in 153 [I-D.ietf-mboned-addrarch]. 155 4.1. Migration Strategies 157 After the move, several options are available for the future handling 158 of MCAST.NET. 160 4.1.1. Freeze 162 The current MCAST.NET zone could be frozen, so that no additions, 163 deletions or changes to the content (apart from those necessary for 164 maintenance, e.g. SOA and NS RRs) would be perfomed. New 165 registrations would only be available in MCAST.ARPA, so this could be 166 an incentive for querying clients to alter their behavior as well. 168 4.1.2. Phase Out 170 MCAST.NET would only see deletions. 172 4.1.3. Continue 174 MCAST.NET could be further operated in parallel, either by 175 operational habit or per DNAME RR. 177 5. Security Considerations 179 The usual Security Considerations for the DNS apply. 181 There is no Security Problem associated with the migration itself. 183 MCAST.ARPA. should be signed with DNSSEC as soon as the ARPA zone is 184 signed. 186 {This section needs more work.} 188 6. IANA Considerations 190 This document amends [RFC3171] to add a mandatory entry in the 191 MCAST.ARPA domain and a corresponding reverse mapping entry. The 192 officially registered multicast group name is made subject to DNS 193 hostname syntax rules. 195 7. Acknowledgements 197 The author would like to thank David Conrad for his input. 199 8. References 201 8.1. Normative References 203 [RFC1034] Mockapetris, P., "Domain names - concepts and facilities", 204 STD 13, RFC 1034, November 1987. 206 [RFC1035] Mockapetris, P., "Domain names - implementation and 207 specification", STD 13, RFC 1035, November 1987. 209 [RFC1123] Braden, R., "Requirements for Internet Hosts - Application 210 and Support", STD 3, RFC 1123, October 1989. 212 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an 213 IANA Considerations Section in RFCs", BCP 26, RFC 2434, 214 October 1998. 216 [RFC3171] Albanna, Z., Almeroth, K., Meyer, D., and M. Schipper, 217 "IANA Guidelines for IPv4 Multicast Address Assignments", 218 BCP 51, RFC 3171, August 2001. 220 [RFC3172] Huston, G., "Management Guidelines & Operational 221 Requirements for the Address and Routing Parameter Area 222 Domain ("arpa")", BCP 52, RFC 3172, September 2001. 224 8.2. Informative References 226 [I-D.ietf-mboned-addrarch] 227 Savola, P., "Overview of the Internet Multicast Addressing 228 Architecture", draft-ietf-mboned-addrarch-05 (work in 229 progress), October 2006. 231 [RFC2780] Bradner, S. and V. Paxson, "IANA Allocation Guidelines For 232 Values In the Internet Protocol and Related Headers", 233 BCP 37, RFC 2780, March 2000. 235 [RFC2908] Thaler, D., Handley, M., and D. Estrin, "The Internet 236 Multicast Address Allocation Architecture", RFC 2908, 237 September 2000. 239 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 240 A., Peterson, J., Sparks, R., Handley, M., and E. 241 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 242 June 2002. 244 [RFC3678] Thaler, D., Fenner, B., and B. Quinn, "Socket Interface 245 Extensions for Multicast Source Filters", RFC 3678, 246 January 2004. 248 Appendix A. Document Revision History 250 This section is to be removed should the draft be published. 252 A.1. Changes from -00 to -01 254 Added text about DNS reverse mapping. Eligibility for an MCAST.ARPA 255 name now restricted to 224.0.0/24 and 224.0.1/24. Stronger 256 requirement for MCAST.ARPA subdomains. 258 A.2. Initial Document 260 First draft, taking over with only little changes from 261 draft-koch-mboned-mcast-arpa-00.txt 263 Author's Address 265 Peter Koch 266 DENIC eG 267 Wiesenhuettenplatz 26 268 Frankfurt 60329 269 DE 271 Phone: +49 69 27235 0 272 Email: pk@DENIC.DE 274 Full Copyright Statement 276 Copyright (C) The IETF Trust (2007). 278 This document is subject to the rights, licenses and restrictions 279 contained in BCP 78, and except as set forth therein, the authors 280 retain all their rights. 282 This document and the information contained herein are provided on an 283 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 284 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 285 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 286 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 287 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 288 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 290 Intellectual Property 292 The IETF takes no position regarding the validity or scope of any 293 Intellectual Property Rights or other rights that might be claimed to 294 pertain to the implementation or use of the technology described in 295 this document or the extent to which any license under such rights 296 might or might not be available; nor does it represent that it has 297 made any independent effort to identify any such rights. Information 298 on the procedures with respect to rights in RFC documents can be 299 found in BCP 78 and BCP 79. 301 Copies of IPR disclosures made to the IETF Secretariat and any 302 assurances of licenses to be made available, or the result of an 303 attempt made to obtain a general license or permission for the use of 304 such proprietary rights by implementers or users of this 305 specification can be obtained from the IETF on-line IPR repository at 306 http://www.ietf.org/ipr. 308 The IETF invites any interested party to bring to its attention any 309 copyrights, patents or patent applications, or other proprietary 310 rights that may cover technology that may be required to implement 311 this standard. Please address the information to the IETF at 312 ietf-ipr@ietf.org. 314 Acknowledgment 316 Funding for the RFC Editor function is provided by the IETF 317 Administrative Support Activity (IASA).