<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.23588"></HEAD>
<BODY>
<DIV><SPAN class=734174815-03072014><FONT color=#0000ff size=2 face=Arial>Dear
Evan,</FONT></SPAN></DIV>
<DIV><SPAN class=734174815-03072014><FONT color=#0000ff size=2
face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN class=734174815-03072014><FONT color=#0000ff size=2 face=Arial>I
think that it is important to distiguish two different accountabilities: one is
for ICANN's economic regulatory function, in particular the gTLD matters, the
other is for the clerical IANA function.</FONT></SPAN></DIV>
<DIV><SPAN class=734174815-03072014><FONT color=#0000ff size=2
face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN class=734174815-03072014><FONT color=#0000ff size=2 face=Arial>It
seems to me that the organizations that rely on the IANA function (registries,
RIRs, IAB/IETF) are well positioned to provide the ultimate oversight for the
IANA function.</FONT></SPAN></DIV>
<DIV><SPAN class=734174815-03072014><FONT color=#0000ff size=2
face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN class=734174815-03072014><FONT color=#0000ff size=2 face=Arial>I do
agree that the registries/registrars are not the appropriate entities to provide
the ultimate oversight for ICANN's economic regulatory function because, as you
say, that would put the regulated in charge of the regulator. My
suggestion is that the ultimate oversigh for ICANN's economic regulatory
function should be the end-users, that is the registrants of domain names
(people/organizations that hold domain name
registrations).</FONT></SPAN></DIV><SPAN class=734174815-03072014>
<DIV><BR><FONT color=#0000ff size=2 face=Arial>Best,</FONT></DIV>
<DIV></SPAN><SPAN class=734174815-03072014><FONT color=#0000ff size=2
face=Arial>Richard</FONT></SPAN></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px"
dir=ltr>
<DIV dir=ltr class=OutlookMessageHeader align=left><FONT size=2
face=Tahoma>-----Original Message-----<BR><B>From:</B> Chapter-delegates
[mailto:chapter-delegates-bounces@elists.isoc.org]<B>On Behalf Of </B>Evan
Leibovitch<BR><B>Sent:</B> jeudi, 3. juillet 2014 17:47<BR><B>To:</B>
Alejandro Pisanty<BR><B>Cc:</B> Chapter Delegates; Demi
Getschko<BR><B>Subject:</B> Re: [Chapter-delegates] Internet Society
Appointments to the NTIA/IANA Stewardship Transition Coordination
Group<BR><BR></FONT></DIV>
<DIV dir=ltr>
<DIV class=gmail_extra>
<DIV class=gmail_quote>On 3 July 2014 05:46, Alejandro Pisanty <SPAN
dir=ltr><<A href="mailto:apisanty@gmail.com"
target=_blank>apisanty@gmail.com</A>></SPAN> wrote:<BR>
<DIV> </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV dir=ltr>
<DIV>ISOC is the only member of the Coordination Group that is not
simultaneously a directly interested party, a "client" of IANA or a
structural participant in ICANN.</DIV></DIV></BLOCKQUOTE>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV>FWIW, I would also generally add to that set of characteristics, the
people currently being considered to fill the spots on the CG by ICANN
At-Large. While coming from a "structural participant in ICANN", the At-Large
delegates are also non-conflicted, and seek to protect the interests of those
who are neither sellers nor buyers of domains. (Indeed, such perspective of
At-Large is mandated in the ICANN bylaws.) It is no coincidence that so
many ISOC chapters are also At-Large Structures.</DIV>
<DIV><BR></DIV>
<DIV>The ALAC and ISOC delegates have highly common interest at the CG, and
the potential to be an effective coalition. No doubt there will be other,
self-interested coalitions with which they will need to contend.</DIV>
<DIV><BR></DIV>
<DIV>I have already been hearing from some corners of ICANN a sentiment that
oversight of IANA should "naturally" fall to those with whom ICANN has
contractual relations. If carried through to its logical conclusion this
perspective would, in effect, put the regulated in change of the regulator; it
needs to be resisted.</DIV>
<DIV><BR></DIV>
<DIV>Indeed, a trusted insider has suggested to me that the reference by some
within ICANN to the current situation as "IANA transition" (as opposed to the
more accurate "IANA stewardship transition") is deliberate, and an attempt to
shift (or at least blur) the focus.</DIV>
<DIV><BR></DIV>
<DIV>This will indeed be an interesting environment.</DIV>
<DIV><BR></DIV>
<DIV>- Evan</DIV>
<DIV><BR></DIV></DIV></DIV></DIV></BLOCKQUOTE></BODY></HTML>