<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Support these suggested edits. Thanks Darcy.</p>
<p>Matthew<br>
</p>
<br>
<div class="moz-cite-prefix">On 12/10/2016 06:50, Darcy Southwell
wrote:<br>
</div>
<blockquote
cite="mid:F45FBB8C-249C-475A-89C7-DBE2D37C89D3@endurance.com"
type="cite">
<meta name="Title" content="">
<meta name="Keywords" content="">
<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;}
@font-face
{font-family:Candara;
panose-1:2 14 5 2 3 3 3 2 2 4;}
@font-face
{font-family:TimesNewRomanPSMT;}
@font-face
{font-family:TimesNewRomanPS;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
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:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Candara;
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.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:1136138703;
mso-list-template-ids:-1788175146;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:Candara">A few thoughts
I have, and I’m sorry I didn’t have the opportunity to share
them earlier during everyone else’s commentary.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:Candara"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:Candara">On page 1, we
call out “Strong support but significant opposition” about
Council speaking for the GNSO, but we don’t do the same for
the rest of the recommendations. I second Amr’s suggestion
that we call out consensus level for each of our four
recommendations. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:Candara"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:Candara">Regarding item
2 from below, I recommend a bit of a language change shown
in red below to more accurately reflect that this is an
opinion of certain DT members:<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:Candara"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black">“DT members from the
Commercial Stakeholders Group said Council should not decide
non-policy matters, since ICANN Bylaws say Council is
“responsible for managing the policy development process of
the GNSO,” </span><span
style="font-family:Calibri;color:red">and it is their
position that this language <s> This </s></span><span
style="font-family:Calibri;color:black">implies that Council
is limited to policy and that GNSO Stakeholder Groups and
Constituencies should handle other matters. <span
style="background:yellow;mso-highlight:yellow">On the
other hand, some DT members noted that there is no
provision in the Bylaws for any group, be it Council or
the GNSO Stakeholder Groups and Constituencies, to assume
these new powers and that there is currently no procedure
for GNSO Stakeholder Groups to handle these matters.</span>”<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:Candara"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:Candara">Regarding the
yellow highlighting above, I remember our discussions on
this a bit differently. I may be confusing it with another
discussion since the “some DT members” language doesn’t
indicate which of us we’re discussing, but I think many DT
members said that the “responsible for managing the policy
development process of the GNSO” language doesn’t prohibit
Council from working on non-policy matters. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:Candara"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:Candara">Do we have any
feedback from David Maher to these various drafts/emails? <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:Candara"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:Candara">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:Candara">Darcy<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:Candara"><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="font-family:Calibri;color:black">From: </span></b><span
style="font-family:Calibri;color:black"><a class="moz-txt-link-rfc2396E" href="mailto:gnso-bylaws-dt-bounces@icann.org"><gnso-bylaws-dt-bounces@icann.org></a>
on behalf of Steve DelBianco
<a class="moz-txt-link-rfc2396E" href="mailto:sdelbianco@netchoice.org"><sdelbianco@netchoice.org></a><br>
<b>Date: </b>Tuesday, October 11, 2016 at 4:01 PM<br>
<b>To: </b>matthew shears <a class="moz-txt-link-rfc2396E" href="mailto:mshears@cdt.org"><mshears@cdt.org></a>, Amr
Elsadr <a class="moz-txt-link-rfc2396E" href="mailto:aelsadr@egyptig.org"><aelsadr@egyptig.org></a>, WUKnoben
<a class="moz-txt-link-rfc2396E" href="mailto:wolf-ulrich.knoben@t-online.de"><wolf-ulrich.knoben@t-online.de></a>,
<a class="moz-txt-link-rfc2396E" href="mailto:gnso-bylaws-dt@icann.org">"gnso-bylaws-dt@icann.org"</a>
<a class="moz-txt-link-rfc2396E" href="mailto:gnso-bylaws-dt@icann.org"><gnso-bylaws-dt@icann.org></a><br>
<b>Subject: </b>[Gnso-bylaws-dt] Another LAST CALL on
revised DT report<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black">In the interest
of getting this done, I offer the attached revised
report, with these changes:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black">1. Made the page
1 edit proposed by Wolf-Ulrich in response to Amr, and
added level of consensus, as requested by Amr. It now
reads:<o:p></o:p></span></p>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-family:Calibri">Note:
Three DT members (IPC, ISPCP, and BC) do not support
Council exercising any of the new powers by voting
within the present House-bound structure. The
recommendation that Council would speak for GNSO
therefore has “Strong support but significant
opposition”. Nonetheless, all DT members contributed to
consensus recommendations for voting thresholds on the
assumption that GNSO Council would approve nominations
and actions created under the new ICANN Bylaws. </span>
<o:p></o:p></p>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black"> <o:p></o:p></span></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black"><o:p> </o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black">2. On page 4 we
follow Matthew’s request to shorten the “not sustainable”
point while retaining Amr's added counter-arguments. It
now reads: <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black"><o:p> </o:p></span></p>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<p class="MsoNormal"><span
style="font-family:Calibri;color:black">DT members from
the Commercial Stakeholders Group said Council should not
decide non-policy matters, since ICANN Bylaws say Council
is “responsible for managing the policy development
process of the GNSO”. This implies that Council is
limited to policy and that GNSO Stakeholder Groups and
Constituencies should handle other matters. On the other
hand, some DT members noted that there is no provision in
the Bylaws for any group, be it Council or the GNSO
Stakeholder Groups and Constituencies, to assume these new
powers and that there is currently no procedure for GNSO
Stakeholder Groups to handle these matters.<o:p></o:p></span></p>
</blockquote>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black">For those of you
counting words and looking for balance, that paragraph is
now 49 words for each point of view! <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black">So, are we good to
go??? Please reply by 12 UTC on Wednesday 12-Oct.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black">—Steve<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black"><o:p> </o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-family:Calibri;color:black">From: </span></b><span
style="font-family:Calibri;color:black"><<a
moz-do-not-send="true"
href="mailto:gnso-bylaws-dt-bounces@icann.org">gnso-bylaws-dt-bounces@icann.org</a>>
on behalf of Matthew Shears <<a moz-do-not-send="true"
href="mailto:mshears@cdt.org">mshears@cdt.org</a>><br>
<b>Date: </b>Tuesday, October 11, 2016 at 5:36 PM<br>
<b>To: </b>Amr Elsadr <<a moz-do-not-send="true"
href="mailto:aelsadr@egyptig.org">aelsadr@egyptig.org</a>>,
WUKnoben <<a moz-do-not-send="true"
href="mailto:wolf-ulrich.knoben@t-online.de">wolf-ulrich.knoben@t-online.de</a>><br>
<b>Cc: </b>"<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>
<b>Subject: </b>Re: [Gnso-bylaws-dt] Correction<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black">Hi Amr - I
believe that I suggested more or less the same. The <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black">repetition of
the same perspective is unfortunate particularly as it
is <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black">made very
explicit up front and in the recommendations section.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black">Matthew<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black">On 11/10/2016
21:04, Amr Elsadr wrote:<o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF
4.5pt;padding:0in 0in 0in
4.0pt;margin-left:3.75pt;margin-right:0in"
id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black">Hi,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black">Speaking for
myself, I have noted over previous versions of the
report that it seemed biased towards the minority
view, which is a bit odd. Perhaps less so now, but it
does seem to me to still be the case. For one thing, I
suggested taking out redundant text that repeats the
same point in multiple parts of the report.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black">This is on
page 3:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black">“Some DT
members noted that the Bylaws describe the role of
GNSO Council to be “responsible for managing the
policy development process of the GNSO,” which does
not cover the non-policy decisions related to exercise
of powers of the Empowered Community."<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black">And this is on
page 4:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black">"Some DT
members noted that it was not sustainable for Council
to continue taking positions on non-policy matters,
since the ICANN Bylaws designate Council as
“responsible for managing the policy development
process of the GNSO”. This could imply that Council
is limited to policy matters and that GNSO Stakeholder
Groups and Constituencies should handle other
matters.”<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black">I really don’t
understand why they both need to be in the report on
two separate pages, when they pretty much say the
exact same thing. I already asked for the section on
page 4 to be removed. Is there a reason that I am
missing to explain it wasn’t?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black">Thanks.<o:p></o:p></span></p>
</div>
</blockquote>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:Calibri">From: </span></b><span
style="font-family:Calibri">Steve DelBianco <<a
moz-do-not-send="true"
href="mailto:sdelbianco@netchoice.org">sdelbianco@netchoice.org</a>><br>
<b>Date: </b>Tuesday, October 11, 2016 at 5:21 PM<br>
<b>To: </b>Amr Elsadr <<a moz-do-not-send="true"
href="mailto:aelsadr@egyptig.org">aelsadr@egyptig.org</a>><br>
<b>Cc: </b>"<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>
<b>Subject: </b>Re: [Gnso-bylaws-dt] LAST CALL: GNSO
Bylaws DT report and matrix -- final version for DT
approval<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal">Amr — <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Good point about Consensus level,
and I thought a lot about that. GNSO Working Group
Guidelines (<a moz-do-not-send="true"
href="https://gnso.icann.org/en/council/annex-1-gnso-wg-guidelines-01sep16-en.pdf">link</a>),
at Section 3.6, suggests two possible designations for
our recommendations:<o:p></o:p></p>
</div>
<div>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<div>
<p class="MsoNormal"><b>Consensus</b> - a position
where only a small minority disagrees, but most
agree.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span
style="font-family:Symbol">·</span></b><b>
Strong support but significant oppositio</b>n -
a position where, while most of the group supports
a recommendation, there are a significant number
of those who do not support it.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</blockquote>
<div>
<p class="MsoNormal">I’d say we had <b>Strong support
but significant opposition</b> on the <u>Who</u> and <u>How</u> questions
described in the Evolution section of our report.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">And for the recommendations on
pages 1-2, I’d say we had <b>Consensus</b> — but
qualified by the abstention of CSG reps. <o:p></o:p></p>
</div>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
<div>
<div>
<p class="MsoNormal">As to whether we drop any
discussion of how the DT came to its recommendation,
that’s against the GNSO Working Group Guidelines (<a
moz-do-not-send="true"
href="https://gnso.icann.org/en/council/annex-1-gnso-wg-guidelines-01sep16-en.pdf">link</a>).
Specifically:<o:p></o:p></p>
</div>
<div>
<div>
<div>
<div>
<p
style="margin-left:.5in;text-indent:-.25in;mso-list:l0
level1 lfo1"><!--[if !supportLists]--><span
style="mso-list:Ignore">1.<span
style="font:7.0pt "Times New
Roman""> </span></span><!--[endif]--><span
style="font-family:TimesNewRomanPSMT">In
cases of </span><b><span
style="font-family:"TimesNewRomanPS","serif"">Consensus</span></b><span
style="font-family:TimesNewRomanPSMT">, </span><b><span
style="font-family:"TimesNewRomanPS","serif"">Strong
support but significant opposition</span></b><span
style="font-family:TimesNewRomanPSMT">, and </span><b><span
style="font-family:"TimesNewRomanPS","serif"">No
Consensus</span></b><span
style="font-family:TimesNewRomanPSMT">, an
effort should be made to document that
variance in viewpoint and to present any </span><b><span
style="font-family:"TimesNewRomanPS","serif"">Minority
View </span></b><span
style="font-family:TimesNewRomanPSMT">recommendations
that may have been made. Documentation of </span><b><span
style="font-family:"TimesNewRomanPS","serif"">Minority
View </span></b><span
style="font-family:TimesNewRomanPSMT">recommendations
normally depends on text offered by the
proponent(s). In all cases of </span><b><span
style="font-family:"TimesNewRomanPS","serif"">Divergence, </span></b><span
style="font-family:TimesNewRomanPSMT">the WG
Chair should encourage the submission of
minority viewpoint(s). </span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div>
<blockquote style="border:none;border-left:solid #B5C4DF
4.5pt;padding:0in 0in 0in
4.0pt;margin-left:3.75pt;margin-right:0in"
id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<p class="MsoNormal"><span
style="font-family:Calibri;color:black"><o:p> </o:p></span></p>
</div>
</blockquote>
</div>
<p class="MsoNormal">_______________________________________________
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><o:p></o:p></p>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
--------------
Matthew Shears
Global Internet Policy and Human Rights
Center for Democracy & Technology (CDT)
+ 44 771 2472987</pre>
</body>
</html>