idnits 2.17.1 draft-hardie-dispatch-rfc3405-update-01.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 : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) -- The draft header indicates that this document updates RFC3405, 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 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 (31 May 2020) is 1424 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: 2 errors (**), 0 flaws (~~), 1 warning (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 DISPATCH T. Hardie 3 Internet-Draft 31 May 2020 4 Updates: 3405 (if approved) 5 Intended status: Best Current Practice 6 Expires: 2 December 2020 8 Updated registration rules for URI.ARPA 9 draft-hardie-dispatch-rfc3405-update-01 11 Abstract 13 This document removes references to the IETF tree of URI 14 registrations for registrations in URI.ARPA. 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 2 December 2020. 33 Copyright Notice 35 Copyright (c) 2020 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 (https://trustee.ietf.org/ 40 license-info) in effect on the date of publication of this document. 41 Please review these documents carefully, as they describe your rights 42 and restrictions with respect to this document. Code Components 43 extracted from this document must include Simplified BSD License text 44 as described in Section 4.e of the Trust Legal Provisions and are 45 provided without warranty as described in the Simplified BSD License. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 50 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 51 2. Updated Requirements . . . . . . . . . . . . . . . . . . . . 2 52 3. References . . . . . . . . . . . . . . . . . . . . . . . . . 2 53 3.1. Normative References . . . . . . . . . . . . . . . . . . 2 54 3.2. Informative References . . . . . . . . . . . . . . . . . 3 55 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 57 1. Introduction 59 Part five of the Dynamic Delegation Discovery System (DDDS), RFC 3405 60 [RFC3405], describes the registration procedures for assignments in 61 URI.ARPA. The document requires that registrations be in the "IETF 62 tree" of URI registrations. The use of URI scheme name trees was 63 defined in RFC 2717 [RFC2717] but discontinued by RFC 4395 [RFC4395]. 64 Since the use of trees was discontinued, there is no way in the 65 current process set out in BCP 35 [RFC7595] to meet the requirement. 67 1.1. Requirements Language 69 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 70 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 71 document are to be interpreted as described in RFC 2119 [RFC2119]. 73 2. Updated Requirements 75 All registrations in URI.ARPA MUST be for schemes which are permanent 76 registrations, as they are described in BCP 35. 78 3. References 80 3.1. Normative References 82 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 83 Requirement Levels", BCP 14, RFC 2119, 84 DOI 10.17487/RFC2119, March 1997, 85 . 87 [RFC3405] Mealling, M., "Dynamic Delegation Discovery System (DDDS) 88 Part Five: URI.ARPA Assignment Procedures", BCP 65, 89 RFC 3405, DOI 10.17487/RFC3405, October 2002, 90 . 92 [RFC7595] Thaler, D., Ed., Hansen, T., and T. Hardie, "Guidelines 93 and Registration Procedures for URI Schemes", BCP 35, 94 RFC 7595, DOI 10.17487/RFC7595, June 2015, 95 . 97 3.2. Informative References 99 [RFC2717] Petke, R. and I. King, "Registration Procedures for URL 100 Scheme Names", RFC 2717, DOI 10.17487/RFC2717, November 101 1999, . 103 [RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and 104 Registration Procedures for New URI Schemes", RFC 4395, 105 DOI 10.17487/RFC4395, February 2006, 106 . 108 Author's Address 110 Ted Hardie 112 Email: ted.ietf@gmail.com