[yang-tooling] Management of SID files

[Andy Bierman <[e-mail]>]

Hi,

I think SID file management is a tooling problem, because it would be
unwise to attempt such an endeavour without automation, or at least
new procedures.

Some questions to consider:

A) How do authors publish (unstable) Internet-Draft SID files?
B) How do users 'extract' SID files for use in local tooling?
C) How do WGs make (stable) RFC SID files "IANA-ready"?
D) How does IANA publish (stable) RFC SID files?
E) How does IANA (or any megarange owner) manage and allocate Assignment Ranges?
F) How do users manage and update YANG and SID files together?

Start with (A)

IMO, including SID files in I-Ds does not scale well.
It may be OK for some constrained modules with small SID files,
but not for large modules that may be used in YANG Push.

E.g ietf-te@2024-02-02:
  -  SIDs: 1704
  -  lines: 10266
  -  bytes: 453091

It seems clear to me that the SID files need to be hosted on github instead of
published in I-Ds or RFCs. The YANG modules could have a simple
YANG extension to link the SID file:

    yangtool:sid-file-source "... stable URL for the SID file ...";

The IANA section gets lost when the YANG module is extracted, so
a new extension is needed to help solve (B) and (F).

I have been working on problem (E) a bit, but that is not in scope yet.


Andy