[Secdispatch] Updating rfc4398 for CBOR Encoding

[Robert Moskowitz <[e-mail]>]

We are working to use 4398 CERT RR in

https://datatracker.ietf.org/doc/draft-ietf-drip-registries/

We have specialized "Endorsements" objects that provide proof of 
registration.  I won't go into the whole DRIP architecture here, but 
CERT RR is an excellent fit.

We CAN just use the type 254 "OID Private" to store our objects, using 
some OID just to hold our stuff, and call it a day.

But....

We are updating this draft for our Endorsements to be CBOR encoded with 
a cononical representation to send over the very constrained DRIP link.  
Moving to CBOR makes this work of interest to other uses.

and there is:

https://datatracker.ietf.org/doc/draft-ietf-cose-cbor-encoded-cert/

On the COSE list, we have discussed that a single CBOR type for CERT RR 
would serve the purpose.  It will be then the CBOR value that informs 
what is stored in the RR.

So what is needed:

Someone from the community that "owns" 4398 to step forward and help 
author a very simple draft for adding CBOR to the list of types 
supported in the CERT RR.

How do we proceed and who can provide that "officialness" to update 4398?


Thanks

Bob