<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=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Cambria-BoldItalic;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Cambria-Bold;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:TimesNewRomanPSMT;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{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:1140655694;
mso-list-type:hybrid;
mso-list-template-ids:-137096814 -2105488148 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1
{mso-list-id:1509445865;
mso-list-type:hybrid;
mso-list-template-ids:288939468 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
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 lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Hi Tom,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>GlobalSign cannot support this draft ballot as written.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo1'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>1)<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>The location of these new requirements (under validity period) are mis-placed and incomplete. This should be a new section (9.8?) where the subject can be addressed clearly and any exceptions to the policy clearly listed. This section should describes the deprecation of SHA-1 and list all the locations where SHA-1 can or cannot be used:<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l1 level2 lfo1'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>a.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>SHA-1 MUST NOT be used as the certificate, CRL(?) and OCSP(?) signature hash algorithm<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l1 level2 lfo1'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>b.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>This section should also clearly call out other places where SHA-1 is used today and where it may continue to be used (OCSP responses, CRLs, SKI, Auth Key ID, etc)<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l1 level2 lfo1'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>c.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>This section must call out dates when SHA-1 must be depreciated for OCSP, CRLs and the other uses not covered by a) above.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo1'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>2)<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>The 1 November date (8 weeks) is too soon for this change as stated<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l1 level2 lfo1'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>a.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>CAs have taken different approaches to meeting the 1 January 2017 date based on the MS Root policy. Not all CAs are in a position to change agreements with their customers and limit SHA-1 certificate issuance to 1-year by 1 January 2015 (or to 2-years by 1 November 2014, then change again starting in 2015)<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l1 level2 lfo1'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>b.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>CAs have customers with Subordinate CAs signed by their roots with SHA-1 signatures and are actively issuing SHA-1 SSL certificates. While I’m sure many have been transitioned to SHA-256 subordinate CAs, not all have been migrated yet and that will take a while to implement. The MS Root policy allows them to use these CAs for 2 more years, but a BR mandates a system wide change on the effective date. This can’t be supported in a matter of weeks.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo1'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>3)<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>If the list of 5 “Exceptions” listed as a) – e) is meant to apply to both long validity period certificates and those with SHA-1, then they need to be refined and updated specifically for SHA-1 or this change will be ineffective (too many loopholes).<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I suggest the following approach:<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>Move this to a new section: 9.8<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>More clearly stating where this change is mandated (and where it is not)<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>Create a new well defined set of exceptions for the use of SHA-1<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>Clearly identify the dates and changes needed for Subordinate CAs and what is permitted and what is not<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>Define the dates (perhaps different dates) for the conversion from SHA-1 to SHA-2 for CRLs, OCSP services and any/all other uses of SHA-1 that are being contemplated<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>Change the Effective Date from 1 November 2014 to “3 months from the approval of the ballot”<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>Allow certificates issued prior to the effective date to be re-issued as SHA-1 certificates<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Regards,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><br>Doug<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"><span style='color:#1F497D'><o:p> </o:p></span></a></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> public-bounces@cabforum.org [mailto:public-bounces@cabforum.org] <b>On Behalf Of </b>Tom Albertson<br><b>Sent:</b> Friday, September 5, 2014 6:47 PM<br><b>To:</b> public@cabforum.org<br><b>Subject:</b> [cabfpub] FW: Ballot - expiration of SHA1 certificates<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi there,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have produced a ballot for discussion, which aligns the Baseline Requirements (v1.1.9) with the planned deprecation of SHA-1. This ballot uses the dates in the <a href="http://blogs.technet.com/b/pki/archive/2013/11/12/sha1-deprecation-policy.aspx">Microsoft SHA-1 deprecation policy</a> as a reference, and right now only addresses SSL certs. I think we can offer similar language for code signing certs and possibly other BRs once we have hashed this out for SSL.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>New text appears as <u><span style='color:red'>red underlined</span></u>. A small amount of text in Appendix A is proposed for deletion (<s>black strikethrough)</s> The amendments relate mainly to Section 9.4 Validity Period, with minor conforming changes to Appendix A.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Special thanks to Ben and Gerv and others, who already struggled through this issue in March 2014, that ballot discussion was most instructive. I have made no efforts to collaborate with other Forum members on this issue except to go back and forth with Kelvin and Aaron here at Microsoft on the best text to offer to represent the Microsoft policy. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Your comments and questions are appreciated, and ultimately we could use an endorser or two of the ballot measure. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks,<o:p></o:p></p><p class=MsoNormal>Tom<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b><span style='color:#1F497D'>Ballot NNN –expirations of SHA1 certificates (FINAL VERSION)<o:p></o:p></span></b></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='text-autospace:none'><b><i><span style='font-size:14.0pt;font-family:"Cambria-BoldItalic","serif"'>9.4 Validity Period<o:p></o:p></span></i></b></p><p class=MsoNormal style='text-autospace:none'><b><span style='font-size:13.0pt;font-family:"Cambria-Bold","serif"'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span style='font-size:13.0pt;font-family:"Cambria-Bold","serif"'>9.4.1 Subscriber Certificates<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Times New Roman","serif"'>Subscriber Certificates issued after the Effective Date MUST have a Validity Period no greater than 60 months.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Times New Roman","serif"'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Times New Roman","serif"'>Except as provided for below, Subscriber Certificates issued after 1 April 2015 MUST have a Validity Period no<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Times New Roman","serif"'>greater than 39 months.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Times New Roman","serif"'> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><u><span style='font-family:"Times New Roman","serif";color:red'>Effective 1 November 2014, CAs MUST NOT issue Subscriber Certificates utilizing the SHA-1 algorithm with an Expiry Date greater than 1 January 2017.</span></u><u><span style='font-family:"Times New Roman","serif";color:#00B050'> </span></u><u><span style='font-family:"Times New Roman","serif";color:#1F497D'><o:p></o:p></span></u></p><p class=MsoNormal style='text-autospace:none'><u><span style='font-family:"Times New Roman","serif";color:red'><o:p><span style='text-decoration:none'> </span></o:p></span></u></p><p class=MsoNormal style='text-autospace:none'><u><span style='font-family:"Times New Roman","serif";color:red'>Except as provided for below, effective 1 January 2016, CAs MUST NOT issue Subscriber Certificates that utilize the SHA-1 algorithm.</span></u><u><span style='font-family:"Times New Roman","serif";color:#00B050'> <o:p></o:p></span></u></p><p class=MsoNormal style='text-autospace:none'><u><span style='font-family:"Times New Roman","serif"'> <o:p></o:p></span></u></p><p class=MsoNormal style='text-autospace:none'><u><span style='font-family:"Times New Roman","serif";color:red'>Effective</span></u><span style='font-family:"Times New Roman","serif";color:red'> </span><span style='font-family:"Times New Roman","serif"'>1 April 2015, CAs MAY continue to issue Subscriber Certificates with a Validity Period greater than 39<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Times New Roman","serif"'>months but not greater than 60 months provided that the CA documents that the Certificate is for a system or<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Times New Roman","serif"'>software that:<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Times New Roman","serif"'>(a) was in use prior to the Effective Date;<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Times New Roman","serif"'>(b) is currently in use by either the Applicant or a substantial number of Relying Parties;<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Times New Roman","serif"'>(c) fails to operate if the Validity Period is shorter than 60 months;<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Times New Roman","serif"'>(d) does not contain known security risks to Relying Parties; and<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>(e) is difficult to patch or replace without substantial economic outlay.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Times New Roman","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Times New Roman","serif"'><o:p> </o:p></span></p><p class=MsoNormal><b><u><span style='font-family:"Times New Roman","serif";color:red'>9.4.2 Root CA Certificates<o:p></o:p></span></u></b></p><p class=MsoNormal><u><span style='font-family:"Times New Roman","serif";color:red'><o:p><span style='text-decoration:none'> </span></o:p></span></u></p><p class=MsoNormal><u><span style='color:red'>The SHA-1 deprecation policy and Validity Dates DO NOT apply to Root CA certificates. CAs MAY continue to use their existing SHA-1 Root Certificates. </span></u><u><span lang=EN style='color:red'>CAs MUST use SHA-2 or successor hash algorithms to sign any Subscriber certificates, Subordinate CA certificates, and CRLs effective 1 January 2016.</span><span style='color:red'><o:p></o:p></span></u></p><p class=MsoNormal><u><span style='font-family:"Times New Roman","serif";color:red'><o:p><span style='text-decoration:none'> </span></o:p></span></u></p><p class=MsoNormal><u><span style='font-family:"Times New Roman","serif";color:red'><o:p><span style='text-decoration:none'> </span></o:p></span></u></p><p class=MsoNormal><b><u><span style='font-family:"Times New Roman","serif";color:red'>9.4.3 Subordinate CA Certificates<o:p></o:p></span></u></b></p><p class=MsoNormal><u><span style='font-family:"Times New Roman","serif";color:red'><o:p><span style='text-decoration:none'> </span></o:p></span></u></p><p class=MsoNormal><u><span style='font-family:"Times New Roman","serif";color:red'>Effective 1 January 2016, CAs MUST NOT issue Subordinate CA Certificates that utilize the SHA-1 algorithm. CAs MUST NOT issue SHA-2 Subscriber certificates under SHA-1 Subordinate CA Certificates.</span></u><span style='font-family:"Times New Roman","serif";color:red'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Times New Roman","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Times New Roman","serif"'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:14.0pt;font-family:"Times New Roman","serif"'>Appendix A - Cryptographic Algorithm and Key Requirements (Normative)<o:p></o:p></span></b></p><p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>…<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Add this note under Table 2, Subordinate CA certificates:<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-family:"Times New Roman","serif";color:red'>* SHA-1 MAY be used with RSA keys in accordance with the criteria defined in Section 9.4.3.<o:p></o:p></span></u></p><p class=MsoNormal><span style='font-family:"Times New Roman","serif";color:red'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>And amend this note at the end of the 3 tables. </span><o:p></o:p></p><p class=MsoNormal><span style='font-family:"Times New Roman","serif";color:red'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-family:"Times New Roman","serif"'>* SHA-1 MAY be used with RSA keys<span style='color:#1F497D'> </span><u><span style='color:red'>in accordance with the criteria defined in Section 9.4.1 </span></u></span><s><span style='font-size:10.0pt;font-family:"TimesNewRomanPSMT","serif"'>until SHA-256 is supported widely by browsers used by a substantial<o:p></o:p></span></s></p><p class=MsoNormal><s><span style='font-size:10.0pt;font-family:"TimesNewRomanPSMT","serif"'>portion of relying-parties worldwide</span></s><span style='font-size:10.0pt;font-family:"TimesNewRomanPSMT","serif"'>. </span><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>