Hi, I have responded to Chris that I would reply with a formal response shortly, but noted that in general I thought there was agreement in the council for such a meeting. I did ask him whether this was to be an open or closed meeting, noting that all of our meetings were generally open but as this was his invitation, I wanted to check. I will pass on his response once I get it. I suggest a 48 hour call on this decision: i.e would anyone who objects to my sending a response formally accepting this invitation with a suggestion of a meeting time of 1230 please respond to the list. Thanks a. Begin forwarded message:
From: "Chris Disspain" <ceo@auda.org.au> Date: 22 January 2008 09:00:21 GMT+01:00 To: "'Avri Doria'" <avri@acm.org> Cc: "ccNSO Council" <ccnso-council@icann.org> Subject: Joint Council meeting - Delhi
Hi Avri,
Further to the ccNSO letter to the ICANN Board of yesterday, I write to formally invite the full GNSO council to a meeting with the full ccNSO Council to discuss the GNSO resolution of 3 January and our response, the ccPDP and the fast track.
I hope that GNSO Council is willing to have this meeting, which, we have suggested in our letter should be independently moderated. If so, I suspect that it is timing that will be challenging. As you know it is intended that the IDNC Working Group will ‘host’ an open session on Monday afternoon in Delhi to discuss where the WG is up to and to get as much input as possible. I think that we can run that workshop from, latest, 3.00 pm to 6.00 pm. On that basis, would the GNSO Council be prepared to meet with the ccNSO Council commencing at some time between Noon and 1.00 pm?
Cheers,
Chris Disspain CEO - auDA Australia's Domain Name Administrator ceo@auda.org.au www.auda.org.au
Important Notice - This email may contain information which is confidential and/or subject to legal privilege, and is intended for the use of the named addressee only. If you are not the intended recipient, you must not use, disclose or copy any part of this email. If you have received this email by mistake, please notify the sender and delete this message immediately. Please consider the environment before printing this email.