And ICANN should not run a registry either. (It does.) On 14/09/16 12:29, John Curran wrote:
On Sep 10, 2016, at 8:28 PM, Bruce Tonkin <Bruce.Tonkin@melbourneit.com.au> wrote:
... Agreed. There has been a tendency at times to over simplify with the result that ICANN’s role appears far broader than it actually is. The work the CCWG did on more clearly defining ICANN’s narrow mission helps – but it does need to be translated into simple messages going forward. There is still a perception that control of ICANN equals control of the Internet.
A consistent strategy of communicating exactly what ICANN is (and is not) would help avoid misunderstandings to the contrary. This may also require that the various roles that ICANN serves within its overall mission be more clearly broken out, since the present amalgamation of roles (ICANN-as-the- IANA-operator, ICANN-as-the-organizer-of-the-names-community, ICANN-as- the-secretary-of-the-empowered-community etc.) does not lend itself to easy explanation to those not already immersed in the stew...
/John
p.s. my views alone - please feel free to discard, use, or reuse as desired.
_______________________________________________ Accountability-Cross-Community mailing list Accountability-Cross-Community@icann.org https://mm.icann.org/mailman/listinfo/accountability-cross-community