May 2016 - council - lists.icann.org

Fwd: Relocating ICANN57 - Blog by Akram Atallah
by James M. Bladel May 17, 2016

May 17, 2016

Councilors, FYI. Sent via iPhone. Blame Siri. Begin forwarded message: From: David Olive <david.olive(a)icann.org<mailto:david.olive@icann.org>> Date: May 17, 2016 at 21:13:35 GMT+2 To: "jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>" <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>>, "katrina(a)nic.lv<mailto:katrina@nic.lv>" <katrina(a)nic.lv<mailto:katrina@nic.lv>>, "oscar(a)lacnic.net<mailto:oscar@lacnic.net>" <oscar(a)lacnic.net<mailto:oscar@lacnic.net>>, "louie(a)louie.net<mailto:louie@louie.net>" <louie(a)louie.net<mailto:louie@louie.net>>, "patrik(a)frobbit.se<mailto:patrik@frobbit.se>" <patrik(a)frobbit.se<mailto:patrik@frobbit.se>>, "Thomas.Schneider(a)bakom.admin.ch<mailto:Thomas.Schneider@bakom.admin.ch>" <Thomas.Schneider(a)bakom.admin.ch<mailto:Thomas.Schneider@bakom.admin.ch>>, "alan.greenberg(a)mcgill.ca<mailto:alan.greenberg@mcgill.ca>" <alan.greenberg(a)mcgill.ca<mailto:alan.greenberg@mcgill.ca>>, "tsinha(a)umd.edu<mailto:tsinha@umd.edu>" <tsinha(a)umd.edu<mailto:tsinha@umd.edu>>, "bverd(a)verisign.com<mailto:bverd@verisign.com>" <bverd(a)verisign.com<mailto:bverd@verisign.com>>, "gregshatanipc(a)gmail.com<mailto:gregshatanipc@gmail.com>" <gregshatanipc(a)gmail.com<mailto:gregshatanipc@gmail.com>>, "Michele(a)blacknight.com<mailto:Michele@blacknight.com>" <Michele(a)blacknight.com<mailto:Michele@blacknight.com>>, "pdiaz(a)pir.org<mailto:pdiaz@pir.org>" <pdiaz(a)pir.org<mailto:pdiaz@pir.org>>, "ncsg(a)tapani.tarvainen.info<mailto:ncsg@tapani.tarvainen.info>" <ncsg(a)tapani.tarvainen.info<mailto:ncsg@tapani.tarvainen.info>>, "rafik.dammak(a)gmail.com<mailto:rafik.dammak@gmail.com>" <rafik.dammak(a)gmail.com<mailto:rafik.dammak@gmail.com>>, "rudi.vansnick(a)isoc.be<mailto:rudi.vansnick@isoc.be>" <rudi.vansnick(a)isoc.be<mailto:rudi.vansnick@isoc.be>>, "tonyarholmes(a)btinternet.com<mailto:tonyarholmes@btinternet.com>" <tonyarholmes(a)btinternet.com<mailto:tonyarholmes@btinternet.com>>, "cwilson(a)21cf.com<mailto:cwilson@21cf.com>" <cwilson(a)21cf.com<mailto:cwilson@21cf.com>>, "mcknight.glenn(a)gmail.com<mailto:mcknight.glenn@gmail.com>" <mcknight.glenn(a)gmail.com<mailto:mcknight.glenn@gmail.com>>, "hilaliaziz(a)yahoo.fr<mailto:hilaliaziz@yahoo.fr>" <hilaliaziz(a)yahoo.fr<mailto:hilaliaziz@yahoo.fr>>, "hcarrascob(a)gmail.com<mailto:hcarrascob@gmail.com>" <hcarrascob(a)gmail.com<mailto:hcarrascob@gmail.com>>, "ocl(a)gih.com<mailto:ocl@gih.com>" <ocl(a)gih.com<mailto:ocl@gih.com>>, "siranush_vardanyan(a)hotmail.com<mailto:siranush_vardanyan@hotmail.com>" <siranush_vardanyan(a)hotmail.com<mailto:siranush_vardanyan@hotmail.com>> Cc: Global Leadership <global_leadership(a)icann.org<mailto:global_leadership@icann.org>>, Melissa King <melissa.king(a)icann.org<mailto:melissa.king@icann.org>>, Duncan Burns <duncan.burns(a)icann.org<mailto:duncan.burns@icann.org>>, Nick Tomasso <nick.tomasso(a)icann.org<mailto:nick.tomasso@icann.org>> Subject: Relocating ICANN57 - Blog by Akram Atallah Dear Community Leaders: This blog will be posted to the ICANN website in a few hours. We are sharing this note with you in advance of the public announcement. Please do not circulate this information until after it is posted ( 0100 UTC 18 May /1800 PST, 17 May) Best regards, David —————————————————————- Relocating ICANN57 By Akram Atallah Earlier this year, we announced that ICANN56 was going to be relocated from Panama City, Panama, to Helsinki, Finland, due to concerns related to the Zika virus. Following a great deal of internal debate and discussion, and taking into consideration the continued spread of Zika, we have decided that we will be relocating ICANN57 from San Juan, Puerto Rico, to Hyderabad, India. Due to highly limited space availabilities, this relocation has necessitated changing the date of the meeting from 29 October – 4 November 2016, to 3 – 9 November 2016. We did not arrive at this decision easily. We would much rather remain in Puerto Rico – the excellent location we had originally chosen. Moving the meeting venue creates a lot of additional work and challenges, and we understand and recognize that moving an ICANN meeting affects many groups within the community. However, we have come to the conclusion that we must postpone going to Puerto Rico after a lengthy discussion with and feedback from SO/AC leaders, the Board, and within our management team. This decision was based on available research and information and the fact that Puerto Rico has declared a state of emergency due to the ongoing Zika virus outbreak. We believe that the Zika virus poses a significant enough threat that we need to postpone going to Puerto Rico for the health and safety of our community and our ICANN team, just as we had to postpone ICANN52 and relocate from Marrakech to Singapore due to the Ebola virus outbreak in 2014. Choosing a location for an ICANN meeting that meets the needs of the community is an incredibly complex task. Few venues in the world are able to satisfy all of our requirements<https://meetings.icann.org/en/host>, especially as the community continues to grow and more and more sessions are held in parallel. San Juan offered outstanding facilities capable of hosting a successful ICANN meeting, which is why we originally selected it as the location for ICANN57. In choosing an alternate location for ICANN57, we explored options all around the globe. A North American venue would have been our preference given our meeting rotation schedule, but due to the time of the year, a very busy conference season and our extremely demanding requirements, we weren’t presented with any ideal options. Fortunately, the Government of India offered to host ICANN57. We are very grateful for their proposal and their willingness to meet our extensive requirements in such a short amount of time. We are therefore pleased to announce that ICANN57 will be held at the Hyderabad International Convention Centre<http://www.hicc.com/>, a state-of-the-art convention center capable of handling an ICANN meeting’s extensive conference space and network infrastructure requirements. Hyderabad itself is home to a booming tech sector, earning itself the nickname “Cyberabad,” and we’re looking forward to hosting a successful ICANN meeting in this wonderful city. We fully understand that by relocating ICANN57, regional organizations and stakeholders will miss out on an opportunity to meet with their communities, as well as a chance to reach out to new community members. We are postponing not cancelling this meeting and we will return to the region as soon as possible. ICANN’s Global Stakeholder Engagement (GSE) team will be working closely with the leaders of the different stakeholder groups in the region to try to mitigate the impact of this decision. We will be providing our increased support to meetings and events scheduled in the region, remote hubs in the region’s strategic points during the next two ICANN meetings, read-out sessions, capacity building webinars, activities in our Montevideo engagement center, support for our community to attend relevant regional and global events, and providing as much senior management and Board support on the ground as required. I want to stress again that the decision to relocate ICANN57 was not made lightly, and that we feel it is extremely unfortunate the situation required us to postpone the meeting in San Juan. We understand how important it is to maintain the global rotation of ICANN meetings, as it allows local and regional communities to attend and participate, and we are committed to returning to Puerto Rico and Panama City as soon as possible, however the welfare of community members and staff is our top priority. We thank you all for understanding this difficult situation and the choice we have had to make. ——————————————— David A. Olive Senior Vice President, Policy Development Support General Manager, ICANN Regional Headquarters –Istanbul Hakki Yeten Cad. Selenium Plaza No:10/C K:10 34349 Fulya, Besiktas, 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 Email: david.olive(a)icann.org<mailto:david.olive@icann.org> www.icann.org<http://www.icann.org>

