Dear Esko, and all, Apologies for the very long delay. Please see responses inline marked [GS: … ].
From: David Dong via RT <[email protected]> Date: Saturday, 25 April 2026 at 08:12 To: Cc: [email protected] <[email protected]>; [email protected] <[email protected]> Subject: [IANA #1442481] expert review for draft-ietf-cose-cbor-encoded-cert (core-parameters) Dear Authors/Chairs/ADs, Following up again on this; please see below for comments from the designated expert. Please let us know how you'd like to address the comments regarding the removal of the spaces in Figure 20; this has been pending since February 11th and it looks like this document is on next week's telechat agenda. My colleague Amanda had already sent in some questions in addition to this pending expert review. Thank you. Best regards, David Dong IANA Services Sr. Specialist > On Wed Feb 11 10:42:22 2026, [email protected] wrote: > > Hello David & COSE WG, > > > > I've reviewed the request. One thing that surprised me was the > > presence > > of an optional parameter "usage" without any explanation for some of > > the > > media types defined. > > > > Is this a copy/paste error maybe? Has there been a media-types review > > of > > these already? > > This is attempting to mimick RFC 9360. Looking through the media types with the optional parameter “usage”, I noted two copy-paste errors ("usage" removed) and extended on the explanation in one of the occurrences. See https://github.com/cose-wg/CBOR-certificates/pull/359 Apart from this, I noted that there is missing text of the kind: "IANA is requested to …”, so, no I don’t think there has been a media-types review. Would adding this address this comment? > > Note that for all the CoAP Content-Format requests that do include a > > "usage" parameter, the explanation is present! So this does not > > hamper > > the present registration request. > > > > If in Figure 20 the spaces in "usage = chain" and "usage = c509" > > could > > be removed, per RFC 9876 Section 4.1.4, and the new media types are > > approved, then this request can be approved. > > This should be fixed in version -18 Best regards Göran > > regards > > > > Esko > > > > > > On 2/10/26 20:29, David Dong via RT wrote: > > > Dear Esko Dijk (cc: cose WG), > > > > > > As the designated expert for the CoAP Content-Formats registry, can > > > you review the proposed registrations in draft-ietf-cose-cbor- > > > encoded-cert-16 for us? > > > > > > Please see: > > > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-cose-cbor-encoded-cert%2F&data=05%7C02%7Cgoran.selander%40ericsson.com%7Cf54d48528de548817b7508dea291acb6%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C639126943719746780%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=1Si1EwdO15pwo7%2FPTHd4jb9NCCBvoAj9TFmS%2BeOJ0fg%3D&reserved=0<https://datatracker.ietf.org/doc/draft-ietf-cose-cbor-encoded-cert/> > > > > > > The due date is February 24th. > > > > > > If this is OK, when the IESG approves the document for publication, > > > we'll make the registration at: > > > > > > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.iana.org%2Fassignments%2Fcore-parameters%2F&data=05%7C02%7Cgoran.selander%40ericsson.com%7Cf54d48528de548817b7508dea291acb6%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C639126943719784391%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=QFeJYrn4zO4Bdf9%2Bxa%2BE0A2Z0Wj3jmVENx3UJef54Zw%3D&reserved=0<https://www.iana.org/assignments/core-parameters/> > > > > > > With thanks, > > > > > > David Dong > > > IANA Services Sr. Specialist
_______________________________________________ COSE mailing list -- [email protected] To unsubscribe send an email to [email protected]
