Shumon Huque schreef op 2025-01-21 04:55:
I've changed the subject line to "Domain Hijacking countermeasures"
since the topic is somewhat different from the problem this draft is
trying to solve.
The problem you cite is how a (typically shared) 'DNS provider'
verifies that someone legitimately h
Shumon Huque schreef op 2025-01-21 04:55:
I've changed the subject line to "Domain Hijacking countermeasures"
since the topic is somewhat different from the problem this draft is
trying to solve.
The problem you cite is how a (typically shared) 'DNS provider'
verifies that someone legitimately h
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.
New EPP exte
While fully agreeing with Michele, some remarks from a ccTLD Manager's
perspective:
On 2025/01/22 17:50, Michele Neylon - Blacknight wrote:
> 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
On Jan 22, 2025, at 10:35 AM, Ben van Hartingsveldt | Yocto
wrote:
> 1) User goes to DNS provider and creates zone.
I think there’s a problem with step 1. A user (which is
any-off-the-street-customer) is not the source of authority when it comes to
control or ownership of a domain. A user “c
Edward Lewis schreef op 2025-01-22 18:11:
On Jan 22, 2025, at 10:35 AM, Ben van Hartingsveldt | Yocto
wrote:
1) User goes to DNS provider and creates zone.
I think there’s a problem with step 1. A user (which is
any-off-the-street-customer) is not the source of authority when it
comes to c
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 the
On Jan 22, 2025, at 13:54, Ben van Hartingsveldt | Yocto
wrote:
>
> Edward Lewis schreef op 2025-01-22 18:11:
>> On Jan 22, 2025, at 10:35 AM, Ben van Hartingsveldt | Yocto
>> wrote:
>>> 1) User goes to DNS provider and creates zone.
>> I think there’s a problem with step 1. A user (which is
Sorry for my mail being sent twice. My mailserver did some strange
things.
Anyway, my response is below:
Dr Eberhard W Lisse schreef op 2025-01-22 16:38:
While fully agreeing with Michele, some remarks from a ccTLD Manager's
perspective:
On 2025/01/22 17:50, Michele Neylon - Blacknight wrote:
