Skip to content

Conversation

@cabo
Copy link
Member

@cabo cabo commented Oct 8, 2025

The present pull request revision is intended as additional input
input for IESG evaluation (2025-10-09 telechat), exploring a way
to integrate the two URI scheme registries created by RFC 7595 and
by this document (issue #140).
It presents an alternative solution so that can be discussed in
detail, not a consensus that this is a better solution than the
one in the WG document.


{{RFC7595@-schemes}} is updated to add a column "CRI Scheme Number" to
the "Uniform Resource Identifier (URI) Schemes" Registry, an unsigned
integer unique in the union of this registry and the "CRI Scheme Numbers for
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you just make this an unsigned integer, and avoid the need for a second registry all together.

@OR13
Copy link

OR13 commented Oct 9, 2025

I think the tricky part of this maneuver will be the guidance to the DE for existing URIs.
Mike Bishop was discussing this on the telechat.

I would suggest text of the form:

New URI registrations may decline to request a CRI integer.
Registrations for existing URIs may have an CRI integer assigned through an expert review process.

@OR13
Copy link

OR13 commented Oct 11, 2025

@cabo and i chatted offline about this, once there is consensus to proceed with this PR / it is merged and new draft is published, I will clear my discuss.

cabo added 4 commits October 12, 2025 22:13
* Shorten the note to be added to the URI Schemes registry.
* Add a paragraph/item list to the text that explains the procedure unambiguously.
* Add another paragraph/item list as an "aside" that explains the rationale.
@cabo cabo merged commit 0c9ac38 into main Oct 16, 2025
2 checks passed
@cabo cabo deleted the merged-scheme-registry branch October 16, 2025 14:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants