- Ccnso-council - lists.icann.org

proposed Triage recommendation 24-2016: ICANN Fellowship Program Application Process Review
by Joke Braeken June 16, 2016

June 16, 2016

Dear Councillors, Please find below the proposed Triage recommendation 24-2016. Kindly provide me with your input by the end of Monday 20 June 2016, 23:59 UTC, in case you do not agree with the proposed recommendation. Thank you. Topic: 24-2016 - ICANN Fellowship Program Application Process Review Originator: ICANN Summary of request: Leading up to the ten-year anniversary of ICANN's Fellowship program, the organization has evaluated this successful initiative in order to address the needs of the global community and provide appropriate enhancements to ensure that the program will continue to thrive while addressing today's ICANN and its capacity-building needs. In this regard, the ICANN staff have identified areas of improvement, mainly to the language used to describe Applicant Selection Criteria and the application assessment process. In doing so, ICANN staff is looking to ensure that the Fellowship selection process remains accountable, transparent, and independent while continuing to strengthen the ICANN Multistakeholder Model. https://www.icann.org/news/announcement-2016-06-14-en Date received: 15 June 2016 Last day for Comments/input/response, if any: 29 July 2016 Recommended action, if any: send to the following mailing lists: ccnso-council, ccTLDcommunity, ccnso-members. Post on social media Recommendation received by Triage Committee: 16 June Date of submission to Council: 16 June Deadline Council decision: 20 June 2016, 23:59 UTC Impact on ccNSO/ccTLDs: low Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

proposed Triage recommendation 23-2016: Draft Root Zone Evolution Review Committee (RZERC) Charter
by Joke Braeken June 16, 2016

June 16, 2016

Dear Councillors, Please find below the proposed Triage recommendation 23-2016. Kindly provide me with your input by the end of Monday 20 June 2016, 23:59 UTC, in case you do not agree with the proposed recommendation. Thank you. Topic: 23-2016 - Draft Root Zone Evolution Review Committee (RZERC) Charter Originator: ICANN Summary of request: As part of the IANA stewardship transition implementation planning efforts, ICANN is seeking community input on the Draft Root Zone Evolution Review Committee (RZERC) Charter developed to reflect the recommendations contained in the proposals by the IANA Stewardship Transition Coordination Group (ICG). https://www.icann.org/news/announcement-2-2016-06-10-en Date received: 13 June 2016 Last day for Comments/input/response, if any: 10 July 2016 Recommended action, if any: send to ccNSO-council, ccNSO-members, cctldcommunity, cctldworld. Share on social media. Recommendation received by Triage Committee: 16 June Date of submission to Council: 16 June Deadline Council decision: 20 June 2016, 23:59 UTC Impact on ccNSO/ccTLDs: high Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

Notes : Council call - 16 June @11:00 UTC
by Joke Braeken June 16, 2016

June 16, 2016

