<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Completely disagree guys, and am writing an extensive message. I
have to say that two days after we were due to report out, I am
surprised/concerned/upset to be debating substantive policy matters.<br>
<br>
But the fact is that the idea of Thick WHOIS database for existing
thin registries (and all, there are Four of them, have we ever
discussed that fact?) is **already being debated**. They recognize
that there may be intended and possibly considerable unintended
consequences of the process. Am reviewing their work and will share
shortly. <br>
<br>
Suffice to say, I think we have leapt headlong into policy... Kathy<br>
<br>
<< Yes - there is not a difference in privacy by implementing
a centralized interface to all the existing Whois pages. All the
interface does is provide a single point of access to the same data
versus multiple points of access (that would still be functional).
<blockquote
cite="mid:20111202092555.00ef555ff13978e3e1b8d2179880f99e.b64d3fa08a.wbe@email12.secureserver.net"
type="cite"><span style="font-family:Verdana; color:#000000;
font-size:10pt;">
<div>Lynn</div>
<div> </div>
<blockquote style="BORDER-LEFT: blue 2px solid; PADDING-LEFT:
8px; FONT-FAMILY: verdana; COLOR: black; MARGIN-LEFT: 8px;
FONT-SIZE: 10pt" id="replyBlockquote" webmail="1">
<div id="wmQuoteWrapper">-------- Original Message --------<br>
Subject: Re: [Rt4-whois] No agreement on Lutz's
recommendations<br>
[SEC=UNCLASSIFIED]<br>
From: "Smith, Bill" <<a moz-do-not-send="true"
href="mailto:bill.smith@paypal-inc.com">bill.smith@paypal-inc.com</a>><br>
Date: Fri, December 02, 2011 10:02 am<br>
To: "<a moz-do-not-send="true"
href="mailto:lynn@goodsecurityconsulting.com">lynn@goodsecurityconsulting.com</a>"
<<a moz-do-not-send="true"
href="mailto:lynn@goodsecurityconsulting.com">lynn@goodsecurityconsulting.com</a>><br>
Cc: Emily Taylor <<a moz-do-not-send="true"
href="mailto:emily@emilytaylor.eu">emily@emilytaylor.eu</a>>,
"<a moz-do-not-send="true"
href="mailto:rt4-whois-bounces@icann.org">rt4-whois-bounces@icann.org</a>"<br>
<<a moz-do-not-send="true"
href="mailto:rt4-whois-bounces@icann.org">rt4-whois-bounces@icann.org</a>>,
Lutz Donnerhacke <<a moz-do-not-send="true"
href="mailto:lutz@iks-jena.de">lutz@iks-jena.de</a>>,<br>
"<a moz-do-not-send="true" href="mailto:rt4-whois@icann.org">rt4-whois@icann.org</a>"
<<a moz-do-not-send="true"
href="mailto:rt4-whois@icann.org">rt4-whois@icann.org</a>><br>
<br>
I agree with Lynn and Peter on this. I'm having difficulty
understanding the privacy implications of better usability,
other than more people would use the service but then that's
the purpose of improved usability.<br>
<br>
On Dec 2, 2011, at 4:39 AM, <<a moz-do-not-send="true"
href="mailto:lynn@goodsecurityconsulting.com">lynn@goodsecurityconsulting.com</a>>
<<a moz-do-not-send="true"
href="mailto:lynn@goodsecurityconsulting.com">lynn@goodsecurityconsulting.com</a>>
wrote:<br>
<br>
> I would like to get a better understanding of the.
Objection or concern about Lutz's recommendation. If an
interface is only implemented for .net and .com, it defeats
the purpose and does not provide ease of access to all WHOIS
registration data.<br>
> Lynn<br>
> <br>
> Sent via BlackBerry by AT&T<br>
> <br>
> -----Original Message-----<br>
> From: Emily Taylor <<a moz-do-not-send="true"
href="mailto:emily@emilytaylor.eu">emily@emilytaylor.eu</a>><br>
> Sender: <a moz-do-not-send="true"
href="mailto:rt4-whois-bounces@icann.org">rt4-whois-bounces@icann.org</a><br>
> Date: Fri, 2 Dec 2011 08:28:15 <br>
> To: Lutz Donnerhacke<<a moz-do-not-send="true"
href="mailto:lutz@iks-jena.de">lutz@iks-jena.de</a>><br>
> Cc: <a moz-do-not-send="true"
href="mailto:rt4-whois@icann.org">rt4-whois@icann.org</a><<a
moz-do-not-send="true" href="mailto:rt4-whois@icann.org">rt4-whois@icann.org</a>><br>
> Subject: Re: [Rt4-whois] No agreement on Lutz's
recommendations<br>
> [SEC=UNCLASSIFIED]<br>
> <br>
> Thank you for these constructive ideas. Apologies for
my mistake on this one. I would like Kathy's view on the
proposed wording before any sign offing this as I am aware
it is something on which she has previously raised comments.
<br>
> <br>
> Peter I think you meant thin registries didn't you?
That would be a more accurate and precise version of what we
agreed. This another one where (I think) we are all agreed
on a minimum which in my view would represent a real step
forward. What there is not consensus on is how far or
whether such a look-up could or should be expanded. If is
not already clear in the text we should find a way of
expressing clearly that our proposal should not necessitate
any transfer of databases, escrow or similar. It is simply a
single look up point. <br>
> <br>
> Sent from my iPhone<br>
> <br>
> On 2 Dec 2011, at 07:35, Lutz Donnerhacke <<a
moz-do-not-send="true" href="mailto:lutz@iks-jena.de">lutz@iks-jena.de</a>>
wrote:<br>
> <br>
>> On Fri, Dec 02, 2011 at 03:05:13PM +1100,
Nettlefold, Peter wrote:<br>
>>> "To make WHOIS data more accessible for
consumers, the review team<br>
>>> recommends that ICANN should set up a
dedicated, multilingual interface<br>
>>> website to help users access thick gTLD WHOIS
data.<br>
>> <br>
>> Remove 'thick gTLD'. The scope is narrowed later.<br>
>> <br>
>>> This would be a smart web portal, that would
assist users to access<br>
>>> publicly available WHOIS data. It is not
envisaged that this would<br>
>>> replicate registry databases in any way, but
instead help users by<br>
>>> providing a single centralised site through
which to search those<br>
>>> databases, and to display the WHOIS data in an
accessible way.<br>
>> <br>
>> Ack. (There is no reference zu gTLD.)<br>
>> <br>
>>> The review team has discussed the scope of this
portal, and seeks<br>
>>> ecommunity views on whether it should only
apply to thin gTLD registries,<br>
>>> or should instead provide a comprehensive gTLD
search service."<br>
>> <br>
>> In order to be really useful, the system should be
able to access any ICANN<br>
>> regulated WHOIS data (which includes ASN and IP).<br>
>> _______________________________________________<br>
>> Rt4-whois mailing list<br>
>> <a moz-do-not-send="true"
href="mailto:Rt4-whois@icann.org">Rt4-whois@icann.org</a><br>
>> <a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/rt4-whois">https://mm.icann.org/mailman/listinfo/rt4-whois</a><br>
> <br>
> _______________________________________________<br>
> Rt4-whois mailing list<br>
> <a moz-do-not-send="true"
href="mailto:Rt4-whois@icann.org">Rt4-whois@icann.org</a><br>
> <a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/rt4-whois">https://mm.icann.org/mailman/listinfo/rt4-whois</a><br>
> <br>
> _______________________________________________<br>
> Rt4-whois mailing list<br>
> <a moz-do-not-send="true"
href="mailto:Rt4-whois@icann.org">Rt4-whois@icann.org</a><br>
> <a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/rt4-whois">https://mm.icann.org/mailman/listinfo/rt4-whois</a><br>
<br>
</div>
</blockquote>
</span>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Rt4-whois mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Rt4-whois@icann.org">Rt4-whois@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/rt4-whois">https://mm.icann.org/mailman/listinfo/rt4-whois</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
</pre>
</body>
</html>