<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";
        mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
        {mso-style-priority:99;
        mso-style-link:"Plain Text Char";
        margin:0cm;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";
        mso-fareast-language:EN-US;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0cm;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";
        mso-fareast-language:EN-US;}
span.PlainTextChar
        {mso-style-name:"Plain Text Char";
        mso-style-priority:99;
        mso-style-link:"Plain Text";
        font-family:"Calibri","sans-serif";}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:"Calibri","sans-serif";
        mso-fareast-language:EN-US;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="RU" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoPlainText"><span lang="EN-US">Dear Bill, colleagues -<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">My understanding was exactly the <span style="background:yellow;mso-highlight:yellow">
same</span>, that no 're-location' was suggested. If there is a chance of misunderstanding, let's
<span style="background:lime;mso-highlight:lime">clarify</span>.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">Rgds,<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">Michael<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US" style="mso-fareast-language:RU">-----Original Message-----<br>
From: rt4-whois-bounces@icann.org [mailto:rt4-whois-bounces@icann.org] On Behalf Of Smith, Bill<br>
Sent: Friday, February 10, 2012 9:44 PM<br>
To: Kathy Kleiman<br>
Cc: rt4-whois@icann.org<br>
Subject: Re: [Rt4-whois] Updated GNSO Council meeting draft agenda 16 February 2012 at 15:00.</span></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText">My understanding of what&nbsp; may be considered at the Council is a requirement to make all registries thick. The impact of this proposal would be limited (I believe) to .net and .com.<o:p></o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText">While the discussion topic is &quot;thick Whois&quot;, it differs from our discussion topic. I believe our recommendation is that a single point of access to all name WHOIS records should exist, regardless of where the data actually resides. An
 implementation of such a service would traverse the DNS hierarchy until it finds content for the requested entry, or fails to find the entry.<o:p></o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText">The location of the content is independent of the service and could be&quot;radically thin&quot; as I think Lutz has proposed. By &quot;radically thin&quot;, I mean that the data would be highly distributed, only residing on individual name servers for
 individual domains.<o:p></o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText">A &quot;radically thick&quot; service would be one where a single name server held the content for all names. In the case of the DNS, there would likely be 13 copies corresponding to the 13 root servers.<o:p></o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText">My point here is that the GNSO Council <span style="background:yellow;mso-highlight:yellow">
