<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Thanks for the great work Corey!<br>
<br>
I reviewed the PR and it seems most of the information has been
properly captured and moved to "reasonable" sections. I am saying
"reasonable" because depending on various interpretations of 3647 we
could propose slightly different locations but what you currently
proposed works fine.<br>
<br>
I'd like to comment on 10.1.2 (highlighted as red). I believe this
information is required and should be referenced in the NEW 3.2.2.2
to point to 10.1.2 of the TLS EV Guidelines.<br>
<br>
The NEW 4.9.7 section includes information about OCSP which we
should probably try to separate from CRLs, although I like the fact
that the issuance requirements for CRLs and OCSP are in one place.
RFC 3647 thinks otherwise :)<br>
<br>
Regarding Appendix A and how this is split between the NEW 6.1.5 and
7.1.3, I noticed that you have migrated language from the latest BRs
regarding the encoding of algorithms but also some additional
requirements like "The CA SHALL NOT use a different algorithm, such
as the id-RSASSA-PSS (OID: 1.2.840.113549.1.1.10) algorithm
identifier, to indicate an RSA key". Similarly for the NEW
7.1.3.2.2, I don't think the current CSBRs have these requirements
enforced. Please let me know if I missed anything.<br>
<br>
Regarding the deprecation of DSA, we must decide whether this "RFC
3647 alignment" ballot is expected to apply any normative changes or
just to "convert" into something that more-less has the same
expectations/requirements as the latest version of the CSBRs. Having
reviewed several ballots in the past, it's nice to know the scope of
the ballot and whether it is expected to make normative changes or
not. With that said, it would be fine - I think- to mark any
possible normative changes, like the deprecation of DSA, in the
preface of the ballot so Members know about them.<br>
<br>
Regarding KeyPurposeIDs, I believe lifetimeSigning IS a KeyPurposeId
that can be used in the EKU extension
(<a class="moz-txt-link-freetext" href="https://oidref.com/1.3.6.1.4.1.311.10.3.13">https://oidref.com/1.3.6.1.4.1.311.10.3.13</a>).<br>
<br>
Finally, some internal hyperlinks (anchors) don't seem to work. I'm
not sure if this is something related to the rendering of GitHub or
if you have typos in the hyperlinks.<br>
<br>
Appendices A and B are quite challenging to review and definitely
need another pair of eyes to check.<br>
<br>
<br>
Thanks,<br>
Dimitris.<br>
<br>
<div class="moz-cite-prefix">On 31/8/2021 6:02 μ.μ., Corey Bonnell
via Cscwg-public wrote:<br>
</div>
<blockquote type="cite"
cite="mid:0100017b9cbb9232-3bf4a5f1-09db-447c-825d-608e68f9ce8a-000000@email.amazonses.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style>@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:"Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}@font-face
{font-family:"\@Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}div.WordSection1
{page:WordSection1;}ol
{margin-bottom:0cm;}ul
{margin-bottom:0cm;}</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]-->
<div class="WordSection1">
<p class="MsoNormal">Hello,<o:p></o:p></p>
<p class="MsoNormal">To aid in the comparison/review process, I
have marked up the current CSBRs with highlighting (explained
below) and comments that indicate the new section where the
content is located.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The highlighting in the mapping document
has the following meanings:<o:p></o:p></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraph"
style="margin-left:0cm;mso-list:l0 level1 lfo1">Green
indicates the text is unchanged<o:p></o:p></li>
<li class="MsoListParagraph"
style="margin-left:0cm;mso-list:l0 level1 lfo1">Yellow
indicates the text is still present, but has been modified
for consistency or to fix section references that have
changed<o:p></o:p></li>
<li class="MsoListParagraph"
style="margin-left:0cm;mso-list:l0 level1 lfo1">Red
indicates the text has been dropped entirely. There are only
a few instances of this, but we should review carefully to
ensure that it can be safely dropped.<o:p></o:p></li>
</ul>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">A PR has been opened for the RFC
3647/Pandoc migration: <a
href="https://github.com/cabforum/code-signing/pull/6"
moz-do-not-send="true">https://github.com/cabforum/code-signing/pull/6</a>.
I pulled in Dimitris’s migration work (thanks Dimitris!) in
section 1 into my branch to complete the document.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Please provide your comments on that PR or
here on the list and let me know if anything isn’t clear or if
there’s any questions. If there’s lots of feedback we may want
to devote some time in upcoming calls to review together.<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">Corey<span
style="font-family:"Arial",sans-serif;color:#686869"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Cscwg-public mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Cscwg-public@cabforum.org">Cscwg-public@cabforum.org</a>
<a class="moz-txt-link-freetext" href="https://lists.cabforum.org/mailman/listinfo/cscwg-public">https://lists.cabforum.org/mailman/listinfo/cscwg-public</a>
</pre>
</blockquote>
<br>
</body>
</html>