ICANN ICANN Email List Archives

[gnso-dow123]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [gnso-dow123] proposal on collection of contact data

  • To: tim@xxxxxxxxxxx, gnso-dow123@xxxxxxxxxxxxxx
  • Subject: Re: [gnso-dow123] proposal on collection of contact data
  • From: KathrynKL@xxxxxxx
  • Date: Tue, 31 Jan 2006 10:39:23 EST

Tim:
Can we make a phone date for a fast call to talk about the issues you raise 
and the data that is collected?  Happy to stick to a time limit (10-15 
minutes).
Regards, Kathy

> 
> I'm trying to understand your proposal, which centers on data collection. 
> I'm confused about how I as a registrar would then determine who has the 
> right 
> to perform non-technical functions for the domain name, such as a transfer to 
> another registrar, transfer to another registered name holder, deletion of 
> the domain name, etc.. The individual or organization that facilitates the 
> purchase or registration of a domain name is not always the intended 
> registered 
> name holder.
>   
> It is important that we don't confuse the individual or organization who 
> facilitates the purchase or registration with the individual or organization 
> that becomes the registered name holder.
>   
> 
> Tim Ruiz
> VP, Domain Services
> The Go Daddy Group, Inc.
> Office: 319-294-3940
> Fax: 480-247-4516
> tim@xxxxxxxxxxx
> 
> 
> 
> >> -------- Original Message --------
>> Subject: [gnso-dow123] proposal on collection of contact data
>> From: KathrynKL@xxxxxxx
>> Date: Sun, January 29, 2006 9:16 pm
>> To: gnso-dow123@xxxxxxxxxxxxxx
>> 
>> Attached please find a statement from the NCUC.  I guess the word proposal 
>> is appropriate.  
>> 
>> Our goal here is to submit that the TF must examine the data collected for 
>> the Whois database.  Regardless of the formulation we pick, we must address 
>> the issue of whether the data collected for the Whois database is 
>> appropriate.  Publication is one issue; collection is another.
>> 
>> 
> 



<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy