See RFC 9595 process: the finalized .sid file is handed over to IANA but
*not* included in the draft.
So we still have some time to fix the finalize bug - don't need it right
away. After IETF LC , or during RFC editing, seems a good moment.
Nice to also auto-build the final .sid file using the makefile, as long
as it doesn't get included in the I-D :)
Esko
On 14-1-2026 18:07, Michael Richardson wrote:
Esko Dijk<[email protected]> wrote:
> 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",
Oh, yes.
I think that pyang ought to have updated it.
We haven't run --sid-finalize yet.... I added a makefile target to do that,
and pyang correctly updates things.
I think we should run --sid-finalize after IETF LC.
> There's also a duplicate import of one module, as below, in B.2.
> {
> "module-name": "ietf-voucher",
> "module-revision": "2023-01-10"
> }
I see that --sid-finalize creates even more duplicates, so that's a bug.
https://github.com/core-wg/pyang/issues/17
--
Michael Richardson<[email protected]> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
--
*IoTconsultancy.nl* | Email/Teams: [email protected] | +31 6
2385 8339
_______________________________________________
Anima mailing list -- [email protected]
To unsubscribe send an email to [email protected]
