I have merged in the YANG extensions that were done in BRSKI-CLOUD, which I had missed before. You can see it in the diff:
> A diff from the previous version is available at: > https://author-tools.ietf.org/iddiff?url2=draft-ietf-anima-rfc8366bis-06 Only, you can't, because the YANG didn't process correctly! Let's see, okay: https://author-tools.ietf.org/iddiff?url2=draft-ietf-anima-rfc8366bis-07&url1=draft-ietf-anima-rfc8366bis-05 The pull request to remove the YANG from brski-cloud is at: https://github.com/anima-wg/brski-cloud/pull/23 The pull request to remove the YANG from constrained-voucher is at: https://github.com/anima-wg/constrained-voucher/pull/262 The pull request to remove the YANG from brski-ai is at: https://github.com/anima-wg/anima-brski-prm/pull/78 It might be better to allow the WGLCs to proceed and *then* move the YANG as being less confusing to reviewers. It might also be better to change rfc8366bis from a document that obsoletes RFC8366, to one that just Updates (Amends) the RFC8366's YANG, and has no other text. -- Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
