For Short-Term:

Closing Public comments

To cover

.PRO Fee Amendment (ends 17 July 09) – ALAC will not comment on.

One & Two-Character Names in dot-travel (deadline: ends 10 July 09) -

Systemization of Organizational review process (deadline: 8 July) – yes (can put in provisional comment that this has now gone to the community for comment) – CLO, AG and VS (draft statement ready by 4 July)

New gTLDs – Final Report on Competition and Pricing (deadline: 20 July) – put under analysis (PRN) – decision date no later than 6 July.

Board Review – 2nd Review on Working Group Report (deadline: 5 July) - Yes -

City TLD – no

Travel Support Guidelines for Community Members - (ends 6 July 09) – out to vote

Applicant Guidebook Analysis and Excerpts - (ends 20 July 09) – briefing yes, see ICANN 35; draft statement due ; vote starts 13 July (NAH: will ask Kurt if At-Large can have 10 days extra)

Fast Track Implementation (3rd Revision) - (ends 15 July 09)

Trademark Protection (IRT Final Report) - (ends 6 July 09) – (ALAC-NCUC joint statement goes out for community review and input) –

Expense Analysis - (ends 29 June 09 Extended to 13 July 09) – CLO would like to put something in re on how much we appreciate the greater details; No briefing required. Final statement due on 6 July. No time for consultation. ExCom to write statement.

Root Server System Scaling Study - (ends 31 July 09) – ExCom to send brief statement – suggest that next is pro-active. Statement is on 10 July, consultation, 4 days to incorporate comments, and 5 day vote.

ccNSO Review (Terms of Reference) - (ends 28 June 09) – No

Plan for Enhanced Internet Security, Stability and Resiliency - (ends 19 June 09) – Try to get answer on this.

SSAC review (Final report) - (ends 28 June 09) –

Draft FY10 Operating Plan and Budget - (ends 17 June 09)

CLO: proposed that the ExCom make a comment that on last day of Sydney meeting allocated X amount of public comments that fell between X and Y, 2009.

Action Item: ALAC to prepare a statement on need to suspend public comment days during ICANN meetings.

Action Item: Need to confirm with ICANN staff – that comments from non-EN speaking groups can be submitted up to 30 days after date that translated version of report is made available.
Get date of posting of translated reports from Marc. Then send advice to person responsible stating that Roberto personally committed in Sydney of X and thus posting deadlines for non-EN public comments are to be extended by days of public comment for EN. (cc Robert and Rob).

Briefing on Travel Guidelines

KW: The Travel Guidelines say that AL line 15 + 10 for each meeting or if you want to put in G.A.s and W.G.s – some process will take 10 x 3 and international travel and smaller set on domestic travel…Now we need a process by which that is determined – could be KW and SA (doesn’t want), Nick’s team…

NAH: if you were going to hold a GA – you’ll need to know sufficiently in advance – and in conjunction with ICANN meetings, Meetings staff will need say if they have bandwidth to take care of…

CLO: Perhaps HU and CLO goes to Regional Meteing and say that we need to hear from them on how they want to organize their General Assemblies.

NAH – ask RALOs on how they would choose their 5 reps and which meeting they want this to be on the sidelines with.

AG: need to assign rough travel figures - $2,000 per person?

KW: yes

SA: for Sydney – guess that avg will be $1,600

AG: 6 and 2 – during Delhi presentation.

AG: Roughly $4,000 per traveler

SA: 10 RALO coming to ICANN, 5 deferring – to GA…$60,000 – could you do 5 G.A.s at $12,000 each?

CLO: no

SA: can we do two G.A.s per year at $30,000

CLO: could look at relationships at NICS

VS: There is a meeting and in Sao Paulo – in Oct. before the Seoul meeting – and then can discuss at Seoul

AG: $35,000 across the five regions.

SA – discussed specifics of getting refunds on travelers who need to cancel last-minute.
Can’t transfer ticket to another person.

SB: nesxt meeting will possibly be more than 15 ALAC – 3 new NomCom

