<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" 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:wf =
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss =
"http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi =
"http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi =
"http://schemas.openxmlformats.org/package/2006/digital-signature" 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:spwp =
"http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t =
"http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m =
"http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl =
"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl =
"http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService"
XMLNS:Z = "urn:schemas-microsoft-com:" xmlns:st = ""><HEAD><TITLE>Assessing the "Domain Name Exchange" service proposed by VeriSign</TITLE>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18904"><!--[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]-->
<STYLE>@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12pt
}
LI.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12pt
}
DIV.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12pt
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: personal
}
SPAN.EmailStyle18 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: personal
}
SPAN.EmailStyle19 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: personal
}
SPAN.EmailStyle20 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
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><SPAN class=732595512-09042010><FONT color=#0000ff size=2 face=Arial>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</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV align=left><FONT size=2 face=Arial><BR><BR><FONT color=#000080>Sarah B.
Deutsch <BR>Vice President & Associate General Counsel <BR>Verizon
Communications <BR>Phone: 703-351-3044 <BR>Fax: 703-351-3670
</FONT><BR></FONT></DIV>
<DIV> </DIV><BR>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> owner-bc-gnso@icann.org
[mailto:owner-bc-gnso@icann.org] <B>On Behalf Of </B>Michael D.
Palage<BR><B>Sent:</B> Thursday, April 08, 2010 9:24 PM<BR><B>To:</B> 'bc - GNSO
list'<BR><B>Subject:</B> RE: [bc-gnso] Assessing the "Domain Name Exchange"
service proposed by VeriSign<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Hello
All,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">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> (i) could raise significant
Security or Stability issues or (ii) could raise significant competition
issues.<SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">.
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></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">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></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Best
regards,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Michael
Palage<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><BEGIN
QUESTIONS><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">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><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #365f91; FONT-SIZE: 11pt">“<I>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></I></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: navy; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: red; FONT-SIZE: 10pt">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></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: red; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">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></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">level domain. In order
to complete a Domain Name Exchange:<o:p></o:p></SPAN></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">? Registrars shall
process the transaction through their connections to the Shared Registration
System ("SRS") via the<o:p></o:p></SPAN></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">Extensible
Provisioning Protocol ("EPP").<o:p></o:p></SPAN></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">? Registrars will
provide the registry with the necessary data to process the exchange, including
the outgoing domain name<o:p></o:p></SPAN></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">and the incoming
domain name. This transaction will be processed as a modification or update to
an existing registration<o:p></o:p></SPAN></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">? The registry will
validate that the exchange meets the following
criteria:<o:p></o:p></SPAN></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">o Registrar must be
the registrar-of-record for the outgoing domain name;<o:p></o:p></SPAN></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">o The outgoing and
incoming domain name must be within the same Top Level
Domain;<o:p></o:p></SPAN></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: red; FONT-SIZE: 9pt">o The
outgoing domain name must have been registered for a minimum of 30 calendar
days;<o:p></o:p></SPAN></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: red; FONT-SIZE: 9pt">o The
outgoing domain has not been exchanged within the previous 30 calendar days;
and<o:p></o:p></SPAN></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">o The incoming domain
name must be available.<o:p></o:p></SPAN></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">? When an exchange
transaction has passed validation, the registry will execute the exchange by
updating the registry<o:p></o:p></SPAN></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">database:<o:p></o:p></SPAN></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">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></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">incoming domain
name;<o:p></o:p></SPAN></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">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></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">the pending delete
period;<o:p></o:p></SPAN></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">o The incoming domain
name will "inherit" all attributes of the registration including create date,
expiration date, name<o:p></o:p></SPAN></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">servers, and statuses.
Therefore, there is no Add Grace Period for incoming domain name;
and<o:p></o:p></SPAN></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">o The incoming domain
name will only be eligible for subsequent exchange after 30 calendar
days.<o:p></o:p></SPAN></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">? The registry will
return a successful response through the EPP
Interface.<o:p></o:p></SPAN></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">? 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></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">year term based upon
initial registration date.<o:p></o:p></SPAN></I></P>
<P class=MsoNormal><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">? The registry will
propagate the change in DNS and Whois.</SPAN></I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: red; FONT-SIZE: 10pt"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: red; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">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></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: navy; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: red; FONT-SIZE: 10pt">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></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: navy; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Question
3: VeriSign says that it will publish “</SPAN><I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">a report that lists
the domain names exchanged as part of a registration.” </SPAN></I><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 9pt">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></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: navy; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: red; FONT-SIZE: 10pt">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></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><END
QUESTIONS><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">
owner-bc-gnso@icann.org [mailto:owner-bc-gnso@icann.org] <B>On Behalf Of
</B>Susan Kawaguchi<BR><B>Sent:</B> Thursday, April 08, 2010 6:43
PM<BR><B>To:</B> icann@rodenbaugh.com; 'bc - GNSO list'<BR><B>Subject:</B> RE:
[bc-gnso] Assessing the "Domain Name Exchange" service proposed by
VeriSign<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">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></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Susan
Kawaguchi<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Domain
Name Manager<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><BR>Facebook
Inc. <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">1601
S. California Avenue <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Palo
Alto, CA <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Phone
- 650 485-6064<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Cell
- 650 387 3904<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">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></DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">
owner-bc-gnso@icann.org [mailto:owner-bc-gnso@icann.org] <B>On Behalf Of
</B>Mike Rodenbaugh<BR><B>Sent:</B> Thursday, April 08, 2010 3:23
PM<BR><B>To:</B> 'bc - GNSO list'<BR><B>Subject:</B> RE: [bc-gnso] Assessing the
"Domain Name Exchange" service proposed by
VeriSign<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Ooops,
my post was missing an important “NOT” in second sentence, now
inserted…<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">
owner-bc-gnso@icann.org [mailto:owner-bc-gnso@icann.org] <B>On Behalf Of
</B>Mike Rodenbaugh<BR><B>Sent:</B> Thursday, April 08, 2010 2:50
PM<BR><B>To:</B> 'bc - GNSO list'<BR><B>Subject:</B> RE: [bc-gnso] Assessing the
"Domain Name Exchange" service proposed by
VeriSign<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">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></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">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></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">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></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">[DRAFT]<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">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></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Mike
Rodenbaugh<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">RODENBAUGH
LAW<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">tel/fax:
+1 (415) 738-8087<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><A
href="http://rodenbaugh.com/">http://rodenbaugh.com</A><o:p></o:p></SPAN></P></DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">
owner-bc-gnso@icann.org [mailto:owner-bc-gnso@icann.org] <B>On Behalf Of
</B>Deutsch, Sarah B<BR><B>Sent:</B> Thursday, April 08, 2010 2:19
PM<BR><B>To:</B> Steve DelBianco; bc - GNSO list<BR><B>Subject:</B> RE:
[bc-gnso] Assessing the "Domain Name Exchange" service proposed by
VeriSign<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">Steve,</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">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><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">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><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">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><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">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><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">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><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">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><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">3) Will
there be a cap on the number of domain names someone could register under the
exchange service?</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">If
Verisign is serious about limiting harms to brand owners, why not:
</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">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><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">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><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">3) Why
not beef up requirements for accurate WHOIS contact information and prohibit
exhanging names through a proxy?</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">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><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><BR><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">Thanks,</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><BR><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">Sarah</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt"><BR><BR><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></SPAN><o:p></o:p></P>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<DIV style="TEXT-ALIGN: center" class=MsoNormal align=center>
<HR align=center SIZE=2 width="100%">
</DIV>
<P style="MARGIN-BOTTOM: 12pt" class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">
owner-bc-gnso@icann.org [mailto:owner-bc-gnso@icann.org] <B>On Behalf Of
</B>Steve DelBianco<BR><B>Sent:</B> Thursday, April 08, 2010 11:05
AM<BR><B>To:</B> bc - GNSO list<BR><B>Subject:</B> [bc-gnso] Assessing the
"Domain Name Exchange" service proposed by VeriSign</SPAN><o:p></o:p></P>
<P style="MARGIN-BOTTOM: 12pt" class=MsoNormal><SPAN style="FONT-SIZE: 10pt">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><o:p></o:p></P>
<P style="MARGIN-BOTTOM: 12pt" class=MsoNormal><I><SPAN
style="FONT-SIZE: 10pt">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></I><o:p></o:p></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt">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><SPAN style="COLOR: blue"><A
href="http://1and1.eu">http://1and1.eu</A></SPAN></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><o:p></o:p></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt"><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><o:p></o:p></P>
<P style="MARGIN-BOTTOM: 12pt"
class=MsoNormal><o:p> </o:p></P></DIV></BODY></HTML>