[discuss] Opportunity for input on the development process for IANAoversight transition plan

[Jordan Carter]

It would be wonderful if ICANN staff could post the slides used at this
morning's session, which set out further ideas about the process.

Is that possible?

Jordan

Ps - here is a photo of one of the relevant slides. It seems mainly to just
show that schedule of meetings again.

[image: image.jpeg]

-- 
Jordan Carter

+64 21 442 649

twitter.com/jordantcarter

'Hope is the dream of a person awake' -- French proverb

On 24/03/2014, at 5:35 pm, Seun Ojedeji <seun.ojedeji at gmail.com> wrote:

++1

Cheers!

sent from Google nexus 4
kindly excuse brevity and typos.
On 24 Mar 2014 17:23, "Ian Peter" <ian.peter at ianpeter.com> wrote:

> The draft timeline (link provided below) is nothing more than a list of
> ICANN meetings, each described as a "meeting of the global multistakeholder
> community". No other events are included.
>
> Of course many, if not most, of the global multistakeholder community do
> not attend ICANN meetings. Many people with only  a passing interest in the
> day to day operations of ICANN have an interest in how this transfer of
> powers is resolved.
>
> One would hope consultation spreads well beyond the narrow set of
> stakeholders involved in ICANN.
>
>
> Ian Peter.
>
>
> -----Original Message----- From: John Curran
> Sent: Monday, March 24, 2014 8:08 PM
> To: 1Net List
> Subject: [discuss] Opportunity for input on the development process for
> IANAoversight transition plan
>
> 1net Discuss Participants -
>
> Folks may be aware that after the NTIA announcement,  ICANN released
> a draft timeline for development of an IANA oversight transition plan -
>
>     http://www.icann.org/en/about/agreements/iana/functions-
> transfer-process-14mar14-en.pdf
>
> Today at ICANN 49 in Singapore, there was a session which discussed
> the need to develop an IANA Accountability plan, as it will be necessary
> to provide NTIA with a community-wide plan for transition of the oversight
> duties which they presently perform.
>
> ICANN is coordinating the effort to develop this plan for IANA transition,
> and the first step is establishing a formal timeline and process for plan
> development.
>
> ICANN has provided a mail list for expedited input on the _process_ to be
> used for IANA transition plan development. This includes items such as
> feedback on the timeline document above, engagement processes, etc.
>
> The list is here: <ianatransition at icann.org>  (An public archive is also
> available here: <http://mm.icann.org/pipermail/ianatransition/>)
>
> Note that the goal is to gather the input on the plan development process
> to
> be used by 27 March 2014, and then combine the mail list discussion and the
> discussions happening at ICANN 49, with the resulting timeline and next
> steps
> to be released for public comment and community feedback on 7 April 2014.
>
> If you have specific views on process for development of the IANA
> transition
> plan, I would suggest that you contribute promptly.  If I see an official
> ICANN
> announcement on this matter, I will forward to 1net and you can discard
> this
> email.
>
> FYI,
> /John
>
> Disclaimer:  My views alone.
>
>
> _______________________________________________
> discuss mailing list
> discuss at 1net.org
> http://1net-mail.1net.org/mailman/listinfo/discuss
>
> _______________________________________________
> discuss mailing list
> discuss at 1net.org
> http://1net-mail.1net.org/mailman/listinfo/discuss
>
_______________________________________________
discuss mailing list
discuss at 1net.org
http://1net-mail.1net.org/mailman/listinfo/discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://1net-mail.1net.org/pipermail/discuss/attachments/20140324/ac8b105b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.jpeg
Type: image/jpeg
Size: 310431 bytes
Desc: not available
URL: <http://1net-mail.1net.org/pipermail/discuss/attachments/20140324/ac8b105b/image-0001.jpeg>