[Yang-sid-logistics] SIDs: YANG documents in process

[Sandy Ginoza <[e-mail]>]

Hi all,

Regarding SIDs, my understanding is that each YANG module will have a corresponding .sid file.  Section 6.5.3 of RFC 9595 [1] indicates that SID values are to be assigned via early assignment (as the documents are being developed) or permanently assigned to already published RFCs.  For our understanding, is there a date by which all YANG modules are expected to have .sid files, and how/where will this be enforced? 

We suggest considering incoming documents and documents already in the RFC Editor queue that do not have SID values as part of the "previously published YANG modules will not have SID allocations” rather than ask authors to update their documents during AUTH48 (for example, draft-ietf-netconf-ssh-client-server-40 [2] entered the RFC Editor queue in March; it has 3 YANG modules and no mention of “SIDs” or “.sid file”).  Are there any concerns with this approach?  

FYI: We currently have 15 active documents that have YANG modules in them, of which one is ready for publication and 9 should be entering AUTH48 in the coming weeks.  There are 8 additional documents with YANG modules in MISSREF.

[1] https://www.rfc-editor.org/rfc/rfc9595.html#section-6.5.3
[2] https://datatracker.ietf.org/doc/draft-ietf-netconf-ssh-client-server/

Thanks,
Sandy