November 2017 - council - lists.icann.org

SC-ICANN Budget: Draft Submission of Council Comments on ICANN's Reserve Target Level
by Berry Cobb 28 Nov '17

28 Nov '17

GNSO Council Members, On behalf of the GNSO Council Standing Committee on ICANN's Budget and Ops Plan (informal until Council adoption of charter), I attach here a draft of comments regarding ICANN's Reserve Target Level for your consideration and eventual submission to the public comment forum, absent any objections from Council members. The comment submission deadline is 30 November 2017 and as such Council's deliberation on this draft can occur via the Council's mailing list and it will also be an agenda item on the 30 Nov Council meeting. The standing committee met last week to discuss this topic and was also joined by Xavier Calvez, ICANN's CFO. As agreed during that call, staff assisted the committee with developing a first draft. This draft contains two options with regards to the size of the Reserve Fund; option 1 in line with the current target as analyzed by staff and the Board Finance Committee, and option 2 that proposes an extension to 24 months of operating expenses. Please refer to the attached draft for details and the analysis paper submitted for public comment (https://www.icann.org/public-comments/reserve-fund-2017-10-12-en). Only one comment has been submitted to date. On behalf of the Council Leadership and again absent any objections, staff can submit the final version of comments to the forum by 23:59 UTC, 30 November 2017. In the meantime, please let staff or Council leadership know if you have any questions about process or this draft of comments. Thank you for your attention to this matter. B Berry A. Cobb 720.839.5735 mail(a)berrycobb.com @berrycobb

6 7

IGO INGO IRT email confirmation
by Michelle DeSmyter 28 Nov '17

28 Nov '17

HI Keith, I hope you are doing well, I wanted to touch base with you and make sure that you received Dennis Chang's email yesterday regarding the IGO INGO IRT final call for support of the policy publication. I also wanted to make sure this was still the current email address you are currently using and you are receiving emails from the IGO INGO IRT mailing list. Thank you so much and I look forward to hearing back from you soon. Kind regards, Michelle Michelle DeSmyter GNSO/GDD SO/AC Support Coordinator Internet Corporation for Assigned Names & Numbers (ICANN) Email: michelle.desmyter(a)icann.org<mailto:michelle.desmyter@icann.org>

1 1

Fwd: [SOAC-Leaders-ICANNMeeting-Planning] - ICANN61
by Heather Forrest 28 Nov '17

28 Nov '17