Dear Councillors, Please find below the notes taken during today’s council call. Best regards, Joke Council call - 16 June @11:00 UTC Wiki: https://community.icann.org/x/BiyAAw Apologies: Byron Holland Demi Getschko Peter Van Roste 1) Welcome and Apologies 2) Minutes and Actions 3) Overview inter-meeting Council decisions 4) Approval membership application .ba (Bosnia and Herzogovina) 5) Appointment new member CCWG use of country and territory names as TLDs 6) IANA Stewardship transition and CCWG –Accountability 6.1 Progress implementation For information 6.2. Progress ccNSO Guideline Selection ccNSO appointed member RZERC 7) CSC membership Selection 7.2 For discussion: selection committee or full Council decisions 8) PDP Review Mechanism and Retirement Framework 9) Meeting B Update/Programme WG update For information (Alejandra Reynoso) 10) Format preparatory face-to face Council meetings 11) Council Updates 12) WG updates 13) Liaison Updates 14) Monthly Work Plan 15) Next meetings 16) AOB 17) Closure NOTES 1) Welcome and Apologies no further apologies. We are quorate. 2) Minutes and Actions minutes from 12.05 have been distributed. No objections, hence minutes are adopted. All action items completed. (see wiki space) 3) Overview inter-meeting Council decisions 1. Alejandra provided updates to the survey. Sent out last Friday. Feedback expected by Helsinki. Reminder sent out today 2. CSC: notification sent to all mailing lists, and ROs. 4) Approval membership application .ba (Bosnia and Herzogovina) new Membership application application from .ba. all checks have been performed. Draft resolution. Movers? Stephen Seconders? Hiro approved. ccTLD manager for .ba is now ccNSO member number 159. in favour? Debbie, Alejandra, Becky, Hiro 5) Appointment new member CCWG use of country and territory names as TLDs CCWG. new member application. Timo (.ee) Movers? Becky Seconders? Peter Vergote Draft resolution. Secretariat to inform co-chairs In favour? Alejandra, Becky, Peter Objections? None Approved. 6) IANA Stewardship transition and CCWG–Accountability 6.1 Progress implementation Presentation included, notes from ISTACC call on Tuesday distributed. The mandate of this group was renewed. ICANN Board has adopted new bylaws. Effective after the transition. Public comment period currently for RZERC charter. ccNSO appoints 1 member. Contract between PTI and ICANN will on agenda in Helsinki Intellectual property rights IANA under discussion CSC membership discussed later today. Discussions on WS2 workload. Meeting on Sunday in Helsinki. Appears that interest of ccTLD community is diminishing. Noted by all participants on the call. We need to check whether our appointed members still want to continue the work. 6.2. Progress ccNSO Guideline Selection ccNSO appointed member RZERC Guideline for CSC. Draft was circulated. CSC guideline used to make the RZERC selection process guideline. Will be easier: no coordination needed with other SO/ACs. In 2 weeks we will be able to send you the proposed guideline for RZERC. Charter is now out for public comments. Pressure on us to adopt this guideline. RZERC needs to be in place by 15 August. 7) CSC membership Selection Guideline adopted today hopefully. In Helsinki we will answer questions from the community. Window EoI will close 15 July. Consult with RySG. Names to be submitted to ICANN secreatry on 22 July. Followed by consultation with GNSO and full slate needs to be adopted by 10 August. Structural overview. New structure, and the position of the CSC in it. Main purpose CSC: satisfactory performance IANA naming function, for the direct customers (e.g. ccTLDs). Need to monitor the performance and engage with PTI regarding possible issues. Composition CSC: 2 members by ccTLD operators. 2 gTLD registry operators, 1 additional TLD representative. 1 liaison from IANA and 1 liasion from each SO/AC within ICANN. Stephen: update on what to expect. Long guideline. 2 hard dates: completion nomination/selection 2 ccTLD appointments 22 july. overall approval by 10 august. Multi-step process. selection of the members. Guideline has a conflict-of-interest section. Requirements the candidates needs to meet: subject matter expertise is fundamental. diversity secondary. Candidate can come from any ccTLD registry, ccNSO member or not. Needs to be back by a cc. Rankings in order of preference sent to icann secretariat. Thoughts to set-up sub-group within the council, to move the selection process forward. 1 member from each of the 5 regions + 1 from NomCom.. Sub-group with final authority, or sub-group does a selection that needs to be approved by the council. Final consultation with gNSO on full slate and liaisons. Debbie: 2 questions 1. list of requirements the candidates should meet. no weight put on those criteria. Requirements consist of 2 parts. 1 part from proposal itself, second part are specific ccTLD requirements. No weight added to those requirements. Based on previous selection rounds (selection members to ICG), elaborate system developed at the time. but it turned out to be very cumbersome. Adds quasi objectivity to the selection process, which is not subjective for each councillor. Guideline may require updates after the first selection round. 2. what is a ccTLD/gTLD? some ccTLDs might be backend provider for gTLDs, set policy, run the operations etc. Draft decision. Movers? Debbie Seconders? Becky, Abibu Against? none Abstentions? none All in favour. 7.2 For discussion: selection committee or full Council decisions How to do consultations, how to appoint full slate? Selection committee within the council, consisting of 1 councillor per region, and 1 from NomCom. These 6 people coordinate with GNSO. If we go for this option, we need to decide on the mandate. only initial work, or also the final approval of the selection and full slate approval? Do you agree to nominate a subset of councilors to do coordination with GNSO and RySG. Supported by Becky, Peter, Alejandra. Its mandate? a. only consultation? opinion of Peter and Alejandra. Debbie agrees. Agree? Alejandra, Debbie, Peter b. also decide on full slate? Suggestion by Bart: take this offline. Council needs to be quorate. This will be difficult around that time of the year. Council has the final say: one of the members can always be removed by the council. process over e-mail takes about a week. 2 decisions: member selection by ccNSO, and the full slate. Only a week in between. Selection of members done by full council. Suggestion by Bart: subcommittee mandated, which has meeting with GNSO. The subcommittee could consult with council, if there is a real concern, the sub-committee is aware of it. Debbie agrees to this. Think about who from your regions can be on this sub-committee. To be further discussed in Helsinki. 8) PDP Review Mechanism and Retirement Framework paper prepared by staff on decision to be taken regarding launch of PDP. issue manager to be appointed. tentative timeline, and oversight committee in council to be appointed. Assumptions: Secretariat to prepare draft resolutions in time for prep. meeting on Monday 27 June. Request for issue report should include initial scope of the issues, advice whether we should have 1/2 PDPs. Optimal structure? Issue manager proposed by Katrina: Bart. Issue report to be ready by start of October. Ready by Hyderabad. Agreement to have Bart appointed as issue manager. Oversight committee from council needed to. Secretariat to issue call for volunteers from the council. 9) Meeting B Update/Programme WG update update by Alejandra. All presenters set. cocktail invitations sent out. chair country & geo names Forum: Cheryl Langdon-Orr Moderators from ccNSO and GNSO 10) Format preparatory face-to face Council meetings 11) Council Updates intro by Goran. later call with GNSO. 12) WG updates 13) Liaison Updates provided by Patrick/Ron 14) Monthly Work Plan 15) Next meetings prep meeting from 11:15 until 12:00, local time on Monday in Helsinki Attention: ICANN meeting schedule will say a different start time. F2F in Helsinki from 10:45 to 12:00 on Thursday, local time. Next meetings: working on schedule until December. No call in august. Bart to submit responses from councilors to IANA. Will happen before Helsinki meeting. Replacement for Keith? No, he is still involved. Willing to remain involved in the implementation process. 16) AOB 17) Closure Thank you. See you in Helsinki. Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

