[Gnso-ppsai-pdp-wg] For review - updated templates Cat B, questions 1 and 2

[Luc SEUFER]

So the reasonable option would be to only compel the p/p provider to verify those details in cases this party has not already verified them in its capacity as registrar?

Whereas we don’t have a re-verification but two separate ones that can be merged to avoid redundancy.

Any opposition to that?

Luc




On Mar 4, 2014, at 5:47, Holly Raiche <h.raiche at internode.on.net<mailto:h.raiche at internode.on.net>> wrote:

I have to agree with Steve on this.  People should not have access to a domain name without someone verifying their details - regardless of whether those details are made public or not.

Holly
On 04/03/2014, at 5:51 AM, Metalitz, Steven wrote:

Thanks Volker.  It is precisely because “the registrars obligation only extends to the registrant of record, not to anyone who may use the domain name with permission of that registrant,” that there should be an independent obligation on the part of the p/p service provider to validate its customer’s contact information.

Steve.


From: Volker Greimann [mailto:vgreimann at key-systems.net]
Sent: Monday, March 03, 2014 5:32 AM
To: Metalitz, Steven; gnso-ppsai-pdp-wg at icann.org<mailto:gnso-ppsai-pdp-wg at icann.org>
Subject: Re: [Gnso-ppsai-pdp-wg] For review - updated templates Cat B, questions 1 and 2

Hi Steven,

Even when this assertion is relevant, it may not be persuasive, for a number of reasons.  For example, the Whois data reminder obligation applies to the registrant of record.  In the case of a proxy service, the registrant or record is the service, not its customer.  If a Whois data reminder is sent to a non-proxy registrant and bounces back, then the RAA requires the registrar to re-verify.  But a data reminder sent to a proxy service will almost never bounce back, and therefore there may be no RAA obligation to re-verify.   This is so even if the customer data provided to the service is inaccurate or outdated.   In this circumstance it is up to the p/p service accreditation standards to specify the conditions under which customer data must be re-verified.

This depends on how the service is set up. One could suggest that if such required messages from the registrar do not reach the registrant, it could become the providers' obligation to perform the information requirements on its own. The registrar could then rely on the provider to perform its duties under the accreditation agreement with ICANN just at it performs its own obligations under the RAA.

Please also remember that the registrars obligation only extends to the registrant of record, not to anyone who may use the domain name with permission of that registrant.

V.
_______________________________________________
Gnso-ppsai-pdp-wg mailing list
Gnso-ppsai-pdp-wg at icann.org<mailto:Gnso-ppsai-pdp-wg at icann.org>
https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg

_______________________________________________
Gnso-ppsai-pdp-wg mailing list
Gnso-ppsai-pdp-wg at icann.org<mailto:Gnso-ppsai-pdp-wg at icann.org>
https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg


________________________________

--------------------------------------------------------

This e-mail and any attached files are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail by mistake, please notify the sender immediately and delete it from your system. You must not copy the message or disclose its contents to anyone.

Think of the environment: don't print this e-mail unless you really need to.

--------------------------------------------------------