While this type implements Default, please consider what a
good default for your use case is.
If you are doing a greenfield implementation where you know that
every client understands RFC9580, you can just explicitly pick
that.
Otherwise, you have to consider the state of the ecosystem your
client will interact with. Maybe it is better to stick to
generating RFC4880 certificates for the time being, while rolling
out RFC9580 support. Consider adding a configuration option or
command line switch like --profile, but pick a sensible default,
and remember to don’t overwhelm your users.
For now, our default is RFC4880. This is a safe default for every
downstream consumer that has existing legacy deployments
(including their own previous versions using a legacy version of
Sequoia). We will update this default once RFC9580 is more widely
deployed.
Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.