idnits 2.17.1 draft-hardie-iris-arpa-00.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 : ---------------------------------------------------------------------------- == There are 2 instances of lines with non-RFC2606-compliant FQDNs in the document. -- The draft header indicates that this document updates RFC4698, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC4698, updated by this document, for RFC5378 checks: 2002-08-15) -- 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 (January 10, 2018) is 2297 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: 0 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group T. Hardie 3 Internet-Draft January 10, 2018 4 Updates: 4698 (if approved) 5 Intended status: Standards Track 6 Expires: July 14, 2018 8 Iris.arpa is Deprecated 9 draft-hardie-iris-arpa-00 11 Abstract 13 This document requests that iris.arpa and areg.iris.arpa be removed 14 from the arpa zone. 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at https://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on July 14, 2018. 33 Copyright Notice 35 Copyright (c) 2018 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (https://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 51 2. Recommendation . . . . . . . . . . . . . . . . . . . . . . . 2 52 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 53 4. Security Considerations . . . . . . . . . . . . . . . . . . . 2 54 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 2 55 6. Normative References . . . . . . . . . . . . . . . . . . . . 3 56 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 58 1. Introduction 60 The Internet Registry Information Service[RFC3981] described a 61 client-server protocol for querying Internet registries. One 62 intended usage of the protocol was address registries, described in 63 [RFC4698]. That document requested the Internet Architecture Board 64 (IAB) to instruct IANA to insert a new label under .arpa. The IAB 65 requested that delegation as set out in [RFC3172], and IANA set up 66 both iris.arpa and a sub-delegation, areg.iris.arpa, as requested. 68 2. Recommendation 70 While IRIS was specified for this usage, it was not deployed for this 71 purpose. At the request of the IAB, IANA reviewed usage statistics 72 for the iris.arpa zone and found zero queries for areg.iris.arpa or 73 NAPTR records during the survey period. 75 This document recommends that these delgations be removed from .arpa. 76 If approved, the IAB is requested to instruct IANA to remove them. 78 3. IANA Considerations 80 This document requests that IANA remove .iris.arpa and its sub- 81 delegations from the arpa zone upon receiving the relevant approval 82 of the IAB. 84 4. Security Considerations 86 If there are users which are testing for the presence of this domain, 87 those tests will fail. Without evidence of the existence of those 88 tests or knowledge of their purpose, the impact is unknown. 90 5. Acknowledgements 92 Michelle Cotton and ICANN staff gathered the DNS request data on 93 iris.arpa utilization. Michelle Cotton and Andy Newton reviewed this 94 document. 96 6. Normative References 98 [RFC3172] Huston, G., Ed., "Management Guidelines & Operational 99 Requirements for the Address and Routing Parameter Area 100 Domain ("arpa")", BCP 52, RFC 3172, DOI 10.17487/RFC3172, 101 September 2001, . 103 [RFC3981] Newton, A. and M. Sanz, "IRIS: The Internet Registry 104 Information Service (IRIS) Core Protocol", RFC 3981, 105 DOI 10.17487/RFC3981, January 2005, 106 . 108 [RFC4698] Gunduz, E., Newton, A., and S. Kerr, "IRIS: An Address 109 Registry (areg) Type for the Internet Registry Information 110 Service", RFC 4698, DOI 10.17487/RFC4698, October 2006, 111 . 113 Author's Address 115 Ted Hardie 117 Email: ted.ietf@gmail.com