<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div dir="ltr">Should we try to integrate here the proposed change to regulate de use and disclosure of QGIS?</div><div dir="ltr"><br></div><div dir="ltr">I made the PR some time ago, but on the old version. </div><div dir="ltr"><br></div><div dir="ltr">BR/P</div><div dir="ltr"><br><blockquote type="cite">Le 12 sept. 2023 à 20:18, Tim Hollebeek via Servercert-wg <servercert-wg@cabforum.org> a écrit :<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><meta http-equiv="Content-Type" content="text/html; charset=iso-2022-jp"><meta name="Generator" content="Microsoft Word 15 (filtered medium)"><style>@font-face { font-family: "MS Gothic"; }
@font-face { font-family: "Cambria Math"; }
@font-face { font-family: Calibri; }
@font-face { font-family: Consolas; }
@font-face { font-family: "MS PGothic"; }
@font-face { font-family: "@MS PGothic"; }
@font-face { font-family: "@MS Gothic"; }
p.MsoNormal, li.MsoNormal, div.MsoNormal { margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif; }
a:link, span.MsoHyperlink { color: rgb(5, 99, 193); text-decoration: underline; }
pre { margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: "Courier New"; }
span.HTMLPreformattedChar { font-family: Consolas; }
span.EmailStyle24 { font-family: Calibri, sans-serif; color: windowtext; }
.MsoChpDefault { font-size: 10pt; }
@page WordSection1 { size: 8.5in 11in; margin: 1in; }
div.WordSection1 { page: WordSection1; }</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"><span style="mso-fareast-language:EN-US">This is perfect, thank you. I’ll run it through our internal ballot review process and get you feedback from our compliance team.<o:p></o:p></span></p><p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p><p class="MsoNormal"><span style="mso-fareast-language:EN-US">-Tim<o:p></o:p></span></p><p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></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> Inigo Barreira <Inigo.Barreira@sectigo.com> <br><b>Sent:</b> Friday, September 8, 2023 12:54 PM<br><b>To:</b> Tim Hollebeek <tim.hollebeek@digicert.com>; 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] SC-065: Convert EVGs into RFC 3647 format pre-ballot<o:p></o:p></p></div></div><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal"><span lang="ES" style="mso-fareast-language:EN-US">Hi all, <o:p></o:p></span></p><p class="MsoNormal"><span lang="ES" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">Attached you´ll find the EVG v1.8.0 with comments in all sections indicating where those sections, and the content, have been moved into the new EVG RFC3647 format. So, with this document, plus the redlined version, I hope you can have now a clearer view of the changes done.<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">Let me know if you need anything else to clarify the new version.<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">Regards<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p><div><div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><span lang="ES">De:</span></b><span lang="ES"> Inigo Barreira <<a href="mailto:Inigo.Barreira@sectigo.com">Inigo.Barreira@sectigo.com</a>> <br><b>Enviado el:</b> martes, 29 de agosto de 2023 17:06<br><b>Para:</b> Tim Hollebeek <<a href="mailto:tim.hollebeek@digicert.com">tim.hollebeek@digicert.com</a>>; Dimitris Zacharopoulos (HARICA) <<a href="mailto:dzacharo@harica.gr">dzacharo@harica.gr</a>>; CA/B Forum Server Certificate WG Public Discussion List <<a href="mailto:servercert-wg@cabforum.org">servercert-wg@cabforum.org</a>><br><b>Asunto:</b> RE: [Servercert-wg] SC-065: Convert EVGs into RFC 3647 format pre-ballot<o:p></o:p></span></p></div></div><p class="MsoNormal"><span lang="ES"><o:p> </o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">Thanks Dimitris and Tim.<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">I did something of that internally but didn´t reflect on the document, so will try to reproduce to have it clearer.<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">OTOH, and as indicated in the PR, the whole section 11 has been placed in section 3.2 keeping the rest of the numbering. So, for example:<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">EVG EVG3647<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">11.1 3.2.1<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">11.1.1 3.2.1.1<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">11.1.2 3.2.1.2<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">11.1.3 3.2.1.3<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">11.2 3.2.2<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">11.2.1 3.2.2.1<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">….. …. <o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">11.13 3.2.13<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">11.14 3.2.14<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">11.14.1 3.2.14.1<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">11.14.2 3.2.14.2<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">11.14.3 3.2.14.3<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">Hope this can clarify the main difficult that I found in the document, where to place it and how.<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">Regards<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p><div><div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><span lang="EN-GB">De:</span></b><span lang="EN-GB"> Tim Hollebeek <<a href="mailto:tim.hollebeek@digicert.com">tim.hollebeek@digicert.com</a>> <br><b>Enviado el:</b> martes, 29 de agosto de 2023 16:59<br><b>Para:</b> Dimitris Zacharopoulos (HARICA) <<a href="mailto:dzacharo@harica.gr">dzacharo@harica.gr</a>>; Inigo Barreira <<a href="mailto:Inigo.Barreira@sectigo.com">Inigo.Barreira@sectigo.com</a>>; CA/B Forum Server Certificate WG Public Discussion List <<a href="mailto:servercert-wg@cabforum.org">servercert-wg@cabforum.org</a>><br><b>Asunto:</b> RE: [Servercert-wg] SC-065: Convert EVGs into RFC 3647 format pre-ballot<o:p></o:p></span></p></div></div><p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p><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;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"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p> </o:p></span></p><div><p class="MsoNormal">Yes, exactly. I would like to see a list that shows that EVG-classic section 1.4 is now in EVG-3647 section 4.1. Then I can look at where the new text landed, see how the conversion was handled, we can all verify that nothing was lost or left out, etc.<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">Without that, anyone attempting to review the document is forced to recreate the mapping just to figure out where everything went and that nothing was missed or put in the wrong place. Redlines are not sufficient when large amounts of text are moving around to different places.<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">I’m saying this because from my spot-checking, the conversion appears to be pretty good, and I’d like to be able to do a final verification that it’s mostly correct so I can endorse.<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">-Tim<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></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> Dimitris Zacharopoulos (HARICA) <<span lang="ES"><a href="mailto:dzacharo@harica.gr"><span lang="EN-US">dzacharo@harica.gr</span></a></span>> <br><b>Sent:</b> Tuesday, August 29, 2023 7:58 AM<br><b>To:</b> Inigo Barreira <<span lang="ES"><a href="mailto:Inigo.Barreira@sectigo.com"><span lang="EN-US">Inigo.Barreira@sectigo.com</span></a></span>>; CA/B Forum Server Certificate WG Public Discussion List <<span lang="ES"><a href="mailto:servercert-wg@cabforum.org"><span lang="EN-US">servercert-wg@cabforum.org</span></a></span>>; Tim Hollebeek <<span lang="ES"><a href="mailto:tim.hollebeek@digicert.com"><span lang="EN-US">tim.hollebeek@digicert.com</span></a></span>><br><b>Subject:</b> Re: [Servercert-wg] SC-065: Convert EVGs into RFC 3647 format pre-ballot<o:p></o:p></p></div></div><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal" style="margin-bottom:12.0pt">Hi Inigo,<br><br>You can take some guidance from previous successful efforts to convert existing documents into RFC 3647 format. The latest attempt was in the Code Signing BRs conversion in May 2022. Check out the mapping document and the comments in the <span lang="ES"><a href="https://lists.cabforum.org/pipermail/cscwg-public/2022-May/000795.html"><span lang="EN-US">ballot discussion period</span></a></span>.<br><br>For each existing section/paragraph, it would be nice to have a comment describing where that existing language will land in the converted document (destination). This will allow all existing text to be accounted for.<br><br>During this process, you might encounter duplicate or redundant text which needs to be flagged accordingly. You might also get into some uncertainty as to which RFC3647 section is a best fit for existing text that might require additional discussion. <br><br>I hope this helps.<br><br><br>Dimitris.<o:p></o:p></p><div><p class="MsoNormal">On 29/8/2023 12:42 μ.μ., Inigo Barreira via Servercert-wg wrote:<o:p></o:p></p></div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal"><span lang="EN-GB">Hi Tim,</span><o:p></o:p></p><p class="MsoNormal"><span lang="EN-GB"> </span><o:p></o:p></p><p class="MsoNormal"><span lang="EN-GB">See attached redlined and current versions. I just used what Martijn suggested yesterday but let me know if this is what you were looking for.</span><o:p></o:p></p><p class="MsoNormal"><span lang="EN-GB"> </span><o:p></o:p></p><p class="MsoNormal"><span lang="EN-GB">Regards</span><o:p></o:p></p><p class="MsoNormal"><span lang="EN-GB"> </span><o:p></o:p></p><div><div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b>De:</b> Tim Hollebeek <span lang="ES"><a href="mailto:tim.hollebeek@digicert.com"><span lang="EN-US"><tim.hollebeek@digicert.com></span></a></span> <br><b>Enviado el:</b> lunes, 28 de agosto de 2023 19:49<br><b>Para:</b> Inigo Barreira <span lang="ES"><a href="mailto:Inigo.Barreira@sectigo.com"><span lang="EN-US"><Inigo.Barreira@sectigo.com></span></a></span>; CA/B Forum Server Certificate WG Public Discussion List <span lang="ES"><a href="mailto:servercert-wg@cabforum.org"><span lang="EN-US"><servercert-wg@cabforum.org></span></a></span><br><b>Asunto:</b> RE: SC-065: Convert EVGs into RFC 3647 format pre-ballot<o:p></o:p></p></div></div><p class="MsoNormal"> <o:p></o:p></p><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;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.</span><o:p></o:p></p></div><p class="MsoNormal"> <o:p></o:p></p><div><p class="MsoNormal">Thanks for doing this Inigo … I know re-organizations like this are a lot of work and fall very much in the category of “important but not fun”. So thanks for taking an initial stab at this.<o:p></o:p></p><p class="MsoNormal"> <o:p></o:p></p><p class="MsoNormal">Is there a mapping that shows where all the original text ended up? I think that’s going to be essential for people to be able to review this. I did some spot checking, and your conversion looks pretty good, but I wasn’t able to do a more detailed review without a mapping.<o:p></o:p></p><p class="MsoNormal"> <o:p></o:p></p><p class="MsoNormal">-Tim<o:p></o:p></p><p class="MsoNormal"> <o:p></o:p></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> Servercert-wg <<span lang="ES"><a href="mailto:servercert-wg-bounces@cabforum.org"><span lang="EN-US">servercert-wg-bounces@cabforum.org</span></a></span>> <b>On Behalf Of </b>Inigo Barreira via Servercert-wg<br><b>Sent:</b> Monday, August 28, 2023 5:20 AM<br><b>To:</b> CA/B Forum Server Certificate WG Public Discussion List <<span lang="ES"><a href="mailto:servercert-wg@cabforum.org"><span lang="EN-US">servercert-wg@cabforum.org</span></a></span>><br><b>Subject:</b> [Servercert-wg] SC-065: Convert EVGs into RFC 3647 format pre-ballot<o:p></o:p></p></div></div><p class="MsoNormal"> <o:p></o:p></p><p class="MsoNormal">Hello,<o:p></o:p></p><p class="MsoNormal">The current Extended Validation Guidelines (EVGs) are written in a non-standardized format. For many years it has been discussed to convert this document into the RFC 3647 format and follow the standardized model for this type of documents. <o:p></o:p></p><p class="MsoNormal"> <o:p></o:p></p><p class="MsoNormal">Given that this has been known for several years, I have prepared the following ballot text, which converts the EVGs into the RFC 3647 format:<o:p></o:p></p><p class="MsoNormal"><span lang="ES"><a href="https://url.avanan.click/v2/___https:/github.com/cabforum/servercert/pull/440___.YXAzOmRpZ2ljZXJ0OmE6bzoyOGIxNWVhZGVmZDlkZTM0NjQzZTA3YTlmYTA2MzM5YTo2OmExZWM6NGZmMGEzM2U0ZWZjOTU4MTM1NWRkNjU3ZDE5YjU3Y2YxNzg1NWU0ZTVjYzkzY2NjM2M0MWU5MzEyYzJmZTQ0NzpoOkY" title="Protected by Avanan: https://github.com/cabforum/servercert/pull/440"><span lang="EN-GB">EVGs based on RFC3647 by barrini · Pull Request #440 · cabforum/servercert (github.com)</span></a></span><o:p></o:p></p><p class="MsoNormal"> <o:p></o:p></p><p class="MsoNormal">I am currently seeking two endorsers as well as any feedback on the ballot content itself (wording, effective dates, etc.).<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"> <o:p></o:p></p></div></div><p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p><pre>_______________________________________________<o:p></o:p></pre><pre>Servercert-wg mailing list<o:p></o:p></pre><pre><span lang="ES"><a href="mailto:Servercert-wg@cabforum.org"><span lang="EN-US">Servercert-wg@cabforum.org</span></a></span><o:p></o:p></pre><pre><span lang="ES"><a href="https://lists.cabforum.org/mailman/listinfo/servercert-wg"><span lang="EN-US">https://lists.cabforum.org/mailman/listinfo/servercert-wg</span></a></span><o:p></o:p></pre></blockquote><p class="MsoNormal"><o:p> </o:p></p></div></div></div></div><span>_______________________________________________</span><br><span>Servercert-wg mailing list</span><br><span>Servercert-wg@cabforum.org</span><br><span>https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.cabforum.org_mailman_listinfo_servercert-2Dwg&d=DwICAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=-bX5hBm1IdRDykQ-dBR8tsFRCM4v1VXUyG7RZa2WqPY&m=WmdTqJM_H2QE7y24jf_bhsDgho69LF2U1SUyhy0F485kRk3VyAqj1CkHFnGrMNyj&s=csiIAzK6IupOVFgFZ0n1R6yd7EHlCpWjeTgaq4hmXUc&e=</span><br></div></blockquote></body></html>