Re: [gnso-cc-idn-tld-rg] Start of ccTLD IDN Questions - Council Rework Group

[steflai@xxxxxxxxxxxxx]

HI Chuck,

Monday and Friday would be best for me, but I can try to work around  
the other times.
Thanks,

Stefanie

----- Message from olgac@xxxxxxxxxxxxxxx ---------
    Date: Thu, 29 Nov 2007 17:07:30 -0300
    From: Olga Cavalli <olgac@xxxxxxxxxxxxxxx>
Reply-To: Olga Cavalli <olgac@xxxxxxxxxxxxxxx>
 Subject: Re: [gnso-cc-idn-tld-rg] Start of ccTLD IDN Questions -  
Council Rework Group
      To: "Gomes, Chuck" <cgomes@xxxxxxxxxxxx>
      Cc: cc-IDN Rework Group <gnso-cc-idn-tld-rg@xxxxxxxxx>


> Chuck,
> thanks for your email.
> For me monday, wednesday or thursday work fine, time of the three options
> are ok.
> Only one comment, 0800 calls do not work from Argentina, so when we decide
> date and time I can send my telephone to be contacted.
> Regards
> Olga
>
>
> 2007/11/29, Gomes, Chuck <cgomes@xxxxxxxxxxxx>:
> >  Thanks to each of you for volunteering to be a part of the GNSO Council
> > Group tasked with reviewing the draft GNSO comments to the ccNSO/GAC Issues
> > Paper on IDN ccTLDs.  For your information, here is the current list of
> > group members:
> >
> >
> > Belal Beirm, BC
> >
> > Edmon Chung, RyC
> >
> > Olga Cavalli, Nom Com Rep
> >
> > Avri Doria, NomCom Rep
> >
> > Chuck Gomes, Chair
> >
> > Adrian Kinderis, RC
> >
> > Stefanie Lai, NCUC
> >
> >
> >
> > To get us started I would like to propose the following:
> >
> >
> >
> > Proposed Approach for Reworking GNSO Response to ccNSO/GAC Issues Paper on
> > IDN ccTLDs:
> >
> >
> >
> >    1. Individual review of existing draft GNSO document by all group
> >    members
> >    2. Initial teleconference call for the following  purposes:
> >       1. Identifying areas in the existing draft GNSO document that
> >       need further work
> >       2. Identifying issues that we should possibly address that are
> >       not contained in the Issues Paper or in our document
> >       3. Developing a work plan for the group including:
> >
> >                                                                i.      An
> > estimated time frame
> >
> >                                                              ii.     
> >    Possible
> > ways of organizing our work (e.g., assigning different issues for group
> > members to take the lead on or handling them as a group)
> >
> >    1. Email list discussion of areas identified in items 2.a and 2.b.
> >    2. Additional teleconference calls as needed.
> >
> > Please provide any feedback you have on this approach.  We may modify it
> > however we decide as a group.
> >
> > To get us started, I would like to schedule an initial teleconference for
> > next week.  Please communicate on this list which of the following options
> > would work for you.
> >
> > 1. Monday, 3 December at 13:00 UTC
> >
> >     [5 am PST (California), 8 am EST (New York), 10 am ART (Buenos
> > Aires), 2 pm CET (Brussels), 3 pm EET (Amman), 9 pm HKT (Hong Kong)]
> >
> > 2. Tuesday, 4 December at 14:00 UTC
> >
> >     [6 am PST (California), 9 am EST (New York), 11 am ART (Buenos
> > Aires), 3 pm CET (Brussels), 4 pm EET (Amman), 10 pm HKT (Hong Kong)]
> >
> > 3. Thursday, 6 December at 13:00 UTC
> >
> >     [5 am PST (California), 8 am EST (New York), 10 am ART (Buenos
> > Aires), 2 pm CET (Brussels), 3 pm EET (Amman), 9 pm HKT (Hong Kong)]
> >
> > 4. Friday, 7 December at 14:00 UTC
> >
> >     [6 am PST (California), 9 am EST (New York), 11 am ART (Buenos
> > Aires), 3 pm CET (Brussels), 4 pm EET (Amman), 10 pm HKT (Hong Kong)]
> >
> > Chuck Gomes
> >
> > "This message is intended for the use of the individual or entity to which
> > it is addressed, and may contain information that is privileged,
> > confidential and exempt from disclosure under applicable law. Any
> > unauthorized use, distribution, or disclosure is strictly prohibited. If you
> > have received this message in error, please notify sender immediately and
> > destroy/delete the original transmission."

----- End message from olgac@xxxxxxxxxxxxxxx -----