Jeff Thank you for the follow up and the explanation. Thanks for confirming, It is a relief that we'd discuss this at the GNSO council call, I was not suggesting we discuss it outside. Best Desiree -- Sent with [ProtonMail](https://protonmail.com/) Secure Email. ------- Original Message ------- On Sunday, March 6th, 2022 at 10:08 PM, Jeff Neuman <jeff@jjnsolutions.com> wrote:
Desiree,
We will discuss this issue at the GNSO Council meeting on the Council call. But to be more clear, the note I sent previously was on Question Set #2 whereby ICANN’s ODP Team pointed out that some of the items that were proposed to be given to a “IRT” actually amounted to something other than implementation (and closer to policy). Thus, the question on the table was whether we wanted to engage in some policy work now despite the fact that the ICANN Board has yet to approve the recommendations.
As seen in the letter from Maarten Botterman to Philippe just sent around today, it seems like the ICANN Board is keen for the community to resolve some of the policy issues (in that case “Closed Generics”) prior to the ICANN Board voting on approving the program. There are other topics such as Applicant Support, the formation of the SPIRT, the RSP Pre-Evaluation Program, Appeals, etc. that can be flushed out with some additional work now as opposed to waiting until next January when the ICANN Board actually has the ODA and can approve the recommendations.
Last point I made was that when the SubPro Working Group made the recommendations involving future work of IRTs, there was no such thing as an “ODP.” Thus, it was assumed that a few months after the GNSO Council delivered the final report to the Council and the Council approved it (March 2021), the Board would be given the report and approve the recommendations (assumed to be in June 2021). Therefore, we would have been well into the work of an IRT by now. However, the concept of an ODP was introduced (after SubPro was done), and that introduced unintended delay in working through some of these issues. That is why we are discussing these items now.
All of this is to say that the question of whether to do the work now or not is a lot more fuzzy than “is it implementation” and if so, “wait for an IRT”.
Should be an interesting discussion this week and I would advise all groups to get feedback from their constituencies / SGs before the Council meeting.
Thanks!
Jeffrey J. Neuman
Founder & CEO
JJN Solutions, LLC
p: +1.202.549.5079
E: jeff@jjnsolutions.com
From: council <council-bounces@gnso.icann.org> On Behalf Of desiree-me via council Sent: Sunday, March 6, 2022 1:36 PM To: philippe.fouquart@orange.com Cc: gnso-secs@icann.org; council@gnso icann. org <council@gnso.icann.org> Subject: Re: [council] FW: Upcoming session and updates
Dear Philippe
Thank you for the heads up about the time change in the agenda.
I recall that Jeff has sent a note a few weeks back regarding the SubPro ODP and the missing Applicant Support Program work, per CCTR, asking whether the GNSO should form a small group to handle that part of the work ahead of time.
Please correct me if I'm wrong, but my understanding is that the new gTLDs Applicant Support Program is part of the IRT process. Therefore, if you and others agree, we should respond that it would not be feasible for the GNSO to form such a group now and take on that work.
Desiree
--
------- Original Message ------- On Thursday, March 3rd, 2022 at 6:45 PM, philippe.fouquart--- via council <council@gnso.icann.org> wrote:
Dear Councillors,
Channelling this on Jeff's behalf, including the change of date for the subpro odp session if you hadnt noticed yet.
Best,
Philippe
-------- Message d'origine --------
De : Jeff Neuman <jeff@jjnsolutions.com>
Date : 03/03/2022 19:35 (GMT+01:00)
À : Karen Lentz <karen.lentz@icann.org>
Cc : SubPro ODP Mailman List <subpro-odp@icann.org>, FOUQUART Philippe INNOV/NET <philippe.fouquart@orange.com>, "Sebastien@registry.godaddy" <sebastien@registry.godaddy>, "Tomslin Samme-Nlar (mesumbeslin@gmail.com)" <mesumbeslin@gmail.com>, Steve Chan <steve.chan@icann.org>
Objet : RE: Upcoming session and updates
Thanks Karen!
GNSO Council Leadership – Can you please post to the Council list as soon as possible so that everyone has this same information to review.
Thanks again for all of this.
Sincerely,
Jeff Neuman
GNSO Council Liaison to SubPro ODP
Jeffrey J. Neuman
Founder & CEO
JJN Solutions, LLC
p: +1.202.549.5079
E: jeff@jjnsolutions.com
From: Karen Lentz <karen.lentz@icann.org> Sent: Thursday, March 3, 2022 1:30 PM To: Jeff Neuman <jeff@jjnsolutions.com> Cc: SubPro ODP Mailman List <subpro-odp@icann.org> Subject: Upcoming session and updates
Hello Jeff,
Prior to our March meeting, and ICANN73, I’m highlighting a few updates here:
- We published on Monday the first in a [blog post](https://www.icann.org/en/blogs/details/icann-subpro-odp-update-highlighting-...) series covering each of the project work tracks; this one looks at Work Track 1, project governance. - In preparation for our [Subsequent Procedures Operational Design Phase (SubPro ODP) ICANN73 meeting session](https://73.schedule.icann.org/meetings/GzLD4X2x8wqi5B4dp#/?limit=10&sortByFields[0]=isPinned&sortByFields[1]=lastActivityAt&sortByOrders[0]=-1&sortByOrders[1]=-1&uid=hkFxCerxzS6Z6wMJe), we’ve posted a draft set of [Initial Assumptions](https://www.icann.org/en/system/files/files/initial-assumptions-subsequent-p...) that will be the ones we cover during that session. These are posted to our [ODP webpage](https://www.icann.org/subpro-odp) and the [session page](https://73.schedule.icann.org/meetings/GzLD4X2x8wqi5B4dp) in advance of ICANN73 as an update to the community and to help inform next week’s discussion. - Please note the ICANN73 session date and time has changed to Monday, 7 March @ 16:30 UTC. It is also a longer time slot, so we have more time for the material and for Q&A.
Thank you and we look forward to the continuing engagement.
Best regards, Karen
_________________________________________________________________________________________________________________________
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.
