<html 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=utf-8"><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:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
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:12.0pt;
font-family:"Aptos",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:812214746;
mso-list-type:hybrid;
mso-list-template-ids:-2061456986 -333675472 134807555 134807557 134807553 134807555 134807557 134807553 134807555 134807557;}
@list l0:level1
{mso-level-start-at:7;
mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;
mso-fareast-font-family:Aptos;
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:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
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:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
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:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style></head><body lang=en-SE link=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;mso-fareast-language:EN-US'>Hi Chris,<br><br>Thank you for getting this ballot out. After having gone through the language more detailed, I have a few comments. I’ve added these to the Github PR, but will list them here additionally for visibility.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><ul style='margin-top:0cm' type=disc><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo1'><span style='font-size:11.0pt;mso-fareast-language:EN-US'>Minor nit: <a href="https://github.com/cabforum/servercert/pull/487#discussion_r1549074735">https://github.com/cabforum/servercert/pull/487#discussion_r1549074735</a><o:p></o:p></span></li><ul style='margin-top:0cm' type=circle><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level2 lfo1'><span style='font-size:11.0pt;mso-fareast-language:EN-US'>I’m not native english, so I may be wrong on this one, but it seems to me like this “from” should be a “by”. <o:p></o:p></span></li></ul><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo1'><span style='font-size:11.0pt;mso-fareast-language:EN-US'>I can imagine CAs may want to differentiate their checks for CAA lookups vs those for Domain Control, as such I would recommend this “and/or”: <a href="https://github.com/cabforum/servercert/pull/487#discussion_r1549076900">https://github.com/cabforum/servercert/pull/487#discussion_r1549076900</a><o:p></o:p></span></li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo1'><span style='font-size:11.0pt;mso-fareast-language:EN-US'>Section 3.2.2.9 paragraph 2 currently reads, or can be read in such a way that a single response from a Network Perspective needs to contain both the necessary information to asses (a) <b>and</b> (b) in that paragraph. I can imagine CAs wanting to use 2 different calls for that, thus resulting in 2 different responses, both confirming different checks. I’ve added a suggestion here, but I’m not fully happy with that language either. If someone else has a better suggestion, please comment. <br>I thought about making the “and” at the end of (a) an “and/or”, but that may then result in CAs believing they only need to confirm either Domain Control or CAA alltogether, which is not desirable.<o:p></o:p></span></li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo1'><span style='font-size:11.0pt;mso-fareast-language:EN-US'>Another minor one, but relevant: <a href="https://github.com/cabforum/servercert/pull/487/files#r1549101349">https://github.com/cabforum/servercert/pull/487/files#r1549101349</a> It seems like re-use should also allow for the domain itself to be able to re-use data. <o:p></o:p></span></li></ul><p class=MsoNormal><span style='font-size:11.0pt;mso-fareast-language:EN-US'><br>Regards,<br><br>Martijn<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div id=mail-editor-reference-message-container><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='color:black'>From: </span></b><span style='color:black'>Servercert-wg <servercert-wg-bounces@cabforum.org> on behalf of Chris Clements via Servercert-wg <servercert-wg@cabforum.org><br><b>Date: </b>Wednesday, 20 March 2024 at 21:20<br><b>To: </b>Dimitris Zacharopoulos (HARICA) <dzacharo@harica.gr>, CA/B Forum Server Certificate WG Public Discussion List <servercert-wg@cabforum.org><br><b>Subject: </b>Re: [Servercert-wg] Discussion Period Begins - Ballot SC-067 V1: "Require domain validation and CAA checks to be performed from multiple Network Perspectives”<o:p></o:p></span></p></div><div style='border:solid black 1.0pt;padding:2.0pt 2.0pt 2.0pt 2.0pt'><p class=MsoNormal style='line-height:12.0pt;background:#FAFA03'><span style='font-size:10.0pt;font-family:"Calibri",sans-serif;color:black'>CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p style='margin:0cm'><span style='font-family:"Arial",sans-serif'>Hi Dimitris,</span><o:p></o:p></p><p style='margin:0cm'><o:p> </o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif'>Your suggestion to extend the discussion period to at least 30 days sounds very reasonable and fair to us. I am providing an updated preamble below that extends the current discussion and makes no other changes. </span><o:p></o:p></p><p style='margin:0cm'><o:p> </o:p></p><p style='margin:0cm'><o:p> </o:p></p><p style='margin:0cm'><b><span style='font-family:"Arial",sans-serif;color:#0E101A'>Purpose of Ballot SC-067</span></b><span style='font-family:"Arial",sans-serif;color:#0E101A'>:</span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:#0E101A'>This Ballot proposes updates to the <i>Baseline Requirements for the Issuance and Management of Publicly-Trusted TLS Server Certificates</i> (i.e., TLS BRs) related to “Multi-Perspective Issuance Corroboration” (“MPIC”).</span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p style='margin:0cm'><b><span style='font-family:"Arial",sans-serif;color:#0E101A'>Background</span></b><span style='font-family:"Arial",sans-serif;color:#0E101A'>:</span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p style='margin:0cm'>- MPIC refers to performing domain validation and CAA checks from multiple Network Perspectives before certificate issuance, as described within the Ballot for the applicable validation methods in TLS BR Sections 3.2.2.4 and 3.2.2.5.<br>- Not all methods described in TLS BR Sections 3.2.2.4 and 3.2.2.5 will require using MPIC.<br>- This work was most recently motivated by research presented at Face-to-Face 58 [1] by Princeton University, but has been discussed for years prior as well.<br>- The goal of this proposal is to make it more difficult for adversaries to successfully launch equally-specific prefix attacks against the domain validation processes described in the TLS BRs.<br>- Additional background information can be found in an update shared at Face-to-Face 60 [2].<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p style='margin:0cm'><b><span style='font-family:"Arial",sans-serif;color:#0E101A'>Benefits of Adoption</span></b><span style='font-family:"Arial",sans-serif;color:#0E101A'>:</span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p style='margin:0cm'>- Recent publicly-documented attacks have used BGP hijacks to fool domain control validation and obtain malicious certificates, which led to the impersonation of HTTPS websites [3][4].<br>- Routing security defenses (e.g., RPKI) can mitigate the risk of global BGP attacks, but localized, equally-specific BGP attacks still pose a significant threat to the Web PKI [5][6].<br>- Corroborating domain control validation checks from multiple network perspectives (i.e., MPIC) spread across the Internet substantially reduces the threat posed by equally-specific BGP attacks, ensuring the integrity of domain validation and issuance decisions [5][7][8].<br>- Existing deployments of MPIC at the scale of millions of certificates a day demonstrate the feasibility of this technique at Internet scale [7][9].<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p style='margin:0cm'><b><span style='font-family:"Arial",sans-serif;color:#0E101A'>Intellectual Property (IP) Disclosure</span></b><span style='font-family:"Arial",sans-serif;color:#0E101A'>:</span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p style='margin:0cm'>- While not a Server Certificate Working Group Member, researchers from Princeton University presented at Face-to-Face 58, provided academic expertise, and highlighted publicly-available peer-reviewed research to support Members in drafting this ballot.<br>- The Princeton University researchers indicate that they have not filed for any patents relating to their MPIC work and do not plan to do so in the future.<br>- Princeton University has indicated that it is unable to agree to the CA/Browser Forum IPR agreement because it could encumber inventions invented by researchers not involved in the development of MPIC or with the CA/B Forum.<br>- Princeton University has instead provided the attached IPR statement. Pursuant to the IPR statement, Princeton University has granted a worldwide royalty free license to the intellectual property in MPIC developed by the researchers and has made representations regarding its lack of knowledge of any other Princeton intellectual property needed to implement MPIC.<br>- For clarity, Princeton University’s IPR statement is NOT intended to replace the Forum’s IPR agreement or allow Princeton to participate in the Forum in any capacity.<br>- Members seeking legal advice regarding this ballot should consult their own counsel.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p style='margin:0cm'><b><span style='font-family:"Arial",sans-serif;color:#0E101A'>Proposal Revision History</span></b><span style='font-family:"Arial",sans-serif;color:#0E101A'>:</span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p style='margin:0cm'>- Pre-Ballot Release #1 (work team artifacts and broader Validation Subcommittee collaboration) [10]<br>- Pre-Ballot Release #2 [11]<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p style='margin:0cm'><b><span style='font-family:"Arial",sans-serif;color:#0E101A'>Previous versions of this Ballot</span></b><span style='font-family:"Arial",sans-serif;color:#0E101A'>:</span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:#0E101A'>- N/A, this is the first discussion period.</span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p style='margin:0cm'><b><span style='font-family:"Arial",sans-serif;color:#0E101A'>References</span></b><span style='font-family:"Arial",sans-serif;color:#0E101A'>:</span><o:p></o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:#0E101A'>[1] </span><a href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcabforum.org%2Fwp-content%2Fuploads%2F13-CAB-Forum-face-to-face-multiple-vantage-points.pdf&data=05%7C02%7Cmartijn.katerbarg%40sectigo.com%7C351c2b0d57d94d1e225a08dc491a9f54%7C0e9c48946caa465d96604b6968b49fb7%7C0%7C0%7C638465628230417253%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=GoX5Lbu9SFpKRc1rISxdAuK7VJvYyDEagL1FwvMqnCA%3D&reserved=0" target="_blank"><span style='font-family:"Arial",sans-serif'>https://cabforum.org/wp-content/uploads/13-CAB-Forum-face-to-face-multiple-vantage-points.pdf</span></a><o:p></o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:#0E101A'>[2] </span><a href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrive.google.com%2Ffile%2Fd%2F1LTwtAwHXcSaPVSsqKQztNJrV2ozHJ7ZL%2Fview%3Fusp%3Ddrive_link&data=05%7C02%7Cmartijn.katerbarg%40sectigo.com%7C351c2b0d57d94d1e225a08dc491a9f54%7C0e9c48946caa465d96604b6968b49fb7%7C0%7C0%7C638465628230427471%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=67N%2Bzjb413rZd5EoEBJxanGoGrzAuXugTPMXbvcv%2BoI%3D&reserved=0" target="_blank"><span style='font-family:"Arial",sans-serif'>https://drive.google.com/file/d/1LTwtAwHXcSaPVSsqKQztNJrV2ozHJ7ZL/view?usp=drive_link</span></a><span style='font-family:"Arial",sans-serif;color:#0E101A'> </span><o:p></o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:#0E101A'>[3] </span><a href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmedium.com%2Fs2wblog%2Fpost-mortem-of-klayswap-incident-through-bgp-hijacking-en-3ed7e33de600&data=05%7C02%7Cmartijn.katerbarg%40sectigo.com%7C351c2b0d57d94d1e225a08dc491a9f54%7C0e9c48946caa465d96604b6968b49fb7%7C0%7C0%7C638465628230434584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=56zKEthdTZLDQHEBjMJlm7M9EdnsQCXbEuokDw63lf8%3D&reserved=0" target="_blank"><span style='font-family:"Arial",sans-serif'>https://medium.com/s2wblog/post-mortem-of-klayswap-incident-through-bgp-hijacking-en-3ed7e33de600</span></a><span style='font-family:"Arial",sans-serif;color:#0E101A'> </span><o:p></o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:#0E101A'>[4] </span><a href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.coinbase.com%2Fblog%2Fceler-bridge-incident-analysis&data=05%7C02%7Cmartijn.katerbarg%40sectigo.com%7C351c2b0d57d94d1e225a08dc491a9f54%7C0e9c48946caa465d96604b6968b49fb7%7C0%7C0%7C638465628230440923%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=XE6439%2F24MaEeGbHQPU%2BgHd99%2Fa%2Bp86qUIY2u26ESR8%3D&reserved=0" target="_blank"><span style='font-family:"Arial",sans-serif'>https://www.coinbase.com/blog/celer-bridge-incident-analysis</span></a><span style='font-family:"Arial",sans-serif;color:#0E101A'> </span><o:p></o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:#0E101A'>[5] </span><a href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.usenix.org%2Fconference%2Fusenixsecurity23%2Fpresentation%2Fcimaszewski&data=05%7C02%7Cmartijn.katerbarg%40sectigo.com%7C351c2b0d57d94d1e225a08dc491a9f54%7C0e9c48946caa465d96604b6968b49fb7%7C0%7C0%7C638465628230447223%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=JUM%2FaN6fWHHowr2W9KbqIhfg0P1Tm30Kx8klEIJ%2FV4k%3D&reserved=0" target="_blank"><span style='font-family:"Arial",sans-serif'>https://www.usenix.org/conference/usenixsecurity23/presentation/cimaszewski</span></a><span style='font-family:"Arial",sans-serif;color:#0E101A'> </span><o:p></o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:#0E101A'>[6] </span><a href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blackhat.com%2Fdocs%2Fus-15%2Fmaterials%2Fus-15-Gavrichenkov-Breaking-HTTPS-With-BGP-Hijacking-wp.pdf&data=05%7C02%7Cmartijn.katerbarg%40sectigo.com%7C351c2b0d57d94d1e225a08dc491a9f54%7C0e9c48946caa465d96604b6968b49fb7%7C0%7C0%7C638465628230452773%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=%2BKTqv6mLNjqvr9TJ3xSM8XD%2FICfoGiKqoZdaKT%2FVRtI%3D&reserved=0" target="_blank"><span style='font-family:"Arial",sans-serif'>https://www.blackhat.com/docs/us-15/materials/us-15-Gavrichenkov-Breaking-HTTPS-With-BGP-Hijacking-wp.pdf</span></a><span style='font-family:"Arial",sans-serif;color:#0E101A'> </span><o:p></o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:#0E101A'>[7] </span><a href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.usenix.org%2Fconference%2Fusenixsecurity21%2Fpresentation%2Fbirge-lee&data=05%7C02%7Cmartijn.katerbarg%40sectigo.com%7C351c2b0d57d94d1e225a08dc491a9f54%7C0e9c48946caa465d96604b6968b49fb7%7C0%7C0%7C638465628230458401%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=uG%2F%2BZU4A2g5xK1tom4JLBKhFLzDgmnReTdig01rqW20%3D&reserved=0" target="_blank"><span style='font-family:"Arial",sans-serif'>https://www.usenix.org/conference/usenixsecurity21/presentation/birge-lee</span></a><span style='font-family:"Arial",sans-serif;color:#0E101A'> </span><o:p></o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:#0E101A'>[8] </span><a href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.usenix.org%2Fconference%2Fusenixsecurity18%2Fpresentation%2Fbirge-lee&data=05%7C02%7Cmartijn.katerbarg%40sectigo.com%7C351c2b0d57d94d1e225a08dc491a9f54%7C0e9c48946caa465d96604b6968b49fb7%7C0%7C0%7C638465628230463868%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=Sn%2BixjQn94EbiLbBVP7IiNIJJHOEzA%2BZUn2wPD57e9A%3D&reserved=0" target="_blank"><span style='font-family:"Arial",sans-serif'>https://www.usenix.org/conference/usenixsecurity18/presentation/birge-lee</span></a><span style='font-family:"Arial",sans-serif;color:#0E101A'> </span><o:p></o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:#0E101A'>[9] </span><a href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsecurity.googleblog.com%2F2023%2F05%2Fgoogle-trust-services-acme-api_0503894189.html&data=05%7C02%7Cmartijn.katerbarg%40sectigo.com%7C351c2b0d57d94d1e225a08dc491a9f54%7C0e9c48946caa465d96604b6968b49fb7%7C0%7C0%7C638465628230469305%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=sp00Gv5b6A%2B8%2Fjp%2BqJ1KHyXx4QifJVKXmmkBc42Y2%2Bs%3D&reserved=0" target="_blank"><span style='font-family:"Arial",sans-serif'>https://security.googleblog.com/2023/05/google-trust-services-acme-api_0503894189.html</span></a><span style='font-family:"Arial",sans-serif;color:#0E101A'> </span><o:p></o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:#0E101A'>[10] </span><a href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fryancdickson%2Fstaging%2Fpull%2F6&data=05%7C02%7Cmartijn.katerbarg%40sectigo.com%7C351c2b0d57d94d1e225a08dc491a9f54%7C0e9c48946caa465d96604b6968b49fb7%7C0%7C0%7C638465628230475067%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=zQgtc7MvlOlKiH6f2GzteKaZG5ZyBrYPCrhPsFHbqHI%3D&reserved=0" target="_blank"><span style='font-family:"Arial",sans-serif'>https://github.com/ryancdickson/staging/pull/6</span></a><span style='font-family:"Arial",sans-serif;color:#0E101A'> </span><o:p></o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:#0E101A'>[11] </span><a href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fryancdickson%2Fstaging%2Fpull%2F8&data=05%7C02%7Cmartijn.katerbarg%40sectigo.com%7C351c2b0d57d94d1e225a08dc491a9f54%7C0e9c48946caa465d96604b6968b49fb7%7C0%7C0%7C638465628230480284%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=qnupbwuMcOtQcw%2FhMx0PYmmejyjQonGr90Xvjaa1oE4%3D&reserved=0" target="_blank"><span style='font-family:"Arial",sans-serif'>https://github.com/ryancdickson/staging/pull/8</span></a><span style='font-family:"Arial",sans-serif;color:#0E101A'> </span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:#0E101A'>The following motion has been proposed by Chris Clements and Ryan Dickson of Google (Chrome Root Program) and endorsed by Aaron Gable (ISRG / Let’s Encrypt) and Wayne Thayer (Fastly). </span><o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><p style='margin:0cm'><b><span style='font-family:"Arial",sans-serif;color:black'>— Motion Begins —</span></b><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:black'>This ballot modifies the “Baseline Requirements for the Issuance and Management of Publicly-Trusted TLS Server Certificates” (“Baseline Requirements”), based on Version 2.0.2.</span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:black'>MODIFY the Baseline Requirements as specified in the following Redline:</span><o:p></o:p></p><p style='margin:0cm'><a href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcabforum%2Fservercert%2Fcompare%2F41f01640748fa612386f8b1a3031cd1bff3d4f35..6d10abda8980c6eb941987d3fc26e753e62858c0&data=05%7C02%7Cmartijn.katerbarg%40sectigo.com%7C351c2b0d57d94d1e225a08dc491a9f54%7C0e9c48946caa465d96604b6968b49fb7%7C0%7C0%7C638465628230485479%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=ANXwEeN5k5oU5S5eBIcwALiRXdJMdX6p17aZklae48c%3D&reserved=0" target="_blank"><span style='font-family:"Arial",sans-serif'>https://github.com/cabforum/servercert/compare/41f01640748fa612386f8b1a3031cd1bff3d4f35..6d10abda8980c6eb941987d3fc26e753e62858c0</span></a><span style='font-family:"Arial",sans-serif;color:black'> </span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p style='margin:0cm'><b><span style='font-family:"Arial",sans-serif;color:black'>— Motion Ends —</span></b><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:black'>This ballot proposes a Final Maintenance Guideline. The procedure for approval of this ballot is as follows:</span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p style='margin:0cm'><b><span style='font-family:"Arial",sans-serif;color:black'>Discussion (at least <span style='background:yellow'>30</span> days)</span></b><o:p></o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:black'>- Start: 2024-03-18 15:30:00 UTC</span><o:p></o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:black'>- End no earlier than: 2024-04-<span style='background:yellow'>17</span> 15:30:00 UTC</span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p style='margin:0cm'><b><span style='font-family:"Arial",sans-serif;color:black'>Vote for approval (7 days)</span></b><o:p></o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:black'>- Start: TBD</span><o:p></o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:black'>- End: TBD</span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Tue, Mar 19, 2024 at 11:00<span style='font-family:"Arial",sans-serif'> </span>AM Dimitris Zacharopoulos (HARICA) via Servercert-wg <<a href="mailto:servercert-wg@cabforum.org" target="_blank">servercert-wg@cabforum.org</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><div><p class=MsoNormal style='margin-bottom:12.0pt'>Hi Chris,<o:p></o:p></p><div><p class=MsoNormal>On 18/3/2024 5:32 μ.μ., Chris Clements via Servercert-wg wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p style='margin:0cm'><b><span style='font-family:"Arial",sans-serif;color:#0E101A'>Intellectual Property (IP) Disclosure</span></b><span style='font-family:"Arial",sans-serif;color:#0E101A'>:</span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:#0E101A'>- While not a Server Certificate Working Group Member, researchers from Princeton University presented at Face-to-Face 58, provided academic expertise, and highlighted publicly-available peer-reviewed research to support Members in drafting this ballot.</span><o:p></o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:#0E101A'>- The Princeton University researchers indicate that they have not filed for any patents relating to their MPIC work and do not plan to do so in the future.</span><o:p></o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:#0E101A'>- Princeton University has indicated that it is unable to agree to the CA/Browser Forum IPR agreement because it could encumber inventions invented by researchers not involved in the development of MPIC or with the CA/B Forum.</span><o:p></o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:#0E101A'>- Princeton University has instead provided the attached IPR statement. Pursuant to the IPR statement, Princeton University has granted a worldwide royalty free license to the intellectual property in MPIC developed by the researchers and has made representations regarding its lack of knowledge of any other Princeton intellectual property needed to implement MPIC.</span><o:p></o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:black'>- For clarity, Princeton University’s IPR statement is NOT intended to replace the Forum’s IPR agreement or allow Princeton to participate in the Forum in any capacity.</span><o:p></o:p></p><p style='margin:0cm'><span style='font-family:"Arial",sans-serif;color:black'>- Members seeking legal advice regarding this ballot should consult their own counsel.</span><o:p></o:p></p></blockquote><p class=MsoNormal><br>This is the first time the Forum and a Chartered Working Group goes through a ballot with essential contributions coming from a non-Member. At the last F2F meeting, we discussed about possibly allowing fewer days for the IPR review in certain cases, and many Members felt that this would create problems because legal departments need time to review these documents. My interpretation is that Organizations that participate in the Forum are very sensitive when it comes to IP issues.<br><br>I would therefore suggest that the discussion period takes <b>at least 30 days</b> (similar to the time it takes for the IPR review period to end for Maintenance Guidelines), so that Members have time to provide information to their legal departments regarding the commitment by Princeton from January 11, 2024, and see if there are any objections or concerns raised. All members will ultimately have to accept the proposed IPR solution offered by Princeton before the ballot enters its voting period. I hope this sounds reasonable and fair. <br><br>At the same time, we can continue discussing the proposed language that updates the BRs.<br><br>Other Members that are sensitive on this matter can also speak up about this suggested process so we can proceed with caution and minimize the IP risks.<br><br><br>Thank you,<br>Dimitris.<o:p></o:p></p></div><p class=MsoNormal>_______________________________________________<br>Servercert-wg mailing list<br><a href="mailto:Servercert-wg@cabforum.org" target="_blank">Servercert-wg@cabforum.org</a><br><a href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.cabforum.org%2Fmailman%2Flistinfo%2Fservercert-wg&data=05%7C02%7Cmartijn.katerbarg%40sectigo.com%7C351c2b0d57d94d1e225a08dc491a9f54%7C0e9c48946caa465d96604b6968b49fb7%7C0%7C0%7C638465628230492660%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=jZ8MBQ4l0cHamgNbuRy3NjWc34gpTaKmVdABBIzfhX4%3D&reserved=0" target="_blank">https://lists.cabforum.org/mailman/listinfo/servercert-wg</a><o:p></o:p></p></blockquote></div></div></div></div></div></body></html>