- edited description
Register openid to the well-known URI scheme IANA registry
I heard some desire from SSI people at IIW that they want openid: to be registered to the Uniform Resource Identifier (URI) Schemes IANA registry [1] according to RFC7595 [2]
[1] https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml
Comments (15)
-
reporter -
reporter - edited description
-
We agreed on the 10-Oct-19 call to do this, since there is increasing interested in the self-issued OP functionality from the self-sovereign identity crowd.
-
- changed status to open
-
-
-
assigned issue to
-
assigned issue to
-
Issue
#1173was marked as a duplicate of this issue. -
- changed milestone to Errata
I plan to add the scheme definition and IANA registration request as part of the errata edits.
-
Will be fixed by https://bitbucket.org/openid/connect/pull-requests/584
-
- changed status to resolved
-
- changed status to open
I have sent a request to register the
openid
scheme to uri-review@ietf.org. -
I sent a registration directly to IANA because there has been no response to my request sent to the mailing list. IANA is tracking this in the thread “[IANA #1278861] AutoReply: Request for Assignment“.
-
We received the following response from IANA. I plan to discuss this on today’s call.
Hi Michael (ccing: uri-review@ietf.org),
Please see below for review from Graham Klyne.
Please let us if you would like to proceed with a provisional registration instead as well.
Best regards,
David Dong
IANA Services Sr. Specialist
--
I would say that this is OK for provisional registration, but not yet for permanent registration.
Problems I’m seeing are:
- the reference provided in the registration template does not appear to provide a URI specification. Among other things, I’m expecting there to be a syntax specification that can be checked for conformity with RFC3986 generic URI syntax. Also there are other considerations mentioned at
- A permanent URI registration is usually expected to broadly meet the requirements for an IETF standard — the obvious way to do this is by publication as a standards track RFC. Other possible routes (for permanent URI scheme registrations) are as an IETF track informational or experimental RFC, or alternatively as publication as a standard (or equivalent) by an organisation recognised in the IETF as a creator of open standards.
I see at https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.iana.org%2Fassignments%2Fiesg-recognized-organizations%2Fiesg-recognized-organizations.xhtml&data=05%7C01%7C%7Cd178d07404e24b3cbd2008db9d11a826%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638276471382850489%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CeikLHSKk8Z%2FQFJH8uEimLfESkctx7WDLDGGfIoeXtA%3D&reserved=0 that OpenId Foundation are recognised in the IETF as a producer of standards. So for a permanent registration I would be looking for an indication that the specification has passed through whatever consensus process that organisation uses for approving its publications as standards.
#g
-
I requested provisional registration, based on the discussions on the 14-Aug-23 working group call.
-
- marked as task
Provisional registration of the openid: scheme was made at https://www.iana.org/assignments/uri-schemes/prov/openid on
2023-08-16
. - Log in to comment