RE: status quo [RE: [gnso-rn-wg] gTLD Reserved Names Chart]

[Tim Ruiz <tim@xxxxxxxxxxx>]

<div>
Edmon, there is still no valid argument for creating a policy that
perpetuates this condition for new gTLD registries. If Ray's argument about 
contractual issues holds water regarding existing gTLDs, then maybe your points 
below are valid. Although, I still think the idea that one competitor needs 
permission from another to do business within their own space is questionable, 
regardless of the conditions put on it.</div>
<div><BR><BR>Tim <BR></div>
<div   name="wmMessageComp"><BR><BR>
<BLOCKQUOTE style="PADDING-LEFT: 8px; MARGIN-LEFT: 8px; BORDER-LEFT: blue 2px 
solid" webmail="1">-------- Original Message --------<BR>Subject: status quo 
[RE: [gnso-rn-wg] gTLD Reserved Names Chart]<BR>From: "Edmon Chung" 
&lt;edmon@xxxxxxxxxxx&gt;<BR>Date: Thu, May 03, 2007 12:36 pm<BR>To: "'Tim 
Ruiz'" &lt;tim@xxxxxxxxxxx&gt;, "'Ray Fassett'" &lt;ray@xxxxxxxxx&gt;<BR>Cc: 
"'Patrick Jones'" &lt;patrick.jones@xxxxxxxxx&gt;, 
&lt;gnso-rn-wg@xxxxxxxxx&gt;<BR><BR>
<STYLE>
 #wmMessageComp #wmMessage v\:*   {behavior:url(#default#VML);}
 #wmMessageComp #wmMessage o\:*   {behavior:url(#default#VML);}
 #wmMessageComp #wmMessage w\:*   {behavior:url(#default#VML);}
 #wmMessageComp #wmMessage .shape   {behavior:url(#default#VML);}

</STYLE>

<STYLE>
 #wmMessageComp #wmMessage /* Font Definitions */ @font-face   
{font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0;}
 #wmMessageComp #wmMessage @font-face   
{font-family:&#26032;&#32048;&#26126;&#39636;; panose-1:2 2 5 0 0 0 0 0 0 0;}
 #wmMessageComp #wmMessage @font-face   {font-family:"Cambria Math"; panose-1:2 
4 5 3 5 4 6 3 2 4;}
 #wmMessageComp #wmMessage @font-face   {font-family:"Arial Unicode MS"; 
panose-1:2 11 6 4 2 2 2 2 2 4;}
 #wmMessageComp #wmMessage @font-face   {font-family:Tahoma; panose-1:2 11 6 4 
3 5 4 4 2 4;}
 #wmMessageComp #wmMessage @font-face   {font-family:"\@Arial Unicode MS"; 
panose-1:2 11 6 4 2 2 2 2 2 4;}
 #wmMessageComp #wmMessage @font-face   
{font-family:"\@&#26032;&#32048;&#26126;&#39636;"; panose-1:2 2 5 0 0 0 0 0 0 
0;}
 #wmMessageComp #wmMessage /* Style Definitions */ p.MsoNormal, #wmMessageComp 
#wmMessage li.MsoNormal, #wmMessageComp #wmMessage div.MsoNormal   {margin:0cm; 
margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman","serif";}
 #wmMessageComp #wmMessage span.emailstyle17   {mso-style-name:emailstyle17;}
 #wmMessageComp #wmMessage span.emailstyle18   {mso-style-name:emailstyle18;}
 #wmMessageComp #wmMessage span.emailstyle19   {mso-style-name:emailstyle19;}
 #wmMessageComp #wmMessage span.emailstyle20   {mso-style-name:emailstyle20;}
 #wmMessageComp #wmMessage span.emailstyle21   {mso-style-name:emailstyle21;}
 #wmMessageComp #wmMessage span.EmailStyle22   {mso-style-type:personal; 
font-family:"Arial","sans-serif"; color:windowtext;}
 #wmMessageComp #wmMessage span.EmailStyle23   {mso-style-type:personal; 
font-family:"Arial","sans-serif"; color:windowtext;}
 #wmMessageComp #wmMessage span.EmailStyle24   {mso-style-type:personal; 
font-family:"Arial","sans-serif"; color:windowtext;}
 #wmMessageComp #wmMessage span.EmailStyle25   {mso-style-type:personal; 
font-family:"Arial","sans-serif"; color:navy;}
 #wmMessageComp #wmMessage span.EmailStyle26   {mso-style-type:personal; 
font-family:"Arial","sans-serif"; color:navy;}
 #wmMessageComp #wmMessage span.EmailStyle27   {mso-style-type:personal-reply; 
