On Mon, Nov 24, 2025 at 3:11 PM Kent Watsen <[email protected]> wrote:
> Hi Andy, > > This seems like a good idea for authors of I-Ds. > Are you suggesting that non-authors would be required to maintain and use > a specific toolchain simply to read an Internet Draft? > Because there is no Internet Draft to read anymore? > > > Sorry for any confusion. The idea is that Datatracker would then itself > consume the built I-D, such that all existing behavior is maintained. The > only difference being that "TGZ" would be offered as a new optional > document format, if available. > > OK good > In case it's unclear, this idea hopes to: > > - simplify Shepherd/AD/IESG/Editor effort in trying to validate > examples > - enable better reconstruction of the original development environment > (for -biz efforts) > - tip-toe into the VELOCE effort > > > Dovetailing with Rob's comment, the examples used for coverage statistics > do NOT have to be in the I-D itself, in case having such potentially long > examples may distract from the value of the example in the I-D. > Personally, if not including the whole example, I'd likely use some > combination of `head` and `tail` to cherry-pick the meaningful part from a > fully-validated example. > > I hope that YANG SID files are eventually part of the process. These files will be really long, and the critical data will be in very long lines, reaching 200 chars. Line-wrapping these JSON files makes them unusable, so putting them in I-Ds and RFCs is really a waste of time. The URL of the SID file in the I-D or RFC is the only real solution for these files. > Kent > > Andy
_______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
