IETF Logo Mail Archive

[yang-tooling] Fwd: Re: Issues with IANA YANG SID registry

Vojtech Vilimek <vojtech.vilimek@nic.cz> Fri, 29 May 2026 09:15 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 DDFFEF744D80 for <yang-tooling@mail2.ietf.org>; Fri, 29 May 2026 02:15:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1780046104; bh=pJkX7ARKH7ufAkodkqivJuLfo2AweYynrmXwfOmrbhY=; h=Date:Subject:References:To:From:In-Reply-To; b=lXcqORNd/QZS6hUuQel78HwXXOUfrbgmFcp7+oCAGTcpD/36MJJB1egWxR9ThIi9W g8tZ4jcp2kAw4Jrv8gQNsjzrryApiVECIpbNEqcIZZwOHZ0y7ubk51aQ/6e9QWMJuw e9tpzN6Jk971d31DkBNvJfn64BmpOyuS+Ms/V0Kk=
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_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_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 aIICvu3QguXj for <yang-tooling@mail2.ietf.org>; Fri, 29 May 2026 02:14:59 -0700 (PDT)
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 3907AF744D65 for <yang-tooling@ietf.org>; Fri, 29 May 2026 02:14:59 -0700 (PDT)
Received: from [10.4.34.247] (unknown [195.113.242.134]) by mail.nic.cz (Postfix) with ESMTPSA id E6A8E1C0602 for <yang-tooling@ietf.org>; Fri, 29 May 2026 11:14:57 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nic.cz; s=default; t=1780046098; 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=rRf0w0yZBv9Cdbh+5N79kSkk5Uh5nrsp8Pqx1axgBMg=; b=u5ewkUYTTiSzlWfYMwaIbyTYTAKJ8mE4HgWGRJRy/OoHtIk2oVsdS2dm3KFDohik76MGkD lzpkVvl5mf2HtLn1E2dx8kx6u8Q5VrKCVOFr/GuOoZu4zJuztNgrEobayRv5FpXThbEeQu 9sEUrVngS+Kam920VBPxrwKLSiZ+oDs=
Authentication-Results: mail.nic.cz; auth=pass smtp.auth=vojtech.vilimek@nic.cz smtp.mailfrom=vojtech.vilimek@nic.cz
Message-ID: <a4a7fb18-487f-4522-84d5-53489fa13943@nic.cz>
Date: Fri, 29 May 2026 11:14:57 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
References: <b36c57ad-37fa-4bf0-9d85-6746f49157b2@nic.cz>
To: "yang-tooling@ietf.org" <yang-tooling@ietf.org>
From: Vojtech Vilimek <vojtech.vilimek@nic.cz>
In-Reply-To: <b36c57ad-37fa-4bf0-9d85-6746f49157b2@nic.cz>
X-Forwarded-Message-Id: <b36c57ad-37fa-4bf0-9d85-6746f49157b2@nic.cz>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Rspamd-Action: no action
X-Spamd-Result: default: False [-0.10 / 16.00]; MIME_GOOD(-0.10)[text/plain]; RCVD_COUNT_ZERO(0.00)[0]; MID_RHS_MATCH_FROM(0.00)[]; FUZZY_RATELIMITED(0.00)[rspamd.com]; ASN(0.00)[asn:2852, ipnet:195.113.0.0/16, country:CZ]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_SIGNED(0.00)[nic.cz:s=default]; TO_DN_EQ_ADDR_ALL(0.00)[]; LOCAL_OUTBOUND(0.00)[]; RCPT_COUNT_ONE(0.00)[1]
X-Rspamd-Server: mail
X-Rspamd-Queue-Id: E6A8E1C0602
X-Spamd-Bar: /
Message-ID-Hash: YHKPDQFMTLIGK5X3BJB5DSNOKDZ27IY3
X-Message-ID-Hash: YHKPDQFMTLIGK5X3BJB5DSNOKDZ27IY3
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] Fwd: Re: Issues with IANA YANG SID registry
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/wAwfFHdI-ScBlCPJmABkRrVONyA>
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 yang-tooling subscribers,

initially wrong list yet again. Sorry for any inconvenience.

Vojtech


-------- Forwarded Message --------
Subject: Re: [yang-tooling] Re: Issues with IANA YANG SID registry
Date: Fri, 29 May 2026 11:10:07 +0200
From: Vojtech Vilimek <vojtech.vilimek@nic.cz>
To: Michael Richardson <mcr@sandelman.ca>
CC: core <core@ietf.org>

Hi Michael,

On 5/29/26 2:00 AM, Michael Richardson wrote:
> I think that this is a pretty important point.
> It's the import that is an issue, but I think augment / sx:structure might
> also cause problems.  Imagine a revision to the thing that is imported, so
> now the importing module changes while it's revision does not change.
> I don't have an example handy.
> I suspect that we have to keep more meta-data in the SID file about
> such situations.  Andy, you go on to explain this.

Neither augment nor sx:structure cause problems because they always live
in the namespace of module where there are defined, not in the module
(or it's namespace) of the target. Therefore if you augment, it is
your responsibility to generate SID file for your module
with augments / sx:structure / sx:augment-structure.

> I think that the DE (Expert: Michel Veillette, Alexander Pelov, Laurent
> Toutain), in consultation with NETMOD and CORE WG chairs should create a
> design team to do this work.
> Call it a hackathon project if that helps schedule it.

Sounds good.

> True, but maybe we need to do the work to know if the tools are working
> right?

I think Andy has a working version. The pyang, I believe, has all the
pieces ready, the pieces only need to be glued together.

> Is it time for another YANG-TOOLING conference call/meeting?
> Or should we do something in-person in Vienna?

Either option works for me.


Best regards,
Vojtech Vilimek
CZ.NIC z.s.p.o.

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