<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:"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;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
h3
{mso-style-priority:9;
mso-style-link:"Heading 3 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:13.5pt;
font-family:"Calibri",sans-serif;}
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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
span.Heading3Char
{mso-style-name:"Heading 3 Char";
mso-style-priority:9;
mso-style-link:"Heading 3";
font-family:"Calibri",sans-serif;
font-weight:bold;}
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.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.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle28
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle29
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle30
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle31
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle32
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle33
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle34
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle36
{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;}
/* List Definitions */
@list l0
{mso-list-id:25329397;
mso-list-template-ids:-2024372214;}
@list l0:level1
{mso-level-start-at:4;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:242379810;
mso-list-template-ids:903123708;}
@list l2
{mso-list-id:1021857319;
mso-list-template-ids:549747298;}
@list l2:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3
{mso-list-id:1185752120;
mso-list-template-ids:1752181058;}
@list l4
{mso-list-id:1629971097;
mso-list-template-ids:-1019307480;}
@list l4:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5
{mso-list-id:1805001828;
mso-list-template-ids:-1282394670;}
@list l5:level1
{mso-level-start-at:3;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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">
<div class="WordSection1">
<p class="MsoNormal">Dear Julie and Ariel, <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I agree with Heather – thank you for following up on this important question.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Pragmatically, as I see it, if the ccNSO and GNSO vote by supermajority for an SIFR then it will happen, following on from those votes.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">But as I recall the inquiry here was purposefully specific – who actually ‘initiates’ the SIFR? (Unfortunately, the word ‘initiated’ in bylaw 18.12(a) (on Special IFRs) is not the word used elsewhere in important parts of Bylaw 18 (on IANA
Naming Function Reviews)). <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">On that question I agree with Samantha. The ccNSO and GNSO “approve” the SIFR – as per Bylaw 18.12(a)(iv) – and the Board then shall “cause … [an SIFR] to be carried out” – as per Bylaw 18.1.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">One reliable English-language dictionary, Merriam-Webster, defines ‘initiate’ as:
<b><span style="letter-spacing:.15pt;background:white">to cause or facilitate the beginning of</span>
</b></span><span style="letter-spacing:.15pt;background:white">- </span><a href="https://www.merriam-webster.com/dictionary/initiate">https://www.merriam-webster.com/dictionary/initiate</a>.<span style="font-size:11.0pt;letter-spacing:.15pt;background:white"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">So, it appears to me that the Board technically initiates an SIFR by causing the SIFR to be carried out.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">To me, this makes it very important that our procedure include an affirmative obligation for both Councils to (probably jointly) pass on to the Board the results of GNSO and ccNSO votes in this respect - the
votes are not self-executing starts to an SIFR.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Best wishes,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">David</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">David McAuley<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Sr International Policy & Business Development Manager<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Verisign Inc.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">703-948-4154<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt"><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="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> Gnso-bylaws-dt <gnso-bylaws-dt-bounces@icann.org>
<b>On Behalf Of </b>Julie Hedlund<br>
<b>Sent:</b> Thursday, July 11, 2019 5:12 PM<br>
<b>To:</b> gnso-bylaws-dt@icann.org<br>
<b>Subject:</b> [EXTERNAL] [Gnso-bylaws-dt] Response from ICANN Legal Concerning Initiation of a Special IFR<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Dear all,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Per action item 1 below from the meeting on 10 July, please see the following response from Sam Eisner at ICANN Legal concerning whether the ccNSO and GNSO can initiate a Special IFR. It appears from this
response that it is the votes of the ccNSO and GNSO to initiate the Special IFR (assuming the Bylaws requirements of 18.12(a) (i)-(iv) are met), that obligate the Board to make sure the Special IFR goes forward. While this appears to confirm the DT’s assumption,
staff is interested in your thoughts concerning the response.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Kind regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Julie & Ariel<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">------------------------------------------------<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">From Samantha Eisner, ICANN Legal:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">The Special IFR can only be initiated once the requirements laid out at 18.12(a) (i)- (iv) have been satisfied. Among those requirements are supermajority support at the GNSO council and ccNSO
Council levels, after consideration of the resolution of the PTI Performance Issue. In this case, it’s the completion of the votes that tells the Board it’s time for a Special IFR, instead of the running of a five-year calendar period that tells the Board
it’s time for a Periodic IFR.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">If the requirements of 18.12(a) are met and the Special IFR is voted to be initiated, then 18.1 obligates the Board to make sure that the Special IFR goes forward and adheres to all other Bylaws
requirements. With that, the Board’s oversight role would include making sure that the org is proceeding with calls to the community to compose the IFRT and supporting the appointing entities in their process, as well as providing all other appropriate support
for the Special IFR to proceed. </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Hope this is helpful.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Sam</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:black">From: </span></b><span style="color:black">Gnso-bylaws-dt <<a href="mailto:gnso-bylaws-dt-bounces@icann.org">gnso-bylaws-dt-bounces@icann.org</a>> on behalf of Julie Hedlund <<a href="mailto:julie.hedlund@icann.org">julie.hedlund@icann.org</a>><br>
<b>Date: </b>Thursday, July 11, 2019 at 4:59 PM<br>
<b>To: </b>"<a href="mailto:gnso-bylaws-dt@icann.org">gnso-bylaws-dt@icann.org</a>" <<a href="mailto:gnso-bylaws-dt@icann.org">gnso-bylaws-dt@icann.org</a>><br>
<b>Subject: </b>[Gnso-bylaws-dt] Actions & Notes: GNSO Drafting Team Meeting 10 July 21:00 UTC<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal">Dear all,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="color:black">Please see below the action items</span> and notes<span style="color:black"> captured by staff from the<span class="apple-converted-space"> </span>GNSO Drafting Team meeting held on<span class="apple-converted-space"> </span></span>10
July <span style="color:black">2019<span class="apple-converted-space"> </span>(21:00-22:00 UTC). Staff have posted
</span>these <span style="color:black">to the wiki space. <b><i>Please note that these<span class="apple-converted-space"> </span>are<span class="apple-converted-space"> </span>high-level notes and are not meant as a substitute for the recording, chat room,
or transcript</i></b><i>.</i> The recording, AC chat,<span class="apple-converted-space"> </span>transcript<span class="apple-converted-space"> </span>and attendance records are posted on the wiki</span><span class="apple-converted-space"> at:
<a href="https://community.icann.org/pages/viewpage.action?pageId=111387729">https://community.icann.org/pages/viewpage.action?pageId=111387729</a>.
</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Please note that all versions of the guidelines may be found on the wiki at:
<a href="https://community.icann.org/display/GBIDT/Templates+and+Guidelines+Depository">
https://community.icann.org/display/GBIDT/Templates+and+Guidelines+Depository</a>.
<o:p></o:p></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black">Best Regards,</span><o:p></o:p></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black">Julie</span><o:p></o:p></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black">Julie Hedlund, Policy Director</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><b>Actions Items:</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="mso-list:l4 level1 lfo3"><u>Joint ccNSO/GNSO Initiation of a Special IFR</u>: Staff will check on the status of questions to ICANN Legal, specifically on whether the GNSO and ccNSO can jointed initiate a Special IFR. (DONE – see
response in separate message.)<o:p></o:p></li><li class="MsoNormal" style="mso-list:l4 level1 lfo3"><u>Section 1.3 Approval Action Community Forum</u>: Staff will accept the grammatical edits in the document from Heather Forrest and generate a new version with the flagged issues/comments called out for
DT consideration (see below), including a timeline for the GNSO Council actions. (DONE – see documents for review in separate message.)<o:p></o:p></li><li class="MsoNormal" style="mso-list:l4 level1 lfo3"><u>Preparation for 24 July Meeting</u>: Staff will circulate for DT review the draft of Section 2.2 Petition Process for Specified Actions and Section 2.3 Rejection Action Community Forum. (DONE – see documents
for review in separate message.)<o:p></o:p></li></ol>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Notes:</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">1. Updates to Statements of Interest (SOIs): None provided.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">2. Section 18.12 Special IFRs -- Brief Update re: 15 July joint GRC/DT meeting on Guidelines for GNSO-ccNSO Consultation on Initiating a Special IFR:<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1ol8461abkOqzXSahZKkuLL-2D7GxDWklmA0wnK1CKwfgY_edit-3Fusp-3Dsharing&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=adDIs0WEx_lLwFfrsdovxTYY8GkRHo5ibc8SR3Npdh8&m=RfYmWnCQSyLL0EsBnWmD6gb5eu50atShEcYcuw1NcLg&s=aQxrVGGlnlFIhJqK6BXgA3NWGE0zel27UR03KM5AROE&e=">https://docs.google.com/document/d/1ol8461abkOqzXSahZKkuLL-7GxDWklmA0wnK1CKwfgY/edit?usp=sharing
[docs.google.com]</a><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">-- What do we expect from the meeting on 15 July and how do we move forward? Could the GRC be satisfied from the call on Monday, or would there be additional deliberations? <o:p></o:p></p>
<p class="MsoNormal">-- Expectation that it is a matter of clarification and coming to a common understanding of the questions. The GRC and DT can finish their documents and they would have two common approaches.<o:p></o:p></p>
<p class="MsoNormal"><b> </b><o:p></o:p></p>
<p class="MsoNormal"><b>ACTION ITEM:</b> <b>Staff will check on the status of questions to ICANN Legal, particularly as to whether the GNSO and ccNSO can jointly initiate a Special IFR.</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">3. Discussion/Edits re: Section 1.3 Approval Action Community Forum:
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1tR6YeATOl-2D-5F6ig7XKKluR3jwY8cLPYKoLCB-2Dt6GhVNc_edit-3Fusp-3Dsharing&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=adDIs0WEx_lLwFfrsdovxTYY8GkRHo5ibc8SR3Npdh8&m=sbkfLm_KS_6kkvPCW33WPWzEqKV0o0RQ_pxSldlvwrw&s=b2S5eYTIFBKQ9F6ZQVRjv1LGZuYnfgHf-hFZ_XSd5uU&e=">
https://docs.google.com/document/d/1tR6YeATOl-_6ig7XKKluR3jwY8cLPYKoLCB-t6GhVNc/edit?usp=sharing </a><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">-- Staff and David McCauley noted that there is a real-time example of the anticipated use of the Approval Action Community Forum to consider the ccNSO’s request for a Fundamental Bylaws Amendment regarding the IANA Naming Function Review
Team's Composition. See: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2Dcomments_bylaws-2Damend-2Diana-2Dnaming-2Dfunction-2D2019-2D06-2D10-2Den&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=adDIs0WEx_lLwFfrsdovxTYY8GkRHo5ibc8SR3Npdh8&m=5VHwARxTSP3PsyJJ-5TsXhC-aJ7h8NXUJdIjfi89Kpg&s=Yb4Kf5QFfGYTcUVHIKbC6T3MT0aMgQq4CKR8jzUp-lg&e=">
https://www.icann.org/public-comments/bylaws-amend-iana-naming-function-2019-06-10-en [icann.org]</a>. <o:p></o:p></p>
<p class="MsoNormal">-- Staff also noted that the EC Administration has accordingly requested, per the Bylaws, that an Approval Action Community Forum should be scheduled to take place during ICANN66 in Montreal.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Edits/Comments for DT Consideration in the Google Doc (as called out in the revised version dated 11 July):<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo6">Noting that although the current representative to the EC Administration is the GNSO Council Chair, there is nothing to prevent the GNSO Council from choosing a different person as
its representative. Thus, it is suggested that references to the GNSO Council Chair in the document should be changed to GNSO Representative to the EC Administration (see page 4 and onward). Maxim Alzoba also inserted a comment relating to this issue, so
we request that he should review this suggested edit. <o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo6">4.3.1 Consultation Mechanism:
<o:p></o:p>
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level2 lfo6">Change “If such a consultation is scheduled” to “If such a consultation occurs”.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level2 lfo6">In response to a point made by David McCauley about ensuring that the GNSO Council can meet the decision deadline of 21 days as specified in the Bylaws, add to the last sentence, “and
in no event later than the 21-day Approval Action Decision Period per Section 1.4 Annex D of the Bylaws.”<o:p></o:p></li></ol>
</li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo6">4.3.2 GNSO Council Decision and Informing the EC Administration:
<o:p></o:p>
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level2 lfo6">The DT discussed how to ensure that the GNSO Council’s actions to decide on whether to support, object to, or abstain from the Approval Action are completed within the above-mentioned
21-day period. Staff suggested adding a timeline showing the timing of the activities. In addition, staff has added the excerpt from the Bylaws with the relevant details.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level2 lfo6">On 11 July Wolf-Ulrich Knoben suggested edits to combine sections 4.3.2 and 4.3.3 into one section. Staff has included those edits in the version dated 11 July.<o:p></o:p></li></ol>
</li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo6">Staff also accepted all of the grammatical changes provided by Heather Forrest.<o:p></o:p></li></ol>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>ACTION ITEM: Staff will accept the grammatical edits in the document from Heather Forrest and generate a new version with the flagged issues/comments called out for DT consideration, including a timeline for the GNSO Council actions.</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">4. Next Meeting: 24 July: The DT will finalize its review of Section 1.3, and begin review of Section 2.2 Petition Process for Specified Actions and Section 2.3 Rejection Action Community Forum.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>ACTION ITEM: Staff will circulate for DT review the draft of Section 2.2 Petition Process for Specified Actions and Section 2.3 Rejection Action Community Forum. </b>
<o:p></o:p></p>
</div>
</body>
</html>