RFC 8958

RFC 8958: Updated Registration Rules for URI.ARPA 🎀

Okay bestie, so this one is by T. Hardie (that's Ted Hardie) 💖, published December 2020. It's a Best Current Practice 👑, numbered BCP 65, and its ISSN is 2070-1721. It updates RFC 3405 ✨, and the header doesn't list anything it obsoletes. It's an IETF thing, so it's a Best Current Practice for the whole Internet community, not just one company's vibe.

---

Abstract 🦋

This doc updates RFC 3405 by taking out the bits about the IETF tree from the steps for asking that a URI scheme get added to the URI.ARPA zone. Lowkey a cleanup, but a necessary one 🧹

Status of This Memo 💅

This memo documents an Internet Best Current Practice.

This is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It went through public review and got approved for publication by the Internet Engineering Steering Group (IESG) 🙌 More info on BCPs is in Section 2 of RFC 7841.

You can find the current status of this document, any errata, and how to send feedback at https://www.rfc-editor.org/info/rfc8958 🌸

Copyright Notice 🌈

Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) as they stand on the publication date. Please actually read those, bestie, because they spell out your rights and restrictions for this document. Code Components pulled out of this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions, and they come with no warranty, as described in the Simplified BSD License ⚖️

Table of Contents 🧚

• 1. Introduction
  • 1.1. Requirements Language
• 2. Updated Requirements
• 3. IANA Considerations
• 4. Security Considerations
• 5. References
  • 5.1. Normative References
  • 5.2. Informative References
• Author's Address

1. Introduction ✨

Okay so Part Five of the Dynamic Delegation Discovery System (DDDS) [RFC3405] is where the registration rules for assignments in URI.ARPA live. The doc says registrations have to be in the "IETF tree" of URI registrations. Back in RFC 2717 [RFC2717], URI scheme name trees were a thing, but RFC 4395 [RFC4395] and its successors discontinued them. So trees are gone, and the current process in BCP 35 [RFC7595] has no way to meet the requirement to register inside a tree that doesn't exist anymore 💀 That's the whole problem this doc fixes.

1.1. Requirements Language 💜

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

2. Updated Requirements 🔥

This document removes the normative requirement from RFC 3405 [RFC3405] that registrations in URI.ARPA come from the IETF URI tree. That tree-only rule is officially gone 👋

All registrations in URI.ARPA MUST now be for schemes that are permanent registrations, as described in BCP 35. So no more temp vibes, it's permanent or nothing ✨

3. IANA Considerations 🧾

This entire document is updated instructions to IANA. So IANA, this whole doc is literally your to-do list 📋

4. Security Considerations ⚠️

This update does not change the security considerations in RFC 3405 [RFC3405]. The security considerations from RFC 3405 still apply in full, so don't skip them just because this doc is shorter 🙈 Those are serious, bestie, and they stay exactly as they were.

5. References 📚

5.1. Normative References 💖

[RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
           Requirement Levels", BCP 14, RFC 2119,
           DOI 10.17487/RFC2119, March 1997,
           <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, October 2002,
           <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, June 2015,
           <https://www.rfc-editor.org/info/rfc7595>.

[RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
           2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
           May 2017, <https://www.rfc-editor.org/info/rfc8174>.

5.2. Informative References 🌸

[RFC2717]  Petke, R. and I. King, "Registration Procedures for URL
           Scheme Names", RFC 2717, DOI 10.17487/RFC2717, November
           1999, <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, February 2006,
           <https://www.rfc-editor.org/info/rfc4395>.

Author's Address 🫶

Ted Hardie

Email: ted.ietf@gmail.com