GNSO-RPM-WG

Download

gnso-rpm-wg@icann.org

April 2019

4 participants
12 discussions

**REMINDER: UPDATED EOI DEADLINE 8 APRIL 2019** Expressions of Interest Sought for Chair of GNSO EPDP on the Temporary Specification for gTLD Registration Data – Phase 2
by Julie Bisland April 5, 2019

April 5, 2019

https://www.icann.org/news/announcement-2019-03-01-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> LOS ANGELES –1 March 2019 – The Generic Names Supporting Organization (GNSO) is looking for expressions of interest to chair Phase 2 of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data. The EPDP Team recently completed its Phase 1 work and is expected to commence planning for Phase 2 at ICANN64 meeting in Kobe, Japan. During Phase 2, the EPDP Team will work on a system for standardized access to non-public registration data, topics identified in the annex to the Temporary Specification, as well as a number of carry over items from Phase 1. The GNSO Council is looking to appoint a neutral Chair to the EPDP Team. With such an important issue under consideration, significant responsibility comes with the role to ensure the success of deliberations. The EPDP Team is expected to have regular calls, although it may be necessary to hold calls more frequently if need arises. Additionally, the EPDP Team may have face-to-face meetings in order to meet the required milestones of the EPDP. The EPDP Team is expected to start developing the work plan for Phase 2 at ICANN64 in Kobe for which the GNSO Council may provide further guidance. There will be no compensation associated with the role of the EPDP Team Chair; however, travel associated with any face-to-face meetings may be supported by ICANN org. To express interest in this role, please submit an Expression of Interest to EOI-EPDPTeam-Chair(a)icann.org<mailto:EOI-EPDPTeam-Chair@icann.org> by 22 March 2019 at 14:00 UTC. Please answer the following questions: · What is your interest in this position? · What particular skills and attributes do you have that will assist you in chairing the EPDP? · What is your knowledge of the Temporary Specification for gTLD Registration Data, EPDP Team's Phase 1 work and associated challenges and requirements particularly as it relates to the EPDP? · What is your experience in and knowledge of the GNSO Policy Development Process, ICANN's consensus policies, ICANN's registry agreements and the Registrar Accreditation Agreement related to gTLD registration data? · Are you able to commit the time required and necessary work needed to chair the EPDP, noting that this to a certain extend will be dependent on the EPDP Team's work plan for phase 2 which is under development? · Conflict of Interest Statement – do you have any affiliation with or involvement in any organization or entity with any financial or non-financial interest in the subject matter of this EPDP? · Please also include: · A link to an up-to-date Statement of Interest (SOI) - https://community.icann.org/display/gnsosoi/New+SOIs · A statement confirming your commitment and ability to act neutrally. Application materials will be reviewed by the Council leadership and will not be shared publicly. Names of applicants, including the recommended candidate, will be shared with the GNSO Council for its consideration. The Council leadership is expected to provide its recommendation to the GNSO Council in time for the GNSO Council meeting on 18 April 2019. Additional questions and inquiries can be sent to EOI-EPDPTeam-Chair(a)icann.org<mailto:EOI-EPDPTeam-Chair@icann.org>. More Information · Temporary Specification for gTLD Registration Data [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> · Additional information about the EPDP is located in Annex-A1 [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> of the ICANN Bylaws and the EPDP Manual [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> [PDF, 345 KB]. · EPDP Charter<https://community.icann.org/x/0opHBQ> · EPDP wiki<https://community.icann.org/x/IYEpBQ> · EPDP Phase 1 Final Report [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draf…> [PDF, 2.7 MB] About EPDP On 17 May 2018, the ICANN Board approved the Temporary Specification for gTLD Registration Data. The Board took this action to establish temporary requirements for how ICANN and its contracted parties would continue to comply with existing ICANN contractual requirements and community-developed policies related to WHOIS, while also complying with the European Union's General Data Protection Regulation (GDPR). The Temporary Specification has been adopted under the procedure for Temporary Policies outlined in the Registry Agreement (RA) and Registrar Accreditation Agreement (RAA). Following adoption of the Temporary Specification, the Board "shall immediately implement the Consensus Policy development process set forth in ICANN's Bylaws." This Consensus Policy development process on the Temporary Specification would need to be carried out within a one-year period. Additionally, the scope includes discussion of a System for Standardized Access to Non-Public Registration Data. However, the discussion of a Standardized Access System will occur only after the EPDP Team has comprehensively answered a series of "gating questions" and non-objection by the GNSO Council. About ICANN ICANN's mission is to help ensure a stable, secure, and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world. ANNEX A – CHAIR RESPONSIBILITIES AND EXPECTATIONS As outlined in the GNSO Working Group Guidelines, the purpose of a Chair is to call meetings, preside over working group (WG) deliberations, manage the process so that all participants have the opportunity to contribute, and report the results of the WG to the Chartering Organization. These tasks require a dedicated time commitment as each call has to be prepared, the agenda concretized, and relevant material has to be reviewed. The Chair shall be neutral. While the Chair may be a member of any group which also has representation on the EPDP Team, the Chair shall not act in a manner which favors such group. The Chair shall not be a member of the PDP Team for purposes of consensus calls. In addition, it is required – that interested candidates have considerable experience in Chairing working groups, and direct experience with at least one GNSO Policy Development Process throughout its lifecycle would be an advantage. Familiarity with the functioning of a Working Group is important to understand the various leadership skills that are necessary to employ during a WG's lifecycle. For example, a chair has to ensure that debates are conducted in an open and transparent matter and that all interests are equally represented within the WG's discussions. During the later stages of a WG when recommendations are drafted, a Chair will benefit from understanding the viewpoints of various members to ensure that an acceptable and effective outcome – ideally in form of consensus – can be achieved. In short, the EPDP Team Chair is expected to: 1. Attend all EPDP Team meetings to ensure continuity and familiarity with the subject matter and the on-going discussions; 2. Prepare meetings by reading all circulated materials; 3. Be familiar with the subject matter, including but not limited to GDPR and data protection laws, and actively encourage participation during the calls 4. Be active on the EPDP Team mailing list and invite EPDP Team participants to share their viewpoints; 5. Drive forward the EPDP Team and assure that discussions remain on point; 6. Work actively towards achieving policy recommendations that ideally receive full consensus; 7. Ensure that particular outreach efforts are made when community reviews are done of the EPDP Team's output; 8. Underscore the importance of achieving overall representational balance on any sub-teams that are formed; 9. Encourage and, where necessary, enforce the ICANN Standards of Behavior and resolve any conflicts in a timely manner. 10. Co-ordinate with ICANN staff and ensure that the EPDP Team is supported as effectively as possible 11. Conduct consistent timely reporting to the GNSO Council on the progress of the EPDP. Finally, as also pointed out the in GNSO Working Group Guidelines, 'appointing a co-chair(s) or vice-chair(s) may facilitate the work of the Chair by ensuring continuity in case of absence, sharing of workload, and allowing the Chair to become engaged in a particular debate.' As a result, similar tasks and skills are expected from vice chairs, although the overall workload may be reduced as a result of being able to share this with the Chair. 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…>