Dear Council colleagues, There is an ongoing discussion on the SO/AC leaders list about cross-community topics for ICANN61. Your SGs and Cs should all have recently received a reminder of the deadline for proposing topics: 30 November 2017. I have excerpted the thread below started by Donna and contributed to by Farzaneh re proposing a GNSO PDP as a cross-community topic. This could be an opportunity to discuss a PDP's initial conclusions or differences of opinion/issues. If we think the policy development process would benefit from an opportunity for wide community discussion and consultation, this could be an opportunity (IGO/INGO Curative Rights was the first to come to my mind). Is this something that we want to pursue? If so, needs to be actioned before end Thursday. Best wishes, Heather ---------- Forwarded message ---------- From: Greg Shatan <gregshatanipc(a)gmail.com> Date: Fri, Nov 24, 2017 at 5:29 AM Subject: Re: [SOAC-Leaders-ICANNMeeting-Planning] - ICANN61 To: farzaneh badii <farzaneh.badii(a)gmail.com> Cc: Mary Wong <mary.wong(a)icann.org>, " soac-leaders-icannmeeting-planning(a)icann.org" < soac-leaders-icannmeeting-planning(a)icann.org>, Steve Chan < steve.chan(a)icann.org>, Mario Aleman <mario.aleman(a)icann.org>, Rodrigo de la Parra <rodrigo.delaparra(a)icann.org>, Patrik Fältström <paf.4711(a)gmail.com>, John Curran <jcurran(a)arin.net>, Zoe Bonython <zoefrabon(a)gmail.com>, Gulten Tepe <gulten.tepe(a)icann.org>, Maria Otanes <maria.otanes(a)icann.org>, GACLEADERSHIP <gac-leadership(a)icann.org>, "team-leaders(a)icann.org" < team-leaders(a)icann.org> I think Donna raised a number of excellent points, and I agree with Tijani and Farzaneh's responses. In particular, I think we need to confront the issue that Farzi raised, which I call the issue of "ownership" of a given session. I'll suggest two or three possible solutions: 1. Make it crystal clear that the proposing SOACetc. does *not* own the session. It does not get to determine the slant or the dominant point of view, or the facilitator or the panelists. This should be done by a small cross-community planning team for each CC session, sharing the planning burden and seeking to put together a well-rounded panel with points and counterpoints well-represented and well-balanced. This does not require every SOACetc. to get a seat at the table, but it does require an understanding and accommodation of the differing (and often, conflicting) points of view. *OR* 2. Acknowledge that some (but not all) of the sessions will be owned by the proposer and will be intended to provide (or at least be dominated by) one point of view or several largely aligned points of view. Perhaps these could be called *"Community-to-Community" *sessions. These could be compared to IGF sessions to some extent. At a following ICANN meeting, another SOACetc. could put together a different C2C session with their "counterpoint" point of view (and neighboring views) dominating. In each case, the audience will provide the counterpoints, but it will be understood how the panel itself is intended to be chosen and work in practice. The angst has arisen because fairly "hot" topics have been proposed as Cross-Community sessions, and the tussle arises between those who believe the proposer gets to shape the session around their views and those who believe the panel should be balanced. A secondary tussle arises because the proposer puts in a lot of effort and believes that those who want a seat at the table (especially later in the process) are "free-loading". A clear decision in advance would solve the first problem, and quick invitations to the planning process would solve the second. As for the conflicts/breadth of interest issues, I think we should acknowledge that some topics have interest for virtually every community, while others may only be of interest to some (but not all) communities. We should manage conflicts accordingly. In other words, if Topic 1 is of interest to communities A,B and C, but not D, E and F, then a second session or sessions of interest to D, E and/or F can be scheduled against Topic 1. The alternative leaves the less-interested communities with no compelling session to attend during the unconflicted CC Topic time. Perhaps the topics where only some communities are interested could be called *"Multi-Community Sessions (A, B, C)" *[where A, B and C are the relevant communities] to distinguish them from true *"Cross-Community"* On a related note, the way that voting in this group is weighted can result in some topics of interest to many or all of the communities grouped under the GNSO (Registries, Registrars, ISPs, Business, IP, Non-Commercial Users, Non-Profits) but only some of the other communities losing out as Cross-Community topics because the GNSO is only given a single vote. This needs to be addressed in some fashion, perhaps through the Multi-Community Sessions. In any event, these are largely "parting notes," as my term of office as IPC President ends November 30. It's been a pleasure working with all of you and I'm sure we will have many other opportunities to work together in various contexts. You and the IPC will be in the good hands of my successor, Brian Winterfeldt, while Vicky Sheckler will be continuing as Vice President. Happy Thanksgiving to those celebrating, Best regards, Greg Shatan IPC President On Fri, Nov 17, 2017 at 1:36 PM, farzaneh badii <farzaneh.badii(a)gmail.com> wrote: > > > Farzaneh > > On Fri, Nov 17, 2017 at 5:05 AM, Tijani BEN JEMAA < > tijani.benjemaa(a)topnet.tn> wrote: > >> Thanks Donna, >> Comments inline: >> >> Le 17 nov. 2017 à 03:13, Austin, Donna via SOAC-Leaders-ICANNMeeting-Planning >> <soac-leaders-icannmeeting-planning(a)icann.org> a écrit : >> >> Hi All >> >> Great to see you all in Abu Dhabi. I trust you’ve all settled back in to >> your home timezones. >> >> I wanted to kick off some discussion about the Cross Community >> Discussions Sessions for Puerto Rico. >> >> I think a few of us expressed some concern that identifying possible >> topics by 30 November 2017, was too early given that the meeting is not >> until mid-March 2018. I still subscribe to that and would ask that there be >> some flexibility to review the topics again in late January to see if there >> are new issues that may be more important. >> >> >> Agree >> > > I agree too. > >> >> However, I would like to put in a ‘place-holder’ for a Cross Community >> Discussion Session for one of the GNSO PDP WGs. We have a number underway >> at the moment and there is the possibility that one or two of these efforts >> will be at a point in their deliberations where the opportunity for a Cross >> Community Discussion Session would be timely. I appreciate that the Puerto >> Rico meeting is not a Policy/Outreach Forum, but as the PDP WGs work to a >> set timetable I would ask for some leeway in this regard. >> >> I’d also like to continue our discussion about Cross Community Discussion >> Sessions (Sessions), in particular the format and purpose. This seems to be >> the topic that always generates the most angst amongst this group and now >> that we’ve had a few goes at it, it might be time to revisit. I am >> concerned that we are in some way being hamstrung by what we think these >> Sessions are supposed to be rather than taking a look at the sessions >> conducted to date and thinking about what has worked well, what we could >> improve upon, and perhaps coming up with some level principles for the >> Sessions that we could agree on moving forward. >> >> For example, I don’t personally subscribe to the view that every SO/AC >> has to be represented on a panel to convey their point of view. This might >> be helpful if the purpose of the Session is to be ‘informational’, but if >> the intent of the Session is to garner community views on a particular >> topic or find a path forward to resolve a difficult situation then I don’t >> believe that a panel of talking heads will achieve that goal. In >> Johannesburg facilitators were used for the geographic names discussion, >> which appeared to work well and by all accounts achieved the objectives of >> those who organized the session. Is this an approach that could be adopted >> for future Sessions? >> >> Unfortunately this will open the way for one group to dominate the > discussion by choosing the facilitator on their own and then facilitators > miraculously become speakers. If facilitators don't do anything other than > just moderating, reading questions and trying to stimulate a discussion > then that's fine but I am skeptical whether this can actually happen. so > two minutes interventions from the community members with no one on the > panel other than the facilitators. Now, who would set the scene? The > facilitators? Since they might be from a certain SO/AC then they might not > be neutral. > > I still think having interested SO/AC members on the panel is not a bad > thing and it went well during Abu Dhabi. > >> >> Do we want these Sessions to be decisional? There has been some very good >> discussions in some of the Sessions to date, but I’m not confident that any >> of the suggestions or decisions were captured and if they were, that there >> is any agreement on who should be responsible for follow-up. Is this >> something we think should be established upfront? >> >> >> My understanding is that decisions are never taken during a cross >> community session. Those sessions are for debate and the discussion may >> impact decisions in working groups or other parties working on the topic >> and habilitated to take decisions. >> > > I agree with Tijani and I think they should not be decisional at all. > >> >> One of the original ideas behind these Sessions was that they be >> non-conflicted to free up the whole community during a meeting to >> participate in these Sessions. In the time of the IANA Transition >> discussions we were certainly able to carve out substantial chunks of time >> on the schedule for community discussions. However, more recently we have >> had trouble maintaining this as there are few topics that seem to rise to a >> level of interest for the whole community. To that end, should we be >> rethinking this requirement and perhaps run two Sessions concurrently when >> it makes sense to do so? >> >> >> Also, today, we still have topics like GDPR/Whois/RDS that are of >> interest for the whole community. These session used to be called « Hot >> Topic Session ». I think we always have hot topics to debate collectively >> (no in our silos). Another exemple of such topics is the new GTLD >> subsequent procedures and especially the geographic names >> >> I suggested during our meeting in Abu Dhabi that ICANN org also have an >> opportunity to identify a topic for these Sessions and I would reiterate >> that suggestion here in the hope that we can agree to implement this for >> Puerto Rico. >> >> >> About policy??? >> If it is not, I think they did in Abu Dhabi (Session called « Open Q&A >> with ICANN Organization Executive Team ») >> > > I hope not about policy! we can invite them to our CCs but does not sound > good to me that they organize CCs on policy ... > >> >> >> I look forward to your comments/input and I hope that you will read my >> email in the spirit of collaboration in which it is meant. I believe that >> as representatives of our respective groups we have an obligation to try to >> make the most of our time together at ICANN meetings and to use the >> opportunity provided through the non-conflicted Cross Community Discussion >> Sessions to have open community dialogue on issues that are important to >> individual SO/ACs and ultimately the broader community, ICANN org and ICANN >> Board. >> >> >> Agree >> >> Donna >> Vice Chair, GNSO Council >> >> >> >> >> >> >> *From:* soac-leaders-icannmeeting-planning-bounces(a)icann.org [ >> mailto:soac-leaders-icannmeeting-planning-bounces@icann.org >> <soac-leaders-icannmeeting-planning-bounces(a)icann.org>] *On Behalf Of *Susie >> Johnson >> *Sent:* Wednesday, November 01, 2017 8:41 AM >> *To:* soac-leaders-icannmeeting-planning(a)icann.org; team-leade >> rs(a)icann.org; Nathalie Peregrine <nathalie.peregrine(a)icann.org>; Kathy >> Schnitt <kathy.schnitt(a)icann.org>; Kimberly Carlson < >> kimberly.carlson(a)icann.org>; Terri Agnew <terri.agnew(a)icann.org>; Julia >> Charvolen <julia.charvolen(a)icann.org>; Gulten Tepe <gulten.tepe(a)icann.org>; >> Mario Aleman <mario.aleman(a)icann.org>; Maria Otanes < >> maria.otanes(a)icann.org>; Gisella Gruber <Gisella.Gruber(a)icann.org>; >> Rodrigo de la Parra <rodrigo.delaparra(a)icann.org>; Maryam Bakoshi < >> maryam.bakoshi(a)icann.org>; Glen de Saint Géry <Glen(a)icann.org>; Patrik >> Fältström <paf.4711(a)gmail.com>; Lars Hoffmann <lars.hoffmann(a)icann.org>; >> Sally Costerton <sally.costerton(a)icann.org>; Carlos Reyes < >> carlos.reyes(a)icann.org>; Heidi Ullrich <Heidi.Ullrich(a)icann.org>; Tom >> Dale <tom(a)acig.com.au>; Pierre Dandjinou <pierre.dandjinou(a)icann.org>; >> GACLEADERSHIP <gac-leadership(a)icann.org>; Zoe Bonython < >> zoefrabon(a)gmail.com>; David Olive <david.olive(a)icann.org>; Paul Diaz < >> pdiaz(a)pir.org>; Julie Hedlund <julie.hedlund(a)icann.org>; amack < >> amack(a)amglobal.com>; Joke Braeken <joke.braeken(a)icann.org>; Mary Wong < >> mary.wong(a)icann.org>; Nick Tomasso <nick.tomasso(a)icann.org>; >> Wolf-Ulrich.Knoben <wolf-ulrich.knoben(a)t-online.de>; Steve Chan < >> steve.chan(a)icann.org>; James M. Bladel <jbladel(a)godaddy.com>; Pamela >> Smith <pamela.smith(a)icann.org>; John Curran <jcurran(a)arin.net> >> *Subject:* [EXTERNAL] [SOAC-Leaders-ICANNMeeting-Planning] Breakfast >> Meeting - ICANN61 SO/AC Scheduling Kick-Off >> >> Dear Community Leaders: >> >> As promised, below please find the draft agenda: >> >> *ICANN61 SO/AC SCHEDULING KICK-OFF MEETING* >> *Thursday, 2 November 2017* >> *08:00-09:00* >> *Capital Suite 03* >> >> *Agenda* >> >> >> 1. *Welcome – David Olive* >> >> >> >> 1. *Schedule Production Calendar & Block Schedule Review – Tanzanica >> King* >> >> >> >> 1. *Cross-Community Topic Sessions – Tanzanica King* >> >> >> >> 1. *Incremental Changes to the Meeting Strategy – Sally Costerton* >> >> >> >> 1. *Future Dates for ICANN Meeting – Tanzanica King* >> >> >> >> 1. *ICANN61 - Puerto Rico – Nick Tomasso* >> >> >> We will use https://participate.icann.org/abu60-capitalsuite3-c >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__participate.icann.org_…> >> for the Adobe Connect room. >> >> Thank you. >> >> >> Kind regards, >> >> Susie >> >> Susie Johnson >> Policy Operations Specialist and Executive Assistant to Sr. VP, Policy >> Development >> ICANN >> www.icann.org >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org&d=DwMFAw&…> >> Cell: 310.383.1240 <(310)%20383-1240> >> Skype: susie.johnson.icann >> >> _______________________________________________ >> SOAC-Leaders-ICANNMeeting-Planning mailing list >> SOAC-Leaders-ICANNMeeting-Planning(a)icann.org >> https://mm.icann.org/mailman/listinfo/soac-leaders-icannmeeting-planning >> >> >> >> _______________________________________________ >> SOAC-Leaders-ICANNMeeting-Planning mailing list >> SOAC-Leaders-ICANNMeeting-Planning(a)icann.org >> https://mm.icann.org/mailman/listinfo/soac-leaders-icannmeeting-planning >> >> > > _______________________________________________ > SOAC-Leaders-ICANNMeeting-Planning mailing list > SOAC-Leaders-ICANNMeeting-Planning(a)icann.org > https://mm.icann.org/mailman/listinfo/soac-leaders-icannmeeting-planning > > _______________________________________________ SOAC-Leaders-ICANNMeeting-Planning mailing list SOAC-Leaders-ICANNMeeting-Planning(a)icann.org https://mm.icann.org/mailman/listinfo/soac-leaders-icannmeeting-planning

