<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:oa="urn:schemas-microsoft-com:office:activation" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 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]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Thanks Chuck, I have three comments on
this. First, I think re 1 and 2 character names, that we also should
consult GAC regarding 2 character ASCII TLDs as I have suggested in prior email
and I believe is supported by Bruce and others.<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=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Second, re “other reserved names at
the second level” (aka ‘premium names’ and the like), if this
is outside the scope of the RN-WG then that is fine, but we need to add it to
the newTLD TF to consider what to require of applicants in this regard. I
doubt that anyone wants to allow new TLD registries to reserve whatever names
they choose for however long they like on whatever basis, which is the current
reality at .travel. There needs to be transparency in the application and
pre-launch phases to address this issue.<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=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Third, I object to re-launching this WG
with the objective to ‘maintain the status quo for now’ re
ICANN/IANA related names. I believe Staff was looking into any reasoning
behind these historical reservations, other than the obvious reason to avoid
user confusion were ‘someone else’ to register something like
iab.web (for example the Interactive Advertising Bureau…). We
should see whether Staff or anyone else comes up with any other reasoning.
Assuming not, then it would make no sense to continue these reservations
on the basis of user confusion. <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=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Indeed that would be entirely self serving
and appalling to many in the community who have to fight and pay for their
defensive registrations with each new TLD launch, or otherwise fight
cybersquatters who register domain names that correspond to brands. ICANN
should experience that as well, in hopes that better policy may be made for us
all, rather than protecting itself via the Reserved Names list when such
protection is not available to those with a far greater need for it. So I
recommend we change this objective to ‘explore basis for current
reservation, and decide whether to continue it.’<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>
<div>
<p class=MsoPlainText><font size=2 color=black face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:black'>Mike Rodenbaugh<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=2 color=black face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:black'>Sr. Legal Director<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=2 color=black face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:black'>Yahoo! Inc.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=navy face="Times New Roman"><span
style='font-size:12.0pt;color:navy'> <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=black face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:black'>NOTICE: This communication is
confidential and may be protected by attorney-client and/or work product
privilege. If you are not the intended recipient, please notify me by
reply, and delete this communication and any attachments.</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-council@gnso.icann.org [mailto:owner-council@gnso.icann.org] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Gomes, Chuck<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, April 05, 2007
5:43 AM<br>
<b><span style='font-weight:bold'>To:</span></b> GNSO Council; Bruce Tonkin<br>
<b><span style='font-weight:bold'>Subject:</span></b> [council] RN-WG SoW<br>
<b><span style='font-weight:bold'>Importance:</span></b> High</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 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Attached is a fairly detailed SoW for a 30-day extension of
the RN-WG. The current plan would be to restart the group on Wednesday,
11 April and end it on Thursday, 10 May. This should allow enough time
for inclusion of the final recommendations into the final New gTLD Report.</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 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>As we discussed on Thursday afternoon in <st1:place w:st="on"><st1:City
w:st="on">Lisbon</st1:City></st1:place>, we need to take action on this via
email before our next teleconference meeting on 12 April, and I need to
communicate the meeting schedule to the working group the end of this week.
Therefore, I would like to propose the following motion:</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 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>"Per the terms of the original Reserved Name
Working Group (RN-WG) Statement of Work approved by the Council, the RN-WG is
extended for an additional 30 days starting on 11 April 2007 and ending on 10
May 2007 with the tasks defined in the attached Statement of Work and with
the requirement to deliver a final report not later than 10 May 2007."</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=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma'>Chuck Gomes</span></font><o:p></o:p></p>
<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 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma'>"This message is intended for the use of the individual
or entity to which it is addressed, and may contain information that is
privileged, confidential and exempt from disclosure under applicable law. Any
unauthorized use, distribution, or disclosure is strictly prohibited. If you
have received this message in error, please notify sender immediately and
destroy/delete the original transmission." </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>
</div>
</body>
</html>