[ispcp] Fwd: [council] For your review - draft GNSO schedule for New ICANN Meeting Strategy
Dear all, Do you have any comment on the draft GNSO schedule? I would need to have yours by tomorrow. Sorry for the short notice. Thank you and best regards, Osvaldo Inicio del mensaje reenviado: De: Marika Konings <marika.konings@xxxxxxxxx<mailto:marika.konings@xxxxxxxxx>> Fecha: 19 de mayo de 2015, 15:26:19 GMT-4 Para: Council GNSO <council@xxxxxxxxxxxxxx<mailto:council@xxxxxxxxxxxxxx>> Asunto: FW: [council] For your review - draft GNSO schedule for New ICANN Meeting Strategy Reminder - please note that the GNSO New ICANN Meeting Strategy Drafting Team is expecting to receive your and your SG/C’s feedback on the attached draft schedule during the GNSO Council meeting coming Thursday. Best regards, Marika From: Marika Konings <marika.konings@xxxxxxxxx<mailto:marika.konings@xxxxxxxxx>> Date: Monday 11 May 2015 10:31 To: "council@xxxxxxxxxxxxxx<mailto:council@xxxxxxxxxxxxxx>" <council@xxxxxxxxxxxxxx<mailto:council@xxxxxxxxxxxxxx>> Subject: [council] For your review - draft GNSO schedule for New ICANN Meeting Strategy Dear All, On behalf of the GNSO New ICANN Meeting Strategy Drafting Team, please find a first draft of the outline of the GNSO related meetings under the new ICANN Meeting Strategy which will take effect in 2016. The drafting team would be interested to obtain the input from you and/or your respective groups on this proposed outline via the mailing list and/or during the upcoming GNSO Council meeting so that any further changes can be made before this draft is shared with other SO/ACs ahead of the ICANN meeting in Buenos Aires. As discussed previously, co-ordination with other SO/Acs on the new meeting strategy will be of key importance to avoid potential conflict and/or overlap and as such the drafting team aims to work with the other SO/ACs to co-ordinate the approach for the new ICANN Meeting Strategy in Buenos Aires which is intended to result in a ‘final’ outline post BA. In the attached document you will find a summary of the main objectives of each of the meetings (A, B and C) as outlined by the ICANN Meeting Strategy Working Group, a high level schedule as prepared by the ICANN Meeting Strategy Working Group complemented by yellow additions that reflect the GNSO related meetings as well as a block schedule that has been prepared by the drafting team to further detail the expected GNSO related meetings. Note that for the B meeting a number of assumptions have been made that are listed on page 4 and 5. As a reminder, the B meeting reflects the biggest departure from the current meeting structure as it is a 4-day meeting focused on outreach and SO/AC work. Best regards, Marika ________________________________ 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.
GNSO ICANN New Meeting Strategy - 11 May 2015.docx
<html><head><meta http-equiv="content-type" content="text/html; charset=us-ascii"></head><body dir="auto"><blockquote type="cite"><div></div></blockquote></body></html>