ALAC:Meeting Notes/2006.06.29 Marrakech Thursday

Marrakesh Schedule & Session Notes > MOR2006 06 29 ALAC Meeting

Session	ALAC Meeting
Time	14:00-18:00
Location	Fez 1a
notetaker	initially, Wendy Seltzer

[edit] Agenda

For each topic: Identify what ALAC would like to produce as output, and what first steps we need to take to get there and get for each a subcommittee to start the work in between meetings.

Deliverables. Distinguish between meeting deliverables; long-term deliverables.

Siavash's list of policy issues (incl. WHOIS, gTLDs, IDNs)

-- Procedure for follow-up on Domain Marketing -- Deal with remainder on list. ID timelines. -- Ask people to tell us about interesting papers -- Bruce to help ALAC coordinate timelines (PDPs, other AC action, Board consideration)

DOC IANA contract, and MOU (procedure for ALAC comments, including call to indivs and ALSs)
- DEADLINE: July 7, 2006 (One week from now)

working back from the deadline, need time to discuss with committee, then make decision to send

--Izumi has prepared a draft, committee members have been commenting on list

- - tentative schedule:

July 1, last date for Committee comments. If we send to ALS, only 3 days to get their comments. Translation would be needed for real multilingual participation. One possibility (Erick): this weekend, get final ALAC comments to Izumi; Monday integrate; publish Monday July 3; circulate widely, 2 days for final integration; Problem with dates/data collection. This is a special case.

Get structures to sign document. (Sebastian, following Jacqueline). Following Vint's question, "who are you representing?" This doc could have more impact if it were signed by a number of structures. Don't worry about the length, but more about whether it says and explains everything we want to say.

Jacqueline suggests short consensus part, with appendices indicating views on which there is no consensus. Use ALACwiki consensus poll? Translate.

Annette. Possibility of consensus. Better to express ourselves in terms we all can agree upon than to send multiple views. Say members can also send individual statements. Timelines. Difficult to get ALSs to sign, better to get input, say 'on the basis of ALAC consultation with NN ALSs'. Inputs by Monday, another round. Procedure for reaching final consensus (July 5/6)

Pierre. involve ALSs, to answer question "Who are you." Help people understand the issues. Translate. Does each region have a discussion list? Simplify communications. Maybe don't focus on signatures. List those who say they agree.

Vittorio. We have 7 days. we're travelling. Orgs need 2 weeks to respond. Rather send ALSs message encouraging them to sign on or send their own submissions, circulate information. Spend time here focusing on substance.

Siavash. Use our limited time to focus on substance, sendng clear message to NTIA. Invite ALSs to send letter of support.

Izumi. Consensus views. Don't think it's feasible to get ALS signature in this time frame. For now, leave controversial points in document, in brackets. We should make maximum effort to listen. Being realistic, we may not get many globally. Ask ALSs to submit their own concurring. This is not the end of the process.

Roberto's suggested paragraph: "We believe that the current multi-stakeholder framework at ICANN should be further strengthened with more proactive and direct involvement of end-users. ALAC is engaged in foster participation of individuals, and ensure that their voice will carry an appropriate weight in the ICANN decision making process, also proposing changes in the way the board seats are currently allocated."

Sebastian. Champions of transparency should be consulting with our structures before releasing a document. Give them time to review. We should have started this process sooner. Some LAC structures might be able to sign, at least.

Erick. Not signatures, but input from ALS. For consensus, we should call to ALSs, or sign as individuals. Erick could not sign or say ALAC should sign if no ALS consultation.

Wendy. Many types of document, different strength of support

Full consensus of ALAC 15; majority of ALAC 15; majority of ALSs; consensus of ALSs. Strongest would be all of ALAC and all of the ALSes.
Most plausible scenario is achieve consensus on procedure for consensus on the document among 15;

Suggest we circulate to ALSs and invite them to send it with their own signatures if they agree.

Alice. Ensure we get input from ALSs. Working on process to get input more effectively. For future docs, build in more time.