font-family:"Arial","sans-serif"; color:windowtext;}
 #wmMessageComp #wmMessage .MsoChpDefault   {mso-style-type:export-only;}
 #wmMessageComp #wmMessage @page Section1   {size:612.0pt 792.0pt; 
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
 #wmMessageComp #wmMessage div.Section1   {page:Section1;}

</STYLE>

<DIV class=Section1>
<div><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">
Hi Ray, I suppose you were mentioning me in your note earlier
:-)<o:p></o:p></SPAN></div>
<div><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 
'Arial','sans-serif'"><o:p>&nbsp;</o:p></SPAN></div>
<div><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">Hi 
Tim,<o:p></o:p></SPAN></div>
<div><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 
'Arial','sans-serif'"><o:p>&nbsp;</o:p></SPAN></div>
<div><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">
When we had the discussion within the subgroup I believe the point was
that all registries currently have that restriction.&nbsp; In fact including 
.COM.&nbsp; The current arrangement is as follows (taken from the current .COM 
contract):<o:p></o:p></SPAN></div>
<div><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 
'Arial','sans-serif'"><o:p>&nbsp;</o:p></SPAN></div>
<div><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">
Registration Restrictions.&nbsp; Registry Operator shall reserve, and
not register any TLD strings (i) appearing on the list of reserved TLD strings 
attached as Appendix 6 hereto or (ii) located at&nbsp; 
http://data.iana.org/TLD/tlds-alpha-by-domain.txt for initial (i.e., other than 
renewal) registration at the second level within the 
TLD.<o:p></o:p></SPAN></div>
<div><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 
'Arial','sans-serif'"><o:p>&nbsp;</o:p></SPAN></div>
<div><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">
What it meant is that domains that are already allocated will be allowed
to continue to renew, but if they are deleted they will be reserved 
thereupon.<o:p></o:p></SPAN></div>
<div><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 
'Arial','sans-serif'"><o:p>&nbsp;</o:p></SPAN></div>
<div><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">
The proposal was to maintain the "status quo" as mentioned and existing
in the contracts, and to allow the release of the names without requiring the 
change.<o:p></o:p></SPAN></div>
<div><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 
'Arial','sans-serif'"><o:p>&nbsp;</o:p></SPAN></div>
<div><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">
My suggestion is actually that registries should give consent to the
release of a name, for which consent must not be unreasonably withheld.&nbsp; 
That I think should be sufficient to address the anti-competitive issue, 
without having to make it overly cumbersome for anyone.&nbsp; By saying that it 
should not be unreasonably withheld, we eliminate the issue of good faith 
release, and stop the potential bad faith registrations (e.g. one used 
specifically to confuse others that they are the registry of the name... 
imagine say a TLD called ".headquarters" and someone puts up a website on 
"nic.jobs.headquarters" confusing people that they are the authority for .jobs 
and offering registrations.&nbsp; I think it will possibly disruptive to 
Ray).&nbsp; Notice on the other hand, is simply served to ICANN and archived 
and should not add to burden of ICANN nor become 
unmanageable.<o:p></o:p></SPAN></div>
<div><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 
'Arial','sans-serif'"><o:p>&nbsp;</o:p></SPAN></div>
<div><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">
The point I think I want to make is that, there is some merits and some
concerns about completely changing the status quo, and this is a solution we 
felt addresses the direction of the release of these names without excessive 
administrative process and in an equitable manner.<o:p></o:p></SPAN></div>
<div><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 
'Arial','sans-serif'"><o:p>&nbsp;</o:p></SPAN></div>
<div><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 
'Arial','sans-serif'">Edmon<o:p></o:p></SPAN></div>
<div><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 
'Arial','sans-serif'"><o:p>&nbsp;</o:p></SPAN></div>
<div><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 
'Arial','sans-serif'"><o:p>&nbsp;</o:p></SPAN></div>
<div><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">
PS. To preserve the new note sent in by Ray on this thread, I have
changed the subject for this simple note.<o:p></o:p></SPAN></div>
<div><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">PPS. 
Apologies for not being able to join the meeting today.<o:p></o:p></SPAN></div>
<div><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 
'Arial','sans-serif'"><o:p>&nbsp;</o:p></SPAN></div>
<div><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 
'Arial','sans-serif'"><o:p>&nbsp;</o:p></SPAN></div>
<DIV style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: medium 
none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: blue 1.5pt solid; 
PADDING-TOP: 0cm; BORDER-BOTTOM: medium none">
<DIV>
<DIV style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 
1pt solid; PADDING-LEFT: 0cm; PADDING-BOTTOM: 0cm; BORDER-LEFT: medium none; 
PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<div><B><SPAN lang=EN-US style="FONT-SIZE: 10pt; FONT-FAMILY: 
'Tahoma','sans-serif'">From:</SPAN></B><SPAN lang=EN-US style="FONT-SIZE: 10pt; 
FONT-FAMILY: 'Tahoma','sans-serif'">
 owner-gnso-rn-wg@xxxxxxxxx [mailto:owner-gnso-rn-wg@xxxxxxxxx]
