<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;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 8, 2017, at 12:24 PM, Ryan Sleevi via Public <<a href="mailto:public@cabforum.org" class="">public@cabforum.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div dir="ltr" class=""><div style="font-size:12.8px" class=""><span style="font-size: 12.8px;" class="">We've seen analysis about what is the 'floor' for the ecosystem to affect change ( </span><a href="https://cabforum.org/pipermail/public/2017-February/009483.html" class="" style="font-size: 12.8px;">https://cabforum.org/pipermail/public/2017-February/009483.html</a><span style="font-size: 12.8px;" class=""> ), but luckily, this ballot focuses on new certificates. By targeting 1 May 2017, any potential impact on subscribers does not manifest until June 2018. </span></div></div></div></blockquote><br class=""></div><div>How this this follow? A customer who has a certificate expiring May 2, 2017 can currently get a 39 month certificate. However with this ballot they will have to get 13 month certificate. The impact seems to be much sooner than you state.</div><div><br class=""></div><div>Thanks,</div><div>Peter</div></body></html>