ICANN ICANN Email List Archives

[gnso-irtp-b-jun09]


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

RE: [gnso-irtp-b-jun09] Updated recommendations overview

  • To: <Gnso-irtp-b-jun09@xxxxxxxxx>
  • Subject: RE: [gnso-irtp-b-jun09] Updated recommendations overview
  • From: "Diaz, Paul" <pdiaz@xxxxxxxxxxxxxxxxxxxx>
  • Date: Wed, 12 Jan 2011 11:54:50 -0500

I have a question/concern about Recommendation #3, in particular the sentence 
that reads:

        It should be noted that this recommendation does not imply that         
additional information collected under a thick WHOIS model needs to be  
publicly displayed.

What is this supposed to mean?  Thick WHOIS Registry Operators display whatever 
contact information registrars have collected and passed through (under the 
terms of their Registry-Registrar Agreements).  Do we really imagine any RO 
parsing out Registrant email addresses so they don't publicly appear, but will 
somehow made available to registrars for IRTP purposes?  I think this is 
unrealistic, and recommend dropping this sentence from Recommendation #3.  

The focus of our Recommendation should be on setting the stage for an Issues 
Report and/or PDP on thick WHOIS for all gTLD registries.  Let that future WG 
debate what data could or should be included in the publicly available WHOIS.  
It's inappropriate/out of scope for the IRTP B WG to color the debate with its 
opinion about whether all data should be presented.

Regards, P

________________________________________
From: owner-gnso-irtp-b-jun09@xxxxxxxxx 
[mailto:owner-gnso-irtp-b-jun09@xxxxxxxxx] On Behalf Of Marika Konings
Sent: Monday, January 10, 2011 4:29 AM
To: Gnso-irtp-b-jun09@xxxxxxxxx
Subject: [gnso-irtp-b-jun09] Updated recommendations overview

Dear All,

Please find attached the updated recommendations overview which incorporates 
the changes discussed at last week's meeting and suggestions posted on the 
mailing list.

With best regards,

Marika




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

Privacy Policy | Terms of Service | Cookies Policy