IETF Logo Mail Archive

[core] Re: rfc9254 'instance-identifier' encoding

Vojtech Vilimek <vojtech.vilimek@nic.cz> Mon, 10 November 2025 13: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 B517686E65A0 for <core@mail2.ietf.org>; Mon, 10 Nov 2025 05:48:01 -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 NKkPP9vgrm4y for <core@mail2.ietf.org>; Mon, 10 Nov 2025 05:48:00 -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) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 8B12286E6592 for <core@ietf.org>; Mon, 10 Nov 2025 05:48:00 -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 7769B1C0D37; Mon, 10 Nov 2025 14:47:53 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nic.cz; s=default; t=1762782473; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=xxqqqil0DgF0bm4M+PmR9NmN4QCNlqzKptxNQVJTcXA=; b=dcr1Au85sVve5iVstc8TNjn697Hi6ezDTbXQFQV91hSwJBl2batSpWyzqdrb7qVlLax7Ru iBMj/TcuaseWvGY2z+AVkH7oABYwreuDHZa4Da8iWmi/bDzb58NQ9nVxjUEtJUKzumJMB4 owVXfeLbjMuP3WzPbrub4JcrNjPRgxI=
Authentication-Results: mail.nic.cz; auth=pass smtp.auth=vojtech.vilimek@nic.cz smtp.mailfrom=vojtech.vilimek@nic.cz
Message-ID: <2138b8bc-e856-4032-8662-606535fd28e2@nic.cz>
Date: Mon, 10 Nov 2025 14:47:53 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Carsten Bormann <cabo@tzi.org>
References: <ef6cfa53-1160-4270-9e4c-89c51b86211e@nic.cz> <CABCOCHTqtUA0+mvXr8HH77WLxDUuzPvQ_ADhUxhbCExwDmVaiw@mail.gmail.com> <CABCOCHQUbyvW-ZeCY1pEavNecO1Cft6ZJMq-w1e5+8X0Lqm-uQ@mail.gmail.com> <cd06044c-93f3-4451-b3a2-f3a2f318e1b1@nic.cz> <CABCOCHTp5LXRsAbi6rXHxEVbTHVLd=B-gUs0Vnv6hiRAhKrb2g@mail.gmail.com> <e6ac9574-591b-40f8-9c47-018eee458e0c@nic.cz> <DEB9FB28-09E0-47C6-9994-DB8DD781C2DD@tzi.org>
Content-Language: en-US
From: Vojtech Vilimek <vojtech.vilimek@nic.cz>
In-Reply-To: <DEB9FB28-09E0-47C6-9994-DB8DD781C2DD@tzi.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Spamd-Result: default: False [-0.10 / 16.00]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DKIM_SIGNED(0.00)[nic.cz:s=default]; FROM_HAS_DN(0.00)[]; WHITELISTED_IP(0.00)[2001:1488:fffe:6:2a0b:2945:82f3:47a3]; ARC_NA(0.00)[]; ASN(0.00)[asn:25192, ipnet:2001:1488::/32, country:CZ]; FROM_EQ_ENVFROM(0.00)[]; URIBL_BLOCKED(0.00)[nic.cz:mid]
X-Rspamd-Action: no action
X-Rspamd-Server: mail
X-Spamd-Bar: /
X-Rspamd-Queue-Id: 7769B1C0D37
X-Rspamd-Pre-Result: action=no action; module=multimap; Matched map: WHITELISTED_IP
Message-ID-Hash: 54BVRPJHFRRZ4HIDSMIGKOFAEYFQKSJQ
X-Message-ID-Hash: 54BVRPJHFRRZ4HIDSMIGKOFAEYFQKSJQ
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
CC: core@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [core] Re: rfc9254 'instance-identifier' encoding
List-Id: "Constrained RESTful Environments (CoRE) Working Group list" <core.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/-eAkg2u-xvXTvbrTF-EuM-VRrMs>
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 Carsten,

On 11/7/25 01:21, Carsten Bormann wrote:
> IETF meetings are also quite overloaded...

A lot of work is being done, so no surprise there :).


> I would like to state my opinion that step 1 should essentially elaborate the simplistic instruction “fill in gaps by doing the appropriate analog to RFC 7951 (YANG-JSON)”.

(answering also the previously attached slide)
I did complain about the reference to the YANG-JSON RFC. I want to 
withdraw it as I it in my humble opinion the best solution (after deeper 
thought). What I think the reasons behind the 9254 YANG-CBOR RFC is 
adding more efficient CBOR alternative for the YANG constructs using the 
YANG SIDs. These alternatives are missing for some 'instance-identifier' 
data type.


> I’ll briefly bring up the issue in the WG meeting tomorrow (draft slide below).
Thanks a lot!


> Grüße, Carsten
Best regards
Vojtech Vilimek

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