OS2ECP failed state - Githubissues

fcelda / nsec5-draft

Working Copy of the NSEC5 Specification

15 stars 2 forks source link

Closed fcelda closed 7 years ago

fcelda commented 7 years ago

@goldbe ad your removed cref in pull #24.

I checked that the OS2ECP algorithm has a variant of a failed state:

SEC 1 section 2.3.4 for NIST P256 outputs "invalid".
RFC 8032 Secion 5.1.3 for Ed25519 says that "decoding fails" instead of explicitly giving "invalid" as an output.

Do you think it has to be clarified? RFC8032 uses less formal and more descriptive language.

goldbe commented 7 years ago

No, I think it is fine. I just wanted to make sure that you checked. Thank you.