...
1. Roll call - 5 min, Co-Chairs
2. Review of WT A 4 Nov AIs - 5 min, Co-Chairs
Seth to place on WT A’s 18 Nov meeting agenda: Drafting of suggested ALAC public comment on ATRT draft recommendations (focusing on treatment of ALAC advice and perhaps ACs’ advice generally by Board).
...
WT A members to read both “Final Report: References to ALAC/At-Large’s continuing purpose” and “ICANN Bylaws - Required Board response to GAC advice” documents (to which there are also links on the WT A Workspace) in preparation for discussion/drafting during 18 Nov meeting.
...
Yrjo to write first draft of suggested ALAC public comment on ATRT recommendations (on collaborative page), focusing on the treatment of ALAC (and possibly other AC) advice by Board.
Heidi to schedule WT A for an informal meeting over a light breakfast in the convention center in Cartagena on Monday at 8:00 am (local time), and to request that a member of ICANN Legal be present to discuss revisions to ICANN Bylaws (incl. Article XI, 4, a).
...
4. Discussion/drafting of suggested ALAC public comment on ATRT draft recommendations (focusing on treatment of ALAC – and perhaps other AC -- advice by Board) – Co-Chairs, 15 min.
Cheryl: My plan is to put forward in the approaching ALAC meeting of 23 November whatever the WT’s draft at that time is of this comment on the ATRT draft recommendations. I’ll request ALAC comments at that time.
Yrjo: I agree with that plan.
Cheryl: I think this the draft is a great introduction. Now we need to insert the actual changes to the Bylaws. These changes should reflect a certain equality in the principled treatment of the ACs. We all agree how bizarre it is that, first, the ACs are treated differently by the Board and, second, that even the GAC’s own interaction with the Board is understood differently by different components. We want clear, understood guidelines regarding how the components of ICANN (especially the ACs) interact. The ATRT, of course, is looking at the GAC, which makes the position of the other ACs all the more precarious.
Evan: Do people feel our goal is to clone the revisions recommended by the ATRT to the GAC guidelines onto the ALAC or is it more to fashion what we think would work best for us, which could even be used as a model for the GAC revisions.?
Cheryl: Certainly the latter.
...
Cheryl: Evan, I think the example you cite and the questions it raises are relevant to cite in WT A’s suggested ALAC public comment on the ATRT. We now have cross-constituency work being done and WGs being created by the GNSO, GAC, ALAC, etc. But this cross-constituency recommendation regarding Rec. 6 was not seen as legitimate by ICANN’s Board Chair. And only because the ACs then supported the recommendation did this change. Even though this cross-constituency activity is very beneficial for our multi-stakeholder model, there is actually no set, predictable mechanism for creating such cross-constituency activity, recognizing it, or reporting it. Similarly, WT A’s recommended ALAC statement on the ATRT draft recommendations should clarify the role of Staff.
Evan: That’s exactly right. I don’t want repeated what, for example, happened in the Summit. We broke up into separate work groups that came up with quite constructive recommendations. But nothing ever came out of it beyond, perhaps, we got our getting a thank-you.
Cheryl: Yes, since everyone gets busy, there must be a set procedure or flowchart on the books that determines exactly what happens and who does it when, for example, such recommendations come up from the constituency.
...
5. Discussion/drafting of needed ICANN Bylaw changes – Co-Chairs, 15 min.
- See ICANN Bylaws pertaining to ALAC/At-Large (Confluence).
- See WT A Drafts: ICANN ByLaw Changes (Confluence).
Yrjo: No comment has yet been made to my draft revision of Article XI, 2, 4, a, which can be found on the Confluence pages.
...
Evan: Or from a corporate entity, such as AT&T, which I’ve seen during some public comment periods.
...
>> AI: Yrjo to draft revisions to At-Large-relevant Bylaw passages (including but not only XI, 2, 4, a) that incorporate WT B’s 18 Nov 2010 discussion ideas (see 18 Nov minutes, agenda item 5), including:
...
The members of the WT agreed that the next meeting would be on Thu, 2 Dec, 18:00 UTC.
The meeting was adjourned.