Fwd: [council] Input Tracking for the Board =?ISO-8859-1?Q?=AD_?=GNSO PDP Recommendations

[joy]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

FYI - Any cmoments on this checklist form?
Joy


- -------- Original Message --------
Subject: 	[council] Input Tracking for the Board ­ GNSO PDP
Recommendations
Date: 	Wed, 15 Aug 2012 12:28:08 -0700
From: 	David Olive <david.olive at icann.org>
To: 	council at gnso.icann.org <council at gnso.icann.org>, liaison6c
<liaison6c at gnso.icann.org>



Dear GNSO Council Members and Liaisons:

As part of ICANN's implementation of the ATRT Recommendations, we have
developed and are implementing the attached checklist as a tool to meet
Recommendation 20, which states:

/20. The Board should ensure that all necessary inputs that have been
received in policy making processes are accounted for and included for
consideration by the Board. To assist in this, the Board should as soon
as possible adopt and make available to the community a mechanism such
as a checklist or template to accompany documentation for Board
decisions that certifies what inputs have been received and are included
for consideration by the Board. /


As the GNSO is the SO that is most active in providing recommendations
to the Board arising out of the policy development process, this
checklist is being piloted within the GNSO.  This would be a tool that
staff would have the primary obligation for completing as part of the
submission of GNSO Policy recommendations, and is not intended to
replace any of the existing documentation requirements.

We would appreciate your thoughts on if there are improvements that
could be made to this checklist to help make sure that this is
sufficient to capture the inputs as identified in the ATRT
Recommendation.

Please provide your inputs to rec-20-checklist at icann.org
<mailto:rec-20-checklist at icann.org> by 7 September 2012.

After your input is collected, we will be revising the checklist for use
by each of the Supporting Organizations.  We expect that this checklist
will go through iterations as we gain experience working with it.

Thank you for your help and input.

Regards,      David

David A. Olive
Vice President, Policy Development Support
Internet Corporation for Assigned Names and Numbers (ICANN)
1101 New York Avenue, NW - Suite 930
Washington, D.C.    20005
Office: 202.570.7126      Mobile:  202.341.3611




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQEcBAEBAgAGBQJQPUuGAAoJEA9zUGgfM+bqSpYH/3yxww6DC6qWo8llOPQ6iSv3
HAbcMugANHYJ33w+bmwpN88/QCbkRkoxTzZS2XTHXH/kUGkl9vAInBj9ksKA9P30
flKx2K2ztA5EiF9Wq21d21Y6ZyPTNKMPjLo5PeSBltVMVuI8cEyifWqLzfALCWDw
8t263dYFAcqPN4y3z3MkSpFa1LSNqb3yw1ZIij4z8A+dlv4QysCkJxl8dSYYig4p
SlEOTAlMyR7z6ZDYTfYYyT8/Jz5hX4r64dfnMrtD/u4wvDbeJcWjueHJC+bGT9bt
NIah1+GsCxCswuZ1Um3cjzIIAeSm5CWNcoyjKegk11jLkJPj7mOgZOBnPyFC7JE=
=XjPI
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Input Tracking  GNSO PDP Recommendations-ATRT Rec 20[4].doc
Type: application/msword
Size: 47616 bytes
Desc: not available
URL: <http://lists.ncuc.org/pipermail/ncuc-discuss/attachments/20120829/e8636fcf/attachment.doc>