4 ms·
Someone not well informed on the matter was rumoured to say that DNSSEC does not work well with ECDSA P-256. This is far from the case. New implementations ar
by ietf-dane 5y ago
Someone not well informed on the matter was rumoured to say that DNSSEC does not work well with ECDSA P-256. This is far from the case. New implementations are increasingly ECDSA, and further bulk rollovers will happen. Many resolvers are not yet ready for EdDSA 25519 or Ed448, so those will not happen in bulk in the short term. Need a few more LTS OS releases that lack Ed25519 support to be phased out before that happens.
It has been said about fundamental science that progress happens one funeral at a time... Something like that is applicable to core infrastructure, it is rarely upgraded, more typically replaced. So the lifecycles are somewhat longer.
In fact ECDSHAP256SHA256(13) will shortly be the most prevalent DNSSEC algorithm, and already has been a few times but for recent algorithm rollovers from the deprecated RSASHA1(7) (90% down from peak and falling) to RSASHA256(8) that temporarily put RSA(8) back in front.
The supremacy of RSA(8) over EC(13) is not for long: <https://stats.dnssec-tools.org/images/ksk-algs.png https://stats.dnssec-tools.org/images/ksk-algs.png>. A month ago there was a 1.2M zone gap, it is now down to ~150k, and will soon be gone.
The TLDs have been a bit slower to adopt P256, just 45 so far, but these include e.g. .cz, .br, .ch and .fr. There will be more TLDs switching to ECDSA in 2022.
- ietf-dane 5y agoTrends in eTLD+1 zone (effective TLD + 1, e.g. example.com, example.co.uk, ...) DNSSEC algorithm adoption. The graph plots the number of delegated domains with a given DNSKEY algorithm in the corresponding DS RRset published in the parent (eTLD) zone. <https://dnssec-stats.ant.isi.edu/~viktor/algs-ds.png https://dnssec-stats.ant.isi.edu/~viktor/algs-ds.png>