Re: [core] Robert Wilton's Discuss on draft-ietf-core-sid-21: (with DISCUSS and COMMENT)

On Fri, Oct 20, 2023 at 8:58 AM Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Thank you for persisting through this Rob!
>
> Robert Wilton via Datatracker <noreply@ietf.org> wrote:
>     > related aspects for creating/managing SID files in drafts that I want
>     > to ensure
>     > that the IESG is at very least aware of and happy with.
>
>     > (1) p 23, sec 6.4.3.  Publication of the ".sid" file
>
>     > For a YANG module approved for publication as an RFC, a ".sid" file
>     > SHOULD be included in the Internet-Draft as a source code block.
>
>     > I'm wondering if this is really the best approach.  I.e., I think to
>     > guarantee
>     > that the SID file is correct at the point of pulication (e.g., if
> names
>     > of YANG
>
> For the first year or two, with a new YANG module I strongly think that the
> authors need to review the resulting sid file (the allocations) to be sure
> that they are correct.
>
> Yes, of course, IANA or RPC SHOULD double check.
> It is here that we might run into bugs in pyang that the RPC will need
> support on, and this is why I keep poking the Tools team about pyang
> maintenance.
>
> I also want to push back on the idea that SIDs are just for constrained
> environments: we have heard from Andy that every byte counts in bigger
> networks, and that comparing uin63s is gonna be way faster than XML string
> compares.
>
>
Agreed.
The use-case for YANG Push has always been an unconstrained device in a
constrained network.

There is no way that SID files from RFCs can just be generated by IANA and
published.
An Expert Review Team should be responsible for that. The tools and
procedures are too new.
Multiple independent verification tools are still needed.

Generating and maintaining a SID file database for a large YANG module set
is complicated.
That is, a robust, complete, and 100% correct SID file database.
A flawed and incomplete database is much easier to create. ;-)

For YANG Push using CBOR, any YANG module could need a SID file.
IMO the CORE WG is not responsible for figuring out this SID database.
It needs more work on tools and procedures, probably in the NETMOD WG.

--
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
>            Sandelman Software Works Inc, Ottawa and Worldwide
>
>
>
Andy

>
>
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core
>