Staff to organize a Community call on the Interim Report of the Internationalized Registration Data Working Group. Steve Sheng is to be invited as Guest Speaker. -COMPLETED
Evan to be Chair AGAT WG.-

COMPLETED

Carlton to lead on drafting of unionized JAS Charter.
CANCELED - It was decided that Alan will draft the document

Olivier to inform GNSO that ALAC going ahead with unionized JAS charter.
DONE

AI: Staff to send draft ALAC unionized JAS Charter to ALAC-Announce mailing list with a courtesy comment to the GNSO.

Olivier to check DSSA WG Charter regarding positions that the ALAC needs to fill (re. alternate Liaison). Will follow up with Chair of SSAC. -
ONGOING - waiting for a reply

Staff to send announcement of At-Large DSSA WG members and their roles to the DSSA WG support staff. -
COMPLETED

Staff to send announcement to RALOs on ALAC decision to expand the ALAC Sub-Committee on Budget and Finance to one non-ALAC regional representative per region.
COMPLETED

Olivier to draft Preparation of At-Large Requests to ICANN's FY12 Budget working with the ExCom. The draft text is to be posted on the At-Large FY12 Budget Workspace.
COMPLETED

Staff, in consultation with CLO, to prepare brief ALAC response to the ATRT Report Recommendations. Staff to send to ExCom for review. -
COMPLETED

Staff to include on the proposed agenda to the next ALAC meeting reports from Improvements WTs. (They are to be put early in the ALAC agenda and allocated sufficient time for presentation, feedback, etc.) -
COMPLETED

Review of Current ALS Applications

...

CLO: Please note that my report has just been updated.

OCL: Do we still need to list the reports for .mobi

...

Inter-Registrar Transfer Policy Part B Working Group Proposed Final Report

Alan: I have not spend spent a lot of time on this.

OCL: Is this something we need to comment on?

...

Alan: I am one of the authors of this document. It is important. It advises that the Advisory Committees should be able to start PDPs. I am happy to talk to everybody interested in writing the ALAC advice but I should not be the author of the ALAC advisecomment.

AI: Dev and Dave to follow up with advise from Alan, Cheryl and everybody involved with the Proposed New GNSO Policy Development Process from At-Large.

...

Alan: This looks at registrants rights post expiration. There are none at this point. The report does not come close to what we would want. There were too many registrars in the WG and they teamed up against our interests. We can still make changes based on comments but we need to make them. Otherwise the registrars will make their comments and push in a certain comments.

OCL: Personally, I was a bit disappointed by the bullying of the registrars.

...

CLO: We need to follow up with the public consultation committee with regards to cultural sensibility issues, in particular with datesrespect to the holiday calendar.

Heidi: We have informed communication of a cross-cultural agenda calendar but given the current resource constraints it is unclear when this calendar will be set up.

Jean-Jacques: ICANN's meeting team already has a quite extensive list of cultural holidays it takes into account for their meeting planning.

AI: Staff will ask the RALO RALOs to review the suggested meeting dates for 2014 - 2016 (see http://www.icann.org/en/announcements/announcement-4-21feb11-en.htm)

...

Proposed Bylaw Amendments as requested by At-Large Improvements WT A

Olivier read out the suggested modification on Some ALAC members had submitted suggested changes to the Bylaws amendments to Article XI, Section 2.4.a (see httpsa as proposed by WT A. These suggested changes can be found at https://community.icann.org/display/Improve/WT+A%27s+Proposed+ICANN+Bylaw+Changes+for+ALAC+Approval). The modifications were submitted by WT A.Seth: You can also find the comments in the comment section on this page. Olivier read each of the suggested changes aloud to the group.

Samantha: The ICANN Bylaws are being maintained by the entire legal departmentLegal Department. I can not make comments on the suggested modifications on behalf of the legal team. I can make general comments, however.

OCL: Jean-Jacques proposed to add a paragraph under XI.2.4a:
"The ALAC, as the primary organizational home within ICANN for individual Internet users, has a responsibility in enhancing ICANN's accountability mechanisms, as called for by the Affirmation of Commitments. It also coordinates some of ICANN's outreach to individual Internet users."

Samantha summarised the legal difference between At-Large and ALAC (details to follow shortly).

Evan: I am not all for this amendement. Registrants is too narrow, end user is much wider community.

Samantha: As we review the comments, we will turn to the final report of the WG. There is a lack of continuity in the WG report with regards to the use of the user concept.
Alan: We do not change At-Large's areas, they remained the same. If we do not make it explicit we will have to fight battles which will become a waste of time. It is not in the report because it was considered a given to the people who wrote it. This is not true for everybody.

Marc: I don't think the fact that it is not consistent with the Bylaws should stop us from doing what is right.

Evan: There are issues where we clash with the interests with registrants, such as Whois.

Samantha: Will there be a proposal with specific language sent to the General Counsels office?

CLO: WT A sent it to the ALAC, it is now up to the ALAC to make a decision. We can either follow Alan or run a vote.

And I will need to take the changes suggested here back to the department. Here and now, I can not comment generally and on behalf of myself, however. Let me explain to the ALAC, as I explained to WT A, that the purpose of the preamble that we've written is to quickly summarize the role of the ALAC without making someone read through every specific point.

Olivier's suggested change is to replace

"The ALAC considers and provides advice on all aspects of work within ICANN" with "The ALAC considers and provides advice on all aspects of activity within ICANN."

Olivier explained in the comments: My reason for this suggestion is that the ALAC is also able to provide advice on matters not directly tagged as work, such as, but not limited to the location of a meeting, personnel changes, opening/closing of ICANN offices, etc. The text it replaces used to mention: "provide advice on the activities of ICANN" and this was wide-ranging. I am aware that the rest of the "new" sentence is: "as well as the many other issues for which community input and advice is sought." and I gather that this was included to expand the first part which restricted its input to "work". However, this also constrains the ALAC's mission.
The ALAC is able to comment on issues for which community input and advice is *NOT* sought too.

The ALAC decided to accept Olivier's suggested change.

Jean-Jacques's suggested change is to replace sentences 1 and 3 with the following: "The ALAC, as the primary organizational home within ICANN for individual Internet users, has a responsibility in enhancing ICANN's accountability mechanisms, as called for by the Affirmation of Commitments. It also coordinates some of ICANN's outreach to individual Internet users." The rationale is to use already standardized language and to add the important element of the AoC to the text.

The ALAC decided to accepted Jean-Jacques's change.

Olivier, buidling on Jean-Jacques's above change, further suggested on the list the following: "At-Large (ALSes, RALOs, and the ALAC), as the primary organizational home within ICANN for individual Internet users, has a responsibility to enhance ICANN's accountability mechanisms, as called for by the Affirmation of Commitments. It also coordinates some of ICANN's outreach to individual Internet users."

The ALAC rejected this change suggested by Olivier.

Alan: The point that our community includes registrants is not obvious to everyone, hence my suggested change in the commnets. Therefore, I have suggested (in the comments) the following addition after the first sentence of XI.2.4.a: "Individual Internet users may include, but are not limited to, domain name registrants in both gTLDs and ccTLDs." This change would not change who At-Large includes. However, if we do not make the inclusion of registrants explicit here, we will have to fight battles later, which will waste time.

Evan: The term "end user" already includes everyone. I am not in favor of this change, because "registrant" is too narrow a term.

Samantha: As we review these suggested comments, we shold turn to the ALAC Review WG Final Report. If the wording is in there, it goes a long way in supporting the suggested change.

Alan: It is not in the report because it was considered a given to the people who wrote it. This is not true for everybody.

Marc: I don't think the fact that something is not consistent with the Bylaws or in the Final Report should stop us from doing what is right.

The ALAC decided to reject Alan's change.

Evan moved that the ALAC approve (a) WT A's revision of Bylaws XI.2.4.a., with Olivier's first change and Jean-Jacques's change incorporated (but not with Olivier's second change or Alan's change incorporated) and (b) WT A's revision, as proposed, to XI.2.4.j. -- and propose propose both to the ICANN's General Counsel's Office. Jean-Jacques seconded the motion.

The wording of XI.2.4.a,, as it was approved by the ALAC, follows:

The ALAC, as the primary organizational home within ICANN for individual Internet users, has a responsibility to enhance ICANN's accountability mechanisms, as called for in the Affirmation of Commitments. It also coordinates some of ICANN's outreach to individual Internet users. The ALAC considers and provides advice on all aspects of activity within ICANN, including policies created through ICANN's Supporting Organizations, as well as the many other issues for which community input and advice are sought.

The specific elements of how ALAC fulfills this mandate are set forth below.

The wording of XI.2.4.j., as it was proposed by WT A and approved by the ALAC, follows:

The ALAC is also responsible, working in conjunction with the RALOs, for coordinating the following activities:

7. Participating in the ICANN policy development processes and providing input and advice that accurately reflects the views of individual Internet users; Evan moved that the ALAC approve the suggestions from WT A with Jean-Jacque's amendment. Jean-Jacques seconded the motion.

In agreement:
TBJ, SHL, SH, CLO, MR, GS, EL, EC, OCL, JJS
The motion passed unanimously.

Samantha: We need the document by next week to include it in the SFO meeting agenda for teh Board.

, EC, OCL, JJS

The motion passed unanimouslySamantha Eisner: I have a question on the scope of the proposed change from Jean-Jacques.

Brief Reports from At-Large Improvements Work Teams

The WG Chairs gave a brief presentation of the work of the Improvement WTs. All the presentations are available on the agenda page for this meeting.

GAC-Board Meeting - Discussion of ALAC positions

OCL: We will talk to the AGAT WG in Brussels. I imagine we could start with the first topic on the summary page for the Board GAC meeting:

T1: The objection procedures including the requirements for governments to pay fees;

Evan: Our position on this is evolving. We have room to move. There might be some fearmongering about a possible GVT veto, I don't think it is sustantialsubstantial.

OCL: I agree with Evan. I think our position has evolved since we submitted these statements. I suggest that we discuss this during the AGAT call.

...

CLO: I encourage all of you to subsribe subscribe to the ATRT Skype list to discuss this further.

...

Heidi: There are several consumer-related meetings in San Francisco. Unfortunately, the most prominent meeting hosted by Beau and Alex is during the ALAC policy meetings on Tuesday.

...

Evan: It is imperative that we have a formal meeting with the GAC. I understand that the GAC is occupied with Bruseels but still, this should not be forgotten.

Tentative Stanford Town Hall

Heidi: We started a mailing list. We have no resources so it would need to be self-organised. If we do move ahead, I suggest that we have a preparatory call in the next few days. The bus would cost USD 900.

Marc: There is a lot of interest but the key person has not responded to my emails. We are still looking at possible meeting venues. Do we reach out do a university environment or do we want to have it closer to the ICANN meeting. ? We need to determine in the next few days whether the local host will go ahead with this. If we don't have their consensus we can't go ahead. We should know by the end of the week.

...

AI: The Staff will ask the RALO to put forward volunteers for the ccNSO study group on he the use of names for countries and territories

...

Content

Space Tools

Versions Compared

Old Version 2

New Version Current

Key

Review of Current ALS Applications

Proposed Bylaw Amendments as requested by At-Large Improvements WT A

Brief Reports from At-Large Improvements Work Teams

GAC-Board Meeting - Discussion of ALAC positions