Reviewer: Charlie Kaufman
Review result: Has nits

I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG.  These comments were written primarily for the benefit of the security area directors.  Document editors and WG chairs should treat these comments just like any other last call comments.

This Standards Track ID extends a family of protocols for limited function devices to obtain certificates from their surrounding environment with the assistance of an on-line manufacturer's authority that can authenticate information as coming from their device. It extends the BRSKI (RFC8995) protocol to deal with devices that prefer to accept incoming initialization requests rather than initiating outbound requests. It does this be defining a new node called a "registrar-agent" that acts as a client to both the to-be-registered "pledge" and the domain registrar.

The protocol is more elaborate that I would have thought necessary, but I could find no problems with it. 

Typos:
p1 "To establishment the" -> "To establish the"
p4 "In this scenarios it is" -> "In this scenario it is"
p5 "defined i this" -> "defined in this"
p8 "as describe in" -> "as described in"
p8 "it SHOULD initiate to that Registrar" --- initiate what? a request? a connection?
p9 "This operational parameters" -> "These operational parameters"
p9 "presume the" -> "presumes the"
p11 "constraint environments" -> "constrained environments"
p12 "endpoints were the" -> "endpoints where the"
p12 "endpoints were additional" -> "endpoints where additional"
p45 "a manufactures pledge" -> "a manufacturer's pledge"
p64 "on misusage" -> "of misuse"
p64 "an registrar-agent" -> "a registrar-agent"
p64 "rouge" -> "rogue"