<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Chris, All,<br>
<br>
Another very good example of scenario, so I Cc Hillary. <br>
<br>
<div class="moz-cite-prefix">Le 29/07/2015 07:24, Chris Disspain a
écrit :<br>
</div>
<blockquote
cite="mid:A27A3F02-A8F3-4CD7-8295-3F0102D6356E@auda.org.au"
type="cite"><span style="font-family: 'Verdana'; font-size: 13px;
color: rgb(102, 102, 102);">However, we should also be very
clear that the community powers we are considering putting in
place will also provide the power to block policy arising from
one of the SOs especially where the policy concerned requires
there to be a by-law change. The GNSO could complete a PDP and
recommend POLICY X and the Board decide to proceed to change the
by-laws BUT all of that would be trumped if the by-law change
were blocked by 'the community'. And whether the GNSO could
‘block' the block depends entirely on the voting thresholds we
put in place. So, for example, with 20 votes and 75% required to
vote to block, the gNSO cannot, alone, block the block. </span></blockquote>
As you rightly point out Chris, two cumulative conditions are needed
for a gNSO policy proposal to get blocked with the new powers : <br>
1) that the policy proposal requires a Bylaw change<br>
2) (in the scenario described earlier) that 2/3 of the community
reject the Bylaw change. In the scenario you described (4x5 votes),
that means 14 votes against out of 20, while 5 votes come from the
gNSO. <br>
<br>
Once again, it's useful (but subjective) to ask whether that's a
useful safeguard or an undue interference with the policy making
role of the gNSO. <br>
<pre class="moz-signature" cols="72">--
*****************************
Mathieu WEILL
AFNIC - directeur général
Tél: +33 1 39 30 83 06
<a class="moz-txt-link-abbreviated" href="mailto:mathieu.weill@afnic.fr">mathieu.weill@afnic.fr</a>
Twitter : @mathieuweill
*****************************
</pre>
</body>
</html>