The ccNSO Council seeks your input
by Joke Braeken June 16, 2016

June 16, 2016

Dear all, In order to improve its transparency and accountability, also in light of the upcoming broader discussions on the accountability of the ccNSO, the ccNSO Council is seeking your input and feed-back. You are kindly requested to submit your responses to the ccNSO Council Accountability Survey by 24 June 2016, 23:59 UTC. We will report back to you shortly after 24 June 2016. How to provide your feedback? Via the online response form: https://s.zoomerang.com/r/ccNSO_Council_Accountability The survey will be open until 24 June 2016, 23:59 UTC. Should you have questions, contact joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Background The ccNSO provides a platform to nurture consensus, technical cooperation and skill building among ccTLDs and facilitates the development of voluntary best practices for ccTLD managers. The policy development process (http://ccnso.icann.org/policy/development) is managed by the ccNSO Council<http://ccnso.icann.org/about/council.htm>, which consists of 18 Councillors (15 elected by ccNSO members, three appointed by the ICANN Nominating Committee). The Councillors are actively involved in determining the work and direction of the ccNSO: they lead and participate in various ccNSO-working groups; they engage the community in topical issues and they develop positions based on community feedback. The ccNSO Council meets regularly at ICANN’s international meetings, and at (monthly) scheduled telephone conferences. All the documents, minutes of the meetings, resolutions and discussions are published on the ccNSO website and on the ccNSO Council wiki space. Your input is most appreciated. Thank you! On behalf of the chair of the ccNSO, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

Draft Agenda and resolution and update Transition Coordination call
by Bart Boswinkel June 15, 2016

June 15, 2016

Dear all, Please find included the draft agenda and resolutions and the informal notes from the Transition coordination call, Kind regards, Bart Draft Agenda and resolutions ccNSO Council Meeting 16 June 2016 1) Welcome and Apologies Attendance list is available at: http://ccnso.icann.org/about/council/attendance.htm 2) Minutes and Actions Minutes 12 May 2016 meeting were circulated. All Actions completed: https://community.icann.org/display/ccnsowkspc/Action+Items+2016 3) Overview inter-meeting Council decisions · Survey ccNSO Council Transparency and accountability · Informational letter community on selection ccNSO appointed members CSC 4) Approval membership application .ba (Bosnia and Herzogovina) For decision: Approval membership application. Draft Resolution The ccNSO Council approves the application of the ccTLD manager of .ba and welcomes Universtiy Telinformatic Centre (UTIC), the ccTLD manager for .ba (Bosnia and Herzogovina), as the 159th member of the ccNSO. 5) Appointment new member CCWG use of country and territory names as TLDs For decision: formal appointment new member CCWG CTN Timo Võhmar, .ee, has applied for membership of the CCWG CTN. Draft Resolution The ccNSO Council approves membership of Timo Võhmar, .ee, of the cross-community working group on use of country and territory names as TLDs. The secretariat is requested to inform the co-chairs of the WG and take all other necessary steps to include Timo as ccNSO appointed member of the WG. 6) IANA Stewardship transition and CCWG –Accountability 6.1 Progress implementation For information 6.2. Progress ccNSO Guideline Selection ccNSO appointed member RZERC The GRC will be using adjusting the CSC Guideline to propose and select a ccNSO appointed member on the RZERC. 7) CSC membership Selection 7.1 For decision: Adoption Guideline selection ccNSO appointed members (12 minutes) Draft resolution Background According to the CWG-Stewardship proposal, as supported by the ccNSO, the ccNSO itself will need to implement procedures and rules in accordance with its own practices and procedures to implement the CWG-Stewardship proposal within a limited timeframe (15 August 2016). The ccNSO Guideline and Review Committee (GRC) is tasked to review the ccNSO Rules and Guidelines, and also to fill in gaps if identified. The GRC has developed a working method over time that enables it to expedite the process of review and development of Guidelines and procedures. At its meeting on 9 March, the ccNSO Council requested and mandated the the ccNSO Guideline Review Committee to do all what is necessary including, but not limited to, reaching out and coordinating with other SO/AC s and ICANN staff to develop all processes and procedures the CWG-Stewardship suggested that should be implemented by the ccNSO. Following this request, the ccNSO GRC has developed and proposes the ccNSO Guideline: ccNSO Actions Respecting the Customer Standing Committee, which was send to Council on 8 June 2016. Draft Decision The ccNSO Council adopts the ccNSO Guideline: ccNSO Actions Respecting the Customer Standing Committee and request the secretariat to publish it on the ccNSO website as soon as possible and this Guideline will become effective 7 days after publication. The ccNSO Council requests its chair to inform the community of the adoption of the Guideline. The ccNSO Council thanks the members of the GRC for their hard work to develop and propose this Guideline in time. 7.2 For discussion: selection committee or full Council decisions 8) PDP Review Mechanism and Retirement Framework For Discussion: To launch PDP(s) at its meeting in Helsinki the following decisions need to be made in Helsinki: - Request for issue report - Appointment Issue Manager - Tentative timeline for Issue report In addition, Council may decide to appoint a committee to oversee (and assist) the appointed Issue Manager. 9) Meeting B Update/Programme WG update For information (Alejandra Reynoso) 10) Format preparatory face-to face Council meetings For discussion: During the ICANN meeting Council meets to prepare for the week/meeting. This prep meeting focuses on: - Possible decisions at the formal Council meeting - Identifying topics, preparation and assigning role of spoke persons for joint meetings ( ALAC –ccNSO Council, Board ccNSO, GAC-ccNSO and joint GNSO-ccNSO Council meetings) - Identifying possible ccTLD relevant sessions on the overall meeting schedule and assigning rapporteurs. To date the role of rapporteur has not really been defined and effective. For discussion: should we continue with assigning rapporteurs if councilors ( or others) do not report back? How to improve the reporting? 11) Council Updates 11.1 Chair Update Katrina: Call with Goran, later today call with GNSO. 11.2 Vice-Chair Update Katrina: no attending 11.3 Councilors Update Katrina: ask if any updates 11.4 Regional Organizations Update Katrina: ask RO present to provide update. Note Andres is now fully subsribed 11.5 Staff Update Katrina: ask staff 12) WG updates 12.1 CCWG Updates · Use of country and territory names (Annebeth Lange, Paul Szyndler, written update) · CWG on CCWG Principles (Becky Burr) · CCWG Internet Governance (Young Eum Lee) 12.2 EPSRP WG Other updates, if any 13) Liaison Updates Written updates 13.1 GNSO Liaison (Patrick Myles). 13.2 ALAC Liaison (Ron Sherwood). 14) Monthly Work Plan For information: Monthly Work Plan has bene provided. 15) Next meetings · Prep meeting 27 June, 11.15-12.00 local time · F-2 F meting Helsinki: Thursday 30 June, 10.45-12.00 UTC · 28 July (tentative), conference call · 1 September 2016 16) AOB 17) Closure