Annette. Clear message on which we all agree, strongest document. Someone willing to draft with highlighted conflicts? Call to ALSs. Timeline: By Monday, list documented consensus, conflicts, proposed consensus.

Jean. Important to engage ALSs, but this isn't the time to do it more deeply. Circulate and ask ALSs to send their own letters. US vacations too. Possibility of losing credibility if we try to "engage" with such limited time. Short and focused. Reality check: MOU has been extended 6 times already; it's likely a shoo-in.

Hong. Possible formats include using names individually, ALAC. Suggests conditions; not published as "ALAC" unless consensus of all 15 members and participation of reasonable number of ALSs. For this important document. ICANN isn't interested in hearing from ALAC, but from community represented by ALAC. Reasonable allocation of time between policy development and RALO establishment.

Erick. Use discussion lists to send our Monday document. [Bruce notes: Mailing lists are not reliable at the moment.] We as volunteers all need to work on document. Presume agreement from those ALAC members who don't oppose. Monday, circulate for support from ALSs. Concerned about North-South split.

Sebastian. Send ALSs the doc translated asking if ALSs have serious concerns. (Hong. That's reasonable) Let ALSs send document with their signature if they agree.

Siavash. Concerns that document is not consistent. Don't want to send the wrong message.

Annette. Ask ALSs now to give input. Refer to call for comment, icannalac. Say we'll send draft.

Jean. What if we ask ALSs and they say "ICANN is a sham."

Pierre. Post what we have now to ALSs.

Siavash. we still haven't discussed it.

Asked whether ALAC has official procedure for approving documents. No answer.

Kieran McCarthy writing stories on NTIA. Is ALAC interested in having people directed toward ALAC to give us input. Committee suggested that they be given the icannalac.org URL.

Siavash. Prepare alternative document.

Annette. Try to reach consensus on non-meaningless document.

Timeline: Tomorrow, send out draft to alac and ALSs, w/ link (oppositions voiced). input requested by July 3. send first-round comments by July 3. Izumi offers to call via Skype. Izumi volunteered to redraft consensus, with highlighted conflicts. July 4. final-round comment 5/6. If there is any explicit opposition, then send the document only as individuals. Submit to NTIA: July 7

President's Committee on Strategy (10 mins became 100)
- Procedure for proposing members. Erick proposed, Pierre accepted, seconded x9.
  - - TOR for position, transparency
    - possibility of nominating multiple people
    - set the process before making nomination
    - inquire of ALSs?
    - what more do we know about the committee?
      - based on Board resolution. no set #. geog diversity, etc. in resolution/description; intended to be relatively small.
    - set a short timeframe for nomination and decision
    - note, this is an external lobbying group
    - set a timeframe for regional nominations
    - seize the moment
    - formal call for nominations
  - check for existence of other proposals
  - send one name now, more later
- List of names to be generated by July 9.
- Follow-up
- Deadline?

Procedure: End of week, circulate list of names with brief bios. Week later, agree on nominees. If no consensus, vote on no more than 3.

Dicussing/vote on ALSs
- Annette in contact with Giovanni for due diligence;
- Jean preparing voting for all that are ready

Domain Tasting, identifying the next steps.
- only an email is required to start the Issues Report
- Bruce can prepare either briefing or issues report.
- Annette will send email to Bruce
- Delegate to list
- Look at materials from Directi (Logic Boxes) -- lots of $$$

IDNs.
- Siavash and Hong to draft document to submit to GNSO WG and President's Committee on IDNs.
- Hong drafting update on last night's meeting.

RALO roadmap.
- Budget relevant items
- What is the budget?
- Self-review doc has suggestions on RALO progresss "ABCs of RALO Roadmap"
- What are the plans?

website
- committee trying to meet. Jacqueline joining committee.
- Jean warns that we need to learn this in case she's not put back by nomcom.
- Jean suggests setting a specific date-time for meeting on webdev