2 1

Fwd: ICANN56 - Schedule DRAFTv3.3
by Austin, Donna May 16, 2016

May 16, 2016

All The latest on Helsinki planning below. Let me know if you have any questions. Donna Sent from my iPhone Begin forwarded message: From: "Tanzanica S. King" <tanzanica.king(a)icann.org<mailto:tanzanica.king@icann.org>> Date: May 16, 2016 at 12:20:58 AM GMT+1 To: "Austin, Donna" <Donna.Austin(a)neustar.biz<mailto:Donna.Austin@neustar.biz>>, "Thomas.Schneider(a)bakom.admin.ch<mailto:Thomas.Schneider@bakom.admin.ch>" <Thomas.Schneider(a)bakom.admin.ch<mailto:Thomas.Schneider@bakom.admin.ch>>, "katrina(a)nic.lv<mailto:katrina@nic.lv>" <katrina(a)nic.lv<mailto:katrina@nic.lv>>, "alejandra.reynoso(a)cctld.gt<mailto:alejandra.reynoso@cctld.gt>" <alejandra.reynoso(a)cctld.gt<mailto:alejandra.reynoso@cctld.gt>>, "vgreimann(a)key-systems.net<mailto:vgreimann@key-systems.net>" <vgreimann(a)key-systems.net<mailto:vgreimann@key-systems.net>>, "ondouglas(a)gmail.com<mailto:ondouglas@gmail.com>" <ondouglas(a)gmail.com<mailto:ondouglas@gmail.com>>, "aftab.siddiqui(a)gmail.com<mailto:aftab.siddiqui@gmail.com>" <aftab.siddiqui(a)gmail.com<mailto:aftab.siddiqui@gmail.com>>, "tsinha(a)umd.edu<mailto:tsinha@umd.edu>" <tsinha(a)umd.edu<mailto:tsinha@umd.edu>>, "bverd(a)verisign.com<mailto:bverd@verisign.com>" <bverd(a)verisign.com<mailto:bverd@verisign.com>>, "patrik(a)frobbit.se<mailto:patrik@frobbit.se>" <patrik(a)frobbit.se<mailto:patrik@frobbit.se>>, "alan.greenberg(a)mcgill.ca<mailto:alan.greenberg@mcgill.ca>" <alan.greenberg(a)mcgill.ca<mailto:alan.greenberg@mcgill.ca>>, "berandondeh(a)yahoo.com<mailto:berandondeh@yahoo.com>" <berandondeh(a)yahoo.com<mailto:berandondeh@yahoo.com>>, "Ana.Neves(a)fct.pt<mailto:Ana.Neves@fct.pt>" <Ana.Neves(a)fct.pt<mailto:Ana.Neves@fct.pt>>, "tom(a)acig.com.au<mailto:tom@acig.com.au>" <tom(a)acig.com.au<mailto:tom@acig.com.au>>, James Bladel <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>> Cc: Nick Tomasso <nick.tomasso(a)icann.org<mailto:nick.tomasso@icann.org>>, "chris(a)disspain.id.au<mailto:chris@disspain.id.au>" <chris(a)disspain.id.au<mailto:chris@disspain.id.au>>, David Olive <david.olive(a)icann.org<mailto:david.olive@icann.org>>, Sally Costerton <sally.costerton(a)icann.org<mailto:sally.costerton@icann.org>>, Teresa Elias <teresa.elias(a)icann.org<mailto:teresa.elias@icann.org>>, "Michelle Bright" <michelle.bright(a)icann.org<mailto:michelle.bright@icann.org>>, Melissa King <melissa.king(a)icann.org<mailto:melissa.king@icann.org>>, Vinciane Koenigsfeld <vinciane.koenigsfeld(a)icann.org<mailto:vinciane.koenigsfeld@icann.org>>, Heidi Ullrich <Heidi.Ullrich(a)icann.org<mailto:Heidi.Ullrich@icann.org>>, Gisella Gruber <Gisella.Gruber(a)icann.org<mailto:Gisella.Gruber@icann.org>>, "Olof Nordling" <olof.nordling(a)icann.org<mailto:olof.nordling@icann.org>>, Julia Charvolen <julia.charvolen(a)icann.org<mailto:julia.charvolen@icann.org>>, Marika Konings <marika.konings(a)icann.org<mailto:marika.konings@icann.org>>, Glen de Saint Géry <Glen(a)icann.org<mailto:Glen@icann.org>>, Bart Boswinkel <bart.boswinkel(a)icann.org<mailto:bart.boswinkel@icann.org>>, Joke Braeken <joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>>, "gac-leadership(a)icann.org<mailto:gac-leadership@icann.org>" <gac-leadership(a)icann.org<mailto:gac-leadership@icann.org>>, Maya Saito <maya.saito(a)icann.org<mailto:maya.saito@icann.org>>, Steve Sheng <steve.sheng(a)icann.org<mailto:steve.sheng@icann.org>>, Julie Hedlund <julie.hedlund(a)icann.org<mailto:julie.hedlund@icann.org>> Subject: ICANN56 - Schedule DRAFTv3.3 Hi All, The latest schedule is attached and updated on the community wiki page<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…>. Block Schedule In an effort to increase the time you have available to meet, I made a few changes to the block schedule format (some of which you may have already noticed in the last version that went out) : - The afternoon coffee break has been reduced to 15 min - Day now ends at 1830 instead of 1800 and all afternoon time slots are 90 min - Lunch is scheduled from 1200-1330 daily, however a minimum of just 60 min is required, therefore you have the option to schedule morning sessions through 12:30 if needed. Slight changes to some of your session times have also been made to match the available time blocks and breaks, but given the above option, you may want to make further adjustments to take advantage of the additional time offered. Proposed Layout for CC Topic Sessions I believe the consensus for the cross-community discussions in the afternoons is for these to be topic based sessions for any SO/AC - type [2] as described in Patrik’s email. One SO/AC is the host/leader for each session, and these have been identified on the latest draft of the schedule. Staff is reaching out to session leaders to collect description/agenda details for each topic and we will share those on this thread as soon as they become available. To Donna’s question below about CCWG and ICANN Accountability – I’ve noted ASO as a potential leader for this topic, but interest came from ASO, ALAC, and ccNSO. Please share any thoughts you might have on the intent for this topic, and ultimately, who will host the discussion. Evening Activities We started to receive a number of requests for cocktails in the evenings. In the spirit of cross community interaction and networking opportunities, we’ve decided the best approach is to have a reception for all delegates every evening. Monday: 1830-2000 Local Host Reception (Location: City Hall) Tuesday: 1830-1930 President’s Reception Wednesday: 1830-1930 Chairman’s Reception Thursday: 1830-1930 Wrap-Up Reception Next Steps An invitation will go out to SO/AC support staff tomorrow so they can submit your final sessions into our Event Management Scheduling Software (EMS). All submissions will be due over the next two weeks and a final schedule will be posted no later than 6 June. Please let me know if you have any questions - Thanks! Tanzanica ________________________________ Tanzanica S. King Sr. Manager, Meeting Strategy and Design ICANN Office +1 310 301 5800 Mobile +1 310 995 3038 Email king(a)icann.org<mailto:king@icann.org> www.icann.org<http://www.icann.org> From: Donna Austin <donna.austin(a)neustar.biz<mailto:donna.austin@neustar.biz>> Date: Mon, 9 May 2016 at 16:47 To: "Tanzanica S. King" <tanzanica.king(a)icann.org<mailto:tanzanica.king@icann.org>>, "Thomas.Schneider(a)bakom.admin.ch<mailto:Thomas.Schneider@bakom.admin.ch>" <Thomas.Schneider(a)bakom.admin.ch<mailto:Thomas.Schneider@bakom.admin.ch>>, "katrina(a)nic.lv<mailto:katrina@nic.lv>" <katrina(a)nic.lv<mailto:katrina@nic.lv>>, "alejandra.reynoso(a)cctld.gt<mailto:alejandra.reynoso@cctld.gt>" <alejandra.reynoso(a)cctld.gt<mailto:alejandra.reynoso@cctld.gt>>, "vgreimann(a)key-systems.net<mailto:vgreimann@key-systems.net>" <vgreimann(a)key-systems.net<mailto:vgreimann@key-systems.net>>, "ondouglas(a)gmail.com<mailto:ondouglas@gmail.com>" <ondouglas(a)gmail.com<mailto:ondouglas@gmail.com>>, "aftab.siddiqui(a)gmail.com<mailto:aftab.siddiqui@gmail.com>" <aftab.siddiqui(a)gmail.com<mailto:aftab.siddiqui@gmail.com>>, "tsinha(a)umd.edu<mailto:tsinha@umd.edu>" <tsinha(a)umd.edu<mailto:tsinha@umd.edu>>, "bverd(a)verisign.com<mailto:bverd@verisign.com>" <bverd(a)verisign.com<mailto:bverd@verisign.com>>, "patrik(a)frobbit.se<mailto:patrik@frobbit.se>" <patrik(a)frobbit.se<mailto:patrik@frobbit.se>>, Alan Greenberg <alan.greenberg(a)mcgill.ca<mailto:alan.greenberg@mcgill.ca>>, Beran Dondeh <berandondeh(a)yahoo.com<mailto:berandondeh@yahoo.com>>, Ana Neves <Ana.Neves(a)fct.pt<mailto:Ana.Neves@fct.pt>>, Tom Dale <tom(a)acig.com.au<mailto:tom@acig.com.au>>, James Bladel <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>> Cc: Nick Tomasso <Nick.tomasso(a)icann.org<mailto:Nick.tomasso@icann.org>>, "chris(a)disspain.id.au<mailto:chris@disspain.id.au>" <chris(a)disspain.id.au<mailto:chris@disspain.id.au>>, David Olive <david.olive(a)icann.org<mailto:david.olive@icann.org>>, Sally Costerton <sally.costerton(a)icann.org<mailto:sally.costerton@icann.org>>, Teresa Elias <teresa.elias(a)icann.org<mailto:teresa.elias@icann.org>>, Michelle Bright <michelle.bright(a)icann.org<mailto:michelle.bright@icann.org>>, Melissa King <melissa.king(a)icann.org<mailto:melissa.king@icann.org>>, Vinciane Koenigsfeld <vinciane.koenigsfeld(a)icann.org<mailto:vinciane.koenigsfeld@icann.org>>, Heidi Ullrich <Heidi.Ullrich(a)icann.org<mailto:Heidi.Ullrich@icann.org>>, Gisella Gruber <Gisella.Gruber(a)icann.org<mailto:Gisella.Gruber@icann.org>>, Olof Nordling <olof.nordling(a)icann.org<mailto:olof.nordling@icann.org>>, Julia Charvolen <julia.charvolen(a)icann.org<mailto:julia.charvolen@icann.org>>, Marika Konings <marika.konings(a)icann.org<mailto:marika.konings@icann.org>>, Glen de Saint Géry <glen(a)icann.org<mailto:glen@icann.org>>, Bart Boswinkel <bart.boswinkel(a)icann.org<mailto:bart.boswinkel@icann.org>>, Joke Braeken <joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>>, "gac-leadership(a)icann.org<mailto:gac-leadership@icann.org>" <gac-leadership(a)icann.org<mailto:gac-leadership@icann.org>>, Maya Saito <maya.saito(a)icann.org<mailto:maya.saito@icann.org>> Subject: RE: ICANN56 - Sched DRAFTv3.1 - PLEASE PROVIDE COMMENTS BY MONDAY 9 MAY Hi Tanzie Thank you for the revised schedule. I think it’s looking good. Is it possible to make a direct swap for two of the Cross Community Discussions please: · Move the PDP New gTLD Subsequent Procedures from Monday 1700-1830 to Tuesday at the same time; and · Move the PDP on Next Generation gTLD Registration Directory Service (WHOIS) from Tuesday at 1700-1830 to Monday at the same time. This will enable the Cross Community Discussions to take place before the respective PDP WG sessions. On your other questions: * Should any of the currently scheduled CC topic sessions be 100% non-conflicted? (I.e. CCWG & ICANN Accountability) I’d like to have a better understanding of the intent of some of the sessions, for example if the CCWG & ICANN Accountability session is intended to be a update session then I question the value of having this identified as a 100% non-conflicted topic. I’m not sure that the Privacy and Proxy issue needs to be a CC topic, but it would help to understand what folks would like to get from the discussion. As this topic was the subject of a long-running PDP and the recommendations were approved by the Council and forwarded to the Board for consideration, I’m not sure what we expect to gain from further discussion. I support the remainder of the topics identified for CC Discussions being non-conflicted. * On the remaining eight discussion topics, I offer the following suggestions: The GNSO Implementation Thick WHOIS Review Team does not need to be a CC topic and I’m not sure that it falls into the category of a bilateral discussion. My understanding is that this would be a meeting of the Implementation Review Team, which we hope can be accommodated into the overall schedule. IGO-INGO names & acronyms also does not need to be a CC topic, but it is a topic that the GNSO Council has an interest in discussing with the Board. The Charter for the CCWG on the use of gTLD Auction Proceeds already has a session on the schedule. Thanks Donna From: Tanzanica S. King [mailto:tanzanica.king@icann.org] Sent: Tuesday, May 03, 2016 10:37 PM To: Thomas.Schneider(a)bakom.admin.ch<mailto:Thomas.Schneider@bakom.admin.ch>; katrina(a)nic.lv<mailto:katrina@nic.lv>; alejandra.reynoso(a)cctld.gt<mailto:alejandra.reynoso@cctld.gt>; vgreimann(a)key-systems.net<mailto:vgreimann@key-systems.net>; ondouglas(a)gmail.com<mailto:ondouglas@gmail.com>; aftab.siddiqui(a)gmail.com<mailto:aftab.siddiqui@gmail.com>; tsinha(a)umd.edu<mailto:tsinha@umd.edu>; bverd(a)verisign.com<mailto:bverd@verisign.com>; patrik(a)frobbit.se<mailto:patrik@frobbit.se>; alan.greenberg(a)mcgill.ca<mailto:alan.greenberg@mcgill.ca>; berandondeh(a)yahoo.com<mailto:berandondeh@yahoo.com>; Ana.Neves(a)fct.pt<mailto:Ana.Neves@fct.pt>; Austin, Donna <Donna.Austin(a)neustar.biz<mailto:Donna.Austin@neustar.biz>>; tom(a)acig.com.au<mailto:tom@acig.com.au>; James Bladel <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>> Cc: Nick Tomasso <nick.tomasso(a)icann.org<mailto:nick.tomasso@icann.org>>; chris(a)disspain.id.au<mailto:chris@disspain.id.au>; David Olive <david.olive(a)icann.org<mailto:david.olive@icann.org>>; Sally Costerton <sally.costerton(a)icann.org<mailto:sally.costerton@icann.org>>; Teresa Elias <teresa.elias(a)icann.org<mailto:teresa.elias@icann.org>>; Michelle Bright <michelle.bright(a)icann.org<mailto:michelle.bright@icann.org>>; Melissa King <melissa.king(a)icann.org<mailto:melissa.king@icann.org>>; Vinciane Koenigsfeld <vinciane.koenigsfeld(a)icann.org<mailto:vinciane.koenigsfeld@icann.org>>; Heidi Ullrich <Heidi.Ullrich(a)icann.org<mailto:Heidi.Ullrich@icann.org>>; Gisella Gruber <Gisella.Gruber(a)icann.org<mailto:Gisella.Gruber@icann.org>>; Olof Nordling <olof.nordling(a)icann.org<mailto:olof.nordling@icann.org>>; Julia Charvolen <julia.charvolen(a)icann.org<mailto:julia.charvolen@icann.org>>; Marika Konings <marika.konings(a)icann.org<mailto:marika.konings@icann.org>>; Glen de Saint Géry <Glen(a)icann.org<mailto:Glen@icann.org>>; Bart Boswinkel <bart.boswinkel(a)icann.org<mailto:bart.boswinkel@icann.org>>; Joke Braeken <joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>>; gac-leadership(a)icann.org<mailto:gac-leadership@icann.org>; Maya Saito <maya.saito(a)icann.org<mailto:maya.saito@icann.org>> Subject: ICANN56 - Sched DRAFTv3.1 - PLEASE PROVIDE COMMENTS BY MONDAY 9 MAY Hi Everyone, Please see the attached document which includes a detailed list of proposed topics for cross community discussions in Helsinki and the latest draft schedule. (This info is also updated on the community wiki page at https://community.icann.org/display/ccmeetschedplan/Meeting+Schedule+Planni…<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…>.) The revised schedule includes significant changes provided by ALAC, GNSO, ccNSO, and RSSAC. Additionally, eight of the most requested topics (out of 16 total) for cross community discussions have been tentatively slotted in the afternoons Monday through Thursday. PAGE 1-2: Please review the revised schedule and share any comments /suggestions with the group. * Day/Time preferences for CC topic sessions currently appearing on the schedule * Should any of the currently scheduled CC topic sessions be 100% non-conflicted? (I.e. CCWG & ICANN Accountability) PAGE 3: Please provide any comments/suggestions for the remaining eight discussion topics. * Which topics are suitable for bilateral meetings? * Will topics of interest to a single group be absorbed within the "intra-community" sessions of that group? Please provide your feedback ASAP, but no later than EOD Monday, 9 May. Thanks, Tanzanica ________________________________ Tanzanica S. King Sr. Manager, Meeting Strategy and Design ICANN Office +1 310 301 5800 Mobile +1 310 995 3038 Email king(a)icann.org<mailto:king@icann.org> www.icann.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org&d=DQMF-g&…>

