<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#330033">
Hi,<br>
<br>
As one of those contributing to this draft who suggested this
formula, I can give my thinking:<br>
<br>
1. We should not be looking for numerical parity between the two
policy makers, cc and g, but rather looking at their organizational
structure. <br>
<br>
ccTLD policy organizes into regions, (5)<br>
gTLD policy organizes into Stakeholder Group (4)<br>
<br>
2. When thinking of gTLD policy, it is the GNSO as a whole that
needs to be represented in the MRT. The registries have a prioirty
in the CSC which focuses on operational issues. I see the MRT as
dealing with the Policy aspects and these are GNSO not just Registry
Stakeholder Group.<br>
<br>
avri<br>
<br>
<div class="moz-cite-prefix">On 13-Dec-14 12:15, Donna Austin wrote:<br>
</div>
<blockquote
cite="mid:35B1B5D6EF50FA4584F57D3B7393C0B123E447BF@MELEX01"
type="cite">
<meta http-equiv="Context-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<div class="WordSection1">
<p class="MsoNormal"><span>Milton,
</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>Speaking as the RySG representative
on the CWG: as direct customers of the IANA function, gTLD
registries would seek at a minimum parity, in your proposal,
for five members from the ccNSO. Your current composition is
inherently imbalanced by providing for only 1 gTLD registry
operator compared to 5 ccTLD registry operators.
</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>While ccTLDs have in the past been
the primary customer of the IANA naming services, the
delegation of more than 400 new gTLDs means that this is no
longer the case. If you can find rationale to have 5 ccTLD
registry operators in your proposed composition of the MRT,
I see no reason why this rationale should not be extended to
gTLD registry operators.</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span> </span></p>
<div>
<p class="MsoNormal"><span>Thanks,</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>Donna</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><img
src="cid:part1.06010108.07070804@acm.org"
alt="Description: Description: Description: ARI Logo"
height="57" width="48"><b><span>D</span></b><b><span>ONNA
AUSTIN</span></b><span><br>
</span><span>Policy and Industry Affairs Manager</span><b><span></span></b></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><b><span>ARI REGISTRY SERVICES</span></b><span><br>
</span><span>Melbourne</span><span>
</span><b><span>|</span></b><span>
</span><span>Los Angeles
</span><span><br>
</span><b><span>P</span></b><span>
</span><span>+1 310 890 9655<br>
</span><b><span>P</span></b><span>
</span><span>+61 3 9866 3710<br>
</span><b><span>E</span></b><b><span>
</span></b><span><a moz-do-not-send="true"
href="mailto:donna.austin@ariservices.com"><span>donna.austin@ariservices.com</span></a></span><u><span><br>
</span></u><b><span>W</span></b><b><span>
</span></b><span><a moz-do-not-send="true"
href="http://www.ariservices.com/"><span>www.ariservices.com</span></a></span><span></span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><i><span>Follow us on
</span></i><span><a moz-do-not-send="true"
href="https://twitter.com/ARIservices"><i><span>Twitter</span></i></a></span><span></span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><i><span>The information contained in
this communication is intended for the named recipients
only. It is subject to copyright and may contain legally
privileged and confidential information and if you are
not an intended recipient you must not use, copy,
distribute or take any action in reliance on it. If you
have received this communication in error, please delete
all copies from your system and notify us immediately.</span></i><span></span></p>
</div>
<p class="MsoNormal"><span> </span></p>
<div>
<div>
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span
lang="EN-US"> <a class="moz-txt-link-abbreviated" href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a>
[<a class="moz-txt-link-freetext" href="mailto:cwg-stewardship-bounces@icann.org">mailto:cwg-stewardship-bounces@icann.org</a>]
<b>On Behalf Of </b>Milton L Mueller<br>
<b>Sent:</b> Friday, 12 December 2014 5:42 AM<br>
<b>To:</b> Guru Acharya; <a class="moz-txt-link-abbreviated" href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a><br>
<b>Subject:</b> Re: [CWG-Stewardship] Composition of MRT</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span lang="EN-US">Here’s an idea that some
of us in NCSG are kicking around</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">We propose a 21-member
team with 2 non-voting liaisons, with some kind of
supermajority voting construct (⅔ or
</span><span lang="EN-US">⅘</span><span lang="EN-US">) for key
decisions. The composition is structured and balanced to
ensure that the MRT embodies a strong commitment to
efficient and neutral administration of the DNS root zone
rather than any specific policy agenda. Safeguards must be
in place to ensure that it is independent of ICANN corporate
but also cannot be captured or unduly influenced by
governments, intergovernmental organizations, or specific
economic interests. The MRT should draw most of its ICANN
community members from ICANN’s GNSO and ccNSO, with the GNSO
forwarding 4 (1 member for each Stakeholder Group), and the
ccNSO forwarding 5 (1 for each world region). The root
server operators should also be represented on the MRT with
2 positions. Each ICANN Advisory Committee (GAC, SSAC and
ALAC) should appoint 2 members. There should be 4
independent experts external to the ICANN community selected
through a public nomination process administered by [who?
ISOC? IEEE?] but subject to conflict of interest
constraints. Additionally, 2 non-voting but fully
participating liaisons from the other operational
communities should be appointed (by ASO for numbers and by
IAB for protocols) to facilitate coordination across the
different IANA functions. MRT members should be appointed
for limited terms sized appropriate to the contract renewal
cycle.</span><span lang="EN-US"></span></p>
<p class="MsoNormal"><a moz-do-not-send="true"
name="_MailEndCompose"></a><span lang="EN-US"> </span></p>
<div>
<div>
<div>
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span
lang="EN-US">
<a moz-do-not-send="true"
href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a>
[<a moz-do-not-send="true"
href="mailto:cwg-stewardship-bounces@icann.org">mailto:cwg-stewardship-bounces@icann.org</a>]
<b>On Behalf Of </b>Guru Acharya<br>
<b>Sent:</b> Friday, December 12, 2014 6:07 AM<br>
<b>To:</b> <a moz-do-not-send="true"
href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a><br>
<b>Subject:</b> [CWG-Stewardship] Composition of MRT</span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">The CWG is yet to
decide the composition of the MRT. I was hoping someone
could throw a strawman composition at us so that
discussions can be initiated.</span></p>
<div>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">As reference, the
composition of ICG is as follows:</span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">ALAC x 2</span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">ASO x 1</span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">ccNSO x 4</span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">GAC x 5</span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">GNSO x 3</span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">gTLD Registries
x 2</span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">ICC/BASIS x 1</span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">IAB x 2</span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">IETF x 2</span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">ISOC x 2</span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">NRO x 2</span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">RSSAC x 2 </span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">SSAC x 2</span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">1) Should members
of non-naming communities (like IETF and ASO) be a
part of MRT since our proposal only relates to the
IANA for the names community? For example, the CRISP
(numbers community) draft proposal does not envision
names community members in its oversight mechanism.</span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">2) Which
stakeholder groups should be included beyond the ICANN
community structures so that the MRT is representative
of the global-multistakeholder community? For example,
should IGF-MAG members have a place?</span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">3) How do we
include ccTLDs that are not ccNSO members?</span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">4) How do we
ensure membership from developing countries (not
government, but civil society or technical community)
- is some sort of affirmative action possible?</span></p>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
CWG-Stewardship mailing list
<a class="moz-txt-link-abbreviated" href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/cwg-stewardship">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a>
</pre>
</blockquote>
<br>
</body>
</html>