Hi Christian, I'm not a chair of any of the groups involved, but here are my two cents.
As a principle, work should generally be done where the experts are. For most drafts in OAUTH, the amount of work needed on parts that require CBOR/COSE/CWT expertise will be limited, and OAUTH-related concerns will dominate the design decisions. Given the overlaps between the people in the groups, simply keeping the WGs with the other experts in the loop should be all that is needed (acknowledging that this might mean a somewhat more limited level of attention by the other experts). For a somewhat more fundamental work with some groundbreaking CBOR/CWT usage, such as SD-CWT, that may be different (in this case, we actually did have another WG to do the work). In general, the document authors and the OAUTH chairs should be in a good position to point out where specifically CBOR/CWT expertise might be helpful in a review. I read your message as a way of “keeping the ACE/COSE/CBOR... WGs in the loop”, and I will add the document to my reading list. Grüße, Carsten > On 2026-01-16, at 14:42, Christian Bormann > <[email protected]> wrote: > > Hello ACE WG, > > We are currently finalising the OAuth Token Status List draft > (https://datatracker.ietf.org/doc/draft-ietf-oauth-status-list/). While the > draft started with only JSON-based representations, upon request we added a > CBOR/CWT based variant. > > We are aware that CBOR/CWT-related work is typically the domain of the SPICE > or ACE WGs and outside of OAuth. However, given that the draft consists of an > encoding-agnostic core data model and only adds JSON and CBOR encoding on > top, we felt that this adds more benefits for using a consistent method > across these two common data representation formats, which have a history of > shared standards. The CBOR-specific parts are currently a rather small part > of the overall draft and mirror the JSON-based definitions. > > Are there any concerns with the current situation of including the CBOR/CWT > parts in the draft? Could you please provide feedback on the situation and > our proposal to keep the CBOR/CWT parts in the current draft, preferably > within ~2 weeks. > > Best Regards, > Christian + Paul + Tobias > _______________________________________________ > Ace mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ Ace mailing list -- [email protected] To unsubscribe send an email to [email protected]
