<div dir="ltr"><div>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Aptos",sans-serif">Hi all,<span></span></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Aptos",sans-serif">I am currently aligned with Wendy’s and Judith’s concerns
expressed on the recent call about sunsetting the Legacy profile, but I look
forward to discussing this further in Bergamo. The Legacy profile provides greater
flexibility, and migrating to only the Multipurpose and Strict profiles may
have unforeseen consequences. While no one else has explicitly stated they are
not ready for this move, the Mozilla Root Program has integrated the S/MIME BRs
into our root store policy, necessitating support for diverse use cases while
ensuring broad compliance. We need to ensure that everyone not
involved in the S/MIME WG is prepared for such a significant move, and we might find out about problems when it is too late to address them. For instance, we could see compliance issues in Bugzilla from CA operators who are currently enabled with the email trust
bit, or we might receive a root inclusion request from a CA operator unwilling or unable
to restrict issuance to only strict or multipurpose certificates.</p><p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Aptos",sans-serif">In summary,
I'd just like to understand the issues better and
minimize disruption and compliance
issues down the road. </p><p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Aptos",sans-serif">I look forward to your thoughts and suggestions.</p><p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Aptos",sans-serif">Thanks,</p><p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Aptos",sans-serif">Ben<br></p><p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Aptos",sans-serif"><span></span></p></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 11, 2024 at 8:40 AM Stephen Davidson via Smcwg-public <<a href="mailto:smcwg-public@cabforum.org" target="_blank">smcwg-public@cabforum.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<div lang="EN-US">
<div>
<p class="MsoNormal">Hello all:<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I attach the summary that we reviewed in the SMCWG call yesterday.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">It highlights the differences between the Legacy generation profiles and the Multipurpose/Strict profiles, including links to the relevant text sections in the S/MIME BR.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><a href="https://cabforum.org/posts/2024/2024-04-10-legacy-deprecation/SMCWG_20240410_Final.pdf" target="_blank">https://cabforum.org/posts/2024/2024-04-10-legacy-deprecation/SMCWG_20240410_Final.pdf</a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">This should facilitate review and feedback to help the SMCWG determine appropriate steps and timelines to migrate to the Multipurpose/Strict profiles.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Regards, Stephen<u></u><u></u></p>
</div>
</div>
_______________________________________________<br>
Smcwg-public mailing list<br>
<a href="mailto:Smcwg-public@cabforum.org" target="_blank">Smcwg-public@cabforum.org</a><br>
<a href="https://lists.cabforum.org/mailman/listinfo/smcwg-public" rel="noreferrer" target="_blank">https://lists.cabforum.org/mailman/listinfo/smcwg-public</a><br>
</div></blockquote></div>