1 0

Re: [GNSO-RPM-WG] [Ext] Re: Recent Correspondence Related to Complaints Issues within the RPM PDP WG & Expected Standards of Behavior
by Julie Hedlund April 5, 2019

April 5, 2019

Hi Paul, You may try it without the [icann.org] append, as in: https://www.icann.org/resources/pages/correspondence<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> That should resolve. Best, Julie From: Paul Keating <Paul(a)law.es> Date: Wednesday, March 13, 2019 at 8:51 PM To: Julie Hedlund <julie.hedlund(a)icann.org>, "gnso-rpm-wg(a)icann.org" <gnso-rpm-wg(a)icann.org> Subject: [Ext] Re: [GNSO-RPM-WG] Recent Correspondence Related to Complaints Issues within the RPM PDP WG & Expected Standards of Behavior I get a page does not exist error. From: GNSO-RPM-WG <gnso-rpm-wg-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Wednesday, March 13, 2019 at 10:08 AM To: "gnso-rpm-wg(a)icann.org" <gnso-rpm-wg(a)icann.org> Subject: [GNSO-RPM-WG] Recent Correspondence Related to Complaints Issues within the RPM PDP WG & Expected Standards of Behavior Dear RPM PDP Working Group members, Please see the recent correspondence related to Complaints Issues within the Rights Protection Mechanisms PDP Working Group and Expected Standards of Behavior. These letters were posted on ICANN Org’s correspondence page on 9 & 10 March: https://www.icann.org/resources/pages/correspondence [icann.org] [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>.” Best regards Julie, Ariel & Mary _______________________________________________ GNSO-RPM-WG mailing list GNSO-RPM-WG(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-rpm-wg[cid:image001.png@01D4D99B…

3 3