4 3

Fwd: FW: [Ext] CCWG-Accountability-WS2 - Reminder of Public Consultations
by Heather Forrest 27 Nov '17

27 Nov '17

Dear Council colleagues, A reminder below of the dates of the 4 currently open public comment periods for CCWG-Accountability WS2. The most immediate closing date is 15 December. Many thanks and best wishes, Heather *From: *Bernard Turcotte <turcotte.bernard(a)gmail.com> *Date: *Tuesday, November 14, 2017 at 21:37 *To: *"soac-chairs(a)icann.org" <soac-chairs(a)icann.org>, Accountability Cross Community <accountability-cross-community(a)icann.org> *Cc: *Bart Boswinkel <bart.boswinkel(a)icann.org>, Marika Konings < marika.konings(a)icann.org>, Steve Sheng <steve.sheng(a)icann.org>, Heidi Ullrich <Heidi.Ullrich(a)icann.org> *Subject: *[Ext] CCWG-Accountability-WS2 - Reminder of Public Consultations All, As per its proposed schedule to complete its work by June 2018 the CCWG-Accountability-WS2 currently has 4 public consultations open: · Enhancing Accountability - Recommendations for Diversity – Open, closes 15 December - https://www.icann.org/public-comments/accountability- diversity-2017-10-26-en[icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> · Recommendations to Improve ICANN's Office of Ombudsman (IOO) – Open, closes 22 December - https://www.icann.org/public-comments/ioo-recs-2017-11-10-en[icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> · Enhancing Accountability – Recommendations for Jurisdiction – Open, closes 5 January - https://www.icann.org/public-comments/accountability-recs- 2017-11-13-en[icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> · Enhancing Accountability – Recommendations and Guidelines for Staff Accountability – Open, closes 5 January. - https://www.icann.org/public-comments/recommendations-on- icann-jurisdiction-2017-11-14-en[icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> As explained and documented since ICANN 58 the CCWG-Accountability-WS2 will be publishing a final integrated report of all recommendations for public comment but will only be seeking comments on the resolution of any inconsistencies between the various individual report recommendations. As such, the community, including all SOs and ACs, are encouraged to provide any substantial comments they may have on the recommendations in the individual reports during the public consultations on these individual reports. The CCWG-Accountability-WS2 would like to take this occasion to remind the community that these recommendations will affect all parts of the ICANN community directly and as such the community is strongly encouraged to take the time to consider these and comment during the public comment period. It is also important to note that although all comments are considered equally that it is just as important for the community to show support for those recommendations they agree with. The CCWG-Accountability-WS2 Co-Chairs Thomas Rickert, Jordan Carter and Tijani Ben Jemaa

