idnits 2.17.1 draft-ietf-mboned-mcast-arpa-00.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 14. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 254. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 265. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 272. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 278. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. 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 (February 26, 2007) is 6240 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC1034' is defined on line 179, but no explicit reference was found in the text == Unused Reference: 'RFC1035' is defined on line 182, but no explicit reference was found in the text == Unused Reference: 'RFC2780' is defined on line 203, but no explicit reference was found in the text == Unused Reference: 'RFC2908' is defined on line 207, but no explicit reference was found in the text ** 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: 2 errors (**), 0 flaws (~~), 7 warnings (==), 8 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 Expires: August 30, 2007 February 26, 2007 6 Moving MCAST.NET into the ARPA infrastructure top level domain 7 draft-ietf-mboned-mcast-arpa-00 9 Status of this Memo 11 By submitting this Internet-Draft, each author represents that any 12 applicable patent or other IPR claims of which he or she is aware 13 have been or will be disclosed, and any of which he or she becomes 14 aware will be disclosed, in accordance with Section 6 of BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on August 30, 2007. 34 Copyright Notice 36 Copyright (C) The IETF Trust (2007). 38 Abstract 40 This document proposes to migrate the MCAST.NET domain into the ARPA 41 top level domain that is dedicated to infrastructure support. It 42 also provides for a maintenance policy and covers migration issues 43 and caveats. 45 Table of Contents 47 1. Introduction . . . . . . . . . . . . . . . . . . . . . 3 48 1.1. The ARPA top level domain . . . . . . . . . . . . . . . 3 49 2. Current Use . . . . . . . . . . . . . . . . . . . . . . 3 50 3. Registration Policy . . . . . . . . . . . . . . . . . . 3 51 3.1. Names and Addresses eligible for Registration in 52 MCAST.ARPA . . . . . . . . . . . . . . . . . . . . . . 3 53 3.2. Subdomains of MCAST.ARPA . . . . . . . . . . . . . . . 4 54 4. Migration Issues . . . . . . . . . . . . . . . . . . . 4 55 4.1. Migration Strategies . . . . . . . . . . . . . . . . . 4 56 4.1.1. Freeze . . . . . . . . . . . . . . . . . . . . . . . . 4 57 4.1.2. Phase Out . . . . . . . . . . . . . . . . . . . . . . . 4 58 4.1.3. Continue . . . . . . . . . . . . . . . . . . . . . . . 4 59 5. Security Considerations . . . . . . . . . . . . . . . . 4 60 6. IANA Considerations . . . . . . . . . . . . . . . . . . 5 61 7. Acknowledgements . . . . . . . . . . . . . . . . . . . 5 62 8. References . . . . . . . . . . . . . . . . . . . . . . 5 63 8.1. Normative References . . . . . . . . . . . . . . . . . 5 64 8.2. Informative References . . . . . . . . . . . . . . . . 5 65 Appendix A. Document Revision History . . . . . . . . . . . . . . . 6 66 A.1. Initial Document . . . . . . . . . . . . . . . . . . . 6 67 Author's Address . . . . . . . . . . . . . . . . . . . 6 68 Intellectual Property and Copyright Statements . . . . 7 70 1. Introduction 72 This document describes a maintenance policy and migration strategy 73 for the MCAST.NET (MCAST.ARPA) domain that contains names for a 74 subset of the multicast groups assigned by the IANA. 76 Comments should be sent to the mboned working group. 78 1.1. The ARPA top level domain 80 [RFC3172] designates the ARPA top level domain as "Address and 81 Routing Parameters Area" to be used for infrastructure applications. 83 The MCAST.NET second level domain fulfills the criteria layed out in 84 section 2.1 of [RFC3172]. However, there is no standards track 85 document explicitly designating this domain to a multicast group name 86 to multicast group address mapping. 88 [RFC3171] defines the multicast address assignment policy. 90 2. Current Use 92 Currently the zone MCAST.NET reflects the contents of the IANA 93 multicast address registry. However, some names are missing from the 94 DNS zone and some names used differ from the description that appears 95 in the registry file. 97 With few exceptions, only multicast group addresses from 224.0.0/24 98 and 224.0.1/24 are listed in MCAST.NET. Addresses outside 224/8 do 99 not appear at all. 101 3. Registration Policy 103 Names within MCAST.ARPA will consist of one additional label and will 104 adhere to the hostname syntax requirements of [RFC1123]. These names 105 will own a single A RR, a single AAAA RR, or both. Addresses will be 106 in the IPv4 or IPv6 multicast address space. 108 3.1. Names and Addresses eligible for Registration in MCAST.ARPA 110 Only IANA multicast address registrations are eligible for being 111 listed in MCAST.ARPA. 113 3.2. Subdomains of MCAST.ARPA 115 There might be subdomains below MCAST.ARPA that serve special 116 purposes. 118 4. Migration Issues 120 The current content of the MCAST.NET zone shall be brought in line 121 with the multicast address registry. 123 Since legacy systems may use MCAST.NET for quite some time, there 124 needs to be a mapping/forwarding solution to answer those queries in 125 a useful manner without discouraging migration. 127 RFCs mentioning MCAST.NET are [RFC3261] and [RFC3678]. 129 An updated multicast address assignment policy appears in 130 [I-D.ietf-mboned-addrarch]. 132 4.1. Migration Strategies 134 After the move, several options are available for the future handling 135 of MCAST.NET. 137 4.1.1. Freeze 139 The current MCAST.NET zone could be frozen, so that no additions, 140 deletions or changes to the content (apart from those necessary for 141 maintenance, e.g. SOA and NS RRs) would be perfomed. New 142 registrations would only be available in MCAST.ARPA, so this could be 143 an incentive for querying clients to alter their behavior as well. 145 4.1.2. Phase Out 147 MCAST.NET would only see deletions. 149 4.1.3. Continue 151 MCAST.NET could be further operated in parallel, either by 152 operational habit or per DNAME RR. 154 5. Security Considerations 156 The usual Security Considerations for the DNS apply. 158 There is no Security Problem associated with the migration itself. 160 MCAST.ARPA. should be signed with DNSSEC as soon as the ARPA zone is 161 signed. 163 {This section needs more work.} 165 6. IANA Considerations 167 This document makes a recommendation to IANA. 169 {This section needs more work.} 171 7. Acknowledgements 173 The author would like to thank David Conrad for his input. 175 8. References 177 8.1. Normative References 179 [RFC1034] Mockapetris, P., "Domain names - concepts and facilities", 180 STD 13, RFC 1034, November 1987. 182 [RFC1035] Mockapetris, P., "Domain names - implementation and 183 specification", STD 13, RFC 1035, November 1987. 185 [RFC1123] Braden, R., "Requirements for Internet Hosts - Application 186 and Support", STD 3, RFC 1123, October 1989. 188 [RFC3171] Albanna, Z., Almeroth, K., Meyer, D., and M. Schipper, 189 "IANA Guidelines for IPv4 Multicast Address Assignments", 190 BCP 51, RFC 3171, August 2001. 192 [RFC3172] Huston, G., "Management Guidelines & Operational 193 Requirements for the Address and Routing Parameter Area 194 Domain ("arpa")", BCP 52, RFC 3172, September 2001. 196 8.2. Informative References 198 [I-D.ietf-mboned-addrarch] 199 Savola, P., "Overview of the Internet Multicast Addressing 200 Architecture", draft-ietf-mboned-addrarch-05 (work in 201 progress), October 2006. 203 [RFC2780] Bradner, S. and V. Paxson, "IANA Allocation Guidelines For 204 Values In the Internet Protocol and Related Headers", 205 BCP 37, RFC 2780, March 2000. 207 [RFC2908] Thaler, D., Handley, M., and D. Estrin, "The Internet 208 Multicast Address Allocation Architecture", RFC 2908, 209 September 2000. 211 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 212 A., Peterson, J., Sparks, R., Handley, M., and E. 213 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 214 June 2002. 216 [RFC3678] Thaler, D., Fenner, B., and B. Quinn, "Socket Interface 217 Extensions for Multicast Source Filters", RFC 3678, 218 January 2004. 220 Appendix A. Document Revision History 222 This section is to be removed should the draft be published. 224 A.1. Initial Document 226 First draft, taking over with only little changes from 227 draft-koch-mboned-mcast-arpa-00.txt 229 Author's Address 231 Peter Koch 232 DENIC eG 233 Wiesenhuettenplatz 26 234 Frankfurt 60329 235 DE 237 Phone: +49 69 27235 0 238 Email: pk@DENIC.DE 240 Full Copyright Statement 242 Copyright (C) The IETF Trust (2007). 244 This document is subject to the rights, licenses and restrictions 245 contained in BCP 78, and except as set forth therein, the authors 246 retain all their rights. 248 This document and the information contained herein are provided on an 249 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 250 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 251 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 252 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 253 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 254 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 256 Intellectual Property 258 The IETF takes no position regarding the validity or scope of any 259 Intellectual Property Rights or other rights that might be claimed to 260 pertain to the implementation or use of the technology described in 261 this document or the extent to which any license under such rights 262 might or might not be available; nor does it represent that it has 263 made any independent effort to identify any such rights. Information 264 on the procedures with respect to rights in RFC documents can be 265 found in BCP 78 and BCP 79. 267 Copies of IPR disclosures made to the IETF Secretariat and any 268 assurances of licenses to be made available, or the result of an 269 attempt made to obtain a general license or permission for the use of 270 such proprietary rights by implementers or users of this 271 specification can be obtained from the IETF on-line IPR repository at 272 http://www.ietf.org/ipr. 274 The IETF invites any interested party to bring to its attention any 275 copyrights, patents or patent applications, or other proprietary 276 rights that may cover technology that may be required to implement 277 this standard. Please address the information to the IETF at 278 ietf-ipr@ietf.org. 280 Acknowledgment 282 Funding for the RFC Editor function is provided by the IETF 283 Administrative Support Activity (IASA).