On Tue 12/Mar/2024 17:24:08 +0100 David Conrad wrote:
On Mar 12, 2024, at 1:57 AM, Alessandro Vesely wrote:
DNSSEC everywhere would make more sense than HTTPS everywhere, which instead
won the hype.
I figure enabling DNSSEC validation everywhere and signing what makes sense
after doing a
On Mar 12, 2024, at 1:57 AM, Alessandro Vesely wrote:
> DNSSEC everywhere would make more sense than HTTPS everywhere, which instead
> won the hype.
I figure enabling DNSSEC validation everywhere and signing what makes sense
after doing a cost/benefit trade off would be the rational way to
> DNSSEC everywhere would make more sense than HTTPS everywhere, which
> instead won the hype. Being sure to connect to the IP designated by
> the domain is essential, while encrypting every page of sites like,
> say, wikipedia is just wasting cycles.
tls gives a bit of authenticity too. modulo
Dear colleagues,
Thank you all very much for your constructive comments. Please make sure you
contribute in the document itself, so our experts can take your views into
account when finalising the document.
As an explanation. IS3C focuses on the deployment of all security-related
Internet
On 11/03/2024 22:30, John Levine wrote:
It appears that Michele Neylon - Blacknight via anti-abuse-wg
said:
Several ccTLD registries have given discounts for DNSSEC.
What is unclear is how many of the domains with DNSSEC enabled are in active
use, so the lack of �problems� could be simply