1 0

Fwd: [SOAC-Infoalert] CSC report PTI performance October 2017
by Heather Forrest 27 Nov '17

27 Nov '17

Dear Council colleagues, Please find below the October update and report of the Customer Standing Committee. Many thanks and best wishes, Heather ---------- Forwarded message ---------- From: Bart Boswinkel <bart.boswinkel(a)icann.org> Date: Sat, Nov 18, 2017 at 7:22 AM Subject: [SOAC-Infoalert] CSC report PTI performance October 2017 To: "soac-infoalert(a)icann.org" <soac-infoalert(a)icann.org> Cc: "icann-csc(a)icann.org" <icann-csc(a)icann.org> Dear all, On behalf of the chair of the CSC (Byron Holland), please find included the latest CSC update and report. Kind regards, Bart Boswinkel 17 November 2017 Dear Community Members, As chair of the Customer Standing Committee I provide you with our monthly report on the performance of Public Technical Identifiers (PTI) over October 2017. I am pleased to inform you that the CSC has concluded PTI’s overall performance in October 2017 was “Satisfactory”- PTI met the service level agreement at 96.9% for the month of October 2017. Missing the service levels was adequately explained and is not an indication of a persistent issue. The CSC was informed that no complaints were received in October 2017. The October 2017 PTI report to the CSC, listing the individual service level metrics along with their actual and historical performance, can be found at: https://www.iana.org/performance/csc-reports/201710 . In addition to its regular view of the PTI report, the CSC held several meetings at ICANN60 and the related the presentations and recordings can be found at: https://www.icann.org/en/csc/documents The CSC regular meeting is scheduled every month at or around the 15th and the CSC report on the PTI performance is send out shortly after each meeting. If you would like to be informed of upcoming meetings or receive CSC reports directly, you may want to subscribe to our announce list at https://mm.icann.org/mailman/listinfo/csc-announce . Any comments on our reporting to you is welcome. The CSC became effective October 1, 2016. Background information on the committee along with transcripts of our meetings and other useful information can be found at https://www.icann.org/csc[icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_csc&d=Dg…> . Kind regards, Byron Holland Chair CSC _______________________________________________ SOAC-Infoalert mailing list SOAC-Infoalert(a)icann.org https://mm.icann.org/mailman/listinfo/soac-infoalert

