<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Dear Colleagues,<br>
<br>
It is greatly valuable to our work at this stage to identify areas
where different views are expressed. It is even more valuable when
they can be voiced with :<br>
- alternate proposals (such as, what would the "community veto
mechanism" look like in the constituency-based approach ?)<br>
- identification of the benefits of the proposed approach to enhance
accountability, as defined in our definition document. <br>
<br>
The criteria, rightly referenced by Kavouss below, can easily be
derived from these definitions. Does one option provide greater
transparency ? Enable accountability to a larger set of stakeholder
? Improve independence ? Provide better checks and balances ? <br>
<br>
We will certainly expand on these criteria very shortly. <br>
<br>
Best<br>
Mathieu<br>
<br>
<div class="moz-cite-prefix">Le 12/03/2015 22:28, Kavouss Arasteh a
écrit :<br>
</div>
<blockquote
cite="mid:0E80BA9A-8AF8-4C67-879F-2C26869110DE@gmail.com"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<div>Dear All,</div>
<div>Yes there are some evident criteria to address the issue of
proportionality.</div>
<div>Instead of defending one and offending the ethers create an
unhealthy </div>
<div>Atmosphere. Instead let us to make valid reasoning and
develop associated criteria</div>
<div>Regars</div>
<div>Kavouss. </div>
<div> <br>
<br>
Sent from my iPhone</div>
<div><br>
On 12 Mar 2015, at 21:11, <<a moz-do-not-send="true"
href="mailto:olivier.muron@orange.com">olivier.muron@orange.com</a>>
<<a moz-do-not-send="true"
href="mailto:olivier.muron@orange.com">olivier.muron@orange.com</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div><span></span></div>
<div>
<div>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt;">I
fully agree with Greg: <span style="background-color:
rgba(255, 255, 255, 0);">the GNSO represent the
largest part of ICANN’s activities , the other
supporting organizations like the ASO and the ccNSO
only rely on ICANN for the overall level of policies
(global policies), and for them most of the policy
work is done at the regional or national level.
Moreover </span><span style="background-color:
rgba(255, 255, 255, 0);">the GNSO represents a very
broad diversity of stakeholders, each with a very
specific point of view on the issues handled by ICANN.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt;"><span
style="background-color: rgba(255, 255, 255, 0);"><br>
</span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt;"><b
style="background-color: rgba(255, 255, 255, 0);"><span
lang="EN-US">I think that the GNSO should benefit
from a specific representation based on its
constituencies</span></b><span
style="background-color: rgba(255, 255, 255, 0);"
lang="EN-US">, that fully represent the diversity of
the stakeholders involved</span><span
style="background-color: rgba(255, 255, 255, 0);"
lang="EN-US">, and take into account the policy work
done at ICANN level.</span></p>
<br>
<span style="background-color: rgba(255, 255, 255, 0);">One
should note that in Work Area 2 inventory of input from
Public Comment, reference is made to a SO/AC Group where
GNSO is indeed represented at the Constituency level.</span></div>
<div><span style="background-color: rgba(255, 255, 255, 0);"><br>
</span></div>
<div><span style="background-color: rgba(255, 255, 255, 0);">Regards,</span></div>
<div><span style="background-color: rgba(255, 255, 255, 0);">Olivier</span></div>
<div><br>
Le 12 mars 2015 à 18:51, Greg Shatan <<a
moz-do-not-send="true"
href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a>>
a écrit :<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">I would be opposed to a group composed
solely of SO and AC chairs. It is a mistake to treat
all SO's and AC's as equivalent organizations. They
are not. Specifically, the GNSO consists of 4
separate Stakeholder Groups, two of which are composed
of 2-3 separate Constituencies. One of those
Stakeholder Groups, the Registry SG, is really the
equivalent of the ccNSO, and when the new gTLD program
wraps up, the RySG will represent more registries than
the ccNSO (even including the non-ccNSO ccTLDs).
Other Stakeholder Groups include the Registrar SG, the
Non-Commercial SG, essentially the equivalent of
"Civil Society," and the Commercial SG, essentially
the equivalent of the "Private Sector." (And that
does not even take the substantial variation at the
Constituency level into account -- the ISPs, for
example, are stuffed into the Commercial SG.)
<div><br>
</div>
<div>Are we suggesting that the ccNSO should share a
seat with representatives of, registrars, the
private sector and civil society? No -- that would
seem absurd. It's no less absurd to do that on the
gTLD side.</div>
<div><br>
</div>
<div>The GNSO and its hierarchical structure exist for
a particular purpose -- to develop policy
recommendations for gTLDs. Using that structure for
other purposes is an abuse of the structure, and
ultimately a distortion and an abuse of the
multistakeholder model.</div>
<div><br>
</div>
<div>Greg Shatan</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Mar 12, 2015 at 12:57
PM, Roelof Meijer <span dir="ltr">
<<a moz-do-not-send="true"
href="mailto:Roelof.Meijer@sidn.nl"
target="_blank">Roelof.Meijer@sidn.nl</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
<div>
<div
style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">All,</div>
<div
style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px"><br>
</div>
<div
style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">Not
so much a content reaction, but the template
set me thinking.</div>
<div
style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px"><br>
</div>
<div
style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px"><font
face="Calibri,sans-serif">Somehow,
referring to your "</font><font
color="#262626" size="3"><i>This challenge
mechanism would only apply to a narrow
set of predetermined high impact board
decisions such as the adoption of the
organization’s strategic plan, approval
of the budget, approval of bylaws, etc</i>.</font><font
color="#262626"><span
style="font-size:15px">”</span></font><font
color="#262626" size="3"> we
should „merge" or „synchronize” this with
the work done on powers 1A, 1B and 1C
(Vetoing changing to the bylaws, vetoing
the budget/strategic plan, vetoing board
action in conflict with bylaws).</font></div>
<div
style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">Veto’s
with different impact should have different
voting thresholds, but the rest of the
„ingredients” of the powers will mostly be
the same and I have the impression that as a
WS/WG we are pretty much aligned on those
ingredients. That also applies for template
7A- removing the board of directors, that
Jordan presented in yesterdays call.</div>
<div
style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px"><br>
</div>
<div
style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">The
most difficult part to discuss and decide
upon now (and we are not yet aligned there
and seem to be kind of touching it lightly
so far) is the overarching mechanism to
apply the powers. We identified: existing
SO/AC structure, permanent CCWG, Statutory
delegates or members, supervisory board. In
his template 7A, Jordan introduces an
additional one, "Community Council", and
provides alternative proposals for its
compilation.</div>
<div
style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px"><br>
</div>
<div
style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">The
group of community representatives that vote
on vetoing a board decision, intention,
action, budget, removing the board etc (the
group that administers the powers we
identified) can –and should in my opinion-
be the same for all those powers.</div>
<div
style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">In
Frankfurt we decided to identify the
requirements first and then determine the
best fitting mechanism.</div>
<div
style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px"><br>
</div>
<div
style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">We
have the requirements (powers to be given to
the community) largely, we are pretty much
aligned on them. So we really have to start
working on the mechanism to apply: what
should the composition of the group (who
should be in it, how do they get in:
elected/appointed/ex officio, how do they
get recalled) , how are positions mandated,
decisions made and how do we fix al that in
the bylaws. I am aware that we will need
legal advice on that, but I don’t think that
we have to wait with everything for that.</div>
<div title="Page 1">
<div>
<div>
<div>
<p><font color="#262626" size="3"> And
let</font><font color="#262626"><span
style="font-size:15px">’</span></font><font
color="#262626" size="3">s make it
as effective, simple and
executable as possible. I noted
again during the call yesterday,
that quite a few of us (I admit, I
am one of them) are in favor of
the group (whatever it will be
called in the end) be composed of
SO and AC chairs. Although we
should not limit ourselves to
that, I submit that we should
really explore that option.</font></p>
</div>
</div>
</div>
</div>
<div
style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<div><font color="#000000"><font
face="Calibri">Best,</font></font></div>
<div><font color="#000000"><font
face="Calibri"><br>
</font></font></div>
<div><font color="#000000"><font
face="Calibri">Roelof</font></font></div>
</div>
</div>
<div
style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px"><br>
</div>
<span
style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<div
style="font-family:Calibri;font-size:11pt;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>Robin
Gross <<a moz-do-not-send="true"
href="mailto:robin@ipjustice.org"
target="_blank">robin@ipjustice.org</a>><br>
<span style="font-weight:bold">Date: </span>woensdag
11 maart 2015 22:15<br>
<span style="font-weight:bold">To: </span>"<a
moz-do-not-send="true"
href="mailto:wp1@icann.org"
target="_blank">wp1@icann.org</a>" <<a
moz-do-not-send="true"
href="mailto:wp1@icann.org"
target="_blank">wp1@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>[Party1]
Accountability Mechanism Template WP-1-F |
Community Veto Proposal<br>
</div>
<div>
<div class="h5">
<div><br>
</div>
<div>
<div>
<div><font><span
style="font-size:10pt">
<div>Attached please find the
template completed for the
proposal regarding a
"community veto process".
<br>
<br>
Improvements, clarifications,
suggestions, etc. are most
welcome.<br>
<br>
Thanks,<br>
Robin<br>
<br>
</div>
</span></font></div>
<div><font><span
style="font-size:10pt">
<div><br>
</div>
</span></font></div>
</div>
</div>
</div>
</div>
</span></div>
<br>
_______________________________________________<br>
WP1 mailing list<br>
<a moz-do-not-send="true"
href="mailto:WP1@icann.org">WP1@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/wp1"
target="_blank">https://mm.icann.org/mailman/listinfo/wp1</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div dir="ltr">
<p style="margin:0in 0in
0.0001pt;line-height:12pt;background-image:initial;background-repeat:initial"><b><span
style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#17365d">Gregory
S. Shatan </span></b><b><span
style="font-size:8.0pt;font-family:Symbol;color:#17365d">ï</span></b><b><span
style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#17365d"> </span></b><b><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#c0504d">Abelman
Frayne & Schwab</span></b><span
style="font-size:9.5pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0in 0in
0.0001pt;line-height:12pt;background-image:initial;background-repeat:initial"><b><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#365f91">Partner</span></b><span><b><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#4f81bd"> </span></b></span><b><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#4f81bd">|
IP | Technology | Media | Internet</span></b><span
style="font-size:9.5pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0in 0in
0.0001pt;line-height:12pt;background-image:initial;background-repeat:initial"><b><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#17365d">666
Third Avenue | New York, NY 10017-5621</span></b><span
style="font-size:9.5pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0in 0in
0.0001pt;line-height:12pt;background-image:initial;background-repeat:initial"><b><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy">Direct</span></b><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy"> <span> </span></span><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1155cc">212-885-9253<span> </span><b>|<span> </span></b></span><b><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy">Main</span></b><span><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy"> </span></span><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1155cc">212-949-9022</span><span
style="font-size:9.5pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0in 0in
0.0001pt;line-height:12pt;background-image:initial;background-repeat:initial"><b><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy">Fax</span></b><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy"> <span> </span></span><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1155cc">212-949-9190<span> </span><b>|</b><span> </span></span><b><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy">Cell<span> </span></span></b><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1155cc">917-816-6428</span><span
style="font-size:9.5pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0in 0in
0.0001pt;line-height:12pt;background-image:initial;background-repeat:initial"><b><i><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy"><a
moz-do-not-send="true"
href="mailto:gsshatan@lawabel.com"
target="_blank">gsshatan@lawabel.com</a></span></i></b><span
style="font-size:9.5pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0in 0in
0.0001pt;line-height:12pt;background-image:initial;background-repeat:initial"><b><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy">ICANN-related:<span> </span><i><a
moz-do-not-send="true"
href="mailto:gregshatanipc@gmail.com"
target="_blank">gregshatanipc@gmail.com</a></i></span></b><span
style="font-size:9.5pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0in 0in
0.0001pt;line-height:12pt;background-image:initial;background-repeat:initial"><b><i><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy"><a
moz-do-not-send="true"
href="http://www.lawabel.com/"
target="_blank">www.lawabel.com</a></span></i></b><span
style="font-size:9.5pt;font-family:Arial,sans-serif"></span></p>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>WP1 mailing list</span><br>
<span><a moz-do-not-send="true"
href="mailto:WP1@icann.org">WP1@icann.org</a></span><br>
<span><a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/wp1">https://mm.icann.org/mailman/listinfo/wp1</a></span><br>
</div>
</blockquote>
</div>
<pre>_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
</pre>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>WP1 mailing list</span><br>
<span><a moz-do-not-send="true" href="mailto:WP1@icann.org">WP1@icann.org</a></span><br>
<span><a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/wp1">https://mm.icann.org/mailman/listinfo/wp1</a></span><br>
</div>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
WP1 mailing list
<a class="moz-txt-link-abbreviated" href="mailto:WP1@icann.org">WP1@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/wp1">https://mm.icann.org/mailman/listinfo/wp1</a>
</pre>
</blockquote>
<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>