Srihari Raghavan (srihari) <[email protected]> wrote: > Agreed that MASA is the signing authority and the draft is meant to > convey that the owner can influence the choice by way of parameterized > inputs to the MASA APIs. So, owner can be presented with a 'security > profile selector' input via the MASA external APIs and when the owner > provides the PDC and the selector input values, MASA can then go ahead > and create the voucher with appropriate security profile settings > (after verification and validation) for the device.
okay, that's a entire API from Registrar to MASA which you have to design and document. And you mention SZTP, and it doesn't have that link. I think that there are better ways to do accomplish the configuration, such as extending the BRSKI-EST link with new actions. -- Michael Richardson <[email protected]>, Sandelman Software Works -= IPv6 IoT consulting =- *I*LIKE*TRAINS*
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
