[CWG-RFP3] Is there is a more suitable legal jurisdiction for an IANA subsidiary?
Milton L Mueller
mueller at syr.edu
Wed Nov 5 14:23:04 UTC 2014
My point is just that you don't wait until IANA service levels drop or fail before you create a capacity to move it. That could get ugly. You create the movability now, as a critical feature of the transition.
--MM
> -----Original Message-----
> From: Paul M Kane [mailto:Paul.Kane at icb.co.uk]
> Sent: Wednesday, November 5, 2014 9:20 AM
> To: Seun Ojedeji
> Cc: Milton L Mueller; RFP3
> Subject: Re: [CWG-RFP3] Is there is a more suitable legal jurisdiction
> for an IANA subsidiary?
>
> Thanks Seun
>
> I agree with you :-)
>
> Today we need to ensure a stable transition without (m)any changes
> to the oversight status-quo (hence IANA function operated by ICANN
> staff but separate/independent/fire-walled).
>
> Should IANA service levels drop/fail, or ICANN falls into financial/legal
> difficulty, one of the options to consider _then_ is the the transition of
> the IANA to a more robust party.
>
> Regards to all
>
> Best
>
> Paul
>
>
>
> Seun Ojedeji wrote:
> >
> > I am not Paul but I saw this:
> >
> > separate/independent/fire-walled
> >
> > Whatever that means seem to be inline with your line of thought. So
> if
> > i may rephrase to say....it's important to keep IANA within ICANN but
> > separate/independent/fire-walled(and will add...Movable ;) )
> >
> > Cheers!
> > sent from Google nexus 4
> > kindly excuse brevity and typos.
> >
> > On 4 Nov 2014 06:49, "Milton L Mueller" <mueller at syr.edu
> > <mailto:mueller at syr.edu>> wrote:
> >
> > If we agree that it must be movable it’s fine. It’s when Paul Kane
> > says it’s important to keep it within ICANN that I get concerned.
> >
> > *From:* Burr, Becky [mailto:Becky.Burr at neustar.biz
> > <mailto:Becky.Burr at neustar.biz>]
> > *Sent:* Monday, November 3, 2014 4:26 PM
> > *To:* Seun Ojedeji; Milton L Mueller
> > *Cc:* RFP3
> > *Subject:* Re: [CWG-RFP3] Is there is a more suitable legal
> > jurisdiction for an IANA subsidiary?
> >
> > Maybe we are talking past each other Milton. I agree that the
> > bundle of IANA “functions” must be a stand-alone/segregated
> from
> > other ICANN activities in order to be moveable - but that doesn’t
> > require a separate legal entity does it?
> >
> > J. Beckwith Burr
> >
> > *Neustar, Inc. /* Deputy General Counsel and Chief Privacy Officer
> >
> > 1775 Pennsylvania Avenue NW, Washington, DC 20006
> >
> > Office: + 1.202.533.2932 <tel:%2B%201.202.533.2932> Mobile:
> > +1.202.352.6367 <tel:%2B1.202.352.6367> /
> becky.burr at neustar.biz
> > <mailto:becky.burr at neustar.biz> / www.neustar.biz
> > <http://www.neustar.biz>
> >
> > *From: *Seun Ojedeji <seun.ojedeji at gmail.com
> > <mailto:seun.ojedeji at gmail.com>>
> > *Date: *Monday, November 3, 2014 at 4:01 PM
> > *To: *Milton L Mueller <mueller at syr.edu
> <mailto:mueller at syr.edu>>
> > *Cc: *RFP3 <cwg-rfp3 at icann.org <mailto:cwg-rfp3 at icann.org>>
> > *Subject: *Re: [CWG-RFP3] Is there is a more suitable legal
> > jurisdiction for an IANA subsidiary?
> >
> > On Mon, Nov 3, 2014 at 7:45 PM, Milton L Mueller
> <mueller at syr.edu
> > <https://urldefense.proofpoint.com/v2/url?u=http-3A__mailto-
> 3Amueller-
> 40syr.edu&d=AAMFaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6
> X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=kNNtm5xxQvyRBwQA9
> 6RBE_d1K8EO_NzPqPTBlfK_hgY&s=ERNwZr9ae2WdJsHy-
> cSqGxHFr1Oq4QLw-s5q4quUTpI&e=>>
> > 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 <mailto:Cwg-rfp3 at icann.org>
> > https://mm.icann.org/mailman/listinfo/cwg-rfp3
> >
> > <https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__mm.icann.org_mai
> > lman_listinfo_cwg-
> 2Drfp3&d=AAMFaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifz
> >
> m6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=kNNtm5xxQvyRBwQ
> A96RBE_d1K8EO_NzPq
> >
> PTBlfK_hgY&s=P6jGDEebdOvmlkyYhJOySAO_aZXMT5YOtGW24kOXTtI
> &e=>
> >
> >
> >
> >
> > --
> >
> >
> > ----------------------------------------------------------------------
> > --
> >
> > /Seun Ojedeji,
> > Federal University Oye-Ekiti
> > web: //http://www.fuoye.edu.ng
> > <https://urldefense.proofpoint.com/v2/url?u=http-
> 3A__www.fuoye.edu.ng&d=AAMFaQ&c=MOptNlVtIETeDALC_lULrw&
> r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=kNNtm5x
> xQvyRBwQA96RBE_d1K8EO_NzPqPTBlfK_hgY&s=AeVUJjgV6bVdp8fSd
> 3nSX5d-gyy89eSid0mclYqRhMk&e=>
> > //Mobile: +2348035233535 <tel:%2B2348035233535>//
> > //alt email:seun.ojedeji at fuoye.edu.ng
> > <mailto:seun.ojedeji at fuoye.edung>/
> >
> > The key to understanding is humility - my view !
> >
> >
> > _______________________________________________
> > Cwg-rfp3 mailing list
> > Cwg-rfp3 at icann.org
> > https://mm.icann.org/mailman/listinfo/cwg-rfp3
> >
More information about the Cwg-rfp3
mailing list