Description of the problem
Per RFC 8422 section 5.1.2:
RFC 4492 specified that if this extension is missing, it means that only the uncompressed point format is supported, so interoperability with implementations that support the uncompressed format should work with or without the extension.
It further states:
Implementations of this document MUST support the uncompressed format for all of their supported curves and MUST NOT support other formats for curves defined in this specification.
IOW, per my reading, specifying some combination of SupportedCurvesExtension without the PointFormatExtension should work and result in the uncompressed point format being used.
However, I don't see a test under the RFC 8422 directory for this behavior, and I see no directory for RFC 4492.
If this is of interest, I'd be happy to submit a PR (with a little guidance on building and running) to add this missing test case.
Additional Information
Description of the problem
Per RFC 8422 section 5.1.2:
It further states:
IOW, per my reading, specifying some combination of SupportedCurvesExtension without the PointFormatExtension should work and result in the uncompressed point format being used.
However, I don't see a test under the RFC 8422 directory for this behavior, and I see no directory for RFC 4492.
If this is of interest, I'd be happy to submit a PR (with a little guidance on building and running) to add this missing test case.
Additional Information