Calling time on DNSSEC? https://blog.apnic.net/2024/05/28/calling-time-on-dnssec/
Calling time on DNSSEC: The costs exceed the benefits Written on 02 June 2023, 11 min read. https://www.mattb.nz/w/2023/06/02/calling-time-on-dnssec/
call time (on somebody/something)to say that it is time for something to finish or stop
call time on one's career as ～としての自分［自ら］のキャリアを終える［終わらせる］
1. whois
Because of the lack of clear signals of general adoption of DNSSEC over three decades, is it time to acknowledge that DNSSEC is just not going anywhere? Is it time to call it a day for DNSSEC and just move on?
What appears to be very clear (to me at any rate!) is that DNSSEC as we know it today is just not going anywhere. It’s too complex, too fragile, and just too slow to use for the majority of services and their users. Some value its benefits highly enough that they are prepared to live with its shortcomings, but that’s not the case for the overall majority of name holders and for the majority of users, and no amount of passionate exhortations about DNSSEC will change this. In its current form, we could do ourselves a favour and just drop DNSSEC and move on. But it feels wrong to just walk away from the objective of securing the namespace.
2. history
Can we fix this? if we want a secured namespace what aspects should we change about the way DNSSEC is used to make it simpler, faster, and more robust?