<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: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="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<meta name=Generator content="Microsoft Word 12 (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>ICANN News Alert</title>
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
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","serif";}
h2
{mso-style-priority:9;
mso-style-link:"Heading 2 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:18.0pt;
font-family:"Times New Roman","serif";
font-weight:bold;}
h3
{mso-style-priority:9;
mso-style-link:"Heading 3 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:13.5pt;
font-family:"Times New Roman","serif";
font-weight:bold;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.Heading2Char
{mso-style-name:"Heading 2 Char";
mso-style-priority:9;
mso-style-link:"Heading 2";
font-family:"Cambria","serif";
color:#4F81BD;
font-weight:bold;}
span.Heading3Char
{mso-style-name:"Heading 3 Char";
mso-style-priority:9;
mso-style-link:"Heading 3";
font-family:"Cambria","serif";
color:#4F81BD;
font-weight:bold;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:109935653;
mso-list-template-ids:-860186298;}
@list l1
{mso-list-id:245648941;
mso-list-template-ids:-1313152416;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2
{mso-list-id:1674450355;
mso-list-template-ids:1369739468;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</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 bgcolor=white lang=EN-US link=blue vlink=purple>
<div class=WordSection1>
<div style='border:solid #CCCCCC 1.0pt;padding:6.0pt 6.0pt 6.0pt 6.0pt'>
<div>
<p class=MsoNormal><span style='font-family:"Arial","sans-serif"'><a
href="http://www.icann.org/"><span style='text-decoration:none'><img border=0
id="_x0000_i1025" src="http://www.icann.org/images/gradlogo_bow.jpg" alt=ICANN></span></a><o:p></o:p></span></p>
<h2><span style='font-family:"Arial","sans-serif"'>News Alert<o:p></o:p></span></h2>
<p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:6.0pt;
margin-left:0in'><span style='font-family:"Arial","sans-serif"'><a
href="http://www.icann.org/en/announcements/announcement-2-22oct10-en.htm">http://www.icann.org/en/announcements/announcement-2-22oct10-en.htm</a><o:p></o:p></span></p>
<div class=MsoNormal align=center style='margin-top:12.0pt;text-align:center'><span
style='font-family:"Arial","sans-serif"'>
<hr size=3 width="100%" align=center>
</span></div>
<h2 style='margin-bottom:0in;margin-bottom:.0001pt'><span style='font-family:
"Arial","sans-serif"'>Public Comment: Review of IDN ccTLD Fast Track Process<o:p></o:p></span></h2>
<p style='mso-margin-top-alt:9.0pt;margin-right:0in;margin-bottom:0in;
margin-left:0in;margin-bottom:.0001pt'><span style='font-family:"Arial","sans-serif"'>22
October 2010<o:p></o:p></span></p>
<p><span style='font-family:"Arial","sans-serif"'>We are nearing the one-year
anniversary date (16 November 2010) of the launch of the IDN ccTLD Fast Track
Process. The Final Implementation Plan for the Fast Track Process requires that
the process undergo review annually. ICANN is now opening a public comments forum
on the review of the process.<o:p></o:p></span></p>
<p><span style='font-family:"Arial","sans-serif"'>Commenters are asked to
suggest potential changes to improve the process for the end-users, including:
the respective IDN ccTLD managers, the governments as well as the users of the
resulting IDN ccTLDs (both registrants and general Internet users).<o:p></o:p></span></p>
<p><span style='font-family:"Arial","sans-serif"'>The public comment period is
open until 17 December 2010. There will also be a session scheduled in the
ICANN meeting in Cartagena, Colombia, to further discuss the performance and
potential improvement of the process, and to facilitate useful community
communication about the review.<o:p></o:p></span></p>
<p><span style='font-family:"Arial","sans-serif"'>Following the close of the
public comment period, Staff will produce a paper that contains analysis of the
received comments as well as recommendations (if any) for changes to the Final
Implementation Plan for the Fast Track Process. This paper will be publicly
posted and it will be provided to the ICANN Board. The ICANN Board will
consider next steps including, which of the proposed changes should be
implemented and if additional community discussion is required.<o:p></o:p></span></p>
<p><span style='font-family:"Arial","sans-serif"'>To help initiate the
discussion, Staff has produced the following information. It should be noted
that all aspects of the Fast Track Process are under review so any other subjects
can be raised and are welcomed.<o:p></o:p></span></p>
<p><span style='font-family:"Arial","sans-serif"'>As of the date of this
posting:<o:p></o:p></span></p>
<ul type=disc>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l1 level1 lfo1'><span style='font-family:"Arial","sans-serif"'>The
submission system has been up and running with no down time since launch.<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l1 level1 lfo1'><span style='font-family:"Arial","sans-serif"'>ICANN
has received a total of 33 requests, covering 22 languages.<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l1 level1 lfo1'><span style='font-family:"Arial","sans-serif"'>The
details of the strings that have passed the String evaluation step can be
viewed here: <a
href="http://www.icann.org/en/topics/idn/fast-track/string-evaluation-completion-en.htm">http://www.icann.org/en/topics/idn/fast-track/string-evaluation-completion-en.htm</a><o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l1 level1 lfo1'><span style='font-family:"Arial","sans-serif"'>The
IANA root zone database is authoritative for the TLDs that are in the root
zone today. Currently 15 IDN ccTLDs have been inserted in the DNS root
zone. <a href="http://www.iana.org/domains/root/db/">http://www.iana.org/domains/root/db/</a><o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l1 level1 lfo1'><span style='font-family:"Arial","sans-serif"'>Statistics
of where the various requests are in the process is available at the newly
opened Dashboard: <a href="https://charts.icann.org/public/">https://charts.icann.org/public/</a><o:p></o:p></span></li>
</ul>
<p><span style='font-family:"Arial","sans-serif"'>From a financial aspect, the
process was intended to cover its own costs by a recommended processing fee of
26.000USD per string requested. A total of $106.000 USD has been received to
date. It should be noted that the invoicing of Fast Track requests are done
towards the end of the processing, hence not all requests that have completed
the String Evaluation step has yet been invoiced.<o:p></o:p></span></p>
<p><span style='font-family:"Arial","sans-serif"'>To submit comments on the
Fast Track Process Review please email <a
href="mailto:fast-track-review-2010@icann.org">fast-track-review-2010@icann.org</a><o:p></o:p></span></p>
<p><span style='font-family:"Arial","sans-serif"'>To review received comments
on the Fast Track Process Review, please see <a
href="http://forum.icann.org/lists/fast-track-review-2010/">http://forum.icann.org/lists/fast-track-review-2010/</a><o:p></o:p></span></p>
<h3><span style='font-family:"Arial","sans-serif"'>Proposed discussion topics –
aspects of the developed IDN policy for the Fast Track:<o:p></o:p></span></h3>
<p><strong><span style='font-family:"Arial","sans-serif"'>Transparency:</span></strong><span
style='font-family:"Arial","sans-serif"'> The published policy document states
that requests are only published when they have successfully passed through the
String Evaluation portion of the process. Before then ICANN publishes only the
total number of received requests, the status the requests are in and the
corresponding number of languages. In this published material there is no
regarding the countries and territories requesting the TLD, nor any details of
the requests’ contents.<o:p></o:p></span></p>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>
<ol start=1 type=1>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo2'><span style='font-family:"Arial","sans-serif"'>This
is very useful from the perspective that in some cases the requester wishes
to keep the request confidential, and in other cases ICANN has received
requests that are not valid and do not fulfill the established
requirements. <o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo2'><span style='font-family:"Arial","sans-serif"'>To
a certain extent, the process is not completely open and transparent. A
lot of end-user inquiries have been received about which countries and
territories ICANN has received requests from, which we have not been able
to adequately respond to. Further, in comparison, the gTLD process will
publish received requests (minus selected confidential information) after
the administrative review that takes place immediately after the close of
an application round.<o:p></o:p></span></li>
</ol>
</blockquote>
<p><strong><span style='font-family:"Arial","sans-serif"'>Community Support:</span></strong><span
style='font-family:"Arial","sans-serif"'> The policy document requires
demonstration of Internet community support for the applied-for TLD string. The
notion of community support and the requirement for documenting such has been a
topic of discussion since the launch of the process. While examples and
descriptions of what this support could entail, the Final Implementation Plan
does not specify exactly the amount or detail of how one can demonstrate
community support. The policy reason behind this is that the approach is
different depending on geographic location, culture, and other developments in
the respective countries and territories. All such different approaches are valid
and appropriate to the Fast Track Process.<o:p></o:p></span></p>
<p><span style='font-family:"Arial","sans-serif"'>The following issues have
been raised, that may be appropriate for discussion in this review:<o:p></o:p></span></p>
<ul type=disc>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l2 level1 lfo3'><span style='font-family:"Arial","sans-serif"'>Some
do not agree with the need for community support documentation and do not
understand the difference between the type of support for the string (to
be established in the String Evaluation) and the type of the support for
the ccTLD manager (to be established in the Delegation evaluation).<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l2 level1 lfo3'><span style='font-family:"Arial","sans-serif"'>Some
do not find it necessary to demonstrate community support for the string nor
the manager. The reason being that such decisions can be made by
government entities, and the need for support undermines the authority of
the government in the country or territory.<o:p></o:p></span></li>
</ul>
<p><strong><span style='font-family:"Arial","sans-serif"'>Meaningfulness:</span></strong><span
style='font-family:"Arial","sans-serif"'> The strings requested through the
Fast Track Process must be demonstrated to be meaningful representations of the
corresponding country or territory name. If the strings requested do not
automatically fulfill this requirement through a published authoritative list,
the requester must include documentation from a linguistic expert that the
strings are in fact meaningful representations of the country or territory
name. Some requesters have stated that this requirement is not necessary in
cases where the strings requested are agreed to by the government and otherwise
seem obviously meaningful.<o:p></o:p></span></p>
<p><span style='font-family:"Arial","sans-serif"'>The issue has been raised
that in some cases, the strings requested do not fulfill the meaningfulness
automatically. Staff is looking especially for feedback as to whether
additional elements could result in automatically fulfilling this requirement,
and if so, which.<o:p></o:p></span></p>
<p><strong><span style='font-family:"Arial","sans-serif"'>Determination of the
IDN ccTLD Manager: </span></strong><span style='font-family:"Arial","sans-serif"'>This
is a topic related to the community support topic discussed above and is
primarily raised here for clarification purposes.<o:p></o:p></span></p>
<p><span style='font-family:"Arial","sans-serif"'>In many cases the IDN ccTLD
manager is the manager that submits the original IDN ccTLD request. However,
this is not a requirement. But it results in confusion in some cases because
the IDN ccTLD manager is not “evaluated” in the String Evaluation, but only
subsequently in the String Delegation.<o:p></o:p></span></p>
<p><span style='font-family:"Arial","sans-serif"'>Clarifications in the long
term will be beneficial on this subject (we are also trying to make this more
clearly in the information provided participants in the Fast Track Process).<o:p></o:p></span></p>
<p><strong><span style='font-family:"Arial","sans-serif"'>IDN tables:</span></strong><span
style='font-family:"Arial","sans-serif"'> Historically the content of IDN
Tables has not been evaluated and approved in any way or form by ICANN. This
includes the IDN tables provided in the Fast Track Process. Staff does review
the received tables in very limited capacity and only in relation to for
example potential/obvious errors and to what extend the tables fulfill the
requirements of the IDN Guidelines.<o:p></o:p></span></p>
<p><span style='font-family:"Arial","sans-serif"'>However there has been a
discussion in the community that requesters should simply send in or refer to
other IDN tables (that have already “passed through” the system) and in that
way their lack of a table will not delay the processing of the IDN ccTLD
request. Such behavior opens the discussion of whether there should be better
or other types of checks in place to review the received IDN tables.<o:p></o:p></span></p>
<p><span style='font-family:"Arial","sans-serif"'>The responsibility of serving
the community in the best possible way (and most secure way) by having measures
in place with these IDN tables, including sufficient variant identification and
registration rules, which is intended to avoid user confusion as much as
possible is a responsibility primarily of the TLD registry. The question is, as
we open up for more IDNs and IDNs generally at the top level, if additional
rules should be in place.<o:p></o:p></span></p>
<p><strong><span style='font-family:"Arial","sans-serif"'>Disputes</span></strong><span
style='font-family:"Arial","sans-serif"'>: No controversial strings have been
considered at this stage. As such, no disputes between requesters from
different territories and countries have been experienced. Disputes between
requesters from the same country or territory needing to deal with and decide
locally which requests proceeds seems to be working adequately at this stage.
The approach to date is that there needs to be agreement within a country or
territory before a fast Track request can be processed.<o:p></o:p></span></p>
<p><span style='font-family:"Arial","sans-serif"'>It might be useful to have a
discussion about what action, if any, ICANN should take in situation where one
part of a government or relevant public authority provides the necessary
support documentation for an IDN ccTLD request, but another part of the same
government or public authority states an opinion which could be considered
opposite. This situation could occur during String Evaluation, String Delegation
or post delegation<o:p></o:p></span></p>
<p><strong><span style='font-family:"Arial","sans-serif"'>Confusingly similar
string</span></strong><span style='font-family:"Arial","sans-serif"'>: Some
issues have arisen out of requested strings that are confusingly similar to
existing strings and/or other requested-strings. The confusability is
determined by the DNS Stability panel, which works well, although there is some
cases has been demonstrated different opinions on whether a string is
confusingly similar or not. Staff believes that the DNS Stability Panel working
guidelines are adequate as they supply a careful approach to what strings are
approved as TLDs, especially due to the limited nature of the Fast Track
Process. Nonetheless this has been raised as a topic of discussion.<o:p></o:p></span></p>
<p><strong><span style='font-family:"Arial","sans-serif"'>Objection/re-evaluation
rights:</span></strong><span style='font-family:"Arial","sans-serif"'> It has
been noted by the community that there are no re-evaluation or objection
mechanism for declined IDN ccTLD requests. The primary reason for this is that
the Fast Track Process is considered an interim process, short-termed for those
countries and territories where there is no controversy with implementing IDN
ccTLDs. As such if there are any disputes or issues coming up through the
evaluation, such should be referred to the coming long-term process for IDN
ccTLDs. The long-term process is currently in the policy developed phase in the
ccNSO. Question is if the Fast Track Process should be expanded to include such
options, or if it should stay in its limited capacity.<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width="100%"
style='width:100.0%'>
<tr>
<td style='background:#333333;padding:.6pt .6pt .6pt .6pt'>
<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width="100%"
style='width:100.0%;background:white'>
<tr>
<td width="100%" style='width:100.0%;padding:.05in .05in .05in .05in'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Verdana","sans-serif"'>This
message was sent from ICANN News Alert to inne@icann.org. It was sent from:
ICANN, 4676 Admiralty Way, Suite 330 , Marina del Rey, CA 90292-6601. You
can modify/update your subscription via the link below.</span><o:p></o:p></p>
</td>
<td width="2%" style='width:2.0%;padding:.05in .05in .05in .05in'>
<p align=center style='margin:0in;margin-bottom:.0001pt;text-align:center'><span
style='font-size:6.0pt;font-family:"Arial","sans-serif"'><a
href="http://www.icontact.com/a.pl/144186" target="_blank"><span
style='color:#999999;text-decoration:none'>Email Marketing by</span></a><br>
<a href="http://www.icontact.com/a.pl/144186" target="_blank"><span
style='text-decoration:none'><img border=0 width=117 height=38
id="_x0000_i1027" src="http://app.icontact.com/images/icontact_tryFree.gif"
alt="iContact - Try It Free!"></span></a><o:p></o:p></span></p>
</td>
</tr>
</table>
</td>
</tr>
</table>
<p class=MsoNormal><span style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0>
<tr>
<td style='background:white;padding:2.4pt 2.4pt 2.4pt 2.4pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Verdana","sans-serif"'><img
border=0 width=14 height=14 id="_x0000_i1028"
src="http://app.icontact.com/icp/static/images/icons/email_manage_subscription.png"><a
href="http://app.icontact.com/icp/mmail-mprofile.pl?r=9826907&l=6333&s=VMK0&m=328504&c=165637"><span
style='text-decoration:none'>Manage your subscription </span></a> </span><o:p></o:p></p>
</td>
</tr>
</table>
<p class=MsoNormal><span style='font-family:"Arial","sans-serif"'><img
border=0 width=1 height=1 id="_x0000_i1029"
src="http://click.icptrack.com/icp/track.php?msgid=328504&act=VMK0&r=9826907&c=165637"><o:p></o:p></span></p>
</div>
</body>
</html>