ICANN ICANN Email List Archives

[gnso-ppsc-pdp]


<<< Chronological Index >>>    <<< Thread Index >>>

RE: [gnso-ppsc-pdp] Questions / comments - the meaning of "act"

  • To: "Marika Konings" <marika.konings@xxxxxxxxx>
  • Subject: RE: [gnso-ppsc-pdp] Questions / comments - the meaning of "act"
  • From: "James M. Bladel" <jbladel@xxxxxxxxxxx>
  • Date: Mon, 21 Feb 2011 13:07:23 -0700

<html><body><span style="font-family:Arial; color:#000000; 
font-size:10pt;"><div>At risk of blowing up this list, may I ask which version 
went 
out?</div><div><br></div><div>:)</div><div><br></div><div>J.</div><div><br></div>
<blockquote id="replyBlockquote" webmail="1" style="border-left: 2px solid 
blue; margin-left: 8px; padding-left: 8px; font-size: 10pt; color: black; 
font-family: verdana;">
<div id="wmQuoteWrapper">
-------- Original Message --------<br>
Subject: Re: [gnso-ppsc-pdp] Questions / comments - the meaning of<br>
"act"<br>
From: Marika Konings &lt;<a 
href="mailto:marika.konings@xxxxxxxxx";>marika.konings@xxxxxxxxx</a>&gt;<br>
Date: Mon, February 21, 2011 2:02 pm<br>
To: "Neuman, Jeff" &lt;<a 
href="http://Jeff.Neuman@xxxxxxxxxx&gt";>Jeff.Neuman@xxxxxxxxxx&gt</a>;, Avri 
Doria &lt;avri@xxxxxxx&gt;,<br>
       "<a href="mailto:Gnso-ppsc-pdp@xxxxxxxxx";>Gnso-ppsc-pdp@xxxxxxxxx</a>" 
&lt;<a href="mailto:gnso-ppsc-pdp@xxxxxxxxx";>gnso-ppsc-pdp@xxxxxxxxx</a>&gt;<br>
<br>
<br>
Apologies, but I have already submitted the report for publication, so no<br>
further changes are possible.<br>
<br>
Marika<br>
<br>
On 21/02/11 20:58, "Neuman, Jeff" &lt;<a 
href="http://Jeff.Neuman@xxxxxxxxxx&gt";>Jeff.Neuman@xxxxxxxxxx&gt</a>; 
wrote:<br>
<br>
&gt;<br>
&gt;Avri,<br>
&gt;<br>
&gt;The wording you have used prejudges that the bylaws allow something to 
be<br>
&gt;declared consensus policies with only a majority, which is arguably more<br>
&gt;prejudicial.  If it is not too late, I would be fine with a factual<br>
&gt;statement such that just recites what the provision states:<br>
&gt;<br>
&gt;"In any case in which the Council is not able to reach GNSO 
Supermajority<br>
&gt;vote, a majority vote of the Board will be sufficient to act."<br>
&gt;<br>
&gt;I understand your passion for this issue, but remember that those on the<br>
&gt;other side are just as passionate.<br>
&gt;<br>
&gt;Jeffrey J. Neuman <br>
&gt;Neustar, Inc. / Vice President, Law &amp; Policy<br>
&gt;<br>
&gt;<br>
&gt;The information contained in this e-mail message is intended only for 
the<br>
&gt;use of the recipient(s) named above and may contain confidential and/or<br>
&gt;privileged information. If you are not the intended recipient you have<br>
&gt;received this e-mail message in error and any review, dissemination,<br>
&gt;distribution, or copying of this message is strictly prohibited. If you<br>
&gt;have received this communication in error, please notify us immediately<br>
&gt;and delete the original message.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;-----Original Message-----<br>
&gt;From: <a 
href="mailto:owner-gnso-ppsc-pdp@xxxxxxxxx";>owner-gnso-ppsc-pdp@xxxxxxxxx</a><br>
&gt;[<a 
href="mailto:owner-gnso-ppsc-pdp@xxxxxxxxx";>mailto:owner-gnso-ppsc-pdp@xxxxxxxxx</a>]
 On Behalf Of Avri Doria<br>
