<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)">
<style><!--
/* Font Definitions */
@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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"Microsoft YaHei UI";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.HTMLChar
{mso-style-name:"HTML 预设格式 Char";
mso-style-priority:99;
mso-style-link:"HTML 预设格式";
font-family:Consolas;}
p.HTML, li.HTML, div.HTML
{mso-style-name:"HTML 预设格式";
mso-style-link:"HTML 预设格式 Char";
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.Char
{mso-style-name:"纯文本 Char";
mso-style-priority:99;
mso-style-link:纯文本;
font-family:Consolas;}
p.a, li.a, div.a
{mso-style-name:纯文本;
mso-style-link:"纯文本 Char";
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.Char0
{mso-style-name:"批注框文本 Char";
mso-style-priority:99;
mso-style-link:批注框文本;
font-family:"Microsoft YaHei UI";}
p.a0, li.a0, div.a0
{mso-style-name:批注框文本;
mso-style-link:"批注框文本 Char";
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle29
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle30
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle31
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle32
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
.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;}
--></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 class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Ben – a strong maybe.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">On the CGL coverage – probably never would cover a claim from a customer or the public for a bad cert. CGL insurance
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">covers things like bodily injury, personal injury,<span class="apple-converted-space"> </span>advertising injury<span class="apple-converted-space"> </span>and property damage – e.g.,
slip and fall in your office, employee’s torts (hitting other people), etc.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">On the Professional Liability/Errors & Omissions – it might cover unintentional negligence by a vetter during issuance of a bad cert, but remember the insurer’s first duty
and attempt will be to deny and defeat any claim from the public or a customer in order to protect the insured CA. First line of defense will be “no duty” to the claimant, second line of defense will be “no causation” – just because the cert was bad does
not mean there is any connection to your <alleged> harm as a customer or relying party. How do we know you saw the cert and relied on it? Were your own systems secure, or were you also negligent? Did you reasonably rely on the bad cert when you sent $50,000
for some bitcoins <allegedly> because you thought you were dealing with Mt. Gox and not a fraudster, etc. Usually the insurance policy coverage limits include defense costs which erode what is left to pay for claims, but an insurer often must defend the CA
in order to protect the remaining limits and protect the insured. Only if it appears the CA will lose at trial will the insurer consider paying money for the claim – so that is the (probably very rare) case where a member of the public or a customer will
get paid something from insurance.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Also – these policies usually don’t cover “contract liabilities” like a customer’s cost of buying a replacement cert if the CA’s certs are all bad and revoked (like Diginotar).
So I’m guessing all of Diginotar’s old customers could never have recovered the cost of buying and installing replacement certs from other CAs from Diginotar’s insurer.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Finally, any bad acts will generally destroy the insurance coverage as well – as in Diginotar.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">So any protection to customers and the public is illusory, for the most part, and the insurance requirements should be pruned from the EVGL. For those who say the insurance
requirements are good because they force a CA to spend some money and therefore have some “skin in the game” – we could just as well require proof of a charitable contribution of $25,000 per year if the goal is to make CAs spend some money. I would say the
cost of the CA infrastructure and programming, plus the cost of three annual WebTrust/ETSI audits, is sufficient to show seriousness and get some skin in the game. Plus the current rules are US-centric, and therefore are unfair.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">I really resented having to waste money on insurance when AffirmTrust was starting up, given that I knew the coverage had nothing to do with being a CA and would not protect
customers or the public.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><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""> Ben Wilson [mailto:ben@digicert.com]
<br>
<b>Sent:</b> Monday, May 05, 2014 10:45 AM<br>
<b>To:</b> 'Richard@WoSign'; Kirk Hall (RD-US); 'Adriano Santoni'; public@cabforum.org<br>
<b>Subject:</b> RE: [cabfpub] Denial of all insurance coverage for Diginotar<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">So, had Diginotar been more responsive on the breach, taking action early on, there would have been insurance coverage?<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>
<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""> public-bounces@cabforum.org [mailto:public-bounces@cabforum.org]
<b>On Behalf Of </b>Richard@WoSign<br>
<b>Sent:</b> Sunday, May 04, 2014 6:37 PM<br>
<b>To:</b> kirk_hall@trendmicro.com; Adriano Santoni; CABFPub (public@cabforum.org)<br>
<b>Subject:</b> Re: [cabfpub] Denial of all insurance coverage for Diginotar<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">Yes, when I consult my insurance broker the each type cert warranty amount, my insurance broker told me that the reparation never happen, so you can write any amount in your
website since it the lost really happen it should go to the court and the insurance company will have 100 reason to deny the claim.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D">Why WoSign endorse this ballot is NOT for reason that WoSign can’t afford it, we think it don’t bring any benefit to end user and waste the money.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Regards,<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Richard<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
<a href="mailto:public-bounces@cabforum.org">public-bounces@cabforum.org</a> [<a href="mailto:public-bounces@cabforum.org">mailto:public-bounces@cabforum.org</a>]
<b>On Behalf Of </b><a href="mailto:kirk_hall@trendmicro.com">kirk_hall@trendmicro.com</a><br>
<b>Sent:</b> Monday, May 5, 2014 12:49 AM<br>
<b>To:</b> Adriano Santoni; CABFPub (<a href="mailto:public@cabforum.org">public@cabforum.org</a>)<br>
<b>Subject:</b> Re: [cabfpub] Denial of all insurance coverage for Diginotar<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I don’t know. I do know that (in the US and Canada) all policies have “cooperation,” “duty to report incidents,” and “bad acts” clauses which are conditions
to providing any coverage. If the insured (Diginotar) fails to comply with those contractual provisions, it makes things harder for the insurer to handle any claims (and remember, the first duty of the insurer is to defend the insured and try to defeat the
claims, not to pay the claims… claims are only paid after litigation, etc., so the insurance is not there to help the public or injured customers).<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">Here, it’s my understanding that the insurer walked away, with the court’s approval, maybe because Diginotar failed to take action early on.<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>
<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""> Adriano Santoni [</span><a href="mailto:adriano.santoni@staff.aruba.it"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">mailto:adriano.santoni@staff.aruba.it</span></a><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">]
<br>
<b>Sent:</b> Saturday, May 03, 2014 11:34 PM<br>
<b>To:</b> Kirk Hall (RD-US); CABFPub (</span><a href="mailto:public@cabforum.org"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">public@cabforum.org</span></a><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">)<br>
<b>Subject:</b> R: [cabfpub] Denial of all insurance coverage for Diginotar<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">This automatic translation is rather difficult to understand, to me. Who was the Insurer in this case? <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:7.0pt;color:#575757">Inviato da Samsung Mobile.<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">-------- Messaggio originale --------<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Da: <a href="mailto:kirk_hall@trendmicro.com">kirk_hall@trendmicro.com</a>
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Data:03/05/2014 23:02 (GMT+01:00) <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">A: "CABFPub (<a href="mailto:public@cabforum.org">public@cabforum.org</a>)"
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Oggetto: [cabfpub] Denial of all insurance coverage for Diginotar
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoPlainText" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">
Jeremy, in response to your question below -- it was Bob Relyea who found the link during our last CABF meeting stating (in translation) that Diginotar’s insurer denied all coverage, so there was no possibility of any recovery for claims by the public or customers.
See link. That’s why it makes sense to delete the current coverage requirements.<o:p></o:p></p>
<p class="MsoPlainText" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">
<o:p></o:p></p>
<p class="MsoPlainText" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">
----- Forwarded Message -----<o:p></o:p></p>
<p class="MsoPlainText" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">
From: Bob Relyea <<a href="mailto:bob@relyea.com">bob@relyea.com</a>><o:p></o:p></p>
<p class="MsoPlainText" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">
To: Robert Relyea <<a href="mailto:rrelyea@redhat.com">rrelyea@redhat.com</a>><o:p></o:p></p>
<p class="MsoPlainText" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">
Sent: Wed, 19 Feb 2014 15:29:26 -0500 (EST)<o:p></o:p></p>
<p class="MsoPlainText" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">
Subject: Diginotar<o:p></o:p></p>
<p class="MsoPlainText" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">
<o:p></o:p></p>
<p class="MsoPlainText" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">
<a href="http://translate.google.com/translate?hl=en&sl=nl&u=http://webwereld.nl/beveiliging/77898-curator-diginotar-haalt-bakzeil-in-zaak-tegen-opta&prev=/search%3Fq%3Ddiginotar%2Bcurator%26biw%3D1280%26bih%3D775">http://translate.google.com/translate?hl=en&sl=nl&u=http://webwereld.nl/beveiliging/77898-curator-diginotar-haalt-bakzeil-in-zaak-tegen-opta&prev=/search%3Fq%3Ddiginotar%2Bcurator%26biw%3D1280%26bih%3D775</a><o:p></o:p></p>
<p class="MsoPlainText" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">
<o:p></o:p></p>
<p class="MsoPlainText" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">
<o:p></o:p></p>
<p class="MsoPlainText" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">
-----Original Message-----<br>
From: Jeremy Rowley [<a href="mailto:jeremy.rowley@digicert.com">mailto:jeremy.rowley@digicert.com</a>]
<br>
Sent: Friday, May 02, 2014 9:00 AM<br>
To: Kirk Hall (RD-US); 'Gervase Markham'; <a href="mailto:public@cabforum.org">public@cabforum.org</a><br>
Subject: RE: [cabfpub] Ballot 121 - EVGL Insurance Requirements<o:p></o:p></p>
<p class="MsoPlainText" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">
<o:p></o:p></p>
<p class="MsoPlainText" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">
Can you please send a link to the info about DigiNotar. This is the first I've heard that the insurance company didn't have to pay anything to damaged end users and would like to investigate further. My guess is that the claims were not being brought by the
right party. <o:p></o:p></p>
<p class="MsoPlainText" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">
<o:p></o:p></p>
<p class="MsoPlainText" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">
<o:p></o:p></p>
<p class="MsoPlainText" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">
<o:p></o:p></p>
</div>
<table class="MsoNormalTable" border="0" cellpadding="0">
<tbody>
<tr>
<td style="background:white;padding:.75pt .75pt .75pt .75pt">
<table class="MsoNormalTable" border="0" cellpadding="0">
<tbody>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<pre><span style="font-size:10.0pt;font-family:"Courier New"">TREND MICRO EMAIL NOTICE<o:p></o:p></span></pre>
<pre><span style="font-size:10.0pt;font-family:"Courier New"">The information contained in this email and any attachments is confidential<o:p></o:p></span></pre>
<pre><span style="font-size:10.0pt;font-family:"Courier New"">and may be subject to copyright or other intellectual property protection.<o:p></o:p></span></pre>
<pre><span style="font-size:10.0pt;font-family:"Courier New"">If you are not the intended recipient, you are not authorized to use or<o:p></o:p></span></pre>
<pre><span style="font-size:10.0pt;font-family:"Courier New"">disclose this information, and we request that you notify us by reply mail or<o:p></o:p></span></pre>
<pre><span style="font-size:10.0pt;font-family:"Courier New"">telephone and delete the original message from your mail system.<o:p></o:p></span></pre>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><o:p> </o:p></p>
<table class="MsoNormalTable" border="0" cellpadding="0">
<tbody>
<tr>
<td style="background:white;padding:.75pt .75pt .75pt .75pt">
<table class="MsoNormalTable" border="0" cellpadding="0">
<tbody>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<pre><span style="font-size:10.0pt;font-family:"Courier New""><o:p> </o:p></span></pre>
<pre><span style="font-size:10.0pt;font-family:"Courier New"">TREND MICRO EMAIL NOTICE<o:p></o:p></span></pre>
<pre><span style="font-size:10.0pt;font-family:"Courier New"">The information contained in this email and any attachments is confidential <o:p></o:p></span></pre>
<pre><span style="font-size:10.0pt;font-family:"Courier New"">and may be subject to copyright or other intellectual property protection. <o:p></o:p></span></pre>
<pre><span style="font-size:10.0pt;font-family:"Courier New"">If you are not the intended recipient, you are not authorized to use or <o:p></o:p></span></pre>
<pre><span style="font-size:10.0pt;font-family:"Courier New"">disclose this information, and we request that you notify us by reply mail or<o:p></o:p></span></pre>
<pre><span style="font-size:10.0pt;font-family:"Courier New"">telephone and delete the original message from your mail system.<o:p></o:p></span></pre>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>
<table><tr><td bgcolor=#ffffff><font color=#000000><pre><table class="TM_EMAIL_NOTICE"><tr><td><pre>
TREND MICRO EMAIL NOTICE
The information contained in this email and any attachments is confidential
and may be subject to copyright or other intellectual property protection.
If you are not the intended recipient, you are not authorized to use or
disclose this information, and we request that you notify us by reply mail or
telephone and delete the original message from your mail system.
</pre></td></tr></table></pre></font></td></tr></table>