Re: [auth48] AUTH48: RFC-to-be 9383 <draft-bar-cfrg-spake2plus-08> for your review

[Lynne Bartholomew <[e-mail]>]

Hi, Eliot and Chris.  Thanks for the quick replies!

Eliot, thanks also for the clarifications.

Regarding the following:

>> I believe RFC 9383 is correct, and is how NIST refers to the curves.

I will pass this info. on (i.e., adding the hyphens in the "For P..." entries) to the folks working on RFC 9382.


>> I hope it got corrected in production, but 9282 had "Table Table 1" in Section 6

It was indeed fixed; RFC 9382 looks fine.

Thanks again!

RFC Editor/lb


> On Apr 11, 2023, at 3:32 PM, Christopher Wood <[e-mail]> wrote:
> 
> +1 to Elliot. P-256 with the hyphen is correct.
> 
>> On Apr 11, 2023, at 6:10 PM, Independent Submissions Editor (Eliot Lear) <[e-mail]> wrote:
>> 
>> 
>>> On 11.04.23 22:46, Lynne Bartholomew wrote:
>>> Hi, Eliot.
>>> 
>>> We have noted your approval on the AUTH48 status page:
>>> 
>>>   https://www.rfc-editor.org/auth48/rfc9383
>>> 
>>> Please note that if we later pick up on any changes to any lines containing "seed" in either of these documents, we will ask the authors about such changes.
>> 
>> Ok.
>> 
>> 
>>> In the meantime, apologies, but we're not sure what "it may be good to reference such values" means in your note below.
>> 
>> Apologies.  What I meant was that the authors could have referenced the appropriate section of RFc 9382 instead of repeating the values.  Let me tell you all what fun it was to compare several long strings of numbers ;-)
>> 
>> As to this:
>> 
>>> rfc9382.txt:   For P256:
>>> rfc9382.txt:   For P384:
>>> rfc9382.txt:   For P521:
>>> rfc9383.txt:   For P-256:
>>> rfc9383.txt:   For P-384:
>>> rfc9383.txt:   For P-521:
>> 
>> I believe RFC 9383 is correct, and is how NIST refers to the curves.
>> 
>> Also, as an aside, I hope it got corrected in production, but 9282 had "Table Table 1" in Section 6 of https://www.rfc-editor.org/internet-drafts/draft-irtf-cfrg-spake2-26.txt.
>> 
>> Eliot
>> 
>