<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:odc="urn:schemas-microsoft-com:office:odc" 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:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" 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:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:st="" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"
xmlns:ns1="http://schemas.microsoft.com/sharepoint/soap/workflow/"
xmlns:ns2="http://schemas.microsoft.com/office/2006/digsig-setup"
xmlns:ns3="http://schemas.microsoft.com/office/2006/digsig"
xmlns:ns4="http://schemas.openxmlformats.org/package/2006/digital-signature"
xmlns:ns5="http://schemas.openxmlformats.org/markup-compatibility/2006"
xmlns:ns6="http://schemas.microsoft.com/office/2004/12/omml"
xmlns:ns7="http://schemas.openxmlformats.org/package/2006/relationships"
xmlns:ns8="http://microsoft.com/sharepoint/webpartpages"
xmlns:ns9="http://schemas.microsoft.com/exchange/services/2006/types"
xmlns:ns10="http://schemas.microsoft.com/exchange/services/2006/messages"
xmlns:ns11="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/"
xmlns:ns12="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService"
xmlns:ns13="urn:schemas-microsoft-com:"
xmlns:ns0="urn:schemas-microsoft-com:office:smarttags">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>Assessing the "Domain Name Exchange" service proposed by
VeriSign</title>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PostalCode"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="State"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="Street"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="address"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--a:link
{mso-style-priority: 99
;}
span.MSOHYPERLINK
{mso-style-priority: 99
;}
a:visited
{mso-style-priority: 99
;}
span.MSOHYPERLINKFOLLOWED
{mso-style-priority: 99
;}
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 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";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:Calibri;
color:#1F497D;}
span.EmailStyle18
{mso-style-type:personal;
font-family:Calibri;
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal;
font-family:Calibri;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:Calibri;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:Arial;
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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><font size=3 color=blue face=Arial><span style='font-size:
12.0pt;font-family:Arial;color:blue'>I support Mike R’s proposed text and
Sarah’s recommendation.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Arial><span style='font-size:
12.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Arial><span style='font-size:
12.0pt;font-family:Arial;color:blue'>RA<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Arial><span style='font-size:
12.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Ronald N. Andruff</span></font><font
color=blue><span style='color:blue'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>President<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face="Times New Roman"><span
style='font-size:12.0pt;color:blue'> <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>RNA Partners, Inc.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>220 </span></font><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'><ns0:Street w:insAuthor="Owner"
w:insDate="2010-04-09T13:14:00Z" w:endInsAuthor="Owner"
w:endInsDate="2010-04-09T13:14:00Z"><ns0:address w:insAuthor="Owner"
w:insDate="2010-04-09T13:14:00Z" w:endInsAuthor="Owner"
w:endInsDate="2010-04-09T13:14:00Z"><st1:Street w:st="on"><st1:address w:st="on"><font
color=blue><span style='color:blue'>Fifth Avenue</span></font></st1:address></st1:Street></ns0:address></ns0:Street><font
color=blue><span style='color:blue'><o:p></o:p></span></font></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><ns0:place w:insAuthor="Owner" w:insDate="2010-04-09T13:14:00Z"
w:endInsAuthor="Owner" w:endInsDate="2010-04-09T13:14:00Z"><ns0:City
w:insAuthor="Owner" w:insDate="2010-04-09T13:14:00Z" w:endInsAuthor="Owner"
w:endInsDate="2010-04-09T13:14:00Z"><st1:place w:st="on"><st1:City w:st="on"><font
color=blue><span style='color:blue'>New York</span></font></st1:City></ns0:City></st1:place><font
color=blue><span style='color:blue'>, </span></font><ns0:State
w:insAuthor="Owner" w:insDate="2010-04-09T13:14:00Z" w:endInsAuthor="Owner"
w:endInsDate="2010-04-09T13:14:00Z"><st1:State w:st="on"><font color=blue><span
style='color:blue'>New York</span></font></st1:State></ns0:State><font
color=blue><span style='color:blue'> </span></font><ns0:PostalCode
w:insAuthor="Owner" w:insDate="2010-04-09T13:14:00Z" w:endInsAuthor="Owner"
w:endInsDate="2010-04-09T13:14:00Z"><st1:PostalCode w:st="on"><font
color=blue><span style='color:blue'>10001</span></font></st1:PostalCode></ns0:PostalCode></ns0:place><font
color=blue><span style='color:blue'><o:p></o:p></span></font></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>+ 1 212 481 2820 ext. 11<o:p></o:p></span></font></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face="Times New Roman"><span style='font-size:12.0pt;
color:blue'> </span></font><o:p></o:p></p>
</div>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
owner-bc-gnso@icann.org [mailto:owner-bc-gnso@icann.org] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Deutsch, Sarah B<br>
<b><span style='font-weight:bold'>Sent:</span></b> Friday, April 09, 2010 8:58
AM<br>
<b><span style='font-weight:bold'>To:</span></b> Michael D. Palage; bc - GNSO
list<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: [bc-gnso] Assessing
the "Domain Name Exchange" service proposed by VeriSign</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>I like the proposal Mike R. has put on the
table. Given that ICANN previously closed the loophole on the AGP to
deter tasting, which clearly affected the stability of DNS operations, why
couldn't we put forth a call for review since this service has the
potential to destabilize the remedy ICANN already fixed?<br>
<br>
Sarah</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><br>
<br>
<font color=navy><span style='color:navy'>Sarah B. Deutsch <br>
Vice President & Associate General Counsel <br>
Verizon Communications <br>
Phone: 703-351-3044 <br>
Fax: 703-351-3670 </span></font></span></font><o:p></o:p></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabIndex=-1>
</span></font></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</span></font></b><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> owner-bc-gnso@icann.org
[mailto:owner-bc-gnso@icann.org] <b><span style='font-weight:bold'>On Behalf Of
</span></b>Michael D. Palage<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, April 08, 2010
9:24 PM<br>
<b><span style='font-weight:bold'>To:</span></b> 'bc - GNSO list'<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: [bc-gnso] Assessing
the "Domain Name Exchange" service proposed by VeriSign</span></font><o:p></o:p></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>Hello All,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>I am not a big fan
of this proposal. While there may be some market for it, I have a concern that
there is the potential for more harm than good. That being said, this registry
service request has been submitted in accordance with the Funnel Request set
forth in the registry agreement and which gives ICANN a very limited number of
grounds to deny a request</span></font> (i) could raise significant
Security or Stability issues or (ii) could raise significant competition
issues.<font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;
font-family:Calibri;color:#1F497D'>. Again, while I personally do not like this
service, I do not see how either of these criteria are met, and I do not
believe these criteria could be objectively met by the GNSO Council passing a
resolution saying so. Therefore, it is mostly likely that ICANN staff
will approve this request within the 15 day time frame. If there are no
proposed contractual modifications, no Board action would be required.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>Listed below are
some questions which I have asked of VeriSign and the answers that they have
provided. I think Steve and the other BC leaders should reach out to VeriSign
and see if they would be willing to provide a briefing on this service to the
stakeholder group. Perhaps there may be some implement options that VeriSign
would be willing to consider to address our concerns.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>Best regards,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>Michael Palage<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><BEGIN
QUESTIONS><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>Question1: Is
the exchange fee paid each time a name is exchanged after waiting the 30 days,
or is the exchange fee paid once and unlimited changes are permitted for one
year provided that the 30 day calendar lock down period is honored. The reason
I am asking is that I am trying to reconcile the following language in the
funnel request “</span></font><font size=2 color="#365f91" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#365F91'>“<i><span
style='font-style:italic'>The registrar's account balance will be debited the
exchange fee at the time of the initial exchange occurring within a one year
term based upon initial registration date.”<o:p></o:p></span></i></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=red face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:red'>The exchange fee is charged upon initial
exchange, subsequent exchanges during the exchange term are not charged an
exchange fee. In the Business Description section of the Domain Exchange RSEP
we provide the business rules, and I’ve highlighted two rules which
address Michael’s statement around “unlimited changes”, just
for clarity…<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=red face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:red'><o:p> </o:p></span></font></p>
<p class=MsoNormal><i><font size=1 face=Arial><span style='font-size:9.0pt;
font-family:Arial;font-style:italic'>VeriSign will offer the Domain Name
Exchange Service to all .ICANN accredited -registrars in good standing for the
.net top<o:p></o:p></span></font></i></p>
<p class=MsoNormal><i><font size=1 face=Arial><span style='font-size:9.0pt;
font-family:Arial;font-style:italic'>level domain. In order to complete a
Domain Name Exchange:<o:p></o:p></span></font></i></p>
<p class=MsoNormal><i><font size=1 face=Arial><span style='font-size:9.0pt;
font-family:Arial;font-style:italic'>? Registrars shall process the transaction
through their connections to the Shared Registration System ("SRS")
via the<o:p></o:p></span></font></i></p>
<p class=MsoNormal><i><font size=1 face=Arial><span style='font-size:9.0pt;
font-family:Arial;font-style:italic'>Extensible Provisioning Protocol
("EPP").<o:p></o:p></span></font></i></p>
<p class=MsoNormal><i><font size=1 face=Arial><span style='font-size:9.0pt;
font-family:Arial;font-style:italic'>? Registrars will provide the registry
with the necessary data to process the exchange, including the outgoing domain
name<o:p></o:p></span></font></i></p>
<p class=MsoNormal><i><font size=1 face=Arial><span style='font-size:9.0pt;
font-family:Arial;font-style:italic'>and the incoming domain name. This
transaction will be processed as a modification or update to an existing
registration<o:p></o:p></span></font></i></p>
<p class=MsoNormal><i><font size=1 face=Arial><span style='font-size:9.0pt;
font-family:Arial;font-style:italic'>? The registry will validate that the
exchange meets the following criteria:<o:p></o:p></span></font></i></p>
<p class=MsoNormal><i><font size=1 face=Arial><span style='font-size:9.0pt;
font-family:Arial;font-style:italic'>o Registrar must be the
registrar-of-record for the outgoing domain name;<o:p></o:p></span></font></i></p>
<p class=MsoNormal><i><font size=1 face=Arial><span style='font-size:9.0pt;
font-family:Arial;font-style:italic'>o The outgoing and incoming domain name
must be within the same Top Level Domain;<o:p></o:p></span></font></i></p>
<p class=MsoNormal><i><font size=1 color=red face=Arial><span style='font-size:
9.0pt;font-family:Arial;color:red;font-style:italic'>o The outgoing domain name
must have been registered for a minimum of 30 calendar days;<o:p></o:p></span></font></i></p>
<p class=MsoNormal><i><font size=1 color=red face=Arial><span style='font-size:
9.0pt;font-family:Arial;color:red;font-style:italic'>o The outgoing domain has
not been exchanged within the previous 30 calendar days; and<o:p></o:p></span></font></i></p>
<p class=MsoNormal><i><font size=1 face=Arial><span style='font-size:9.0pt;
font-family:Arial;font-style:italic'>o The incoming domain name must be
available.<o:p></o:p></span></font></i></p>
<p class=MsoNormal><i><font size=1 face=Arial><span style='font-size:9.0pt;
font-family:Arial;font-style:italic'>? When an exchange transaction has passed
validation, the registry will execute the exchange by updating the registry<o:p></o:p></span></font></i></p>
<p class=MsoNormal><i><font size=1 face=Arial><span style='font-size:9.0pt;
font-family:Arial;font-style:italic'>database:<o:p></o:p></span></font></i></p>
<p class=MsoNormal><i><font size=1 face=Arial><span style='font-size:9.0pt;
font-family:Arial;font-style:italic'>o The registry will modify the domain name
for the specified registration by deleting the outgoing registration and
inserting the<o:p></o:p></span></font></i></p>
<p class=MsoNormal><i><font size=1 face=Arial><span style='font-size:9.0pt;
font-family:Arial;font-style:italic'>incoming domain name;<o:p></o:p></span></font></i></p>
<p class=MsoNormal><i><font size=1 face=Arial><span style='font-size:9.0pt;
font-family:Arial;font-style:italic'>o The outgoing domain name will have a
pending delete status and be returned to the available pool following
expiration of<o:p></o:p></span></font></i></p>
<p class=MsoNormal><i><font size=1 face=Arial><span style='font-size:9.0pt;
font-family:Arial;font-style:italic'>the pending delete period;<o:p></o:p></span></font></i></p>
<p class=MsoNormal><i><font size=1 face=Arial><span style='font-size:9.0pt;
font-family:Arial;font-style:italic'>o The incoming domain name will
"inherit" all attributes of the registration including create date,
expiration date, name<o:p></o:p></span></font></i></p>
<p class=MsoNormal><i><font size=1 face=Arial><span style='font-size:9.0pt;
font-family:Arial;font-style:italic'>servers, and statuses. Therefore, there is
no Add Grace Period for incoming domain name; and<o:p></o:p></span></font></i></p>
<p class=MsoNormal><i><font size=1 face=Arial><span style='font-size:9.0pt;
font-family:Arial;font-style:italic'>o The incoming domain name will only be
eligible for subsequent exchange after 30 calendar days.<o:p></o:p></span></font></i></p>
<p class=MsoNormal><i><font size=1 face=Arial><span style='font-size:9.0pt;
font-family:Arial;font-style:italic'>? The registry will return a successful
response through the EPP Interface.<o:p></o:p></span></font></i></p>
<p class=MsoNormal><i><font size=1 face=Arial><span style='font-size:9.0pt;
font-family:Arial;font-style:italic'>? The registrar's account balance will be
debited the exchange fee at the time of the initial exchange occurring within a
one<o:p></o:p></span></font></i></p>
<p class=MsoNormal><i><font size=1 face=Arial><span style='font-size:9.0pt;
font-family:Arial;font-style:italic'>year term based upon initial registration
date.<o:p></o:p></span></font></i></p>
<p class=MsoNormal><i><font size=1 face=Arial><span style='font-size:9.0pt;
font-family:Arial;font-style:italic'>? The registry will propagate the change
in DNS and Whois.</span></font></i><font size=2 color=red face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:red'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=red face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:red'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>Question 2: VeriSign
has touted the use of its WhoWas verification as a mechanism to help identify
potential abuse. Will VRSN be charging for this WhoWas feature or will it be
free?<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=red face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:red'>As stated in the Who Was Registry Service
proposal there will be a nominal fee in order to offset the implementation,
maintenance and operational costs of providing the service.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>Question 3: VeriSign
says that it will publish “</span></font><i><font size=1 face=Arial><span
style='font-size:9.0pt;font-family:Arial;font-style:italic'>a report that lists
the domain names exchanged as part of a registration.” </span></font></i><font
size=1 face=Arial><span style='font-size:9.0pt;font-family:Arial'>Will there be
a fee for accessing these reports, and how will they be provided and to whom
will they be provided.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=red face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:red'>Domain Exchange reports like all activity
reports will be provided to the registrar of record at no cost, and made
available over existing FTP and web interfaces.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><END
QUESTIONS><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
owner-bc-gnso@icann.org [mailto:owner-bc-gnso@icann.org] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Susan Kawaguchi<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, April 08, 2010
6:43 PM<br>
<b><span style='font-weight:bold'>To:</span></b> icann@rodenbaugh.com; 'bc -
GNSO list'<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: [bc-gnso] Assessing
the "Domain Name Exchange" service proposed by VeriSign<o:p></o:p></span></font></p>
</div>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>It would be good to
get clarification on several issues from Verisign. Do you think they
would talk to the BC about their proposal? <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>Susan Kawaguchi<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>Domain Name Manager<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><br>
Facebook Inc. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>1601 S. California
Avenue <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>Palo Alto, CA <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>Phone - 650 485-6064<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>Cell - 650 387 3904<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>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></font></p>
</div>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
owner-bc-gnso@icann.org [mailto:owner-bc-gnso@icann.org] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Mike Rodenbaugh<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, April 08, 2010
3:23 PM<br>
<b><span style='font-weight:bold'>To:</span></b> 'bc - GNSO list'<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: [bc-gnso] Assessing
the "Domain Name Exchange" service proposed by VeriSign<o:p></o:p></span></font></p>
</div>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>Ooops, my post was
missing an important “NOT” in second sentence, now inserted…<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
owner-bc-gnso@icann.org [mailto:owner-bc-gnso@icann.org] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Mike Rodenbaugh<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, April 08, 2010
2:50 PM<br>
<b><span style='font-weight:bold'>To:</span></b> 'bc - GNSO list'<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: [bc-gnso] Assessing
the "Domain Name Exchange" service proposed by VeriSign<o:p></o:p></span></font></p>
</div>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>Thanks both Steve
and Sarah for the thoughtful posts. I agree this proposal needs further
consideration and public comment, and should NOT be
‘rubber-stamped’ by ICANN, like most RSEP proposals. It
certainly has the potential to unravel a lot of the progress made with the AGP
Limits policy. Another mitigation step could be to limit the percentage
of any registrar’s domains that can be exchanged, similar to the AGP
Limits policy.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>We could make a
motion for the next GNSO Council meeting on 4/21, to see if the Council would
ask Staff to conduct further consideration. The deadline for such a
motion is 4/13. I suspect it would have broad support from the NCSG, and
probably none from the CSG, but it might still pass depending upon attendance at
the meeting, and in any event ought to serve the purpose. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>Individual member
and constituency comments should also be submitted to ICANN directly. Do
we have BC consensus at least on the following?<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>[DRAFT]<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>The BC requests that
Staff make the preliminary determination, with respect to Versign’s RSEP
proposal for “domain exchange” services in the .net TLD, that this
proposal requires further study because it could raise significant issues with
security and stability and/or competition. Specifically, the proposal may
permit resumption of commercial “domain tasting” activities which
have been curbed by the AGP Limits policy, and therefore appropriate
limitations on the proposed registry service must be considered.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>Mike Rodenbaugh<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>RODENBAUGH LAW<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'>tel/fax: +1
(415) 738-8087<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><a
href="http://rodenbaugh.com/">http://rodenbaugh.com</a><o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p> </o:p></span></font></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
owner-bc-gnso@icann.org [mailto:owner-bc-gnso@icann.org] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Deutsch, Sarah B<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, April 08, 2010
2:19 PM<br>
<b><span style='font-weight:bold'>To:</span></b> Steve DelBianco; bc - GNSO
list<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: [bc-gnso] Assessing
the "Domain Name Exchange" service proposed by VeriSign<o:p></o:p></span></font></p>
</div>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Steve,</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Thanks for giving all of us more
background on the proposed Verisign service. My view is that because this
proposal could pass through very quickly with little ICANN input and has very
serious potential consequences for businesses and brand owners, we should
quickly reach out to ICANN staff and tell them that there are enough concerns
that the process must be slowed down and studied carefully.</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>The concerns I've raised have nothing to
do with someone registering generic names. Whether we call it
"tasting" or something else, the fact remains that this service
allows someone for the price of a single domain name, to register at
least 12 different domain names a year. So, if you spent $8 to
register 100 domain names under the exchange service, you could wind up
registering nearly 10,000 different domain names. On its face, this seems
to be a recipe for mischief and abuse.</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>When we had full blown domain name tasting
under the AGP for free, the number of infringements skyrocketed, but even
today, brand owners face thousands of instances of new infringements
because cybersquatters are still willing to pay a relatively low registration
fee for the high quality names that drive traffic. The recent
report on cybersquatting out of Harvard shows that even vigilant
companies like Verizon still face many hundreds of typosquatting incidents --
all from infringers who are willing to pay a fee for our trademarked
names. The report estimates that the top 100,000 websites
containing cybersquatted domains collectively receive at least 68.2
million daily visitors. If these cybersquatted sites were considered as a
single website, they would be ranked by Alexa as the 10th most popular website
in the world. So it is reasonable to be concerned that a service which
allows one to register multiple domain names for a single price will only add
to this problem.</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>I appreciate that Verisign believes it has
taken some steps to make their service more "transparent," but I
don't believe transparency is the same as fixing your business model to prevent
infringements in the first place. A few questions, comments and ideas:</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>1) A "free" reporting service on
exchanged names is better than no reporting service -- but it appears that the
burden, administrative costs and enforcement costs shifts to business
and brand holders, who on a daily or even hourly basis,
must check this reporting service for possible infringements.
What will Verisign do when the brand holder writes to them and demands they
stop selling the name? My guess is that they would not be
accountable for taking this name out of circulation and the trademark
owner would be sending numerous cease and desist letters, filing more UDRP actions
and filing more lawsuits.</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>2) Your mention of the WHOWAS service does
not say whether this will be provided for free or at a cost. In any case,
the same concerns about pushing the burden on trademark owners remains.
Also, what steps does Verisign intend to take to ensure the accuracy of the
information provided in its WHOIS, WHOAS and its reporting service associated
with this service? Will it permit applicants to "exchange"
names through a proxy service?</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>3) Will there be a cap on the number of domain
names someone could register under the exchange service?</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>If Verisign is serious about limiting
harms to brand owners, why not: </span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>1) Limit the service to generic names
only? Why not allow trademark owners to provide Verisign with a list of
their registered trademarks that should not be permitted to be sold under the
exchange service and allow them to opt names out of this service? </span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>2) Why not build in protections for the
trademark owner up front when offering the service? For example, when an applicant
searches for the availability of a name, the trademarked names provided
by owners who opt out would pop up with a warning telling the
applicant that the name is a trademark owned by a third party, warning them
about the penalties associated with cybersquatting and requiring them to
declare that they have a legal right to use such name.</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>3) Why not beef up requirements for
accurate WHOIS contact information and prohibit exhanging names through a
proxy?</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Obviously, the issues are all quite
complicated as are the potential fixes, so more reason that this proposal be
slowed down and studied carefully with all affected stakeholders.</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><br>
</span></font><font size=2 color=blue face=Arial><span style='font-size:10.0pt;
font-family:Arial;color:blue'>Thanks,</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><br>
</span></font><font size=2 color=blue face=Arial><span style='font-size:10.0pt;
font-family:Arial;color:blue'>Sarah</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><br>
<br>
<font color=navy><span style='color:navy'>Sarah B. Deutsch <br>
Vice President & Associate General Counsel <br>
Verizon Communications <br>
Phone: 703-351-3044 <br>
Fax: 703-351-3670 </span></font></span></font><o:p></o:p></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center>
</span></font></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</span></font></b><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
owner-bc-gnso@icann.org [mailto:owner-bc-gnso@icann.org] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Steve DelBianco<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, April 08, 2010
11:05 AM<br>
<b><span style='font-weight:bold'>To:</span></b> bc - GNSO list<br>
<b><span style='font-weight:bold'>Subject:</span></b> [bc-gnso] Assessing the
"Domain Name Exchange" service proposed by VeriSign</span></font><o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=2
face="Times New Roman"><span style='font-size:10.0pt'>BC Members:<br>
<br>
On April 5, VeriSign (operator of .com, .net, and .name) proposed a new
registry service called "Domain Name Exchange."
VeriSign’s proposal and QA& is posted at <a
href="http://www.icann.org/en/registries/rsep/verisign-dnex-05apr10-en.pdf">http://www.icann.org/en/registries/rsep/verisign-dnex-05apr10-en.pdf</a>
Here’s how VeriSign describes the service:</span></font><o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><i><font size=2
face="Times New Roman"><span style='font-size:10.0pt;font-style:italic'>Based
on ongoing discussions with registrars who represent diverse business models
and market segments, VeriSign has developed the concept for the Domain Name
Exchange Service to allow a registrar to repurpose a domain name registration
that has significant time remaining until expiration. Today when a
registrant terminates a package of services from a registrar after, for
example, an introductory 1 or 3 month period, the registrar is forced to recoup
the investment in the associated domain via monetization or the secondary
market. The domain exchange will allow a registrar to offer another registrant
a package that sits on top of that same registration using a new domain.<br>
The Domain Name Exchange Service is an optional service that is designed to
provide registrars and registrants with an effective and efficient way to
manage domain name registration terms for domain names that are no longer
needed.</span></font></i><o:p></o:p></p>
<p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:
10.0pt'>For many website hosting service providers, the registration of a
domain name is a secondary service. For example, the European registrar <br>
1and1 offers web hosting with “free domains included” ( <u><font
color=blue><span style='color:blue'><a href="http://1and1.eu">http://1and1.eu</a></span></font></u>
) in order to attract new clients to establish their online presence.
Domain Exchange lets 1&1 re-use the registration if a client wants to
drop the website and domain after just a few months. Registrars
would pay around 1.5x the cost of a regular annual registration in order to get
the Exchange option, and they could exchange once per month. Perhaps
there will be significant demand for this service from registrars who have lots
of turnover with hosting clients.<br>
<br>
Domain Exchange is being proposed only for .net domains, but VeriSign may
propose it for .com at some point. And that’s where several BC
officers are already raising concerns that Domain Exchange could be a new form
of “domain tasting” that would lead to even more cyber-squatting
and typo-squatting. <br>
<br>
“Domain tasting” is a loaded term in ICANN circles.
“Tasting” is how domainers test a domain name to learn
whether type-in traffic generates enough advertising revenue to cover costs of
registering the domain. The names typically tasted were
generic words and phrases (like SpringCleaning.com or SpringFashions.com) that
some users might guess at by entering the URL ( instead of going thru a page-ranked
search engine). <br>
Domainers make money on these domain names by “parking” a page with
ads for related products and services. <br>
<br>
The parked pages that result from tasted names are objectionable in the way
that highway billboards are objectionable, but there’s nothing illegal
about monetizing domain traffic with advertising. Moreover, several BC
members are domainers who monetize traffic this way, and other BC members
providing online advertising services to support the trade. <br>
<br>
But nothing infuriates BC members and Internet users more than tasting or
parking domains that involve trademarked terms or typographical variants
designed to deceive users. Cybersquatting and typosquatting could
increase if a new service makes it easier to discover domain names that mislead
users into thinking they have landed on a page belonging to a known business or
organization they intended to reach.<br>
<br>
Domainers discovered they could taste traffic for 5 days for zero cost by using
the Add Grace Period (AGP) that has always been offered by registrars and
registries. That led to rampant tasting in domains like .com.
The ICANN community, incl many in the BC, pushed ICANN to end the
practice of free tasting thru abuse of the AGP privilege. Using the
policy development process, ICANN effectively eliminated free AGP tasting in
2009 (<a href="http://www.icann.org/en/tlds/agp-policy-17dec08-en.htm">http://www.icann.org/en/tlds/agp-policy-17dec08-en.htm</a>
)<br>
<br>
Question is, will a new Domain Exchange service increase the incidence of
trademark and typographical squatting? I asked my friends at VeriSign (a
NetChoice member) about this concern, and here’s what I learned: <br>
<br>
Domain Exchange is not going to replace the free and unchecked tasting that was
done with AGP before 2009. First, a domain 'taster' has to actually buy a
1-year registration to be able to use domain exchange at 11 monthly intervals.
That’s cheaper than buying a dozen registrations, but its not free.
Second, it would take a year just to 'taste' a dozen names for ad traffic.
<br>
<br>
Still, VeriSign acknowledges that some parties may see Domain Exchange as a way
to “taste” and then register names that infringe on trademarks.
So VeriSign is offering additional IP protection tools described in their
proposal, such as limitations on exchanges, free reporting on exchanged names,
and the WhoWas service (a permanent record of historical Whois). <br>
<br>
VeriSign is open to suggestions from the BC (and IPC) about other tools that
would minimize use of Domain Exchange for TM infringement or other illegal
purposes. They’re also prepared to answer questions in a direct
dialogue with our members if that’s easier and quicker than using the
public comment process described below.<br>
<br>
So let’s begin internal discussions on BC List, with an intent to send
concerns and questions to staff, to VeriSign, and eventually in ICANN public
comments.<br>
<u><br>
<br>
Finally, a word about the ICANN process for review and approval of new registry
services</u>: </span></font><o:p></o:p></p>
<p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:
10.0pt'><br>
ICANN evaluates new registry services thru its Registry Service Evaluation
Process (RSEP). ICANN staff has 15-days to make a "preliminary
determination" whether this Registry Service requires further
consideration by ICANN because it could raise significant issues with Security
& Stability or competition. There’s no official comment period
during these 15 days, but BC members can always explain concerns to staff.
See RSEP at <a href="http://www.icann.org/en/registries/rsep/rsep.html">http://www.icann.org/en/registries/rsep/rsep.html</a><br>
<br>
If ICANN determines that the service might raise significant Stability or
Security issues, it goes to the Registry Services Technical Evaluation Panel
and simultaneously invites public comment on the proposal (2nd chance to
comment). This panel has 45 days to do a written report regarding the
proposed service effect on Security or Stability.<br>
<br>
ICANN’s Board then posts the report for public comment (3rd chance to
comment), and the Board has 30 days to reach a decision. “In the event
the ICANN Board reasonably determines that the proposed Registry Service
creates a reasonable risk of a meaningful adverse effect on Stability or
Security, Registry Operator will not offer the proposed Registry
Service.”<br>
<br>
So there are 2 or 3 chances to comment over a period of 45 days (or 90 days if
the panel raises S&S concerns). </span></font><o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
</div>
</body>
</html>