<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:m="http://schemas.microsoft.com/office/2004/12/omml" 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 14 (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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@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","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;}
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.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:1330714425;
mso-list-template-ids:573338052;}
@list l0: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 l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:2091080680;
mso-list-template-ids:765119574;}
@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 l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
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">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Query: The staff recommendations resulting from the Name Collision study have just been put out for public comment. It suggests that for the 80% of gTLD applications
deemed Low Risk that there be two sequential waiting periods, of 120 days plus 30 days, before domains at those new gTLDs go live. That delay period runs from the date of signing the registry agreement with ICANN.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">While not strictly a BC issue, since many on the list are either affiliated with or working with applicants, does that result in any significant additional
delay since after the date of agreement signing given that there is still a sunrise registration period, marketing efforts must be engaged in, etc. I’m just interested in appraising the real world impact in a broader context.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">For the 20% of applications deemed to be of Uncalculated Risk, the study recommends an additional study that will run 3-6 months.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Two applications -- .home and .corp – are deemed High Risk and would be put on indefinite hold.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Philip S. Corwin, Founding Principal</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Virtualaw LLC</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">1155 F Street, NW</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Suite 1050</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Washington, DC 20004</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">202-559-8597/Direct</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">202-559-8750/Fax</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">202-255-6172/cell</span></b><b><span style="color:navy"><o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Twitter: @VlawDC</span></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><b><i><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">"Luck is the residue of design" -- Branch Rickey</span></i></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> ICANN News Alert [mailto:communications@icann.org]
<br>
<b>Sent:</b> Tuesday, August 06, 2013 2:18 PM<br>
<b>To:</b> Phil Corwin<br>
<b>Subject:</b> ICANN News Alert -- Addressing the Consequences of Name Collisions<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:solid #CCCCCC 1.0pt;padding:8.0pt 8.0pt 8.0pt 8.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:7.5pt;margin-left:0in">
<span style="font-family:"Arial","sans-serif""><a href="http://www.icann.org/en/news/announcements/announcement-3-05aug13-en.htm">http://www.icann.org/en/news/announcements/announcement-3-05aug13-en.htm</a><o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="margin-top:15.0pt;text-align:center">
<span style="font-family:"Arial","sans-serif"">
<hr size="2" width="100%" align="center">
</span></div>
<h2 style="margin-bottom:0in;margin-bottom:.0001pt"><span style="font-family:"Arial","sans-serif"">Addressing the Consequences of Name Collisions<o:p></o:p></span></h2>
<p style="mso-margin-top-alt:11.25pt;margin-right:0in;margin-bottom:0in;margin-left:0in;margin-bottom:.0001pt">
<span style="font-family:"Arial","sans-serif"">5 August 2013<o:p></o:p></span></p>
<p><span style="font-family:"Arial","sans-serif"">As directed by the ICANN Board of Directors on 18 May 2013, ICANN commissioned and today releases the results of a study that considers the likelihood and impact of name space collisions between applied-for
new gTLD strings and non-delegated TLDs. Additionally, the study also reviewed the possibility of collisions arising from the use of X.509 digital certificates.<o:p></o:p></span></p>
<p><strong><span style="font-family:"Arial","sans-serif"">Background</span></strong><span style="font-family:"Arial","sans-serif"">: In a study published in January 2013, ICANN's Security and Stability Advisory Committee (SSAC) identified fact that some certificate
authorities issue X.509 certificates for domain names that are not resolvable in the public DNS. Such issues identified in SAC 057, as well as in SAC 045, are symptoms of entities that have local environments that include strong assumptions about the number
of top-level domains and/or have introduced local top-level domains in private namespaces that may conflict with names yet to be allocated. These private namespaces sometimes "leak" into the public DNS (either through misconfiguration or the use of old software),
meaning that requests for resources on private networks could end up querying the public-facing DNS Root Servers and hence "colliding" with the delegated new gTLD.<o:p></o:p></span></p>
<p><strong><span style="font-family:"Arial","sans-serif"">The Study</span></strong><span style="font-family:"Arial","sans-serif"">: On 18 May 2013, the ICANN Board approved a resolution calling for a detailed study of the name collision issue. ICANN contracted
with Interisle Consulting Group, LLC to collect and analyze the necessary data on all applied-for strings.<o:p></o:p></span></p>
<p><span style="font-family:"Arial","sans-serif"">The resulting study, <em><b><span style="font-family:"Arial","sans-serif""><a href="http://www.icann.org/en/about/staff/security/ssr/name-collision-02aug13-en.pdf">Name Collision in the DNS</a></span></b></em>
[PDF, 3.34 MB], identifies three categories of strings by the potential risk of name space collision:<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">
<strong><span style="font-family:"Arial","sans-serif"">Low Risk:</span></strong><span style="font-family:"Arial","sans-serif""> 80% of applied-for strings.<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">
<strong><span style="font-family:"Arial","sans-serif"">Uncalculated Risk:</span></strong><span style="font-family:"Arial","sans-serif""> 20% of applied-for strings.<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">
<strong><span style="font-family:"Arial","sans-serif"">High Risk:</span></strong><span style="font-family:"Arial","sans-serif""> 2 strings (.home, .corp).<o:p></o:p></span></li></ul>
<p><span style="font-family:"Arial","sans-serif"">To minimize the likelihood of any impact, ICANN proposes to the community several mitigation measures to be taken as described in an accompanying staff recommendation paper,
<em><b><span style="font-family:"Arial","sans-serif""><a href="http://www.icann.org/en/about/staff/security/ssr/new-gtld-collision-mitigation-05aug13-en.pdf">New gTLD Collision Risk Management</a></span></b></em> [PDF, 166 KB]. They include:<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:l0 level1 lfo2">
<span style="font-family:"Arial","sans-serif"">Proceeding with contracting and delegation of those strings categorized as
<strong><span style="font-family:"Arial","sans-serif"">"low risk" (80%)</span></strong> but recommending additional mitigation measures which should not materially impact their timeline for delegation.<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"">Conducting further study on those strings categorized as
<strong><span style="font-family:"Arial","sans-serif"">"uncalculated risk" (20%)</span></strong> anticipated to take 3-6 months to complete.<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"">Delaying contracting and delegation of the two
<strong><span style="font-family:"Arial","sans-serif"">"high risk"</span></strong> strings until mitigation efforts can place them in the "low risk" category.<o:p></o:p></span></li></ul>
<p><strong><span style="font-family:"Arial","sans-serif"">New gTLD Security and Stability:</span></strong><span style="font-family:"Arial","sans-serif""> Throughout the development of the New gTLD program, the security and stability of the Domain Name System
has remained the paramount concern of the ICANN community. ICANN staff has prepared an information sheet,
<em><b><span style="font-family:"Arial","sans-serif""><a href="http://www.icann.org/en/about/staff/security/ssr/intro-new-gtlds-05aug13-en.pdf">Secure and Stable Introduction of new gTLDs</a></span></b></em> [PDF, 102 KB], that describes the measures ICANN
has taken to ensure the introduction of new gTLDs will not jeopardize that commitment.<o:p></o:p></span></p>
<p><strong><span style="font-family:"Arial","sans-serif"">Public Comment</span></strong><span style="font-family:"Arial","sans-serif"">: At this time, the mitigation steps outlined in the staff recommendation paper are proposals only and community input is
strongly suggested. As a result, ICANN has opened a formal process for soliciting public comment. The form for submitting public comment and the calendar for doing so is
<a href="http://www.icann.org/en/news/public-comment/name-collision-05aug13-en.htm">
available here</a>.<o:p></o:p></span></p>
<p><strong><span style="font-family:"Arial","sans-serif"">Coordinated Vulnerability Disclosure Process</span></strong><span style="font-family:"Arial","sans-serif"">: ICANN takes this opportunity to inform the community that it has updated its risk management
procedures for improved reporting and response to any unforeseen issues arising from the delegation of new gTLDs. Members of the community are urged to familiarize themselves with the process available for review
<a href="http://www.icann.org/en/about/staff/security/vulnerability-disclosure-05aug13-en.pdf">
here</a> [PDF, 628 KB].<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%">
<tbody>
<tr>
<td width="100%" style="width:100.0%;background:white;padding:0in 0in 0in 0in">
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:3.75pt;margin-left:0in;line-height:15.0pt">
<span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#5E5E5E">This message was sent to
<a href="mailto:pcorwin@butera-andrews.com">pcorwin@butera-andrews.com</a> from:<o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:3.75pt;margin-left:0in;line-height:15.0pt">
<span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#5E5E5E">ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536<o:p></o:p></span></p>
</td>
<td width="2%" style="width:2.0%;background:white;padding:0in 0in 0in 0in">
<p style="line-height:9.75pt"><span style="font-size:7.0pt;font-family:"Arial","sans-serif";color:#5E5E5E">Email Marketing by
<a href="http://www.icontact.com/a.pl/144186" target="_blank"><span style="text-decoration:none"><img border="0" 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>
</tbody>
</table>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif";display:none"><o:p> </o:p></span></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td style="background:white;padding:0in 0in 0in 0in">
<p class="MsoNormal"><a href="http://app.icontact.com/icp/mmail-mprofile.pl?r=9829339&l=6333&s=7I8Y&m=917981&c=165637"><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#115880;text-decoration:none">Manage Your Subscription
</span></b></a><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><img border="0" width="1" height="1" id="_x0000_i1028" src="http://click.icptrack.com/icp/track.php?msgid=917981&act=7I8Y&r=9829339&c=165637"><o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-family:"Arial","sans-serif"">
<hr size="1" width="100%" noshade="" style="color:#A0A0A0" align="center">
</span></div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Arial","sans-serif"">No virus found in this message.<br>
Checked by AVG - <a href="http://www.avg.com">www.avg.com</a><br>
Version: 2013.0.3392 / Virus Database: 3209/6545 - Release Date: 08/02/13<o:p></o:p></span></p>
</div>
</body>
</html>