On Wed, May 31, 2023 at 02:13:11AM +0200, Robert Varga wrote: > On 30/05/2023 20.28, Jürgen Schönwälder wrote: > > It is unclear what "identical" means here. If two people extract a > > module from an RFC, they may not end up with identical byte > > sequences. So does white space matter when we talk about MUST be > > identical? What about comments? The problem is that the IETF still > > publishes YANG modules in RFCs instead of files. > > As for RFC vs. files, the mechanics of extracting of files from RFCs seems > to be well established, plus it is an IETF-owned cron job which updates > https://github.com/YangModels/yang/tree/main/standard/ietf/RFC -- so I would > (and I actually do) assume that is the normative source of byte-exact files.
I have YANG modules that were extracted years ago using some version of smistrip of the past. Do you believe my files extracted back then are byte-by-byte equivalent to what some cron job produces on some github repo somewhere today? Do you guarantee that the software behind the cron job will never ever be updated causing it to produce something where white space may differ? /js -- Jürgen Schönwälder Constructor University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <https://constructor.university/> _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
