RPM Charter Addendum - Motion for Council Vote on 23 January
Hi all, Please find below and attached the motion for the GNSO Council's 23 January vote to approve the RPM Charter addendum establishing an IGO Work Track. I would like to invite John or Martin, as members of the small team dedicated to finalizing the addendum, to second this motion. Regards, Keith WHEREAS: 1. On 9 July 2018, the Policy Development Process (PDP) Working Group on International Governmental Organizations (IGO) and International Non-Governmental Organizations (INGO) Access to Curative Rights Protection Mechanisms submitted its Final Report<https://gnso.icann.org/en/issues/igo-ingo-crp-access-final-17jul18-en.pdf> to the GNSO Council. The Final Report contains five policy recommendations on which the Working Group reached consensus. 2. On 19 July 2018, the GNSO Council acknowledged<https://gnso.icann.org/en/council/resolutions#20180719-1> receipt of the PDP Final Report, noted that, "[i]n view of the need to consider the topic of curative rights protections for IGOs in the broader context of appropriate overall scope of protection for all IGO identifiers (including IGO acronyms), the GNSO Council intends to review this Final Report ... with a view toward developing a possible path forward that will also facilitate the resolution of the outstanding inconsistencies between GAC advice and prior GNSO policy recommendations on the overall scope of IGO protections"; 3. Between July 2018 and March 2019, the GNSO Council discussed the PDP Final Report at various meetings and considered the procedural options available to it under the GNSO's Operating Rules and ICANN Bylaws 4. On 18 April 2019, the GNSO Council resolved to approve, and recommend that the ICANN Board adopt, Recommendations 1, 2, 3 & 4 of the PDP Final Report. 5. The GNSO Council elected not to approve Recommendation 5 of the PDP Final Report and directed the Review of All Rights Protection Mechanisms in All gTLDs (RPM) PDP to consider, as part of its Phase 2 work, whether an appropriate policy solution can be developed that is generally consistent with Recommendations 1, 2, 3 & 4 of the PDP Final Report and: a. accounts for the possibility that an IGO may enjoy jurisdictional immunity in certain circumstances; b. does not affect the right and ability of registrants to file judicial proceedings in a court of competent jurisdiction; c. preserves registrants' rights to judicial review of an initial UDRP or URS decision; and d. recognizes that the existence and scope of IGO jurisdictional immunity in any particular situation is a legal issue to be determined by a court of competent jurisdiction. 6. The GNSO Council had engaged with the GAC on several occasions during its deliberations on the PDP Final Report, including at the joint GAC-GNSO meeting at ICANN65 in Kobe, Japan, where the GNSO Council had sought the GAC's feedback on the GAC's willingness to participate in a targeted effort focusing on the issue of curative rights for IGOs and possibly drawing on the community's recent experiences with the Expedited PDP on the Temporary Specification and Work Track 5 of the GNSO New gTLD Subsequent Procedures PDP 7. At ICANN65 in Marrakech, members of the GNSO Council met with certain members of the GAC and IGOs, where there appeared to be agreement from the GAC/IGOs to support the chartering of this separate work. On 20 August, the GAC sent a letter<https://www.icann.org/en/system/files/correspondence/ismail-to-chalaby-20aug...> to the ICANN Board, affirming, "its willingness to participate in such chartering effort." Dialogue between the GNSO Council, GAC, and IGOs continued at ICANN66 in Montreal, followed by further discussions within the Council. 8. The GNSO Council, in consultation with the GAC and IGOs, has prepared the necessary amendments to the RPMs Charter, in the form of an Addendum to that Charter ("Addendum"). RESOLVED: 1. The GNSO Council adopts the amendments to the RPMs Charter to create an IGO Work Track, as reflected in the Addendum. 2. The GNSO shall collaborate with each GNSO Stakeholder Group, Constituency, SO and AC to expeditiously issue a call for Members and Observers to join the IGO Work Track, each in accordance with its own rules. The GNSO Council specifically notes that Members and Observers, although appointed by community groups, must nevertheless meet the Membership Criteria as defined in the Addendum. 3. In accordance with the Addendum, the GNSO Council shall conduct an Expressions of Interest process as soon as is reasonably possible, in order to identify and confirm a single, qualified Work Track Chair, consistent with the criteria as defined in the Addendum. 4. The GNSO Council directs the Work Track Chair and Members to conduct its work in as efficient and effective a manner as possible; and as such, monthly written updates shall be submitted to the GNSO Council by the IGO Work Track Chair and/or Council liaison to the Work Track. These updates must include a report as to the progress of the Work Track according to the timeline and milestones identified in its Work Plan. 5. The GNSO Council further directs the Work Track Chair and Members to develop a Work Plan and timeline for its work as a matter of priority and as its first order of business. To facilitate this effort, the GNSO Council instructs ICANN staff to prepare a draft Work Plan and timeline for the Work Track, based on the model adopted for the Expedited Policy Development Process on gTLD Registration Data. The GNSO Council requests that the Work Track Chair submit a proposed Work Plan and timeline to the GNSO Council within four (4) weeks of the first meeting of the Work Track. 6. To facilitate communications between the GNSO and the GAC on this topic, the GNSO Council directs the GNSO liaison to the GAC to provide regular progress reports to the GAC, in accordance with the GAC's internal rules and processes. 7. The GNSO Council thanks the members of the GNSO Council, as well as those from the GAC and IGOs, for their contributions in developing the Addendum.
Thank you for this Keith, it has been posted on Motions wiki page: https://community.icann.org/x/8gCJBw Kind regards, Terri From: council <council-bounces@gnso.icann.org> on behalf of "Drazek, Keith via council" <council@gnso.icann.org> Reply-To: "Drazek, Keith" <kdrazek@verisign.com> Date: Monday, January 13, 2020 at 5:44 PM To: "council@gnso.icann.org" <council@gnso.icann.org> Cc: "gnso-secs@icann.org" <gnso-secs@icann.org> Subject: [council] RPM Charter Addendum - Motion for Council Vote on 23 January Hi all, Please find below and attached the motion for the GNSO Council’s 23 January vote to approve the RPM Charter addendum establishing an IGO Work Track. I would like to invite John or Martin, as members of the small team dedicated to finalizing the addendum, to second this motion. Regards, Keith WHEREAS: 1. On 9 July 2018, the Policy Development Process (PDP) Working Group on International Governmental Organizations (IGO) and International Non-Governmental Organizations (INGO) Access to Curative Rights Protection Mechanisms submitted its Final Report [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_issue...> to the GNSO Council. The Final Report contains five policy recommendations on which the Working Group reached consensus. 2. On 19 July 2018, the GNSO Council acknowledged [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_counc...> receipt of the PDP Final Report, noted that, "[i]n view of the need to consider the topic of curative rights protections for IGOs in the broader context of appropriate overall scope of protection for all IGO identifiers (including IGO acronyms), the GNSO Council intends to review this Final Report … with a view toward developing a possible path forward that will also facilitate the resolution of the outstanding inconsistencies between GAC advice and prior GNSO policy recommendations on the overall scope of IGO protections"; 3. Between July 2018 and March 2019, the GNSO Council discussed the PDP Final Report at various meetings and considered the procedural options available to it under the GNSO's Operating Rules and ICANN Bylaws 4. On 18 April 2019, the GNSO Council resolved to approve, and recommend that the ICANN Board adopt, Recommendations 1, 2, 3 & 4 of the PDP Final Report. 5. The GNSO Council elected not to approve Recommendation 5 of the PDP Final Report and directed the Review of All Rights Protection Mechanisms in All gTLDs (RPM) PDP to consider, as part of its Phase 2 work, whether an appropriate policy solution can be developed that is generally consistent with Recommendations 1, 2, 3 & 4 of the PDP Final Report and: * accounts for the possibility that an IGO may enjoy jurisdictional immunity in certain circumstances; * does not affect the right and ability of registrants to file judicial proceedings in a court of competent jurisdiction; * preserves registrants' rights to judicial review of an initial UDRP or URS decision; and * recognizes that the existence and scope of IGO jurisdictional immunity in any particular situation is a legal issue to be determined by a court of competent jurisdiction. 6. The GNSO Council had engaged with the GAC on several occasions during its deliberations on the PDP Final Report, including at the joint GAC-GNSO meeting at ICANN65 in Kobe, Japan, where the GNSO Council had sought the GAC’s feedback on the GAC's willingness to participate in a targeted effort focusing on the issue of curative rights for IGOs and possibly drawing on the community's recent experiences with the Expedited PDP on the Temporary Specification and Work Track 5 of the GNSO New gTLD Subsequent Procedures PDP 7. At ICANN65 in Marrakech, members of the GNSO Council met with certain members of the GAC and IGOs, where there appeared to be agreement from the GAC/IGOs to support the chartering of this separate work. On 20 August, the GAC sent a letter [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system...> to the ICANN Board, affirming, “its willingness to participate in such chartering effort.” Dialogue between the GNSO Council, GAC, and IGOs continued at ICANN66 in Montreal, followed by further discussions within the Council. 8. The GNSO Council, in consultation with the GAC and IGOs, has prepared the necessary amendments to the RPMs Charter, in the form of an Addendum to that Charter (“Addendum”). RESOLVED: 1. The GNSO Council adopts the amendments to the RPMs Charter to create an IGO Work Track, as reflected in the Addendum. 2. The GNSO shall collaborate with each GNSO Stakeholder Group, Constituency, SO and AC to expeditiously issue a call for Members and Observers to join the IGO Work Track, each in accordance with its own rules. The GNSO Council specifically notes that Members and Observers, although appointed by community groups, must nevertheless meet the Membership Criteria as defined in the Addendum. 3. In accordance with the Addendum, the GNSO Council shall conduct an Expressions of Interest process as soon as is reasonably possible, in order to identify and confirm a single, qualified Work Track Chair, consistent with the criteria as defined in the Addendum. 4. The GNSO Council directs the Work Track Chair and Members to conduct its work in as efficient and effective a manner as possible; and as such, monthly written updates shall be submitted to the GNSO Council by the IGO Work Track Chair and/or Council liaison to the Work Track. These updates must include a report as to the progress of the Work Track according to the timeline and milestones identified in its Work Plan. 5. The GNSO Council further directs the Work Track Chair and Members to develop a Work Plan and timeline for its work as a matter of priority and as its first order of business. To facilitate this effort, the GNSO Council instructs ICANN staff to prepare a draft Work Plan and timeline for the Work Track, based on the model adopted for the Expedited Policy Development Process on gTLD Registration Data. The GNSO Council requests that the Work Track Chair submit a proposed Work Plan and timeline to the GNSO Council within four (4) weeks of the first meeting of the Work Track. 6. To facilitate communications between the GNSO and the GAC on this topic, the GNSO Council directs the GNSO liaison to the GAC to provide regular progress reports to the GAC, in accordance with the GAC’s internal rules and processes. 7. The GNSO Council thanks the members of the GNSO Council, as well as those from the GAC and IGOs, for their contributions in developing the Addendum.
Please find below and attached the motion for the GNSO Council’s 23 January vote to approve the RPM Charter addendum establishing an IGO Work Track.
Thanks, Keith!
6. To facilitate communications between the GNSO and the GAC on this topic, the GNSO Council directs the GNSO liaison to the GAC to provide regular progress reports to the GAC, in accordance with the GAC’s internal rules and processes.
I am slightly concerned by the wording of this. "In accordance with the GAC’s internal rules and processes" is rather open-ended. Is it our job to be aware of and confirm to GAC internal procedures? I assume the actual progress reports will come from the WT leads and staff, or am I, as liaison to the GAC, expected to participate in the WT and produce independent reports? Julf Julf
Council, I would like to propose an amendment based on Julf input on .6. so it reads only “6. In accordance with the GAC’s internal rules and processes" Best, Martín
On 15 Jan 2020, at 08:44, Johan Helsingius <julf@julf.com> wrote:
Please find below and attached the motion for the GNSO Council’s 23 January vote to approve the RPM Charter addendum establishing an IGO Work Track.
Thanks, Keith!
6. To facilitate communications between the GNSO and the GAC on this topic, the GNSO Council directs the GNSO liaison to the GAC to provide regular progress reports to the GAC, in accordance with the GAC’s internal rules and processes.
I am slightly concerned by the wording of this. "In accordance with the GAC’s internal rules and processes" is rather open-ended. Is it our job to be aware of and confirm to GAC internal procedures?
I assume the actual progress reports will come from the WT leads and staff, or am I, as liaison to the GAC, expected to participate in the WT and produce independent reports?
Julf
Julf _______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
So what would the amended wording read as? Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ http://blacknight.blog/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Personal blog: https://michele.blog/ Some thoughts: https://ceo.hosting/ ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 On 23/01/2020, 09:03, "council on behalf of Martin Pablo Silva Valent" <council-bounces@gnso.icann.org on behalf of mpsilvavalent@gmail.com> wrote: Council, I would like to propose an amendment based on Julf input on .6. so it reads only “6. In accordance with the GAC’s internal rules and processes" Best, Martín > On 15 Jan 2020, at 08:44, Johan Helsingius <julf@julf.com> wrote: > >> Please find below and attached the motion for the GNSO Council’s 23 >> January vote to approve the RPM Charter addendum establishing an IGO >> Work Track. > > Thanks, Keith! > >> 6. To facilitate communications between the GNSO and the GAC on this >> topic, the GNSO Council directs the GNSO liaison to the GAC to >> provide regular progress reports to the GAC, in accordance with the >> GAC’s internal rules and processes. > > I am slightly concerned by the wording of this. "In accordance with the > GAC’s internal rules and processes" is rather open-ended. Is it our job > to be aware of and confirm to GAC internal procedures? > > I assume the actual progress reports will come from the WT leads and > staff, or am I, as liaison to the GAC, expected to participate in the WT > and produce independent reports? > > Julf > > > Julf > _______________________________________________ > council mailing list > council@gnso.icann.org > https://mm.icann.org/mailman/listinfo/council > > _______________________________________________ > By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. _______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
participants (5)
-
Drazek, Keith -
Johan Helsingius -
Martin Pablo Silva Valent -
Michele Neylon - Blacknight -
Terri Agnew