Hi Dear author, I'm assigned to review draft-ietf-lamps-automation-keyusages-06.

General status: Ready
This document is a concrete proposal of defining 4 new KeyPurposeIds of a certificate. The definition and the use case/background are well described, and ready for publish.

My only minor comment is regarding to the title, that the usage of the 4 new KeyPurposeIds is summarized as “Automation”. I think 3 of them (id-kp-configSignin, id-kp-trustanchorSigning, id-kp-updateSigning) are pretty general and theoretically could be used in any network systems/nodes.
I can understand it’s not easy to summarize the usage. If there is consensus on changing the title, maybe considering simply list the key purposes in the title? (E.g. “X.509 Certificate Extended Key Usage (EKU) for trust anchor configuration files, software and firmware update, and safety-critical communication”); if not, pls ignore this comment.

B.R.
Bing