<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font face="Calibri">me too</font><br>
</p>
<br>
<div class="moz-cite-prefix">Il 21/06/2017 15:36, Rich Smith via
Public ha scritto:<br>
</div>
<blockquote type="cite"
cite="mid:1b5501d2ea93$63d2fef0$2b78fcd0$@comodo.com">
<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:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@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:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@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]-->
<div class="WordSection1">
<p class="MsoNormal">If I’m not mistaken, Gerv is saying, rather
than update a bunch of text in other places, how about
changing the name back to <i>Baseline Requirements for the
Issuance and Management of Publicly-Trusted Certificates</i>.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Gerv, if that is correct, I second the
motion.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">-Rich<o:p></o:p></p>
<p class="MsoNormal"><a name="_MailEndCompose"
moz-do-not-send="true"><o:p> </o:p></a></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<p class="MsoNormal"><b>From:</b> Public
[<a class="moz-txt-link-freetext" href="mailto:public-bounces@cabforum.org">mailto:public-bounces@cabforum.org</a>] <b>On Behalf Of </b>Ryan
Sleevi via Public<br>
<b>Sent:</b> Wednesday, June 21, 2017 7:26 AM<br>
<b>To:</b> Gervase Markham <a class="moz-txt-link-rfc2396E" href="mailto:gerv@mozilla.org"><gerv@mozilla.org></a><br>
<b>Cc:</b> Ryan Sleevi <a class="moz-txt-link-rfc2396E" href="mailto:sleevi@google.com"><sleevi@google.com></a>; CA/Browser
Forum Public Discussion List <a class="moz-txt-link-rfc2396E" href="mailto:public@cabforum.org"><public@cabforum.org></a><br>
<b>Subject:</b> Re: [cabfpub] Baseline Requirements
"Certificate Policy" for the Issuance and Management of
Publicly-Trusted Certificates<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">On Wed, Jun 21, 2017 at 8:23 AM, Gervase
Markham <<a href="mailto:gerv@mozilla.org" target="_blank"
moz-do-not-send="true">gerv@mozilla.org</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC
1.0pt;padding:0in 0in 0in
6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">On 21/06/17 13:56, <span
style="font-family:"MS Gothic"">陳立群</span> via
Public wrote:<br>
> *Baseline Requirements: *The Baseline Requirements for
the Issuance and<br>
> Management of Publicly-Trusted Certificates as<br>
> published by the CA/Browser Forum and any amendments to
such document.<br>
><br>
> To<br>
><br>
> *Baseline Requirements: *The Baseline Requirements
Certificate Policyfor<br>
> the Issuance and Management of Publicly-Trusted
Certificates as<br>
> published by the CA/Browser Forum and any amendments to
such document.<br>
<br>
I realise it's important for this document to have a single
name, but do<br>
we really have to fix the problem by making what is already
a very long<br>
name even longer?<br>
<br>
If we are going to ballot a new name and update everything
to match,<br>
let's take the opportunity to make it shorter.<br>
<br>
Gerv<o:p></o:p></p>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">I believe you may have misunderstood. We
updated the name in 1.3.0, but not the text in Section 2.2 <o:p></o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Public mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Public@cabforum.org">Public@cabforum.org</a>
<a class="moz-txt-link-freetext" href="https://cabforum.org/mailman/listinfo/public">https://cabforum.org/mailman/listinfo/public</a>
</pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<p style="font-family: Serif">
Cordiali saluti,<br>
<br>
Adriano Santoni<br>
ACTALIS S.p.A.<br>
(Aruba Group)</p>
</div>
</body>
</html>