[CWG-RFP3] Is there is a more suitable legal jurisdiction for an IANA subsidiary?

[Seun Ojedeji]

On Mon, Nov 3, 2014 at 7:45 PM, Milton L Mueller <mueller at syr.edu> wrote:

>
>
> > -----Original Message-----
> > It would be appropriate to emphasise the importance of keeping IANA as a
> > separate/independent/fire-walled service unit within ICANN.
>
> I don't consider this acceptable, nor do many others. If you can't move
> the names IANA to another entity, there is no accountability of the most
> basic type.


Isn't it possible to keep it within ICANN and still be able to move it when
the need arises? I would assume that was what


> On the jurisdiction issue, I am flexible, but let's make it clear: when
> you say you don't want a separable IANA, you are saying yo don't want real
> accountability. If IANA is locked into ICANN's structure and there is no
> NTIA, we are moving backwards.
>

It really depends and i will suggest that we look at the merits of all
these options in totality. We shouldn't just get locked in on just one
route. I for one thinks ICANN as IANA operator can be accountable without
necessarily taking IANA completely out of ICANN. Nevertheless, irrespective
of what i think, we should look at all the options in an holistic manner.
A document has been shared on the summary of discussions so far and i think
its a good starting point for this group.

Cheers!

>
> _______________________________________________
> Cwg-rfp3 mailing list
> Cwg-rfp3 at icann.org
> https://mm.icann.org/mailman/listinfo/cwg-rfp3
>



-- 
------------------------------------------------------------------------





*Seun Ojedeji,Federal University Oye-Ekitiweb:      http://www.fuoye.edu.ng
<http://www.fuoye.edu.ng> Mobile: +2348035233535**alt email:
<http://goog_1872880453>seun.ojedeji at fuoye.edu.ng
<seun.ojedeji at fuoye.edu.ng>*

The key to understanding is humility - my view !
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/cwg-rfp3/attachments/20141103/9e3c14c2/attachment.html>