[ALT-Plus] Summary Report of GNSO Council 17 Nov 2022 meeting

Sebastien Bachollet sebicann at bachollet.fr
Sat Nov 19 10:16:24 UTC 2022


Thanks Justine 
As usual great job 
May I ask you few acronyms explanation 
RPMs IRT
EDPB
DNSAI

Thanks 


Sébastien Bachollet 
Envoyé de mon iPhone

> Le 19 nov. 2022 à 10:18, Justine Chew via ALT-Plus <alt-plus at icann.org> a écrit :
> 
> 
> All,
> 
> I am submitting my written report ahead of the ALAC monthly meeting on 22 Nov. This, even though summary in form, is considerably lengthier than usual. It is also recorded on the GNSO Liaison workspace should you find it easier to absorb with the various references.  Happy to answer questions, if any.
> 
> Special Summary Report of 17 Nov 2022 Meeting to ALT-PLUS
> For brevity, I will just provide highlights. For some of the issues, you can glean a wider perspective from GNSO Council Nov 2022 Matters of Interest and/or from GNSO Council Nov 2022 Meeting Records.
> 1. Consent Agenda
> Council acknowledged John McElwaine as the GNSO Council Liaison to the RPMs IRT.
> 2. Expedited Policy Development Process on Internationalized Domain Names (part of Consent Agenda also)
> Council approved the EPDP's Project Change Request (PCR) wherein the EPDP sought:
> To facilitate the implementation planning of the New gTLD Subsequent Procedures by bifurcating its work into two phases, with Phase 1 covering topics related to top-level IDN gTLD definition and variant management, and Phase 2 covering issues pertaining to second-level IDN variant management, and
> Due to the diversity and complexity of IDN issues, additional data collection needs, review of ICANN org input for draft recommendations, and public comment-related processes, a 31-month extension to the original project plan, with projection of the following key milestone dates:
> Publish Phase 1 Initial Report for Public Comment by April 2023
> Submit Phase 1 Final Report to the GNSO Council by November 2023
> Publish Phase 2 Initial Report for Public Comment by April 2025
> Submit Phase 2 Final Report to the GNSO Council by November 2025
> 3. Whois Disclosure System (WDS) Next Steps / EPDP Phase 2
> Council accepted the EPDP Phase 2 small team findings and recommendations as outlined in the small team's addendum.
> Council also confirms that pending the implementation and subsequent running of the WDS for a period of up to two (2) years, the SSAD recommendations should remain paused for consideration by the ICANN Board.
> 4.  Registration Data Accuracy Scoping Team 
>      In relation to the Scoping Team's write up which recommended:
> 1) pausing the work in relation to proposals that require access to registration data,
> 2) encouraging ICANN org to proceed with their outreach to the EDPB as well as the Data Protection Impact Assessment in connection with the scenario(s) in which the request and processing of registration data takes place as a matter of urgency, and
> 3) requesting that ICANN org and Contracted Parties finalize the negotiations on the Data Processing Agreement (DPA) as soon as practicable as the absence of a completed DPA may act as a roadblock for policy work before Council
> Council adopted recommendation #3
> Council deferred consideration of recommendations #1 and #2 until such time the DPA negotiations between ICANN org and Contracted Parties have completed and there is feedback from ICANN org on if/how it anticipates the requesting and processing of registration data will be undertaken in the context of measuring accuracy, or for six months, whichever is the shorter
> Once the DPA negotiations are completed and the feedback referred to at paragraph 2 is received from ICANN org, Council will review the formation and instructions to the Scoping Team to ensure these are still fit for purpose and request the Scoping Team to further consider potential proposals that require access to registration data as well as how these impact the existing recommendations #1 and #2 (e.g. should these still be considered by Council for adoption, or in the context of proposals that require access to registration data these may no longer be relevant or a priority?). If, after 6 months from this resolution, the DPA negotiations are not completed and/or the required feedback referred to at paragraph 2 has not been provided by ICANN org, Council will discuss and determine whether or not to continue deferring the consideration of recommendations #1 and #2.
> Taking into account the delay with which the write up was delivered, as well as some of the challenges that were shared with the Scoping Team’s Chair during his briefing to the Council, Council leadership will reach out informally to Scoping Team members to better understand the issues encountered to help inform the Council’s review of the formation and instructions.
> Council leadership is requested to send a communication to ICANN org in relation to recommendation #3 (as well as Contracted Parties in relation to the DPA) as well as communicateCouncil’s decision to non-GNSO groups participating in this effort (ALAC, GAC and SSAC) as well as the Scoping Team.
> Council thanks Michael Palage, outgoing Chair, and Olga Cavalli, outgoing Council liaison, for their efforts. As part of its review of the formation and instructions to the Scoping Team, Council will consider next steps for finding new leadership for this effort.
> 5. DNS Abuse Small Team Report
>     In relation to the small team's report, containing 4 recommendations, delivered to Council on 10 October, which in summary are:           
> 1) Recommendation #1 re Malicious Registrations: After the community has been able to process the community outreach and other suggestions made in this report, if further tools are considered necessary, the small
> team recommends that Council considers requesting the development of a Preliminary Issue Report on the topic of malicious registrations,
> 2) Recommendation #2 re Bulk Registrations: The small team recommends that Council requests RrSG and others (for example, ICANN org, the RySG and the DNSAI) to further explore the role that bulk registrations play in DNS Abuse as well as measures that Registrars may have already put in place to address this vector. Based on the feedback received, Council will consider whether further action on bulk registrations is deemed necessary,
> 3) Recommendation #3 re DNS Abuse Reporting: With an eye towards outreach, the small team recommends that Council encourages continued discussion between Contracted Parties and DNS Abuse reporters/potential reporters with the goal of further fine-tuning and promoting existing tools and initiatives, and/or those under development, to further work towards easier, better and actionable reporting of DNS Abuse. Take into consideration additional pipelines that might be helpful, and
> 4) Recommendation #4 re Action & Enforcement: The small team recommends that Council reaches out, via a letter, to the RrSG and RySG to share the findings of the small team and requests feedback on how these
> potential gaps can be best addressed. This letter should request that Contracted Parties initiate work on the “Suggested Standards” document in consultation with ICANN Compliance.  Based on the feedback received to this letter, Council will determine next steps, but at a minimum, Council would expect to be kept up to date on any further work that would be undertaken by Contracted Parties in consultation with ICANN Compliance.
> Council accepts the recommendations as outlined in the report and requests that the leadership of the small team works with Council leadership on developing the respective communications as foreseen under recommendations #2, #3 and #4.
> In relation to recommendation #1, Council commits to considering requesting the development of a Preliminary Issue Report on the topic of malicious registrations after the outreach and communication as foreseen under recommendations #2, #3 and #4 have taken place and Council has had an opportunity to consider the progress made from efforts related to that outreach. If Council determines that a Preliminary Issue Report is needed, it must be undertaken in a way that avoids overlap and/or duplication of efforts.
> Council thanks the small team for its efforts, as well as the community groups that contributed to it.
> 6. Uniform Domain Name Dispute Resolution Policy (UDRP) (Phase 2 of Rights Protection Mechanisms (RPMs) in all New gTLDs)
> After Phase 1 of the RPMs PDP (i.e. review of the Uniform Rapid Suspension (URS)) was completed in January 2021, Phase 2 (i.e. review of the UDRP) was deferred for a number of reasons, including need to redraft its charter, need to prioritise other work so as not to overwhelm the community with more work, Council once again revisited the options on what to do with this review of the UDRP which are:
> 1) Go forward with the review with a to-be-redrafted charter, or
> 2) Defer the work for a set period of time (eg 12 or 18 months) or until triggered (eg by completion of Phase 1 RPMs IRT's work which would then free up community and staff resources), or
> 3) Terminate the RPMs PDP (requiring a super-majority vote) (which effect is thought to be equivalent to a long deferral & re-chartering since all policies needs to be reviewed repeated and periodically).
> There was some support for option 2 in deferring 12-18 months and also the possibility of constituting an 'expert group' to alleviate pressure on the community, and to recharter the PDP to reflect reliance on such a smaller group. No formal decision taken.
> 7. Expired Domain Deletion Policy and the Expired Registration Recovery Policy 
> At Council's request, Contractual Compliance presented on their report to Council of 1 November 2022. Noting that the general perception that no known issues have presented themselves, and that a request for a Policy Status Report (PSR) has already be deferred for 2 years (from November 2020 to November 2022).
> There were suggestions that (1) registrars could be tasked with better handling the ambiguity mentioned as between resellers-registrants on the role of registrars/resellers, and (2) to examine the need for clear policy to address the ambiguity in order to safeguard registrant interests. No formal decision taken.
> 8. Council Committee for Overseeing and Implementing Continuous Improvements (CCOICI) - Work Stream 2 (WS2)
> Council is looking at adopting WS2 Recommendations Report received on 4 November 2022 in its December meeting.
> 
> 
> Thanks for reading / your consideration.
> 
> Justine Chew
> ALAC Liaison to the GNSO 
> GNSO Liaison Report Workspace
> 
> 
> 
>> On Wed, 9 Nov 2022 at 20:26, Justine Chew <justine.chew.icann at gmail.com> wrote:
>> Dear all, 
>> 
>> Apologies for the delay in getting this message out.
>> 
>> Just a note to inform you that the next GNSO Council meeting agenda is as follows. It again has a very full agenda with several matters of interest to us. For a curated version of the highlighted agenda items, please visit this link. 
>> 
>> GNSO Council Meeting #11 of 2022 held on 17 Nov 2022
>> Full Agenda  |  Motions 
>> Item 1: Administrative Matters
>> Item 2: Opening Remarks / Review of Projects & Action List
>> Item 3: Consent Agenda
>> Item 4: COUNCIL VOTE - Whois Disclosure System Next Steps
>> Item 5: COUNCIL VOTE - Registration Data Accuracy Scoping Team - Adoption of Recommendation #3
>> Item 6: COUNCIL VOTE - DNS Abuse Small Team Report
>> Item 7: COUNCIL DISCUSSION - Uniform Domain Name Dispute Resolution Policy (UDRP) Review Next Steps 
>> Item 8: COUNCIL DISCUSSION - Expired Domain Deletion Policy and the Expired Registration Recovery Policy Next Steps
>> Item 9: COUNCIL DISCUSSION - Council Committee for Overseeing and Implementing Continuous Improvements (CCOICI) - Work Stream 2 (WS2)
>> Item 10: COUNCIL DISCUSSION - SPS planning
>> Item 11: ANY OTHER BUSINESS 
>> 
>> I have been contented to monitor items 7, 8 and 9 so far and will continue to do so, with the unchanged goal of assessing whether there might be some action needed by the ALAC/At-Large for each of those items, respectively. 
>> 
>> If you would like to observe the meeting, please check this link for details.
>> 
>> Thanks for reading / your consideration.
>> 
>> Justine Chew
>> ALAC Liaison to the GNSO 
>> GNSO Liaison Report Workspace 
>> 
> _______________________________________________
> ALT-Plus mailing list
> ALT-Plus at icann.org
> https://mm.icann.org/mailman/listinfo/alt-plus
> 
> _______________________________________________
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/alt-plus/attachments/20221119/1e5e7bc3/attachment-0001.html>


More information about the ALT-Plus mailing list