<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#330033">
<br>
<div class="moz-cite-prefix">On 01-Dec-14 20:25, Seun Ojedeji wrote:<br>
</div>
<blockquote
cite="mid:CAD_dc6jC-VY0EojZ9-Z-MaJ3RwoqdpHCdEfTM9KcpLoS0dcSWg@mail.gmail.com"
type="cite">Honestly at this point I think something is not clear
here. Can you confirm if this PRT is within ICANN or not because
your message above is implying outside. The second question is,
what are the "IANA operation" related issues that ICANN board
could say no to? and how is the accountability track
fixing/addressing that. </blockquote>
<br>
a few of us were talking about this evening over Eurodig drings and
over dinner.<br>
<br>
I have come to believe the the MRT is really the ICANN Community as
we know + others, but instead of sending its decisions to the Board
for blessing it sends its decision to the Contract Co. for
execution.<br>
<br>
It has been obvious for a while that the ICANN community and ICANN
Corporate are separate. So I have no trouble imagining that for the
purposes of the MRT we organize what is essentially the stakeholders
invovled in the ICANN community + some other parts of the Internet
community into the MRT. Pretty much exactly just as we done with the
ICG.<br>
<br>
As for who pays for the whole sructure we are talking about, it
should be the IANA contractor, ICANN at this point, as part of its
zero cost support of the IANA function. The only thing that seems
like it may require outside funding is the RFP/rebid process. And
for that we just follow the example we have been taught by ICANN
Corporate and Contract Co. charges the applicants for the IANA
contract an application fee sufficient for the process to be, as
they say, cost neutral.<br>
<br>
So it is not within ICANN, but it is formed by the ICANN Community
with others.<br>
<br>
avri<br>
</body>
</html>