Michele Neylon - Blacknight schreef op 2025-01-22 15:50:
So you want to create a level of complexity and extra work for
everyone?
As a registrar that’s my read on this.
If you want to avoid hijacking then “registry lock” in one of its
flavours gets you there. And DNS records existing where they
shouldn’t can also be fixed by other means.
Registry lock isn't a fix. It only makes sure that the domain isn't
altered, but that is not the issue that I'm trying to solve.
New EPP extensions might work for some registrars who might
implement them, but a lot won’t, because it’s non-standard,
whereas other processes already exist that do not require lots of
extra code.
And of course this also assumes that people’s “registrars” are
actually registrars and not resellers of a registrar, so more
complexity.
I see it more as an opt-in feature. Registries have to start to support
this. If they to, registrars can start to support it. They may choose
not to, but users may complain in the end, when the spec will become
well-known. Until the whole world uses the new ZDVT records, DNS
providers likely have to fall back on another verification method too.
But I hope you understand that every new DNS feature has a similar
problem if it comes to adoption?
Or am I missing something?
regards
Michele
Ben
--
Mr Michele Neylon
Blacknight Solutions
Hosting, Colocation & Domains
https://www.blacknight.com/
https://blacknight.blog/
Intl. +353 (0) 59 9183072
Personal blog: https://michele.blog/
Some thoughts: https://ceo.hosting/
-------------------------------
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business
Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.:
370845
I have sent this email at a time that is convenient for me. I do not
expect you to respond to it outside of your usual working hours.
_______________________________________________
DNSOP mailing list -- dnsop@ietf.org
To unsubscribe send an email to dnsop-le...@ietf.org
