<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 16px; font-family: Calibri, sans-serif; color: rgb(0, 0, 0);">
<div style="color: rgb(0, 0, 0);">
<div>DT members: Thanks for looking at this in advance of our Wednesday working session. </div>
<div><br>
</div>
<div>In the attached, I pasted the ISPCP points sent by Wolf-Ulrich via eat email below. And I added BC’s discussion points. (both in red, on pages 2-5.</div>
<div><br>
</div>
<div>Glad to have others enter their points in the attached doc, or just send as email text and I will insert. </div>
<div><br>
</div>
<div>—Steve</div>
<div><br>
</div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE"></div>
</div>
</div>
<div style="color: rgb(0, 0, 0);"><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div 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">
<div bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<div style="color: rgb(0, 0, 0);">
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; color: windowtext;">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; color: windowtext;">
<a href="mailto:gnso-bylaws-dt-bounces@icann.org">gnso-bylaws-dt-bounces@icann.org</a> [<a href="mailto:gnso-bylaws-dt-bounces@icann.org">mailto:gnso-bylaws-dt-bounces@icann.org</a>]
<b>On Behalf Of </b>Wolf-Ulrich Knoben<br>
<b>Sent:</b> Monday, March 13, 2017 5:41 AM<br>
<b>To:</b> <a href="mailto:gnso-bylaws-dt@icann.org">gnso-bylaws-dt@icann.org</a><br>
<b>Subject:</b> Re: [Gnso-bylaws-dt] For your review - Staff Report Bylaws & GNSO Operating Procedures Proposed Revisions & Legal Review<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="color: rgb(0, 0, 0);"><o:p> </o:p></p>
<p style="color: rgb(0, 0, 0);">Steve and all,<o:p></o:p></p>
<p style="color: rgb(0, 0, 0);">some short answers/comments:<o:p></o:p></p>
<p><font color="#ff0000">IN 1: yes<o:p></o:p></font></p>
<p><font color="#ff0000">IN 5: yes<o:p></o:p></font></p>
<p><font color="#ff0000">IN 15: yes, it should be documented. But Board member selection is done on
<u>house</u> level, not SG.<o:p></o:p></font></p>
<p><font color="#ff0000">IN 37: Is this drafting team the right body to address this (I mean from its composition point of view)? Or shouldn't these procedural items been elaborated by the GNSO RT which took over similar tasks from the SCI? Who's the addressee
of a petition in this context? A petition in principle could be filed from anyone within the GNSO community. Criteria should be developed with respect to the specific character of a petition in order to avoid that it just circumvents the GNSO's working process.<o:p></o:p></font></p>
<p><font color="#ff0000">IN 44-46: Maybe a kind of "PDP" (Petition Development Process): Raising an issue, preleminary evaluation by (legal?) staff, council decision...<o:p></o:p></font></p>
<p><font color="#ff0000">IN 45 (3/4 threshold): I tend to leave this decision with the body which appointed the board member (house). On the other hand each board member is accountable to the entire (SO?) community. This should be taken into consideration as
well.</font></p>
<div style="color: rgb(0, 0, 0);">
<p class="MsoNormal">Am 11.03.2017 um 17:07 schrieb Steve DelBianco:<o:p></o:p></p>
</div>
<blockquote style="color: rgb(0, 0, 0); margin-top: 5pt; margin-bottom: 5pt;">
<div>
<div>
<p class="MsoNormal">Thanks, Marika. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">When we completed our DT report late last year, we did promise to stay engaged and answer questions like these. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal">So our first step is for <u>each of us</u> to read the draft and think about how to answer the 8 “Questions Identified” in column B, pages 1-4 of our attached doc. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If we can each draft some rough answers to your questions, that would be a great setup for the meeting.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From: </b><<a href="mailto:gnso-bylaws-dt-bounces@icann.org">gnso-bylaws-dt-bounces@icann.org</a>> on behalf of Marika Konings <<a href="mailto:marika.konings@icann.org">marika.konings@icann.org</a>><br>
<b>Date: </b>Monday, March 6, 2017 at 3:13 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] For your review - Staff Report Bylaws & GNSO Operating Procedures Proposed Revisions & Legal Review<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family: 'Times New Roman', serif;"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Dear Bylaws Drafting Team,</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">As you will recall, on 1 December 2016, the GNSO Council directed ‘ICANN Policy Staff to draft proposed language for any necessary modifications or additions to the GNSO Operating Procedures and, if applicable,
those parts of the ICANN Bylaws pertaining to the GNSO. The GNSO Council requests that ICANN Legal evaluate whether the proposed modifications are consistent with the post-transition Bylaws and report their findings to the GNSO Council’. In the analysis of
the DT recommendations, staff took a minimalist approach by focusing on the minimum changes needed to implement the DT recommendations.</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">However, in undertaking this work, staff did identify a number of questions and made a number of assumptions that it is requesting the DTs input on before this document and the revised ICANN Bylaws and GNSO
Operating Procedures are published for public comment. You will find these questions and assumptions outlined in the attached document (in pdf and word version). To facilitate your review, the main questions have been flagged in the table contained in the
executive summary. </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">We realise that there may be little time for you to review this document ahead of ICANN58 but we hope you are available to join us for the session that has been scheduled on Wednesday 15 March from 17.00 –
18.30 local time (see <a href="http://sched.co/9nqV">http://sched.co/9nqV</a> for further details). This session is intended to walk you through our questions and assumptions as well as answer any questions you may have. The DT can also discuss how to proceed
following ICANN58 to develop its input on these questions and assumptions which will then allow staff to finalise the documents for publication for public comment.</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">We look forward to receiving your feedback.</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">Best regards,</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">Marika</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">Marika Konings</span></i></b><o:p></o:p></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) </span></i><o:p></o:p></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">Email: <a href="mailto:marika.konings@icann.org">
marika.konings@icann.org</a> </span></i><o:p></o:p></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt"> </span></i><o:p></o:p></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">Follow the GNSO via Twitter @ICANN_GNSO</span></i><o:p></o:p></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">Find out more about the GNSO by taking our <a href="http://learn.icann.org/courses/gnso">interactive courses</a> and visiting the <a href="http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers">GNSO
Newcomer pages</a>. </span></i><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><span style="font-family: 'Times New Roman', serif;"><br>
<br>
<br>
<o:p></o:p></span></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Gnso-bylaws-dt mailing list<o:p></o:p></pre>
<pre><a href="mailto:Gnso-bylaws-dt@icann.org">Gnso-bylaws-dt@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/gnso-bylaws-dt">https://mm.icann.org/mailman/listinfo/gnso-bylaws-dt</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal" style="color: rgb(0, 0, 0);"><span style="font-family: 'Times New Roman', serif;"><br>
<br>
<o:p></o:p></span></p>
<pre style="color: rgb(0, 0, 0);">-- <o:p></o:p></pre>
<pre style="color: rgb(0, 0, 0);"><o:p> </o:p></pre>
<pre style="color: rgb(0, 0, 0);">Am Steinringer Berg 19<o:p></o:p></pre>
<pre style="color: rgb(0, 0, 0);">53639 Königswinter<o:p></o:p></pre>
<pre style="color: rgb(0, 0, 0);">Tel: 02244 873999<o:p></o:p></pre>
<pre style="color: rgb(0, 0, 0);">Fax: 02244 873955<o:p></o:p></pre>
<pre style="color: rgb(0, 0, 0);">Mob: 0151 1452 5867<o:p></o:p></pre>
</div>
</div>
</div>
</span><style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 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";
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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Calibri","sans-serif";
color:black;}
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.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas","serif";
color:black;}
span.EmailStyle21
{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>
</body>
</html>