Re: [core] CoRECONF Topic Interim: CORECONF (Re: CoRE WG Virtual Interim 2023-03-15)

Michael Richardson <> Thu, 16 March 2023 08:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BE7EBC15153F for <>; Thu, 16 Mar 2023 01:20:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id T_9KlcfmuYOm for <>; Thu, 16 Mar 2023 01:20:29 -0700 (PDT)
Received: from ( []) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by (Postfix) with ESMTPS id A3819C14F748 for <>; Thu, 16 Mar 2023 01:20:29 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTPS id 910EC1F47D; Thu, 16 Mar 2023 08:20:26 +0000 (UTC)
Received: by (Postfix, from userid 1000) id 2CE17A10BC; Thu, 16 Mar 2023 04:20:25 -0400 (EDT)
Received: from dyas (localhost []) by (Postfix) with ESMTP id 2AC46A013E; Thu, 16 Mar 2023 08:20:25 +0000 (GMT)
From: Michael Richardson <>
To: Carsten Bormann <>, " WG (" <>
In-reply-to: <>
References: <> <>
Comments: In-reply-to Carsten Bormann <> message dated "Wed, 15 Mar 2023 13:30:02 +0100."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 16 Mar 2023 08:20:25 +0000
Message-ID: <2630676.1678954825@dyas>
Archived-At: <>
Subject: Re: [core] CoRECONF Topic Interim: CORECONF (Re: CoRE WG Virtual Interim 2023-03-15)
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 16 Mar 2023 08:20:33 -0000

Carsten Bormann <> wrote:
    > Since we have a number of issues in the area of CORECONF and other
    > YANG-related efforts, we decoded to focus today’s interim on a single
    > wider topic: bringing the YANG and CoRE ecosystems closer together.

I didn't see this until the meeting was starting, at which point I was on a
train.   I tuned in for part of it, decamped to my hotel room, and caught the
end of things.  I guess I might watch the recording to understand what
YANG-CBOR stuff I missed.

    > * SID completeness

    > It does not seem the PYANG tool we are using to generate the SID file
    > generates a complete set of SIDs (thank you for pointing this out,
    > Jernej [4]).  So do we agree what a complete set would be?  How do we
    > get PYANG to emit this complete set, or do we add the missing parts
    > manually?  (Of course, new SIDs can always be added, so missing one is
    > not catastrophic.)

    > The LPWAN draft cited above proposes the specific allocations for
    > certain LPWAN protocols. How do we check a document like this?  Is it
    > complete?

I have experience with the, with some more unmerged patches related to
the last stable/etc. set of changes.  I have fixed it to allocate for
sx:structure nodes as well as yang-rest.

    > [4]:

I seem to have skipped over that email last week.
It is certainly true that does allocate many things.

My take on this is that I can't validate code paths with test data, and I
don't have enough YANG-fu to understand input and output parts, so I didn't
attempt to fix that.  I would be happy to review patches though.

pyang now has a reasonable number, if somewhat tedious at times, set of
regression tests, including SID allocation tests.  I won't be in Yokohama
(Hackathon), but I'm happy to sit down with someone with screen(1) and jitsi
and pair program a solution.

]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]        |   ruby on rails    [

Michael Richardson <>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*