1 0

For your review: Updated GNSO Project list
by Nathalie Peregrine 27 Nov '17

27 Nov '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

Re: [council] [Ext] Re: Final Proposed Agenda GNSO Council Meeting - 30 November 2017 at 21:00 UTC
by Nathalie Peregrine 27 Nov '17

27 Nov '17

Dear Darcy, Thank you, and yes, Pam was nice enough to point this out to me, it was corrected last week on the wiki (https://community.icann.org/x/VQByB) and on the GNSO website. There have been other updates to the agenda since, so an updated version will be circulated to the GNSO list, reflecting those changes – already visible on the wiki – tomorrow, once we are sure the agenda is finalized. Thanks ever so much for the reminder! Kind regards, Nathalie From: Darcy Southwell <darcy.southwell(a)endurance.com> Date: Monday, November 27, 2017 at 9:17 PM To: Nathalie Peregrine <nathalie.peregrine(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [Ext] Re: [council] Final Proposed Agenda GNSO Council Meeting - 30 November 2017 at 21:00 UTC Hello, Nathalie. As Pam Little pointed out to me today, I think “7.3 – Next steps” should more likely be “7.3 – Council vote (voting threshold: simple majority).” Thanks, Darcy From: council <council-bounces(a)gnso.icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Tuesday, November 21, 2017 at 11:38 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] Final Proposed Agenda GNSO Council Meeting - 30 November 2017 at 21:00 UTC Dear Councilors, Please below find the final proposed agenda for the GNSO Council Meeting on 30 November 2017 at 21:00 UTC. They will also be posted shortly on the GNSO Council wiki space[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> and on the GNSO master calendar[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>. Final Proposed Agenda 30 November 2017 Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/WQByB[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> This agenda was established according to the GNSO Operating Procedures<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> v3.2, updated on 01 September 2016. For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. Coordinated Universal Time: 21:00 UTC: http://tinyurl.com/ybcbm2ev[tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__tinyurl.com_ybcbm2ev&d=…> 13:00 Los Angeles; 16:00 Washington; 21:00 London; (Friday) 02:00 Islamabad; 08:00 Hobart GNSO Council Meeting Audio Cast To join the event click on the link: http://stream.icann.org:8000/abu60-hallbc-en.m3u[stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1. Administrative Matters (5 mins) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_meet…> of the meetings of the GNSO Council on 12 October 2017, were posted on 3rd November 2017 Minutes of Part 1 and minutes of Part 2 of the GNSO Council on the 1 November 2017 will be posted on 23 November 2017. Item 2. Opening Remarks / Review of Projects & Action List (10 mins) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…>and Action Item List[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Item 3. Consent Agenda (0 min) None Item 4: COUNCIL VOTE – Adoption of the GNSO of GAC Communiqué for submission to the ICANN Board (15 minutes) The GNSO Council has adopted the practice of providing feedback to the ICANN Board on matters pertaining to gTLD policy, where the Governmental Advisory Committee (GAC) has included advice on such matters as part of a GAC Communique issued at each ICANN Public Meeting. Following the issuance of the GAC Abu Dhabi Communique (https://gac.icann.org/advice/communiques/public/gac-60-abu-dhabi-communique…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gac.icann.org_advice_c…>), a team of Councilors and the current GNSO Liaison to the GAC agreed to prepare an initial draft of possible GNSO Council input to the Board for Council consideration. This draft was circulated to the Council mailing list on 20 Nov 2017 (https://gnso.icann.org/en/drafts/review-gac-communique-21nov17-en.pdf[gnso.…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draf…>). Here the Council will discuss the draft Council feedback, and vote on whether or not to approve it for transmission to the ICANN Board. 4.1 – Presentation of motion [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>(Donna Austin) 4.2 – Council discussion 4.3 – Council vote (voting threshold: simple majority) Item 5. COUNCIL VOTE – Referral of the privacy and proxy services issue, related to IRTP-C, to the PPSAI IRT (15 minutes) At the request of the Registrars’ Stakeholder Group (RrSG), which raised a substantive concern regarding the application of Inter-Registrar Transfer Policy-C (IRTP-C) to privacy and proxy services, the GNSO Council wrote to the ICANN Board[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_corr…> to recommend that the matter be referred to the Privacy/Proxy Services Accreditation Implementation (PPSAI) Implementation Review Team (IRT) for consideration before the Policy effective date. The Board responded on 21 December 2016[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_corr…> to note that it was reviewing the Council’s request and in the interim, directed ICANN Contractual Compliance to defer enforcement of the issue. On 3 February 2017, the Board passed a resolution[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> confirming its instructions regarding deferral of Contractual Compliance enforcement and declaring its intention of further discussing the concerns raised by the GNSO Council at a subsequent meeting. On 16 March 2017, the Board passed a resolution[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> directing the ICANN CEO to instruct ICANN staff to work with the RrSG and other interested parties to determine the appropriate path forward. ICANN Staff and the RrSG are in agreement that the discussion should be referred to the PPSAI IRT. Here, the Council will consider a motion to refer the issue of applying IRTP-C to privacy and proxy services to the PPSAI IRT for resolution. 5.1 – Presentation of motion[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> (Darcy Southwell) 5.2 – Council discussion 5.3 – Council vote (voting threshold: simple majority) Item 6: COUNCIL VOTE – Confirmation of GNSO Representative to the Empowered Community Administration (15 minutes) The GNSO Council adopted the proposed process and criteria[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> for selecting the GNSO representative to the Empowered Community Administration during its meeting on 28 June 2017. Utilizing that process, the GNSO Council confirmed on 9 November 2017 that Heather Forrest would serve in interim basis to represent the GNSO as the Decisional Participant on the Empowered Community Administration. Further utilizing that process, the GNSO Council leadership has met and agreed that Heather Forrest will perform the role of GNSO representative to the Empowered Community Administration. Here, the Council will vote to confirm this selection. 6.1 – Presentation of motion[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> (Donna Austin) 6.2 – Council Discussion 6.3 – Council vote (voting threshold: simple majority) Item 7: COUNCIL VOTE – Confirmation that modification to the procedure that implements the Whois conflicts with privacy law policy recommendation with the Contracted Party Request and Legal Opinion triggers is consistent with the intent of the policy recommendation (20 minutes) As a result of community input and the work of the Implementation Advisory Group (IAG), ICANN made effective the revised WHOIS Conflicts with Privacy Law Procedure[whois.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__whois.icann.org_en_rev…> on 18 April 2017 to better accommodate issues where Whois requirements conflict with applicable laws. As requested by this GNSO Council, ICANN published a paper[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> for public comment[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> to provide analysis and solicit community input on the practicality and feasibility of the triggers identified in the revised WHOIS Conflicts with Privacy Law Procedure. The public comment period was also intended to collect suggestions for moving forward with the review. The public comment period closed on 7 July 2017 and the staff report of public comments[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> was published on 28 July 2017. On 1 August 2017, the Council received a letter[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_corr…> from Akram Atallah, providing a collection of possible options for proceeding with the review, and offering to discuss those options or others identified by Council. On 24 August 2017, the Council received an update from GDD staff and discussed possible options for moving forward with the review of the Procedure For Handling WHOIS Conflicts with Privacy Law. The Council has since considered the possible modifications to the procedure identified in the letter from Akram Atallah. Here, the Council will vote to confirm that the modifications to the procedure are consistent with the intent of the policy recommendation. 7.1 – Presentation of motion[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> (Keith Drazek) 7.2 – Council Discussion 7.3 – Next steps Item 8: COUNCIL DISCUSSION – Update on the GNSO Council Strategic Planning Session (15 minutes) In January of 2017, the GNSO Council submitted a FY18 additional budget request[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_do…> to support a 3 day face-to-face strategic planning session in January of 2018. At a high-level, the purpose of the meetings is to allow for focused and dedicated sessions to strategically develop a work plan for the upcoming year. This additional budget request was approved[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> by the ICANN Board on 19 April 2017. The GNSO Council Strategic Planning Session is scheduled to take place on January 29–31 2018 at the ICANN office in Los Angeles. Here the Council leadership will provide an update to the Council on preliminary planning steps undertaken to date, including review of a draft agenda. 8.1 – Presentation of discussion topic (Council leadership) 8.2 – Council discussion 8.3 – Next steps Item 9: COUNCIL DISCUSSION – Update on the GNSO Council Standing Committee on ICANN budget (15 minutes) The GNSO Council has determined that it may need to provide a Council specific response (not to supersede any response from any SG/C) to certain ICANN budget related public comments. The interim GNSO Council Standing Committee on ICANN budget has considered two public comments 1) Draft PTI and IANA FY19 Operating Plans and Budgets[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_Do…> and 2) ICANN Reserve Fund – Public Comment on Rationale and Target Level[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> and prepared draft responses to both for Council consideration. The Council may discuss the state of this standing committee’s charter as well. Here, the Council will discuss those draft responses and any possible next steps for the committee’s charter. 9.1 – Presentation of discussion topic (Council leadership) 9.2 – Council discussion 9.3 – Next steps Item 10: ANY OTHER BUSINESS (10 minutes) 10.1 – Discussion of Council meeting dates and rotation for 2018 10. 2 – Update on the status of the Second Security, Stability, and Resiliency Review Team (SSR2-RT) 10.3 – Other? ________________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11[icann…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf[gnso.icann.o…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…>. References for Coordinated Universal Time of 21:00 UTC Local time between March and October Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-8 13:00 San José, Costa Rica (CST) UTC-6 15:00 New York/Washington DC, USA (EDT) UTC-5 16:00 Buenos Aires, Argentina (ART) UTC-3 18:00 Rio de Janeiro, Brazil (BRST) UTC-2 19:00 London, United Kingdom (GMT) UTC 21:00 Paris, France (CEST) UTC+1 22:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 22:00 Islamabad, Pakistan (PKT) UTC+5 (Friday) 02:00 Singapore (SGT) UTC+8 (Friday) 05:00 Tokyo, Japan (JST) UTC+9 (Friday) 06:00 Sydney/Hobart, Australia (AEDT) UTC+11 (Friday) 08:00 ---------------------------------------------------------------------------- DST starts/ends on Sunday 25 of March 2018, 2:00 or 3:00 local time (with exceptions) for EU countries. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com[timeanddate.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.timeanddate.com_&d=…> and http://tinyurl.com/ybcbm2ev[tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__tinyurl.com_ybcbm2ev&d=…> Nathalie Peregrine Manager, Operations 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<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…> _______________________________________________ council mailing list council(a)gnso.icann.org https://mm.icann.org/mailman/listinfo/council

1 0

Re: [council] Final Proposed Agenda GNSO Council Meeting - 30 November 2017 at 21:00 UTC
by Darcy Southwell 27 Nov '17

27 Nov '17

Hello, Nathalie. As Pam Little pointed out to me today, I think “7.3 – Next steps” should more likely be “7.3 – Council vote (voting threshold: simple majority).” Thanks, Darcy From: council <council-bounces(a)gnso.icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Tuesday, November 21, 2017 at 11:38 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] Final Proposed Agenda GNSO Council Meeting - 30 November 2017 at 21:00 UTC Dear Councilors, Please below find the final proposed agenda for the GNSO Council Meeting on 30 November 2017 at 21:00 UTC. They will also be posted shortly on the GNSO Council wiki space[community.icann.org] and on the GNSO master calendar[gnso.icann.org]. Final Proposed Agenda 30 November 2017 Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/WQByB This agenda was established according to the GNSO Operating Procedures v3.2, updated on 01 September 2016. For convenience: An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. Coordinated Universal Time: 21:00 UTC: http://tinyurl.com/ybcbm2ev 13:00 Los Angeles; 16:00 Washington; 21:00 London; (Friday) 02:00 Islamabad; 08:00 Hobart GNSO Council Meeting Audio Cast To join the event click on the link: http://stream.icann.org:8000/abu60-hallbc-en.m3u Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1. Administrative Matters (5 mins) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes of the meetings of the GNSO Council on 12 October 2017, were posted on 3rd November 2017 Minutes of Part 1 and minutes of Part 2 of the GNSO Council on the 1 November 2017 will be posted on 23 November 2017. Item 2. Opening Remarks / Review of Projects & Action List (10 mins) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List and Action Item List Item 3. Consent Agenda (0 min) None Item 4: COUNCIL VOTE – Adoption of the GNSO of GAC Communiqué for submission to the ICANN Board (15 minutes) The GNSO Council has adopted the practice of providing feedback to the ICANN Board on matters pertaining to gTLD policy, where the Governmental Advisory Committee (GAC) has included advice on such matters as part of a GAC Communique issued at each ICANN Public Meeting. Following the issuance of the GAC Abu Dhabi Communique (https://gac.icann.org/advice/communiques/public/gac-60-abu-dhabi-communique…), a team of Councilors and the current GNSO Liaison to the GAC agreed to prepare an initial draft of possible GNSO Council input to the Board for Council consideration. This draft was circulated to the Council mailing list on 20 Nov 2017 (https://gnso.icann.org/en/drafts/review-gac-communique-21nov17-en.pdf). Here the Council will discuss the draft Council feedback, and vote on whether or not to approve it for transmission to the ICANN Board. 4.1 – Presentation of motion (Donna Austin) 4.2 – Council discussion 4.3 – Council vote (voting threshold: simple majority) Item 5. COUNCIL VOTE – Referral of the privacy and proxy services issue, related to IRTP-C, to the PPSAI IRT (15 minutes) At the request of the Registrars’ Stakeholder Group (RrSG), which raised a substantive concern regarding the application of Inter-Registrar Transfer Policy-C (IRTP-C) to privacy and proxy services, the GNSO Council wrote to the ICANN Board to recommend that the matter be referred to the Privacy/Proxy Services Accreditation Implementation (PPSAI) Implementation Review Team (IRT) for consideration before the Policy effective date. The Board responded on 21 December 2016 to note that it was reviewing the Council’s request and in the interim, directed ICANN Contractual Compliance to defer enforcement of the issue. On 3 February 2017, the Board passed a resolution confirming its instructions regarding deferral of Contractual Compliance enforcement and declaring its intention of further discussing the concerns raised by the GNSO Council at a subsequent meeting. On 16 March 2017, the Board passed a resolution directing the ICANN CEO to instruct ICANN staff to work with the RrSG and other interested parties to determine the appropriate path forward. ICANN Staff and the RrSG are in agreement that the discussion should be referred to the PPSAI IRT. Here, the Council will consider a motion to refer the issue of applying IRTP-C to privacy and proxy services to the PPSAI IRT for resolution. 5.1 – Presentation of motion (Darcy Southwell) 5.2 – Council discussion 5.3 – Council vote (voting threshold: simple majority) Item 6: COUNCIL VOTE – Confirmation of GNSO Representative to the Empowered Community Administration (15 minutes) The GNSO Council adopted the proposed process and criteria for selecting the GNSO representative to the Empowered Community Administration during its meeting on 28 June 2017. Utilizing that process, the GNSO Council confirmed on 9 November 2017 that Heather Forrest would serve in interim basis to represent the GNSO as the Decisional Participant on the Empowered Community Administration. Further utilizing that process, the GNSO Council leadership has met and agreed that Heather Forrest will perform the role of GNSO representative to the Empowered Community Administration. Here, the Council will vote to confirm this selection. 6.1 – Presentation of motion (Donna Austin) 6.2 – Council Discussion 6.3 – Council vote (voting threshold: simple majority) Item 7: COUNCIL VOTE – Confirmation that modification to the procedure that implements the Whois conflicts with privacy law policy recommendation with the Contracted Party Request and Legal Opinion triggers is consistent with the intent of the policy recommendation (20 minutes) As a result of community input and the work of the Implementation Advisory Group (IAG), ICANN made effective the revised WHOIS Conflicts with Privacy Law Procedure on 18 April 2017 to better accommodate issues where Whois requirements conflict with applicable laws. As requested by this GNSO Council, ICANN published a paper for public comment to provide analysis and solicit community input on the practicality and feasibility of the triggers identified in the revised WHOIS Conflicts with Privacy Law Procedure. The public comment period was also intended to collect suggestions for moving forward with the review. The public comment period closed on 7 July 2017 and the staff report of public comments was published on 28 July 2017. On 1 August 2017, the Council received a letter from Akram Atallah, providing a collection of possible options for proceeding with the review, and offering to discuss those options or others identified by Council. On 24 August 2017, the Council received an update from GDD staff and discussed possible options for moving forward with the review of the Procedure For Handling WHOIS Conflicts with Privacy Law. The Council has since considered the possible modifications to the procedure identified in the letter from Akram Atallah. Here, the Council will vote to confirm that the modifications to the procedure are consistent with the intent of the policy recommendation. 7.1 – Presentation of motion (Keith Drazek) 7.2 – Council Discussion 7.3 – Next steps Item 8: COUNCIL DISCUSSION – Update on the GNSO Council Strategic Planning Session (15 minutes) In January of 2017, the GNSO Council submitted a FY18 additional budget request to support a 3 day face-to-face strategic planning session in January of 2018. At a high-level, the purpose of the meetings is to allow for focused and dedicated sessions to strategically develop a work plan for the upcoming year. This additional budget request was approved by the ICANN Board on 19 April 2017. The GNSO Council Strategic Planning Session is scheduled to take place on January 29–31 2018 at the ICANN office in Los Angeles. Here the Council leadership will provide an update to the Council on preliminary planning steps undertaken to date, including review of a draft agenda. 8.1 – Presentation of discussion topic (Council leadership) 8.2 – Council discussion 8.3 – Next steps Item 9: COUNCIL DISCUSSION – Update on the GNSO Council Standing Committee on ICANN budget (15 minutes) The GNSO Council has determined that it may need to provide a Council specific response (not to supersede any response from any SG/C) to certain ICANN budget related public comments. The interim GNSO Council Standing Committee on ICANN budget has considered two public comments 1) Draft PTI and IANA FY19 Operating Plans and Budgets and 2) ICANN Reserve Fund – Public Comment on Rationale and Target Level and prepared draft responses to both for Council consideration. The Council may discuss the state of this standing committee’s charter as well. Here, the Council will discuss those draft responses and any possible next steps for the committee’s charter. 9.1 – Presentation of discussion topic (Council leadership) 9.2 – Council discussion 9.3 – Next steps Item 10: ANY OTHER BUSINESS (10 minutes) 10.1 – Discussion of Council meeting dates and rotation for 2018 10. 2 – Update on the status of the Second Security, Stability, and Resiliency Review Team (SSR2-RT) 10.3 – Other? ________________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf. References for Coordinated Universal Time of 21:00 UTC Local time between March and October Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-8 13:00 San José, Costa Rica (CST) UTC-6 15:00 New York/Washington DC, USA (EDT) UTC-5 16:00 Buenos Aires, Argentina (ART) UTC-3 18:00 Rio de Janeiro, Brazil (BRST) UTC-2 19:00 London, United Kingdom (GMT) UTC 21:00 Paris, France (CEST) UTC+1 22:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 22:00 Islamabad, Pakistan (PKT) UTC+5 (Friday) 02:00 Singapore (SGT) UTC+8 (Friday) 05:00 Tokyo, Japan (JST) UTC+9 (Friday) 06:00 Sydney/Hobart, Australia (AEDT) UTC+11 (Friday) 08:00 ---------------------------------------------------------------------------- DST starts/ends on Sunday 25 of March 2018, 2:00 or 3:00 local time (with exceptions) for EU countries. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com and http://tinyurl.com/ybcbm2ev Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages _______________________________________________ council mailing list council(a)gnso.icann.org https://mm.icann.org/mailman/listinfo/council

