[ALT-Plus] Summary Report of GNSO Council 20 Apr 2023 meeting
Natalia Filina
filinafilka at gmail.com
Mon Apr 24 12:06:50 UTC 2023
Dear Justine,
Thank you very much for the excellent report, structure and clarity.
Very informative and useful as always.
Hugs,
Natalia Filina
Moscow, Russia
пн, 24 апр. 2023 г. в 10:41, Justine Chew via ALT-Plus <alt-plus at icann.org>:
> All,
>
> I am submitting a written report ahead of the ALAC monthly meeting of 25
> Apr. In case I unexpectedly miss the ALAC call (due to the timing), please
> feel free to contact me by email before or after the call should you have
> any questions regarding this report.
>
> *Special Summary Report of 20 Apr 2023 Meeting to ALT-PLUS
> <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct+2021#Apr2023-SumRep_Apr2023>*
>
> For brevity, I will just highlight a few things here. For some of the
> issues, you can glean a wider perspective from GNSO Council Apr 2023
> Matters of Interest and/or from GNSO Council Apr 2023 Meeting Records.
>
> *1. Consent Agenda Items*
>
> - Council agreed to defer consideration of a Policy Status Report
> (PSR) for the Expedited Domain Deletion Policy (EDDP) and Expedited
> Registration Recovery Policy (ERRP) for 6 months from the date additional
> requested information from ICANN org is received.
> - Council agreed to defer next steps on Phase Two of the RPMs PDP for
> an 18-month period beginning on 20 April 2023.
> - Council approved the Final Report
> <https://mm.icann.org/pipermail/council/2023-March/026675.html> of the
> CSC Effectiveness Review Team.
>
> *2. Subsequent Procedures (SubPro) & Next Round of New gTLDs*
>
> * Recap: ICANN Board 16 March 2023 Resolution
> <https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-16-03-2023-en#section2.a>*
>
> - ICANN Board had resolved
> <https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-16-03-2023-en#section2.a> during
> its Board Meeting at ICANN76 <https://icann76.sched.com/event/1J4ZL> to
> adopt the SubPro Outputs in Section A of its "Scorecard on Subsequent
> Procedures PDP" (Scorecard)
> <https://www.icann.org/en/system/files/files/scorecard-subpro-pdp-board-action-16mar23-en.pdf>;
> marking 38 Outputs in Section B of the Scorecard as "pending" and noting
> ongoing community discussions relating to Topic 17: Applicant Support,
> Topic 23: Closed Generics, and Topic 25: Internationalized Domain Names
> (IDNs), as well as additional dependencies concerning specific Review Team
> Recommendations, the Name Collision Analysis Project Study 2 Report
> (NCAP2), and other items noted in Section C of the Scorecard.
>
> * Section A Outputs: Next Steps*
>
> - The SubPro Implementation Review Team (SubPro IRT) will be
> constituted: call for volunteers
> <https://www.icann.org/en/announcements/details/icann-calls-for-volunteers-for-the-new-gtld-program-next-round-implementation-review-team-05-04-2023-en> has
> gone out, criteria apply.
> - This IRT will take on the Open + Representative model and is
> expected to start work in the week of 14/15 May.
>
> * Section B Outputs: 38 "Pending" Outputs*
>
> - The Council's SubPro Pending Recommendations Small Team has been
> discussing with Avri Doria and Becky Burr (from the Board SubPro Caucus) to
> seek clarification on the Board's concerns on the 38 Pending SubPro
> Outputs, in order to conduct a triage of the outputs.
> - The small team - comprising Anne Aikman-Scalese, Bruna Martins dos
> Santos, Jeff Neuman, Justine Chew, Nacho Amados, Paul McGrady, Sebastien
> Ducos, Stephanie Perrin, Susan Payne and Tomslin Samme-Nlar - is working
> towards discussing the outcomes of its triage exercise with the full
> Council at an *GNSO Extraordinary Council meeting on 4 May*. This is a
> step towards meeting Deliverable #1 in *ICANN Board 16 March 2023
> Resolution
> <https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-16-03-2023-en#section2.a>* for
> "*A plan and timeline as agreed upon by the ICANN Board and the GNSO
> Council for consideration and resolution of all Outputs contained in
> Section B of the Scorecard*".
> - The 4 May extraordinary meeting is also expected to determine
> whether the current small team will continue beyond the triage exercise or
> will be reconstituted for next steps.
> - There is a high expectation that (a small team or) the full Council
> will, prior to ICANN77, meet with either the full Board or the full Board
> SubPro Caucus to iron out/resolve many, if not all, the hindrance to the
> Board's approving these 38 pending outputs.
>
> *Action by ALAC Liaison*
>
> To monitor and keep sharing updates regarding progress of the
> Council Small Team work on the 38 Pending Outputs
>
> - With the CPWG SubPro Prioritization Sub-Team; and
> - To assist in formulating ALAC positions on the 38 Pending Outputs
> (if any) in time for the pre-ICANN77 ALAC-GNSO Bilateral.
>
>
> -
>
> *3. Closed Generics : Next Steps *
>
> - Closed Generics is a Board SubPro PDP Scorecard Section C Dependency.
> - Council received an update from John McElwaine, its Liaison to the
> GNSO-GAC-ALAC Dialogue on Closed Generics who indicated that a draft
> framework is anticipated to be ready around 28 April for community comment,
> and that the work of the group will continue into Q3 of 2023 beyond
> ICANN77, but still meet Deliverable #3 in *ICANN Board 16 March 2023
> Resolution
> <https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-16-03-2023-en#section2.a>* for
> "*A GNSO Council project plan and timeline for policy work, or an
> alternate path, on how to handle closed generics for the next round of new
> gTLDs.*"
> - Notwithstanding, John hinted that because the framework will require
> a policy process for it to become policy, the suitable path would be a
> tightly scoped EPDP.
> - More and better details will be forthcoming through the draft
> framework expected next week. More and better details should also be sought
> from the ALAC representative and/or alternate to this Dialogue.
>
> *Action by ALAC Liaison*
>
>
>
> - To monitor and share updates on the proposed framework for Closed
> Generics
> - To coordinate with ALAC's rep & alternate and At-Large staff on
> consultation for the proposed framework for Closed Generics.
>
> *4. DNS Abuse: Next Steps*
>
> - Following Council's DNS Abuse Small Team's 7 Oct 2022 report to
> Council, where Recommendation #2 advised Council to request, et. al., the
> Registrar Stakeholder Group “to further 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, the GNSO
> Council will consider whether further action on bulk registrations is
> deemed necessary.”
> - Council has determined that this small team should continue its work
> reviewing the replies received from gTLD Registries Stakeholder Group
> <https://gnso.icann.org/sites/default/files/policy/2023/correspondence/woods-to-ducos-03mar23-en.pdf>
> , Registrar Stakeholder Group
> <https://gnso.icann.org/sites/default/files/policy/2023/correspondence/heineman-to-ducos-13mar23-en.pdf>
> , ICANN Contractual Compliance
> <https://gnso.icann.org/sites/default/files/policy/2023/correspondence/hedlund-to-ducos-22feb23-en.pdf>
> and DNS Abuse Institute
> <https://gnso.icann.org/sites/default/files/policy/2023/correspondence/bunton-to-ducos-27feb23-en.pdf> to
> its 6 Jan letter
> <https://gnso.icann.org/sites/default/files/policy/2023/correspondence/ducos-to-heineman-et-al-06jan23-en.pdf>
> .
> - This Council small team now has a refreshed membership of Thomas
> Rickert (ISCP), Mark Datysgeld (BC), Wisdom Donkor (NCSG), Theo Geurts
> (RrSG), Sebastien Ducos (RySG), Greg DiBiase (RrSG), Tomslin Samme-Nlar
> (NCSG), Paul McGrady (NCA-NCPH), Nacho Amadoz (RySG) and Justine Chew
> (ALAC Liaison to the GNSO).
> - NB. The deliberations of the issue of bulk registrations are running
> parallel to the ICANN org - Contracted Parties ongoing contractual
> amendment negotiations on RAA section 3.18 (and perhaps, less on RA Spec 11
> 3(a))
>
> *5. Registration Data Accuracy (RDA)*
>
> - Council considered the Survey Summary Results
> <https://gnso.icann.org/sites/default/files/policy/2023/presentation/registration-data-accuracy-scoping-team-survey-summary-results-13apr23-en.pdf> and
> Council Leadership alluded to inputs from these results being taken into
> consideration in relevant fora - in this case, the re-charter of the RDA
> Scoping Team, but also any relevant GNSO processes in future.
> - Council also received an update
> <https://www.icann.org/en/system/files/correspondence/gutterman-to-ducos-14mar23-en.pdf> from
> ICANN org on the 4 scenarios that have been identified to review the
> accuracy of registration data and the data protection questions that arise
> from these scenarios. I believe this input is for the RDA Scoping Team (or
> successor) to consider once it is reconstituted.
>
> *6. Registration Data Request Service (RDRS)*
>
> - ICANN org has informed that it is ready to start development of the
> RDRS. A demo could be expected in the ICANN77 June time frame.
> - This is while the EPDP Phase 2 Small Team continues work (1) to
> establish success factors for the RDRS - eg. on how to ensure wide
> participation/usage of the RDRS especially by non-RrSG registrars (if it
> were kept as voluntary); and (2) what can be extracted from the data
> collected via the RDRS.
>
>
> Thanks for reading / your consideration.
>
> Justine Chew
> ALAC Liaison to the GNSO
> GNSO Liaison Report Workspace
> <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct+2021>
>
>
>
>
> On Tue, 11 Apr 2023 at 19:14, Justine Chew <justine.chew.icann at gmail.com>
> wrote:
>
>> Dear all,
>>
>> Just a note to inform you that the next GNSO Council meeting agenda is
>> out as follows.
>>
>> It is a very packed agenda with many items that would be of interest to
>> ALAC/At-Large, so it is likely easier to draw your attention to the curated
>> version of the highlighted agenda items, which is posted at this link
>> <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct+2021#Apr2023-MOI_Apr2023>
>> .
>>
>> Otherwise, here is the high level view of the agenda items:
>>
>> *GNSO Council Meeting #4 of 2023 held on 20 Apr 2023*
>>
>> *Full Agenda <https://community.icann.org/x/6AE5Dg> | Motions
>> <https://community.icann.org/x/6gE5Dg> | Documents
>> <https://community.icann.org/x/5gE5Dg>*
>>
>> - *Item 1: Administrative Matters*
>> - Item 2: Opening Remarks / Review of Projects
>> <https://gnso.icann.org/en/council/project> & Action Item List
>> <https://community.icann.org/x/RgZlAg>
>> - *Item 3: Consent Agenda*
>> - *Item 4: COUNCIL DISCUSSION - Accuracy - Results of Scoping Team’s
>> Self-Assessment Survey + Update from ICANN org*
>> - *Item 5: COUNCIL DISCUSSION - Update from Council SubPro Small Team*
>> - *Item 6: COUNCIL DISCUSSION - Update from EPDP Phase 2 Small Team*
>> - *Item 7: COUNCIL DISCUSSION - Next Steps on Closed Generics*
>> - *Item 8: COUNCIL DISCUSSION - Next Steps on DNS Abuse*
>> - *Item 9: ANY OTHER BUSINESS*
>>
>>
>> If you would like to observe the meeting, please check this link
>> <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct+2021#Apr2023-Meet_Apr2023temp>
>> for details.
>>
>> Thanks for reading / your consideration.
>>
>> Justine Chew
>> ALAC Liaison to the GNSO
>> GNSO Liaison Report Workspace
>> <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct+2021>
>> ------
>>
>> _______________________________________________
> 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/20230424/7d53976f/attachment-0001.html>
More information about the ALT-Plus
mailing list