<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Steve and all,</p>
<p>some short answers/comments:</p>
<p>IN 1: yes</p>
<p>IN 5: yes</p>
<p>IN 15: yes, it should be documented. But Board member selection
is done on <u>house</u> level, not SG.</p>
<p>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.</p>
<p>IN 44-46: Maybe a kind of "PDP" (Petition Development Process):
Raising an issue, preleminary evaluation by (legal?) staff,
council decision...</p>
<p>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.</p>
<p>Best regards</p>
<p>Wolf-Ulrich</p>
<p><br>
</p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">Am 11.03.2017 um 17:07 schrieb Steve
DelBianco:<br>
</div>
<blockquote
cite="mid:CBD05BFA-2B68-4512-A42E-B44A7A557BDF@netchoice.org"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div>
<div>Thanks, Marika. </div>
<div><br>
</div>
<div>When we completed our DT report late last year, we did
promise to stay engaged and answer questions like these. </div>
<div><br>
</div>
<div>
<div>
<div>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. </div>
<div><br>
</div>
<div>If we can each draft some rough answers to your
questions, that would be a great setup for the meeting.</div>
<div><br>
</div>
<div>
</div>
</div>
<div><br>
</div>
</div>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:12pt;
text-align:left; color:black; BORDER-BOTTOM: medium none;
BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT:
0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;
BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span><<a
moz-do-not-send="true"
href="mailto:gnso-bylaws-dt-bounces@icann.org">gnso-bylaws-dt-bounces@icann.org</a>>
on behalf of Marika Konings <<a moz-do-not-send="true"
href="mailto:marika.konings@icann.org">marika.konings@icann.org</a>><br>
<span style="font-weight:bold">Date: </span>Monday, March 6,
2017 at 3:13 PM<br>
<span style="font-weight:bold">To: </span>"<a
moz-do-not-send="true"
href="mailto:gnso-bylaws-dt@icann.org">gnso-bylaws-dt@icann.org</a>"
<<a moz-do-not-send="true"
href="mailto:gnso-bylaws-dt@icann.org">gnso-bylaws-dt@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>[Gnso-bylaws-dt]
For your review - Staff Report Bylaws & GNSO Operating
Procedures Proposed Revisions & Legal Review<br>
</div>
<div><br>
</div>
<div 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">
<meta name="Title" content="">
<meta name="Keywords" content="">
<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;}
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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:Calibri;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
<div bgcolor="white" link="#0563C1" vlink="#954F72"
lang="EN-US">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Dear
Bylaws Drafting Team,<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">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.<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">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. <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">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 moz-do-not-send="true"
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.<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">We
look forward to receiving your feedback.<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
regards,<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">Marika<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">Marika
Konings<o:p></o:p></span></i></b></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) <o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">Email:
<a moz-do-not-send="true"
href="mailto:marika.konings@icann.org">
<span style="color:#0563C1">marika.konings@icann.org</span></a> <o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt"> <o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">Follow
the GNSO via Twitter @ICANN_GNSO<o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">Find
out more about the GNSO by taking our <a
moz-do-not-send="true"
href="http://learn.icann.org/courses/gnso"><span
style="color:#0563C1">interactive courses</span></a> and
visiting the <a moz-do-not-send="true"
href="http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers"><span
style="color:#0563C1">GNSO Newcomer pages</span></a>. <o:p></o:p></span></i></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</span>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gnso-bylaws-dt mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gnso-bylaws-dt@icann.org">Gnso-bylaws-dt@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-bylaws-dt">https://mm.icann.org/mailman/listinfo/gnso-bylaws-dt</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Am Steinringer Berg 19
53639 Königswinter
Tel: 02244 873999
Fax: 02244 873955
Mob: 0151 1452 5867</pre>
</body>
</html>