Content-Type: multipart/alternative;
 boundary="------------H8u9ypJHZ2lO5t0tt0Ov8Oy0"
Message-ID: <3b3929bb-32ec-4855-bf8d-eadca96dc796@iotconsultancy.nl>
Date: Wed, 22 Oct 2025 17:24:18 +0200
MIME-Version: 1.0
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <5124478f-eb4e-485c-aa15-501a9ba99e98@iotconsultancy.nl>
 <27008.1760999205@obiwan.sandelman.ca>
Content-Language: en-US
From: Esko Dijk <esko.dijk@iotconsultancy.nl>
Organization: IoTconsultancy.nl
In-Reply-To: <27008.1760999205@obiwan.sandelman.ca>
Message-ID-Hash: R7W3S5KAM3HI6OEHRX3ZTUMSDRCP5DLH
CC: "anima@ietf.org" <anima@ietf.org>
Precedence: list
Subject: =?utf-8?q?=5BAnima=5D_Re=3A_WGLC_review_of_draft-ietf-anima-rfc8366bis-14_/_?=
 =?utf-8?q?Invite_for_a_SID_party?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/anima/RxVFhp5I3T63Ezlet8Fig6kvdFs>

This is a multi-part message in MIME format.
--------------H8u9ypJHZ2lO5t0tt0Ov8Oy0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

During the hackathon we might take a closer look into the YANG and 
8366bis details?

For me the "make" didn't work immediately due to a missing semicolon - 
created https://github.com/anima-wg/voucher/pull/87 for this.
Also my (latest) pyang 2.7.1 doesn't support the "--generate-sid-file" 
option, but it needs to be "--sid-generate-file".

Doing custom PRs/patches for pyang is also an option at the hackathon. 
But in this case the build process would only work for those people 
who've installed these patches.

When I try SID generation on my machine, the file and the paths look 
really different: for example the "choice nonceless" and "choice 
pinning" elements also gets a name assigned in the overall 
path/identifier. And a SID value also.
Overall it looks completely different from our draft - maybe I've used 
the wrong parameters?

   pyang --verbose --sid-generate-file 2450:50 ietf-voucher-test.yang

This doesn't preserve the previously defined SID values in our draft, 
however.

One way to possibly get rid of some issues would be removing all 
"choice" elements from the YANG. This avoids SID values being allocated 
for the choice elements themselves.

(To be continued...)

Esko


On the PYANG tool related issues:

On 21-10-2025 00:26, Michael Richardson wrote:
> Esko Dijk<esko.dijk@iotconsultancy.nl> wrote:
>      > I've reviewed draft-ietf-anima-rfc8366bis-14 as part of the WGLC; with
>      > issues/questions listed below and some editorial updates proposed in a PR.
>      > (See:https://github.com/anima-wg/voucher/pull/85)
>
> Thank you.
> I've been fighting PYANG things for a few hours (DAYS?!), and I've run out of
> time now.  So I'm posting -16 with updates that I have.  More details later.
>
>      > *** Section 7.4
>
>      > Some items have 2 SIDs assigned: additional-configuration-url, est-domain,
>      > expires-on.
>
> Yes, this is the thing I'm fighting.
>
>      > *** Section 7.5
>
>      > "In JSON serialization, these extensions require a unique name, and this MUST
>      > be allocated by IANA. The name MUST be the same as the YANG module name. "
>      -> this is unclear to me. If every extension has the same name, it's not
>      > unique and not useful.
>
>      > *** Section 8.1
>      > Again like in 7.1, why are some items/leaves outside of the "voucher"
>      > element?
>
> Yes. ARGH.
>
>      > In the YANG, the name of RFC XXXX differs from the actual name - same thing
>      > as in 7.3.
>
> The RPC will s/XXXX/1234/ when they assign the number.
>
> I got as far as:
>
>      > The boilerplate BCP text is included twice in the same field:
>
> Sorry.
>
> --
> Michael Richardson<mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
>             Sandelman Software Works Inc, Ottawa and Worldwide
>
>
>
>

-- 
*IoTconsultancy.nl* | Email/Teams: esko.dijk@iotconsultancy.nl | +31 6 
2385 8339

--------------H8u9ypJHZ2lO5t0tt0Ov8Oy0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    During the hackathon we might take a closer look into the YANG and
    8366bis details?<br>
    <br>
    For me the "make" didn't work immediately due to a missing semicolon
    - created <a class="moz-txt-link-freetext" href="https://github.com/anima-wg/voucher/pull/87">https://github.com/anima-wg/voucher/pull/87</a> for this.<br>
    Also my (latest) pyang 2.7.1 doesn't support the
    "--generate-sid-file" option, but it needs to be
    "--sid-generate-file". <br>
    <br>
    Doing custom PRs/patches for pyang is also an option at the
    hackathon. But in this case the build process would only work for
    those people who've installed these patches.<br>
    <br>
    When I try SID generation on my machine, the file and the paths look
    really different: for example the "choice nonceless" and "choice
    pinning" elements also gets a name assigned in the overall
    path/identifier. And a SID value also.<br>
    Overall it looks completely different from our draft - maybe I've
    used the wrong parameters?<br>
    <br>
      pyang --verbose --sid-generate-file 2450:50 ietf-voucher-test.yang<br>
    <br>
    This doesn't preserve the previously defined SID values in our
    draft, however.<br>
    <br>
    One way to possibly get rid of some issues would be removing all
    "choice" elements from the YANG. This avoids SID values being
    allocated for the choice elements themselves.<br>
    <br>
    (To be continued...)<br>
    <br>
    Esko<br>
    <br>
    <br>
    On the PYANG tool related issues: <br>
    <br>
    <div class="moz-cite-prefix">On 21-10-2025 00:26, Michael Richardson
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:27008.1760999205@obiwan.sandelman.ca">
      <pre wrap="" class="moz-quote-pre">
Esko Dijk <a class="moz-txt-link-rfc2396E" href="mailto:esko.dijk@iotconsultancy.nl">&lt;esko.dijk@iotconsultancy.nl&gt;</a> wrote:
    &gt; I've reviewed draft-ietf-anima-rfc8366bis-14 as part of the WGLC; with
    &gt; issues/questions listed below and some editorial updates proposed in a PR.
    &gt; (See: <a class="moz-txt-link-freetext" href="https://github.com/anima-wg/voucher/pull/85">https://github.com/anima-wg/voucher/pull/85</a>)

Thank you.
I've been fighting PYANG things for a few hours (DAYS?!), and I've run out of
time now.  So I'm posting -16 with updates that I have.  More details later.

    &gt; *** Section 7.4

    &gt; Some items have 2 SIDs assigned: additional-configuration-url, est-domain,
    &gt; expires-on.

Yes, this is the thing I'm fighting.

    &gt; *** Section 7.5

    &gt; "In JSON serialization, these extensions require a unique name, and this MUST
    &gt; be allocated by IANA. The name MUST be the same as the YANG module name. "
    -&gt; this is unclear to me. If every extension has the same name, it's not
    &gt; unique and not useful.

    &gt; *** Section 8.1
    &gt; Again like in 7.1, why are some items/leaves outside of the "voucher"
    &gt; element?

Yes. ARGH.

    &gt; In the YANG, the name of RFC XXXX differs from the actual name - same thing
    &gt; as in 7.3.

The RPC will s/XXXX/1234/ when they assign the number.

I got as far as:

    &gt; The boilerplate BCP text is included twice in the same field:

Sorry.

--
Michael Richardson <a class="moz-txt-link-rfc2396E" href="mailto:mcr+IETF@sandelman.ca">&lt;mcr+IETF@sandelman.ca&gt;</a>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide




</pre>
    </blockquote>
    <br>
    <div class="moz-signature">-- <br>
      <b>IoTconsultancy.nl</b> | Email/Teams:
      <a class="moz-txt-link-abbreviated" href="mailto:esko.dijk@iotconsultancy.nl">esko.dijk@iotconsultancy.nl</a> | +31 6 2385 8339</div>
    <br>
  </body>
</html>

--------------H8u9ypJHZ2lO5t0tt0Ov8Oy0--