[council] Re: Joint Council meeting - Delhi

[Avri Doria <avri@xxxxxxx>]

Dear Chris,

The GNSO council appreciates and formally accepts the ccNSO's  
invitation for a joint meeting of the two councils to discuss our  
respective communications to the Board.
The GSNO council is prepared to meet during the time suggested, and  
further suggests 12:30 on Monday as a starting time.  As you and I  
have discussed separately, while this meeting will be opened to  
observers, conversation will be limited to the council members and  
their liaisons.  We further accept the suggestion that this meeting be  
independently moderated.
Best Regards,

Avri Doria


On 22 Jan 2008, at 09:00, Chris Disspain wrote:

> 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@xxxxxxxxxxx
> 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.