Page History

IdentifybarrierswithinALACprocessesusedtocontributetostrategicplanningandproposefollow‐up.

Complete

Allocated to the ALAC Chair, the Executive Committee, the Director for At-Large, and RALO leaders.

5.1(a)

Ratify the strategic planning process reflected in the flowchart titled “Figure C-1: Proposed At-Large Strategic Planning Process.”

Complete

See: At-Large Policy Development Page See: Figure C-1

5.1(b)

Review and amend the ALAC’s strategic planning process yearly, in line with annual amendments to ICANN’s overall Strategic Plan.

Complete

See: At-Large Policy Development Page

See: ICANN Strategic and Operating Plan Process

5.1(c)

Conduct periodic “SWOT” (strengths, weaknesses, opportunities and threats) analyses of the At-Large strategic planning process, in conjunction with the RALOs and compare the results of these analyses to identify areas that have improved or deteriorated.

Complete

Allocated to the ALAC Chair, the Executive Committee, the Director for At-Large, and RALO leaders.

See: At-Large Work Team C SWOT Analysis 1-3  Workspace

5.1(d)

Articulate the ALAC’s and At-Large’s vision and mission.

Complete

See: ALAC/At-Large Vision Statement

See: ALAC vote results endorsing the At-Large  Visions Statement as Proposed by the At-Large  Improvements Taskforce.

5.1(e)

Use appropriate metrics to ensure that the ALSes are diverse, effective and well informed.

Complete

See: ALAC Metrics Sub-Committee

Allocated to the Metrics Sub-Committee and the ALAC as a whole.

• The Global Diversity of At-Large ALSes is clearly shown through this map:  http://www.atlarge.icann.org/maps/
• RALO ALSes: AFRALO ALSes, APRALO ALSes,  EURALO ALSes, LACRALO ALSesNARALO ALSes
• RALO Brochures: AFRALO Brochure, APRALO  Brochure, EURALO Brochure, LACRALO  Brochure, NARALO Brochure

5.1(f)

Initiate, develop and maintain an institutional knowledge management and retention system for At-Large.

Complete and ongoing

Allocated to Policy Staff in support of the ALAC and At-Large Members as past and present Members of the ALAC and At-Large Community and will be required to integrate with required future ICANN wide systems.

5.1(g)

Encourage the five RALOs to coordinate their outreach and “inreach” policies in order to facilitate the search for new skill sets needed within At-Large.

Complete and ongoing

Allocated to the ALAC Chair, the Executive Committee, the Director for At-Large Director for At-Large, and RALO leaders.

5.1(h)

Continue actively pursuing At-Large growth, for ICANN’s overall benefit.

Complete and ongoing

Allocated to the ALAC Chair, the Executive Committee, the Director for At-Large, and RALO leaders.

5.1(i)

When requesting ALAC outreach project funding, the ALAC emphasizes their role not only as a strategic resource benefiting the ALAC and RALOs but also as part of a wider ICANN legitimacy process.

Complete

Allocated to the ALAC Chair, the Executive Committee, the Director for At-Large, and RALO leaders.

5.1(j)

Continue to encourage ICANN to prioritize & increase funding for outreach.

Complete and ongoing

Allocated to the ALAC Chair, the Executive Committee, the Director for At-Large, and RALO leaders.

5.2

IdentifybarrierswithinALACprocessesusedtocontributetooperationalplanningandproposefollow‐up.

Complete

5.2(a)

Ratify the operational and financial planning process reflected in the flowchart titled “Figure C-3: Proposed At-Large Operational and Financial Planning Process.”

Complete

The ALAC has determined that, for this action item to be effective, it must be performed on a recurring schedule.

The item has been completed previously in February 2012. Each January, the ALAC and Policy Staff in support of the ALAC have will consider when it should be next repeated by the At-Large community.

See: Figure C-3

5.2(b)

Acknowledge and encourage a continuation of the better collaboration between the ALAC and ICANN’s Finance Staff seen in preparing the FY2012 Budget.

Complete

This proposal is in addition to the fact that most At- Large operational planning is done by Policy Staff in support of the ALAC.

5.2(c)

Conduct periodic “SWOT” (strengths, weaknesses, opportunities and threats) analyses of the At-Large operational and financial planning process, in conjunction with the RALOs (as WT C did), and compare the results of these analyses to identify areas that have improved or deteriorated.

Complete

See: At-Large Improvement WT C SWOT Analysis

