Based on spec text, number of pages and implementation experience, the Constrained BRSKI protocol as currently defined is complex - this hinders adoption and deters implementers. But it doesn't need to be this complex.
Proposal is to simplify / streamline the protocol by:
Removing any of the unnecessary discovery operations from the description; and move into an Appendix or section at the end as optional (MAY) tweaks and extensions.
e.g. discovery of different voucher formats supported, alternative ports, or enrollment protocols, etc.
e.g. discovery of resources where to report voucher status and in what format to report
all these things have a sensible default that we should focus on.
Move any description on fields that are typically not used (e.g. x5bag or kid in certain places) to separate sections at the end.
Move RPK based operation without doing X.509 cert chain operations, to separate section at end. Or to a separate draft.
Based on spec text, number of pages and implementation experience, the Constrained BRSKI protocol as currently defined is complex - this hinders adoption and deters implementers. But it doesn't need to be this complex.
Proposal is to simplify / streamline the protocol by: