<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Oct 20, 2017, at 11:30 AM, Ryan Sleevi <<a href="mailto:sleevi@google.com" class="">sleevi@google.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><br class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On Fri, Oct 20, 2017 at 2:20 PM, Geoff Keating via Public <span dir="ltr" class=""><<a href="mailto:public@cabforum.org" target="_blank" class="">public@cabforum.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word" class=""></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word" class=""></div></blockquote></div></div></div></div></blockquote><br class=""><blockquote type="cite" class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word" class=""><div class="">- How this matches with the X.520 definition of dnQualifier, in particular the second sentence:</div><div class=""><br class=""></div><div class="">The DN Qualifier attribute type specifies disambiguating information to add to the relative distinguished <wbr class="">name of an entry. It is intended to be used for entries held in multiple DSAs which would otherwise have the same name, and that its value be the same in a given DSA for all entries to which this information has been added.</div></div></blockquote><div class=""><br class=""></div><div class="">This matches 1:1. Is there a concern that it doesn't match, or that more rules are necessary?</div></div></div></div></blockquote><div><br class=""></div><div>What I quoted above is X.520. It doesn't seem to me to be describing the same thing as the ballot. In particular, normally you would consider a CA’s issuing infrastructure to be one single DSA, which produces a contradiction between the ballot text "The CA MAY set the dnQualifer value to the base64 encoding of the SHA1 hash of the subjectAlternativeName” and X.520’s text “its value be the same in a given DSA”.</div><br class=""><blockquote type="cite" class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word" class=""><div class="">- How this is actually intended to be used in the web PKI?</div><div class=""><br class=""></div></div></blockquote><div class=""><br class=""></div><div class="">As raised on our most recent call, one notable thing is that this allows CAs to issue single certificates for domain names greater than 64 characters, at a DV level, while interoperably working with the Web PKI. This flows as follows:</div><div class=""><br class=""></div><div class="">- The X.509/RFC 5280 definition for commonName is limited to 64 characters.</div><div class="">- If you have a certificate with a domain name greater than 64 characters, you cannot place it in the common name of the subject.</div><div class="">- The common name of the subject may only contain domain names and IP addresses.</div><div class="">- All other specified fields of the Subject must be validated to OV level.</div><div class=""><br class=""></div><div class="">As a consequence, the only way with DV today to represent these certificates is with an empty sequence for the subject name and a critical subjectAltName, pursuant with RFC5280. You can see this at <a href="https://no-subject.badssl.com" class="">https://no-subject.badssl.com</a></div><div class=""><br class=""></div><div class="">If you tried to load that on Apple iOS, it would load.</div><div class="">If you tried to load that on Apple macOS earlier than 10.10, it would load.</div><div class="">If you tried to load that on Apple macOS since 10.10, it will fail, as empty subjects are no longer supported.</div></div></div></div></blockquote><div><br class=""></div><div>It works for me in 10.11—so does that mean this ballot is no longer needed?</div><br class=""><blockquote type="cite" class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class="">This provides a way for a CA to ensure that a DV certificate with a domain name of more than 64 characters can be issued, by using the dnQualifier field (which is CA-controlled, as noted in the relevant X.520 text you cited) to serve as a disambiguator between certificates the CA has issued.</div><div class=""><br class=""></div><div class="">Does that help capture it?</div></div></div></div></blockquote><div><br class=""></div><div>I see the problem but I’m very hesitant to standardise something in CABforum which contradicts X.520.</div><div><br class=""></div><div>Have we really explored other alternatives? For example, truncate the commonName to 60 characters and append an ellipsis in Unicode (“…”) so that it can’t be confused with a domain name.</div><div><br class=""></div><blockquote type="cite" class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class=""> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word" class=""><div class=""></div><div class=""><div class=""><blockquote type="cite" class=""><div class=""><div class="gmail-h5"><div class="">On Oct 12, 2017, at 11:04 AM, Ben Wilson via Public <<a href="mailto:public@cabforum.org" target="_blank" class="">public@cabforum.org</a>> wrote:</div><br class="gmail-m_-4595804663788861089Apple-interchange-newline"></div></div><div class=""><div class=""><div class="gmail-h5"><div class="gmail-m_-4595804663788861089WordSection1" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><p class="gmail-m_-4595804663788861089line867" style="margin-right:0in;margin-left:0in;font-size:11pt;font-family:Calibri,sans-serif"><strong class=""><span style="font-family:Calibri,sans-serif" class="">Ballot 208 - dnQualifiers</span></strong><u class=""></u><u class=""></u></p><p class="gmail-m_-4595804663788861089line874" style="margin-right:0in;margin-left:0in;font-size:11pt;font-family:Calibri,sans-serif">This ballot allows CAs to use dnQualifiers in certificates to partition groups of certificates into different sets and to allow non-identity information to be included in DV certificates.<span class="gmail-m_-4595804663788861089Apple-converted-space"> </span><u class=""></u><u class=""></u></p><p class="gmail-m_-4595804663788861089line862" style="margin-right:0in;margin-left:0in;font-size:11pt;font-family:Calibri,sans-serif">The following motion has been proposed by Peter Bowen of Amazon and endorsed by Ben Wilson of DigiCert and Ryan Sleevi of Google.<span class="gmail-m_-4595804663788861089Apple-converted-space"> </span><u class=""></u><u class=""></u></p><p class="gmail-m_-4595804663788861089line874" style="margin-right:0in;margin-left:0in;font-size:11pt;font-family:Calibri,sans-serif">-- MOTION BEGINS --<span class="gmail-m_-4595804663788861089Apple-converted-space"> </span><u class=""></u><u class=""></u></p><p class="gmail-m_-4595804663788861089line874" style="margin-right:0in;margin-left:0in;font-size:11pt;font-family:Calibri,sans-serif">In the Baseline Requirements, REPLACE the definition of "Subject Identity Information" with:<span class="gmail-m_-4595804663788861089Apple-converted-space"> </span><u class=""></u><u class=""></u></p><p class="gmail-m_-4595804663788861089line874" style="margin-right:0in;margin-left:0in;font-size:11pt;font-family:Calibri,sans-serif">"Information that identifies the Certificate Subject. Subject Identity Information does not include [strikeout]<s class="">a domain name listed in the subjectAltName extension or the Subject commonName field</s>[/strikeout] [insert]<u class="">dnQualifier attributes in Distinguished Names, commonName attributes in Distinguished Names, dNSName Subject Alternative Names, iPAddress Subject Alternative Names, or SRVName Subject Alternative Names</u>[/insert]."<span class="gmail-m_-4595804663788861089Apple-converted-space"> </span><u class=""></u><u class=""></u></p><p class="gmail-m_-4595804663788861089line874" style="margin-right:0in;margin-left:0in;font-size:11pt;font-family:Calibri,sans-serif">In Section 7.1.4.2.2 Subject Distinguished Name Fields, re-letter "j" (Other Subject Attributes) as letter "k" and INSERT a new subsection j. that reads:<span class="gmail-m_-4595804663788861089Apple-converted-space"> </span><u class=""></u><u class=""></u></p><p class="gmail-m_-4595804663788861089line874" style="margin-right:0in;margin-left:0in;font-size:11pt;font-family:Calibri,sans-serif">j. Certificate Field: subject:dnQualifier<span class="gmail-m_-4595804663788861089Apple-converted-space"> </span><u class=""></u><u class=""></u></p><ul type="disc" style="margin-bottom:0in" class=""><li class="MsoNormal" style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Optional. Contents: This field is intended to be used when several certificates with the same subject can be partitioned into sets of related certificates. Each related certificate set MAY have the same dnQualifier. The CA may include a dnQualifier attribute with a zero length value to explicitly indicate that the CA makes no assertion about relationship with other certificates with the same subject. The CA MAY set the dnQualifer value to the base64 encoding of the SHA1 hash of the subjectAlternativeName extnValue if it wishes to indicate grouping of certificates by alternative name set.<span class="gmail-m_-4595804663788861089Apple-converted-space"> </span><u class=""></u><u class=""></u></li></ul><p class="gmail-m_-4595804663788861089line874" style="margin-right:0in;margin-left:0in;font-size:11pt;font-family:Calibri,sans-serif">-- MOTION ENDS --<span class="gmail-m_-4595804663788861089Apple-converted-space"> </span><u class=""></u><u class=""></u></p><p class="gmail-m_-4595804663788861089line874" style="margin-right:0in;margin-left:0in;font-size:11pt;font-family:Calibri,sans-serif">The procedure for approval of this Final Maintenance Guideline ballot is as follows (exact start and end times may be adjusted to comply with applicable Bylaws and IPR Agreement):<span class="gmail-m_-4595804663788861089Apple-converted-space"> </span><u class=""></u><u class=""></u></p><p class="gmail-m_-4595804663788861089line874" style="margin-right:0in;margin-left:0in;font-size:11pt;font-family:Calibri,sans-serif">BALLOT 208 Status: Final Maintenance Guideline Start time (22:00 UTC) End time (22:00 UTC)<span class="gmail-m_-4595804663788861089Apple-converted-space"> </span><u class=""></u><u class=""></u></p><p class="gmail-m_-4595804663788861089line874" style="margin-right:0in;margin-left:0in;font-size:11pt;font-family:Calibri,sans-serif">Discussion begins October 12, 2017 22:00 UTC and ends October 19, 2017 22:00 UTC (7 days)<span class="gmail-m_-4595804663788861089Apple-converted-space"> </span><u class=""></u><u class=""></u></p><p class="gmail-m_-4595804663788861089line874" style="margin-right:0in;margin-left:0in;font-size:11pt;font-family:Calibri,sans-serif">Vote for approval begins October 19, 2017 22:00 UTC and ends October 26, 2017 22:00 UTC (7 days)<span class="gmail-m_-4595804663788861089Apple-converted-space"> </span><u class=""></u><u class=""></u></p><p class="gmail-m_-4595804663788861089line874" style="margin-right:0in;margin-left:0in;font-size:11pt;font-family:Calibri,sans-serif">If vote approves ballot: Review Period (Chair to send Review Notice) (30 days). If Exclusion Notice(s) filed, ballot approval is rescinded and PAG to be created. If no Exclusion Notices filed, ballot becomes effective at end of Review Period. Upon filing of Review Notice by Chair 30 days after filing of Review Notice by Chair<span class="gmail-m_-4595804663788861089Apple-converted-space"> </span><u class=""></u><u class=""></u></p><p class="gmail-m_-4595804663788861089line874" style="margin-right:0in;margin-left:0in;font-size:11pt;font-family:Calibri,sans-serif">From Bylaw 2.3: If the Draft Guideline Ballot is proposing a Final Maintenance Guideline, such ballot will include a redline or comparison showing the set of changes from the Final Guideline section(s) intended to become a Final Maintenance Guideline, and need not include a copy of the full set of guidelines. Such redline or comparison shall be made against the Final Guideline section(s) as they exist at the time a ballot is proposed, and need not take into consideration other ballots that may be proposed subsequently, except as provided in Bylaw Section 2.3(j).<span class="gmail-m_-4595804663788861089Apple-converted-space"> </span><u class=""></u><u class=""></u></p><p class="gmail-m_-4595804663788861089line862" style="margin-right:0in;margin-left:0in;font-size:11pt;font-family:Calibri,sans-serif">Votes must be cast by posting an on-list reply to this thread on the Public list. A vote in favor of the motion must indicate a clear 'yes' in the response. A vote against must indicate a clear 'no' in the response. A vote to abstain must indicate a clear 'abstain' in the response. Unclear responses will not be counted. The latest vote received from any representative of a voting member before the close of the voting period will be counted. Voting members are listed here:<span class="gmail-m_-4595804663788861089Apple-converted-space"> </span><a href="https://cabforum.org/members/" style="color:rgb(149,79,114);text-decoration:underline" target="_blank" class="">https://cabforum.org/<wbr class="">members/</a><u class=""></u><u class=""></u></p><p class="gmail-m_-4595804663788861089line874" style="margin-right:0in;margin-left:0in;font-size:11pt;font-family:Calibri,sans-serif">In order for the motion to be adopted, two thirds or more of the votes cast by members in the CA category and greater than 50% of the votes cast by members in the browser category must be in favor. Quorum is shown on CA/Browser Forum wiki. Under Bylaw 2.2(g), at least the required quorum number must participate in the ballot for the ballot to be valid, either by voting in favor, voting against, or abstaining.<span class="gmail-m_-4595804663788861089Apple-converted-space"> </span><u class=""></u><u class=""></u></p><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif" class=""><u class=""></u> <u class=""></u></div></div></div></div><span id="gmail-m_-4595804663788861089cid:BAB55128-E418-43BE-B09C-97EF1F017818@apple.com" class=""><pre-ballot-208-dnQualifier.<wbr class="">pdf></span><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline" class="">__________________________<wbr class="">_____________________</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class=""><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline" class="">Public mailing list</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class=""><a href="mailto:Public@cabforum.org" style="color:rgb(149,79,114);text-decoration:underline;font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank" class="">Public@cabforum.org</a><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class=""><a href="https://cabforum.org/mailman/listinfo/public" style="color:rgb(149,79,114);text-decoration:underline;font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank" class="">https://cabforum.org/mailman/<wbr class="">listinfo/public</a></div></blockquote></div><br class=""></div></div><br class="">______________________________<wbr class="">_________________<br class="">
Public mailing list<br class="">
<a href="mailto:Public@cabforum.org" class="">Public@cabforum.org</a><br class="">
<a href="https://cabforum.org/mailman/listinfo/public" rel="noreferrer" target="_blank" class="">https://cabforum.org/mailman/<wbr class="">listinfo/public</a><br class="">
<br class=""></blockquote></div><br class=""></div></div>
</blockquote></div><br class=""></body></html>