In the first SWOT analysis conducted by WT C, the main barriers to operational and financial planning were identified as the ALAC’s being slow to react; translation processes being slow, and translations not being available for all documents; the ALAC members’ potential conflicts of interest; a lack of travel funding, putting At-Large in a second-class tier; and not enough informational materials for the ALSes.

5.2(d)

Formalize the process by which the ALAC collects operational demands from the RALOs and includes them in its operational plans.

Complete

See: At-Large Policy Development Page

5.2(e)

Clearly estimate and document the time required for the ALAC’s operational processes (e.g., responding to a call for Public Comments) and use these estimates to formalize its operational processes.

Complete

The Director for At-Large has consulted with the ICANN Staff responsible for the implementation of the Public Comment Enhancements regarding Recommendation 8 of the ALAC/At-Large Improvements Implementation Project. Following discussion between the Director for At-Large, the ALAC Chair and the Chair of the ALAC/At-Large Improvements Taskforce, the ALAC confirmed its understanding that the guidelines for Public Comments recognize flexibility in extending the Public Comment period beyond the minimum requirements. The ALAC may, on a case-by-case basis, request extensions of 5, 10, 15, 21 or 30 days (in exceptional circumstances). Such requests will be made directly to the Staff person responsible for the specific Public Comment period thereby notifying them that the ALAC intends to submit a comment. The ALAC further requests that a Staff response to such requests for an extension to a Public Comment period be granted or denied in an expeditious manner. If the request is denied, the ALAC may use its right to submit advice to the ICANN Board as per the ICANN Bylaws.

We note that the ATRT implementation process  includes the following relevant text: 

16. Publicnoticeandcommentprocessesshouldprovideforbotha distinct “Comment” cycle and a “Reply Comment” cycle that allows community respondents to address and rebut arguments raised in opposing parties’ comments.

17. Aspartofimplementingrecommendations15and16,timelinesforpublicnoticeandcommentshouldbereviewedandadjustedtoprovideadequateopportunityformeaningfulandtimelycomment.CommentandReplyCommentperiodsshouldbeofa fixed duration.  

The ALAC and its Improvements Taskforce established that the ALAC Chair, the ALAC Executive Committee and the Director for At-Large will continue to monitor this issue and will provide input to the Senior Director for Participation and Engagement and the Board PPC.

5.2(f)

Continue requesting face-to-face funded general assemblies (GAs) for each RALO every three years and an At-Large Summit.

Complete

See: At-Large Event Roadmap

The Events Roadmap has been submitted to ICANN Finance for their review.

5.2(g)

Continue to assist the RALOs in completing their annual ICANN requests for funding, as needed, in terms of writing, packaging and advocacy.

Complete

The item has been completed previously in February 2012. Each January, the ALAC and Policy Staff in support of the ALAC have will consider when it should be next repeated by the At-Large community.

ReviewongoingPolicyStaffinsupportoftheALAClevelsandbudgetallocationsandincreasesupportasprovidedthroughoutthisproject,consistentwiththerecommendationsinFinalReport.

Complete

AllocatedtotheALACChairandtheDirectorforAt-Large.

5.3(a)

Continue to monitor its level of needed Policy Staff in support of the ALAC and ICANN’s commitment to and progress in filling open

positions.

Complete

As of September 2011, all allotted positions for Policy Staff in support of the ALAC had been filled.

5.3(b)

The ALAC and Policy Staff in support of the ALAC should develop an annual support agreement

Withdrawn

