IETF Logo Mail Archive

[yang-tooling] Re: SID file issues / .sid file differences in pyang and core-wg/pyang

Vojtech Vilimek <vojtech.vilimek@nic.cz> Mon, 09 February 2026 17:56 UTC

Return-Path: <vojtech.vilimek@nic.cz>
X-Original-To: yang-tooling@mail2.ietf.org
Delivered-To: yang-tooling@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 196FCB431C8E for <yang-tooling@mail2.ietf.org>; Mon, 9 Feb 2026 09:56:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -7.101
X-Spam-Level:
X-Spam-Status: No, score=-7.101 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_HI=-5, 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 X7wQUKVEmN1x for <yang-tooling@mail2.ietf.org>; Mon, 9 Feb 2026 09:56:39 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (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 A526FB431C89 for <yang-tooling@ietf.org>; Mon, 9 Feb 2026 09:56:39 -0800 (PST)
Received: from [10.128.141.242] (unknown [78.128.191.226]) by mail.nic.cz (Postfix) with ESMTPSA id BADFF1C0FFC for <yang-tooling@ietf.org>; Mon, 9 Feb 2026 18:56:38 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nic.cz; s=default; t=1770659798; 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=k2hwIeV6v+nuO3SSt8YGU62HXDF/3W2ovBrFDZY5+l0=; b=vMAemiezBAvMC5hXQjhDS+N0YtwKOVB5Iv5RIALdNlSGc06IYFPckhJHl+bUrOzo07vFQX vPB8gJiU8WwnMRoDPA8hIg/bBeE/WLFJOdftuPTqi3diwLtOiPjBWGroLPhiQm9yHtMhnh Peb83Ei0hFp461jLLbXzmhuq2DyUtgw=
Authentication-Results: mail.nic.cz; auth=pass smtp.auth=vojtech.vilimek@nic.cz smtp.mailfrom=vojtech.vilimek@nic.cz
Message-ID: <586eddea-6163-4f5d-b13a-59696c08db59@nic.cz>
Date: Mon, 09 Feb 2026 18:56:38 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: yang-tooling@ietf.org
References: <CABCOCHTP52cfDVeguY3iYbzJqmCfg-z5cMeFz-y_3vNw250TEg@mail.gmail.com> <ee28c8c1-fe81-4f9f-ba36-b60c74b5d156@iotconsultancy.nl> <CABCOCHR-oo5xK2bbagDUtK=1Mi5dBLjNT8r=4Y4QSJoFs0SgRA@mail.gmail.com> <b1256b3f-794b-40e8-a7e8-d1395fa7aa0d@iotconsultancy.nl> <EE144B22-21ED-46E8-8963-3D5639F377E9@tzi.org> <CABCOCHSzgtHZ3YpEwCrCtXBTFjusidzP3aCDbeJySM36toFoeA@mail.gmail.com> <81BE63E4-AB15-4298-8A63-94726BD7F024@tzi.org> <CABCOCHTC-VTk5gBY7O95Au8eUF84pgVA2q4z7d8kY8N4hsFVtw@mail.gmail.com> <6E107270-5943-4615-A221-24FC6A66D914@tzi.org> <CABCOCHR32FgW_y54KTomJcD+kaFn_yqupr1-zCJJyHsPEoxX5g@mail.gmail.com> <CABONVQZTqmiGPW3WdEABPeLCwiJXoXxnWZqEo2zVVt0wLto-6g@mail.gmail.com> <CABCOCHR7NyT3BYqp7AWhKx30dYgLDc9bTPRMCDxYtgWBTw37_A@mail.gmail.com> <CABONVQYyuVaeUYiF2jVQP+WecntE3pdZ=S_9h3D=3OKmOaZYFg@mail.gmail.com> <CABCOCHSohiqD3knXA4BGbBRUz=QYS+JmfZy+KTfu_gwXs1x_ug@mail.gmail.com> <3A8390F8-C788-4174-A7E2-2872694AAD41@tzi.org>
Content-Language: en-US
From: Vojtech Vilimek <vojtech.vilimek@nic.cz>
In-Reply-To: <3A8390F8-C788-4174-A7E2-2872694AAD41@tzi.org>
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]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; ASN(0.00)[asn:2852, ipnet:78.128.128.0/17, country:CZ]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; NEURAL_HAM(-0.00)[-0.915]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_SIGNED(0.00)[nic.cz:s=default]; FROM_EQ_ENVFROM(0.00)[]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]
X-Rspamd-Action: no action
X-Rspamd-Server: mail
X-Spamd-Bar: /
X-Rspamd-Queue-Id: BADFF1C0FFC
Message-ID-Hash: BDOQ4KHRU54ESEKPR5TOYXB6EIBQGGLL
X-Message-ID-Hash: BDOQ4KHRU54ESEKPR5TOYXB6EIBQGGLL
X-MailFrom: vojtech.vilimek@nic.cz
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; 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: [yang-tooling] Re: SID file issues / .sid file differences in pyang and core-wg/pyang
List-Id: "Contributing to and tracking the progress of YANG tooling, as it concerns IETF work that uses YANG." <yang-tooling.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-tooling/gWTpLD7W2X95JJN-FjgzEcWop_g>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-tooling>
List-Help: <mailto:yang-tooling-request@ietf.org?subject=help>
List-Owner: <mailto:yang-tooling-owner@ietf.org>
List-Post: <mailto:yang-tooling@ietf.org>
List-Subscribe: <mailto:yang-tooling-join@ietf.org>
List-Unsubscribe: <mailto:yang-tooling-leave@ietf.org>

Hi all,

I also think and hope that the CORECONF will be good standard for the 
constrained nodes and/or networks. Laurent, if you find the checking of 
the choice/case too demanding for the hardware, do you really need them 
in your models? I also do not believe that you won't do any checks on 
the constrained node. I hope that the checks mandated by 
CORECONF/YANG-CBOR are not too heavy for such use-cases (i.e. some 
additional checks implied by the protocol in use).


Best regards,

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

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