[Gnso-igo-ingo-crp] Question about WG facilitated session in Singapore (ICANN52)

[Novoa, Osvaldo]

+1
Regards,
Osvaldo

Sent from my iPhone

On Nov 17, 2014, at 9:57 PM, David Cake <dave at difference.com.au<mailto:dave at difference.com.au>> wrote:

I plan to be at the face to face meeting.

David

On 11 Nov 2014, at 3:17 am, Mary Wong <mary.wong at icann.org<mailto:mary.wong at icann.org>> wrote:

Dear WG members,

We are beginning to work with the ICANN Meetings Team to put together the schedule for the upcoming ICANN52 Meeting in Singapore, in February 2015. As you will recall, our WG has been selected by the GNSO Council as the second WG to participate in the Council’s pilot project for facilitating successful WG outcomes, following the Privacy & Proxy Services Accreditation Issues WG’s positive experience in Los Angeles last month.

I am writing now to find out how many, and which, WG members intend to participate in the Singapore full-day, face-to-face facilitated session, to be held immediately following the end of the ICANN Meeting, on Friday 13 February 2015. This will permit the organizers to secure the most appropriate meeting room space, among other arrangements.

Please note that WG members who require ICANN travel funding in order to be at the Singapore meeting will have to have their travel approved by their respective GNSO Stakeholder Group or other ICANN SO/AC. We will be writing separately to each SG/SO/AC Chair to inform them of the Friday session, and request that they nominate members who are active WG participants for the available slots. As a reminder, each GNSO Stakeholder Group may nominate up to 6 active WG members, and funding for this specific initiative is limited to one hotel night each (for 6 members) or a maximum of two nights (if fewer than 6). As such, a participant’s airfare and additional accommodation costs will have to be funded from each SG’s general travel allocations or other sources.

For those who are not able to join the meeting in person, remote participation facilities will be available, and the facilitators will be briefed to ensure that remote participants are as actively involved as those who will be present in person.

Please let me know if you plan to attend (subject to your obtaining the necessary travel/funding approval, if applicable) as soon as possible.

Thanks and cheers
Mary

Mary Wong
Senior Policy Director
Internet Corporation for Assigned Names & Numbers (ICANN)
Telephone: +1 603 574 4892
Email: mary.wong at icann.org<mailto:mary.wong at icann.org>




_______________________________________________
Gnso-igo-ingo-crp mailing list
Gnso-igo-ingo-crp at icann.org<mailto:Gnso-igo-ingo-crp at icann.org>
https://mm.icann.org/mailman/listinfo/gnso-igo-ingo-crp

_______________________________________________
Gnso-igo-ingo-crp mailing list
Gnso-igo-ingo-crp at icann.org<mailto:Gnso-igo-ingo-crp at icann.org>
https://mm.icann.org/mailman/listinfo/gnso-igo-ingo-crp

________________________________

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.