Bouncycastle support for SPHINCS shows that they treat it as a separate
(unique) crypto system
https://www.bouncycastle.org/docs/docs1.8on/org/bouncycastle/pqc/jcajce/interfaces/SPHINCSKey.html
https://www.bouncycastle.org/docs/docs1.8on/org/bouncycastle/pqc/crypto/sphincs/SPHINCSPublicKeyParameters.html
also when it comes to creating keys from external representations.
If other platforms code-wise prefer lumping different key families together
they can still do that at the cost of an additional case label:
swith (kty) {
case "RSA"
RSA specific reader
break;
case "EC"
EC specific reader
break;
case "OKP":
case "SPHINCS+":
case "BLS":
Common reader for a bunch of key families
}
I leave it there. It is a pity that .NET doesn't natively support Ed25519
since that would have provided yet another view on this topic.
Cheers,
Anders
_______________________________________________
COSE mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/cose