&gt;Sent: Monday, February 21, 2011 2:48 PM<br>
&gt;To: <a href="mailto:Gnso-ppsc-pdp@xxxxxxxxx";>Gnso-ppsc-pdp@xxxxxxxxx</a><br>
&gt;Subject: Re: [gnso-ppsc-pdp] Questions / comments - the meaning of "act"<br>
&gt;<br>
&gt;<br>
&gt;Dear Jeff,<br>
&gt;<br>
&gt;Oh course, I just want to _insist_ that the highlighting is done fairly<br>
&gt;and properly.  This is an issue I feel very strongly about and is an<br>
&gt;issue that I seen crop up in a couple of places now and one I feel I 
must<br>
&gt;be very clear about.<br>
&gt;<br>
&gt;For example, in recommendation 42, I find that differentiation along the<br>
&gt;lines of narrow and broad is prejudicial.  i also fined the explanation<br>
&gt;to be in error.  It is not the case that the "even if it was not 
approved<br>
&gt;by the required GNSO voting threshold"  but rather that "even if it was<br>
&gt;approved by a required majority GNSO voting threshold as allowed in the<br>
&gt;current By-laws instead of the supermajority threshold as also allowed 
in<br>
&gt;the current By-laws).    I apologize for not having pointed this out<br>
&gt;earlier, but until this discussio, I did not fully realize the prejudice<br>
&gt;contained in the current wording.  Ie. the discussion made me study it<br>
&gt;more closely.  and I thank you for that.<br>
&gt;<br>
&gt;<br>
&gt;Note:   while looking for the text in questions, which I never found i<br>
&gt;found the following<br>
&gt;<br>
&gt;&gt;  Recommendation 1.<br>
&gt;&gt; <br>
&gt;&gt; The PDP-WT discussed whether the voting thresholds currently n 
place<br>
&gt;<br>
&gt;should be 'in place'<br>
&gt;<br>
&gt;<br>
&gt;a.<br>
&gt;<br>
&gt;<br>
&gt;On 21 Feb 2011, at 20:05, Neuman, Jeff wrote:<br>
&gt;<br>
&gt;&gt; Avri,<br>
&gt;&gt; <br>
&gt;&gt; As I said in my earlier e-mail, the issue should be highlighted and 
we<br>
&gt;&gt;should get public input.  That should be the key take away from my 
point<br>
&gt;&gt;in the last e-mail.<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; Jeffrey J. Neuman<br>
&gt;&gt; Neustar, Inc. / Vice President, Law &amp; Policy<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; The information contained in this e-mail message is intended only 
for<br>
&gt;&gt;the use of the recipient(s) named above and may contain confidential<br>
&gt;&gt;and/or privileged information. If you are not the intended recipient 
you<br>
&gt;&gt;have received this e-mail message in error and any review,<br>
&gt;&gt;dissemination, distribution, or copying of this message is strictly<br>
&gt;&gt;prohibited. If you have received this communication in error, please<br>
&gt;&gt;notify us immediately and delete the original message.<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; -----Original Message-----<br>
&gt;&gt; From: <a 
href="mailto:owner-gnso-ppsc-pdp@xxxxxxxxx";>owner-gnso-ppsc-pdp@xxxxxxxxx</a><br>
&gt;&gt;[<a 
href="mailto:owner-gnso-ppsc-pdp@xxxxxxxxx";>mailto:owner-gnso-ppsc-pdp@xxxxxxxxx</a>]
 On Behalf Of Avri Doria<br>
