All questions and completed forms should be sent to controller@icann.org.

Please remember that the deadline for FY17 Budget consideration is 15 February 2016.

 

 

REQUEST  INFORMATION

Title of Proposed Activity  

 

 

ALAC Discretion to use Allocated Travel Slots to Support Active Volunteer Leaders within At-Large to Travel to and attend ICANN Public Meetings

Community Requestor Name

Chair

ALAC and Sub-committee on Outreach and Engagement Members Maureen Hilyard, Glenn McKnight,  Daniel Nanghaka, Olivier Crepin-Leblond

Alan Greenberg, ALAC Chair

ICANN Staff Community Liaison

 

Heidi Ullrich

 

 

 

 

request description

 

1. Activity: Please describe your proposed activity in detail

The ALAC has been allocated travel slots specifically for GNSO and ccNSO liaisons to attend ICANN meetings. Currently these positions have been filled by persons who are already entitled to travel to ICANN Meetings.

 

The current Travel Support Guidelines provide the At-Large community with the following:

 

The travel support for At-Large has been set to 27 positions. This number includes 15 ALAC members, 2 Regional Leaders, 5 RALO’s plus 2 Liaisons to the GNSO and ccNSO.  The two liaisons are non - voting members. This support includes the costs for air travel, lodging, and a per diem amount set for each city. 

 

Notably, the other AC/SOs receiving travel support have no such restrictions for the use of their travel support slots (other than the requirement to fund NomCom Appointees). We specifically note that the GNSO has 22 unrestricted travel slots, whereas there are only 21 GNSO Council Members – the 22 nd slot was originally designated for the Liaison sent from the ALAC to the GNSO, but the GNSO has never used it in that way.

 

We believe that the ALAC should be given full discretion about how they can use their 27 travel slots.

 

The ALAC and RALOs currently reallocate travel slots when an ALAC Member or a regional leader cannot attend a meeting. The replacement traveller is selected based on a combination of who will be able to contribute most to the At-Large meetings and sessions, and who would benefit most from this participation. A similar process would be used for filling the “Liaison” slots. 

 

The ALAC notes that since this request involves no additional budget allocation, it might be considered one which should be resolved purely within the Constituency Travel processes, and the ALAC agrees. However, since that process has not provided the needed flexibility, the ALAC is following this unusual process.

2. Type of Activity : e.g. Outreach - Education/training - Travel support - Research/Study -  Meetings - Other

Although this travel allocation might on occasion be used as a form of education/training for the traveller, in most cases it would be used to enhance our meetings by allowing a volunteer to travel who contributes heavily to the day-by-day teleconference/Wiki/e-mail At-Large activities but does not otherwise qualify for travel to ICANN meetings.

3. Proposed Timeline/Schedule: e.g. one time activity, recurring activity

The timeframe will be the whole FY17 (All three ICANN meetings). If the request is honoured, there seems little reason to not allow it for the remaining FY16 slots as well (since there is no budget implication).

 

 

 

  request objectives

 

 

 

1. Strategic Alignment. Which area of ICANN’s Strategic Plan does this request support?

ICANN Strategic Plan : https://www.icann.org/en/system/files/files/strategic-plan-2016-2020-10oct14-en.pdf
 

3 Advance organizational, technological and operational excellence.

ICANN seeks to mature our organization—to improve the skillsets, processes, and technologies through which we operate to deliver services to the ICANN community and the public. We seek to develop a greater ability to meet the speed and scale of innovation happening around us and deliver with excellence in everything we do.

 

 

2. Demographics. What audience(s), in which geographies, does your request target?

All geographies

 

 

3. Deliverables. What are the desired outcomes of your proposed activity?

         Provide needed flexibility to the ALAC for the allocation of their 27 allotted travel support slots

         Harmonization in ALAC travel support guidelines with those of other AC/SO.

         Participation by key leaders of the At-Large community, including WG Chairs, in ICANN Public Meetings

 

4. Metrics. What measurements will you use to determine whether your activity achieves its desired outcomes?

         Additional participation and engagement in ICANN Meetings by At-Large leaders

         Increased effectiveness of At-Large sessions due to WG chairs being in attendance at ICANN Meetings. 

 

 

 

 

 

Resource Planning – incremental to accommodate  this request

Staff Support Needed (not including subject matter expertise):

 

Description

Timeline

Assumptions

Costs basis or parameters

Additional Comments

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Subject Matter Expert Support:

None

Technology Support: (telephone, Adobe Connect, web streaming, etc.)

None

Language Services Support:

None

Other:

None

Travel Support:

Flexibility in allocating two travel slots for At-Large already granted within existing ICANN travel support guidelines.

Potential/planned Sponsorship Contribution:

None