<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;}
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.Heading3Char
{mso-style-name:"Heading 3 Char";
mso-style-priority:9;
mso-style-link:"Heading 3";
font-family:"Calibri",sans-serif;
font-weight:bold;}
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-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">
<div class="WordSection1">
<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">This is a reminder of the action item for consideration and approval by DT members. See details below.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><i><span style="font-size:11.0pt">If there are no objections received in
<u>one week</u> by <u>COB Thursday, 11 April</u> the document will be considered as approved by the Drafting Team. If there are any objections to provisions in the document DT member(s) with objections are requested to propose text to resolve them.</span></i></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Thank you very much for your consideration.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">With best regards,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Julie<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 <gnso-bylaws-dt-bounces@icann.org> on behalf of Julie Hedlund <julie.hedlund@icann.org><br>
<b>Date: </b>Thursday, March 28, 2019 at 6:08 PM<br>
<b>To: </b>"gnso-bylaws-dt@icann.org" <gnso-bylaws-dt@icann.org><br>
<b>Subject: </b>[Gnso-bylaws-dt] FOR APPROVAL BY COB 11 APRIL 2019: Guidelines and Motion Templates 4.2 Community IRP & 4.3 IRP for Covered ICANN Actions<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"><span style="font-size:11.0pt">Dear all,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Per the action items below, please review the attached final version of the Guidelines and Motion Templates for Sections 4.2 Community IRP and 4.3 IPR for Covered ICANN Actions. This document reflects the
accepted edits previously reviewed, as well as the revision requested at the meeting on 27 March to question 10 of the Reconsideration Request to separate the question into 10a and 10b asking for names and contact information of multiple entities.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><b><i><span style="font-size:11.0pt">If there are no objections received in
<u>two weeks</u> by <u>COB Thursday, 11 April</u> the document will be considered as approved by the Drafting Team. If there are any objections to provisions in the document DT member(s) with objections are requested to propose text to resolve them.</span></i></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Thank you very much for your consideration.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">With best regards,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Julie</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Julie Hedlund, Policy Director</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><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="color:black">From: </span></b><span style="color:black">Gnso-bylaws-dt <gnso-bylaws-dt-bounces@icann.org> on behalf of Julie Hedlund <julie.hedlund@icann.org><br>
<b>Date: </b>Thursday, March 28, 2019 at 5:55 PM<br>
<b>To: </b>"gnso-bylaws-dt@icann.org" <gnso-bylaws-dt@icann.org><br>
<b>Subject: </b>[Gnso-bylaws-dt] Actions & Notes: GNSO Drafting Team Meeting 27 March 21:00 UTC</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></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 and notes captured by staff from the<span class="apple-converted-space"> </span>GNSO Drafting Team meeting held on<span class="apple-converted-space"> </span></span>27 March
<span style="color:black">2019<span class="apple-converted-space"> </span>(21:00-22:00 UTC). Staff have posted to the wiki space the action items and notes. <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 class="apple-converted-space"> </span>at:<span class="apple-converted-space"> </span></span><span class="apple-converted-space"><a href="https://community.icann.org/pages/viewpage.action?pageId=105383460">https://community.icann.org/pages/viewpage.action?pageId=105383460</a>.
</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"> </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 & NOTES:</b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><b>Actions:</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>ACTION ITEM re: Timeline</b> -- Heather will communicate the timeline to the GNSO Council leadership
<i>(DONE 27 March by Heather – final is attached)</i><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>ACTION ITEMS re: Sections 4.2 and 4.3 Guidelines and Templates</b><o:p></o:p></p>
<p class="MsoNormal">1. Staff will revise question 10 -- break into 10(a) and 10(b) asking for names and contact information of multiple entities.
<i>(DONE 28 March by staff and attached in Word and PDF)</i><o:p></o:p></p>
<p class="MsoNormal">2. Send for review to the list as a last call in 2 weeks, asking for objections but if someone objects to a provision they should propose text.
<i>(DONE 28 March by staff)</i><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>ACTION ITEMS re: Section 18.12 Special IFRs </b><o:p></o:p></p>
<p class="MsoNormal"><u>1. GNSO Input Process</u>: DT members should review the GIP and in the context of the initiation of a Special IFR on the IANA function. See questions below. The GIP is at:
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_council_annex-2D3-2Dinput-2Dprocess-2Dmanual-2D18jun18-2Den.pdf&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=adDIs0WEx_lLwFfrsdovxTYY8GkRHo5ibc8SR3Npdh8&m=VTAJdtLMkvUT9bfmr7KeEF99S4rkchPeXPMyJLuYuLY&s=VyZKr_fwCqgVrYp_SmkIy1OR9bF6i8s6NPV47i2xs7M&e=">
https://gnso.icann.org/en/council/annex-3-input-process-manual-18jun18-en.pdf [gnso.icann.org]</a> and attached in Word and PDF. <i>(FOR DISCUSSION ON 10 APRIL – INPUT TO THE LIST PRIOR IS APPRECIATED)</i><o:p></o:p></p>
<p class="MsoNormal">-- Is it useful, is anything missing -- a gap analysis. Should help to identify any GNSO-specific items. If we do need something else suggest what that could be.<o:p></o:p></p>
<p class="MsoNormal">-- Can we focus on just how to coordinate on just the consultation process. How formal do we need to be with that consultation process? Could be informal during development, but more formal for approval which you can enter into via the
respective chairs.<o:p></o:p></p>
<p class="MsoNormal"><u>2. Coordination with the ccNSO Guidelines Review Committee:
</u><o:p></o:p></p>
<p class="MsoNormal">-- Staff is checking with ccNSO support staff on timing. <i>
(ONGOING)</i><o:p></o:p></p>
<p class="MsoNormal">-- David McAuley will check with Katrina Sataki, ccNSO Chair.
<i>(ONGOING)</i><o:p></o:p></p>
<p class="MsoNormal">-- DT members should think about what needs to be documented such as timing, consultation, and how to make a final joint decision.
<i>(FOR DISCUSSION ON 10 APRIL – INPUT TO THE LIST PRIOR IS APPRECIATED)</i><o:p></o:p></p>
<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): No updates provided.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">2. Review and approval of Draft Timeline:<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">-- Discussion on 18.12 Special IFRs will include a need to coordinate with the ccNSO.<o:p></o:p></p>
<p class="MsoNormal">-- Three-call rotation to complete/approve documents.<o:p></o:p></p>
<p class="MsoNormal">-- Substantive work done by end of May.<o:p></o:p></p>
<p class="MsoNormal">-- Package would go to the Council in time for the June document deadline (16 June). Suggest putting this on the agenda as a discussion item.<o:p></o:p></p>
<p class="MsoNormal">-- One of us to attend the June meeting (Heather volunteers).<o:p></o:p></p>
<p class="MsoNormal">-- Gives the time to go back to SGs and Cs.<o:p></o:p></p>
<p class="MsoNormal">-- Proposed vote in the July GNSO Council meeting.<o:p></o:p></p>
<p class="MsoNormal"><b>ACTION ITEM: Heather will communicate the timeline to the GNSO Council leadership.</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">3. Review and Discuss Revised Draft of Guidelines/Templates for Sections 4.2 and 4.3:<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">-- Page 7, Question 10: on whether we can ask if you are bringing this Reconsideration Request on behalf -- insert a 10a include the names/contact on whose behalf you are bringing this request.<o:p></o:p></p>
<p class="MsoNormal">-- Question 6, re: Question 10 -- could we identify others in this question? The responses to the questions are slightly different.<o:p></o:p></p>
<p class="MsoNormal">-- If people disagree that you are bringing the claim on behalf of them then the claim is invalid. ICANN should confirm.<o:p></o:p></p>
<p class="MsoNormal">-- What if it can't be verified? This would be so rare I don't think we have to anticipate that this would happen.<o:p></o:p></p>
<p class="MsoNormal">-- Question 10 asked if you are bringing it on behalf of multiple entities, but we haven't asked if it is on behalf of a single entity. If there is even one more the question would be accurate.<o:p></o:p></p>
<p class="MsoNormal">-- Informal feedback to staff: the form is not as clear as it could be. Once we've used it more in practice it might be further improved.<o:p></o:p></p>
<p class="MsoNormal">-- A single entity can represent multiple entities.<o:p></o:p></p>
<p class="MsoNormal"><b>ACTION ITEMS: </b><o:p></o:p></p>
<p class="MsoNormal"><b>1. Revise question 10 -- break into 10(a) and 10(b) asking for names and contact information of multiple entities.</b><o:p></o:p></p>
<p class="MsoNormal"><b>2. Send for review to the list as a last call in 2 weeks, asking for objections but if someone objects to a provision they should propose text.</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">4. Review and Discuss Approach for Guidelines for 18.12 Special IANA Naming Function Reviews (IFRs):<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">-- Bringing an IFR outside of the IFR process (a "Special IFR" and only in two instances.<o:p></o:p></p>
<p class="MsoNormal">-- Where a remedial action has already taken place but has not resolved the problem.<o:p></o:p></p>
<p class="MsoNormal">-- These are very limited circumstances.<o:p></o:p></p>
<p class="MsoNormal">-- The GIP GIP is proposed, but as a suggestion for the DT to consider. There might be other options, such as a small group within the Council, for example, or a drafting team.<o:p></o:p></p>
<p class="MsoNormal">-- Consider not reinventing the wheel.<o:p></o:p></p>
<p class="MsoNormal">-- Might require additional time, but perhaps allow for consultation with experts, research, etc.<o:p></o:p></p>
<p class="MsoNormal">-- Might be necessary given the IANA function.<o:p></o:p></p>
<p class="MsoNormal">-- ccNSO Guidelines Review Committee: May need a bit more time than in the GNSO.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>ACTION ITEMS: </b><o:p></o:p></p>
<p class="MsoNormal"><b>1. GNSO Input Process: The DT member review the GIP and in the context of the initiation of a Special IFR on the IANA function. Staff will provide a link to the document. Is it useful, is anything missing -- a gap analysis. Should
help to identify any GNSO-specific items. If we do need something else suggest what that could be.</b><o:p></o:p></p>
<p class="MsoNormal"><b>-- Can we focus on just how to coordinate on just the consultation process. How formal do we need to be with that consultation process? Could be informal during development, but more formal for approval -- which you can enter into
via the respective chairs.</b><o:p></o:p></p>
<p class="MsoNormal"><b>2. Coordination with the ccNSO Guidelines Review Committee.
</b><o:p></o:p></p>
<p class="MsoNormal"><b>-- Staff is checking with ccNSO support staff on timing.
</b><o:p></o:p></p>
<p class="MsoNormal"><b>-- David McAuley will check with Katrina Sataki, ccNSO Chair.
</b><o:p></o:p></p>
<p class="MsoNormal"><b>-- DT members should think about what needs to be documented such as timing, consultation, and how to make a final joint decision.</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">6. AOB: Next meeting Wednesday, 10 April 2019 at 21:00 UTC.<o:p></o:p></p>
</div>
</body>
</html>