Hello Göran & Amanda,
I've just provided inline comments in the PR that removes the "usage"
parameters where it was a copy/paste error. If not applicable, it should
say "N/A" to be fully clear.
This was the reason I brought up the media types review question: either
it wasn't reviewed yet, or the review was done but the issue wasn't
found. In the latter case we need to consider improving the review
process. I'm not sure that IESG review is the right place for this --
they would not specifically scrutinize media type registrations, I
think, but focus on the bigger picture. This review process was similar
to what we had for CoAP Content-Formats (IESG handled) until we fixed
that in RFC 9876. In any case, no additional text for review status
would be needed in the draft, from my perspective.
> - Figure 20 still shows "usage = chain" and "usage = c509" (instead
of "usage=chain" and "usage=c509") in -18.
Indeed, saw that too: the spaces still need to be removed. The RFC 9110
ABNF definition, as I read it, does not allow whitespace at both sides
of the '=' character.
regards
Esko
On 4/27/26 21:12, Amanda Baber via RT wrote:
Hi Göran, Esko,
A couple of notes:
- IANA actually doesn't send media types in IETF-stream documents to the
experts for approval. It's non-intuitive, but Ned Freed confirmed that this is
what's called for by RFC 6838. Instead, the approval comes from the IESG, as
part of approving the document. Instead, the RFC recommends that the authors
send the media types to the mailing list (currently [email protected]) for
an informal review.
- Figure 20 still shows "usage = chain" and "usage = c509" (instead of "usage=chain" and
"usage=c509") in -18.
thanks,
Amanda
On Sun Apr 26 10:56:25 2026, [email protected] wrote:
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]>; draft-ietf-cose-cbor-encoded-
[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]