[moving anima list to BCC]
>> [2] https://github.com/YangModels > > okay, so at this point, my I think that pulls from YangModels github > (directly, or wget'ing the rawusercontent file...) is the simplest. seems sensible. > Kent, doeds 8366 replace: > https://github.com/YangModels/yang/blob/master/standard/ietf/DRAFT\ > /ietf-zerotouch-ownership-voucher.yang > ?? Yes. That module is a stale holdover from back before when we moved the voucher module into its own draft, and moved that draft to the ANIMA WG. Joe/Benoit, maybe the scripts could somehow track modules extracted from I-Ds (not RFCs) to see when old modules go away, and then delete those old modules? Consider this history: zerotouch-08 (April 2016) is the last draft to define ietf-zerotouch-ownership-voucher zerotouch-09 (July 2016) renamed the module to "example-zerotouch-ownership-voucher" zerotouch-10 (October 2016) no longer had the module at all draft-kwatsen-netconf-voucher-00 (October 2016) is when "ietf-voucher" began draft-kwatsen-anima-voucher-00 (December 2016) replaced draft-kwatsen-netconf-voucher draft-ietf-anima-voucher-00 (January 2017) replaced draft-kwatsen-anima-voucher RFC 8366 (May 2018) replaced draft-ietf-anima-voucher Kent _______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
