idnits 2.17.00 (12 Aug 2021) /tmp/idnits42017/draft-hardie-dispatch-rfc3405-update-04.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC3405, updated by this document, for RFC5378 checks: 1998-08-14) -- 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 (15 October 2020) is 576 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) -- Obsolete informational reference (is this intentional?): RFC 2717 (Obsoleted by RFC 4395) -- Obsolete informational reference (is this intentional?): RFC 4395 (Obsoleted by RFC 7595) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 DISPATCH T. Hardie 3 Internet-Draft 15 October 2020 4 Updates: 3405 (if approved) 5 Intended status: Best Current Practice 6 Expires: 18 April 2021 8 Updated registration rules for URI.ARPA 9 draft-hardie-dispatch-rfc3405-update-04 11 Abstract 13 This document updates RFC 3405 by removing references to the IETF 14 tree from the procedures for requesting that a URI scheme be inserted 15 into the uri.arpa zone. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at https://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on 18 April 2021. 34 Copyright Notice 36 Copyright (c) 2020 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 41 license-info) in effect on the date of publication of this document. 42 Please review these documents carefully, as they describe your rights 43 and restrictions with respect to this document. Code Components 44 extracted from this document must include Simplified BSD License text 45 as described in Section 4.e of the Trust Legal Provisions and are 46 provided without warranty as described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 51 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 52 2. Updated Requirements . . . . . . . . . . . . . . . . . . . . 2 53 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 54 4. Security Considerations . . . . . . . . . . . . . . . . . . . 2 55 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 2 56 5.1. Normative References . . . . . . . . . . . . . . . . . . 3 57 5.2. Informative References . . . . . . . . . . . . . . . . . 3 58 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 60 1. Introduction 62 Part five of the Dynamic Delegation Discovery System (DDDS), RFC 3405 63 [RFC3405], describes the registration procedures for assignments in 64 URI.ARPA. The document requires that registrations be in the "IETF 65 tree" of URI registrations. The use of URI scheme name trees was 66 defined in RFC 2717 [RFC2717] but discontinued by RFC 4395 [RFC4395] 67 and its successors. Since the use of trees was discontinued, there 68 is no way in the current process set out in BCP 35 [RFC7595] to meet 69 the requirement to register within that tree. 71 1.1. Requirements Language 73 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 74 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 75 "OPTIONAL" in this document are to be interpreted as described in BCP 76 14 [RFC2119][RFC8174] when, and only when, they appear in all 77 capitals, as shown here. 79 2. Updated Requirements 81 This document removes the normative requirement from RFC 3405 for 82 registrations in URI.ARPA to be from the IETF URI Tree. 84 All registrations in URI.ARPA MUST now be for schemes which are 85 permanent registrations, as they are described in BCP 35. 87 3. IANA Considerations 89 This entire document is updated instructions to IANA. 91 4. Security Considerations 93 This update does not change the Security Considerations in RFC 3405 95 5. References 96 5.1. Normative References 98 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 99 Requirement Levels", BCP 14, RFC 2119, 100 DOI 10.17487/RFC2119, March 1997, 101 . 103 [RFC3405] Mealling, M., "Dynamic Delegation Discovery System (DDDS) 104 Part Five: URI.ARPA Assignment Procedures", BCP 65, 105 RFC 3405, DOI 10.17487/RFC3405, October 2002, 106 . 108 [RFC7595] Thaler, D., Ed., Hansen, T., and T. Hardie, "Guidelines 109 and Registration Procedures for URI Schemes", BCP 35, 110 RFC 7595, DOI 10.17487/RFC7595, June 2015, 111 . 113 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 114 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 115 May 2017, . 117 5.2. Informative References 119 [RFC2717] Petke, R. and I. King, "Registration Procedures for URL 120 Scheme Names", RFC 2717, DOI 10.17487/RFC2717, November 121 1999, . 123 [RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and 124 Registration Procedures for New URI Schemes", RFC 4395, 125 DOI 10.17487/RFC4395, February 2006, 126 . 128 Author's Address 130 Ted Hardie 132 Email: ted.ietf@gmail.com