1 0

Council Call, Thursday 16 June @11:00 UTC
by Kimberly Carlson June 15, 2016

June 15, 2016

Dear Councilors, This is a reminder of tomorrow's Council call, 16 June at 11:00 UTC. Relevant documents have been distributed through the email list and can also be found on the Council Wiki workspace https://community.icann.org/x/OgKOAw Dial in details can be found below: Dial in numbers: http://www.adigo.com/icann/ Conference ID: 5258 Adobe Room with audio: http://icann.adobeconnect.com/ccnsocouncil/ If you require a dial out or are unable to attend, please let me know. Thank you and kind regards, Kim Carlson

1 0

SAVE THE DATE: ccNSO Community Cocktail Helsinki
by Kimberly Carlson June 15, 2016

June 15, 2016

Dear all, On behalf of our sponsor, you are all invited to join our ccNSO organized Community Cocktail in Helsinki on Tuesday 28 June, between 18:30 and 22:00 local time. The location is Café Piritta, about 1.2km from the meeting venue. Walking distance from the venue (15 mins). http://www.visithelsinki.fi/en/stay-and-enjoy/eat/cafe-piritta The location is easy to find, however we will be walking over as a group, starting around 18:15 - there will also be a group walking over together after the President & CEO Reception. See map below. The printed invitations will be handed out during the ccNSO Members Meeting. Many THANKS to our generous sponsor, FICORA (.fi), who made this event possible. Kind regards, Kim [cid:image003.jpg@01D1C611.5CDBAFE0]

1 0

NextGen@ICANN Application Round Opens for ICANN57 Hyderabad
by Joke Braeken June 15, 2016

June 15, 2016

Dear All, NextGen@ICANN Application Round Opens for ICANN57 Hyderabad ICANN is looking for the next generation of individuals who are interested in becoming more engaged in their regional communities and in shaping the future of global Internet policy. This application round will stay open until 22 July 2016. Successful candidates will be announced on the ICANN website on 19 August 2016. Read more: https://www.icann.org/news/announcement-2016-06-13-en Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

Call for Expressions of Interest for 2017 Nominating Committee Chair and Chair-Elect : deadline 30 June 2016
by Joke Braeken June 15, 2016

June 15, 2016

Dear all, ICANN is seeking expressions of interest for leadership roles in the 2017 Nominating Committee (NomCom) - that of the 2017 NomCom Chair and Chair-Elect. Expressions of Interest, which will be maintained as confidential, should be sent to NomComChair2017(a)icann.org<mailto:NomComChair2017@icann.org> no later than 10 June 2016. (Extended until 30 June) A suggested form for submitting an Expression of Interest is available here<https://www.icann.org/en/system/files/files/expressions-interest-form-03jun…> [PDF, 1.87 MB]. For more information about the NomCom see http://nomcom.icann.org/. In September 2016, the ICANN Board appointed Stéphane Van Gelder as the 2016 Nominating Committee Chair and Hans Petter Holen as the 2016 Nominating Committee Chair-Elect (https://www.icann.org/resources/board-material/resolutions-2015-09-28-en#2.g.) Article VII, section 3.4 of the Bylaws states, "[i]t is anticipated that upon the conclusion of the term of the Chair-Elect, the Chair-Elect will be appointed by the Board to the position of Chair." While it is anticipated that the 2016 NomCom Chair Elect will become the 2017 NomCom Chair, in support of continuous improvement in its accountability and transparency, the NomCom will evaluate the performance of the current NomCom leadership, and the results of that evaluation will be available to the Board Governance Committee before it makes a recommendation to the full Board on 2017 NomCom leadership. These reviews will be conducted by an independent third party provider and will consist of interviewing other NomCom leadership, NomCom members, and designated NomCom staff. The Board Governance Committee (BGC) will utilize the outcomes of these reviews in their processes leading up to the Board's formal appointment of the 2017 NomCom Chair and Chair-Elect. The NomCom Chair is responsible for organizing the NomCom in its activities to select certain ICANN Board members and individuals who will serve in key leadership positions within ICANN's supporting organizations (SOs) and advisory committees (ACs) in accordance with ICANN's Bylaws. The Chair is a non-voting member of the NomCom selected by ICANN's Board to serve until the conclusion of the next ICANN Annual Meeting. The Chair-Elect is a position created within the Bylaws as an outcome of the independent review of the NomCom. The Chair-Elect is not intended to fill an advisory role. Rather, the Chair-Elect will receive the benefit of training while serving alongside the Chair, gaining skills and knowledge to be applied for the Chair-Elect's anticipated succession into the role of the Chair. Candidates for Chair-Elect should possess the same skills as candidates for the Chair. Read more on https://www.icann.org/news/announcement-2016-06-10-en about the position description, the skills and experience, the specific duties and responsabilities, the eligibility exclusion and the expression of interest. Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