1 0

CCT RT Conference calls
by Nathalie Peregrine May 16, 2016

May 16, 2016

Dear all, The CCT-RT now has 4 sub teams which conduct work on calls (in addition to plenary calls). This results in a large number of call. As such, we have added the CCT RT plenary calls to our GNSO Master calendar: http://gnso.icann.org/en/group-activities/calendar For additional details and dial in details of the sub team calls: * Plenary https://community.icann.org/pages/viewpage.action?pageId=56989447 * Competition & Consumer Choice https://community.icann.org/pages/viewpage.action?pageId=58737630 * Safeguards & Trust https://community.icann.org/pages/viewpage.action?pageId=58737319 * Nielsen Subteam https://community.icann.org/display/CCT/Nielsen+Subteam+-+Calls * Application & Evaluation Process https://community.icann.org/pages/viewpage.action?pageId=59639637 Note: the procedure to join calls remains the same I.e. Via https://icann.adobeconnect.com/cctreview-observers Kind regards, Nathalie

1 0

Draft Letter to the Board on Red Cross Names & Identifier
by Austin, Donna May 13, 2016

May 13, 2016

James, all Following on from the discussion on the Council call yesterday about next steps in resolving the issue of permanent protection of certain Red Cross identifiers, the RySG has requested that the letter to the Board be amended to request an update/resolution of the outstanding issues related to the permanent protection of certain Red Cross identifiers and IGO acronyms. These issues have not previously been decoupled and we are concerned that if the Council suggests this as a path forward at this point it may be at the expense of resolving the remaining issues associated with IGO acronyms. Proposed amendments to the letter are provided for consideration. Thanks Donna Donna Austin: Neustar, Inc. Policy and Industry Affairs Manager Cell: +1.310.890.9655 Email: donna.austin(a)neustar.biz<mailto:donna.austin@neustar.biz> ________________________________ The information contained in this e-mail message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this e-mail message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify me immediately and delete the original message. Follow Neustar: [cid:image001.png@01CC3CD3.5F595DC0] Facebook<http://www.facebook.com/neustarinc> [cid:image002.png@01CC3CD3.5F595DC0] LinkedIn<http://www.linkedin.com/company/5349> [cid:image003.png@01CC3CD3.5F595DC0] Twitter<http://www.twitter.com/neustar> P Please consider the environment before printing this e-mail.