<B>On Behalf Of </B>Tim Ruiz<BR><B>Sent:</B> Friday, May 04, 2007 1:04 
AM<BR><B>To:</B> Ray Fassett<BR><B>Cc:</B> 'Patrick Jones'; 
gnso-rn-wg@xxxxxxxxx<BR><B>Subject:</B> RE: [gnso-rn-wg] gTLD Reserved Names 
Chart<o:p></o:p></SPAN></div></DIV></DIV>
<div><o:p>&nbsp;</o:p></div>
<DIV>
<div>
Ray, that argument goes both ways. What is the rationale for maintaining
the status quo? In fact, there is no status quo. This requirement does not 
affect .com, larger than all other gTLDs combined. Evidence needs to be 
presented to justify this requirement. I don't believe there is 
any.<o:p></o:p></div></DIV>
<DIV>
<div>&nbsp;<o:p></o:p></div></DIV>
<DIV>
<div>
However, the fact that these registrations exist in .com and the history
we have to date regarding them IS evidence that there is no apparent adverse 
affect. And the fact that EmployMedia, NeuLevel, Afilias, Tralliance, and so on 
saw no problem applying for strings, and getting those strings approved, that 
were in current use at the second level for .com IS evidence as 
well.<o:p></o:p></div></DIV>
<DIV>
<div>&nbsp;<o:p></o:p></div></DIV>
<DIV>
<div>
Bottom line, the evidence that does exist supports removing the
requirement. There is no evidence that maintaining it and creating further 
burden on ICANN, prospective registrants, and subsequent gTLD applicants makes 
any kind of sense whatsoever.<o:p></o:p></div></DIV>
<DIV>
<div><BR><BR>Tim <o:p></o:p></div></DIV>
<DIV name="wmMessageComp">
<div><BR><BR><BR><o:p></o:p></div>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt">-------- Original Message 
--------<BR>Subject: RE: [gnso-rn-wg] gTLD Reserved Names Chart<BR>From: "Ray 
Fassett" &lt;ray@xxxxxxxxx&gt;<BR>Date: Thu, May 03, 2007 11:49 am<BR>To: 
"'Patrick Jones'" &lt;patrick.jones@xxxxxxxxx&gt;, 
&lt;gnso-rn-wg@xxxxxxxxx&gt;<o:p></o:p></P>
<DIV>
<DIV>
<div><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 
'Arial','sans-serif'">
Patrick, as you know, another member of our own 3 person sub-group has
opinioned just the opposite - and it&rsquo;s not me </SPAN><SPAN 
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Wingdings">J</SPAN><SPAN 
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">
 &nbsp; Opinions are great and welcome and important, but when there are
conflicting opinions &ndash; whether in or outside the sub-group (really does 
not matter) &ndash; evidence needs to be presented so that an objective 
conclusion can be reached.&nbsp; And, we have to appreciate that the status quo 
is a certain way right now (i.e. a managed list).&nbsp; So, if the opinion is 
to change the status quo, it (in my view) is going to have to require more than 
just opinion.&nbsp; It&rsquo;s a good point you are making and thank you for 
mentioning it.</SPAN><o:p></o:p></div></DIV>
<DIV>
<div><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 
'Arial','sans-serif'">&nbsp;</SPAN><o:p></o:p></div></DIV>
<DIV>
<div><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 
'Arial','sans-serif'">Ray</SPAN><o:p></o:p></div></DIV>
<DIV>
<div><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 
'Arial','sans-serif'">&nbsp;</SPAN><o:p></o:p></div></DIV>
<DIV>
<div><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 
'Arial','sans-serif'">&nbsp;</SPAN><o:p></o:p></div></DIV>
<DIV>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center>
<HR align=center width="100%" SIZE=2>
</DIV>
<DIV>
<div><B><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 
'Tahoma','sans-serif'">From:</SPAN></B><SPAN style="FONT-SIZE: 10pt; 
FONT-FAMILY: 'Tahoma','sans-serif'">
 owner-gnso-rn-wg@xxxxxxxxx [mailto:owner-gnso-rn-wg@xxxxxxxxx]