GNSO activity update - June 2016
by Patrick Myles June 15, 2016

June 15, 2016

Hi councillors. Please find attached the June 2016 activity update on the GNSO. For quick reference, it's also copied below. Regards Patrick Myles CENTR -------- CCWG - Accountability Members - Work Stream 2 Given the CCWG-Accountability is transitioning from Work Stream 1 to Work Stream 2, GNSO leadership has asked each Stakeholder Group to re-confirm its member selection for this CCWG. If members do not plan to continue they are to determine who will assume the role starting from ICANN Helsinki. James Bladel has already stated he will not continue and that the Registry SG will need to find a replacement. The GNSO has requested SG's to confirm their existing member or their replacement by 20 June 2016. GNSO Liaison to the CSC - Selection Committee GNSO council received expressions of interests to serve on the Selection Committee from: David Cake, Rubens, Kuhl, and Susan Kawaguchi. GNSO will need to formally approve both the Liaison and the entire slate of CSC members. GNSO Policy Development Process (PDP) Improvements The GNSO Council in 2013 started gathering ideas to improve and streamline the existing Policy Development Process. Ideas were translated into 10 PDP Improvements<http://gnso.icann.org/en/drafts/pdp-improvements-table-16jan14-en.pdf> many of which were closely aligned with ATRT2 recommendations. A final status update has been issued including proposed next steps on how to transform improvements into permanent features of the PDP. Improvements are grouped as follows: include charter in issue report, intensity of WG meetings, increase pool of WG volunteers, require WG rep from each SG/G with possible liaison, improved online tools, PDP WG rapporteur, professional moderation from experts, organize workshops/discussions at outset, improved data/metrics and flexibility with public comment duration. GAC Liaison update The GNSO recently closed the nomination period for candidates interested in the role of GNSO Liaison to the GAC with an 'underwhelming response' * from the GNSO community (potentially linked to timing of the announcement as perhaps better when other elections/positions). They have since postponed with nominations accepted until 1 October 2016. A new liaison is envisaged by 9 November 2016. *none of the applicants had any previous experience with the GNSO Council or with PDP working groups (chair or participant). GNSO Obligations in the Revised ICANN Bylaws Following revised ICANN Bylaws and the IANA Transition, staff conducted a detailed review and analysis of the revised ICANN Bylaws with respect to GNSO obligations. The analysis could provide guidance on where new GNSO operating procedures may be necessary, where it appears that existing procedures may apply, and where no action is necessary. The following areas are covered in the analysis: Obligations of the GSNO as a Decisional Participant of the Empowered Community, Engagement in the new Customer Standing Committee and New procedures or existing procedures concerning voting thresholds. Policy implementation update: IRTP-C and IRTP-D ICANN staff announced effective date of 1 December 2016 for IRTP-C<http://gnso.icann.org/en/issues/irtp-c-final-report-09oct12-en.pdf> and IRTP-D<http://gnso.icann.org/en/issues/transfers/irtp-d-final-25sep14-en.pdf>. The updated TDRP<https://www.icann.org/news/announcement-2016-06-01-en> (transfer dispute resolution policy) will also be effective on 1 December 2016. Other - ICANN56 scheduling: Overlap on Wednesday between the ccNSO cross community session on geographic names and the RPM PDP WG not likely to be resolved. - RySG Propose Amendment to New gTLD Registry Agreement: After 18 months of discussions, the revisions proposed by the RySG that ICANN agreed to have been made available to the community for comment. More information<https://www.icann.org/news/blog/amending-the-new-gtld-registry-agreement> - Graham Schreiber was removed from membership to the RPM (rights protection mechanism) review WG<https://community.icann.org/display/RARPMRIAGPWG/Review+of+all+Rights+Prote…>.

1 0