[Uri-review] Permanent Registration Request for New URI Schemes: teapot and teapots

[Karwan <[e-mail]>]

Dear IANA,

On behalf of the Teapot Protocol (me being the owner of https://teapotprotocol.com/) I respectfully request the permanent registration of two new URI schemes: teapot and teapots.

Overview:
The Teapot Protocol is a forward-compatible, secure, and extensible evolution of HTTP/HTTPS semantics. It introduces enhanced negotiation mechanisms, stringent security requirements, and specialized operational features, all while maintaining a familiar foundation aligned with existing web standards. The teapot and teapots schemes function similarly to http and https, offering both clear-text and encrypted variants, respectively.

URI Schemes:

- teapot: for clear-text interactions
- teapots: for secure, TLS-encrypted interactions

These schemes conform to RFC 3986 and RFC 7595. The teapots scheme mandates TLS 1.3 or higher, ensuring robust confidentiality and integrity.

Intended Applications: The Teapot Protocol is designed for a wide range of advanced web applications, services, and infrastructures. By extending well-understood HTTP paradigms, it provides a stable and future-proof platform for next-generation services that require enhanced security, flexible negotiation, and more granular control over resource interactions.

Contact Information:

- Name: Karwan Stark
- Email: [e-mail]
- Organization: Teapot Protocol
- Domain: [https://teapotprotocol.com](https://teapotprotocol.com/)

Change Controller: Karwan Stark ([e-mail]) on behalf of Teapot Protocol. Any future change control will adhere to RFC 7595 procedures.

Reference: A preliminary draft of the Teapot Protocol Specification is available at:
[https://specification.teapotprotocol.com](https://specification.teapotprotocol.com/)
(This document is intended to be published as an Internet-Draft and eventually as an RFC.)

Semantics and Operations:

- teapot: URIs map to resources accessible via a clear-text protocol.
- teapots: URIs provide equivalent functionality but require TLS, ensuring secure interactions.
- Standard methods (GET, POST, PUT, DELETE, etc.) apply, with optional advanced capabilities enabled through a Teapot-Capabilities header.
- HTTP status code 418 ("I'm a teapot") is reserved as a standardized code for signaling unique resource conditions.

Unique Requirements:

-

Strict TLS Mandate for teapots:
All teapots: URIs MUST be served over TLS 1.3 or higher, using modern cipher suites.

-

Capability Negotiation:
Servers can advertise supported features via Teapot-Capabilities. Clients adapt dynamically to available functionality.

-

Internationalization and Canonicalization:
Full support for IRIs (RFC 3987) ensures global interoperability. Non-ASCII characters must be UTF-8 encoded and percent-encoded as needed.

-

Authentication and Authorization:
Certain operations require valid credentials. A TP-Auth header and OAuth2.0-based flows are recommended to ensure secure operations.

-

Long-Term Utility and Versioning:
Teapot-Version enables version negotiation, allowing the protocol to evolve gracefully while maintaining backward compatibility.

Interoperability and Deployment: The teapot and teapots schemes integrate seamlessly with existing URI parsing logic, simplifying adoption. Gateways and proxies may bridge between these and traditional HTTP/HTTPS services, ensuring gradual and scalable deployment. Clear guidance on feature negotiation supports smooth interoperability as the protocol matures.

Demonstrable, Long-Lived Utility: By blending familiarity with forward-looking enhancements, the Teapot Protocol ensures stable, long-term applicability. Its secure, extensible nature supports evolving standards and infrastructure, meriting the request for permanent registration.

---------------------------------------------------------------

We respectfully request IANA's review and approval for the permanent addition of the teapot and teapots URI schemes. Please contact me if additional information or clarification is required.

Thank you for your consideration.

Submitted by: Karwan Stark
Teapot Protocol
[e-mail]
Date: 2024-12-10