<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<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:12.0pt;
font-family:"Times New Roman","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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 77.95pt 1.0in 77.95pt;}
div.Section1
{page:Section1;}
-->
</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=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Jeff,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I believe that part of what Iron Mountain is doing is looking at
the data randomly and verifying that it is complete and correct. I think they
have to report to ICANN that we have delivered properly formatted data, and
that they look in detail at a subset of it for these purposes.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>So while I think your idea is a great one, I don’t think it
could be applied here, as Iron Mountain would need to have the keys.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Rob.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>P.S. Hs anyone thought to ask Iron Mountain to give up their
ICANN accreditation ? Seems to me that this contract is probably worth much
more to them than the accreditation they are not using. They might be willing
to just give it up in order to win the contract, thus removing all competitive
concerns.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
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"'>
owner-registrars@gnso.icann.org [mailto:owner-registrars@gnso.icann.org] <b>On
Behalf Of </b>Jeffrey Eckhaus<br>
<b>Sent:</b> Friday, August 24, 2007 11:21 AM<br>
<b>To:</b> registrars@gnso.icann.org<br>
<b>Cc:</b> Tim Cole; Mike Zupke<br>
<b>Subject:</b> [registrars] Information regarding Data Escrow<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoPlainText><span style='font-family:"Arial","sans-serif"'>All, <o:p></o:p></span></p>
<p class=MsoPlainText><span style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoPlainText><span style='font-family:"Arial","sans-serif"'>I did not
see this covered in the questionnaire from Iron Mountain, so maybe I missed
this, but will there be a form of data encryption held by ICANN only? <o:p></o:p></span></p>
<p class=MsoPlainText><span style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'>We have been thinking of solutions and one
possible solution for the concerns of Iron Mountain looking at registrar data
is using a form of public key cryptography, where the registrars are all given
ICANN's public key and only ICANN holds the private key. All of the
registrars will encrypt their data with that public key, and in the event that
this data is necessary, the encrypted data can be delivered to ICANN and they
can use the private key to decrypt it. This way, even if IRON Mountain
does look at our data, it's useless to them in an encrypted form. Only ICANN
can see the data<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'>If this was covered then I apologize, but if
not would like this to be considered and thoughts from other Registrars<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'>Thanks<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'>Jeff<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt;
font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt;
font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>-----Original Message-----<br>
From: owner-registrars@gnso.icann.org [mailto:owner-registrars@gnso.icann.org]
On Behalf Of Tim Ruiz<br>
Sent: Friday, August 17, 2007 10:36 AM<br>
To: registrars@gnso.icann.org<br>
Subject: RE: [registrars] FW: Information regarding Data Escrow<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Agreed. All valid issues we'll also consider before
selecting ICANN's<o:p></o:p></p>
<p class=MsoPlainText>agent or another. And the separation issue should likely
be covered<o:p></o:p></p>
<p class=MsoPlainText>whether the agent is currently accredited as a registrar
or not, since<o:p></o:p></p>
<p class=MsoPlainText>that could obviously change.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Tim <o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>-------- Original Message --------<o:p></o:p></p>
<p class=MsoPlainText>Subject: RE: [registrars] FW: Information regarding Data
Escrow<o:p></o:p></p>
<p class=MsoPlainText>From: "Nevett, Jonathon"
<jnevett@networksolutions.com><o:p></o:p></p>
<p class=MsoPlainText>Date: Fri, August 17, 2007 8:58 am<o:p></o:p></p>
<p class=MsoPlainText>To: "Tim Ruiz" <tim@godaddy.com>,
<registrars@gnso.icann.org><o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>I am reserving my comments on the escrow program and on
Iron Mountain<o:p></o:p></p>
<p class=MsoPlainText>until a draft contract is available for review. I
appreciate that Iron<o:p></o:p></p>
<p class=MsoPlainText>Mountain has provided answers to a questionnaire about
how it would<o:p></o:p></p>
<p class=MsoPlainText>protect our customer data and how it would address the
perceived<o:p></o:p></p>
<p class=MsoPlainText>conflict or interest situation, but we don't know how
that will<o:p></o:p></p>
<p class=MsoPlainText>translate into a contract. Will Iron Mountain agree
contractually to<o:p></o:p></p>
<p class=MsoPlainText>some sort of structural separation between its registrar
business and<o:p></o:p></p>
<p class=MsoPlainText>this escrow arrangement? What contractual warranties will
Iron Mountain<o:p></o:p></p>
<p class=MsoPlainText>provide that it will protect our customer data and cover
us in case of a<o:p></o:p></p>
<p class=MsoPlainText>breach? Similarly, if ICANN wants to access the data for
checking<o:p></o:p></p>
<p class=MsoPlainText>purposes, what contractual warranties and protections
will it provide to<o:p></o:p></p>
<p class=MsoPlainText>registrars in order to give us comfort that our customer
data will be<o:p></o:p></p>
<p class=MsoPlainText>protected? Perhaps ICANN should be negotiating with the
top two bidders<o:p></o:p></p>
<p class=MsoPlainText>to ensure that the contract is as competitive as
possible.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Thanks.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Jon<o:p></o:p></p>
<p class=MsoPlainText>-----Original Message-----<o:p></o:p></p>
<p class=MsoPlainText>From: owner-registrars@gnso.icann.org<o:p></o:p></p>
<p class=MsoPlainText>[mailto:owner-registrars@gnso.icann.org] On Behalf Of Tim
Ruiz<o:p></o:p></p>
<p class=MsoPlainText>Sent: Friday, August 17, 2007 8:46 AM<o:p></o:p></p>
<p class=MsoPlainText>To: registrars@gnso.icann.org<o:p></o:p></p>
<p class=MsoPlainText>Subject: RE: [registrars] FW: Information regarding Data
Escrow<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Larry, appreciate your concerns.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>1) Most likely, yes. Escrowing the beneficial user data
behind<o:p></o:p></p>
<p class=MsoPlainText>private/proxied registrations is not required under the
currently<o:p></o:p></p>
<p class=MsoPlainText>proposed process. But two points about that. First,
speaking just for Go<o:p></o:p></p>
<p class=MsoPlainText>Daddy, while there are a large number of our domain names
registered<o:p></o:p></p>
<p class=MsoPlainText>through Domains by Proxy the majority are not. Second,
Domains by Proxy<o:p></o:p></p>
<p class=MsoPlainText>is willing to escrow the beneficial user data but not
likely under the<o:p></o:p></p>
<p class=MsoPlainText>standard Escrow agreement. So that will be discussed with
ICANN and<o:p></o:p></p>
<p class=MsoPlainText>hopefully worked out soon. And after our experience with
assuming the<o:p></o:p></p>
<p class=MsoPlainText>RegisterFly names, I hope other registrars who offer
private/proxied<o:p></o:p></p>
<p class=MsoPlainText>registrations will consider it as well.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>2) You're assuming that Iron Mountain is currently mining
data? Our<o:p></o:p></p>
<p class=MsoPlainText>records show no evidence of that at all. I would suggest
that before<o:p></o:p></p>
<p class=MsoPlainText>making any judgement you look closely at who Iron
Mountain is how<o:p></o:p></p>
<p class=MsoPlainText>they've built their publicly traded company on a
worldwide reputation of<o:p></o:p></p>
<p class=MsoPlainText>trust and security. Corp. Domain management is a small
part of their<o:p></o:p></p>
<p class=MsoPlainText>overall business. It's hard to imagine them sacrificing
that reputation<o:p></o:p></p>
<p class=MsoPlainText>for what little they might gain from data that is otherwise
public<o:p></o:p></p>
<p class=MsoPlainText>anyway.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>3) I doubt that ICANN can select a provider that all
registrars will be<o:p></o:p></p>
<p class=MsoPlainText>100% happy with. So there is no requirement to use
ICANN's selected<o:p></o:p></p>
<p class=MsoPlainText>agent. Some are going to use their own agent regardless.
Is Iron<o:p></o:p></p>
<p class=MsoPlainText>Mountain more of a risk just because they are accredited
any more so<o:p></o:p></p>
<p class=MsoPlainText>than another agent who isn't? You may have a different
answer to that<o:p></o:p></p>
<p class=MsoPlainText>than we do. Fortunately, we'll all have a choice.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Bottom line, registrars are under fire right now due to
recent events.<o:p></o:p></p>
<p class=MsoPlainText>We need to get this escrow thing figured out and
implemented. If we<o:p></o:p></p>
<p class=MsoPlainText>delay with the idea that we need a process that 100% of
us are 100%<o:p></o:p></p>
<p class=MsoPlainText>happy with it will never get done.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Tim <o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
</div>
</body>
</html>