Received: from ODCEDGE01-1.lrrlaw.com (10.32.8.38) by
 ODCCAS01-1.firm.lrrlaw.com (10.32.8.35) with Microsoft SMTP Server (TLS) id
 14.3.195.1; Tue, 22 Sep 2015 06:41:37 -0700
Received: from us-smtp-1.mimecast.com (207.211.31.120) by edge.lrrlaw.com
 (10.32.8.38) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 22 Sep 2015
 06:41:35 -0700
Received: from smtp01.icann.org (smtp01.icann.org [192.0.33.81]) (Using TLS)
 by us-smtp-1.mimecast.com with ESMTP id us-mta-43-IJt1YzmxScOicnlWted5Yg-1;
 Tue, 22 Sep 2015 09:41:34 -0400
Received: from mm.icann.org (mm.icann.org [192.0.32.100])	by smtp01.icann.org
 (8.13.8/8.13.8) with ESMTP id t8MDfBxA030166;	Tue, 22 Sep 2015 13:41:11 GMT
Received: from mm.icann.org (localhost [127.0.0.1])	by mm.icann.org (Postfix)
 with ESMTP id BA37061DA85;	Tue, 22 Sep 2015 13:41:11 +0000 (UTC)
Received: from pechora7.dc.icann.org (pechora7.icann.org
	[IPv6:2620:0:2830:201::1:73])	by mm.icann.org (Postfix) with ESMTP id
 1F4E560BDB1	for <accountability-cross-community@mm.icann.org>;	Tue, 22 Sep
 2015 13:41:10 +0000 (UTC)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12])	by
 pechora7.dc.icann.org (8.13.8/8.13.8) with ESMTP id t8MDf9V5007305	for
 <accountability-cross-community@icann.org>;	Tue, 22 Sep 2015 13:41:09 GMT
Received: from mx4.nic.fr (localhost [127.0.0.1])	by mx4.nic.fr (Postfix) with
 SMTP id 818AE281578;	Tue, 22 Sep 2015 15:41:08 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163])	by mx4.nic.fr
 (Postfix) with ESMTP id 7A5D4280A78;	Tue, 22 Sep 2015 15:41:08 +0200 (CEST)
Received: from [10.10.84.89] (larcenet.users.prive.nic.fr [10.10.84.89])	by
 relay2.nic.fr (Postfix) with ESMTP id 716AAB38024;	Tue, 22 Sep 2015 15:40:38
 +0200 (CEST)
From: Mathieu Weill <mathieu.weill@afnic.fr>
To: Chris Disspain <ceo@auda.org.au>, Jordan Carter <jordan@internetnz.net.nz>
CC: "Accountability Cross Community
	(accountability-cross-community@icann.org)"
	<accountability-cross-community@icann.org>
Subject: Re: [CCWG-ACCT] MEM and enforceability
Thread-Topic: [CCWG-ACCT] MEM and enforceability
Thread-Index:  =?utf-8?q?AdD1LbmNvnOg6JSHSLWIz5615G6qp4+ZsnIm8GbIOQD//5KBAIA?=
 =?utf-8?q?Ad8OAgAACaoCAAAX5AIAAAnsAgAACr4A=3D?=
Sender: "accountability-cross-community-bounces@icann.org"
	<accountability-cross-community-bounces@icann.org>
Date: Tue, 22 Sep 2015 13:40:51 +0000
Message-ID: <56015A63.8090208@afnic.fr>
References: 
 <35A914B1BE398440838C7AFFD79D34A20111592B@BRN1WNEXMBX02.vcorp.ad.vrsn.com>
	<80F513A5-E44F-4856-8F19-B7FDA302E7F1@auda.org.au>
	<CAK2bTy-p8iQY2M8dJgPNBgnbwnK13FasH5vkEQip63V9JYeA8w@mail.gmail.com>
	<D2269A17.37468%samantha.eisner@icann.org>
	<CAK2bTy_yOeEMDWmufeYPghKeOJF5YDZZUDerWrGOmhZNEGf-1g@mail.gmail.com>
	<972FB98E-3865-4247-B6D9-CCA0A8BD3D09@auda.org.au>
	<CAK2bTy-AZGp9Y05URDbxkC6Z8aM_k=yTKwbbbvcFfOGS-5Cd3Q@mail.gmail.com>
	<7DF5F5CD-0ADB-4152-8C5B-1DF0A3825BDA@auda.org.au>
