Re: [netconf] Relative HTTP URLs in RESTCONF's ietf-yang-library `location` leafs

Kent Watsen <kent+ietf@watsen.net> Sat, 02 March 2024 04:07 UTC

Return-Path: <0100018dfd58616c-49c84a82-f883-4844-a26c-6b1eef06e45d-000000@amazonses.watsen.net>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44E63C14F686 for <netconf@ietfa.amsl.com>; Fri, 1 Mar 2024 20:07:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.com
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 0xH99lV5YDyU for <netconf@ietfa.amsl.com>; Fri, 1 Mar 2024 20:07:25 -0800 (PST)
Received: from a8-88.smtp-out.amazonses.com (a8-88.smtp-out.amazonses.com [54.240.8.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6630CC14F680 for <netconf@ietf.org>; Fri, 1 Mar 2024 20:07:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1709352444; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=EWPY4Vo0IDtiFdaI2Fyic4UMk2UJlbLc0Vyu0hCBpdQ=; b=iI2yHlc/VDsy7drLSbZ98DDMLcxKLULIvclu9caBj6KLIzqNBJf2CAAGOk2Mg7ek CizrJg0EqmkyMXCEquxhKd1z9MhIThfxDQiwyNQjTqagVxNzvRs/aD8DhzX3bxJ2soD nk7tbvJbDlBRwdesxul14VTmeJOThfDaMMX4950I=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <0100018dfd58616c-49c84a82-f883-4844-a26c-6b1eef06e45d-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0254FA4D-0DB9-41AA-BE7F-B48E03611306"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
Date: Sat, 02 Mar 2024 04:07:24 +0000
In-Reply-To: <54d0f63b-b750-4037-a1a2-ad75d8e4edcb@cesnet.cz>
Cc: "netconf@ietf.org" <netconf@ietf.org>
To: Jan Kundrát <jan.kundrat@cesnet.cz>
References: <67362192-7a28-4842-bef5-e88de428b069@cesnet.cz> <0100018df7f32499-392fe0b4-64f0-4cdd-b1ad-a994fd0f6a91-000000@email.amazonses.com> <54d0f63b-b750-4037-a1a2-ad75d8e4edcb@cesnet.cz>
X-Mailer: Apple Mail (2.3774.400.31)
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2024.03.02-54.240.8.88
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/xVqdSgGY-KZ4N3w0NPVwBnPBf4w>
Subject: Re: [netconf] Relative HTTP URLs in RESTCONF's ietf-yang-library `location` leafs
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Mar 2024 04:07:26 -0000

Hi Jan,


> On Mar 1, 2024, at 6:01 AM, Jan Kundrát <jan.kundrat@cesnet.cz> wrote:
> 
>> RFC 6991 defines inet:uri as
>> 
>>  typedef uri {
>>    type string {
>>      pattern '[a-z][a-z0-9+.-]*:.*';
>>    }
>>    …
>>  }
>> 
>> Thus a relative URL would be invalid.
> 
> Thanks, but that's not what my copy of that RFC [1] says:
> 
>    typedef uri {
>      type string;
>      description
>       "The uri type represents a Uniform Resource Identifier
>        (URI) as defined by STD 66.
> 
>        ...
> 
> I also checked the errata, and none of them appear to apply here. What RFC are you referring to?

Sorry, I was referring to the bis here:

	https://datatracker.ietf.org/doc/html/draft-ietf-netmod-rfc6991-bis-15#section-4


> 
>> FWIW, the restconf-client-server draft [1] defines an "external-endpoint” node to configure the user-facing  endpoint:
>> 
>>            description
>>              "Identifies contact information for the external
>>               system that terminates connections before passing
>>               them through to this server (e.g., a network address
>>               translator or a load balancer).  These values have
>>               no effect on the local operation of this server,
>>               but may be used by the application when needing to
>>               inform other systems how to contact this server.";
> 
> That will indeed "solve" the problem for our server, but there are two problems with it:
> 
> 1) If the wording says that "it has no effect on the local operation of this server", I think that that implies that its value should not affect data returned by the server in question. Right?

Look at the second half of that sentence:

	"but may be used by the application when needing to
              inform other systems how to contact this server."

Clearly in scope - agreed?


> 2) Someone will have to figure out how to set this value properly :).
> 
> [1] https://datatracker.ietf.org/doc/html/rfc6991#page-23
> 

Sorry, I don’t understand.  What property?



> With kind regards,
> Jan


Thanks again,
Kent