David Dong via RT <[email protected]> wrote: > Hi Michael,
> Thank you for the clarifications.
> The YANG-SID Ranges were added as RFC 7120 early allocations (and still
> are in the registry there), but the YANG-SID Modules themselves have
> not been:
Yes, I don't quite remember when we changed this around, but I did look at
the registry to see that yeah, they were changed to early allocations.
I keep hoping we'll slide in under the 2yr line :-)
> Regarding the YANG SID files, we're not familiar with how to extract
> these files and to perform any needed updates on them. Our
> understanding and instructions, as per RFC 9595 Section 6.4.3, have
> been that the designated experts will provide the files for us to post.
The "normal" kramdown-rfc-extract-sourcecode, etc. should work.
I hope the VELOCE process update will make this simpler and clearer soon.
> We're also not sure when to post these SID files; our understanding
> have been that we would post the SID files along with the YANG Modules
> after the document has been published as an RFC, since we post YANG
> Module files after the document has been published as an RFC, but we've
> also asked for clarifications in our Last Call review sent earlier
> today. This is the first time we're having to post SID files as well.
:-)
I think that they get posted at the same time as the YANG module.
--
Michael Richardson <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =- *I*LIKE*TRAINS*
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list -- [email protected] To unsubscribe send an email to [email protected]