<B>On Behalf Of </B>Patrick Jones<BR><B>Sent:</B> Thursday, May 03, 2007 11:36 
AM<BR><B>To:</B> gnso-rn-wg@xxxxxxxxx<BR><B>Subject:</B> RE: [gnso-rn-wg] gTLD 
Reserved Names Chart</SPAN><o:p></o:p></div></DIV></DIV>
<DIV>
<div>&nbsp;<o:p></o:p></div></DIV>
<DIV>
<div><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 
'Arial','sans-serif'">
We should discuss this in the call today. I am still concerned that
leaving the requirement (to reserve gTLD strings at the second level) in its 
present form will become very difficult to manage as new gTLDs are added in the 
future. </SPAN><o:p></o:p></div></DIV>
<DIV>
<div><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 
'Arial','sans-serif'">&nbsp;</SPAN><o:p></o:p></div></DIV>
<DIV>
<div><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 
'Arial','sans-serif'">Patrick</SPAN><o:p></o:p></div></DIV>
<DIV>
<div><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 
'Arial','sans-serif'">&nbsp;</SPAN><o:p></o:p></div></DIV>
<DIV>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center>
<HR align=center width="100%" SIZE=2>
</DIV>
<DIV>
<div><B><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 
'Tahoma','sans-serif'">From:</SPAN></B><SPAN style="FONT-SIZE: 10pt; 
FONT-FAMILY: 'Tahoma','sans-serif'">
 owner-gnso-rn-wg@xxxxxxxxx [mailto:owner-gnso-rn-wg@xxxxxxxxx]
<B>On Behalf Of </B>Tim Ruiz<BR><B>Sent:</B> Thursday, May 03, 2007 8:29 
AM<BR><B>To:</B> Ray Fassett<BR><B>Cc:</B> 
gnso-rn-wg@xxxxxxxxx<BR><B>Subject:</B> RE: [gnso-rn-wg] gTLD Reserved Names 
Chart</SPAN><o:p></o:p></div></DIV></DIV>
<DIV>
<div>&nbsp;<o:p></o:p></div></DIV>
<DIV>
<DIV>
<div>
If this is going to be the recommendation, then I would like to add to
that the business names of then existing Accredited Registrars. And I am sure 
that the IP community would then like to add the well known names of other 
Internet services providers (search engines, ISPs, etc., 
etc.).<o:p></o:p></div></DIV></DIV>
<DIV>
<DIV>
<div>&nbsp;<o:p></o:p></div></DIV></DIV>
<DIV>
<DIV>
<div>
I cannot imagine a registry giving a competitor permission to register
the equivalent of its gTLD string at the second level. In fact, I think 
investigation of antitrust and other anti-competitive laws and regulations 
should be done before we consdier making such a 
recommendation.<o:p></o:p></div></DIV></DIV>
<DIV>
<DIV>
<div>&nbsp;<o:p></o:p></div></DIV></DIV>
<DIV>
<DIV>
<div>
What is&nbsp;the is actual evidence&nbsp;of potential harm to justify
this recommendation, or the existing policy regarding these reservations? What 
is the justification to continue to expand the existing imbalance regarding the 
registrations of such names? All this does is&nbsp;make an ever growing number 
of valuable and useful generic strings unavailable to the general public, and 
assumes bad intentions on the part of those who may like to use 
them.<o:p></o:p></div></DIV></DIV>
<DIV>
<DIV>
<div>&nbsp;<o:p></o:p></div></DIV></DIV>
<DIV>
<DIV>
<div><BR>Tim <o:p></o:p></div></DIV></DIV>
<DIV name="wmMessageComp">
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt; mso-margin-top-alt: 
auto"><o:p>&nbsp;</o:p></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt; mso-margin-top-alt: 
auto">-------- Original Message --------<BR>Subject: [gnso-rn-wg] gTLD Reserved 
Names Chart<BR>From: "Ray Fassett" &lt;ray@xxxxxxxxx&gt;<BR>Date: Wed, May 02, 
2007 7:47 pm<BR>To: &lt;gnso-rn-wg@xxxxxxxxx&gt;<o:p></o:p></P>
<DIV>
<DIV>
<DIV>
<div><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">
Attached find the gTLD Reserved Names Chart outlining the sub group
recommendation for discussion on Thursday.</SPAN><o:p></o:p></div></DIV></DIV>
<DIV>
<DIV>
<div><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 
'Arial','sans-serif'">&nbsp;</SPAN><o:p></o:p></div></DIV></DIV>
<DIV>
<DIV>
<div><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Ray 
Fassett</SPAN><o:p></o:p></div></DIV></DIV></DIV></DIV></DIV></DIV></DIV></DIV></BLOCKQUOTE></DIV>