[council] FW: [gnso-secs] EPDP Ph2 SSAD ODP and next steps

Wed Jan 5 13:57:34 UTC 2022

Dear councilors,

Forwarding Janis’ email to the Council mailing list (although the email address was correctly cc-ed), as it doesn’t appear yet on the mailing list archives.

Kind regards,

Nathalie

From: Gnso-secs <gnso-secs-bounces at icann.org> on behalf of "gnso-secs at icann.org" <gnso-secs at icann.org>
Reply to: Janis Karklins <karklinsj at gmail.com>
Date: Wednesday, 5 January 2022 at 11:15
To: "philippe.fouquart at orange.com" <philippe.fouquart at orange.com>
Cc: Steve Chan <steve.chan at icann.org>, "julf at julf.com" <julf at julf.com>, "council at gnso.icann.org" <council at gnso.icann.org>, "gnso-secs at icann.org" <gnso-secs at icann.org>, "secretariat at icannregistrars.org" <secretariat at icannregistrars.org>, "milton at gatech.edu" <milton at gatech.edu>, Andrea Glandon <andrea.glandon at icann.org>, "brian.king at markmonitor.com" <Brian.King at markmonitor.com>, Berry Cobb <Berry.Cobb at icann.org>, "mmcross at amazon.com" <mmcross at amazon.com>, "matt at brandsight.com" <matt at brandsight.com>, "fasonga at gmail.com" <fasonga at gmail.com>, "benakin at gmail.com" <benakin at gmail.com>, "thomas at rickert.law" <thomas at rickert.law>, "alan at donuts.email" <alan at donuts.email>, Ashley Heineman <aheineman at godaddy.com>, "secretariat at rysg.info" <secretariat at rysg.info>, "lschulman at inta.org" <lschulman at inta.org>, James Bladel <jbladel at godaddy.com>, Emily Barabas <emily.barabas at icann.org>, Steve DelBianco <sdelbianco at netchoice.org>, Brenda Brewer <brenda.brewer at icann.org>, "volker.greimann at centralnic.com" <volker.greimann at centralnic.com>, "aelsadr at tucows.com" <aelsadr at tucows.com>, Marc Anderson <mcanderson at verisign.com>, Ariel Liang <ariel.liang at icann.org>, "plommer at gmail.com" <plommer at gmail.com>, "mason.cole at appdetex.com" <mason.cole at appdetex.com>, "marksv at microsoft.com" <marksv at microsoft.com>, "Caitlin.rubergen at icann.org" <Caitlin.rubergen at icann.org>, Mary Wong <mary.wong at icann.org>, "franck_journoud at motionpictures.org" <Franck_Journoud at motionpictures.org>, "stefan.filipovic01 at gmail.com" <stefan.filipovic01 at gmail.com>, "bruna.mrtns at gmail.com" <bruna.mrtns at gmail.com>, Marika Konings <marika.konings at icann.org>, Stephanie Perrin <stephanie.perrin at mail.utoronto.ca>, Julie Hedlund <julie.hedlund at icann.org>, "chair at rysg.info" <chair at rysg.info>, "margiemilam at fb.com" <margiemilam at fb.com>, Wolf-Ulrich Knoben <Wolf-Ulrich.Knoben at t-online.de>
Subject: Re: [gnso-secs] EPDP Ph2 SSAD ODP and next steps

Good morning, Philippe, and all on the list.

Let me start by wishing very happy, successful and productive 2022.

My initial reaction to your and Council leadership reflection is two fold - one always can hope for a better result, but also process can't be eternal. It already has been sufficiently long.
Cost is an issue and we should look into ways to reduce it. Automation of processes may be a solution.
We will not be able to change GDPR. Hence, manual review of requests will remain with us until the GDPR will be modified or Central Gateway recommendations systematically will be identical to the results of the manual review and CPs will accept to follow the CG recommendations.
But all re rest in SSAD needs to be automated. That includes accreditation. Scrapping accreditation will not resolve the issue, but rather increase work (and the cost) for CPs who will need to do manual verification of identity of each requestor.
Automation of accreditation seems feasible. I recall my application for the Canadian visa (to attend ICANN meeting). I filed an online application and 15 min and 7$ later my request was approved. I doubt that a human was involved in that decision. Something similar can be done within SSAD following existing policy recommendations on accreditation.

Hope that might help. Or at least fuel conversation of the group.

With greetings from Strasbourg
JK

On Tue, Jan 4, 2022 at 8:13 PM <philippe.fouquart at orange.com<mailto:philippe.fouquart at orange.com>> wrote:
Dear Councilors,
Dear EPDP Phase 2 members,
Dear SG/C Chairs,

I trust this finds you all well.

Following the informal SSAD ODP update on 20 December, in which representatives from the ICANN Board GDPR Caucus, ICANN org, the GNSO Council and GNSO appointed members of the EPDP Phase 2 team participated, Council leadership has worked with the staff support team on the attached paper which aims to provide a high level outline of the different ideas and suggestions that were made during that meeting. This is intended to serve as a basis for further discussions within the GNSO community for how to prepare for next steps in the consultation with the ICANN Board, which is in the process of being scheduled.

To continue our conversation, obtain further input on possible next steps and assess whether there is possible convergence concerning next steps, we would like to schedule another call for the Council and GNSO appointed members of the EPDP Phase 2 on Wednesday 12 January at 6.00 UTC (a calendar invite will follow shortly). Of course, if there are any ideas or suggestions that have not been captured in the paper, or any new ones that have come to mind since our last meeting, please feel free to share these by replying all to this email.

And Best Wishes for the New Year.
Regards,
Philippe

From: FOUQUART Philippe INNOV/NET
Sent: Friday, December 3, 2021 4:15 PM
To: 'council at gnso.icann.org<mailto:council at gnso.icann.org>' <council at gnso.icann.org<mailto:council at gnso.icann.org>>
Cc: gnso-secs at icann.org<mailto:gnso-secs at icann.org>
Subject: EPDP Ph2 SSAD ODP and next steps

Dear Councilors,

For those that have attended the recent SSAD ODP Webinars, you may be aware that the SSAD ODP Team is in the process of finalizing its analysis, including its work on the SSAD Cost Model. As a result, the Council requested consultation with the ICANN Board is expected to be scheduled in January 2022. To prepare accordingly for this consultation and possible next steps, Council leadership has worked with the staff support team to put forward the following proposed schedule:

  *   16 December 2021 at 14.00 UTC – GNSO Council meeting to discuss the approach outlined in this email
  *   20 December 2021 at 21.00 UTC – Update session on SSAD ODP, including SSAD Cost Model information for Council and GNSO appointed EPDP Team members (closed session)
  *   Between 21 December and January 2022, GNSO Council with input from SG/Cs to prepare for GNSO Council – ICANN Board consultation (e.g. informal conversations, formal meetings, mailing list discussion, small team – to be discussed)
  *   January 2022 (date TBC) – GNSO Council & ICANN Board consultation

Although at this stage we do not have any further insight into what the SSAD Cost Model will tell us or how it may, or may not, change the positions on the SSAD recommendations, there are roughly three scenarios that can be anticipated:

  1.  ICANN Board determines that the adoption of the recommendations is in the best interest of the ICANN community and ICANN and adopts the SSAD recommendations – no further action expected from the GNSO Council at this stage;
  2.  ICANN Board determines that the adoption of the recommendation is not in the best interest of the ICANN community or ICANN and does not adopt all or part of the recommendations – the GNSO Council will be requested to affirm or modify its recommendations in the form of a “Supplemental Recommendation”.
  3.  The GNSO Council decides to avail itself of section 16 (“Amendments or Modifications of Approved Policies”) and agrees to modify or amend the recommendations before the ICANN Board considers the recommendations for approval.

To be clear, Council Leadership does not want to get ahead of the discussion and as such, we are not making any kind of prediction about which scenario is most likely, but we would like the Council and SG/Cs to start thinking about these scenarios and consider what is needed to be prepared for the next steps.

Our main objective here is to make sure that conversations within the GNSO as well as with the ICANN Board are constructive and effective – it is on all of us to work towards an approach and outcome that we are all willing and able to defend and live with.

Please come prepared to share your feedback during the Council meeting on 16 December. Of course, you are encouraged to already start the conversation on the mailing list.

Best regards,
Philippe

_________________________________________________________________________________________________________________________

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/council/attachments/20220105/a431957d/attachment-0001.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <https://mm.icann.org/pipermail/council/attachments/20220105/a431957d/ATT00001-0001.txt>