You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »


Para traducir a español

Pour traduire en Français


Summary of recommendation: ALAC should choose – taking into account budgetary constraints and technologies already used elsewhere in the ICANN community – its own communication and other collaborative tools.

Suggested work team:

Summary of tasks in implementation:

  • The communication and collaboration needs considered unmet by ALSes and RALOs will be reviewed.
  • Technologies already used, as well as those not used, within At-Large and ICANN will be reviewed as solutions to these unmet needs (accessibility and cost/benefit issues will be considered).
  • A plan for the use of those technologies deemed appropriate will be created and implemented within At-Large.
  • Recommendations, as appropriate, will be made for the use of these technologies elsewhere in ICANN.

Target completion date: September--December 2010

Task No.

Sub-Task

Implementation Task

Status

7.1

 

Review of communication and collaboration needs considered unmet by ALSes and RALOs globally   

TBC 

 

6.1(a)

Encourage the same high level of input into ICANN’s annual financial planning from the ALSes and RALOs as was demonstrated in the planning for FY2012.         

TBC

 

6.1(b)

Continue to encourage ICANN to increase its level of detailed disclosure regarding the process of financing the ALAC and At-Large. 

The ALAC acknowledges that this level significantly improved for FY2012.  

TBC

 

6.1(c)

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

TBC

 6.2

 

Regarding meeting accommodations, ensure that At‐Large representatives are given treatment equal to that of other funded communities 

TBC

 

6.2(a)

Continue to monitor the accommodations given to At-Large representatives at ICANN Meetings to ensure they are equal to those of other funded communities.

TBC


Comments (accepted in the 6 UN languages):

  • No labels