<html xmlns:v="urn:schemas-microsoft-com:vml" 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=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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]--></head><body lang=EN-US link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Acknowledged; will revert.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Note that the usage in the TLS BR is inconsistent: there are some uses of Delegated Party and delegated part as well when the sense is clearly Delegated Third Party.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks Bruce.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><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>From:</b> Bruce Morton <Bruce.Morton@entrust.com> <br><b>Sent:</b> Monday, August 22, 2022 10:44 AM<br><b>To:</b> Stephen Davidson <Stephen.Davidson@digicert.com>; SMIME Certificate Working Group <smcwg-public@cabforum.org><br><b>Subject:</b> RE: Redline of recent changes to SBR<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi Stephen,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks for the redline. The updates have improved the SBRs.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I do have a question a about changing “Delegated Third Party” to “Delegated Party”. The term “Delegated Third Party” is a CA/Browser Forum term which is used in the SSLBR, EVG, CSBR and NetSec documents. I would also assume the term has been reused in CPs, CPSs and Subscriber Agreements provided by the CAs. So why are we changing this term (using the same definition) for the SBRs? I would recommend we use common terms in our requirements which would provide consistency for CAs and Subscribers which issue/use different certificate types.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks, Bruce. <o:p></o:p></p><p class=MsoNormal><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>From:</b> Smcwg-public <<a href="mailto:smcwg-public-bounces@cabforum.org">smcwg-public-bounces@cabforum.org</a>> <b>On Behalf Of </b>Stephen Davidson via Smcwg-public<br><b>Sent:</b> Friday, August 19, 2022 1:42 PM<br><b>To:</b> <a href="mailto:smcwg-public@cabforum.org">smcwg-public@cabforum.org</a><br><b>Subject:</b> [EXTERNAL] [Smcwg-public] Redline of recent changes to SBR<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>WARNING: This email originated outside of Entrust.<br>DO NOT CLICK links or attachments unless you trust the sender and know the content is safe.<o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" align=center></div><p class=MsoNormal>Hello:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>As noted during our call this week, we have been having a pre-ballot discussion of the S/MIME Baseline Requirements (SBR) since May 2022 seeking to address issues raised by WG members with the draft text.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Our goal in that lengthy pre-ballot discussion has been to address potential issues before ballot, so that the S/MIME BR can progress through the formal balloting steps as smoothly as possible. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>A “roll up” was requested of recent changes to the draft S/MIME BR as a redline. As such, the following link shows edits made to the draft since we began our pre-ballot discussion. <o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><a href="https://urldefense.com/v3/__https:/github.com/cabforum/smime/compare/bc6881a6d6bbff1b6793a17a6b737c1b9480146b...1dc71b4a72ea93fbed010640f37bdbabe88c2591__;!!FJ-Y8qCqXTj2!Y_lGGXW_a0KEdEnPZuuF_p8iFKSjybQBNuCRNqkIJJmAxrsb3s9dipr8lDj0dX0MxOsRQty42rteKhTbAFPRQxp3CPKt$">https://github.com/cabforum/smime/compare/bc6881a6d6bbff1b6793a17a6b737c1b9480146b...1dc71b4a72ea93fbed010640f37bdbabe88c2591</a><o:p></o:p></p><p class=MsoNormal><br>Best regards, Stephen<o:p></o:p></p><p class=MsoNormal><i>Any email and files/attachments transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. If this message has been sent to you in error, you must not copy, distribute or disclose of the information it contains. <u>Please notify Entrust immediately</u> and delete the message from your system.</i> <o:p></o:p></p></div></body></html>