November 2019 - council - lists.icann.org

GNSO Council Review of the ICANN66 GAC Communique
by Steve Chan Nov. 22, 2019

Nov. 22, 2019

Dear Councilors, On behalf of the small team of Councilors (Julf, Michele, Tatiana, and Tom), please find the GNSO Council’s draft review of the ICANN66 GAC Communique, to eventually be shared with the ICANN Board: https://docs.google.com/document/d/1hbXl51OUWr4UtkJg13uHmwztv1gRd3bJ2BW9Xbm… To the extent there is a meeting needed for the GAC to clarify any elements of the GAC Communique that the ICANN Board is having trouble understanding, that meeting would be targeted for the second week of December. Accordingly, your timely review of the draft response is appreciated. Best, Steve Steven Chan  Policy Director, GNSO Support Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar

1 0

PDP 3.0 Package 4: Proposed Documents for Improvements 9 & 15
by Ariel Liang Nov. 21, 2019

Nov. 21, 2019

Dear GNSO Councilors, On behalf of the PDP 3.0 Small Team, staff would like to inform you that the Small Team has completed proposed documents for implementing twelve (12) out of fourteen (14) PDP 3.0 improvements so far. Previously, the Small Team sent to the GNSO Council proposed implementation documents for: · Improvements #1, #2, #3 & #6 on 22 August<https://mm.icann.org/pipermail/council/2019-August/022965.html>; · Improvements #11, #12, #14, and #16 on 25 September<https://mm.icann.org/pipermail/council/2019-September/023075.html>; · Improvements #5 & #13 on 22 October<https://mm.icann.org/pipermail/council/2019-October/023185.html>. The Small Team is now sending the proposed implementation documents for improvements #9 & #15. They are packaged together as they are concerned with consensus building and conflict resolution within GNSO working groups. #4 and #17 are the two improvements remaining in the pipeline. The Small Team invites the GNSO Council to review these documents and welcomes your questions and feedback. All delivered PDP 3.0 implementation documents can be found here: https://community.icann.org/x/v4rkBg *** Improvements #9 (Provide further guidance for section 3.6 and clarification of section 3.7 of the GNSO working group guidelines) · A guideline document that suggests detailed improvements to the complaint process within a GNSO working group, as well as proposed revisions to Section 3.7 of the GNSO Working Group Guidelines: https://docs.google.com/document/d/1pIHFupCdXoH3BSgRfu6KbzUm2jt1AQ-_MEk0JeM… · A briefing document that explains the concept of “consensus” and references experience with consensus building in the Internet Engineering Taskforce (IETF): https://drive.google.com/a/icann.org/file/d/1o8732tPyRh6PnER76VlT984HCLfovn… – NOTE: Since this document will be absorbed by the consensus playbook to be developed under Improvement #4, it does not require further deliberation by the GNSO Council at this time. Improvement #15 (Independent Conflict Resolution) · A reference guide to existing conflict resolution resources available to the ICANN community: https://docs.google.com/document/d/1yq__EGRYmicTGEOoZPqh6FdsXWNzFblqWwZkXhP… Best Regards, Ariel Ariel Xinyue Liang GNSO Policy Support Specialist Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

Reminder: Documents to review
by Nathalie Peregrine Nov. 21, 2019

Nov. 21, 2019

Dear all, A reminder that a wiki page has been created as repository for documents which councilors may wish to review and/or provide input on: https://community.icann.org/x/zIAzBw Thank you, Kind regards, Nathalie 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 visiting: https://learn.icann.org/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0

FYI: 21 November Update
by Michelle DeSmyter Nov. 21, 2019

Nov. 21, 2019

