<<<
Chronological Index
>>> <<<
Thread Index
>>>
[jig] RE: JIG Public session in Beijing
- To: "'Glen de Saint Géry'" <Glen@xxxxxxxxx>, "'Bart Boswinkel'" <bart.boswinkel@xxxxxxxxx>, "'Julia Charvolen'" <julia.charvolen@xxxxxxxxx>
- Subject: [jig] RE: JIG Public session in Beijing
- From: "Edmon Chung" <edmon@xxxxxxxxxxxxx>
- Date: Wed, 27 Mar 2013 07:25:11 +0800
Ah ok.
In that case, suggest going back to the suggestion during our call yesterday,
to split up the session:
1. Public session (on Universal Acceptance of IDN TLDs): Monday 16:00-17:00
(moved up 30min from original slot)
2. WG session (also open): Wednesday before the 2 council meetings 14:00-15:00
Edmon
> -----Original Message-----
> From: Glen de Saint Géry [mailto:Glen@xxxxxxxxx]
> Sent: Wednesday, March 27, 2013 1:16 AM
> To: Bart Boswinkel; Edmon Chung; Julia Charvolen
> Cc: 'Jian Zhang'; gnso-secs@xxxxxxxxx
> Subject: RE: JIG Public session in Beijing
>
> Dear Edmon,
>
> Yes, it will overlap with the GNSO Council session and the Council leadership
> has requested that there be no overlapping sessions.
> I will refer your request for meeting changes to the name and the day to the
> meeting team.
>
> Thanks so much .
> Kind regards,
> Glen
>
> -----Message d'origine-----
> De : Bart Boswinkel
> Envoyé : mardi 26 mars 2013 17:53
> À : Edmon Chung; Julia Charvolen; Glen de Saint Géry Cc : 'Jian Zhang';
> jig@xxxxxxxxx Objet : Re: JIG Public session in Beijing
>
> Hi Edmon,
> This wil overlap with the ccNSO meeting and Council meeting on Wednesday
> Kind regards, Bart
>
>
> On 3/26/13 5:49 PM, "Edmon Chung" <edmon@xxxxxxxxxxxxx> wrote:
>
> > Hi Julia, Bart and Glen,
> >
> >Following up with the room allocation/schedule for the JIG sessions in
> >Beijing from the discussions on the call.
> >
> >Currently the session is scheduled for:
> >Joint ccNSO / GNSO IDN Working Group (JIG)
> >Date: 8 April 2013 - 16:30 - 18:15
> >Room: Function 8AB
> >
> >Currently, the session on Monday overlaps with the APRALO Roundtable on
> >IDN TLDs.
> >I wonder if it is possible to move it to:
> >
> >WEDNESDAY, 10 April
> >1530-1700 in Function 8AB
> >
> >Also, as sent earlier in the email to the WG mailing list and discussed
> >in the call, would like to change the session title and description to:
> >
> >===============================================================
> ========
> >Acceptance of IDN TLDs: Community Recommendations for ICANN Actions
> >===============================================================
> ========
> >
> >Based on practical operational experience, not all systems (e.g.
> >browsers, spam filters, registration databases, user profiles, ISPs,
> >etc.) work seamlessly when new TLDs are added. Users may experience
> >failures in resolution or other issues with newer TLDs, which in turn
> >impacts consumer trust on the DNS. The issue of the Universal
> >Acceptance of TLDs (Top-Level Domains) is critically related to the
> >introduction of new gTLDs, as well as the introduction of IDN ccTLDs.
> >
> >This session will focus on the 4 key recommendations from the working
> >group to address the issue:
> >
> >A. Recommend IDN TLD operators (including IDN ccTLD, IDN gTLD and IDN
> >gTLD Accredited Registrars) to support Universal Acceptance of IDN TLDs
> >in their own systems
> >
> >B. Allocate specific resources for the advocacy of Universal Acceptance
> >beyond the development of informational materials and toolkits
> >
> >C. Development of informative reference materials for new IDN TLDs
> >(including gTLD and ccTLD) to handle issues of Universal Acceptance
> >
> >D. Direct efforts, lead by staff, with the participation from the
> >community, for further studies to investigate the scope of the issue
> >and what other services or actions could be taken by ICANN to support
> >the Universal Acceptance of IDN TLDs beyond outreach and awareness
> >campaigns
> >
> >Who should attend?
> >Registrars and Registries, New gTLD Applicants, New IDN ccTLDs.
> >
> >===============================================================
> ========
> >
> >Edmon
> >
> >
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2013.0.2904 / Virus Database: 2641/6199 - Release Date: 03/23/13
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|