<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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI Emoji";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
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;
color:black;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle25
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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 bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">With our new ballot procedure, I suggest that members with ballots that are not ready (or near ready) for a vote start by publishing them as pre-ballots (as we used to do), without any start/end dates for discussion
period. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">In that way, once there has been some discussion and a final proposal is clear, the proponents can then quickly put in a 7 day formal discussion period and a 7 day voting period, like we did in the past. If
additional amendments are required, the dates can be pushed out, but that should be the exception and not the rule. That will avoid some of this confusion.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">To my mind, the new procedures allowing amendments during the formal discussion period were intended primarily to deal with unanticipated changes in a completed draft once formal discussion was launched, and
was not intended as the best way to help determine support and to draft an open-ended concept – I think pre-ballots do better for that, and avoid artificial time deadlines.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><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 style="color:windowtext">From:</span></b><span style="color:windowtext"> Public [mailto:public-bounces@cabforum.org]
<b>On Behalf Of </b>Tim Hollebeek via Public<br>
<b>Sent:</b> Monday, April 2, 2018 8:34 AM<br>
<b>To:</b> Dimitris Zacharopoulos <jimmy@it.auth.gr>; CA/Browser Forum Public Discussion List <public@cabforum.org>; Corey Bonnell <CBonnell@trustwave.com><br>
<b>Subject:</b> [EXTERNAL]Re: [cabfpub] Discussion Period to End/Voting to Begin on Ballot 219 v2: Clarify handling of CAA Record Sets with no "issue"/"issuewild" property tag<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:windowtext">Well, there’s only one previous precedent for a v2
</span><span style="font-family:"Segoe UI Emoji",sans-serif;color:windowtext">😊</span><span style="color:windowtext"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">I’d recommend that when people post a v2 (or v3, or v4 …) they update the discussion period dates and times just to make things a bit easier to track. But the bylaws don’t require it.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">The ballot is still live, and Corey can start voting at any time right now (though I commend him for giving advance notice of when voting will start, which is also recommended but not required).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">-Tim<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><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><span style="color:windowtext">From:</span></b><span style="color:windowtext"> Public [<a href="mailto:public-bounces@cabforum.org">mailto:public-bounces@cabforum.org</a>]
<b>On Behalf Of </b>Dimitris Zacharopoulos via Public<br>
<b>Sent:</b> Monday, April 2, 2018 11:06 AM<br>
<b>To:</b> Corey Bonnell <<a href="mailto:CBonnell@trustwave.com">CBonnell@trustwave.com</a>>;
<a href="mailto:public@cabforum.org">public@cabforum.org</a><br>
<b>Subject:</b> Re: [cabfpub] Discussion Period to End/Voting to Begin on Ballot 219 v2: Clarify handling of CAA Record Sets with no "issue"/"issuewild" property tag<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
Tim also mentioned (<a href="https://clicktime.symantec.com/a/1/0KHANVDFnfLVAmtz4Is4yJ_vrKLGGE3-RX-huUbo2nQ=?d=3Q5Sp5uOLsOLbJ8m2KAart5kDxz3Zclmbzwst60BF9nRh0M-Hag2Of0nzqc84gLH84NG5LByFs4nSFlyTf4HFnYaHRrAx_lv9ywqLo4o0rhpmgSFwMWdZ74-QaezgMklgAFhojgri5HbUXH6taJND1Y3YXfBNEpZ8BxLPiWedxlXHIg7xuTzjBPhqFXppR2M2Z2lYvjoCV8gillB-DbD4FCWALvSPvMX_SKs5POx05QgDX3X04Gc8aCwFl-N91p5MItNNlQPsNgdG6GVIpePyZ6IvmeniZ0WK2KmXPZz4YH1Spt-b0mrq_BSsashXNEz0i-XdmAYjQkfG64rgNcA3AwE-h1nbvAAInrSRH_TvGCfTymoUbDKDDQZN1J3dy7oKcJhIsuVIip5dPnong5l3KxWZFuwukBTPbr_LbANspHMxKxnme6yFxhr3eUjrlve8fJ-TS153-lROWf_WL4Zr5nF1Tk3UA%3D%3D&u=https%3A%2F%2Fcabforum.org%2Fpipermail%2Fpublic%2F2018-March%2F013076.html">https://cabforum.org/pipermail/public/2018-March/013076.html</a>)
that you would need to post a new version, even with no changes (this was a bit odd but it's the rules :). Your e-mail on March 14th clearly indicates a v2 but I'm having a little trouble following the discussion dates mentioned in your previous posts. On
March 14th, you indicate that the discussion period ends on March 23rd. In today's message, you indicate that the discussion period ends tomorrow (April 3rd) and then we vote. It seems a bit strange to what we've seen in the past :)<br>
<br>
<br>
Thanks,<br>
Dimitris.<o:p></o:p></p>
<div>
<p class="MsoNormal">On 2/4/2018 5:31 μμ, Corey Bonnell wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Hi Dimitris,<o:p></o:p></p>
<p class="MsoNormal">From v1.8 of the Bylaws, section 2.3.c: “The ballot automatically fails if 21 calendar days elapse since the proposer last posted a version of the ballot and the voting period has not been started.”<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I last posted a version of the ballot on March 14th (<a href="https://clicktime.symantec.com/a/1/AQ_K_GqCUHp3kQeKQ2KoZGH-_BZ1cYUSgiTrPfbMzbA=?d=3Q5Sp5uOLsOLbJ8m2KAart5kDxz3Zclmbzwst60BF9nRh0M-Hag2Of0nzqc84gLH84NG5LByFs4nSFlyTf4HFnYaHRrAx_lv9ywqLo4o0rhpmgSFwMWdZ74-QaezgMklgAFhojgri5HbUXH6taJND1Y3YXfBNEpZ8BxLPiWedxlXHIg7xuTzjBPhqFXppR2M2Z2lYvjoCV8gillB-DbD4FCWALvSPvMX_SKs5POx05QgDX3X04Gc8aCwFl-N91p5MItNNlQPsNgdG6GVIpePyZ6IvmeniZ0WK2KmXPZz4YH1Spt-b0mrq_BSsashXNEz0i-XdmAYjQkfG64rgNcA3AwE-h1nbvAAInrSRH_TvGCfTymoUbDKDDQZN1J3dy7oKcJhIsuVIip5dPnong5l3KxWZFuwukBTPbr_LbANspHMxKxnme6yFxhr3eUjrlve8fJ-TS153-lROWf_WL4Zr5nF1Tk3UA%3D%3D&u=https%3A%2F%2Fcabforum.org%2Fpipermail%2Fpublic%2F2018-March%2F013086.html">https://cabforum.org/pipermail/public/2018-March/013086.html</a>),
which is less than 21 calendar days ago. Given that, I do not believe this ballot has expired.<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">Corey<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt">From: </span></b><span style="font-size:12.0pt">Dimitris Zacharopoulos
<a href="mailto:jimmy@it.auth.gr"><jimmy@it.auth.gr></a><br>
<b>Date: </b>Monday, April 2, 2018 at 10:23 AM<br>
<b>To: </b>Corey Bonnell <a href="mailto:CBonnell@trustwave.com"><CBonnell@trustwave.com></a>, CA/Browser Forum Public Discussion List
<a href="mailto:public@cabforum.org"><public@cabforum.org></a><br>
<b>Subject: </b>Re: [cabfpub] Discussion Period to End/Voting to Begin on Ballot 219 v2: Clarify handling of CAA Record Sets with no "issue"/"issuewild" property tag</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hello Corey,<br>
<br>
I'm afraid you've passed the 21 days from first introduction and according to the Bylaws (section 2.3 c) the ballot automatically fails. I think this is actually the first time we have this situation so I would like at least another member to confirm or correct
my interpretation.<br>
<br>
If I am correct, you should pick a new ballot number and send a new ballot to start the 7-day (minimum) discussion period. If you are certain that you will not need more than 7 days for discussion, you could indicate that the voting period begins exactly after
the 7-days discussion.<br>
<br>
<br>
Best Regards,<br>
Dimitris.<o:p></o:p></p>
<div>
<p class="MsoNormal">On 2/4/2018 4:52 μμ, Corey Bonnell via Public wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Hello, <o:p></o:p></p>
<p class="MsoNormal"><a name="_MailOriginalBody">IETF 101 has transpired two weeks ago and erratum 5244 (</a><a href="https://clicktime.symantec.com/a/1/R8Ju4sLmddyXb9qhGfvNuKcDdvNv6KOVXC9piy0UZh4=?d=3Q5Sp5uOLsOLbJ8m2KAart5kDxz3Zclmbzwst60BF9nRh0M-Hag2Of0nzqc84gLH84NG5LByFs4nSFlyTf4HFnYaHRrAx_lv9ywqLo4o0rhpmgSFwMWdZ74-QaezgMklgAFhojgri5HbUXH6taJND1Y3YXfBNEpZ8BxLPiWedxlXHIg7xuTzjBPhqFXppR2M2Z2lYvjoCV8gillB-DbD4FCWALvSPvMX_SKs5POx05QgDX3X04Gc8aCwFl-N91p5MItNNlQPsNgdG6GVIpePyZ6IvmeniZ0WK2KmXPZz4YH1Spt-b0mrq_BSsashXNEz0i-XdmAYjQkfG64rgNcA3AwE-h1nbvAAInrSRH_TvGCfTymoUbDKDDQZN1J3dy7oKcJhIsuVIip5dPnong5l3KxWZFuwukBTPbr_LbANspHMxKxnme6yFxhr3eUjrlve8fJ-TS153-lROWf_WL4Zr5nF1Tk3UA%3D%3D&u=https%3A%2F%2Fscanmail.trustwave.com%2F%3Fc%3D4062%26d%3D-7zC2mLoCEj_NneVHp-V3QEqSUXMX5Za_nt1gdSZOA%26s%3D5%26u%3Dhttps%253a%252f%252fwww%252erfc-editor%252eorg%252ferrata%252feid5244">https://www.rfc-editor.org/errata/eid5244</a>)
was discussed. There is acknowledgement by the RFC 6844-bis author that the wording will be clarified in the next version of the RFC (see Jacob Hoffman-Andrews’s acknowledgement at <a href="https://clicktime.symantec.com/a/1/V9G_MYsz2vy_7h-_OQfgquhWE2XvabHHFJ-imdUR2UI=?d=3Q5Sp5uOLsOLbJ8m2KAart5kDxz3Zclmbzwst60BF9nRh0M-Hag2Of0nzqc84gLH84NG5LByFs4nSFlyTf4HFnYaHRrAx_lv9ywqLo4o0rhpmgSFwMWdZ74-QaezgMklgAFhojgri5HbUXH6taJND1Y3YXfBNEpZ8BxLPiWedxlXHIg7xuTzjBPhqFXppR2M2Z2lYvjoCV8gillB-DbD4FCWALvSPvMX_SKs5POx05QgDX3X04Gc8aCwFl-N91p5MItNNlQPsNgdG6GVIpePyZ6IvmeniZ0WK2KmXPZz4YH1Spt-b0mrq_BSsashXNEz0i-XdmAYjQkfG64rgNcA3AwE-h1nbvAAInrSRH_TvGCfTymoUbDKDDQZN1J3dy7oKcJhIsuVIip5dPnong5l3KxWZFuwukBTPbr_LbANspHMxKxnme6yFxhr3eUjrlve8fJ-TS153-lROWf_WL4Zr5nF1Tk3UA%3D%3D&u=https%3A%2F%2Fscanmail.trustwave.com%2F%3Fc%3D4062%26d%3D-7zC2mLoCEj_NneVHp-V3QEqSUXMX5Za_nkii4fEOg%26s%3D5%26u%3Dhttps%253a%252f%252fclicktime%252esymantec%252ecom%252fa%252f1%252fuUwicKB8-pbHUWekhZLLnL1-iQ4iv8xW0naYU8AFGIw%253d%253fd%253dq3oyNowL2aeaPqmICQ6FILMGQnUfIOKUv5cXNx7atOigOD%255fQT40kd5gytm1HYEMEC5lPaH7h2Z8%255frmod645WTM4RcJ0f2NjDMvKUaPdN%255fNMSYIvaHstwmn7QNVmPT8lyOMUi--ogk2eOrlGGaWrMS9A6FiBImZuZ3OPHhoEWrCgKUUWTwngjo-SM%255fS3gSUr8NNNN2zTX2c2EHeYXnHvU5FgDJofsezIeuOxr2iYXJMYqQCCKHEq-m5mX66RT-wjoereyGuNb5VjIn9QGZuB-ds1QFnrLQKdMRrxIaIiDLgSqSlkfUqIU1BzVD-AaoO8sTJlufu3%255f0hW6KIgY5aKiDcHcgZZQSZwNjiazIwVkAGQeel0RrA%253d%253d%2526u%253dhttps%253a%252f%252fwww%252eietf%252eorg%252fmail-archive%252fweb%252fspasm%252fcurrent%252fmsg01203%252ehtml"><span style="color:#954F72">https://www.ietf.org/mail-archive/web/spasm/current/msg01203.html</span></a> and
my response at <a href="https://clicktime.symantec.com/a/1/NsK23IW4slVaaxCigtv4Htb-0evw2m1Fvgdl05SjxU0=?d=3Q5Sp5uOLsOLbJ8m2KAart5kDxz3Zclmbzwst60BF9nRh0M-Hag2Of0nzqc84gLH84NG5LByFs4nSFlyTf4HFnYaHRrAx_lv9ywqLo4o0rhpmgSFwMWdZ74-QaezgMklgAFhojgri5HbUXH6taJND1Y3YXfBNEpZ8BxLPiWedxlXHIg7xuTzjBPhqFXppR2M2Z2lYvjoCV8gillB-DbD4FCWALvSPvMX_SKs5POx05QgDX3X04Gc8aCwFl-N91p5MItNNlQPsNgdG6GVIpePyZ6IvmeniZ0WK2KmXPZz4YH1Spt-b0mrq_BSsashXNEz0i-XdmAYjQkfG64rgNcA3AwE-h1nbvAAInrSRH_TvGCfTymoUbDKDDQZN1J3dy7oKcJhIsuVIip5dPnong5l3KxWZFuwukBTPbr_LbANspHMxKxnme6yFxhr3eUjrlve8fJ-TS153-lROWf_WL4Zr5nF1Tk3UA%3D%3D&u=https%3A%2F%2Fscanmail.trustwave.com%2F%3Fc%3D4062%26d%3D-7zC2mLoCEj_NneVHp-V3QEqSUXMX5Za_n1w0YWfYQ%26s%3D5%26u%3Dhttps%253a%252f%252fclicktime%252esymantec%252ecom%252fa%252f1%252f8ZBAp3FOCf908ne78Zhxwn40HD9hrc0H9QE-w1fF6oI%253d%253fd%253dq3oyNowL2aeaPqmICQ6FILMGQnUfIOKUv5cXNx7atOigOD%255fQT40kd5gytm1HYEMEC5lPaH7h2Z8%255frmod645WTM4RcJ0f2NjDMvKUaPdN%255fNMSYIvaHstwmn7QNVmPT8lyOMUi--ogk2eOrlGGaWrMS9A6FiBImZuZ3OPHhoEWrCgKUUWTwngjo-SM%255fS3gSUr8NNNN2zTX2c2EHeYXnHvU5FgDJofsezIeuOxr2iYXJMYqQCCKHEq-m5mX66RT-wjoereyGuNb5VjIn9QGZuB-ds1QFnrLQKdMRrxIaIiDLgSqSlkfUqIU1BzVD-AaoO8sTJlufu3%255f0hW6KIgY5aKiDcHcgZZQSZwNjiazIwVkAGQeel0RrA%253d%253d%2526u%253dhttps%253a%252f%252fwww%252eietf%252eorg%252fmail-archive%252fweb%252fspasm%252fcurrent%252fmsg01206%252ehtml"><span style="color:#954F72">https://www.ietf.org/mail-archive/web/spasm/current/msg01206.html</span></a>).
However, there is still no indication that the erratum state will change to “Held for Document Update” or “Approved” anytime soon.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">We believe that the acknowledgement from the RFC author to fix this in the next version of the RFC is a sufficient surrogate to getting the erratum state changed. Waiting for the erratum state to change is merely red-tape in the process.
As such, we intend to proceed with the ballot in its current form by closing the Discussion Period on Ballot 219 and begin voting tomorrow evening (UTC time).
<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">Corey<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">Ballot 219 v2: Clarify handling of CAA Record Sets with no "issue"/"issuewild" property tag</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">Purpose of this ballot:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">RFC 6844 contains an ambiguity in regard to the correct processing of a non-empty CAA Resource Record Set that does not contain any issue property tag (and also does not contain any issuewild
property tag in the case of a Wildcard Domain Name). It is ambiguous if a CA must not issue when such a CAA Resource Record Set is encountered, or if such a Resource Record Set is implicit permission to issue.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">Given that the intent of the RFC is clear (such a CAA Resource Record Set is implicit permission to issue), we are proposing the following change to allow for CAA processing consistent with
the intent of the RFC.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">The following motion has been proposed by Corey Bonnell of Trustwave and endorsed by Tim Hollebeek of Digicert and Mads Egil Henriksveen of Buypass.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">-- MOTION BEGINS --</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">This ballot modifies the “Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates” as follows, based upon Version 1.5.6:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">In section 3.2.2.8, add this sentence:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">CAs MAY treat a non-empty CAA Resource Record Set that does not contain any issue property tags (and also does not contain any issuewild property tags when performing CAA processing for
a Wildcard Domain Name) as permission to issue, provided that no records in the CAA Resource Record Set otherwise prohibit issuance.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">to the end of this paragraph:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">When processing CAA records, CAs MUST process the issue, issuewild, and iodef property tags as specified in RFC 6844, although they are not required to act on the contents of the iodef property
tag. Additional property tags MAY be supported, but MUST NOT conflict with or supersede the mandatory property tags set out in this document. CAs MUST respect the critical flag and not issue a certificate if they encounter an unrecognized property with this
flag set.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">-- MOTION ENDS –</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
<p class="MsoNormal">The procedure for approval of this ballot is as follows:<o:p></o:p></p>
<p class="MsoNormal">Discussion (7+ days) <o:p></o:p></p>
<p class="MsoNormal"> Start Time: 2018-03-07 19:00:00 UTC <o:p></o:p></p>
<p class="MsoNormal"> End Time: 2018-04-03 19:00:00 UTC<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Vote for approval (7 days) <o:p></o:p></p>
<p class="MsoNormal"> Start Time: 2018-04-03 19:00:00 UTC<o:p></o:p></p>
<p class="MsoNormal"> End Time: 2018-04-10 19:00:00 UTC<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal"><b><span style="font-size:10.5pt;font-family:"Arial",sans-serif;color:#428FC5">Corey Bonnell</span></b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Arial",sans-serif;color:gray">Senior Software Engineer</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Arial",sans-serif;color:gray">t: +1 412.395.2233</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt"> </span><o:p></o:p></p>
</div>
<p class="MsoNormal"><b><span style="font-size:10.5pt;font-family:"Arial",sans-serif;color:#428FC5">Trustwave</span></b><b><span style="font-size:10.5pt;font-family:"Arial",sans-serif;color:gray"> </span></b><span style="font-size:10.5pt;font-family:"Arial",sans-serif;color:gray">| SMART
SECURITY ON DEMAND</span><a href="https://clicktime.symantec.com/a/1/F0LdSZyhFOYiwqsh48BGmF39HEqX0IHb_XSPKMr4NDk=?d=3Q5Sp5uOLsOLbJ8m2KAart5kDxz3Zclmbzwst60BF9nRh0M-Hag2Of0nzqc84gLH84NG5LByFs4nSFlyTf4HFnYaHRrAx_lv9ywqLo4o0rhpmgSFwMWdZ74-QaezgMklgAFhojgri5HbUXH6taJND1Y3YXfBNEpZ8BxLPiWedxlXHIg7xuTzjBPhqFXppR2M2Z2lYvjoCV8gillB-DbD4FCWALvSPvMX_SKs5POx05QgDX3X04Gc8aCwFl-N91p5MItNNlQPsNgdG6GVIpePyZ6IvmeniZ0WK2KmXPZz4YH1Spt-b0mrq_BSsashXNEz0i-XdmAYjQkfG64rgNcA3AwE-h1nbvAAInrSRH_TvGCfTymoUbDKDDQZN1J3dy7oKcJhIsuVIip5dPnong5l3KxWZFuwukBTPbr_LbANspHMxKxnme6yFxhr3eUjrlve8fJ-TS153-lROWf_WL4Zr5nF1Tk3UA%3D%3D&u=http%3A%2F%2Fwww.trustwave.com%2F"><span style="font-size:10.5pt;font-family:"Arial",sans-serif;color:gray;text-decoration:none"><br>
www.trustwave.com</span></a><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Public mailing list<o:p></o:p></pre>
<pre><a href="mailto:Public@cabforum.org">Public@cabforum.org</a><o:p></o:p></pre>
<pre><a href="https://clicktime.symantec.com/a/1/T2_yE0PCrhdIhlP3KFoISDGD69z_QmKpqXKeOL_XNyw=?d=3Q5Sp5uOLsOLbJ8m2KAart5kDxz3Zclmbzwst60BF9nRh0M-Hag2Of0nzqc84gLH84NG5LByFs4nSFlyTf4HFnYaHRrAx_lv9ywqLo4o0rhpmgSFwMWdZ74-QaezgMklgAFhojgri5HbUXH6taJND1Y3YXfBNEpZ8BxLPiWedxlXHIg7xuTzjBPhqFXppR2M2Z2lYvjoCV8gillB-DbD4FCWALvSPvMX_SKs5POx05QgDX3X04Gc8aCwFl-N91p5MItNNlQPsNgdG6GVIpePyZ6IvmeniZ0WK2KmXPZz4YH1Spt-b0mrq_BSsashXNEz0i-XdmAYjQkfG64rgNcA3AwE-h1nbvAAInrSRH_TvGCfTymoUbDKDDQZN1J3dy7oKcJhIsuVIip5dPnong5l3KxWZFuwukBTPbr_LbANspHMxKxnme6yFxhr3eUjrlve8fJ-TS153-lROWf_WL4Zr5nF1Tk3UA%3D%3D&u=https%3A%2F%2Fscanmail.trustwave.com%2F%3Fc%3D4062%26d%3D-7zC2mLoCEj_NneVHp-V3QEqSUXMX5Za_ihz19TKaQ%26s%3D5%26u%3Dhttps%253a%252f%252fcabforum%252eorg%252fmailman%252flistinfo%252fpublic">https://cabforum.org/mailman/listinfo/public</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<o:p></o:p></p>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>