Recommendation 8

8.1

Develop ALAC process for requesting extended consultation window 

Substantially Complete

• http://forum.icann.org/lists/public-comment-enhancements-ii/msg00007.html
• http://atlarge-lists.icann.org/pipermail/alac-excom/2012-April/002046.html

8.1(a)

Ratify the process reflected in the flowchart titled “Figure D-1:  How the ALAC Should Request an Extension to a Public Comment Period” (see Appendix 2), by which the ALAC could request that a Public Comment period be extended. 
This proposed process includes the following steps (see Figure D-1 in Appendix 2):

• The ALAC’s deciding on the number of days needed for the extension;
• The ALAC’s submitting an extension request; and
• If the request is denied, the ALAC’s deciding on next steps (i.e., whether to submit a comment or not).

Substantially Complete

See: Figure D-1
 
At the 43rd ICANN Meeting in Costa Rica, the ALAC will be discussing the new ICANN Public Comment Process, with respect to the ALAC's right to submit policy advice at any time, with the Senior Director for Participation and Engagement. 

8.1(b)

Request that extensions to Public Comment periods be allowed of any length up to 30 additional days (see “A” on Figure D-1 in Appendix 2).

Substantially Complete

See: Figure D-1

8.2

Develop ICANN staff and Board process for implementing extension requests received 

Substantially Complete

8.2(a)

Request that any extension request to a Public Comment period be granted or denied within 24 hours (see “B” on Figure D-1 in Appendix 2).

Substantially Complete   

See: Figure D-1

8.3

Review of public comment processes 

Complete

8.3(a)

Recommend the establishment of a Policy Scheduling Team (PST), consisting of ICANN staff, to coordinate the opening of Public Comment periods. 
The PST should:

• Be comprised of an ICANN staff member assigned to each SO and AC and the Language Services Manager; and
• Maintain a publicly available Policy Comment Schedule (PCS), which tracks upcoming Public Comment periods, in order to (a) avoid many such periods opening around the same time, (b) allow the ACs and SOs to better plan their time and (c) allow better planning for needed translations.  (For each upcoming Public Comment period, the PCS should Include the policy name, a synopsis, the responsible AC or SO, and tentative opening date.)

Complete  

8.3(b)

Establish a standing committee, the ALAC/At-Large Policy Review Committee (PRC), responsible for advising the ALAC of actions needed regarding upcoming PCS policy issues, as well as policy issues not on the PCS but of At-Large interest.

The working of the PCS is depicted in the flowchart titled “ALAC/At-Large Policy Review Committee (PRC)” (see Figure D-2 in Appendix 2).

The specific responsibilities of the PRC should include advising the ALAC as early as possible of:

• ALAC comments needed in response to upcoming Policy Comment periods;
• At-Large community briefings, documentation or translations needed for upcoming Policy Comment periods;
• The degree of interest that the RALOs and ALSes have in the ALAC’s submitting comments during Policy Comment periods; and
  Policy issues (and other concerns) relevant to end users that are not on the PCS but that the RALOs and ALSes are interested in bringing to ICANN’s attention. 
   
  In order to perform its function, the PRC should be comprised of:
• The Chair and Secretariat of each RALO;
• At least two additional representatives from each RALO;
• The ALAC Rapporteur; and
• The ALAC liaisons to the various ACs, SOs and cross-constituency WGs.

Complete 

This sub-task will be completed during the San Jose meeting.

See: Figure D-2

8.4

Review measures to make policy development activities across ICANN's communities more accessible. Propose measures for community review. 

Complete