<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [council] Potential Topics / Action Items for Wrap-up
- To: Wendy Seltzer <wendy@xxxxxxxxxxx>
- Subject: Re: [council] Potential Topics / Action Items for Wrap-up
- From: "Novoa, Osvaldo" <onovoa@xxxxxxxxxxxx>
- Date: Wed, 10 Apr 2013 23:58:56 -0300
- Accept-language: es-ES, es-UY
- Acceptlanguage: es-ES, es-UY
- Cc: Jonathan Robinson <jrobinson@xxxxxxxxxxxx>, GNSO Council List <council@xxxxxxxxxxxxxx>
- In-reply-to: <516623F0.3000808@seltzer.com>
- List-id: council@xxxxxxxxxxxxxx
- References: <7wi006jo1ct3iowfl8os3ipl.1365644989891@email.android.com> <516623F0.3000808@seltzer.com>
- Sender: owner-council@xxxxxxxxxxxxxx
- Thread-index: Ac42YII8hqGVSZ+TQoqVmC1ZYTySqg==
- Thread-topic: [council] Potential Topics / Action Items for Wrap-up
I think this is a very good idea.
Regards,
Osvaldo
El 11/04/2013, a las 10:47, "Wendy Seltzer"
<wendy@xxxxxxxxxxx<mailto:wendy@xxxxxxxxxxx>> escribió:
I'd like to suggest an update to our working methods: Let's get reports
or slide-decks in writing in advance and begin at least the weekend
sessions by taking the reports as read, starting directly with
questions. It felt as though we spent a long time hearing summaries of
reports rather than discussing issues with or consensus around them. I
know I for one process information more thoroughly and more quickly in
writing.
To aid that, can we ask for a set of links in one place (or even better,
a single page HTML or PDF) containing everything we're expected to read,
for advance printing/downloading.
Thanks,
--Wendy
On 04/10/2013 09:49 PM, Jonathan Robinson wrote:
>
> Wrap-up Session - Potential Topics to Cover
>
> * GNSO Council Board - Next steps?
> * GNSO GAC / BGRI WG - Next Steps?
> * ICANN Durban Meeting Organisation
> * Response to / letter on EWG?
> * Policy and Implementation
> - Outcomes and next steps
> - Letter from GNSO Council to other SO/ACs?
> * GNSO Review
> - Consider self-review
> - Look at previous GNSO self-review work
> - Understand link / overlap with ATRT2
> - Seek update from Ray Plzak
> * Motions due 8 business days before meeting
> - Change operating procedures or fix existing ones
> * Information channels for review of RAA / new gTLD agreement
> * Privacy/proxy DT
> * CWG - Where to next?
> * Review of Motions for next session
> * Template to request Issue Report
> * Plural vs. Singular new gTLDs - Any GNSO Council Action / Steps to be taken?
> * Lack of interest on IDN issues - how to promote next steps / action
> (Could staff ensure Council is continually appraised of developements?)
>
> Action Items:
>
> * GNSO Council Chair comment to public forum
> * GNSO Council Chair to write to:
> - Board / CEO re Council Policy Advice
> - Other SO & AC leaders regarding Policy & Implementation
> - Bruce Tonkin re previous GNSO review
> - BGRI WG and/or GAC re tabulated summary of policy interaction points
> Refer timing of motions to SCI (business vs calendar days, as well as time)
> * GNSO Council Chair to contact Chairs of SO/ACs to ask for interest in
> policy vs. implementation WG
>
________________________________
El presente correo y cualquier posible archivo adjunto está dirigido únicamente
al destinatario del mensaje y contiene información que puede ser confidencial.
Si Ud. no es el destinatario correcto por favor notifique al remitente
respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los
posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier
utilización, difusión o copia de este e-mail por cualquier persona o entidad
que no sean las específicas destinatarias del mensaje. ANTEL no acepta ninguna
responsabilidad con respecto a cualquier comunicación que haya sido emitida
incumpliendo nuestra Política de Seguridad de la Información
This e-mail and any attachment is confidential and is intended solely for the
addressee(s). If you are not intended recipient please inform the sender
immediately, answering this e-mail and delete it as well as the attached files.
Any use, circulation or copy of this e-mail by any person or entity that is not
the specific addressee(s) is prohibited. ANTEL is not responsible for any
communication emitted without respecting our Information Security Policy.
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|