Summary Minutes 18 June 2012
Holly looked at the rules and would like to make a lot of changes, but the first question is we use the term member but if we look at the ALAC rules, "members" refer to the organization. So we need to be careful.
CLO: ALS are at large structures accredited to be part of AT large, the ALAC is the 15 members Committee. We need to make sure we refer to the same terminology.
We will be bundling the areas of the ROP into layers, such as operational layers.
AG: The current rules were written long time ago, and we may end up something different. We have to try to specify what is what we want to say.
The kind of recommendations, people should not be hung up on these as they are the final outcome.
We need to identify what are the things that we need to keep and what are the things that need to be open.
Where would Ex-Com go?
If the Excom does have executive powers then we need to put it in.
CLO: This is a very good discussion but we have a drafting team that was put together to look at the existing rules.
If we think about other layers, we will be carving out ROP into sections.
CLO called people from EACH of the Regions to participate.
We also need to look at definition and process, election, selection.
If you look at the page in the AC room.
Definition and Structure of the ALAC
We may need 5 rooms running.
The break out rooms may need to be segregated as follows
Section 3 two parts: Meeting and also elections, selections, we have 4 pieces of work.
Process which is an overarching one.
Section by Section analysis:
1) Drafting team Work space. Definition and Structure page.
Why are the UN GA mentioned and not the ICANN by laws sections mentioned.
CLO the current ROP are based on the UN GA.
The current ROP modify UN GA rules.
The By-Laws will be referenced.
All references to UNGA will be deleted in the future rules.
An Executive role exists in the UNGA which is the rapporteur.
AG will be glad to part and lead the group.
AG: The title was carried from UN rules as thi have adrlere were no tasks associated to it.
Carlton asked to be part of the Duties call and metrics plus Process Work Teams.
CLO: The rules will look at what will happen in the measuring of all the metrics. In this section, we will be defining what the expectations are.
It is also within expectations that the consequences of any measuring are also outlined.
ED: Suggested that in work spaces what you said about the expectations we should put an introductory paragraph.
AI: To add a paragraph on the Expectations to the WIKI.
The members of the Drafting teams were mentioned.
AG: I think it is important that we have to make sure that each person is represented and that person is going to do the work diligently.
What we are aiming for in Prague is to get the structure right, but we are not aiming to complete the task in Prague?
AG: We want to come out of Prague, with a general idea is not hard to draft, but we cannot do drafting rule by rule, it will be a poor use of time.
There will be plenty of room to analyze, and then detailed work will be done on the WIKI, post Prague world. We should not have holes or overlaps.
We want to make sure that no particular detail work is done in Prague.
AG: Once we have a draft we can look at it again. It is hard to critique vague things.
We need to look at a document that we should look at and be able to be translated.
ALAC 3.0 is the third iteration of what the ALAC is.
It is the first time that the ALAC has an operational role.
OCL: We should do a final read out to make sure that the rules are translatable.
UN languages are those significant to the At-Large community.
We need to recognize that ICANN legal needs to be sold, the community as well as ICANN legal.
Those who like to work in the world of the legal language are also satisfied.
Logistics: ICANN confirmed that meetings will be held on Wednesday in the ROMA room.
CLO asked all to be punctual in arrival.
.
