idnits 2.17.1 draft-ymbk-6to4-arpa-delegation-00.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 (February 13, 2003) is 7736 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) No issues found here. Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 2 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: August 14, 2003 J. Damas 5 February 13, 2003 7 Delegation of 2.0.0.2.ip6.arpa 8 draft-ymbk-6to4-arpa-delegation-00.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 August 14, 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 2.0.0.2.ip6.arpa DNS zone in order to enable reverse lookups for 6to4 40 addresses. 42 1. 6to4 and DNS 44 6to4 [RFC3056] provides a mechanism for IPv6 native hosts to 45 communicate over IPv4 clouds without explicit tunnel setup. 47 6to4 and DNS [I-D.moore-6to4-dns] describes methods to find the 48 delegation path for reverse lookups of 6to4 addresses in the DNS. 49 Section 3.1 of the I-D describes a simple method, using established 50 mechanisms at the RIRs, that would enable such a mechanism to be 51 deployed using a minimum of additional setup. 53 Under the described method, the holders of IPv4 address space can 54 request the delegation of a sub-zone in the 2.0.0.2.ip6.arpa DNS tree 55 from the party from which they obtained the corresponding IPv4 56 in-addr.arpa delegation (or the holder of an even shorter IPv4 prefix 57 if their immediate parent is not configured for ip6.arpa), following 58 the mapping of IPv4 delegations. This sub-zone can then be populated 59 by the entity deploying the 6to4 infrastructure. 61 2. IANA Considerations 63 This memo requests that the IANA delegate the 2.0.0.2.IP6.ARPA domain 64 to the RIRs as will be described in instructions to be provided by 65 the IAB. Names within this zone are to be further delegated within 66 the regional IP registries and ISPs in accordance with the delegation 67 of IPv4 address space. 69 3. Security Considerations 71 While DNS spoofing of address to name mapping has been exploited in 72 IPv4, delegation of the 2.0.0.2.ip6.arpa zone creates no new threats 73 to the security of the internet. 75 Normative References 77 [RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains 78 via IPv4 Clouds", RFC 3056, February 2001. 80 Informative References 82 [I-D.moore-6to4-dns] 83 Moore, K., "6to4 and DNS", draft-moore-6to4-dns-03 (work 84 in progress), October 2002. 86 Authors' Addresses 88 Randy Bush 89 IIJ 90 5147 Crystal Springs 91 Bainbrisge Island, WA 98110 92 US 94 Phone: +1 206 780 0431 95 EMail: randy@psg.com 96 URI: http://psg.com/~randy/ 97 Joao Damas 98 Amsterdam, 99 The Netherlands 101 Phone: 102 EMail: joao@psg.com 104 Intellectual Property Statement 106 The IETF takes no position regarding the validity or scope of any 107 intellectual property or other rights that might be claimed to 108 pertain to the implementation or use of the technology described in 109 this document or the extent to which any license under such rights 110 might or might not be available; neither does it represent that it 111 has made any effort to identify any such rights. Information on the 112 IETF's procedures with respect to rights in standards-track and 113 standards-related documentation can be found in BCP-11. Copies of 114 claims of rights made available for publication and any assurances of 115 licenses to be made available, or the result of an attempt made to 116 obtain a general license or permission for the use of such 117 proprietary rights by implementors or users of this specification can 118 be obtained from the IETF Secretariat. 120 The IETF invites any interested party to bring to its attention any 121 copyrights, patents or patent applications, or other proprietary 122 rights which may cover technology that may be required to practice 123 this standard. Please address the information to the IETF Executive 124 Director. 126 Full Copyright Statement 128 Copyright (C) The Internet Society (2003). All Rights Reserved. 130 This document and translations of it may be copied and furnished to 131 others, and derivative works that comment on or otherwise explain it 132 or assist in its implementation may be prepared, copied, published 133 and distributed, in whole or in part, without restriction of any 134 kind, provided that the above copyright notice and this paragraph are 135 included on all such copies and derivative works. However, this 136 document itself may not be modified in any way, such as by removing 137 the copyright notice or references to the Internet Society or other 138 Internet organizations, except as needed for the purpose of 139 developing Internet standards in which case the procedures for 140 copyrights defined in the Internet Standards process must be 141 followed, or as required to translate it into languages other than 142 English. 144 The limited permissions granted above are perpetual and will not be 145 revoked by the Internet Society or its successors or assignees. 147 This document and the information contained herein is provided on an 148 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 149 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 150 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 151 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 152 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 154 Acknowledgement 156 Funding for the RFC Editor function is currently provided by the 157 Internet Society.