Hi,
I learnt that perfection can never be reached in the realm of YANG and
SID. It's so much more complex than most people realize if you count in
the procedures, variations, tooling (versions), and what could all go wrong.
Thanks for adding the SID files! I think that is what a "SID-guiding
developer" per RFC 9595 is supposed to do. Note that during RFC editing,
it gets taken out again (see Section 6.4.3 - "type-1" module developer)
I notice in the SID files that there are 4 occurrences of the string
"module-revision": "2023-01-10",
which I think were meant to point to the most recent YANG revision as
defined in this document, which is 2025-12-18.
There's also a duplicate import of one module, as below, in B.2.
{
"module-name": "ietf-voucher",
"module-revision": "2023-01-10"
}
Esko
On 11-1-2026 20:59, Michael Richardson wrote:
[email protected] wrote:
> Title: A Voucher Artifact for Bootstrapping Protocols
> Authors: Kent Watsen
> Michael C. Richardson
> Esko Dijk
> Max Pritikin
> Toerless Eckert
> Qiufang Ma
> Name: draft-ietf-anima-rfc8366bis-24.txt
Sorry for the duds as -22 and -23.
There was hiccup with my git, and I didn't publish the document I expected.
Turned out my changes were not actually committed, so the tag -a pointed at
the wrong place.
The important part is:
Appendix B. SID Allocations . . . . . . . . . . . . . . . . . . 51
B.1. SID Allocations for Voucher . . . . . . . . . . . . . . . 51
B.2. SID Allocations for Voucher Request . . . . . . . . . . . 54
This includes the two .sid files which are finally correct.
I hope we can get from WGLC into Mahesh's Q ASAP.
--
Michael Richardson<[email protected]> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
_______________________________________________
Anima mailing list [email protected]
To unsubscribe send an email [email protected]
--
*IoTconsultancy.nl* | Email/Teams: [email protected] | +31 6
2385 8339
_______________________________________________
Anima mailing list -- [email protected]
To unsubscribe send an email to [email protected]
