[core] Re: I-D Action: draft-ietf-core-uri-path-abbrev-04.txt
Christian Amsüss <christian@amsuess.com> Thu, 19 March 2026 22:57 UTC
Return-Path: <christian@amsuess.com>
X-Original-To: core@mail2.ietf.org
Delivered-To: core@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id A756CCE3B9C9 for <core@mail2.ietf.org>; Thu, 19 Mar 2026 15:57:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V4SZ5xYVdujW for <core@mail2.ietf.org>; Thu, 19 Mar 2026 15:57:10 -0700 (PDT)
Received: from smtp.akis.at (smtp.akis.at [IPv6:2a02:b18:500:a515::f455]) (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 mail2.ietf.org (Postfix) with ESMTPS id 970DACE3B9BD for <core@ietf.org>; Thu, 19 Mar 2026 15:57:10 -0700 (PDT)
Received: from poseidon-mailhub.amsuess.com (095129206250.cust.akis.net [95.129.206.250]) by smtp.akis.at (8.18.1/8.18.1) with ESMTPS id 62JMv8s9012645 (version=TLSv1.2 cipher=ECDHE-ECDSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <core@ietf.org>; Thu, 19 Mar 2026 23:57:08 +0100 (CET) (envelope-from christian@amsuess.com)
Received: from poseidon-mailbox.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bf]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id 5A5F96C84B for <core@ietf.org>; Thu, 19 Mar 2026 23:57:07 +0100 (CET)
Received: from hephaistos.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:ae78:bb39:8648:f948]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id CEA255B166 for <core@ietf.org>; Thu, 19 Mar 2026 23:57:06 +0100 (CET)
Received: (nullmailer pid 2664287 invoked by uid 1000); Thu, 19 Mar 2026 22:57:05 -0000
Date: Thu, 19 Mar 2026 23:57:05 +0100
From: Christian Amsüss <christian@amsuess.com>
To: core@ietf.org
Message-ID: <abx_QXF30QNpg2xO@hephaistos.amsuess.com>
References: <177396056091.1369444.2316405475310014787@dt-datatracker-5477d56788-5pkt5>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="FDALt8f544XgGxpv"
Content-Disposition: inline
In-Reply-To: <177396056091.1369444.2316405475310014787@dt-datatracker-5477d56788-5pkt5>
X-Scanned-By: MIMEDefang 2.86 on 95.129.200.85
Message-ID-Hash: XIEAXEJIJAERXOQVN5AKLO4QRVXLRZGR
X-Message-ID-Hash: XIEAXEJIJAERXOQVN5AKLO4QRVXLRZGR
X-MailFrom: christian@amsuess.com
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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [core] Re: I-D Action: draft-ietf-core-uri-path-abbrev-04.txt
List-Id: "Constrained RESTful Environments (CoRE) Working Group list" <core.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/eGN3beROA3a-CkcNQBsshjwpPUA>
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>
Hello CoRE, On Thu, Mar 19, 2026 at 03:49:20PM -0700, internet-drafts@ietf.org wrote: > https://datatracker.ietf.org/doc/draft-ietf-core-uri-path-abbrev/ this very late update of -04 includes editorial changes that Carsten recently sent (IMO the only possibly contentious item being that "this document updates [...] to ~~alter~~++repair+ the behavior of"), but also contains a change worth elaborating on: I missed that as a consequence of -03, a further simplification around the Proxy-Uri handling from "Interaction with other options" could be made. -03 already forbade Uri-Path and Uri-Path-Abbrev mixes resulting from the use of Proxy-Uri (to be consistent with the easier and well-established case of Proxy-Scheme processing). In terms of odd combinations, this only leaves Proxy-Uri (without an actual path segment) to be processed together with Uri-Path-Abbrev. But what I should have simplified that already in -03 is this: The servers that actually see this are exclusively some weird hybrid of proxy and server, never plain servers. Thus, what used to be a SHOULD for every server (and a MUST for some proxies) is now a MUST only for that small proxy-and-server category. It was a SHOULD before because it was unrealistic in the general case, but it is doable in that very special case (if that case is even actually realized; I don't think it is). I'll be presenting the updated -04 version as a delta from -02 in the full meeting, hoping to meet the WG's approval for a WGLC on it. BR Christian -- You don't become great by trying to be great. You become great by wanting to do something, and then doing it so hard that you become great in the process. -- Marie Curie (as quoted by Randall Munroe)
- [core] I-D Action: draft-ietf-core-uri-path-abbre… internet-drafts
- [core] Re: I-D Action: draft-ietf-core-uri-path-a… Christian Amsüss
- [core] Uri-Path-Abbrev: handling of option togeth… Esko Dijk
- [core] Re: Uri-Path-Abbrev: handling of option to… Carsten Bormann
- [core] Re: Uri-Path-Abbrev: handling of option to… Esko Dijk
- [core] Re: Uri-Path-Abbrev: handling of option to… Christian Amsüss
- [core] Re: Uri-Path-Abbrev: handling of option to… Christian Amsüss
- [core] Re: Uri-Path-Abbrev: handling of option to… Esko Dijk