In the ID, you write: } 5. Changes to Registrar Behavior } The Registrar is the component that authenticates the pledge, makes } authorization decisions, and distributes vouchers. If the extensions are } supported, the Registrar MAY process a security profile selector request from } owner that identifies what underlying security parameters need to be enabled } in the security-profile-selector send down to the pledge as part of these } extensions.
1. You haven't understood how vouchers are used. The Registrar does not create them. 2. Unfortunately, the result of the year+ effort to provide a way to incrementally extend RFC8366 has failed due to limitations in YANG. Under the hood, it ought to be trivial to do in the JSON or CBOR. RFC8366bis simply revises the module as a whole, and your extension would have to go into 8366bis, if it made sense. 3. 32 is not enough bits. Using bits is probably a failure. Probably you need an IANA registry of posture definitions, and it probably needs to have an integer per item. There is probably need to have vendor extensions, probably by PEN. -- 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
