February 2017 - council - lists.icann.org

MP3 and AC Chat transcript/ GNSO Council Teleconference 16 February 2017
by Nathalie Peregrine 16 Feb '17

16 Feb '17

Dear GNSO Council, Please find the MP3 recording of the GNSO Council teleconference, held on Thursday, 16 February 2017 at: https://audio.icann.org/gnso/gnso-council-16feb17-en.mp3 as well as the Adobe chat at : https://gnso.icann.org/en/meetings/transcript-chat-council-16feb17-en.pdf And Adobe recording: https://participate.icann.org/p6hy7zc10rv/ all on page https://gnso.icann.org/en/group-activities/calendar#feb<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> Thank you. Happy listening and reading! With kind regards, Nathalie -- Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

FW: GNSO Council Abstention Notification Form [#236]
by Nathalie Peregrine 15 Feb '17

15 Feb '17

FYI Name of Officer: * Tapani Tarvainen Officer Email Address: * ncsg(a)tapani.tarvainen.info<mailto:ncsg@tapani.tarvainen.info> Date Prepared: * Sunday, February 12, 2017 GNSO Organization: * Non-Commercial Stakeholder Group Officer Position or Title: * NCSG Chair Voting Remedy: * Temporary Alternate Reason(s) for or condition(s) leading to the remedy: * Amr Elsadr has resigned from the council. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * Any and all. Date upon which the remedy will expire or terminate: [Note: may not exceed 3 months initially; may be renewed by sending an email with explanation to GNSO Secretariat] * Saturday, February 25, 2017 Please identify the individual (cannot be a current GNSO Councilor) who will serve as the abstaining Councilor's Temporary Alternate. [Note: if not already published and available, a short bio and Statement/Disclosure of Interest should be prepared by the Temporary Alternate and delivered to the GNSO Secretariat in advance of any discussion or voting scheduled to take place]. * Avri Doria Temporary Alternate Email Address: * avri(a)acm.org<mailto:avri@acm.org>

1 0

Draft IETF "Problem Statement" on Special Use TLDs
by James M. Bladel 15 Feb '17

15 Feb '17

Councilors - For those interested, the IETF has recently published a Draft Problem Statement on "Special Use Domain Names". https://datatracker.ietf.org/doc/draft-ietf-dnsop-sutld-ps/?include_text=1 I believe we, the GNSO and ICANN more broadly, should follow the developing work on this subject. Please feel free to share with your SG/C communities. Thank you, J.

3 3

FW: [bc-gnso] ICANN News -- Selection of the Second Security, Stability, and Resiliency of the DNS (SSR2) Review Team Members Announced
by Susan Kawaguchi 15 Feb '17

15 Feb '17

James, Surprised that there are only 15 members on this team. Were we not able to add our 4 additional endorsed candidates? Susan [CANN]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMGaQ…> News Alert https://www.icann.org/news/announcement-2-2017-02-14-en<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ________________________________ Selection of the Second Security, Stability, and Resiliency of the DNS (SSR2) Review Team Members Announced 14 February 2017 Today ICANN announced the selection of a 16-member team to conduct the second review on the security, stability and resiliency of the DNS (SSR2)<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. The selection of the SSR2 Review Team followed the new post-Transition process which assigned the responsibility for the selection of Review Team members to the chairs of ICANNs Supporting Organizations (SO's) and Advisory Committees (AC's). The SSR review was formerly required under the affirmation of commitments and is now one of the Specific Reviews under the ICANN Bylaws<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. The members of the SSR2 Review Team include…. Name Gender SO/AC Nomination Region 1 Jabhera Matogoro M ALAC AF 2 Alain Aina M ccNSO AF 3 Mohamad Amin Hasbini M GAC AP 4 Noorul Ameen M GAC AP 5 Geoff Huston M SSAC AP 6 Ramkrishna Pariyar M ALAC AP 7 James Gannon M GNSO EUR 8 Boban Krsic M ccNSO EUR 9 Emily Taylor F GNSO EUR 10 Žarko Kecić M ccNSO EUR 11 Kerry-Ann Barrett F GAC NA 12 Cathy Handley F RSSAC NA 13 Denise Michel F GNSO NA 14 Don M. Blumenthal M SSAC NA 15 Eric Osterweil M RSSAC NA In addition, Kaveh Ranjbar will be the ICANN Board representative on the SSR2. SSR2 Diversity Highlights<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…> Under the ICANN Bylaws, the SO/AC chairs are responsible for selecting a group that is balanced for diversity and skill. The SSR Review Team announced today includes: * Review Team Gender Diversity * Four females and eleven males * Review Team Regional Diversity * North America and Europe have five members * Europe and Asia have four members * Africa is represented with two members * Latin America/Carribean is not represented The SSR2 review team is expected to convene for its first meeting during ICANN 58 in Copenhagen in March 2017. There will be an SSR2 Public Consultation session during ICANN 58 prior to the SSR2 Review Team meeting in order to gather input from the community on items for the Review Team to consider as they develop the scope of their work. Periodic updates on the progress of the review will be made available on icann.org<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_&d=DwMGa…>, at ICANN public meetings and on the review team's wiki page here.<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…> Find more information on the Review Team members here<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…>. Find more information on the SSR2 review here.<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> About Specific Reviews Specific Reviews<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> are mandated by ICANN Bylaws<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> and are crucial to the legitimacy and accountability of ICANN. Specific Reviews serve as ICANN's progress report to the world. They demonstrate how ICANN delivers on its commitments and identify areas where ICANN can improve. Specific Reviews are conducted by members of the stakeholder community who look at past processes, actions and outcomes in order to make recommendations to improve future performance. Click here<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> to learn more about Reviews and how you can get involved. This message was sent to sdelbianco(a)netchoice.org<mailto:sdelbianco@netchoice.org> 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 [Contact - Try It Free!] <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icontact.com_a.pl_1…> Manage Your Subscription <https://urldefense.proofpoint.com/v2/url?u=http-3A__app.icontact.com_icp_mm…>

1 0

UPDATED: Draft GNSO Block Schedule for ICANN58
by Mary Wong 14 Feb '17

14 Feb '17

Dear Councilors, Please find attached an updated draft GNSO Block Schedule for ICANN58. While we anticipate that there may be more tweaks here and there as the Meetings Team works toward a final schedule for publication, those updates are more likely than not to relate only to start/end times, room allocations and the like. Please use this version 3.5 (dated 12 February 2017) for your and your groups’ planning purposes, including for the Council meeting later this week, as this version shows the latest changes. Here are a few additional notes for your information: · Day 1 (Saturday 11 March) will see three PDP Working Group face-to-face meetings. Due to the tight scheduling, some overlap and conflict was unavoidable (as is the case with the overall schedule). · The two sessions for the GAC-GNSO facilitated discussion on Red Cross and IGOs are currently scheduled for Saturday 11 March morning (07.30 – 09.30) and Sunday 12 March evening (18.30 – 20.30). As these are additional sessions on top of the “normal” GAC and GNSO meetings, and given the scheduling for the two groups and the Board, these were the only times which were available. · Day 2 (Sunday 12 March) is the only full-day GNSO Working Session – at the Council chairs’ direction, staff will be requesting all groups who are scheduled for that day to focus on their top issues for discussion (and not give status updates). · On Day 3, a session for a discussion with Data Protection Commissioners has now been scheduled, for the afternoon. · Day 5 (Wednesday 15 March) will see the “usual” Working Group open sessions, IRT meetings and the GNSO Council Public Meeting – please note that this is currently scheduled to run for 2 hours from 11.00-13.00. · Day 6 (Thursday 16 March) has the GNSO Wrap Up scheduled for 11.00 – 12.30. Thanks and cheers Mary

3 2

Please review: Active Project List
by Nathalie Peregrine 14 Feb '17

14 Feb '17

Dear Councilors, Attached please find the updated Project List in both red-line and clean version for your review before the Council meeting. If there are no comments, the list will be posted on the website on page: http://gnso.icann.org/en/council/project<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_counc…> and be directly viewed at :http://gnso.icann.org/meetings/projects-list.pdf<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_meetings…> Thanks so much, Kind regards, Nathalie

1 0

Additional information about and context for the GNSO schedule at ICANN58
by Mary Wong 14 Feb '17

14 Feb '17

Dear Councilors, In light of some concerns that some SG/C leaders have raised about conflicting sessions at ICANN58, GNSO Policy Staff thought it might be helpful if we provide some background on the scheduling. Please feel free to share the information with your respective community groups, and please let us know if you have any questions or comments. In general, we believe you know that it is getting more and more difficult to avoid conflicts, given the number of sessions and the increasing number of community group requests. We continue to get a great deal of these requests, many of which are for specific times and/or duration. In trying to accommodate as many requests as possible, and trying to keep to the times, duration and open/closed rooms requested, the result is some of the conflicts you are seeing on the draft overall ICANN block schedule. Here are some notes about a few of the meeting days: Saturday (Day 1, 11 March): · As you know, the suggestion had been made early on to use this first day for the three newest PDP Working Groups to do face-to-face meetings. Initially, we had hoped to schedule them all consecutively with no overlap, but the following two constraints made that impossible – having an early session that morning for the GAC-GNSO facilitated discussion on Red Cross/IGOs, and needing to accommodate (as much as possible) the official schedule, including timing of breaks. We scheduled the GAC-GNSO session in the GNSO room due to the early start and Bruce Tonkin’s request to use the GNSO set up. As a result, the three PDPs cannot now be consecutive due to lack of time, and New gTLD Subsequent Procedures was moved to another room. · RPMs was given a morning slot as it is the first time this group will be doing a F2F meeting. Similarly, New gTLD Subsequent Procedures got a morning slot (and RDS the afternoon) to reverse the order from Hyderabad, for fairness to the participants. This of course means that RPMs is now scheduled across from New gTLD Subsequent Procedures – note, however, that in reviewing the membership overlaps there are overlaps across all three PDPs, and there seemed a larger overlap between RPMs and the Privacy/Proxy IRT (which is meeting in the afternoon on Day 1 – this is the only time that GDD and the IRT can have more than the usual 90-minute or so slot to meet, which the IRT requested). · While it might look as though one or two WGs have much more time, that’s not the case once you factor in breaks and lunch. Basically, New gTLDs is likely to have 3.5 hours (not counting the coffee break), RPMs 3 hours (not including a break to grab lunch, which will be served for all 3 WGs in the RPMs (GNSO) room), and RDS a 3-hour afternoon block. SUGGESTION for Saturday – Perhaps the WG leadership of the three PDPs can get together to see if they wish to swop any of their sessions, taking into account their planned agenda topics and likely membership attendance? Monday (Day 3, 13 March): · No all-GNSO session has been scheduled across from the Cross Community Discussion Topics. As noted above, however, some SG/C requests were for this day and placed there either accordingly, or due to there not being a better (for fewer conflicts) slot. Wednesday (Day 5, 15 March): · The various GNSO WG and IRT sessions were planned around the Council meeting, which, at 2 hours, needed a specific slot. The WG and IRT sessions also took into account factors such as the availability of chairs and staff, and likely room size needed. For example, for IGO-INGO Curative Rights, it was scheduled so as not to conflict with the Board-GAC meeting or the IGO-INGO Protections IRT. · As far as possible, GNSO, Compliance, GDD and other staff tried to coordinate to avoid conflicts, at least for those sessions where traditionally we knew the GNSO community would be keen to attend, and within the constraints of the meeting framework for times, room and staff resource availability. We realize this doesn’t always work, and there may be other topics that are now on the meeting schedule that will also attract GNSO community interest. SUGGESTION for Wednesday – Perhaps the Council, or the SG/C leaders, can identify those meetings that GNSO community members are unlikely to be able to attend given the current schedule, and request that the session organizers see if they can be moved? We hope the above is useful. Thanks and cheers Mary From: Mary Wong <mary.wong(a)icann.org> Date: Monday, February 13, 2017 at 19:41 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: UPDATED: Draft GNSO Block Schedule for ICANN58 Dear Councilors, Please find attached an updated draft GNSO Block Schedule for ICANN58. While we anticipate that there may be more tweaks here and there as the Meetings Team works toward a final schedule for publication, those updates are more likely than not to relate only to start/end times, room allocations and the like. Please use this version 3.5 (dated 12 February 2017) for your and your groups’ planning purposes, including for the Council meeting later this week, as this version shows the latest changes. Here are a few additional notes for your information: · Day 1 (Saturday 11 March) will see three PDP Working Group face-to-face meetings. Due to the tight scheduling, some overlap and conflict was unavoidable (as is the case with the overall schedule). · The two sessions for the GAC-GNSO facilitated discussion on Red Cross and IGOs are currently scheduled for Saturday 11 March morning (07.30 – 09.30) and Sunday 12 March evening (18.30 – 20.30). As these are additional sessions on top of the “normal” GAC and GNSO meetings, and given the scheduling for the two groups and the Board, these were the only times which were available. · Day 2 (Sunday 12 March) is the only full-day GNSO Working Session – at the Council chairs’ direction, staff will be requesting all groups who are scheduled for that day to focus on their top issues for discussion (and not give status updates). · On Day 3, a session for a discussion with Data Protection Commissioners has now been scheduled, for the afternoon. · Day 5 (Wednesday 15 March) will see the “usual” Working Group open sessions, IRT meetings and the GNSO Council Public Meeting – please note that this is currently scheduled to run for 2 hours from 11.00-13.00. · Day 6 (Thursday 16 March) has the GNSO Wrap Up scheduled for 11.00 – 12.30. Thanks and cheers Mary

1 0

Amr Elsadr resignation from GNSO council
by Rafik Dammak 13 Feb '17

13 Feb '17

Dear Councillors, I wanted to share with you that Amr Elsadr is resigning from GNSO council since he is joining ICANN staff as policy manager. It is a big loss for NCSG but I do believe that he is going to do a good job as staff, Best, Rafik

4 3

FOR DISCUSSION: Preparation for Joint Meetings at ICANN58
by Mary Wong 10 Feb '17

10 Feb '17

Dear Councilors, On behalf of the GNSO Council chairs, staff is circulating the list of topics below to kick-start a discussion on the list of topics that the GNSO Council and community wish to propose for the upcoming joint meetings with the Board, GAC and ccNSO Council in Copenhagen. For the joint meeting with the GAC: The following topics were raised as possibilities on the most recent GAC-GNSO leadership call - · New gTLD subsequent rounds (focus on other topics that are not part of the facilitated discussions). · Adopting or discussing the implementation plan of the GAC-GNSO CG Final Report. · More substantive discussions on topics within a PDP for which there are different opinions in the community - for example, discussion on geographic names in the context of new gTLDs so that the input from proposed discussion in Johannesburg can feed into the PDP. · The PDP-generated workload, opportunities for prioritization, slowing the pace to allow stakeholders more space to engage effectively. (Note: The GAC and GNSO leadership teams also agreed that the meeting should focus on generating more discussion, using fewer slides and minimizing one-way presentations. For the joint meeting with the Board: The following topics were discussed in Hyderabad - · What do we, the Board and ICANN the organization, need to do to make the transition effective? · Discussion regarding the differences - in substance but also procedure – between the GAC advice and GNSO policy relating to IGO and Red Cross protections · Progress on implementation of GNSO Review recommendations For the joint meeting with the ccNSO Council: This was the agenda for Hyderabad: · Update on ongoing joint ccNSO-GNSO CCWG efforts a. CWG Principles (Becky Burr) (staff suggests that this can be removed as community work on this has been completed b. CWG to develop a framework for the use of Country and Territory names as TLDs c. CWG Internet Governance d. CCWG new gTLD Auction Proceeds · Non-CCWG Hot topics: a. Future scheduling of the ICANN meetings: High Interest Sessions, block schedule. Ensuring broad participation in HIT sessions. Specified time on schedule? b. Implementation of new Bylaws Please review the above list and comment on whether you wish to support their inclusion for ICANN58 or have different topics to suggest. Staff will note here that the topic of CCWG work (relative to policy development) has cropped up in a number of recent discussions, so this may be a topic for consideration as well. Thanks and cheers Mary

1 0

GNSO Appointed co-chair to the CCWG-Auction Proceeds
by James M. Bladel 09 Feb '17

09 Feb '17

Councilors - I'd like to draw your attention to this recent announcement, posted by Jonathan Robinson to the CCWG-Auctions mailing list (and copied below): http://mm.icann.org/pipermail/ccwg-auctionproceeds/2017-February/000080.html For the sake of transparency, I've reached out to Jonathan to ascertain whether there was any chance to persuade him to change his mind on this, or to otherwise address his concerns. And while Jonathan has graciously agreed to stay on in an interim capacity until we find a successor, his decision to step down is firm. So we go forward from here. I'm asking that we add this topic as a Discussion Item to the agenda for our 16 FEB Council meeting, and that we plan a Call for Volunteers for a replacement GNSO Co-Chair to this CCWG. Thank you, J. -------------------------------- All, Please note that I have written to the GNSO Council asking that I be replaced as the GNSO Appointed Co-Chair to this group - the Cross-Community Working Group on new gTLD Auction Proceeds (CWG Auctions). In this context, I would like to remind you of the following: 1.The net proceeds arising from ICANN's new gTLD auctions now total in excess of US$230m. 2. In excess of US$130m of that US$230m is derived from the auction of .web, a TLD for which Afilias plc was an applicant and eventual ICANN auction participant. Moreover, Afilias is clearly on record as disputing the outcome of the ICANN auction for .web. The charter drafting team for the CWG Auctions placed particular emphasis on the issue of conflict of interest when drafting the Charter for this CWG. Close attention to conflict of interest related concerns will be necessary now in relation to the work of the CWG and, even more so, in future with regard to any process or mechanism that may be put in place as a result of the work of the CWG. Now, considering that the tests for conflict of interest may include a actual, potential or even perceived conflict of interest and given the context provided above, it is quite possible that I may be seen to have at least a perceived conflict of interest in the execution of the work of the CWG Auctions. Accordingly, I have written to the GNSO to ask that a successor co-chair be appointed as soon as reasonably possible. Thank-you, Jonathan --------------------------------

1 0