[Uri-review] [IANA #1278861] Request for Assignment (uri-schemes)
David Dong via RT <iana-prot-param@iana.org> Mon, 14 August 2023 21:58 UTC
Return-Path: <iana-shared@icann.org>
X-Original-To: uri-review@ietfa.amsl.com
Delivered-To: uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E2D7C152577 for <uri-review@ietfa.amsl.com>; Mon, 14 Aug 2023 14:58:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.654
X-Spam-Level:
X-Spam-Status: No, score=-1.654 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zxdyIo3-gyoy for <uri-review@ietfa.amsl.com>; Mon, 14 Aug 2023 14:58:55 -0700 (PDT)
Received: from smtp.lax.icann.org (smtp.lax.icann.org [192.0.33.81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 062D5C15256E for <uri-review@ietf.org>; Mon, 14 Aug 2023 14:58:55 -0700 (PDT)
Received: from request6.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp.lax.icann.org (Postfix) with ESMTP id D6AB3E1B71; Mon, 14 Aug 2023 21:58:54 +0000 (UTC)
Received: by request6.lax.icann.org (Postfix, from userid 48) id D0F5B237F; Mon, 14 Aug 2023 21:58:54 +0000 (UTC)
RT-Owner: david.dong
From: David Dong via RT <iana-prot-param@iana.org>
Reply-To: iana-prot-param@iana.org
In-Reply-To: <3se2yk0wyu-1@ppa4.dc.icann.org>
References: <RT-Ticket-1278861@icann.org> <3se2yk0wyu-1@ppa4.dc.icann.org>
Message-ID: <rt-5.0.3-1310995-1692050334-105.1278861-37-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1278861
X-Managed-BY: RT 5.0.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: david.dong@iana.org
To: michael_b_jones@hotmail.com
CC: uri-review@ietf.org
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Mon, 14 Aug 2023 21:58:54 +0000
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/uri-review/jzOs3o0mK7BwGwaefg-PCQwuJE8>
Subject: [Uri-review] [IANA #1278861] Request for Assignment (uri-schemes)
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uri-review/>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Aug 2023 21:58:59 -0000
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 -- Referring to: https://openid.net/specs/openid-connect-core-1_0-31.html#URISchemeRegistry I would say that this is OK for provisional registration, but not yet for permanent registration. Problems I’m seeing are: 1. 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 https://www.rfc-editor.org/rfc/rfc7595#section-3 2. 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://www.iana.org/assignments/iesg-recognized-organizations/iesg-recognized-organizations.xhtml 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 On Mon Aug 14 16:33:23 2023, michael_b_jones@hotmail.com wrote: > > Contact Name: > Michael B. Jones > > Contact Email: > michael_b_jones@hotmail.com > > Type of Assignment: > URI Scheme > > Registry: > https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml > > Description: > The OpenID Connect protocol has used the “openid” scheme for a decade > but it has never been registered. Several requests have come in over > the years to register it. I requested registration on the uri- > review@ietf.org list over two weeks ago and there has been no > response. > > Additional Info: > Please register the “openid” scheme as requested at > https://openid.net/specs/openid-connect-core-1_0- > 31.html#URISchemeRegistry.
- [Uri-review] [IANA #1278861] Request for Assignme… David Dong via RT
- Re: [Uri-review] [IANA #1278861] Request for Assi… Michael Jones
- [Uri-review] [IANA #1278861] Request for Assignme… David Dong via RT