&gt;&gt; Sent: Monday, February 21, 2011 1:58 PM<br>
&gt;&gt; To: <a 
href="mailto:Gnso-ppsc-pdp@xxxxxxxxx";>Gnso-ppsc-pdp@xxxxxxxxx</a><br>
&gt;&gt; Subject: Re: [gnso-ppsc-pdp] Questions / comments - the meaning of 
"act"<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; Hi,<br>
&gt;&gt; <br>
&gt;&gt; I am sure you are right.  But we should make sure that the opposite<br>
&gt;&gt;sides of the issues are well outlined as opposed to only one side 
being<br>
&gt;&gt;discussed or just leaving the issues undiscussed.<br>
&gt;&gt; <br>
&gt;&gt; And I see ABSOLUTELY NO REASON why this should be a issue discussed 
in<br>
&gt;&gt;private between Contracted Parties and Staff.  This is policy and is 
the<br>
&gt;&gt;business of us all, especially the GNSO Non Contracted Parties.  
Your<br>
&gt;&gt;contracts are our business, as the community is ICANN.  the staff is 
not<br>
&gt;&gt;ICANN, it is just one part of ICANN.  This is a fundamental point of 
the<br>
&gt;&gt;PDP and should not be lost in any chair level presumptions about<br>
&gt;&gt;different avenues of recourse!<br>
&gt;&gt; <br>
&gt;&gt; a.<br>
&gt;&gt; <br>
&gt;&gt; On 21 Feb 2011, at 18:04, Neuman, Jeff wrote:<br>
&gt;&gt; <br>
&gt;&gt;&gt; All,<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; We are not going to agree on this issue as a group before 
publishing.<br>
&gt;&gt;&gt;Let's make sure the issue is reflected and goes out for comment.  
I<br>
&gt;&gt;&gt;would like to see comment from the community as well as ICANN 
(which<br>
&gt;&gt;&gt;may be a first).<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; In the end it may not matter what we (the work team)  say as it 
may be<br>
&gt;&gt;&gt;fought out between ICANN staff/board and the contracted parties as 
this<br>
&gt;&gt;&gt;goes to the heart of the contracts.  But the issue should be<br>
&gt;&gt;&gt;highlighted.<br>
&gt;&gt;&gt; Jeffrey J. Neuman, Esq.<br>
&gt;&gt;&gt; Vice President, Law &amp; Policy<br>
&gt;&gt;&gt; NeuStar, Inc.<br>
&gt;&gt;&gt; <a 
href="http://Jeff.Neuman@xxxxxxxxxxx";>Jeff.Neuman@xxxxxxxxxxx</a><br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; ----- Original Message -----<br>
&gt;&gt;&gt; From: Avri Doria [<a 
href="mailto:avri@xxxxxxx";>mailto:avri@xxxxxxx</a>]<br>
&gt;&gt;&gt; Sent: Monday, February 21, 2011 11:58 AM<br>
&gt;&gt;&gt; To: <a 
href="mailto:Gnso-ppsc-pdp@xxxxxxxxx";>Gnso-ppsc-pdp@xxxxxxxxx</a> &lt;<a 
href="mailto:gnso-ppsc-pdp@xxxxxxxxx";>gnso-ppsc-pdp@xxxxxxxxx</a>&gt;<br>
&gt;&gt;&gt; Subject: Re: [gnso-ppsc-pdp] Questions / comments - the meaning 
of<br>
&gt;&gt;&gt;"act"<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; Hi,<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; I would never presume to say you, or anyone else, was not<br>
&gt;&gt;&gt;understanding something, so please do not take my response as 
trying to<br>
&gt;&gt;&gt;explain something you don't already understand.<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; What I take from what is in the current Bylaws and what I 
support<br>
&gt;&gt;&gt;keeping, is that approval of a consensus policy has two 
thresholds.<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; 1. If the GNSO has consensus, ie. supermajority, then the Board 
really<br>
&gt;&gt;&gt;can't refuse the policy unless they have a contravening 
supermajority.<br>
&gt;&gt;&gt;That is a very powerful ability to give the GNSO - the right to 
force<br>
&gt;&gt;&gt;the requirement for a supermajority vote and essentially force 
the<br>
&gt;&gt;&gt;Board's hand on creating a policy.<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; 2. On the other hand, if just a democratically reached majority in 
the<br>
&gt;&gt;&gt;GNSO approves of the policy then the Board's hand is not forced 
and<br>
&gt;&gt;&gt;they only need a majority of the Board to decide whether something 
is<br>
&gt;&gt;&gt;the right policy for ICANN.<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; And the reason to have this sort of mechanism is that it prevents 
any<br>
&gt;&gt;&gt;one SG from creating a roadblock that would prevent a policy they 
found<br>
&gt;&gt;&gt;unfavorable.<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; I actually think it is a clever way of handling the situation 
and<br>
&gt;&gt;&gt;removing it would create all sorts of roadblock scenarios that 
could<br>
&gt;&gt;&gt;deadlock ICANN on important issues.<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; a.<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; On 21 Feb 2011, at 17:43, James M. Bladel wrote:<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; "I would also note that not meeting the higher threshold does 
not mean<br>
&gt;&gt;&gt;&gt; rejected, it just means accepted at a lower threshold. "<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; So, what's the purpose of defining two thresholds?  What I am 
I not<br>
&gt;&gt;&gt;&gt; understanding on this?<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; Thanks--<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; J.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; -------- Original Message --------<br>
&gt;&gt;&gt;&gt; Subject: Re: [gnso-ppsc-pdp] Questions / comments - the 
meaning of<br>
&gt;&gt;&gt;&gt; "act"<br>
&gt;&gt;&gt;&gt; From: Avri Doria &lt;<a 
href="mailto:avri@xxxxxxx";>avri@xxxxxxx</a>&gt;<br>
&gt;&gt;&gt;&gt; Date: Mon, February 21, 2011 10:41 am<br>
&gt;&gt;&gt;&gt; To: "<a 
href="mailto:Gnso-ppsc-pdp@xxxxxxxxx";>Gnso-ppsc-pdp@xxxxxxxxx</a>" &lt;<a 
href="mailto:gnso-ppsc-pdp@xxxxxxxxx";>gnso-ppsc-pdp@xxxxxxxxx</a>&gt;<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; On 21 Feb 2011, at 14:30, James M. Bladel wrote:<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt;&gt; + Wouldn't the proposed addition of "If approved by the 
Council by<br>
&gt;&gt;&gt;&gt;&gt; the required thresholds" to section 1 (required elements 
of a PDP) of<br>
&gt;&gt;&gt;&gt;&gt; the new Annex A, prejudge the outcome of the outstanding 
discussion<br>
&gt;&gt;&gt;&gt;&gt;on<br>
&gt;&gt;&gt;&gt;&gt; whether the Board can act on recommendations that have not 
been<br>
&gt;&gt;&gt;&gt;&gt;approved<br>
&gt;&gt;&gt;&gt;&gt; by the required GNSO voting threshold? Would it be better 
to leave<br>
&gt;&gt;&gt;&gt;&gt;this<br>
&gt;&gt;&gt;&gt;&gt; proposed addition out for now and consider this following 
the<br>
&gt;&gt;&gt;&gt;&gt;outcome of<br>
&gt;&gt;&gt;&gt;&gt; the discussion on the Board can 'act'?<br>
&gt;&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt;&gt; JMB: I support Jeff's addition. The Board can "act" on 
GNSO-rejected<br>
&gt;&gt;&gt;&gt;&gt; recommendations by initiating a PDP/Issues Report of their 
own.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; On this one, I am still of the opinion that the Board can act 
means<br>
&gt;&gt;&gt;&gt;they<br>
&gt;&gt;&gt;&gt; can approve as consensus policy that only got a majority vote 
in the<br>
&gt;&gt;&gt;&gt; council by a supermajority vote.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt;&gt; f. In any case in which the Council is not able to reach 
GNSO<br>
&gt;&gt;&gt;&gt;&gt;Supermajority vote, a majority vote of the Board will be 
sufficient<br>
&gt;&gt;&gt;&gt;&gt;to act.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; I contend that the word 'act' is defined in the same as 'act; 
is in:<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt;&gt; c. In the event that the Board determines not to act in 
accordance<br>
&gt;&gt;&gt;&gt;&gt;with the GNSO Supermajority Vote recommendation, the Board 
shall (i)<br>
&gt;&gt;&gt;&gt;&gt;articulate the reasons for its determination in a report to 
the<br>
&gt;&gt;&gt;&gt;&gt;Council (the "Board Statement"); and (ii) submit the Board 
Statement<br>
&gt;&gt;&gt;&gt;&gt;to the Council.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; And that this means that in the event the GNSO only agrees by 
a<br>
&gt;&gt;&gt;&gt;majority<br>
&gt;&gt;&gt;&gt; on a policy recommendation the Board can decide to approve it 
with a<br>
&gt;&gt;&gt;&gt; majority or to disapprove it with a majority.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; Of course I am not a lawyer and may be missing some important 
modality<br>
&gt;&gt;&gt;&gt; of legal exegesis in my interpretation, but i do think that 
the same<br>
&gt;&gt;&gt;&gt; word used in two sentences in the same paragraph would 
normally have<br>
&gt;&gt;&gt;&gt;the<br>
&gt;&gt;&gt;&gt; same meaning in both sentences.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; I also would add that I do not think this is something that 
should be<br>
&gt;&gt;&gt;&gt; changed. I certainly expect the Board would take the majority 
only<br>
&gt;&gt;&gt;&gt; opinion into account, would read the explanations and the 
reasons<br>
&gt;&gt;&gt;&gt; against and make an informed decision.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; Also, I do not think they need to initiate another PDP in this 
case.<br>
&gt;&gt;&gt;&gt;At<br>
&gt;&gt;&gt;&gt; least not as a general rule, though of course I do not suggest 
making<br>
&gt;&gt;&gt;&gt;a<br>
&gt;&gt;&gt;&gt; rule that would prevent them from doing so, should they 
desire.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; I would also note that not meeting the higher threshold does 
not mean<br>
&gt;&gt;&gt;&gt; rejected, it just means accepted at a lower threshold.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; a.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;<br>
&gt;<br>
&gt;<br>
<br>
<br>

</div>
</blockquote></span></body></html>



<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy