[ALT-Plus] Summary Report of GNSO Council 19 May 2022 meeting ++

[Justine Chew]

All,

Just sharing some supplementary information as they become available to me
via Council and/or Council Small Team meetings.

*3. SubPro ODP + 4. SubPro GGP*,

   - The SubPro ODP is currently ongoing and is only expected to produce
   an ODA sometime later this year.
   - There remains some aspects of SubPro Outputs which require further
   work by the ICANN community and for now, the topics of interest to the ALAC
   which have been identified for further work are implementation aspects
   related to:
      - the Applicant Support Program (ASP) (possibly touching on some
      policy elements);
      - Limited Public Interest objections (limited to handling frivolous
      objections); and
      - the lowering of the threshold for succeeding in a Community
      Priority Evaluation (CPE).
   - As mentioned earlier, Council is considering initiating a *GNSO
   Guidance Process for Subsequent Procedures* to handle future work on
   topics as identified both from the SubPro Outputs (Group 1 issues) and out
   of the SubPro ODP (Group 2 issues)
   - *Deliberations on this SubPro GPP progresses within Council is ongoing*
   - this GPP is currently envisaged to take on a representative model, and I
   will alert ALAC in due course on the need for ALAC to name its appointees
   to the GPP.


*GNSO-GAC Dialogue on Closed Generics*

   - As has been reported before, the ICANN Board has invited the GNSO and
   the GAC to dialogue on the issue of Closed Generics, in its attempt to
   clarify how applications for Closed Generics might be handled in the next
   round.
   - Councilors making up the GNSO Council Small Team for Closed Generic
   had more or less insisted that ALAC's participation in this dialogue must
   be predicated on not upsetting current negotiations being had within the
   Small Team (and correspondingly within GAC) in relation to the balanced
   number of representatives from GNSO and GAC.
   - Taking note of that condition, then having consulted ALAC leadership
   as well as taking into account the GAC's perspective, I proceeded to seek
   for ALAC to have a single member (+ an alternate) to participate in said
   dialogue.  Following this, there is no longer resistance in this Council
   Small Team to ALAC's participation in the dialogue. *Please note
   however, that the decision whether GNSO will invite ALAC to participate
   lies with Council*. *This question has not be posed to Council yet
   because this Small Team is still working on recommending to Council, the
   parameters for the dialogue*.
   - Things will become clearer as we approach ICANN 74, but at this point
   I am unable to advise if the ALAC/At-Large session on Closed Generics
   during ICANN 74 ought to include any specific angle.


Thanks for reading / your consideration.

Justine Chew
ALAC Liaison to the GNSO Council



On Sun, 22 May 2022 at 18:39, Justine Chew <justine.chew.icann at gmail.com>
wrote:

> All,
>
> I am submitting a written report ahead of the ALAC monthly meeting on 24
> May, so that my 2 minutes at the ALAC call can be used for Q&A instead (if
> any).
>
> As in the past, for brevity, I will just highlight a few things here. For
> some of the issues, you can glean a wider perspective from GNSO Council
> May 2022 Matters of Interest
> <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct+2021#May2022-MOI_May2022>
> and the meeting records from GNSO Council May 2022 Meeting Records
> <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct+2021#May2022-Meet_May2022>
> .
>
> *1. EPDP on Specific Curative Rights Protection for IGOs Final Report*
>
>    - Council was meant to consider and vote on a motion to approve the
>    recommendations in the Final Report but eventually resolved to defer the
>    vote to Council's June 2022 meeting to allow the RrSG time for further
>    consideration prior to the vote.
>
> *NB. Yrjo Lansipuro and I had presented on the substance of the Final
> Report to CPWG on 23 Mar <https://community.icann.org/x/ugN1Cw>, and Yrjo
> has provided updates re its consensus designation thereafter.*
>
> *2. Impact of SSAD Light on other work*
>
>    - Council noted that ICANN org resources were likely being directed by
>    the ICANN Board towards designing SSAD Light, and considered concerns on
>    the impact of this on other ongoing work, including the Subsequent
>    Procedures Operational Design Phase.
>    - Council discussed the concerns but did not arrive at a clear
>    conclusion; Council opined that the Board would not do anything until ICANN
>    74 at the earliest.
>
> *3. SubPro ODP*
>
>    - The ICANN org SubPro ODP team had shared question set #4 and SubPro
>    Topic Assumptions
>    <https://mm.icann.org/pipermail/council/2022-May/025688.html> with
>    Council’s liaison to the ODP who notified Council of the same on 19 May
>    2022 just before Councils' meet. So, Council is to consider this further
>    through its usual process.
>
> *4. GNSO Guidance Process for Subsequent Procedures (SubPro GGP)*
>
>    - GNSO support staff had prepared a draft SubPro GPP Initiation Request
>    <https://mm.icann.org/pipermail/council/2022-May/025646.html> for
>    Council's consideration. If approved, it would be the first GPP ever. Key
>    points to note for the proposed GGP:
>       - A GGP does not require a separate charter. Things like scope,
>       working mechanism, and method of operation should all be contained in the
>       initiation request.
>       - The draft contains a concept of Group 1 versus Group 2 topics.
>       Group 1 is where the SubPro Final Report specifically called out
>       substantive work that it envisioned would be completed during the
>       Implementation Review Team phase. Group 2 will be topics that are
>       identified by the ODP Team, where they are able to determine that
>       additional guidance is needed to support the presumed eventual
>       implementation. The specifics for Group 2 are currently to be determined,
>       as we await input from the ODP Team.
>       - Relevant Outputs from the SubPro Final Report are reproduced,
>       with Tasks identified or TBD. These tasks are envisioned as the specific
>       scope of work for the GGP. Per the previous bullet, the tasks for Group 2
>       are still TBD.
>       - The suggested working model for this group is proposed as a
>       representative steering group, which can do the work itself, but it can
>       also delegate the work to sub-teams where it is evident that the work is
>       best performed by those with specific expertise in a certain field.
>    - Council did not come to a decision on the draft initiation request.
>
> *5. Registration Data Accuracy Scoping Team*
>
>    - Michael Palage, Chair of this Scoping Team, reported that it was
>    informed that the Board had requested ICANN org to submit a list of
>    questions to the European Data Protection Board (EDPB) to gain some insight
>    on 4 different scenarios and for org to do a data privacy impact assessment
>    in connection with one of those scenarios. This was to to better prepare
>    ICANN for onward engagement with the EDPB. All stakeholders in the Scoping
>    Team were to consult their groups on the scenario(s).
>    - Michael had also submitted a Project Change Request (PCR) for
>    Council's consideration; the PCR sought to:
>       - extend the timeline of the Scoping Team's work in order to
>       deliver the write up for assignments #1 and #2 at the latest shortly after
>       ICANN74. The write up for assignments #1 and #2 may include recommendations
>       for further work to be undertaken to gather data to help inform the group’s
>       deliberations on assignments #3 and #4. This work is expected to focus on
>       data gathering that does not involve access to registration data as further
>       clarity on that aspect is being pursued separately.
>    - No objection was raised to the PCR.
>
> *6. ICANN74 planning*
>
>    - There will not be an ALAC-GNSO Council bilateral session at ICANN74;
>    due to brevity in length of ICANN74 and associated challenges of
>    insufficient resources. Instead, a meeting to progress any intersessional
>    work between the 2 groups may be called if needed.
>
>
> NB. The topics of DNS Abuse and GAC-GNSO Dialogue on Closed Generics were
> not on the agenda of this Council meeting.
>
> Thanks for reading / your consideration.
>
> Justine Chew
> ALAC Liaison to the GNSO Council
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/alt-plus/attachments/20220527/b5b8a0a1/attachment.html>