<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi Antti,<div><div><br><blockquote type="cite"><div>On Apr 8, 2024, at 10:52 PM, Backman, Antti <antti.backman@teliacompany.com> wrote:</div><br class="Apple-interchange-newline"><div><meta charset="UTF-8"><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">Hi Clint<o:p></o:p></span></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">When reviewing the text I got wonder about couple of fairly minor things within section 3.1.1, specifically following sections / language:<span class="Apple-converted-space"> </span><o:p></o:p></span></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">3.1.1.1, 3.1.1.2 and 3.1.2.1,<span class="Apple-converted-space"> </span><o:p></o:p></span></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">Should we use the name for TLS BR as it is written in the BR document front page “Baseline Requirements for the Issuance and Management of Publicly-Trusted TLS Server Certificates”? I would think the name reference is ambiguous as how it is now written in the text, due to the fact that we have S/MIME BR, how would you see this.<span class="Apple-converted-space"> </span></span></div></div></div></blockquote><div><br></div><div>Great catch, I’ve updated these three instances to state "Baseline Requirements for the Issuance and Management of Publicly-Trusted TLS Server Certificates” instead of "Baseline Requirements for the Issuance and Management of Publicly‐Trusted Certificates”.</div><br><blockquote type="cite"><div><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p></o:p></span></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;">Then in regards to the links in the same sections to the TLS BR-document, is it an official practice to make direct reference to the Github for the BRs? I’ve understood that the published versions of the BRs are considered the official version of the documents, thus should be used as reference point in the language? I guess this is more for the clarity how such links should be prepared and embedded in to the CA/B governed documents and to understand that how stakeholders should treat the different copies of the same documentation published by CA/B.<span class="Apple-converted-space"> </span></span></div></div></div></blockquote><div><br></div><div>I don’t believe there’s an official practice related to this. The EVGs don’t seem to include a link at all, rather just the section number and document title (<a href="https://github.com/cabforum/servercert/blob/main/docs/EVG.md#72-by-the-applicant">https://github.com/cabforum/servercert/blob/main/docs/EVG.md#72-by-the-applicant</a>). The SBRs do include a link to the specific section being referenced (<a href="https://github.com/cabforum/smime/blob/main/SBR.md#3221-validating-authority-over-mailbox-via-domain">https://github.com/cabforum/smime/blob/main/SBR.md#3221-validating-authority-over-mailbox-via-domain</a>). Of the two methods of linking between documents, my personal preference is the SBR approach, but I’m not particularly opposed to removing the links or updating them if others feel strongly. For the moment, I’ve left them as-is.</div><div><br></div><div>I’ll push these changes later today, after the NSWG call in case there’s further discussion.</div><div><br></div><div>Cheers!</div><div>-Clint</div><br><blockquote type="cite"><div><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p></o:p></span></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span lang="EN-US" style="font-size: 11pt;">//Antti</span><span style="font-size: 11pt;"><o:p></o:p></span></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 11pt;"><o:p> </o:p></span></div><div id="mail-editor-reference-message-container"><div><div style="border-width: 1pt medium medium; border-style: solid none none; border-color: rgb(181, 196, 223) currentcolor currentcolor; border-image: none; padding: 3pt 0cm 0cm;"><p class="MsoNormal" style="margin: 0cm 0cm 12pt; font-size: 12pt; font-family: Aptos, sans-serif;"><b><span style="">From:<span class="Apple-converted-space"> </span></span></b><span style="">Netsec <<a href="mailto:netsec-bounces@cabforum.org" style="color: blue; text-decoration: underline;">netsec-bounces@cabforum.org</a>> on behalf of Clint Wilson via Netsec <<a href="mailto:netsec@cabforum.org" style="color: blue; text-decoration: underline;">netsec@cabforum.org</a>><br><b>Date:<span class="Apple-converted-space"> </span></b>Monday, 8. April 2024 at 23.15<br><b>To:<span class="Apple-converted-space"> </span></b>NetSec CA/BF <<a href="mailto:netsec@cabforum.org" style="color: blue; text-decoration: underline;">netsec@cabforum.org</a>><br><b>Subject:<span class="Apple-converted-space"> </span></b>[cabf_netsec] Updated Draft NS-003: Restructure NCSSRs<o:p></o:p></span></p></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;">Hi all,<o:p></o:p></div><div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><o:p> </o:p></div></div><div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;">I’ve pushed an update for NS-003 to address feedback received and add the effective date discussed at last meeting. I have a few questions outstanding that I'd appreciate feedback on.<o:p></o:p></div></div><div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><o:p> </o:p></div></div><div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;">1. The effective date is currently set to 15 October 2024. I don’t think this is quite the correct date, but would 15 November 2024 or 15 January 2025 be more appropriate?<o:p></o:p></div></div><div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><o:p> </o:p></div></div><div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;">I’ve placed language at the top of the Requirements stating that 1) until the effective date, either the version of the NCSSRs represented by this draft or Version 1.7 of the NCSSRs must be followed and 2) as of the effective date, this draft version of the NCSSRs must be followed.<o:p></o:p></div></div><div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><o:p> </o:p></div></div><div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;">2. Is this the correct location for this language?<o:p></o:p></div></div><div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;">3. Is this the correct language to convey this future effective data?<o:p></o:p></div></div><div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;">4. Does this language work well for a future update to section 4?<o:p></o:p></div></div><div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><o:p> </o:p></div></div><div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;">The updated draft can be found here: <a href="https://github.com/cabforum/netsec/compare/offline-hsms" style="color: blue; text-decoration: underline;">https://github.com/cabforum/netsec/compare/offline-hsms</a><o:p></o:p></div></div><div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;">Latest commit:<span class="Apple-converted-space"> </span><a href="https://github.com/cabforum/netsec/commit/251ac72ab8389e93018945a41f31779dae51aa5c" style="color: blue; text-decoration: underline;">https://github.com/cabforum/netsec/commit/251ac72ab8389e93018945a41f31779dae51aa5c</a><o:p></o:p></div></div><div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;">Comparison between main and commit:<span class="Apple-converted-space"> </span><a href="https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...251ac72ab8389e93018945a41f31779dae51aa5c" style="color: blue; text-decoration: underline;">https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...251ac72ab8389e93018945a41f31779dae51aa5c</a><o:p></o:p></div></div><div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;">Comparison between prior major commit (Oct 2023) and latest commit:<span class="Apple-converted-space"> </span><a href="https://github.com/cabforum/netsec/compare/0d34f4ab148439130e28d4fa8128af7385fc21d3...251ac72ab8389e93018945a41f31779dae51aa5c" style="color: blue; text-decoration: underline;">https://github.com/cabforum/netsec/compare/0d34f4ab148439130e28d4fa8128af7385fc21d3...251ac72ab8389e93018945a41f31779dae51aa5c</a><o:p></o:p></div></div><div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><o:p> </o:p></div></div><div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;">Thanks all!<o:p></o:p></div></div><div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;">-Clint</div></div></div></div></div></div></blockquote></div><br></div></body></html>