ICANN ICANN Email List Archives

[pdp-pcceg-feb06]


<<< Chronological Index >>>    <<< Thread Index >>>

[pdp-pcceg-feb06] Terminology of reports and need for further formal input

  • To: <pdp-pcceg-feb06@xxxxxxxxxxxxxx>
  • Subject: [pdp-pcceg-feb06] Terminology of reports and need for further formal input
  • From: "Bruce Tonkin" <Bruce.Tonkin@xxxxxxxxxxxxxxxxxx>
  • Date: Mon, 4 Dec 2006 21:54:36 +1100

Hello All,

In response to Jeff Neuman's suggestion regarding the need to get
additional public comment/constituency input given the fact that the
recommendations may have substantially evolved from that originally
envisaged in the issues report (or even the Preliminary Task Force
Report)

I recommend that a "Draft Final Report" be created.   This Draft should
contain draft recommendations that have strong support from the task
force members.   The Draft should be clearly identified with a version
number and date, which will allow iterative refinement.

This "Draft Final Report" can then be put out for public comment on the
basis of substantially new information, and provide the opportunities
for constituencies to update their original constituency statement and
also comment specifically on the recommendations.

This would then allow staff to properly complete the following section
of the report:

"An analysis of how the issue would affect each constituency, including
any financial impact on the constituency;"

The report can then be updated to a "Final Report" status, prior to
sending to the Council.

Essentially we would be adding an additional step around section 9(b) of
the PDP process.
See: http://www.icann.org/general/bylaws.htm#AnnexA

This process should apply to all of the current PDP processes where
there are substantial recommendations that have evolved after a long
(e.g more than 12 months) policy process.

Regards,
Bruce Tonkin






<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy