Dear Councilors,

 

Please have a look at Justine’s suggestions for our bilateral session with ALAC at ICANN 73. We will have this on our agenda for the council call, and would suggest to have topic leads on these 4 points if the corresponding small team rapporteur or liaison would be willing (you’d know who you are ;):

1.  Operational Design Assessment of Standardized System for Access/Disclosure  Recommendations

2. Subsequent Procedures Operational Design Phase (SubPro ODP)

3.  DNS Abuse Mitigation

4.  Priorities for 2022

 

Other suggestions for the bilateral would be welcome.

Regards,

Philippe

 

 

Orange Restricted

From: Gnso-chairs <gnso-chairs-bounces@icann.org> On Behalf Of Nathalie Peregrine via Gnso-chairs
Sent: Friday, February 11, 2022 9:33 AM
To: gnso-chairs@icann.org
Cc: gnso-secs@icann.org
Subject: [gnso-chairs] FW: [Ext] ALAC - GNSO Council bilateral session at ICANN73

 

FYI

 

It would be good to have these circulated on the Council mailing list, and also added to the Council agenda.

 

Best,

 

Nathalie

 

From: Justine Chew <justine.chew.icann@gmail.com>
Date: Friday, 11 February 2022 at 02:07
To: Nathalie Peregrine <nathalie.peregrine@icann.org>
Subject: [Ext] ALAC - GNSO Council bilateral session at ICANN73

 

Hi Nathalie,

Here is the list of the issues that the ALAC wishes to raise at its bilateral session with Council during ICANN73, along with the context and questions for consideration. While noting that the list appears lengthy, the ALAC would appreciate if we could try and cover as much of it as is feasible.

1.  Operational Design Assessment of Standardized System for Access/Disclosure  Recommendations
On 25 Jan 2022, ICANN Org released its Operational Design Assessment (ODA) of the Standardized System for Access/Disclosure (SSAD) Recommendations which became a preliminary basis for the GNSO Council's consultation with the ICANN Board on 27 Jan 2022 [icann.zoom.us]. 

  • How does Council intend to proceed with its recommendations on the SSAD given the concerns raised by the ICANN Board, which also reflect concerns contained in the ALAC's Statement of 24 Aug 2020 [atlarge.icann.org]?

2. Subsequent Procedures Operational Design Phase (SubPro ODP)

Although announced on 20 Dec 2021, it is understood that the SubPro ODP had only officially kicked off circa 18 Jan 2022 just before the SSAD ODP came to its conclusion on 25 Jan 2022. 

  • Has Council made any observations or acquired lessons from its involvement with the SSAD ODP which it intends to apply to the SubPro ODP process to improve the efficacy and transparency of the ODP concept for the entire ICANN community?
  • Would Council be able to briefly share any preliminary feedback on the SubPro ODP's progress so far?

3.  DNS Abuse Mitigation

During Part 2 of its meeting on 27 Oct 2021, the GNSO Council established a small team of councilors to draft potential Council next steps regarding DNS Abuse.  

  • Has Council arrived at any next steps regarding DNS Abuse per its agenda?
  • How would Council take on board inputs/efforts from other parts of the ICANN community on such next steps?
  • Would Council be able to share an indication of its plan and timeline for such next steps?

4.  Priorities for 2022

Apart from the SSAD ODA and the SubPro ODP which we know are on Council's agenda, what other priorities have Council identified for 2022? For example:-

    • (a) the implementation of PDP 3.0 and increasing use of the representative model in recently constituted GNSO EPDP and PDP WGs; and/or 
    • (b) any efforts by Council in respect of the continuous improvements to its operating procedure?.


Please let me know if this meets what Council Leadership wanted for purposes of Council's February meeting. I would be happy to address any immediate request for clarification or feedback to the above. 


Many thanks and kind regards,

Justine

 

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.