List-Help: 
 <mailto:accountability-cross-community-request@icann.org?subject=help>
List-Subscribe: 
 <https://mm.icann.org/mailman/listinfo/accountability-cross-community>,
	<mailto:accountability-cross-community-request@icann.org?subject=subscribe>
List-Unsubscribe: 
 <https://mm.icann.org/mailman/options/accountability-cross-community>,
	<mailto:accountability-cross-community-request@icann.org?subject=unsubscribe>
In-Reply-To: <7DF5F5CD-0ADB-4152-8C5B-1DF0A3825BDA@auda.org.au>
Reply-To: "Mathieu.Weill@afnic.fr" <Mathieu.Weill@afnic.fr>
Content-Language: en-US
X-MS-Exchange-Organization-AuthSource: ODCEDGE01-1.lrrlaw.com
X-MS-Has-Attach: yes
X-Auto-Response-Suppress: All
X-MS-TNEF-Correlator: 
x-mc-unique: IJt1YzmxScOicnlWted5Yg-1
authentication-results: mimecast.com; spf=neutral (spfCheck: 192.0.33.81 is
 neither permitted nor denied by domain of icann.org) client-ip=192.0.33.81;
 envelope-from=accountability-cross-community-bounces@icann.org;
 helo=smtp01.icann.org;
delivered-to: accountability-cross-community@mm.icann.org
list-post: <mailto:accountability-cross-community@icann.org>
x-original-to: accountability-cross-community@mm.icann.org
list-archive: <http://mm.icann.org/pipermail/accountability-cross-community/>
errors-to: accountability-cross-community-bounces@icann.org
list-id: Mailing List for the ICANN Accountability & Governance Cross
	Community Group <accountability-cross-community.icann.org>
user-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
	Thunderbird/38.2.0
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="_004_56015A638090208afnicfr_"

--_004_56015A638090208afnicfr_
Content-Type: multipart/alternative; boundary="_000_56015A638090208afnicfr_"

--_000_56015A638090208afnicfr_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Chris,

Sorry for chiming in but I believe the point below deserves our full attent=
ion. It is indeed apparent in some contributions that the key concern about=
 the single member model lies in a (at least perceived) lack of accountabil=
ity of the SO and ACs.

The CCWG report was recommending to add SO/AC accountability to the list of=
 topics reviewed on a regular basis under the Board's supervision. And work=
 further in WS2. This did not seem to properly address the concerns.

Did the Board spend time considering what enhancements to SO/AC accountabil=
ity systems would bring these bodies to a level of accountability which wou=
ld be felt appropriate ? Or what the current (perceived, at least) accounta=
bility issues were ?

It would immensely valuable to our group if you or other Board members (or =
other stakeholders who shared that view) could provide additional details o=
n this, because I believe this is absolutely central in the discussion rega=
rding the single member model, but may not have been totally, explicitly st=
ated so far.

Best,
Mathieu


Le 22/09/2015 15:31, Chris Disspain a =E9crit :




   I disagree. Under the Board=92s proposal there is a focussed point that =
can be =91attacked' and put to arbitration and eventual judicial decision. =
Under the member model there is a gap because the same things cannot happen=
 to the member. In the Board=92s proposal the ultimate responsibility is th=
e Board=92s subject to binding arbitration and court enforcement. In the CC=
WG model the ultimate responsibility is the member but to whom are they acc=
ountable under the mission of ICANN that we must act in the global public i=
nterest.


