<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Dear Susan,<br>
I understand your desire to see a Thick Whois Model imposed across
the board. Watching the users on the video we watched in MDR
struggle with the searches was painful. Knowing that you struggle
with this issue every day is even worse.<br>
<br>
However, adopting the Applicant Guidebook provisions for New
Registries I don't see as being the right answer. In part, because
it raises as many questions as it answers, and it may pose
instability to the Net.<br>
<br>
To expand: As we have discussed, in the early days, the functions of
Registry and Registrar were not separate and Network Solutions both
managed the database for .COM, .ORG and NET, and also registered
domain names into it.<br>
<br>
In 1999, I believe, ICANN introduced the first bit of competition, 4
registrars to register domain names into the new gTLDs. As more
competition in the registrar business came in (considered a hallmark
of ICANN's work to introduce competition into the domain name
space), the registrars began banging on Network Solutions, then
owned by SAIC, then purchased by Verisign, to stop their compete
ownership and control of the Whois information. It was an element of
the competitive nature of the new domain name space to break up the
information so one registry would not own and control it all.<br>
<br>
The key concern was, of course, .COM. And these issues, and the real
concern of this largest of the registry database, now numbering
almost 100 million names (Oct 2011), would control the customer data
and be able to bypass the new registrars and compete directly for
the registration business, as well as creating a series of
additional business functions. It's an enormous set of competitive
data (as we heard from the Registrars in the Registry/Registrar
meeting in Singapore with us) Registrars remain very committed to
this model, and for legitimate reasons.<br>
<br>
Further, the danger of converting a 100 million database is
enormous. When the Public Interest Registry took over the .ORG
contract (after competitive applications), among the first things it
had to do was convert the ORG registrations to thick ones. There
were only a few million registrations at the time and it was still
an enormous and delicate task. It was a huge moment.<br>
<br>
Such a change, now to the enormous .COM database, is not an easy one
to think about. Every major company in the world has a .COM
registration. These websites are 24*7 operations. The risk to the
Security & Stability of the Net would be one to study closely
and carefully. The difficulties, not to mention risks and
liabilities, would be enormous. <br>
<br>
Is there something we can do, within the confines of our mandate and
our fact-based research and assessment. Yes, I really think there
are. <br>
<br>
We have some key things we have agreed to:<br>
<b>1) Findability </b>- thin registration data should be findable.
That's a technical issue (broken links) and an educational issue
(what's a thin Whois, or better yet, how to I find .COM data). On
education, there is much we can do to educate and help Law
Enforcement and Fraud Investigators (public and private) to find the
data we need. Let's include some recommendations on these.<br>
<b>2) Access & Accuracy </b>- as we have already been
discussing and which are key.<br>
<br>
One thing we could do (and it will make us few friends) is to throw
this kettle of fish into the hands of the registries and registrars
on a timeframe, e.g., six months or one year, for their solutions
and recommendations. They, together with the Community which must
review and accept their solutions, must move quickly. <br>
<br>
But I don't think we can mandate a specific answer. <br>
Best, <br>
Kathy<br>
<br>
<br>
<br>
<br>
<br>
:
<blockquote
cite="mid:CAD6B3759A38A247AC29584C29147EA441989515@SC-MBX02-3.TheFacebook.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 12 (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:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
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;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Just realized
that I did not attach the document to this email last week.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
Susan Kawaguchi
<br>
<b>Sent:</b> Tuesday, November 08, 2011 11:13 PM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:rt4-whois@icann.org">rt4-whois@icann.org</a><br>
<b>Subject:</b> Adopting Specification 4 of the AGB<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Attached is a draft of recommendations for
adopting Specification 4 of the AGB for existing gTlds.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">At the end of the document are rough
thoughts on ICANN creating a voluntary program for registrars
to be considered<b> A</b> list registrars. This would
recognize the responsible registars and the proactive service
they provide.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I will not be on the call tonight since it
is 3 am my time. Not sure anything I would say would make any
sense.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:Consolas">Susan
Kawaguchi<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:Consolas">Domain Name
Manager<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:Consolas"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:Consolas">Facebook Inc.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:Consolas">1601
California Avenue<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:Consolas">Palo Alto, CA<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:Consolas"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:Consolas">Phone - 650
485-6064<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:Consolas">Cell - 650 387
3904<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:Consolas"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:Consolas">Please note my
email address has changed to <a class="moz-txt-link-abbreviated" href="mailto:skawaguchi@fb.com">skawaguchi@fb.com</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">NOTICE: This
email (including any attachments) may contain information
that is private, confidential, or protected by
attorney-client or other privilege. Unless you are the
intended recipient, you may not use, copy, or retransmit the
email or its contents.<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<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>