[art] Re: [Uri-review] Re: Alternative representation of URIs in YANG
Mark Nottingham <mnot@mnot.net> Fri, 23 January 2026 23:17 UTC
Return-Path: <mnot@mnot.net>
X-Original-To: art@mail2.ietf.org
Delivered-To: art@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id B584CAC3ED24; Fri, 23 Jan 2026 15:17:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level:
X-Spam-Status: No, score=-2.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b="rhIOn9e6"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="weBmr7tm"
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 FN1-_if5f7ox; Fri, 23 Jan 2026 15:17:01 -0800 (PST)
Received: from fhigh-b6-smtp.messagingengine.com (fhigh-b6-smtp.messagingengine.com [202.12.124.157]) (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 39ACDAC3ED1D; Fri, 23 Jan 2026 15:17:01 -0800 (PST)
Received: from phl-compute-06.internal (phl-compute-06.internal [10.202.2.46]) by mailfhigh.stl.internal (Postfix) with ESMTP id B25967A00F6; Fri, 23 Jan 2026 18:17:00 -0500 (EST)
Received: from phl-frontend-03 ([10.202.2.162]) by phl-compute-06.internal (MEProxy); Fri, 23 Jan 2026 18:17:01 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1769210220; x=1769296620; bh=RzcGw9xR3YQZR2VgqakUhpfllKWIJhP3govmwTtTBAU=; b= rhIOn9e6rjqmLUnwNyjRawvBISM7X4aZUcfdyqHQNMiHdWwuZwA4ML7PJA5fKBTp PEkGSpaxvaxxu9EBACQHI3qdHwSCkKFJr7U7gpC00LfBUr0woTa3AZCj1FM8/Xy3 D04UCJsV4yIKGLeSGoSBgvikTAf81QN4V7ZrY+OZ5zkwccpZDEdlDBaS+pwybWGt LX7Be8MqHgQVnPgf01e6l6KNcrN92G/QQyfUDXIB8ReTEJxoulomTWuPK+teduTN 8xYtSfQ0Milu4BUa46cEutY7gZHSoOn0laeEnUNMn+kiDCk0n8OuXzqOBsx0qBy8 2zjnVSjd5m4lTtwRb6N6LQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1769210220; x= 1769296620; bh=RzcGw9xR3YQZR2VgqakUhpfllKWIJhP3govmwTtTBAU=; b=w eBmr7tmlkAD/urNvTwBiNkhXRLmkLVeQ8K/N5Atzh6G6N68POE3JIh5xfb7UEhsq +ewrEtSOCFTole8+NFRi3x8N0IY1/S8cOC6Cu4fVFOT6RI9D1LMfSkYgLMmIA38w LpM7Wev31WiVJ73dx4lGiegGzorL9DpUGhlBUaI7WW7FYgzg9vEjNDPq9+Hhwrgt gDYTo6UnrFRoedTNu6U+eaKjXWoAW+BLNyEDhx9Dd4CaakZgX2WWMHHRif69bihQ kGq7ACp39IFHAdGLLI1xSMskMWYjoo2+7ltjJP8vJENHU9gro7Pm38LjFvtEPqhs iUu44H3mKI20tx+olwlMQ==
X-ME-Sender: <xms:bAF0acGrFiZYQjUPxuRSmwVt3bAYXP9xDnAZPBWpTJ9dDHajDnEKYA> <xme:bAF0aaQ8b1ceKSOGfFYXogBJFPfH1U77DmfwWrlYPzAB3vYiO2cm00ILaw-AaOBPj nYpmK7lAfH7TR20vLpCodumJtMLkldzdRoOR7SvTg6wXQC1OQQ2fUw>
X-ME-Received: <xmr:bAF0aaZZiMs9pUdCO4hWJHSeOVo-3s2ph1JGegqjP2sQg9UnfFAyyWz3uXWOLxlv6AzyuUAV-QHH41KJPFeLuLP0KWxllyA8kImcsF_NH10p4nCUiROfeQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefgedrtddtgdduhedtfeefucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujf gurheptggguffhjgffvefgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpeforghrkhcu pfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuggftrfgrthhtvg hrnhepkeekhffhleeifeethedvudehveefuefgjeefgfegveffgeettdethfefjeevffet necuffhomhgrihhnpehhthhtphhsohhimhhhohhithhsshhtihhllhhmihhslhgvrgguih hnghdrhhhtpdhmnhhothdrnhgvthenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgr mhepmhgrihhlfhhrohhmpehmnhhothesmhhnohhtrdhnvghtpdhnsggprhgtphhtthhope elpdhmohguvgepshhmthhpohhuthdprhgtphhtthhopehmjhgvthhhrghnrghnuggrnhhi sehgmhgrihhlrdgtohhmpdhrtghpthhtohephhhtsehinhhfrdgvugdrrggtrdhukhdprh gtphhtthhopehmtheslhhofigvnhhtrhhophihrdhnvghtpdhrtghpthhtohepkhgvnhht odhivghtfhesfigrthhsvghnrdhnvghtpdhrtghpthhtohepfihorhhlvgihsegrrhhirg gunhgvrdgtohhmpdhrtghpthhtohepihgvthhfrgessghttghonhhnvggtthdrtghomhdp rhgtphhtthhopegrrhhtsehivghtfhdrohhrghdprhgtphhtthhopehurhhiseiffedroh hrghdprhgtphhtthhopehurhhiqdhrvghvihgvfiesihgvthhfrdhorhhg
X-ME-Proxy: <xmx:bAF0ad0FQ9RsXRn9tzWyfufhAscCqc4VASHjvr_-GFTESvTI_dGrFw> <xmx:bAF0aVoJkW50_TyXSMIV2LOoXl0yI765yFfD8SKx1eEa-UaSBbpo2g> <xmx:bAF0aUO-64SVED2rRdQV-25Ch4QO7vPWVUDo9uoQFDGo-8Rk4qQsnQ> <xmx:bAF0aWptulg7jG8DZUS2f-dA1VkIUblaBTK_P9KWxqmhA8JrRFGjag> <xmx:bAF0adXAkgEQLZ3n0HnbTbAAk6zOPKRhZzbUPJzgMabgss1jTYNjt2ua>
Feedback-ID: ie6694242:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 23 Jan 2026 18:16:57 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.300.41.1.7\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <D7A3B7FB-0284-4DCF-B840-8114860A0FDD@gmail.com>
Date: Sat, 24 Jan 2026 10:16:57 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <802512BC-D897-40DE-A79F-ACB6E8921DA7@mnot.net>
References: <87zf669z4x.fsf@hobgoblin.ariadne.com> <0100019be639037e-5401829e-3666-454e-b2c1-e9ac65a04ac5-000000@email.amazonses.com> <e1356eb8-31ba-47ce-9a1f-8d42713184a9@betaapp.fastmail.com> <263D72B1-54D9-47BA-9787-8A3F3889A6ED@gmail.com> <f5bjyx8y0v0.fsf@lochinver.inf.ed.ac.uk> <D7A3B7FB-0284-4DCF-B840-8114860A0FDD@gmail.com>
To: Mahesh Jethanandani <mjethanandani@gmail.com>
X-Mailer: Apple Mail (2.3864.300.41.1.7)
Message-ID-Hash: MCUSUPU7DNELXKXBJMPSBPMVYAJVYAKY
X-Message-ID-Hash: MCUSUPU7DNELXKXBJMPSBPMVYAJVYAKY
X-MailFrom: mnot@mnot.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-art.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "Henry S. Thompson" <ht@inf.ed.ac.uk>, Martin Thomson <mt@lowentropy.net>, Kent Watsen <kent+ietf@watsen.net>, "Dale R. Worley" <worley@ariadne.com>, tom petch <ietfa@btconnect.com>, art@ietf.org, "uri@w3.org" <uri@w3.org>, uri-review@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [art] Re: [Uri-review] Re: Alternative representation of URIs in YANG
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/H0UMcXdsTnevFA0IkiG8y5n9pOM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Owner: <mailto:art-owner@ietf.org>
List-Post: <mailto:art@ietf.org>
List-Subscribe: <mailto:art-join@ietf.org>
List-Unsubscribe: <mailto:art-leave@ietf.org>
I understand that from a YANG perspective the focus is on getting something configured. However, what's being talked about here is creating a protocol artefact that claims to be "ietf-uri" -- i.e., something that the whole IETF community considers to be a good way to convey a URI -- and yet there is clear and consistent feedback from the relevant expert community that what is described is not an appropriate construct. As has been pointed out by others, handling and comparing URIs requires a _lot_ of subtlety, compounded by the many different syntactic options that they offer. It's not at all clear that this structure has been thought through with reference to how it will be used -- hence the nervousness you're hearing from the URI expert community. Furthermore, if something is called "ietf-uri", it is likely to be reused in other situations where the constraints you have in mind are no longer applicable. So the fairly strong advice you're getting is to either: a. Just use a string, per MT (preferred) b. Rename to something *much* more specific to your use case Cheers, > On 24 Jan 2026, at 9:56 am, Mahesh Jethanandani <mjethanandani@gmail.com> wrote: > > Hi Henry, > > Can you provide a specific example of how the current definition of 'ietf-uri’ in YANG does not meet the requirements of configuring HTTP? > > Thanks. > >> On Jan 23, 2026, at 4:22 AM, Henry S. Thompson <ht@inf.ed.ac.uk> wrote: >> >> Mahesh Jethanandani writes: >> >>> How about we go with option 2 that limits the applicability of the definition to the following: >>> >>> The 'ietf-url' module defines a YANG 'grouping' for a URL described as a >>> constrained subset of the URI defined in <relref section="3" target="RFC3986"/>. >> >> Just changing the 'i' to a 'u' doesn't change the fact that it's no >> longer a UR[IL] if it's restricted to 'HTTP', so IMHO it's still >> misleading. >> >> ht > > > Mahesh Jethanandani > mjethanandani@gmail.com > > > > > > > _______________________________________________ > art mailing list -- art@ietf.org > To unsubscribe send an email to art-leave@ietf.org -- Mark Nottingham https://www.mnot.net/
- [art] Re: Alternative representation of URIs in Y… Kent Watsen
- [art] Alternative representation of URIs in YANG Martin Thomson
- [art] Re: Alternative representation of URIs in Y… Martin J. Dürst
- [art] Re: Alternative representation of URIs in Y… tom petch
- [art] Re: Alternative representation of URIs in Y… Martin J. Dürst
- [art] Re: Alternative representation of URIs in Y… Kent Watsen
- [art] Re: Alternative representation of URIs in Y… Martin Thomson
- [art] Re: Alternative representation of URIs in Y… Kent Watsen
- [art] Re: Alternative representation of URIs in Y… Martin Thomson
- [art] Re: Alternative representation of URIs in Y… Kent Watsen
- [art] Re: Alternative representation of URIs in Y… Martin Thomson
- [art] Re: Alternative representation of URIs in Y… Mahesh Jethanandani
- [art] Re: Alternative representation of URIs in Y… Kent Watsen
- [art] Re: Alternative representation of URIs in Y… Kent Watsen
- [art] Re: Alternative representation of URIs in Y… Martin Thomson
- [art] Re: Alternative representation of URIs in Y… Kent Watsen
- [art] Re: Alternative representation of URIs in Y… worley
- [art] Re: [Uri-review] Re: Alternative representa… Tim Bray
- [art] Re: [Uri-review] Re: Alternative representa… worley
- [art] Re: [Uri-review] Re: Alternative representa… Kent Watsen
- [art] Re: [Uri-review] Re: Alternative representa… worley
- [art] Re: [Uri-review] Alternative representation… Roy T. Fielding
- [art] Re: [Uri-review] Re: Alternative representa… Kent Watsen
- [art] Re: Alternative representation of URIs in Y… Sampo Syreeni
- [art] Re: [Uri-review] Re: Alternative representa… worley
- [art] Re: [Uri-review] Re: Alternative representa… worley
- [art] Re: [Uri-review] Re: Alternative representa… Martin Thomson
- [art] Re: [Uri-review] Re: Alternative representa… worley
- [art] Re: [Uri-review] Re: Alternative representa… Kent Watsen
- [art] Re: [Uri-review] Re: Alternative representa… Martin Thomson
- [art] Re: [Uri-review] Re: Alternative representa… Tim Bray
- [art] Re: [Uri-review] Re: Alternative representa… Mahesh Jethanandani
- [art] Re: [Uri-review] Re: Alternative representa… Martin Thomson
- [art] Re: [Uri-review] Re: Re: Alternative repres… Henry S. Thompson
- [art] Re: [Uri-review] Re: Alternative representa… Kent Watsen
- [art] Re: [Uri-review] Re: Alternative representa… Mahesh Jethanandani
- [art] Re: [Uri-review] Re: Alternative representa… Mark Nottingham
- [art] Re: [Uri-review] Re: Alternative representa… Mahesh Jethanandani
- [art] Re: [Uri-review] Re: Alternative representa… Kent Watsen
- [art] Re: [Uri-review] Re: Alternative representa… Martin Thomson
- [art] Re: [Uri-review] Re: Alternative representa… Kent Watsen
- [art] Re: [Uri-review] Re: Alternative representa… Tim Bray
- [art] Re: [Uri-review] Re: Alternative representa… Orie
- [art] Re: [Uri-review] Re: Alternative representa… Martin Thomson