Fair points made, Farzaneh.  Indeed, the CSG has stated similar concerns in the past, including in the attached letter from February. 

 

From: soac-leaders-icann59-bounces@icann.org [mailto:soac-leaders-icann59-bounces@icann.org] On Behalf Of farzaneh badii
Sent: Tuesday, April 4, 2017 10:22 AM
To: David Olive
Cc: soac-leaders-icann59@icann.org
Subject: Re: [Soac-leaders-icann59] Reminder and Agenda - ICANN59 Planning Call - Wednesday, 5 April 2017 at 14:00 UTC

 

Thank you David. 

 

I will attend the call, but I would like to raise a point here which I will reiterate during the call too

 

corss -community sessions: From my limited observation I have gathered that, cross-community sessions are not really cross-community . The group that submits the request normally decides on the format, who to invite and what to discuss. If that is how we want to hold such meetings, we can't call them cross-community. It is misleading. 

 

we could make a change in format: the submission has to be made by at least to members of different SO/ACs. They should have a planning team open to anyone who would like to join. Does this sound impossible? Has it been done before? Do we even need such sessions? 

 

 

 

Best 

 

Farzaneh 


Farzaneh

 

On Tue, Apr 4, 2017 at 10:04 AM, David Olive <david.olive@icann.org> wrote:

Dear Community Leaders:

 

Here is the draft agenda for our call on Wednesday :

 

ICANN59 SO/AC Schedule Planning Group

5 April 1400 – 1500 UTC

 

PROPOSED AGENDA

 

  1. Welcome and Introduction - David Olive
  2. Opening Remarks – ICANN59 Community Planning Group – Sally Costerton
  3. Update ICANN59 Program – Nick Tomasso
  4. Schedule Production Timeline & Process Review – Tanzanica King
  5. Block Schedule Overview – Tanzanica King

                                - ICANN59 Preliminary Block Schedule

  1. Current Requests – Tanzanica King/Nick Tomasso

                                - Jeff Neuman - Geographic Names Working Group/new gTLD Subsequent Round PDP

                                -Other requests to date or expected

                                -Outreach sessions at ICANN59

       7.     Process/Forms for Cross Community Discussion Sessions/Topics

                                - Afternoon Sessions

8.       AOB 

  1. Closing Remarks and Next Call – David Olive  

 

REMINDER:

The call scheduled for Wednesday, 5 April 2017 at 14:00 UTC.

 

CALL DETAILS:

 

Conference Provider: Adigo - Conference Number: U.S. / Canada: 1-800-550-6865 – Conference ID: 2569

For International numbers, please refer to: http://adigo.com/ICANN/[adigo.com]

Adobe Connect: https://participate.icann.org/icann-soac

Additional information:

  1. This call will be recorded and transcribed
  2. If you cannot attend, please provide an alternate (provide e-mail address off-list)
  3. If you would like a dial out, please provide the phone number, off list
  4. If you would like assistance locating an international number, please send me a request, off list.

 

Regards,   David

 

David A. Olive
Senior Vice President

Policy Development Support
Managing Director, ICANN Regional Headquarters –Istanbul

Internet Corporation for Assigned Names and Numbers (ICANN)

Direct Line: +90.212.999.6212
Mobile:       + 1. 202.341.3611
Mobile:       +90.533.341.6550

 


_______________________________________________
Soac-leaders-icann59 mailing list
Soac-leaders-icann59@icann.org
https://mm.icann.org/mailman/listinfo/soac-leaders-icann59

 

This message and its attachments may contain legally privileged or confidential information. It is intended solely for the named addressee. If you are not the addressee indicated in this message (or responsible for delivery of the message to the addressee), you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments that does not relate to the official business of Twenty-First Century Fox, Inc. or its subsidiaries must be taken not to have been sent or endorsed by any of them. No representation is made that this email or its attachments are without defect.