1 0

GNSO Council resolution 12 May 2016
by Glen de Saint Géry May 13, 2016

May 13, 2016

Dear Councillors, The GNSO Council passed the following resolution<http://gnso.icann.org/en/council/resolutions> at its meeting on 12 May 2016. Consent agenda Council confirmation of Kathy Kleiman, Philip Corwin and J. Scott Evans as co-chairs for the Review of all Rights Protection Mechanisms (RPMs) in all gTLDs Policy Development Process (PDP) Working Group<https://community.icann.org/display/RARPMRIAGPWG/Review+of+all+Rights+Prote…>. Voting results<http://gnso.icann.org/en/council/motion-recorder-confirmation-rpm-review-12…> The transcript of the Council meeting is published to: http://gnso.icann.org/en/meetings/transcript-council-12may16-en.pdf On page : http://gnso.icann.org/en/group-activities/calendar#may The next GNSO Council Public Meeting will take place in Helsinki on Thursday, 30 July 2016 at 07:45 UTC (10:45 EEST Local Time). Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

1 0

Fwd: ICANN News Alert -- ICANN Announces Senior Leader Transitions
by James M. Bladel May 13, 2016

May 13, 2016

Councilors - Please see announcement below. Sent via iPhone. Blame Siri. Begin forwarded message: From: "ICANN News Alert" <no-reply(a)external.icann.org<mailto:no-reply@external.icann.org>> Date: May 13, 2016 at 20:11:57 GMT+2 To: <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>> Subject: ICANN News Alert -- ICANN Announces Senior Leader Transitions Reply-To: no-reply(a)external.icann.org<mailto:no-reply@external.icann.org> [ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2016-05-13-en ________________________________ ICANN Announces Senior Leader Transitions 13 May 2016 The Internet Corporation for Assigned Names and Numbers (ICANN) today announced its Chief Contract Compliance Officer, Allen R. Grogan, and Nora Abusitta, Senior Vice President of Development and Public Responsibility Programs (DPRD), have notified the organization of their intent to leave ICANN later this year. Grogan will transition to a part-time role beginning 1 August 2016 and continue to oversee Contractual Compliance and Consumer Safeguards until his departure at the end of December 2016. Abusitta will remain in her current capacity until 1 June 2016, followed by a short part-time engagement period to ensure an efficient and seamless shift of duties. "I want to extend my deep thanks to Allen and Nora for the significant contributions they have made in their respective areas, as well as their commitment to ensuring a smooth transition of responsibilities," said Akram Atallah, acting Chief Executive Officer (CEO). "Compliance, safeguards and public responsibility are areas of extreme importance to ICANN, to me personally, and to G?ran Marby, who will be taking the reins as CEO later this month. We will continue to build on the work that has been done in these critical areas." Atallah further noted that "ICANN remains fully committed to enforcing its contracts and engaging with the community to help find creative ways to solve difficult issues in a manner consistent with ICANN's mission and remit." Additional Information Grogan has been with ICANN since May 2013, serving as Chief Contracting Counsel before assuming his current role as Chief Contract Compliance Officer in October 2014. ICANN is currently searching for a Consumer Safeguards Director<https://icann-openhire.silkroad.com/epostings/index.cfm?fuseaction=app.jobI…>. "My decision to leave was highly personal and difficult, but it will allow me to pursue other opportunities in my life," said Grogan. "It has been a privilege to work with the dedicated staff at ICANN and I specifically want to commend the Contractual Compliance team for their extraordinary work. My time at ICANN genuinely has been one of the most fascinating and remarkable experiences I've ever had." Abusitta joined ICANN in January 2013 as Executive Director of International and Inter-Governmental Organizations and in June of that year was appointed Vice President of Public Responsibility. "It has been an honor to work alongside dedicated and talented colleagues at ICANN, in particular the members of DPRD who were instrumental in building an infrastructure that empowers the community while ensuring participation within ICANN remains global and representative," said Abusitta. "This has not been an easy decision for me, but I am confident the ICANN staff will continue to focus on supporting current and new stakeholders' participation at ICANN." ICANN's mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you have to type an address into your computer - a name or a number. That address has to be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation and a community with participants from all over the world. ICANN and its community help keep the Internet secure, stable and interoperable. It also promotes competition and develops policy for the top-level of the Internet's naming system and facilitates the use of other unique Internet identifiers. This message was sent to jbladel(a)godaddy.com<mailto:jbladel@godaddy.com> from: ICANN News Alert | no-reply(a)external.icann.org<mailto:no-reply@external.icann.org> | ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536 Email Marketing by [iContact - Try It Free!] <http://www.icontact.com/a.pl/144186> Manage Your Subscription <http://app.icontact.com/icp/mmail-mprofile.pl?r=9826961&l=6333&s=0TYU&m=987…>

1 0

Legal Memo on IGO Sovereign Immunity
by Phil Corwin May 12, 2016

May 12, 2016

Councilors: As just discussed on the Council call, I am pleased to share the final draft of the legal memo discussing IGO sovereign immunity that was prepared for the IGO CRP WG by Prof. Edward Swaine of George Washington Law School in Washington, DC. As described on the call, our WG will be engaging in a dialogue with Prof. Swaine on Thursday, May 19th; it is also scheduled to have a 75 minute F2F meeting in Helsinki starting at 1:30 pm on Monday, June 27th. As you will see when you review the memo, the degree to which an IGO has immunity is not a simple black and white matter but is in fact a highly complex question -- the answer to which will vary with the type of IGO, the national jurisdiction in which the question is raised, and the activity for which the IGO seeks to assert immunity. If you have any questions please get back to me. Best regards, Philip Philip S. Corwin, Founding Principal Virtualaw LLC 1155 F Street, NW Suite 1050 Washington, DC 20004 202-559-8597/Direct 202-559-8750/Fax 202-255-6172/Cell Twitter: @VlawDC "Luck is the residue of design" -- Branch Rickey

2 1

MP3 recording and chat transcript GNSO Council 12 May 2016
by Glen de Saint Géry May 12, 2016

May 12, 2016

Please find the MP3 recording of the GNSO Council teleconference held on Thursday, 12 May 2016 at: http://audio.icann.org/gnso/gnso-council-12may16-en.mp3<http://mailer.samanage.com/wf/click?upn=NrFWbrBstcrPWP369qgbqlXiSKeL20xnUXz…> as well as the Adobe chat transcript at : http://gnso.icann.org/en/meetings/transcript-chat-council-12may16-en.pdf<http://mailer.samanage.com/wf/click?upn=KTB340yHI8DoUtMP4BGJnjfgjJp6GMAHPLM…> both on page http://gnso.icann.org/en/group-activities/calendar#may Thank you. Happy listening and reading! Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

1 0

IANA Stewardship Transition Planning Update (Volume 2)
by Glen de Saint Géry May 12, 2016

May 12, 2016

Dear All, For easy access, this document has been published to : http://gnso.icann.org/en/council/drafts<http://mailer.samanage.com/wf/click?upn=KTB340yHI8DoUtMP4BGJnral-2F6hkupRgT…> http://gnso.icann.org/en/drafts/draft-overview-obligations-post-transition-…<http://mailer.samanage.com/wf/click?upn=KTB340yHI8DoUtMP4BGJnuFT4taHix-2FWC…> Thank you. Kind regards, Glen De : owner-council(a)gnso.icann.org [mailto:owner-council@gnso.icann.org] De la part de Julie Hedlund Envoyé : mercredi 11 mai 2016 19:48 À : GNSO Council List Cc : Marika Konings Objet : Re: [council] IANA Stewardship Transition Planning Update (Volume 2) Dear All, Pursuant to Marika’s message below, please see the attached overview that Mary Wong and I have drafted as an introductory aid to the 12 May initial discussion on agenda item 6. I will be happy to outline the document on the call should the Council need a quick summary at that time about what’s in store for the transition. Kind regards, Julie Julie Hedlund, Policy Director From: <owner-council(a)gnso.icann.org<mailto:owner-council@gnso.icann.org>> on behalf of Marika Konings <marika.konings(a)icann.org<mailto:marika.konings@icann.org>> Date: Wednesday, May 11, 2016 at 4:10 AM To: GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: [council] IANA Stewardship Transition Planning Update (Volume 2) Dear All, For your information, please find below the latest IANA Stewardship Transition Planning Update which may be helpful in your preparation for agenda item 6 (Implementation of the IANA Stewardship Transition Plan). Heather, who will be chairing Thursday’s meeting, requests that you focus in addressing Item 6 on the 'how" rather than the "what" - in other words, use Thursday's meeting to think about the mechanics of how the Council go about answering the questions articulated in the agenda (From the agenda: "Here the Council will determine whether or not the amended Bylaws accurately reflect the ICG and CCWG-Accountability recommendations, and consequently whether a public comment from the Council is warranted. The Council will also discuss any concerns that have been identified relating to the establishment of the CSC, and begin deliberations over broader issues arising from the implementation of the transition plan, including the possible need to develop mechanisms that will facilitate the GNSO's participation in the new Empowered Community to be created”). Best regards, Marika From: <accountability-cross-community-bounces(a)icann.org<mailto:accountability-cross-community-bounces@icann.org>> on behalf of Hillary Jett <hillary.jett(a)icann.org<mailto:hillary.jett@icann.org>> Date: Tuesday 10 May 2016 at 23:33 To: CCWG-Accountability <accountability-cross-community(a)icann.org<mailto:accountability-cross-community@icann.org>> Subject: [CCWG-ACCT] [blog] IANA Stewardship Transition Planning Update (Volume 2) Original link: https://www.icann.org/news/blog/iana-stewardship-transition-planning-update… IANA Stewardship Transition Planning Update (Volume 2) [ana implementation timeline v5] • Previous update (27 April 2016) <https://www.icann.org/news/blog/iana-stewardship-transition-planning-update…> Root Zone Management The Root Zone Management implementation planning track contains projects relating to changes to the Root Zone Management System (RZMS) to remove NTIA's authorization role, parallel testing of the production and parallel test RZMS systems; and the development, and execution of an agreement with Verisign as the root zone maintainer. Root Zone Management System (RZMS) Parallel Testing Status update: It has been one month since the start of the parallel testing period and everything continues to go smoothly. Click here to view Verisign’s daily Parallel Operations Root Zone Management System Comparison Reports<http://www.verisign.com/rzms-parallel-ops/index.html> of all the root zone files generated. In addition to Verisign’s daily reports, ICANN has posted the first of three Monthly Reports on RZMS Parallel Testing Progress <https://www.icann.org/iana_imp_docs/23-1st-rzms-parallel-testing-monthly-re…> during the testing period. The report is available on ICANN’s dedicated Parallel Testing landing page<https://www.icann.org/stewardship-implementation/root-zone-management-syste…>. In the event that no unexplained differences in root zone files are identified between the production RZMS and the parallel test RZMS, the testing period will end successfully on 5 July 2016. Documents/announcements posted: • Monthly Report on RZMS Parallel Testing Progress<https://www.icann.org/iana_imp_docs/23-1st-rzms-parallel-testing-monthly-re…> • Verisign’s daily Parallel Operations Root Zone Management System Comparison Reports<http://www.verisign.com/rzms-parallel-ops/index.html> Mailing list: • None. Root Zone Maintainer Agreement (RZMA) Status update: Discussions between ICANN and Verisign to finalize details of the RZMA are continuing. The two parties have coalesced around many key elements of the agreement and hope to have a final draft by the end of the month. Once the draft RZMA is finalized it will be made publicly available on icann.org. Documents/announcements posted: • None. Mailing list(s): • None. ________________________________ Stewardship Transition The Stewardship Transition planning track contains projects to prepare relationship documentation with the operational communities, creation of a Post-Transition IANA (PTI) entity, establishment of a Customer Standing Committee (CSC) and a Root Zone Evolution Review Committee (RZERC), operationalizing the IANA customer service escalation mechanisms and Service Level Agreements (SLAs). Post-Transition IANA (PTI) Status update: ICANN has been working with the Implementation Oversight Task Force (IOTF) on various activities relating to the PTI. Summaries of PTI formation documents (Bylaws, articles of incorporation) as well as the conflict of interest policy have been shared with the IOTF. ICANN continues to work with the IOTF to finalize the process and timing of review for these documents as well as for the ICANN-PTI contracts. Documents/announcements posted this week: • None. Mailing list(s): • http://mm.icann.org/pipermail/iotf/ • http://mm.icann.org/pipermail/cwg-client/ Customer Standing Committee (CSC) Status update: In the CWG-Stewardship proposal, the Domain Names community recommended that a CSC be formed to replace NTIA’s role as it relates to monitoring performance of the IANA naming function. The composition of the CSC will include members and liaisons from all ICANN Supporting Organizations(SOs) and Advisory Committees (ACs). A Request for Appointment is expected to be sent to SOs and ACs this month to appoint members and liaisons to the CSC using their internal processes. Documents/announcements posted this week: • None. Mailing list(s): • http://mm.icann.org/pipermail/iotf/ Root Zone Evolution Review Committee (RZERC) Status update: The RZERC Charter (v4)<http://mm.icann.org/pipermail/cwg-stewardship/attachments/20160503/c35e40d7…> was circulated<http://mm.icann.org/pipermail/cwg-stewardship/2016-May/004977.html> to the CWG-Stewardship on 4 May 2016. The CWG-Stewardship will discuss the Charter on their 12 May 2016 call, and members and participants of the group are encouraged to provide any comment by 23:59 UTC on 17 May 2016. Following analysis and incorporation of any input received from the CWG-Stewardship, ICANN will post the Charter for a 30-day public comment period. Documents/announcements: • Root Zone Evolution Review Committee (RZERC) Charter (v4)<http://mm.icann.org/pipermail/cwg-stewardship/attachments/20160503/c35e40d7…> Mailing list(s): • http://mm.icann.org/pipermail/cwg-stewardship/ • http://mm.icann.org/pipermail/iotf/ ________________________________ Accountability Enhancements The Accountability Enhancements track contains plans to implement enhancements to ICANN’s Independent Review and Reconsideration Request processes, to update ICANN’s governance documents, and to operationalize new community powers defined by the Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability). ICANN's Bylaws Status update: ICANN and the community are in the middle of a 30-day public comment period on the new draft ICANNBylaws. Any interested party can submit comments to the public comment forum until 23:59 UTC on 21 May 2016. • Public Comment Page<https://www.icann.org/public-comments/draft-new-bylaws-2016-04-21-en> • Submit Comment to Forum<http://comments-draft-new-bylaws-21apr16@icann.org/> • Comments Forum<http://forum.icann.org/lists/comments-draft-new-bylaws-21apr16/> Adoption of the new Bylaws by the ICANN Board is anticipated for on or around 27 May 2016. Once new ICANN Bylaws have been adopted, ICANN will notify NTIA so they can complete their anticipated 90-day review of the IANA Stewardship Transition Proposal. Documents/announcements: • Draft New ICANN Bylaws<https://www.icann.org/en/system/files/files/proposed-new-bylaws-20apr16-en.…> • Comparison of Draft New ICANN Bylaws to Current Bylaws<https://www.icann.org/en/system/files/files/proposed-new-bylaws-redline-20a…> Mailing list(s): • http://mm.icann.org/pipermail/bylaws-coord/ • http://mm.icann.org/pipermail/accountability-cross-community/ • http://mm.icann.org/pipermail/cwg-stewardship/ • http://mm.ianacg.org/pipermail/internal-cg_ianacg.org/

1 1

GDD Summit
by Austin, Donna May 12, 2016

May 12, 2016

Hi All During the Council call today Francisco mentioned the GDD Summit. This summit is geared primarily for registries and registrars and will take place in Amsterdam next week. More information is available at: https://www.icann.org/gddsummit Happy to answer any questions. Thanks Donna Donna Austin: Neustar, Inc. Policy and Industry Affairs Manager Cell: +1.310.890.9655 Email: donna.austin(a)neustar.biz<mailto:donna.austin@neustar.biz> ________________________________ The information contained in this e-mail message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this e-mail message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify me immediately and delete the original message. Follow Neustar: [cid:image001.png@01CC3CD3.5F595DC0] Facebook<http://www.facebook.com/neustarinc> [cid:image002.png@01CC3CD3.5F595DC0] LinkedIn<http://www.linkedin.com/company/5349> [cid:image003.png@01CC3CD3.5F595DC0] Twitter<http://www.twitter.com/neustar> P Please consider the environment before printing this e-mail.

1 0