...
Ganesh – timeline seems ok. However, we need to define scope – effectiveness has a broad scope
ALAC or At-Large?
OCL – : Effectiveness of At-Large is not possibility as At-Large is not possible as that is a broad group. ALAC is more defined. ALAC/efficiency of its policy development
JJS – we : We need to take a wide picture (to give us context), but we need to drill down – what are the issues for the end user. One ex was that given by Garth re scam.
Sandra – : To clarify – See Theme A as a standing issue, but Theme B will be a changing issue which can change
EL: Agree…
JJS – : It is our duty to propse to the alac a complete view with possible solutions. However, a choice of a way forward.
Garth – : Sandra’s statement of making spam abuse go away is useful. However, … should be the top agenda item.
EL: term of abuse has been used a lot within ICANN – but narrow def. Part of the role we can play is that registration abuse goes wider
Holly - : RAA recs should be picked up. Also, the Registrant Rights Charter should also be included.
Yjro – point : Point 3 – ALAC Improvement recs – bylaws article was amended – EL and Y were aprt of that. New text creates slightly broader scope for AL. One approach would be to see how AL could fill up this new space. Also, if we are to rep end users worldwide, we should have more research. Perhaps the RALOs and aLSes could provide ALAC with more evidence so we could have more facts when we make …(our
...
JJS: what are one or two key items for Theme A
Ganesh – we : We are only 15, so time to what we can have as output. Current members of WG, we should ask ourselves how we can optimize our work. Ganesh – There should be a prioritrization mechnaims –prioritization mechanism.
Holly – suggested : Suggested each RALO picking topic they feel they are competent with. Holly would like to focus on Registrant Rights.
...