Hi,
The Content Type name needs to be updated I believe. Applying the
following rules:
* encoding of parameters per Section 5.6.6 of RFC 9110, using a
semicolon as separator between all parameters
* rule 2 of Section 4.1.4 of draft-ietf-core-cf-reg-update-09, make
parameters unquoted
* rule 1 of Section 4.1.4 of draft-ietf-core-cf-reg-update-09, implies:
parameter names in lowercase
the resulting types would be:
application/aif+cbor;toid=oscore-gname;tperm=oscore-gperm
application/aif+json;toid=oscore-gname;tperm=oscore-gperm
Some of these results may be unexpected, so I'm okay to have some
discussion around this if needed!
For the remaining items of the registration request I don't have
comments: these look good, and agree on the proposed CF numbers.
best regards,
Esko
On 24-9-2025 02:05, Sabrina Tanamal via RT wrote:
Hi Esko (cc: ace wg),
As the designated expert for the CoAP Content-Formats registry, can you review
the proposed registrations in Section 16.9 of
draft-ietf-ace-key-groupcomm-oscore-18 for us? Please see
https://datatracker.ietf.org/doc/html/draft-ietf-ace-key-groupcomm-oscore-18
The due date is October 7th.
If these are OK, when the IESG approves the document for publication, we'll
make the registrations at:
https://www.iana.org/assignments/core-parameters
Thanks,
Sabrina
--
*IoTconsultancy.nl* | Email/Teams: [email protected] | +31 6
2385 8339
_______________________________________________
Ace mailing list -- [email protected]
To unsubscribe send an email to [email protected]
