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

[Nick Ashton-Hart]

That set of meetings will cover the technical community well and is a good start - but there will need to be a sustained outreach beyond that. It is also not going to be sufficient to rely upon email lists or other technological mechanisms - many, especially in governments, simply don't work that way. This process will need to got to where non-technical stakeholders go, not oblige them to go to technical community meetings. 

My 0.02

On 25 Mar 2014, at 08:31, Grace Abuhamad <grace.abuhamad at icann.org> wrote:

> Hi all, 
> The slides are up at
> http://singapore49.icann.org/en/schedule/mon-iana-accountability
> The last slide includes a timeline with many opportunities for dialogue.
> 
> On 3/24/14 5:22 PM, "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-1
>> 4mar14-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 --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://1net-mail.1net.org/pipermail/discuss/attachments/20140325/86d4ca70/signature.asc>