1 0

GNSO Council Comment - FY19 Draft IANA-PTI Budget
by Berry Cobb 26 Nov '17

26 Nov '17

ICANN Staff, On behalf of the GNSO Council, the following comments are submitted with regards to the FY19 Draft Budget for IANA-PTI. Thank you for providing the opportunity to comment. B Berry Cobb GNSO Policy Consultant

1 0

CCWG-IG: ICANN booth at IGF2017 - community use and presence
by Tatiana Tropina 23 Nov '17

23 Nov '17

Dear all, I am sending this email in my capacity of the interim GNSO Council liaison to the CCWG on Internet Governance. Please find below the information about ICANN Booth at IGF 2017: if you are attending this year's IGF in Geneva, you might find this useful. It would be great if you could share the info with your stakeholder groups and constituencies. Warm regards, Tanya ---------- Forwarded message ---------- *From: *ccwg-internet-governance <ccwg-internet-governance-bounces(a)icann.org> on behalf of Adam Peake <adam.peake(a)icann.org> *Date: *Tuesday, November 21, 2017 23:28 *To: *"ccwg-internet-governance(a)icann.org" <ccwg-internet-governance@ icann.org> *Subject: *[ccwg-internet-governance] ICANN booth at IGF2017 - community use and presence Hi everyone, During the CCWG-IG public forum in Abu Dhabi I spoke about the ICANN booth at this year's IGF. The booth is for all the ICANN community, to distribute materials, as spot where you can hold briefing sessions, a meeting point, and anything else that might come in useful. Could those of you on this list acting as liaisons to your respective SO/AC and constituencies let your colleagues know that there will be an ICANN booth in the "IGF Village", that any of your colleagues attending the IGF are welcome to use it. If you have materials you would like to share (brochures, flyers, etc), please let me <adam.peake(a)icann.org> know and we will start making necessary arrangements to have those made available. As we do with the ICANN booth at regular ICANN meetings, we will also schedule times when SO/AC/constituency members can talk about their groups and activities. I'll let you know more as we get a bit closer to the start of the IGF (December 18). Best, Adam

1 0