IETF Logo Mail Archive

[yang-tooling] Re: PYANG evolution

Carsten Bormann <cabo@tzi.org> Mon, 23 March 2026 16:31 UTC

Return-Path: <cabo@tzi.org>
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 5A738CFFC109 for <yang-tooling@mail2.ietf.org>; Mon, 23 Mar 2026 09:31:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 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_LOW=-0.7, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=tzi.org
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 mpI2BdCTMvd5 for <yang-tooling@mail2.ietf.org>; Mon, 23 Mar 2026 09:31:52 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (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 78AB9CFFC100 for <yang-tooling@ietf.org>; Mon, 23 Mar 2026 09:31:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=tzi.org; s=2019; t=1774283511; bh=2S6T3SvXS9dCo4avmZ6h9uYUZEbrgVjTCg6PPeS95E8=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=lmMBFJQTq9I3b6e11bjZ4ysuRKKEWoULUe7padGb9og6PwL97XgenOi0dlEvfbExW Mheoeq3zdN/j1D32UvF8vSCZi04FYa/LGzWVJa6X/WFXvRZ68jTXc6MoXnfKvSLmc+ 7MJ8qLL0Z+iTgqs6PDEO6stdywAQzYYzYfjjIRIJlCHhLm0uOObelrQuFyKJO5DaXa gIKa78Wii+gesUr8sF7Y3QxdmaCXJ0YvtW4ujD/KooqFsgvdVHjrbkU19PNwvFhpeo kUHJJMLg84fGn6FKaV3bkZs9TIv4TPaZXmJzDvols2vB6ZtB59bD67LB0pVKKkvhmv mHsxjsjp4ZvEQ==
Received: from [192.168.217.132] (p5089a635.dip0.t-ipconnect.de [80.137.166.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4ffdwl3DmDzDCbX; Mon, 23 Mar 2026 17:31:51 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <b6b8d979-e5cd-45c4-a5bc-a6c55e409207@nic.cz>
Date: Mon, 23 Mar 2026 17:31:51 +0100
X-Mao-Original-Outgoing-Id: 795976310.746417-404ff447a1286f5be1df9b5fbebda355
Content-Transfer-Encoding: quoted-printable
Message-Id: <4130EF89-220D-4907-BFF0-93AAC36869B6@tzi.org>
References: <5f6fa282-8c1e-43e2-8334-e5a025d526a1@nic.cz> <470c14d2-8d96-4dc7-b224-8b4e2ddfd44d@nic.cz> <AA31955C-D8E8-4E4E-9799-FBF2AB321F7B@tzi.org> <cec3bc52-c0e5-40b0-9e65-aa81c82a6a6e@nic.cz> <233FAF50-4A4F-4481-A215-5A31BE62217B@tzi.org> <CABCOCHQAeC1T3kjUavb7iSepeJAWn4E1Lqoof_RFL2QFXwvDiw@mail.gmail.com> <b6b8d979-e5cd-45c4-a5bc-a6c55e409207@nic.cz>
To: Vojtech Vilimek <vojtech.vilimek@nic.cz>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
X-FromAuthMilter: ok
Message-ID-Hash: 6HI4MOPW3SR3GSMIRO3EAU3RPCUM2Y2P
X-Message-ID-Hash: 6HI4MOPW3SR3GSMIRO3EAU3RPCUM2Y2P
X-MailFrom: cabo@tzi.org
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
CC: Andy Bierman <andy@yumaworks.com>, "yang-tooling@ietf.org" <yang-tooling@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [yang-tooling] Re: PYANG evolution
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/oCdCE9WRO3_HD6Px6SvZND0EUZw>
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>

On 2026-03-23, at 17:10, Vojtech Vilimek <vojtech.vilimek@nic.cz> wrote:
> 
> Is something like RESTCONF + YANG-CBOR desired and/or planned?

The intention of RFC 9254 was to make this “just work”.

Now I’m not a NETCONF or RESTCONF expert, so I’m not sure I can help a lot here.

YANG-CBOR should be covering what is called the “message-body” in RFC 8040.
There is a URI that governs each RESTCONF interaction.
YANG-CBOR uses module names instead of prefixes when using name-based identifiers, and obviously SIDs mapping to those when using SID-based identifiers.

It seems we’ll need to piece together a more complete set of examples demonstrating the use of these two kinds of identifiers, targeting NETCONF and RESTCONF.
draft-ietf-core-comi-21.txt has CORECONF (COMI) RPC and action examples we could align with (e.g., section 3.5 for RPC and action).

It seems we should be doing this over at core@ietf.org, not here.

Grüße, Carsten

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