<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
-----BEGIN PGP SIGNED MESSAGE----- <br>
Hash: SHA1 <br>
<br>
Hi - sharing this from the chair of the GNSO council in case you
have any comments for councillors before the next meeting.<br>
Sorry for the delay in passing it on, but i understand there is
still time to comment.<br>
<br>
Kind regards<br>
Joy Liddicoat<br>
<br>
<br>
- -------- Original Message --------<br>
Subject: [council] ICANN Durban - GNSO Council meeting with the
Board<br>
Date: Sun, 16 Jun 2013 12:48:48 +0100<br>
From: Jonathan Robinson <a class="moz-txt-link-rfc2396E" href="mailto:jrobinson@afilias.info"><jrobinson@afilias.info></a><br>
Reply-To: <a class="moz-txt-link-rfc2396E" href="mailto:jrobinson@afilias.info"><jrobinson@afilias.info></a><br>
Organisation: Afilias<br>
To: <a class="moz-txt-link-rfc2396E" href="mailto:council@gnso.icann.org"><council@gnso.icann.org></a><br>
<br>
<br>
<br>
All,<br>
<br>
<br>
<br>
As you know, Durban is approaching and we have the great opportunity
of an hour and a half with the ICANN Board.<br>
<br>
<br>
<br>
*Background*<br>
<br>
<br>
<br>
In my time on the Council, our meetings with the board have mostly
comprised an agenda made up from topics sent in both directions
which the Council has then worked to develop our position on,
typically on the Saturday of the weekend session. I feel that these
have been characterised, in part, by both the Council and the Board
?throwing topics over the fence? and, at times, these have been
lacking in strategic thought and / or thorough preparation by the
Council. Also, the tone of the meetings has felt in the past, to me
at least, to be a little antagonistic and not in necessarily the
spirit of moving a topic or topics forward.<br>
<br>
<br>
<br>
Prior to Beijing, I met with Steve Crocker and discussed with him
some of the above and part of the outcome of that discussion was a
suggestion that the Council come to the board with topics. We did
this through a softer introduction by me and then got into the ?meat
in the sandwich? via an intervention by Jeff (I recall). We went on
to have a good discussion on some critical issues. The discussion
was firm but reasonable and the feedback I heard afterwards from
both councillors and board members was largely if not universally
positive.<br>
<br>
<br>
<br>
*Towards Durban*<br>
<br>
<br>
<br>
I intend to meet with Steve again before Durban if possible, at
least through a telephone conversation. Before doing so, I would
like to be sure we are heading in the right direction and so would
appreciate your input.<br>
<br>
<br>
<br>
As chair, my feeling is that we should enter the discussion with an
objective. What do we want to communicate and how do we want to
achieve that?<br>
<br>
In this context, we may also think what we do not want to do /
achieve and how to make sure of that.<br>
<br>
<br>
<br>
My sense of what we should try to communicate is the following:<br>
<br>
<br>
<br>
1. A dynamic and forward looking GNSO Council that is actively
seeking to undertake productive work in the interests of a
successful multi-stakeholder model.<br>
<br>
2. A vigilant and responsible GNSO Council with some specific
and reasonable issues / concerns that will benefit from being aired
and discussed.<br>
<br>
<br>
<br>
Assuming the above, what is the purpose and substance of 1 & 2.<br>
<br>
<br>
<br>
1. Dynamic and forward looking GNSO Council ? Direct
communication of activity and taking feedback<br>
<br>
a. Key relationships<br>
<br>
i. Within the Council & GNSO<br>
<br>
ii. With ICANN staff<br>
<br>
iii. With others in the ICANN ecosystem<br>
(Actively reaching out to Board, GAC, ccNSO, other groups to
participate in joint initiatives)<br>
<br>
b. Operational productivity and efficiency initiatives<br>
<br>
c. Critical new / forward looking initiatives<br>
(in addition to ?regular? policy work)<br>
<br>
i. Development of a set of principles to guide (cross)
community working groups<br>
<br>
ii. Initiation of a WG to examine and develop critical issues
around policy and implementation<br>
<br>
iii. Awareness of forthcoming reviews (of GNSO & GNSO
Council) and willingness to anticipate these<br>
<br>
2. Vigilant and responsible GNSO Council ? Able to coherently
highlight critical issues, discuss these and move the agenda forward<br>
<br>
a. The MS model is critical to the ?defence? of ICANN, the MS
Model needs to be upheld<br>
<br>
b. BB<br>
<br>
c. CC<br>
<br>
<br>
<br>
*Summary*<br>
<br>
<br>
<br>
My belief is that we have an opportunity, and should seize it, to
communicate positively and in a way which we are most likely to be
engaged with productively.<br>
<br>
I think the issues raised and discussed in 2 above will benefit from
the context of 1 and so a structure along the lines above will work
and will welcome your feedback.<br>
<br>
<br>
<br>
Please note that 2 may contain one or more topics. I have suggested
one so far since it links to our discussion, both in Beijing and
subsequently, and could do with being moved on / developed.<br>
<br>
<br>
<br>
Look forward to your feedback and input on the above.<br>
<br>
<br>
<br>
<br>
<br>
Jonathan<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
-----BEGIN PGP SIGNATURE----- <br>
Version: GnuPG v1.4.9 (MingW32) <br>
Comment: Using GnuPG with Thunderbird - <a class="moz-txt-link-freetext" href="http://www.enigmail.net/">http://www.enigmail.net/</a> <br>
<br>
iQEcBAEBAgAGBQJRy1HdAAoJEA9zUGgfM+bqo9gH/RUQrmdiJem1DYzTo09lZMIu <br>
o6KS79801vkjXmRRBRbljGLSARAaFW0hSDIipOL/mEnfMb6824RKJzTmuGkUR1FO <br>
m0vNTrHRFMW2ct9CRQ7OldZwo02OCpCKxNgWgSYl1/ZgRvEp0ZSrBdMnz/cRcy4U <br>
kR/DAO4OWQOOgDEQBOx9qR3c4aACWCTCEfOaTkPFtM77WObwuaw+fA+muQmiYKd7 <br>
EteHx1lOgBGhNq0uiynwtAP2s6vkJkymwPgoWVI/IioK7GKcVRhOh38WVmkzk50M <br>
nOWN4GiKy2S7bjg4BvoY3Vrdnd+bgBsiA41+qqQOHFvx/Qa20B+NUt3SXTAoLzI= <br>
=tLRh <br>
-----END PGP SIGNATURE----- <br>
<br>
</body>
</html>