ICANN/GNSO GNSO Email List Archives

[council]


<<< Chronological Index >>>    <<< Thread Index >>>

RE: [council] Topics for Board/Staff/GNSO Dinner Meeting in Nairobi


The topics for the joint GAC/GNSO meeting are New gTLDs including the EOI and 
the AoC.  Under New gTLDs, the ongoing delays have not been specifically 
mentioned but we could bring it up in the discussion if we wanted to.  Aren't 
working with Rosemary and Bill on that meeting?

Chuck 

> -----Original Message-----
> From: KnobenW@xxxxxxxxxx [mailto:KnobenW@xxxxxxxxxx] 
> Sent: Wednesday, February 10, 2010 5:01 AM
> To: adrian@xxxxxxxxxxxxxxxxxx; wendy@xxxxxxxxxxx; 
> stephane.vangelder@xxxxxxxxx
> Cc: Gomes, Chuck; council@xxxxxxxxxxxxxx
> Subject: AW: [council] Topics for Board/Staff/GNSO Dinner 
> Meeting in Nairobi
> 
> Supported.
> Isn't that an item for the joint GNSO/GAC meeting in Nairobi, too? 
> 
> Kind regards
> Wolf-Ulrich 
> 
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: owner-council@xxxxxxxxxxxxxx 
> [mailto:owner-council@xxxxxxxxxxxxxx] Im Auftrag von Adrian Kinderis
> Gesendet: Dienstag, 9. Februar 2010 23:58
> An: Wendy Seltzer; Stéphane Van Gelder
> Cc: Gomes, Chuck; GNSO Council List
> Betreff: RE: [council] Topics for Board/Staff/GNSO Dinner 
> Meeting in Nairobi
> 
> 
> I support Wendy here.
> 
> Adrian Kinderis
> 
> 
> -----Original Message-----
> From: owner-council@xxxxxxxxxxxxxx 
> [mailto:owner-council@xxxxxxxxxxxxxx] On Behalf Of Wendy Seltzer
> Sent: Wednesday, 10 February 2010 1:10 AM
> To: Stéphane Van Gelder
> Cc: Gomes, Chuck; GNSO Council List
> Subject: Re: [council] Topics for Board/Staff/GNSO Dinner 
> Meeting in Nairobi
> 
> 
> I agree, and would support the stronger phrasing.  I think we 
> need to help make management and Board more conscious of the 
> risks to the organization of continued delay.
> 
> --Wendy
> 
> Stéphane Van Gelder wrote:
> > Hi Chuck,
> > 
> > The main area of worry that I see remains the ever-delaying 
> new gTLD program.
> > 
> > Would it be appropriate to suggest a topic along those 
> lines (perhaps something like: "are delays to the new gTLD 
> program hurting it and ICANN as a whole", or something more 
> neutral like "suggestions to solve remaining overarching 
> issues in 2010 and avoid further delays spilling into 2011")?
> > 
> > I realize some may not feel at ease being upfront about 
> this. However, I do think GNSO Principle A is getting more 
> and more often overlooked as time passes and that reminders 
> that the GNSO's first focus was on the new gTLDs being 
> introduced in a "orderly, timely and predictable way", the 
> operative words here being timely and predictable, are warranted.
> > 
> > I'm sure we all realise that for prospective applicants, 
> the current process is neither timely nor predictable...
> > 
> > Thanks,
> > 
> > Stéphane
> > 
> > Le 9 févr. 2010 à 02:40, Gomes, Chuck a écrit :
> > 
> >> I don't believe that there were any responses to this last 
> week.  It would be helpful to receive some suggestions before 
> our 18 Feb meeting so that we can hopefully finallize the topics then.
> >>  
> >> Chuck
> >>
> >> From: owner-council@xxxxxxxxxxxxxx 
> >> [mailto:owner-council@xxxxxxxxxxxxxx] On Behalf Of Gomes, Chuck
> >> Sent: Monday, February 01, 2010 6:17 PM
> >> To: GNSO Council List
> >> Subject: [council] Topics for Board/Staff/GNSO Dinner Meeting in 
> >> Nairobi
> >>
> >> An agenda item for the 18 Feb Council meeting will be to 
> finalize discussion topics for the Board/Staff/GNSO Dinner 
> Meeting in Nairobi,  In preparation for that, I would like to 
> request that Councilors propose topics this week.  Discussion 
> of proposed topics is also encouraged on the list.
> >>  
> >> Chuck
> > 
> > 
> 
> 
> --
> Wendy Seltzer -- wendy@xxxxxxxxxxx
> phone: +1.914.374.0613
> Fellow, Silicon Flatirons Center at University of Colorado 
> Law School Fellow, Berkman Center for Internet & Society at 
> Harvard University http://cyber.law.harvard.edu/seltzer.html
> http://www.chillingeffects.org/
> https://www.torproject.org/
> 
> 




<<< Chronological Index >>>    <<< Thread Index >>>