Hi, I support adoption of the draft, since we need it as part of Anima.
A couple of points seem to need attention before we get to WGLC: > NOTE: AT THIS TIME, THE SIGNING STRATEGY HAS NOT BEEN SELECTED I think that needs to resolved. > Implementations MUST ensure devices have > an accurate clock when shipped from manufacturing facilities, and > take steps to prevent clock tampering. Doesn't that pose a problem for very low-end devices? That is not a concern for devices that are in scope for Anima, but I understand the applicability is intended to be general. As such, the MUST seems impossible to enforce. Shouldn't the formulation be like this: Implementations SHOULD ensure devices have an accurate clock when shipped from manufacturing facilities, and MUST then take steps to prevent clock tampering. If it is not possible to ensure clock accuracy and integrity, implementations MUST disable the aspects of the solution having clock sensitivity. By the same logic, > It is important to note that implementations SHOULD NOT rely on NTP > for time, as it is not a secure protocol. I think that should be a MUST NOT. Otherwise product managers will ignore it. Regards Brian On 14/12/2016 05:57, Sheng Jiang wrote: > Hi, all, > > This message starts a two-week adoption call for Voucher work, which is a > straight-forward definition of common voucher formats as needed in both ANIMA > and NETCONF WG. Although it was submitted to netconf WG originally, after > discussion with netconf chairs and corresponding ADs, we all agree ANIMA is > the right home for it. If adopted, the authors hope to be ready for WGLC > before Chicago, giving that our milestone work item bootstrap key > infrastructure normatively refer it. > > Title: Voucher and Voucher Revocation Profiles for Bootstrapping > Protocols > > Authors : Watsen, et al. > Filename: draft-kwatsen-netconf-voucher > > https://tools.ietf.org/html/draft-kwatsen-netconf-voucher-00 > > Please express your support or rejection. If you think this document should > _not_ be adopted, please also explicitly indicate the reasons. > > This adoption call will end on Dec. 27, 2016. > > Regards, > > Sheng > _______________________________________________ > Anima mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/anima > _______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
