<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im HOEnZb"><br>
</div>
</blockquote>
<div>Hi Wayne,</div>
<div><br>
</div>
<div>Considering we already do not indicate EV on Android, nor have we ever, I don't think this perceived loss of functionality is as significant as you may believe.</div>
<div><br>
</div>
<div>Further, considering the very real and distinct performance characteristics of mobile (radio warmups, RTTs, initcwnds), the idea of fetching OCSP, or, worse, CRLs - especially when some CAs have CRLs that are quite large (20+ MB) - in order to assure the
EV display is... non-ideal. So again, the EV indicator on mobile is not as strong or as present as it may be on desktop platforms.</div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>In that case, what does this statement mean?</div>
<div><br>
</div>
<div>
<p style="margin: 0px; font-size: 11px; font-family: Helvetica;">Chrome for mobile platforms will cease to show EV indicators for certificates that are not CT qualified according to the criteria below.</p>
<p style="margin: 0px; font-size: 11px; font-family: Helvetica;"><br>
</p>
<p style="margin: 0px; font-size: 11px; font-family: Helvetica;"><br>
</p>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im HOEnZb">-----Original Message-----<br>
From: therightkey [mailto:<a href="mailto:therightkey-bounces@ietf.org">therightkey-bounces@ietf.org</a>] On Behalf Of Ben<br>
Laurie<br>
Sent: Tuesday, February 04, 2014 10:08 AM<br>
To: CABFPub; <a href="mailto:certificate-transparency@googlegroups.com">certificate-transparency@googlegroups.com</a>;<br>
<a href="mailto:therightkey@ietf.org">therightkey@ietf.org</a><br>
</div>
<div class="im HOEnZb">Subject: [therightkey] Updated Certificate Transparency + Extended<br>
Validation plan<br>
<br>
</div>
<div class="HOEnZb">
<div class="h5">Enclosed, our revised plan.<br>
<br>
Comments welcome.<br>
<br>
</div>
</div>
<div class="HOEnZb">
<div class="h5">_______________________________________________<br>
Public mailing list<br>
<a href="mailto:Public@cabforum.org">Public@cabforum.org</a><br>
<a href="https://cabforum.org/mailman/listinfo/public" target="_blank">https://cabforum.org/mailman/listinfo/public</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>