Page History
...
Task No. | Sub-Task | Implementation Task | Status | |||||
---|---|---|---|---|---|---|---|---|
78.1 | Review of communication and collaboration needs considered unmet by ALSes and RALOs globally |
| Develop ALAC process for requesting extended consultation window | TBC | ||||
| 7 8.1(a) Introduce to the ALSes selected information-dissemination, communication and collaboration tools (such as Posterous, Twitter Twibes, mobile-device compatibility) and provide training. | 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.
| TBC | |||||
| 7 8.1(b) | Conduct a survey of ALSes regarding communication & collaboration tools | TBC | 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). | TBC | |||
8.2 |
|
| Develop ICANN staff and Board process for implementing extension requests received | TBC | ||||
| 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). | TBC | |||||
8.3 |
|
| Review of public comment processes | 7.2 |
| Regarding meeting accommodations, ensure that At‐Large representatives are given treatment equal to that of other funded communities | TBC | |
| 7 8.23(a) | Establish a Technology Task Force (TTF) of community members that would periodically review the appropriateness of available technology, help train RALOs/ALSes in new technologies introduced and possibly staff a help desk. | TBC ||||||
7.3 |
| Review of currently available technologies not already used by At‐Large or elsewhere in ICANN that could fill the 7.1 needs of the ALSes and RALOs | TBC | |||||
7.4 |
| Create and conduct implementation plan for training ICANN's IT Support in the 7.3 technologies (and, as needed, in keeping IT Support current in 7.2 technologies) | TBC | |||||
7.5 |
| Based on At‐Large's choice of communication and collaboration tools to best fill its needs, make recommendations for use, or not, of these tools across ICANN | TBC | |||||
Recommend the establishment of a Policy Scheduling Team (PST), consisting of ICANN staff, to coordinate the opening of Public Comment periods.
| TBC | |||||||
| 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.
| TBC | |||||
8.4 |
|
| Review measures to make policy development activities across ICANN's communities more accessible. Propose measures for community review. | 7.6 |
| Create and conduct implementation plan for the periodic identification of technologies, either newly introduced to the market or updated, that can better fill the 7.1 needs of the ALSes and RALOs than those technologies currently being used | TBC |
...