This task is no longer relevant due to the following changes within ICANN in recent years (i.e., since submission of the ALAC Review Final Report). An increase in Policy Staff in support of the ALAC (as of September 2011, all allotted positions for Policy Staff in support of the ALAC had been filled.

6.1

ReviewofadditionalAt‐Largeinformationthatwouldbeuseful,subsequenttoimprovementsinfinancialreporting.

Complete

See: ALAC Subcommittee on Finance and Budget

Encourage the same high level of input into ICANN’s annual financial planning from ALSes & RALOs.

Complete

Complete

Allocated to the ALAC Finance and Budget Sub- Committees Working Group.

Continue to assist the RALOs in completing their annual ICANN requests for funding (writing, advocacy, & packaging)

Complete

The item has been completed previously in February 2012. Each January, the ALAC and Policy Staff in support of the ALAC have will consider when it should be next repeated by the At-Large community.

Continue to monitor the accommodations given to At-Large members at Meetings to ensure they are equal to those of others.

Complete and ongoing

Allocated to the Executive Committee.

7.1

ReviewofcommunicationandcollaborationneedsconsideredunmetbyALSesandRALOsglobally.

Complete

AllocatedtotheTechnologyTaskforce,itscontinuousprogresswillbesupervisedbythePolicyStaffinsupportoftheALAC.

Introduce to the ALSes selected information- dissemination, communication and collaboration tools (such as Posterous, Twitter Twibes, mobile-device compatibility) and provide training.

Complete

See: At-Large Technology Taskforce Tools  Workspace

Conduct a survey of ALSes regarding communication & collaboration tools.

Complete

See: At-Large Structure 2010 Survey Workspace

7.2

ReviewoftechnologiesusedbyAt‐LargeandacrossICANNthatcouldfillallorsomeofthe7.1needsoftheALSesandRALOs.

Complete

AllocatedtotheTechnologyTaskforce,itscontinuousprogresswillbesupervisedbythePolicyStaffinsupportoftheALAC.

Establish a Technology Task Force (TTF) of community members that will periodically review the appropriateness of available technology, train RALOs/ALSes in new technologies, and possibly staff a help desk.

Complete

Allocated to the Technology Taskforce, its continuous progress will be supervised by the Policy Staff in support of the ALAC.

7.3

ReviewofavailabletechnologiesnotalreadyusedbyAt‐LargeorelsewhereinICANNthatcouldfillthe7.1needsoftheALSesandRALOs.

Complete

AllocatedtotheTechnologyTaskforce,itscontinuousprogresswillbesupervisedbythePolicyStaffinsupportoftheALAC.

7.4

CreateandconductimplementationplanfortrainingICANN'sITSupportinthe7.3technologies(and,asneeded,inkeepingITSupportcurrentin

7.2technologies).

Complete

AllocatedtotheTechnologyTaskforce,itscontinuousprogresswillbesupervisedbythePolicyStaffinsupportoftheALAC.

7.5

BasedonAt‐Large'schoiceofthecommunicationandcollaborationtoolstobestfillitsneeds,makeneededrecommendations foruse,ornot,ofthesetoolsacrossICANN.

Complete

AllocatedtotheTechnologyTaskforce,itscontinuousprogresswillbesupervisedbythePolicyStaffinsupportoftheALAC.

7.6

Createandconductimplementationplanfortheperiodicidentificationoftechnologies,eithernewlyintroducedtothemarketorupdated,thatcanbetterfillthe7.1needsoftheALSesandRALOsthanthosetechnologiescurrentlybeing used.

Complete

AllocatedtotheTechnologyTaskforce,itscontinuousprogresswillbesupervisedbythePolicyStaffinsupportoftheALAC.

 foruse,ornot,ofthesetoolsacrossICANN.

7.6

Createandconductimplementationplanfortheperiodicidentificationoftechnologies,eithernewlyintroducedtothemarketorupdated,thatcanbetterfillthe7.1needsoftheALSesandRALOsthanthosetechnologiescurrentlybeing

used.

Complete

AllocatedtotheTechnologyTaskforce,itscontinuousprogresswillbesupervisedbythePolicyStaffinsupportoftheALAC.

8.1

DevelopanALACprocessforrequestingextendedconsultationwindow.

Complete

The Director for At-Large has consulted with the ICANN Staff responsible for the implementation of the Public Comment Enhancements regarding Recommendation 8 of the ALAC/At-Large Improvements Implementation Project. Following discussion between the Director for At-Large, the ALAC Chair and the Chair of the ALAC/At-Large Improvements Taskforce, the ALAC confirmed its understanding that the guidelines for Public Comments recognize flexibility in extending the Public Comment period beyond the minimum requirements. The ALAC may, on a case-by-case basis, request extensions of 5, 10, 15, 21 or 30 days (in exceptional circumstances). Such requests will be made directly to the Staff person responsible for the specific Public Comment period thereby notifying them that the ALAC intends to submit a comment. The ALAC further requests that a Staff response to such requests for an extension to a Public Comment period be granted or denied in an expeditious manner. If the request is denied, the ALAC may use its right to submit advice to the ICANN Board as per the ICANN Bylaws.

We note that the ATRT implementation process  includes the following relevant text:

16.Publicnoticeandcommentprocessesshouldprovideforbotha distinct “Comment” cycle and a