--
*****************************
Mathieu WEILL
AFNIC - directeur g=E9n=E9ral
T=E9l: +33 1 39 30 83 06
mathieu.weill@afnic.fr<mailto:mathieu.weill@afnic.fr>
Twitter : @mathieuweill
*****************************

--_000_56015A638090208afnicfr_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <ABF18B9B1CF01B47820A4A7067FE1D82@lrrlaw.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body bgcolor=3D"#FFFFFF" text=3D"#000000">
Chris, <br>
<br>
Sorry for chiming in but I believe the point below deserves our full attent=
ion. It is indeed apparent in some contributions that the key concern about=
 the single member model lies in a (at least perceived) lack of accountabil=
ity of the SO and ACs.
<br>
<br>
The CCWG report was recommending to add SO/AC accountability to the list of=
 topics reviewed on a regular basis under the Board's supervision. And work=
 further in WS2. This did not seem to properly address the concerns.
<br>
<br>
Did the Board spend time considering what enhancements to SO/AC accountabil=
ity systems would bring these bodies to a level of accountability which wou=
ld be felt appropriate ? Or what the current (perceived, at least) accounta=
bility issues were ?
<br>
<br>
It would immensely valuable to our group if you or other Board members (or =
other stakeholders who shared that view) could provide additional details o=
n this, because I believe this is absolutely central in the discussion rega=
rding the single member model, but
 may not have been totally, explicitly stated so far. <br>
<br>
Best,<br>
Mathieu<br>
<br>
<div class=3D"moz-cite-prefix">Le 22/09/2015 15:31, Chris Disspain a =E9cri=
t&nbsp;:<br>
</div>
<blockquote cite=3D"mid:7DF5F5CD-0ADB-4152-8C5B-1DF0A3825BDA@auda.org.au" t=
ype=3D"cite">
<span style=3D"font-family: 'Verdana'; font-size: 13px;
        color: rgb(102, 102, 102);">
<div class=3D""><br class=3D"">
</div>
I disagree. Under the&nbsp;Board=92s proposal there is a focussed point tha=
t can be =91attacked' and put to arbitration and eventual judicial decision=
. Under the member model there is a gap because the same things cannot happ=
en to the member. In the&nbsp;Board=92s proposal
 the ultimate responsibility is the&nbsp;Board=92s subject to binding arbit=
ration and court enforcement. In the CCWG model the ultimate responsibility=
 is the member but to whom are they accountable under the mission of&nbsp;I=
CANN that we must act in the global public interest.</span></blockquote>
<br>
<pre class=3D"moz-signature" cols=3D"72">--=20
*****************************
Mathieu WEILL
AFNIC - directeur g=E9n=E9ral
T=E9l: &#43;33 1 39 30 83 06
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:mathieu.weill@afnic.fr=
">mathieu.weill@afnic.fr</a>
Twitter : @mathieuweill
*****************************
</pre>
</body>
</html>

--_000_56015A638090208afnicfr_--

--_004_56015A638090208afnicfr_
Content-Type: text/plain; name="ATT00001.txt"
Content-Description: ATT00001.txt
Content-Disposition: attachment; filename="ATT00001.txt"; size=206;
	creation-date="Tue, 22 Sep 2015 13:41:37 GMT";
	modification-date="Tue, 22 Sep 2015 13:41:37 GMT"
Content-ID: <E32B23308D92CC4DBD494E3E2790214D@lrrlaw.com>
Content-Transfer-Encoding: base64

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkFjY291bnRh
YmlsaXR5LUNyb3NzLUNvbW11bml0eSBtYWlsaW5nIGxpc3QNCkFjY291bnRhYmlsaXR5LUNyb3Nz
LUNvbW11bml0eUBpY2Fubi5vcmcNCmh0dHBzOi8vbW0uaWNhbm4ub3JnL21haWxtYW4vbGlzdGlu
Zm8vYWNjb3VudGFiaWxpdHktY3Jvc3MtY29tbXVuaXR5DQo=
--_004_56015A638090208afnicfr_--

