<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: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]--><style><!--
/* Font Definitions */
@font-face
        {font-family:"MS Mincho";
        panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
        {font-family:Batang;
        panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
        {font-family:Batang;
        panose-1:2 3 6 0 0 1 1 1 1 1;}
@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:"\@Batang";
        panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
        {font-family:"MS UI Gothic";
        panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
        {font-family:"\@MS UI Gothic";
        panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
        {font-family:"\@MS Mincho";
        panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 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";}
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;}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        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.EmailStyle21
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle22
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;
        font-weight:normal;
        font-style:normal;}
.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";color:#1F497D'>Thomas,<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'>The paragraph you quoted:<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'>A CA may specify that an OCSP client can trust a responder for the<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>     lifetime of the responder's certificate.  The CA does so by<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>     including the extension id-pkix-ocsp-nocheck.  This SHOULD be a<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>     non-critical extension.  The value of the extension SHALL be NULL.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>     CAs issuing such a certificate should realize that a compromise of<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>     the responder's key is as serious as the compromise of a CA key<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>     used to sign CRLs, at least for the validity period of this<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>     certificate….<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'>does not *<b>require</b>* the CA to use id-pkix-ocsp-nocheck. It starts with “A CA *<b>may</b>* specify…” You don’t have to use it.<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'>-Rick<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 style='margin-left:.5in'><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"'> questions-bounces@cabforum.org [mailto:questions-bounces@cabforum.org] <b>On Behalf Of </b>Thomas Kopp<br><b>Sent:</b> Monday, October 27, 2014 8:12 AM<br><b>To:</b> </span><span style='font-size:10.0pt;font-family:"MS UI Gothic","sans-serif"'>王文正</span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>; public@cabforum.org; questions@cabforum.org<br><b>Subject:</b> Re: [cabfquest] Question concerning CAB Forum OCSP Requirments<o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Dear Wen-Cheng,<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>We have well understood the wording of the RFC. However, our goal is to completely avoid issuing responder certificates containing the id-pkix-ocsp-nocheck extension because even with a short life time of a responder certificate we consider such an approach as an unnecessary lowering of security. <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>In addition, I’m not sure whether you are aware what issuance of an OCSP responder certificates within hours means in practice. Such a rule seems a bit far away from reality because it requires key ceremonies charging a couple responsible people for several hours.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Finally, our question concerning the motivation behind the requirement has not been answered yet.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal style='mso-margin-top-alt:1.9pt;margin-right:14.05pt;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-autospace:none'><span lang=DE-LU style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Bescht Gréiss, meilleures salutations, mit freundlichen Grüßen, with best regards,<o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:1.9pt;margin-right:14.05pt;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-autospace:none'><b><span lang=DE-LU style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#C00000'><o:p> </o:p></span></b></p><p class=MsoNormal style='mso-margin-top-alt:1.9pt;margin-right:14.05pt;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-autospace:none'><b><span lang=EN-GB style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#C00000'>Thomas KOPP <o:p></o:p></span></b></p><p class=MsoNormal style='mso-margin-top-alt:1.9pt;margin-right:14.05pt;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-autospace:none'><span lang=EN-GB style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Head of Information Technologies</span><span lang=EN-GB style='font-size:11.0pt;font-family:"Arial","sans-serif";color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in;text-autospace:none'><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#C00000'>P:<span style='letter-spacing:-.65pt'> </span></span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#1F497D'>+352 26 68 15-574 - </span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#C00000'>M: </span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#1F497D'>+352<span style='letter-spacing:-.05pt'> </span>621 229 316 - </span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#C00000'>F:</span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#1F497D;letter-spacing:-.75pt'> </span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#1F497D'>+352 26 68 15-789 – </span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#C00000'>E:</span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#1F497D'> </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="mailto:thomas.kopp@luxtrust.lu"><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif"'>thomas.kopp@luxtrust.lu</span></a></span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in;text-autospace:none'><span lang=DE style='font-size:9.0pt;font-family:"Arial","sans-serif";color:#BFBFBF'><br></span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#A6A6A6'>LuxTrust S.A</span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#BFBFBF'>.</span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#C00000'> | </span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#BFBFBF'> </span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#A6A6A6'>IVY<span style='letter-spacing:.15pt'> </span>Building</span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:black'> </span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#C00000'>| </span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#A6A6A6'>13-15,<span style='letter-spacing:-.15pt'> </span><span style='letter-spacing:-.05pt'>P</span>a<span style='letter-spacing:-.25pt'>r</span>c<span style='letter-spacing:-.15pt'> </span>d’activités</span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#BFBFBF'> </span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#C00000'>|</span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:black'> </span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#A6A6A6'>L-8308<span style='letter-spacing:-.45pt'> </span>Capel<span style='letter-spacing:-.2pt'>l</span>en</span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#BFBFBF'> </span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#C00000'>|</span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:black'> </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="http://www.luxtrust.lu/"><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#A6A6A6;text-decoration:none'>ww<span style='letter-spacing:-.4pt'>w</span>.luxtru<span style='letter-spacing:-.05pt'>s</span>t.lu</span></a></span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#A6A6A6'><o:p></o:p></span></p><div style='border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal style='margin-left:.5in;text-autospace:none'><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:black'><o:p> </o:p></span></p></div><p class=MsoNormal style='margin-left:.5in'><span lang=DE style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#A6A6A6'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span lang=EN-GB style='font-size:6.0pt;font-family:"Arial","sans-serif";color:#A6A6A6;mso-fareast-language:LB-LU'>The information in this e-mail and any attachment is confidential and for use by the addressee only. Access to this e-mail by anyone else is not authorized. If you are not the intended recipient, please inform the sender and erase all copies of it from your system. Internet communications are by default not secure. LuxTrust S.A. cannot guarantee the integrity and origin of e-mails unless they have been properly digitally signed. Confidentiality of e-mails can only be guaranteed if they are encrypted properly using a secure digital certificate.LuxTrust S.A. takes precautions to ensure that e-mails are scanned for viruses but cannot accept liability for any damage sustained as a result of software viruses.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><a href="https://www.luxtrust.lu/"><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;text-decoration:none'><img border=0 width=414 height=126 id="_x0000_i1025" src="cid:image001.jpg@01CFF1EC.FC0E3880" alt="Email_banner_CSS_like"></span></a><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p></div><p class=MsoNormal style='margin-left:.5in'><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 style='margin-left:.5in'><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"'> </span><span style='font-size:10.0pt;font-family:"MS UI Gothic","sans-serif"'>王文正</span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> [<a href="mailto:wcwang@cht.com.tw">mailto:wcwang@cht.com.tw</a>] <br><b>Sent:</b> Méindeg 27 Oktober 2014 15:49<br><b>To:</b> Thomas Kopp; <a href="mailto:public@cabforum.org">public@cabforum.org</a>; <a href="mailto:questions@cabforum.org">questions@cabforum.org</a><br><b>Subject:</b> Re: [cabfquest] Question concerning CAB Forum OCSP Requirments<o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><div><p class=MsoNormal style='margin-left:.5in'>Thomas,<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>The CAB forum does not impose any high risk on trust service providers or relying parties. You misquote the text, please read the full paragraph in the RFC.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>The intention of the text you highlighted in yellow color is to  remind CAs that it is dangrous if the lifetime of a 'nocheck' OCSP responder's certificate is too long. That is why the subsequent  text says "CAs may choose to issue this type of certificate with a very short lifetime and renew it frequently."<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>The RFC is intent to tell CAs that it will be safe if they keep the lifetime of a 'nocheck' OCSP responder's certificate very short. In a typical implemention, the lifetime might range from several hours to several days.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>Wen-Cheng Wang<o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'><br><br><br>-------- <span style='font-family:"MS Mincho"'>原始郵件</span> --------<br><span style='font-family:"MS Mincho"'>自:</span> Thomas Kopp <<a href="mailto:thomas.kopp@luxtrust.lu">thomas.kopp@luxtrust.lu</a>> <br><span style='font-family:"MS Mincho"'>日期:</span> <br><span style='font-family:"MS Mincho"'>至:</span> <a href="mailto:public@cabforum.org,questions@cabforum.org">public@cabforum.org,questions@cabforum.org</a> <br><span style='font-family:"MS Mincho"'>主旨:</span> [cabfquest] Question concerning CAB Forum OCSP Requirments <o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'>Dear all,<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'>Can you please clarify the subsequent point?<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'>In the CAB baseline requirements <a href="https://cabforum.org/wp-content/uploads/Baseline_Requirements_V1_1_9.pdf" target="_BLANK">https://cabforum.org/wp-content/uploads/Baseline_Requirements_V1_1_9.pdf</a> section 13.2.5 imposes the id-pkix-ocsp-nocheck extension in the case of an authorized responder scenario.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'>By contrast, RFC 2560 and the successor RFC 6960 stipulate (cf. section 4.2.2.2.1):<o:p></o:p></p><pre style='margin-left:.5in'>A CA may specify that an OCSP client can trust a responder for the<o:p></o:p></pre><pre style='margin-left:.5in'>     lifetime of the responder's certificate.  The CA does so by<o:p></o:p></pre><pre style='margin-left:.5in'>     including the extension id-pkix-ocsp-nocheck.  This SHOULD be a<o:p></o:p></pre><pre style='margin-left:.5in'>     non-critical extension.  The value of the extension SHALL be NULL.<o:p></o:p></pre><pre style='margin-left:.5in'>     <span style='background:yellow'>CAs issuing such a certificate should realize that a compromise of</span><o:p></o:p></pre><pre style='margin-left:.5in'><span style='background:yellow'>     the responder's key is as serious as the compromise of a CA key</span><o:p></o:p></pre><pre style='margin-left:.5in'><span style='background:yellow'>     used to sign CRLs, at least for the validity period of this</span><o:p></o:p></pre><pre style='margin-left:.5in'><span style='background:yellow'>     certificate</span>….<o:p></o:p></pre><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'>How can CAB Forum impose such a requirement, which imposes to trust service providers such a high security risk?<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'>Please provide us a reasonable explanation for this particular requirement. Please note that we would not want to hear any technical reasoning like possible “self-looping” during OCSP responder certificate status checking, because such issues can perfectly be addressed without having to lower security.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;margin-right:14.05pt;margin-left:.5in;text-autospace:none'><span lang=DE-LU style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Bescht Gréiss, meilleures salutations, mit freundlichen Grüßen, with best regards,</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;margin-right:14.05pt;margin-left:.5in;text-autospace:none'><b><span lang=DE-LU style='font-family:"Arial","sans-serif";color:#C00000'> </span></b><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;margin-right:14.05pt;margin-left:.5in;text-autospace:none'><b><span lang=EN-GB style='font-family:"Arial","sans-serif";color:#C00000'>Thomas KOPP </span></b><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;margin-right:14.05pt;margin-left:.5in;text-autospace:none'><span lang=EN-GB style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Head of Information Technologies</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in;text-autospace:none'><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#C00000'>P:<span style='letter-spacing:-.65pt'> </span></span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif"'>+352 26 68 15-574 - <span style='color:#C00000'>M: </span>+352<span style='letter-spacing:-.05pt'> </span>621 229 316 - <span style='color:#C00000'>F:</span><span style='letter-spacing:-.75pt'> </span>+352 26 68 15-789 – <span style='color:#C00000'>E:</span> </span><a href="mailto:thomas.kopp@luxtrust.lu"><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif"'>thomas.kopp@luxtrust.lu</span></a><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in;text-autospace:none'><span lang=DE style='font-size:9.0pt;font-family:"Arial","sans-serif";color:#BFBFBF'><br></span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#A6A6A6'>LuxTrust S.A</span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#BFBFBF'>.</span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#C00000'> | </span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#BFBFBF'> </span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#A6A6A6'>IVY<span style='letter-spacing:.15pt'> </span>Building</span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:black'> </span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#C00000'>| </span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#A6A6A6'>13-15,<span style='letter-spacing:-.15pt'> </span><span style='letter-spacing:-.05pt'>P</span>a<span style='letter-spacing:-.25pt'>r</span>c<span style='letter-spacing:-.15pt'> </span>d’activités</span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#BFBFBF'> </span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#C00000'>|</span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:black'> </span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#A6A6A6'>L-8308<span style='letter-spacing:-.45pt'> </span>Capel<span style='letter-spacing:-.2pt'>l</span>en</span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#BFBFBF'> </span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#C00000'>|</span><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:black'> </span><a href="http://www.luxtrust.lu/" target="_BLANK"><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#A6A6A6;text-decoration:none'>ww<span style='letter-spacing:-.4pt'>w</span>.luxtru<span style='letter-spacing:-.05pt'>s</span>t.lu</span></a><o:p></o:p></p><div style='border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in;text-autospace:none'><span lang=DE style='font-size:8.0pt;font-family:"Arial","sans-serif";color:black'> </span><o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'><span lang=DE style='color:#A6A6A6'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'><span lang=EN-GB style='font-size:6.0pt;font-family:"Arial","sans-serif";color:#A6A6A6'>The information in this e-mail and any attachment is confidential and for use by the addressee only. Access to this e-mail by anyone else is not authorized. If you are not the intended recipient, please inform the sender and erase all copies of it from your system. Internet communications are by default not secure. LuxTrust S.A. cannot guarantee the integrity and origin of e-mails unless they have been properly digitally signed. Confidentiality of e-mails can only be guaranteed if they are encrypted properly using a secure digital certificate.LuxTrust S.A. takes precautions to ensure that e-mails are scanned for viruses but cannot accept liability for any damage sustained as a result of software viruses.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'><a href="https://www.luxtrust.lu/" target="_BLANK"><span style='color:windowtext;text-decoration:none'><img border=0 width=414 height=126 id="Picture_x0020_2" src="cid:image001.jpg@01CFF1EC.FC0E3880" alt="Email_banner_CSS_like"></span></a><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'> <o:p></o:p></p></div><p class=MsoNormal style='margin-left:.5in'><b><br><br></b><b><span style='font-size:10.0pt;font-family:"MS Mincho"'>本信件可能包含中華電信股份有限公司機密資訊</span></b><b><span style='font-size:10.0pt'>,</span></b><b><span style='font-size:10.0pt;font-family:"MS Mincho"'>非指定之收件者</span></b><b><span style='font-size:10.0pt'>,</span></b><b><span style='font-size:10.0pt;font-family:"MS Mincho"'>請勿蒐集、處理或利用本信件</span></b><b><span style='font-size:10.0pt;font-family:"Batang","serif"'>內容</span></b><b><span style='font-size:10.0pt'>,</span></b><b><span style='font-size:10.0pt;font-family:"MS Mincho"'>並請銷毀此信件</span></b><b><span style='font-size:10.0pt'>. </span></b><b><span style='font-size:10.0pt;font-family:"MS Mincho"'>如為指定收件者</span></b><b><span style='font-size:10.0pt'>,</span></b><b><span style='font-size:10.0pt;font-family:"MS Mincho"'>應確實保護郵件中本公司之營業機密及個人資料</span></b><b><span style='font-size:10.0pt'>,</span></b><b><span style='font-size:10.0pt;font-family:"MS Mincho"'>不得任意傳佈或揭露</span></b><b><span style='font-size:10.0pt'>,</span></b><b><span style='font-size:10.0pt;font-family:"MS Mincho"'>並應自行確認本郵件之附檔與超連結之安全性</span></b><b><span style='font-size:10.0pt'>,</span></b><b><span style='font-size:10.0pt;font-family:"MS Mincho"'>以共同善盡資訊安全與個資保護責任</span></b><b><span style='font-size:10.0pt'>. <br>Please be advised that this email message (including any attachments) contains confidential information and may be legally privileged. If you are not the intended recipient, please destroy this message and all attachments from your system and do not further collect, process, or use them. Chunghwa Telecom and all its subsidiaries and associated companies shall not be liable for the improper or incomplete transmission of the information contained in this email nor for any delay in its receipt or damage to your system. If you are the intended recipient, please protect the confidential and/or personal information contained in this email with due care. Any unauthorized use, disclosure or distribution of this message in whole or in part is strictly prohibited. Also, please self-inspect attachments and hyperlinks contained in this email to ensure the information security and to protect personal information.</span></b> <o:p></o:p></p></div></body></html>