[core] Re: Mail regarding draft-ietf-core-comi

Vojtech Vilimek <vojtech.vilimek@nic.cz> Mon, 03 November 2025 16:48 UTC

Return-Path: <vojtech.vilimek@nic.cz>
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 EE47C81A53BC for <core@mail2.ietf.org>; Mon, 3 Nov 2025 08:48:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.399
X-Spam-Level:
X-Spam-Status: No, score=-4.399 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_MED=-2.3, 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 (1024-bit key) header.d=nic.cz
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 16yMfdwlY81J for <core@mail2.ietf.org>; Mon, 3 Nov 2025 08:48:47 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 74D1281A5267 for <core@ietf.org>; Mon, 3 Nov 2025 08:48:15 -0800 (PST)
Received: from [IPV6:2001:1488:fffe:6:2a0b:2945:82f3:47a3] (unknown [IPv6:2001:1488:fffe:6:2a0b:2945:82f3:47a3]) by mail.nic.cz (Postfix) with ESMTPSA id C1A981C05FA for <core@ietf.org>; Mon, 3 Nov 2025 17:48:13 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nic.cz; s=default; t=1762188493; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=EhRV3GkVqTuM/F03soDIehBoQO9IrK1/xTknwqp/M4A=; b=UD6A31Vzf+FIWZ0afNdn8I9V9gRp7jTHzmlKO0YAm5C4uiixzjZ5GqpuEn571iEyUu3V21 YDFs6yyO0VkzJBSba33TT3Kr+nZyvOGqGB2cjRliSNe/LoYsreP/M7kp5x1Z318zV25zX5 k1mcihiQAO8rAAJ7P09QYd7v+4fHVXo=
Authentication-Results: mail.nic.cz; auth=pass smtp.auth=vojtech.vilimek@nic.cz smtp.mailfrom=vojtech.vilimek@nic.cz
Message-ID: <7454b77c-d12b-44a0-94c9-ba0cae99b4d3@nic.cz>
Date: Mon, 03 Nov 2025 17:48:13 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: core@ietf.org
References: <IA1PR11MB7943C4E99801A80F2B03386FE8292@IA1PR11MB7943.namprd11.prod.outlook.com> <BFF69BF8-64BC-4E2E-AC29-9AE1E84D67CA@tzi.org> <CABCOCHT_4nBea4VN7OLnHRBfJuMLfqegWsg1yMOn7wc4DOxidw@mail.gmail.com> <IA1PR11MB7943CD2AD8BA4BE67CE21C98E83C2@IA1PR11MB7943.namprd11.prod.outlook.com>
Content-Language: en-US
From: Vojtech Vilimek <vojtech.vilimek@nic.cz>
In-Reply-To: <IA1PR11MB7943CD2AD8BA4BE67CE21C98E83C2@IA1PR11MB7943.namprd11.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spamd-Result: default: False [-0.10 / 16.00]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; ASN(0.00)[asn:25192, ipnet:2001:1488::/32, country:CZ]; WHITELISTED_IP(0.00)[2001:1488:fffe:6:2a0b:2945:82f3:47a3]; FROM_HAS_DN(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_SIGNED(0.00)[nic.cz:s=default]; MIME_TRACE(0.00)[0:+]
X-Rspamd-Action: no action
X-Rspamd-Server: mail
X-Spamd-Bar: /
X-Rspamd-Queue-Id: C1A981C05FA
X-Rspamd-Pre-Result: action=no action; module=multimap; Matched map: WHITELISTED_IP
Message-ID-Hash: FFDZSZQ65PSGMGYE7O2WF3TPRMLVPKCE
X-Message-ID-Hash: FFDZSZQ65PSGMGYE7O2WF3TPRMLVPKCE
X-MailFrom: vojtech.vilimek@nic.cz
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: Mail regarding draft-ietf-core-comi
List-Id: "Constrained RESTful Environments (CoRE) Working Group list" <core.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/hsSZST88KuYqVYGksWfCP9WJXKA>
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>

Hi Joergen, Carsten and Andy

On 28. Nov 2024, at 10:33, Joergen.Andreasen@microchip.com wrote:
 > [...]
 >
 > FETCH:
 > (1)
 > The example in section 3.1.3.1 shows that a FETCH can retreive an
 > interface by using [1533, "eth0"].
 > A map containing the content of this interface is returned.
 > Is it legal to perform a FETCH on the same node without using a key,
 > such as 1533 only?
 > If it is, what is then expected in the response?
 > Maybe an array containing maps of all interfaces?
 >
 > [...]

Andy pointed out in different thread [1] that this is not possible. The 
YANG 'instance-identifier' SID not [ SID, key1, key2 ] is not valid for 
leaf-lists and lists. This restriction is mandated by YANG
(RFC 7950) and is most likely due to the XML encoding defined in same 
document.

There might be an workaround by container wrapping but for example the 
standard YANG modules do not utilize this.

Cite of Andy's comment:
 > This 3rd issue is not allowed by the instance-identifier data type.
 > https://datatracker.ietf.org/doc/html/rfc7950#section-9.13
 >
 > The XPath node-set must resolve to a single data node for an 
instance-> identifier.

I hope we will find a nice solution to this issue.


Have a nice day!

Vojtech Vilimek
CZ.NIC z.s.p.o.
Czech Republic

[1]: https://mailarchive.ietf.org/arch/msg/core/WIfYqWQcvpV0g46KiAk7VqFSJ64/