[registrars] Fw: BOUNCE registrars at gnso.icann.org: Non-member submission from [chrisk at domainpeople.com]

Wed Oct 15 17:27:27 UTC 2003

Anotyher bounced message...

-rick

Begin forwarded message:

Date: Wed, 15 Oct 2003 08:49:28 -0700
From: owner-registrars at gnso.icann.org
To: registrars-approval at gnso.icann.org
Subject: BOUNCE registrars at gnso.icann.org:    Non-member submission from [chrisk at domainpeople.com]   

>From bounces at ar.com Wed Oct 15 08:49:27 2003
Received: from pechora.icann.org (pechora.icann.org [192.0.34.35])
	by greenriver.icann.org (8.11.6/8.11.6) with ESMTP id h9FFnRb18666
	for <registrars at greenriver.icann.org>; Wed, 15 Oct 2003 08:49:27 -0700
Received: from webmail.netnation.com (webmail.netnation.com [204.174.223.83])
	by pechora.icann.org (8.11.6/8.11.6) with ESMTP id h9FFpGW28162
	for <registrars at dnso.org>; Wed, 15 Oct 2003 08:51:16 -0700
Received: from apache by webmail.netnation.com with local (Exim 4.23)
	id 1A9ntt-0001kv-Eo; Wed, 15 Oct 2003 08:49:25 -0700
Received: from 24.84.169.177 ( [24.84.169.177])
	as user chrisk at mail.domainpeople.com by webmail.domainpeople.com with HTTP;
	Wed, 15 Oct 2003 08:49:25 -0700
Message-ID: <1066232965.3f8d6c854ef30 at webmail.domainpeople.com>
Date: Wed, 15 Oct 2003 08:49:25 -0700
From: chrisk at domainpeople.com
To: Tim Ruiz <tim at godaddy.com>
Cc: "'Paul Stahura'" <stahura at enom.com>,
   "'Registrars Constituency'" <registrars at dnso.org>
Subject: RE: [registrars] WDRP Compliance Date and Presentation Method
References: <007301c392e4$41c7ae70$fa05a8c0 at TIMRUIZ>
In-Reply-To: <007301c392e4$41c7ae70$fa05a8c0 at TIMRUIZ>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.1
X-Originating-IP: 24.84.169.177

Tim,

The policy states the following 3 key provisions:

1. "What the WDRP Notice Must Include: Each WDRP notice must include a copy of
the data elements listed in RAA subsection 3.3.1 as contained in the registrar's
database for each registration"

2. "How, and to Whom, the WDRP Notice May Be Presented: The WDRP Notice can be
presented via web, fax, postal mail, e-mail, or other appropriate means."

3. "Documentation Requirements: Registrars must maintain either copies of each
WDRP Notice or an electronic database documenting the date and time, the
addressee, and the content, of each WDRP notice sent under this policy."

All the required data can be captured in a Registrar's database simply by saving
and mapping the admin email address to all domains registered with it at the
given date and time of notification along with the version number of the message.

Since the policy states the notice must include the whois data for each
registration, we feel this method would best serve our customers.

 -Chris

Quoting Tim Ruiz <tim at godaddy.com>:

> I think the key is that it can be documented as required. That may be
> where the concern was regarding Christopher's implementation.
> 
> -----Original Message-----
> From: owner-registrars at gnso.icann.org
> [mailto:owner-registrars at gnso.icann.org] On Behalf Of Paul Stahura
> Sent: Tuesday, October 14, 2003 7:42 PM
> To: 'Registrars Constituency'
> Subject: RE: [registrars] WDRP Compliance Date and Presentation Method
> 
> Tim,
> That is how I read it too, and I also took it to mean that it does not
> prevent
> using *both* web and email in combination, but since it seems
> Christopher Kruk has an indication from ICANN otherwise, I'd like to
> make
> sure.
> Paul
> 
> -----Original Message-----
> From: Tim Ruiz [mailto:tim at godaddy.com] 
> Sent: Tuesday, October 14, 2003 2:43 PM
> To: 'Paul Stahura'; 'Christopher Kruk'; 'Registrars Constituency'
> Subject: RE: [registrars] WDRP Compliance Date and Presentation Method
> 
> 
> Paul, the entire policy can be found at:
> 
> http://www.icann.org/registrars/wdrp.htm
> 
> It states very clearly that "The WDRP Notice can be presented via web,
> fax, postal mail, e-mail, or other appropriate means."
> 
> I don't believe it prohibits combining multiple domains in a notice, at
> least as far as I understand it, as long as the documentation
> requirements can be met.
> 
> Tim
> 
> -----Original Message-----
> From: owner-registrars at gnso.icann.org
> [mailto:owner-registrars at gnso.icann.org] On Behalf Of Paul Stahura
> Sent: Tuesday, October 14, 2003 3:18 PM
> To: 'Christopher Kruk'; 'Registrars Constituency'
> Subject: RE: [registrars] WDRP Compliance Date and Presentation Method
> 
> I would like this cleared up as well
> 1) can we use email and web in combination to comply?
> I don't see why not because the registrant would need to
> go to a website to change the information anyway.
> (most registrars do not allow whois changes via email nowadays)
> 
> 2) can we send one message that lists multiple domains?
> Or MUST we send a separate message for each domain?
> 
> I really do not want to be required to send a ton
> of separate email messsages to one registrant with many domain names.
> Don't we want them to pay attention to these notices and actually have
> them
> work?
> If they get too many messages, they will ignore them, let alone the fact
> that
> many of our email servers will get blacklisted for spam.
> 
> Paul
> 
> 
> -----Original Message-----
> From: Christopher Kruk [mailto:kruk at domainpeople.com] 
> Sent: Tuesday, October 14, 2003 11:37 AM
> To: 'Registrars Constituency'
> Subject: [registrars] WDRP Compliance Date and Presentation Method
> 
> 
> Dear Registrars
> 
> As we all know, the Whois Data Reminder Policy (WDRP) was adopted by
> ICANN
> as a consensus policy on 27 March 2003. All ICANN-accredited registrars
> must
> comply with the WDRP with respect to registrations they sponsor in all 
> top-level
> domains for which they are accredited. Details of compliance
> requirements
> are
> provided at:
> 
> http://www.icann.org/registrars/wdrp.htm
> 
> As the compliance date is drawing near (Oct. 31, 2003), I've submitted
> to
> ICANN
> DomainPeople's intended method of presentation consisting of an email 
> containing:
> 
> 1. A link to the data elements listed in RAA subsection 3.3.1 for each 
> domain registered with the recipient.
> 2. A statement reminding the registrant that false Whois information can
> be 
> grounds for cancellation of a domain registration
> 3. A link to the registration agreement
> 4. The version number of the notification
> 
> ICANN has indicated that they may have concerns about whether our
> proposed
> approach meets the requirements. We believe using a combination of email
> and
> web interface to present the reminder is an appropriate means of getting
> the
> message across to registrants.
> 
> ICANN's Model WDRP Notice seems to indicate an individual email message
> for
> each domain name. Any registrar supporting bulk registrations can see
> the 
> potential
> problems with this method as bulk registrants would be flooded with
> reminders.
> 
> Can anyone, particularly someone from the Whois task force, see any
> problem 
> with
> my proposed method of notification for the WDRP meeting ICANN's
> requirements?
> 
> 
> Thanks & regards,
> Chris Kruk
> Business Area Manager
> DomainPeople, Inc. <http://www.domainpeople.com>
> (604) 639-1680 Ext. 116
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 