KW: this has not yet been addressed in the Guidelines. Stressed he needs to know who will be choosing who travel funding. Currently, on Seoul, there are 15 budgeted. Not ready to confirm…We need to handle this within exception process – and generally say yes. If we find out that we are way over budget, new CEO, etc, there’ll be a need to revisit.

AG: if there are not enough funds to have regional meetings once a year, then every two years…could then re-visit how much was left-over.

CLO: now that we have 5 regions…

KW: SA/KW will work with NAH on numbers.

SA: would like to have a better idea of what a GA would consist of, so could get a better sense of potential costs.

SB: discussed EURALO

AG: ALAC statement will say that the TG missed the issue of GA;

KW: Travel Guidelines won’t change to add regional GA. – strongly advise to work within the existing bucket…We went from 8 to 10.

AG: we asked for 15+8+2 = 25

Action Item: KW: will give At-Large staff units to discuss

HU: RALOs have been discussing possible meetings where GA.s could be held. Also, travel funding allotment should be discussed among broader Secretariat in some RALOs.

SA: Has heard some discussion of GA.s would be connected to ICANN meetings – but he advised against given busy schedule of these meetings.

AG: Yes, because they would expect to come to entire meeting.

General consensus was that this would not be a good idea.

NAH: Remote participation – Veriline would need to send a pre-packaged tech pack to

Sydney travel – and looking forward to Seoul

Action Item: CLO to send letter of thanks to Frank Fowley on Sydney travel/per diem.

CLO: on travel database – will get to gold?

SA: Many things involved in getting people to meetings…Rooms are blocked – don’t need to know names until week before meeting. The earlier we can book airline tickets the better that is for us. Also, depending on the country, visas are an interesting issue. Korea Meeting site includes.

CLO: Our staff can provide you with database – 15 + 10 + NomCom

SA: Although could arrange travel/hotel for people 3 weeks in advance – but visas are the issue. Steps: we get name, so we get them an itinerary – and get visa process underway.

CLO: The earlier you know where are people are coming from, the better travel staff can assist. We have the situation, where important people who we want to present last day, have left already.

SA: At-Large staff are your best conduit to what it is you want to accomplish.

CLO: The ExCom needs to be in the building until 18:00 on last day. Also, to allow the ExCom to stay the night of the final day is money list.

SA: We need a list of names with the countries in which they reside as soon as possible.

CLO: Re date of arrivals, we will need to confirm dates of working groups that will be held in the days before the official start of the ICANN meeting.

AG: For frequent travelers, buying tickets way in advance is somewhat problematic.

CLO: It is hugely important that better value on travel is made.

SA: Flexibility will allow us to be smarter.

AG: We can inform Travel Staff who the At-Large staff are that are problematic.

NAH: Sylvia will be replacing Jose.

Discussion of overlap – ex. need of Sylvia to be in Seoul as well as Jose…

SB: We need to inform Sylvia as soon as possible whether she will receive travel-funding

SA: At-Large will not need to create a new database. Are working with IT to create an electronic database system – that travelers will be able to complete.

CLO: Will particular chains be used in the future?

SA: Explained difference between Meetings and Travel staff. Meetings staff are looking possibility of using chains to receive discounts. SA is doing the same with airlines.

CLO: Good that we seeing dialogue.

NAH: RALOs will not be happy.

Discussion of Election of Board Liaison and possible ALAC/At-Large Board Members

Action Item: NAH will distribute details of his suggested approach to the election of the Board liaison

Meeting Reports

Discussed status of meeting report postings.

Youth Meetings

SB: Proposed that At-Large work with ccNSO on proposed youth forum to be held in Seoul.

Action Item: ccNSO liaison to find out details on planned youth forum to be held in Seoul. Based on this information, ExCom will discuss possibility of working with ccNSO on the planning of this event.

Fellowship Program

VS discussed developments in the Fellowship Program.

Outreach to potential ALS candidates

SB: Proposed that the RALO secretariats are responsible for working toward Summit decision of having one ALS per country.

  • No labels