Re: [iucg] [Ianaplan] SSAC Report on the IANA Functions contract

[JFC Morfin <[e-mail]>]

At 10:34 14/10/2014, Richard Hill wrote:
>The SSAC has prepared a Report on the IANA Functions Contract 
>(SAC068).  It is at:
>
>   https://www.icann.org/en/system/files/files/sac-068-en.pdf

Dear Richard,

This document concerns the pre-post-NTIA-removal. I belong to those 
who do not believe ICANN can have the NTIA's US sovereignty 
transferred to it. In that category, there seems to be 191 non-US 
States that do not share the NTIA plan, and actually have, in their 
wide majority, voted against it or politely abstained in Dubai.

What I know is that from now until September 30, 2015, all of them, 
most of the ISP, Libre developers, network lead users, entrepreneurs, 
militaries, informed politicians, etc. will consider at one time or 
another the "MYCANN Plugs-in" options. We all know how to assemble 
it. However, we do not know where it can politically/commercially 
lead us and what will be the innovative impact on the vision of the 
network architecture.

For the transition to be seamless, this new NTIA-less context is to 
be prepared.

If ICANN has found a credible self-accountability formula (not only a 
"community" applauded one), many will stay with ICANN, at least until 
the MYCANN Plugs-in have been validated.

Many others will probably have a gallant, legal, or greedy attempt at 
having one or several MYCANN Plugs-in. They will most probably help 
improving their codes, features, and services and stabilize them in 
the architectural netscape, as has happened for NATs.

It is up to this WG to decide how its beloved status quo is going to 
match this.

I have played my whistleblower's part. It is on the records. I will 
appeal the IESG in due time (after having seen how this debate 
develops), and then probably the IAB, and thereafter probably ISOC. I 
have started exploring, experimenting, preparing documents, and 
gathering developers. Our team will proceed (and advocate to proceed) 
along the ICANN ICP-3 reasonable constraints. Our first objective is 
the experimentation, a pragmatic understanding of the nature, 
structure, advantages, and risks of a MYCANN Plug-in (MPI), and then 
report on it.

As per RFC 6852, lead users, developers, governments, cyber commands, 
entrepreneurs, politics, edge providers, manufacturers, ISPs, and 
markets will then decide.

Best,
jfc