feat(registry): add SPAKE2 (RFC 9382) and SPAKE2+ (RFC 9383)

[Mehrn0ush]

Summary

Add SPAKE2 (RFC 9382) and SPAKE2+ (RFC 9383) to schema/cryptography-defs.json.

References

• Issue: [FEATURE]: Add SPAKE2 (RFC 9382) and SPAKE2+ (RFC 9383) to Cryptography Registry #797
• RFC 9382: https://doi.org/10.17487/RFC9382
• RFC 9383: https://doi.org/10.17487/RFC9383

Change

• Add family: SPAKE2 with variants:
  • SPAKE2
  • SPAKE2[-{group}][-{hashFunction}][-{kdf}][-{mac}]
• Add family: SPAKE2PLUS (represents SPAKE2+) with variants:
  • SPAKE2+
  • SPAKE2+[-{group}][-{hashFunction}][-{kdf}][-{mac}]

Notes:

• family uses SPAKE2PLUS (no +) to match existing registry naming constraints, while pattern preserves the canonical protocol name SPAKE2+ from RFC 9383.
• Entries are placed in alphabetical order within algorithms[].

Validation

• python3 -m json.tool schema/cryptography-defs.json (JSON OK)

[stevespringett]

cc: @bhess

[Mehrn0ush]

Thanks @bhess ! Agreed — I’ll remove the plain SPAKE2 and SPAKE2+ variants.

Re: family naming — I kept SPAKE2PLUS (no +) to align with existing registry family identifiers, while preserving the canonical protocol name SPAKE2+ in the variant pattern per RFC 9383. If you’d prefer family: "SPAKE2+" for consistency with the canonical name, I’m happy to update it — I kept SPAKE2PLUS only because the current registry doesn’t appear to use + in family identifiers.

[bhess]

Thanks for the update, LGTM