Thank you, looks good: I approve.

On Fri, Oct 10, 2025 at 10:16 PM Sandy Ginoza <[email protected]>
wrote:

> Hi Jake, Bas, and Sean,
>
> We have updated the document and posted the revised files here:
>    https://www.rfc-editor.org/authors/rfc9881.xml
>    https://www.rfc-editor.org/authors/rfc9881.txt
>    https://www.rfc-editor.org/authors/rfc9881.pdf
>    https://www.rfc-editor.org/authors/rfc9881.html
>
> Diffs highlighting only the recent changes:
>    https://www.rfc-editor.org/authors/rfc9881-lastdiff.html
>    https://www.rfc-editor.org/authors/rfc9881-lastrfcdiff.html (side by
> side)
>
> AUTH48 diffs:
>    https://www.rfc-editor.org/authors/rfc9881-auth48diff.html
>    https://www.rfc-editor.org/authors/rfc9881-auth48rfcdiff.html (side by
> side)
>
> Comprehensive diffs:
>    https://www.rfc-editor.org/authors/rfc9881-diff.html
>    https://www.rfc-editor.org/authors/rfc9881-rfcdiff.html (side by side)
>
>
> Bas - regarding the following, the lines in RFC 5912 are already outdented
> (see https://www.rfc-editor.org/rfc/rfc5912.txt, p17).  The lines in RFC
> 5912 are actually outdented 3 additional spaces; we are unable to make them
> match with our current tools.
>
> >> Note that instead of breaking the line, we outdented — please let us
> know if you prefer otherwise.
> >
> > Outdenting looks good to me, I'm assuming both "Current" and "From
> [RFC5912]" will be outdented to match eachother.
>
>
> Please review and let us know if any further updates are needed or if you
> approve the RFC for publication.
>
> Thanks,
> Sandy Ginoza
> RFC Production Center
>
>
>
> > On Oct 10, 2025, at 6:01 AM, Bas Westerbaan <[email protected]> wrote:
> >
> > Yes, good catch.
> >
> > On Fri, Oct 10, 2025 at 2:57 PM Sean Turner <[email protected]> wrote:
> > Just want to make sure I didn’t introduce an error, but wanted more eyes:
> >
> > Appendix D includes this:
> >
> >      # Referred to as 'Externalμ-ML-DSA.Prehash(pk, M, ctx)'
> >      # in the FIPS 204 FAQ.
> >
> > and this:
> >
> >      # Referred to as 'Externalμ-ML-DSA.Sign(sk, μ)'
> >      # in the FIPS 204 FAQ.
> >
> > Do we need to change these μ to Mu because that’s how the are actually
> referenced in the FIPS FAQ?
> >
> > spt
> >
> >
> >> On Oct 10, 2025, at 06:03, Bas Westerbaan <[email protected]> wrote:
> >>
> >> Hi Sandy,
> >>
> >> Thank you for the quick updates.
> >>
> >> I see some changes are still required.
> >>
> >> - Section 2. Regarding changes for your origin point 1: you added an
> ampersand in front of "Params", but not in front of "id" on the line before
> that.
> >>
> >> - References. Regarding changes for your original point 7: you haven't
> updated the URL of the reference CDFFJ21 to the specific version correctly.
> It should be https://eprint.iacr.org/archive/2020/1525/20231023:114351
> >>
> >> Otherwise it looks great, thanks!
> >>
> >> Best,
> >>
> >>  Bas
> >>
> >> On Fri, Oct 10, 2025 at 4:50 AM Massimo, Jake <jakemas=
> [email protected]> wrote:
> >> Hey Sandy, Bas,
> >>
> >> I can check a few confirmations off of this list:
> >>
> >> > Note that instead of breaking the line, we outdented — please let us
> know if you prefer otherwise.
> >>
> >> Outdenting looks good to me, I'm assuming both "Current" and "From
> [RFC5912]" will be outdented to match eachother.
> >>
> >> > We updated to use “pre-hash” except in the following:
> >> > # Referred to as 'Externalμ-ML-DSA.Prehash(pk, M, ctx)'
> >> > Please let us know if any updates are needed.
> >>
> >> Confirming this is ok, and that we would not want to change
> 'Externalμ-ML-DSA.Prehash'.
> >>
> >> Cheers,
> >> Jake
> >>
> >
>
>
-- 
auth48archive mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to