Great, thanks - that looks all okay now.

Esko

On 4/28/26 12:08, Göran Selander wrote:
Hi Esko, hi Amanda,

Thanks for your careful reading. The corrections are now included in the github Editor's copy [1].

Please advise if any further actions are requested.

Thanks,
Göran

[1] https://cose-wg.github.io/CBOR-certificates/draft-ietf-cose-cbor-encoded-cert.html


*From: *Esko Dijk <[email protected]>
*Date: *Tuesday, 28 April 2026 at 10:48
*To: *[email protected] <[email protected]>
*Cc: *Göran Selander <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]> *Subject: *Re: [IANA #1442481] expert review for draft-ietf-cose-cbor-encoded-cert (core-parameters)

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
>
_______________________________________________
COSE mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to