Internet-Draft RFC 3405 Update May 2020
Hardie Expires 2 December 2020 [Page]
Workgroup:
DISPATCH
Internet-Draft:
draft-ietf-xml2rfc-template-06
Updates:
3405 (if approved)
Published:
Intended Status:
Best Current Practice
Expires:
Author:
T. Hardie

Updated registration rules for URI.ARPA

Abstract

This document removes references to the IETF tree of URI registrations for registrations in URI.ARPA.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 2 December 2020.

Table of Contents

1. Introduction

Part five of the Dynamic Delegation Discovery System (DDDS), RFC 3405 [RFC3405], describes the registration procedures for assignments in URI.ARPA. The document requires that registrations be in the "IETF tree" of URI registrations. The use of URI scheme name trees was defined in RFC 2717 [RFC2717] but discontinued by RFC 4395 [RFC4395]. Since the use of trees was discontinued, there is no way in the current process set out in BCP 35 [RFC7595] to meet the requirement.

1.1. Requirements Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].

2. Updated Requirements

All registrations in URI.ARPA MUST be for schemes which are permanent registrations, as they are described in BCP 35.

3. References

3.1. Normative References

[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
[RFC3405]
Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Five: URI.ARPA Assignment Procedures", BCP 65, RFC 3405, DOI 10.17487/RFC3405, , <https://www.rfc-editor.org/info/rfc3405>.
[RFC7595]
Thaler, D., Ed., Hansen, T., and T. Hardie, "Guidelines and Registration Procedures for URI Schemes", BCP 35, RFC 7595, DOI 10.17487/RFC7595, , <https://www.rfc-editor.org/info/rfc7595>.

3.2. Informative References

[RFC2717]
Petke, R. and I. King, "Registration Procedures for URL Scheme Names", RFC 2717, DOI 10.17487/RFC2717, , <https://www.rfc-editor.org/info/rfc2717>.
[RFC4395]
Hansen, T., Hardie, T., and L. Masinter, "Guidelines and Registration Procedures for New URI Schemes", RFC 4395, DOI 10.17487/RFC4395, , <https://www.rfc-editor.org/info/rfc4395>.

Author's Address

Ted Hardie