FYI: [http://r20.rs6.net/on.jsp?ca=66e1107e-8fa0-4612-8d27-e880169127e0&a=1122025…] Thursday, 21 November 2019 ICANN Community Leadership Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support team publishes this twice-weekly digest to help ICANN community leaders track requests and updates. Table of Contents Information Sharing · REMINDER: ICANN Fellowship Program Mentors · REMINDER: ICANN Preparations for IGF 2019: Information for the Community and Requests for Input · REMINDER: NextGen@ICANN Community Consultation ICANN67 Planning · REMINDER: ICANN67 Publication Support · REMINDER: CROP Deadline for ICANN67 Public Comment · CLOSING SOON: Registration Directory Service (WHOIS2) Review Team Final Report · CLOSING SOON: Proposed IANA SLAs for ccTLD Creation and Transfer · CLOSING SOON: Draft PTI and IANA FY20 Operating Plan and Budgets · Implementation Plan for the GNSO Consensus Policy Relating to the Protection of Certain Red Cross Names · Proposal for Future Root Zone KSK Rollovers Information Sharing REMINDER: ICANN Preparations for IGF 2019: Information for the Community and Requests for Input FOR: All Community Leaders INFORMATION SHARING The 14th Annual Meeting of the Internet Governance Forum (IGF) will be hosted by the Government of Germany in Berlin from 25 to 29 November 2019. ICANN org will have a booth, hold sessions, and co-host a reception with other Internet technical organizations. A few things we would like to share with you: · ICANN booth – The booth will be a resource for the ICANN community. Please contact us (see below) if you or any of your members would like to volunteer at the booth, or use the booth as a place for small meet-ups, etc. Once we have a better idea, we will create a schedule reflecting this. · Technical community reception – Monday, 25 November 2019, 18:30-20:00 (IGF venue). Space will be limited, and the reception will be by invitation only. Please send us (see below) the names of any community members attending the IGF and they will receive an invitation. Deadline: Tuesday, 12 November 2019. · Community sessions – Please send us (see below) details of any session at the IGF your community group and members are planning, and we will share this information online and at the ICANN booth. ICANN sessions IGF Day 0 Pre-Events: Monday, 25 November 2019 · 15:05-14:35 | Workshop: The evolving ecosystem: ICANN's role in the security and stability of the Internet [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> IGF Day 1: Tuesday, 26 November 2019 · 10:45-11:45 | ICANN Open Forum: ICANN - DNS, Threats and Opportunities [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> IGF Day 3: Thursday 28 November 2019 · 11:05-12:35 | Workshop: Online Identity in the Multilingual Domain Name Space [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> ICANN org contact for community members and requests: Adam Peake, adam.peake(a)icann.org<mailto:adam.peake@icann.org>. REMINDER: NextGen@ICANN Community Consultation Executive: Sally Costerton, Senior Vice President, Global Stakeholder Engagement FOR: All Community Leaders INFORMATION SHARING The NextGen@ICANN program is currently undergoing a community consultation [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. One request from the preliminary feedback received to-date was for ICANN org to explore the feasibility of having community volunteer representatives from Supporting Organizations (SOs), Advisory Committees (ACs), Stakeholder Groups (SGs), and Constituencies (Cs) to nominate individuals for the following two roles: 1. NextGen Selection Committee members 2. NextGen mentors For the Selection Committee, a time commitment of approximately 20 hours over three weeks is required (for each application round). Selection Committee members will typically serve for two years (or six application rounds). Mentors are expected to devote approximately 24 hours to pre-ICANN Public Meeting preparation with their mentees, to offer advice, networking support, and regular check-ins on-site, and to complete evaluations following the ICANN Public Meeting. Based on previous estimates, mentors spend about two hours per week during the six-week preparation period in advance of the meeting and about two hours per day providing on-site support at the ICANN Public Meeting. Mentors will typically serve for one year (or three meetings). Is your group interested in nominating individuals for either of these roles? By Monday, 16 December 2019, please take the following poll [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> to help ICANN org can gauge the level of community interest. The findings of this poll will inform the proposed NextGen program approach that will be published for Public Comment. Note: You will not be asked to submit the names of potential volunteers for roles at this time. REMINDER: ICANN Fellowship Program Mentors From: Sally Costerton, Senior Vice President, Global Stakeholder Engagement FOR: All Community Leaders INFORMATION SHARING ICANN's Supporting Organizations (SOs) and Advisory Committees (ACs) are invited to nominate [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> one individual each (total of seven) to serve as a mentor in the ICANN Fellowship Program. Mentors will serve a term that includes three consecutive ICANN Public Meetings, beginning with ICANN68. They will provide extensive pre-meeting preparation and on-site support for their assigned fellows, as well as complete a survey after each meeting. Mentors are expected to follow Fellowship Program guidelines to help ensure consistency in capacity development opportunities for fellows. They also play an important role to help fellows actively participate in ICANN's work. Mentors will receive travel funding support. Mentors cannot serve on the Fellowship Program Selection Committee [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> at the same time they are serving as mentors. For more information on the guidelines and expectations for mentors, please read about the program here [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. SOs/ACs should first select their respective Fellowship Program mentor by Thursday, 31 January 2020, and notify fellowshipconsultation(a)icann.org. Individual self-nominations will not be considered. ICANN67 Planning REMINDER: ICANN67 Publication Support From: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING Design Deadline If you require design assistance for an ICANN67 publication, all text, images, layout, and publication type/size requirements (i.e. newsletter, 1-pager, tri-fold, etc.) are due Friday, 3 January 2020. Please ensure that all materials, new or updated, are evergreen. Translation Deadline If your ICANN67 publication requires translation, please provide the final material(s) by Monday, 27 January 2020. This ensures that there is enough time to translate the publication by the print deadline. If your materials require design assistance (outlined above), please note that the final materials will have to be complete, including the edit/approval process, by this deadline in order to be translated. Print-Only Deadline If you only need your ICANN67 publication printed (meaning your publication is ready to send directly to the printer and needs no translation or design/layout modifications), please provide the file along with the quantity you want printed and dimensions of the publication by Friday, 7 February 2020. Please work directly with your support staff to submit these requests to chantelle.doerksen(a)icann.org and liana.teo(a)icann.org. REMINDER: CROP Deadline for ICANN67 From: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING For eligible groups planning to use Community Regional Outreach Program (CROP) funds to conduct outreach during ICANN67, requests must be submitted no later than Friday, 17 January 2020. No exceptions will be made. When submitting a CROP travel request, please keep in mind the following: Trip requests must be approved by the respective community leadership team. For FY20, the trip request must be filled in by the CROP participant via the CROP workspace [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. In order to access it, applicants must first have an account; please let the CROP coordinator know if you need an account. All individuals requesting CROP funding must also review the CROP Guidelines [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> prior to submitting a request. Please contact crop-staff(a)icann.org with any questions. Public Comment Registration Directory Service (WHOIS2) Review Team Final Report [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> CLOSING SOON: Monday, 25 November 2019 Proposed IANA SLAs for ccTLD Creation and Transfer [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> CLOSING SOON: Monday, 25 November 2019 Draft PTI and IANA FY20 Operating Plan and Budgets [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> CLOSING SOON: Wednesday, 27 November 2019 Implementation Plan for the GNSO Consensus Policy Relating to the Protection of Certain Red Cross Names [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Thursday, 12 December 2019 Proposal for Future Root Zone KSK Rollover [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 31 January 2020 Volume 1, Issue 66 | Archive [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> | Next Issue: Monday, 25 November 2019 ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe so-ac-sg-cleaders(a)icann.org [visitor.constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__visitor.constantcontac…> Update Profile [visitor.constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__visitor.constantcontac…> | About Constant Contact [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Sent by david.olive(a)icann.org<mailto:david.olive@icann.org> in collaboration with [Trusted Email from Constant Contact - Try it FREE today.][constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Try email marketing for free today! [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…>

1 0

Post-ICANN66 Policy Report Now Available
by Nathalie Peregrine Nov. 20, 2019

Nov. 20, 2019

Dear all, The Post-ICANN66 Policy Report is now available. Please click here to access it: https://go.icann.org/post66. Kind regards, Nathalie 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 visiting: https://learn.icann.org/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> See All SO and AC events on the ICANN Global calendar<https://features.icann.org/calendar>

1 0

GNSO nominated mentor - ICANN Fellowship Program
by Emily Barabas Nov. 19, 2019

Nov. 19, 2019

Dear Councilors, The GNSO has again been invited to nominate a mentor for the ICANN Fellowship Program to serve in the coming year (announcement at https://www.icann.org/news/announcement-2019-11-13-en) The deadline for nominations is 31 January 2020. An Expression of Interest process for the GNSO mentor role will be launched on 2 December with an application deadline of 16 December. Council leadership anticipates that this will leave enough time for the SSC to evaluate Expressions of Interest and recommend a candidate in time for Council to consider the selection at the January Council meeting. If you have any questions or concerns about this approach to the process, please share on list. Staff will send the link to the EOI announcement and application once it is launched. In the interim, please feel free to mention this upcoming opportunity to those who might be interested. Kind regards, Emily Emily Barabas | Policy Manager ICANN | Internet Corporation for Assigned Names and Numbers Email: emily.barabas(a)icann.org | Phone: +31 (0)6 84507976

1 0

Resignation from GNSO Council
by Darcy Southwell Nov. 19, 2019

Nov. 19, 2019

All, I’m writing to advise that I must resign my GNSO Council position effective immediately. I’ve taken on a new role with my company that does not allow me the time necessary to devote to Council work at this time. The RrSG leadership will begin the election process to select a replacement and will identify the necessary proxy to serve in my absence until that selection is complete. It has been such a pleasure working with all of you! I’ve enjoyed my time so much, built valuable relationships, and learned a great deal from all of you. You are doing valuable work and I look forward to watching (albeit a little bit from afar) all that you accomplish. Best, Darcy Southwell

7 6

Fwd: Re: [Ext] Re: FW: Reminder: Deadline Tuesday 19 November 2019: Beginning of the GNSO community feedback period: Fundamental Bylaws Amendment Approval Action
by Maxim Alzoba Nov. 18, 2019

Nov. 18, 2019

Dear Councillors, Please find RySG feedback below: ⁣Maxim Alzoba On 18 Nov 2019, 13:01, at 13:01, Nathalie Peregrine <nathalie.peregrine(a)icann.org> wrote: >Dear Maxim, > >Thank you ever so much for this feedback. Would you please be able to >forward it to the GNSO Council mailing list for all to review prior to >the electronic vote on Monday 25th November 2019? > >Thank you, > >Nathalie > >From: "m.alzoba(a)gmail.com" <m.alzoba(a)gmail.com> >Date: Friday, November 15, 2019 at 7:50 PM >To: Nathalie Peregrine <nathalie.peregrine(a)icann.org> >Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org>, Donna Austin ><donna.austin(a)team.neustar>, "kdrazek(a)verisign.com" ><kdrazek(a)verisign.com>, "Ducos, Sebastien" ><sebastien.ducos(a)team.neustar> >Subject: [Ext] Re: FW: Reminder: Deadline Tuesday 19 November 2019: >Beginning of the GNSO community feedback period: Fundamental Bylaws >Amendment Approval Action > >Dear Nathalie, >Please find RySG feedback below: >Maxim Alzoba > > > >The RySG supports the Fundamental Bylaws Amendment re IANA Naming >Function Review Composition as requested by the ccNSO. > > >The RySG appreciates the discussion during the Community Action >Approval Forum (CAAF) that recognized the importance of the community >process that ultimately lead to the approval of the Fundamental Bylaws >in order to move forward with the IANA Transition as well as >highlighting some of the challenges associated with meeting the >prescribed requirements that ultimately lead to the amendment request >from the ccNSO. During the discussion, Katrina Sataki also highlighted >that the ccNSO is likely to have the same problem in finding a >non-ccNSO representative in the event that a separation working group >(Section 19.4) is ever required. > > >The RySG also had challenges meeting the prescribed requirements for >representatives from the RySG for the IANA Naming Function Review that >we highlighted during the associated public comment process: > >https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.wixstatic.com_ugd… > > >During the CAAF, Jim Galvin recognized that the bylaws were written “ >.. very, very quickly during the transition…” and further that “… where >we as the community find loopholes or flaws, or contradictions within >the bylaws, it's up to us now as the communities here to raise these >fundamental bylaw changes, to come back to ICANN Legal with proposals >on, oh hey, we've seen a conflict here between these two requirements. >This is really our role now in order to solve those conflicts.” > > >In this context, it may be prudent for the Empowered Community to >consider a review of the Fundamental Bylaws at some time in the future >with a view to removing flaws, contradictions or conflicts between >requirements. > > ====== > >From: Nathalie Peregrine [mailto:nathalie.peregrine@icann.org] >Sent: Thursday, November 14, 2019 1:45 AM >To: gbunton(a)tucows.com; Austin, Donna <Donna.Austin(a)team.neustar>; >Selli, Claudia <cs574w(a)intl.att.com>; Brian Winterfeldt ><Brian(a)Winterfeldt.law>; Wolf-Ulrich Knoben ><Wolf-Ulrich.Knoben(a)t-online.de>; Stephanie Perrin ><stephanie.perrin(a)mail.utoronto.ca>; Joan Kerr <joankerr(a)fbsc.org>; >Bruna Martins dos Santos <bruna.mrtns(a)gmail.com> >Cc: Ariel Liang <ariel.liang(a)icann.org>; Sue Schuler ><secretariat(a)rysg.info>; gnso-secs(a)icann.org; Zoe Bonython ><secretariat(a)icannregistrars.org>; Maryam Bakoshi ><maryam.bakoshi(a)icann.org>; Chantelle Doerksen ><chantelle.doerksen(a)icann.org>; Julie Hedlund <julie.hedlund(a)icann.org> >Subject: Reminder: Deadline Tuesday 19 November 2019: Beginning of the >GNSO community feedback period: Fundamental Bylaws Amendment Approval >Action > > >Dear Stakeholder Groups and Constituency Chairs, > > >Following the Approval Action Community Forum >[66.schedule.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__66.schedule.icann.org_…> >on the “Fundamental Bylaws Amendment Approval Action in regard to the >IANA Naming Function Review Composition”, which took place on Sunday, 3 >November 2019 during ICANN66, GNSO Stakeholder Groups’ and >Constituencies’ input is now being sought by the GNSO Council. This >marks the start of the GNSO community feedback period following the >Approval Action Community Forum. > > > >Please provide opinions or comments, if any, from your Stakeholder >Groups or Constituencies’ on the Approval Action under consideration >that would inform the GNSO Council’s support for, objection to, or >abstention from the Approval Action. Any feedback from your Stakeholder >Groups and Constituencies must be submitted to the GNSO Council through >your Council representatives by Tuesday 19 November 2019 at 23:59 UTC. > >Following the closing of the GNSO community feedback period, the GNSO >Council – the representative body of the GNSO as a Decisional >Participant in the Empowered Community – will conduct an electronic >vote to decide whether to support, object to, or abstain from the >Approval Action. > >Please use the following materials for context of the Approval Action >that the GNSO Council is going to vote on: > >* Board Notice of the Board Approval of Fundamental Bylaws Amendment >re IANA Naming Function Review Composition: >https://www.icann.org/en/system/files/bm/secretarys-notice-3-13sep19-en.pdf >[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> >* Board Approval of Fundamental Bylaws Amendment to composition of >the IANA Naming Functions Review: >https://www.icann.org/resources/board-material/prelim-report-2019-09-08-en#… >[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> >* Staff report of the public comment on the “Fundamental Bylaws >Amendment Proposal – IANA Naming Function Review”: >https://www.icann.org/en/system/files/files/report-comments-bylaws-amend-ia… >[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> > >Thank you, > >Kind regards, > >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 visiting: https://learn.icann.org/ ><https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> >Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO ><https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> >Transcripts and recordings of GNSO Working Group and Council events are >located on the GNSO Master Calendar ><https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> >See All SO and AC events on the ICANN Global calendar >[features.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__features.icann.org_cal…>

1 0

Call for Volunteers - Addendum to the Review of All Rights Protection Mechanisms in All gTLDs Charter to Integrate Rec 5 From IGO-INGO Access to Curative Rights Protection Mechanisms Final Report
by Steve Chan Nov. 18, 2019

Nov. 18, 2019

Dear GNSO Council, As agreed during Council meeting at ICANN66, staff is circulating a call for volunteers to continue the work on the addendum to the RPMs Charter to integrate recommendation 5 from the IGO-INGO Curative Rights Protection Mechanisms Final Report. This drafting exercise was led previously by Paul McGrady, whose term on the Council has ended at the AGM. Currently, Martin Silva Valent and John McElwaine have volunteered for this team. In brief, the small team of Councilors prepared a draft, which resulted in a handful of agreed edits from the Council. That revised draft was sent to the GAC for their review and suggested edits. The GAC returned feedback shortly before ICANN66, which was discussed several times during multiple meetings. The next step for this drafting team will be to consider the suggested revisions from the GAC and put forth a version for the GNSO Council to consider. If you are interested in joining this small drafting team, along with Martin and John, please let staff know (either directly to me and/or gnso-secs(a)icann.org) by close of business in Los Angeles on Thursday, 21 November. Best, Steve Steven Chan  Policy Director, GNSO Support Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar See All SO and AC events on the ICANN Global calendar [features.icann.org]

1 0

FYI: 18 November Update
by Michelle DeSmyter Nov. 18, 2019

Nov. 18, 2019

FYI: [http://r20.rs6.net/on.jsp?ca=56723561-3cdc-4087-b229-0cf98df52b25&a=1122025…] Monday, 18 November 2019 ICANN Community Leadership Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support team publishes this twice-weekly digest to help ICANN community leaders track requests and updates. Table of Contents Information Sharing · REMINDER: ICANN Fellowship Program Mentors · REMINDER: ICANN Preparations for IGF 2019: Information for the Community and Requests for Input · REMINDER: NextGen@ICANN Community Consultation ICANN67 Planning · NEW: ICANN67 Publication Support · NEW: CROP Deadline for ICANN67 Public Comment · Registration Directory Service (WHOIS2) Review Team Final Report · Proposed IANA SLAs for ccTLD Creation and Transfer · Draft PTI and IANA FY20 Operating Plan and Budgets · Implementation Plan for the GNSO Consensus Policy Relating to the Protection of Certain Red Cross Names · Proposal for Future Root Zone KSK Rollovers Information Sharing REMINDER: ICANN Preparations for IGF 2019: Information for the Community and Requests for Input FOR: All Community Leaders INFORMATION SHARING The 14th Annual Meeting of the Internet Governance Forum (IGF) will be hosted by the Government of Germany in Berlin from 25 to 29 November 2019. ICANN org will have a booth, hold sessions, and co-host a reception with other Internet technical organizations. A few things we would like to share with you: · ICANN booth – The booth will be a resource for the ICANN community. Please contact us (see below) if you or any of your members would like to volunteer at the booth, or use the booth as a place for small meet-ups, etc. Once we have a better idea, we will create a schedule reflecting this. · Technical community reception – Monday, 25 November 2019, 18:30-20:00 (IGF venue). Space will be limited, and the reception will be by invitation only. Please send us (see below) the names of any community members attending the IGF and they will receive an invitation. Deadline: Tuesday, 12 November 2019. · Community sessions – Please send us (see below) details of any session at the IGF your community group and members are planning, and we will share this information online and at the ICANN booth. ICANN sessions IGF Day 0 Pre-Events: Monday, 25 November 2019 · 15:05-14:35 | Workshop: The evolving ecosystem: ICANN's role in the security and stability of the Internet [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> IGF Day 1: Tuesday, 26 November 2019 · 10:45-11:45 | ICANN Open Forum: ICANN - DNS, Threats and Opportunities [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> IGF Day 3: Thursday 28 November 2019 · 11:05-12:35 | Workshop: Online Identity in the Multilingual Domain Name Space [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> ICANN org contact for community members and requests: Adam Peake, adam.peake(a)icann.org<mailto:adam.peake@icann.org>. REMINDER: NextGen@ICANN Community Consultation Executive: Sally Costerton, Senior Vice President, Global Stakeholder Engagement FOR: All Community Leaders INFORMATION SHARING The NextGen@ICANN program is currently undergoing a community consultation [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. One request from the preliminary feedback received to-date was for ICANN org to explore the feasibility of having community volunteer representatives from Supporting Organizations (SOs), Advisory Committees (ACs), Stakeholder Groups (SGs), and Constituencies (Cs) to nominate individuals for the following two roles: 1. NextGen Selection Committee members 2. NextGen mentors For the Selection Committee, a time commitment of approximately 20 hours over three weeks is required (for each application round). Selection Committee members will typically serve for two years (or six application rounds). Mentors are expected to devote approximately 24 hours to pre-ICANN Public Meeting preparation with their mentees, to offer advice, networking support, and regular check-ins on-site, and to complete evaluations following the ICANN Public Meeting. Based on previous estimates, mentors spend about two hours per week during the six-week preparation period in advance of the meeting and about two hours per day providing on-site support at the ICANN Public Meeting. Mentors will typically serve for one year (or three meetings). Is your group interested in nominating individuals for either of these roles? By Monday, 16 December 2019, please take the following poll [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> to help ICANN org can gauge the level of community interest. The findings of this poll will inform the proposed NextGen program approach that will be published for Public Comment. Note: You will not be asked to submit the names of potential volunteers for roles at this time. REMINDER: ICANN Fellowship Program Mentors From: Sally Costerton, Senior Vice President, Global Stakeholder Engagement FOR: All Community Leaders INFORMATION SHARING ICANN's Supporting Organizations (SOs) and Advisory Committees (ACs) are invited to nominate [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> one individual each (total of seven) to serve as a mentor in the ICANN Fellowship Program. Mentors will serve a term that includes three consecutive ICANN Public Meetings, beginning with ICANN68. They will provide extensive pre-meeting preparation and on-site support for their assigned fellows, as well as complete a survey after each meeting. Mentors are expected to follow Fellowship Program guidelines to help ensure consistency in capacity development opportunities for fellows. They also play an important role to help fellows actively participate in ICANN's work. Mentors will receive travel funding support. Mentors cannot serve on the Fellowship Program Selection Committee [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> at the same time they are serving as mentors. For more information on the guidelines and expectations for mentors, please read about the program here [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. SOs/ACs should first select their respective Fellowship Program mentor by Thursday, 31 January 2020, and notify fellowshipconsultation(a)icann.org. Individual self-nominations will not be considered. ICANN67 Planning NEW: ICANN67 Publication Support From: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING Design Deadline If you require design assistance for an ICANN67 publication, all text, images, layout, and publication type/size requirements (i.e. newsletter, 1-pager, tri-fold, etc.) are due Friday, 3 January 2020. Please ensure that all materials, new or updated, are evergreen. Translation Deadline If your ICANN67 publication requires translation, please provide the final material(s) by Monday, 27 January 2020. This ensures that there is enough time to translate the publication by the print deadline. If your materials require design assistance (outlined above), please note that the final materials will have to be complete, including the edit/approval process, by this deadline in order to be translated. Print-Only Deadline If you only need your ICANN67 publication printed (meaning your publication is ready to send directly to the printer and needs no translation or design/layout modifications), please provide the file along with the quantity you want printed and dimensions of the publication by Friday, 7 February 2020. Please work directly with your support staff to submit these requests to chantelle.doerksen(a)icann.org and liana.teo(a)icann.org. NEW: CROP Deadline for ICANN67 From: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING For eligible groups planning to use Community Regional Outreach Program (CROP) funds to conduct outreach during ICANN67, requests must be submitted no later than Friday, 17 January 2020. No exceptions will be made. When submitting a CROP travel request, please keep in mind the following: Trip requests must be approved by the respective community leadership team. For FY20, the trip request must be filled in by the CROP participant via the CROP workspace [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. In order to access it, applicants must first have an account; please let the CROP coordinator know if you need an account. All individuals requesting CROP funding must also review the CROP Guidelines [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> prior to submitting a request. Please contact crop-staff(a)icann.org with any questions. Public Comment Registration Directory Service (WHOIS2) Review Team Final Report [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 25 November 2019 Proposed IANA SLAs for ccTLD Creation and Transfer [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 25 November 2019 Draft PTI and IANA FY20 Operating Plan and Budgets [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Wednesday, 27 November 2019 Implementation Plan for the GNSO Consensus Policy Relating to the Protection of Certain Red Cross Names [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Thursday, 12 December 2019 Proposal for Future Root Zone KSK Rollover [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 31 January 2020 Volume 1, Issue 65 | Archive [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> | Next Issue: Thursday, 21 November 2019 ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe so-ac-sg-cleaders(a)icann.org [visitor.constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__visitor.constantcontac…> Update Profile [visitor.constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__visitor.constantcontac…> | About Constant Contact [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Sent by david.olive(a)icann.org<mailto:david.olive@icann.org> in collaboration with [Trusted Email from Constant Contact - Try it FREE today.][constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Try email marketing for free today! [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…>

1 0