Thanks, Filip.
PR<https://github.com/ietf-wg-jose/draft-ietf-jose-fully-specified-algorithms/pull/29>
merged.
-- Mike
From: Filip Skokan <[email protected]>
Sent: Wednesday, February 26, 2025 11:28 AM
To: [email protected]
Cc: [email protected]; [email protected]; [email protected];
[email protected]
Subject: Re: [IANA #1413496] expert review for
draft-ietf-jose-fully-specified-algorithms (jose)
Hello David,
Note that, for the record, I have suggested changes to the document in its very
early (before WG adoption) stages, specifically about the new JOSE algorithm
identifier values themselves. I have also reviewed the document during its two
Working Group Last Calls.
Nevertheless, I have reviewed the IANA registrations section again and I find
them in good order wrt the JOSE registries. A small nit though: in
#section-4.4-3.2<https://www.ietf.org/archive/id/draft-ietf-jose-fully-specified-algorithms-07.html#section-4.4-3.2>
I found a typo. Proposed a PR to fix it
here<https://github.com/ietf-wg-jose/draft-ietf-jose-fully-specified-algorithms/pull/29>.
S pozdravem,
Filip Skokan
On Tue, 25 Feb 2025 at 18:12, David Dong via RT
<[email protected]<mailto:[email protected]>>
wrote:
Dear Sean Turner, Filip Skokan (cc: Mike Jones, jose WG, jose-reg-review
mailing list),
As the designated experts for the JSON Web Signature and Encryption Algorithms
registry, can you review the proposed registrations in
draft-ietf-jose-fully-specified-algorithms-07 for us? Please note that Mike is
one of the authors for this document.
Please see:
https://datatracker.ietf.org/doc/draft-ietf-jose-fully-specified-algorithms/
The due date is March 18.
If this is OK, when the IESG approves the document for publication, we'll make
the registration at:
https://www.iana.org/assignments/jose/
Unless you ask us to wait for the other reviewer, we'll act on the first
response we receive.
With thanks,
David Dong
IANA Services Sr. Specialist
_______________________________________________
jose mailing list -- [email protected]
To unsubscribe send an email to [email protected]
