Hi, Chairs: I have read the latest version of this draft and support adoption of this work. Here are a few comments:
1. Since we still reuse rc:yang-data to model vouch-artifact, I believe the model structure in section 5.1 of RFC8366 should keep as is. 2. Secondly, vouch-artifact doesn’t need to be coupled with RESTCONF protocol message, suggest to use YANG extension statement “structure” defined in RFC8791 to replace yang-data. 3. Do we expect iana-voucher-assertion-type to be changed in the future, e.g., add a new enum value? Does it make sense to change voucher-assertion typedef into identity data type. -Qin 发件人: Anima [mailto:[email protected]] 代表 Sheng Jiang 发送时间: 2021年12月6日 14:57 收件人: [email protected] 抄送: [email protected]; Toerless Eckert <[email protected]> 主题: [Anima] Call for adoption: draft-richardson-anima-rfc8366bis, ends December 19th, 2021 Hi, all ANIMAer, This message starts a two-week adoption call for draft-richardson-anima-rfc8366bis, which we have traced a few discussion and think the WG is interested in. The adoption call ends December 19th, 2021. Title: A Voucher Artifact for Bootstrapping Protocols Name: draft-richardson-anima-rfc8366bis-04 Authors: K. Watsen, M. Richardson, M. Pritikin and T. Eckert URL: https://datatracker.ietf.org/doc/draft-richardson-anima-rfc8366bis/ IPR: No IPR disclosures have been submitted directly on draft-richardson-anima-voucher-delegation This document is intended to become a standards track ANIMA WG document. Please express your support or rejection. If you think this document should _not_ be adopted, please also explicitly indicate the reasons. Regards, Sheng
_______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
