[CCWG-ACCT] The Board's take on the Mission Statement

[Bruce Tonkin]

Hello Becky,

The addition of "allocation and assignment of names" was intended to capture the role of putting names in the root zone including new gTLDs and IDN-ccTLDs."

I accept that this could be considered as part of "implementation of policies" = but it was trying to be more specific.

If you are concerned about the language you could reword like:

"coordinate the development and implementation of polices (including the allocation and assignment of names in the root zone as a result of those policies). "

Speaking personally I have no issue with also including the last two paragraphs in your note below which is really a limitation on what policies can be created and how they should be created.   This text is really lifted from the registry and registrar agreements so ICANN has already committed to that.   It is not something that we as a board directly discussed.


Regards,
Bruce Tonkin





From: accountability-cross-community-bounces at icann.org [mailto:accountability-cross-community-bounces at icann.org] On Behalf Of Burr, Becky
Sent: Thursday, 17 December 2015 3:00 AM
To: Accountability Community <accountability-cross-community at icann.org>
Subject: [CCWG-ACCT] The Board's take on the Mission Statement

I have run a comparison between the Mission Statement with respect to names, which has been on the table since January of this year, and the Board's proposed substitute.  In doing so, I have set aside totally the difficult wording issues relating to regulatory prohibition and contracting authority.  I am also setting aside, for the moment, Alan G's concern regarding the bottom-up policy development language (which I believe is addressed through the contracting language).  By any measure, the changes are significant.  Because the fundamental role of the IRP is to ensure that ICANN stays within its Mission, the changes in the Mission statement directly impact the effectiveness of the  "crown jewels" of this accountability exercise.

I have asked Bruce to explain what is encompassed by "the allocation and assignment of names in the root zone" that is not covered by "coordination of the development and implantation of policies."

I encourage each of you to study the side-by-side comparison attached to determine for yourself whether the Board's approach is consistent with the goals of clarifying ICANN's limited Mission.

[cid:image001.png at 01D13907.5FF1EE20]

J. Beckwith Burr
Neustar, Inc. / Deputy General Counsel & Chief Privacy Officer
1775 Pennsylvania Avenue NW, Washington D.C. 20006
Office: +1.202.533.2932  Mobile: +1.202.352.6367 / neustar.biz<http://www.neustar.biz>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/accountability-cross-community/attachments/20151217/589a4a26/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 200180 bytes
Desc: image001.png
URL: <http://mm.icann.org/pipermail/accountability-cross-community/attachments/20151217/589a4a26/image001-0001.png>