IETF Logo Mail Archive

[core] Keep (URI-)scheme-name? Re: WG Last Call for draft-ietf-core-href-18 (2nd WGLC)

Carsten Bormann <cabo@tzi.org> Fri, 21 February 2025 11:48 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BB11C1D4A62 for <core@ietfa.amsl.com>; Fri, 21 Feb 2025 03:48:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_TEMPERROR=0.01] autolearn=ham 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 2WhHg_jHPoyI for <core@ietfa.amsl.com>; Fri, 21 Feb 2025 03:48:14 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 882E9C151522 for <core@ietf.org>; Fri, 21 Feb 2025 03:48:12 -0800 (PST)
Received: from smtpclient.apple (p548dc3ec.dip0.t-ipconnect.de [84.141.195.236]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4YzpKj6HbczDCfw; Fri, 21 Feb 2025 12:48:09 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.400.131.1.6\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <Z7XpqMiWhB-Eo6hf@hephaistos.amsuess.com>
Date: Fri, 21 Feb 2025 12:47:59 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <07356622-637E-4A5D-8895-DBEA96C5EFFE@tzi.org>
References: <aebdceb8-2025-43a5-a065-19e9715f4451@ri.se> <Z7XpqMiWhB-Eo6hf@hephaistos.amsuess.com>
To: Christian Amsüss <christian@amsuess.com>
X-Mailer: Apple Mail (2.3826.400.131.1.6)
Message-ID-Hash: 24BLIMFKMVLTOQH2XXAPOLRI742XG4TR
X-Message-ID-Hash: 24BLIMFKMVLTOQH2XXAPOLRI742XG4TR
X-MailFrom: cabo@tzi.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-core.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "core@ietf.org" <core@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [core] Keep (URI-)scheme-name? Re: WG Last Call for draft-ietf-core-href-18 (2nd WGLC)
List-Id: "Constrained RESTful Environments (CoRE) Working Group list" <core.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/F5eDSoWAKVPEGGdxGac87FI5SbM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Owner: <mailto:core-owner@ietf.org>
List-Post: <mailto:core@ietf.org>
List-Subscribe: <mailto:core-join@ietf.org>
List-Unsubscribe: <mailto:core-leave@ietf.org>

On 19. Feb 2025, at 15:24, Christian Amsüss <christian@amsuess.com> wrote:
> 
> * Now that we have that big number table of schemes and the update to
>  7595, why is scheme-name even still in there? (Or conversely, if we
>  admit scheme-name, why go through the hassle of registering every
>  registered or otherwise known scheme?)

scheme-name is still an allowed alternative to scheme-number to support generic implementations that do not reload the registry at runtime on every cache miss (or to support mqtt-like non-registered URI-Schemes).
The main use case for scheme number is an implementation that supports a couple dozen URI schemes and now can find numbers for all of them with near-zero effort; adding further schemes by scheme-name to that implementation would also cause acquiring the scheme number during development time. 

I don’t think there is a “good” solution to x-dash; I do think we are quite close here.

Grüße, Carsten

v2.46.0 | Report a Bug | By Email | System Status