issue is one of data location whereas our discussion is one of access and ease of use</span>. If our recommendation speaks to data location, I suggest we change it to make
<span style="background:lime;mso-highlight:lime">it clear that we do *not* intend for WHOIS data to move</span>.<o:p></o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText">On Feb 10, 2012, at 7:25 AM, Kathy Kleiman wrote:<o:p></o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText">Hi All,<o:p></o:p></p>
<p class="MsoPlainText">FYI that the issue of the Thick Whois, the very issue we are working on as well, is up for discussion in the upcoming GNSO Council meeting on 2/16.<o:p></o:p></p>
<p class="MsoPlainText">Best,<o:p></o:p></p>
<p class="MsoPlainText">Kathy<o:p></o:p></p>
<p class="MsoPlainText">-----------------------------------------------------------<o:p></o:p></p>
<p class="MsoPlainText">From: owner-liaison6c@gnso.icann.org&lt;mailto:owner-liaison6c@gnso.icann.org&gt; [mailto:owner-liaison6c@gnso.icann.org] On Behalf Of Glen de Saint Géry &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; Agenda for GNSO Council Meeting &#8211; 16 February 2012 http://gnso.icann.org/meetings/agenda-council-16feb12-en.htm<o:p></o:p></p>
<p class="MsoPlainText">Wiki agenda :<o:p></o:p></p>
<p class="MsoPlainText">https://community.icann.org/display/gnsocouncilmeetings/Agenda&#43;16&#43;February&#43;2012<o:p></o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText">*** Excerpted...****<o:p></o:p></p>
<p class="MsoPlainText">Meeting Time 15:00 UTC&lt;<a href="http://www.timeanddate.com/worldclock/fixedtime.html?msg=GNSO&#43;Council&#43;meeting&amp;iso=20120216T15&amp;ah=2"><span style="color:windowtext;text-decoration:none">http://www.timeanddate.com/worldclock/fixedtime.html?msg=GNSO&#43;Council&#43;meeting&amp;iso=20120216T15&amp;ah=2</span></a>&gt;<o:p></o:p></p>
<p class="MsoPlainText">Coordinated Universal Time: 15:00 UTC<o:p></o:p></p>
<p class="MsoPlainText">07:00 Los Angeles; 10:00 Washington DC; 15:00 London; 16:00 Paris; 00:00 Tokyo; Item 3: 'thick' Whois Final Issue Report (10 minutes)<o:p></o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText">As recommended by the IRTP Part B Working Group, the GNSO Council requested ICANN Staff to prepare an Issue Report on the requirement of &#8216;thick&#8217; WHOIS for all incumbent gTLDs. The Preliminary Issue Report was published for public comment
 (see <a href="http://www.icann.org/en/announcements/announcement-2-21nov11-en.htm">
<span style="color:windowtext;text-decoration:none">http://www.icann.org/en/announcements/announcement-2-21nov11-en.htm</span></a>).<o:p></o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText">Staff has now submitted the Final Issue Report,&lt;<a href="http://gnso.icann.org/issues/whois/final-report-thick-whois-02feb12-en.pdf"><span style="color:windowtext;text-decoration:none">http://gnso.icann.org/issues/whois/final-report-thick-whois-02feb12-en.pdf</span></a>&gt;
 which includes the report of comments received and additional updates as a result of the comments made. The GNSO Council will now consider the Final Issue Report&lt;<a href="http://gnso.icann.org/issues/whois/final-report-thick-whois-02feb12-en.pdf"><span style="color:windowtext;text-decoration:none">http://gnso.icann.org/issues/whois/final-report-thick-whois-02feb12-en.pdf</span></a>&gt;
 and decide whether or not to initiate a PDP.<o:p></o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText">3.1&nbsp;&nbsp; Presentation of Final Issue Report&lt;<a href="http://gnso.icann.org/issues/whois/final-report-thick-whois-02feb12-en.pdf"><span style="color:windowtext;text-decoration:none">http://gnso.icann.org/issues/whois/final-report-thick-whois-02feb12-en.pdf</span></a>&gt;
 (Marika Konings)<o:p></o:p></p>
<p class="MsoPlainText"><a href="http://gnso.icann.org/issues/whois/final-report-thick-whois-02feb12-en.pdf"><span style="color:windowtext;text-decoration:none">http://gnso.icann.org/issues/whois/final-report-thick-whois-02feb12-en.pdf</span></a><o:p></o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText">Refer to motion:<o:p></o:p></p>
<p class="MsoPlainText"><a href="https://community.icann.org/display/gnsocouncilmeetings/Motions&#43;16&#43;February&#43;2012"><span style="color:windowtext;text-decoration:none">https://community.icann.org/display/gnsocouncilmeetings/Motions&#43;16&#43;February&#43;2012</span></a><o:p></o:p></p>
<p class="MsoPlainText">3.2&nbsp;&nbsp; Reading of the motion (Stéphane Van Gelder)<o:p></o:p></p>
<p class="MsoPlainText">3.3&nbsp;&nbsp; Discussion<o:p></o:p></p>
<p class="MsoPlainText">3.3&nbsp;&nbsp; Vote<o:p></o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText">_______________________________________________<o:p></o:p></p>
<p class="MsoPlainText">Rt4-whois mailing list<o:p></o:p></p>
<p class="MsoPlainText"><a href="mailto:Rt4-whois@icann.org%3cmailto:Rt4-whois@icann.org"><span style="color:windowtext;text-decoration:none">Rt4-whois@icann.org&lt;mailto:Rt4-whois@icann.org</span></a>&gt;<o:p></o:p></p>
<p class="MsoPlainText"><a href="https://mm.icann.org/mailman/listinfo/rt4-whois"><span style="color:windowtext;text-decoration:none">https://mm.icann.org/mailman/listinfo/rt4-whois</span></a><o:p></o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText">_______________________________________________<o:p></o:p></p>
<p class="MsoPlainText">Rt4-whois mailing list<o:p></o:p></p>
<p class="MsoPlainText"><a href="mailto:Rt4-whois@icann.org"><span style="color:windowtext;text-decoration:none">Rt4-whois@icann.org</span></a><o:p></o:p></p>
<p class="MsoPlainText"><a href="https://mm.icann.org/mailman/listinfo/rt4-whois"><span style="color:windowtext;text-decoration:none">https://mm.icann.org/mailman/listinfo/rt4-whois</span></a><o:p></o:p></p>
</div>
</body>
</html>