<<<
Chronological Index
>>> <<<
Thread Index
>>>
[gnso-lockpdp-wg] Differentiating between lockings in case of own and third party privacy services
- To: "Gnso-lockpdp-wg@xxxxxxxxx" <Gnso-lockpdp-wg@xxxxxxxxx>
- Subject: [gnso-lockpdp-wg] Differentiating between lockings in case of own and third party privacy services
- From: Volker Greimann <vgreimann@xxxxxxxxxxxxxxx>
- Date: Thu, 10 Jan 2013 17:13:36 +0100
To describe our current process:
1) We receive the inquiry email from the proider.
2) We review the domain name.
3a) In case the domain uses our privacy service, the service is
deactivated, then the domain is locked
3b) In all other cases, the domain is locked. If the domain name uses a
known privacy service, we inform the provider of this fact.
4) We respond to the inquiry email with the requested data points.
I would like to propose that accredited whois privacy providers rather
belong in category 3a than 3b in oder to ensure the service can be
removed in case of it wanting to reveal the underlaying registrant. To
achieve that, a differentiated locking procedure may be beneficial
where a lock is in place but modifications could still be made by the
registrar within a limited window:
Such as:
-> After receipt of the provider notification, the domain name is
locked, however, within a certain time period 2-3 working days after the
lock, a registrar may allow modifications if ICANN accredited whois
privacy and/or proxy providers provide updated information replacing the
registrant record to reflect the actual registrant.
Volker
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|