idnits 2.17.1 draft-ymbk-6bone-arpa-delegation-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. 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 : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 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 (April 2, 2003) is 7688 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) ** Obsolete normative reference: RFC 2471 (Obsoleted by RFC 3701) == Outdated reference: A later version (-04) exists of draft-fink-6bone-phaseout-00 -- Obsolete informational reference (is this intentional?): RFC 3152 (Obsoleted by RFC 3596) Summary: 3 errors (**), 0 flaws (~~), 3 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group R. Bush 3 Internet-Draft IIJ 4 Expires: October 1, 2003 R. Fink 5 April 2, 2003 7 Delegation of E.F.F.3.IP6.ARPA 8 draft-ymbk-6bone-arpa-delegation-01.txt 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance with 13 all provisions of Section 10 of RFC2026. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that other 17 groups may also distribute working documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference 22 material or to cite them other than as "work in progress." 24 The list of current Internet-Drafts can be accessed at http:// 25 www.ietf.org/ietf/1id-abstracts.txt. 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html. 30 This Internet-Draft will expire on October 1, 2003. 32 Copyright Notice 34 Copyright (C) The Internet Society (2003). All Rights Reserved. 36 Abstract 38 This document discusses the need for delegation of the 39 E.F.F.3.IP6.ARPA DNS zone in order to enable reverse lookups for 40 6bone addresses, and makes specific recommendations for the process 41 needed to accomplish this. 43 1. 6bone and DNS 45 The 6bone, whose address space was allocated by [RFC2471], has 46 provided a network for IPv6 experimentation for numerous purposes for 47 seven years. Up to the present time, reverse lookups for 6bone 48 addresses have been accomplished through IP6.INT. It is now 49 important that the thousands of 6bone users be able to update their 50 IPv6 software to use IP6.ARPA [RFC3152]. 52 Although the 6bone has a limited life, as a phaseout plan is being 53 discussed at the IETF at this time [I-D.fink-6bone-phaseout], there 54 is likely to be 2.5 to 3.5 more years of operation. During this 55 remaining 6bone lifetime IP6.ARPA reverse lookup services for the 56 3ffe::/16 address space are required. 58 Discussions have been underway between the 6bone and RIR communities, 59 about having the RIRs perform this service. It was agreed at the San 60 Francisco IETF meeting in March 2003 that it was more practical for 61 the 6bone to provide this service for itself. This would relieve the 62 RIRs of the costs of providing this service, yet still provide the 63 IP6.ARPA authority the ability to terminate the service when the 64 planned 6bone termination date is reached (currently anticipated to 65 be June 6, 2006). 67 The current planning within the 6bone operational community is to 68 provide new inet6num attributes in the 6bone registry database for 69 top level 6bone address space holders to request delegation to their 70 reverse path servers. 72 2. IANA Considerations 74 This memo requests that the IANA delegate the E.F.F.3.IP6.ARPA domain 75 to the 6bone as will be described in instructions to be provided by 76 the IAB. Names within this zone are to be further delegated within 77 the top level 6bone ISPs (known as pTLAs) in accordance with the 78 delegation of 6bone 3FFE::/16 address space. 80 3. Security Considerations 82 While DNS spoofing of address to name mapping has been exploited in 83 IPv4, delegation of the E.F.F.3.IP6.ARPA zone creates no new threats 84 to the security of the internet. 86 Normative References 88 [RFC2471] Hinden, R., Fink, R. and J. Postel, "IPv6 Testing Address 89 Allocation", RFC 2471, December 1998. 91 Informative References 93 [I-D.fink-6bone-phaseout] 94 Fink, R. and R. Hinden, "6bone (IPv6 Testing Address 95 Allocation) Phaseout", draft-fink-6bone-phaseout-00 (work 96 in progress), January 2003. 98 [RFC3152] Bush, R., "Delegation of IP6.ARPA", BCP 49, RFC 3152, 99 August 2001. 101 Authors' Addresses 103 Randy Bush 104 IIJ 105 5147 Crystal Springs 106 Bainbrisge Island, WA 98110 107 US 109 Phone: +1 206 780 0431 110 EMail: randy@psg.com 111 URI: http://psg.com/~randy/ 113 Robert Fink 114 Truckee, CA 115 US 117 Phone: 118 EMail: bob@thefinks.com 120 Intellectual Property Statement 122 The IETF takes no position regarding the validity or scope of any 123 intellectual property or other rights that might be claimed to 124 pertain to the implementation or use of the technology described in 125 this document or the extent to which any license under such rights 126 might or might not be available; neither does it represent that it 127 has made any effort to identify any such rights. Information on the 128 IETF's procedures with respect to rights in standards-track and 129 standards-related documentation can be found in BCP-11. Copies of 130 claims of rights made available for publication and any assurances of 131 licenses to be made available, or the result of an attempt made to 132 obtain a general license or permission for the use of such 133 proprietary rights by implementors or users of this specification can 134 be obtained from the IETF Secretariat. 136 The IETF invites any interested party to bring to its attention any 137 copyrights, patents or patent applications, or other proprietary 138 rights which may cover technology that may be required to practice 139 this standard. Please address the information to the IETF Executive 140 Director. 142 Full Copyright Statement 144 Copyright (C) The Internet Society (2003). All Rights Reserved. 146 This document and translations of it may be copied and furnished to 147 others, and derivative works that comment on or otherwise explain it 148 or assist in its implementation may be prepared, copied, published 149 and distributed, in whole or in part, without restriction of any 150 kind, provided that the above copyright notice and this paragraph are 151 included on all such copies and derivative works. However, this 152 document itself may not be modified in any way, such as by removing 153 the copyright notice or references to the Internet Society or other 154 Internet organizations, except as needed for the purpose of 155 developing Internet standards in which case the procedures for 156 copyrights defined in the Internet Standards process must be 157 followed, or as required to translate it into languages other than 158 English. 160 The limited permissions granted above are perpetual and will not be 161 revoked by the Internet Society or its successors or assignees. 163 This document and the information contained herein is provided on an 164 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 165 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 166 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 167 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 168 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 170 Acknowledgement 172 Funding for the RFC Editor function is currently provided by the 173 Internet Society.