Dear Councilors, Staff has started preparing a final revision of the letter with the comments received so far. Thanks Kurt, Greg, Manju. In the meantime, please see Jeff’s suggestion below, shared with his permission, to add “preestablished” before “published milestones” as well as the sentence “This letter should not be interpreted as the Council accepting any delays in either of these projects.” We discussed this within leadership and don’t think this is inconsistent with the exchange we have had so far (including Greg’s edits), and useful given the latest exchanges with the ODP team. As a rule, however, we don’t want to add text that has not been circulated. If you think otherwise, please say so by Friday 1700UTC. Thank you. Philippe Orange Restricted From: Jeff Neuman <jeff@jjnsolutions.com> Sent: Wednesday, June 29, 2022 11:20 PM To: FOUQUART Philippe INNOV/NET <philippe.fouquart@orange.com>; Tomslin Samme-Nlar (mesumbeslin@gmail.com) <mesumbeslin@gmail.com>; Sebastien@registry.godaddy Cc: kurt@kjpritz.com Subject: FW: [council] SSAD Light Impact Council - draft response Dear council leadership, I understand there is a desire to send this letter tonight or tomorrow. I just wanted to give you an update on the call I had with the SubPro ODP ICANN team. I am in the process of drafting up my other notes to send a full note to the Council (which I should send around tomorrow or Friday). With respect to the SubPro ODP, there have been no instructions yet to the ODP Team that the SSAD Light work has been approved for them to start working on. Therefore, the ODP Team is still working on their current deadlines. However, if and when there are instructions to proceed with the SSAD ODP Light design, they reminded me that it will be at least a 6 week delay. Although the ODP Team has not yet figured out what delays would actually be caused by the SSAD Light project, they committed to me that they would immediately develop a new timeline for the SubPro ODP letting us know the specific intended delays. The confirmed that if it were just 6 weeks that would be pushing against the December holiday time when ICANN closes down and this may cause the ODA to not be released until Mid-January which would of course result in a 10-week delay. It is also unknown how that would impact their other milestones. For example, I believe there is no ICANN Board Meeting in December so the earliest the ODP Team could brief the Board on the ODA would be January. But they are unsure when the Board Workshop will be (which is the natural place where they intended to update the Board). This could mean that the Board could not be updated until February unless the ICANN Board moved their intended workshop or figured out another time to discuss these. In any case, it puts a vote by the ICANN Board on the GNSO SubPro Policies in March at risk. And of course this will ultimately lead to a decision in September when the SSAD Light proposal is presented on whether to move ahead with the implementation of that and whether the implementation of that will also delay implementation of SubPro. The ICANN ODP team that is not also on the SSAD Light project will continue to work on the SubPro ODP during any delay. I have asked them to present creative ideas on how we can mitigate the impact of any of these delays on future activities. This includes releasing parts of the ODA earlier than others (if that is even possible) or any other ideas to mitigate the delays. I am not a councilor, but as an impacted GNSO member, I believe a sentence must be added to the letter that states :”This letter should not be interpreted as the Council accepting any delays in either of these projects.” I have therefore cc’d Kurt. If you want to send it to the Council, feel free. But when I read the letter in my opinion it very lightly says that they should try to meet published milestones, but we don’t have the expertise to say anything else. I disagree with that…but even if we accept that notion, this letter as drafted basically gives ICANN carte blanche to do whatever they want. Therefore, the added setence states what I believe we expect. Finally, I added the word “Pre-established” before the words published milestones. ICANN can always meet published milestones If they keep publishing new timelines 😉 Its your call on what you want to do, but I think the letter should be stronger on what we expect. Its not our job to organize their resources, yes. But, it is their job to perform. [cid:image001.png@01D88BDB.1CDC7BE0] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of philippe.fouquart--- via council Sent: Tuesday, June 28, 2022 8:28 AM To: kurt kjpritz.com <kurt@kjpritz.com<mailto:kurt@kjpritz.com>> Cc: gnso-secs@icann.org<mailto:gnso-secs@icann.org>; council@gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] SSAD Light Impact Council - draft response Hi Kurt. Thanks for sorting out the order of priorities in the letter, this is helpful. Some of the elements of the first iteration being more records of the discussion, we will see whether there’s benefit in bringing some of them back without losing in conciseness or being repetitive. Everyone, please share any other comment you may have by the end of the day, for us to send this later this week. Thanks. Regards, Philippe Orange Restricted From: kurt kjpritz.com <kurt@kjpritz.com<mailto:kurt@kjpritz.com>> Sent: Monday, June 27, 2022 10:52 PM To: FOUQUART Philippe INNOV/NET <philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com>> Cc: council@gnso.icann.org<mailto:council@gnso.icann.org>; gnso-secs@icann.org<mailto:gnso-secs@icann.org> Subject: Re: [council] SSAD Light Impact Council - draft response Hi Philippe: Thanks for the opportunity to comment on this draft. Please consider the attached and feel free to use some, all or none of it. I have added a brief bit of context at the start as this issue did not arise from the Board-Council interaction but rather came in separately from the staff. I maintained the two main messages: 1. to emphasize the importance of both (SSAD and SubPro) initiatives, and 2. that the Council does not view itself in a position, nor does it consider it the role of the Council, to dictate the allocation of ICANN org resources now that these policy recommendations are with the ICANN Board. There was some re-arranging / re-wording that would render a redline somewhat ineffective but I can produce one. I hope you find this constructive and helpful. Best regards, Kurt On Jun 22, 2022, at 3:22 AM, philippe.fouquart--- via council <council@gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Dear Councilors, For you review, please find attached a draft letter to the Board regarding the impact of the development of an SSAD Light Design Paper on other ongoing work, including the SubPro ODP. This is intended to capture the conclusions of last week’s discussion item. Please provide your comments within a week, by Wednesday 29th COB UTC. Hope all those who could attend the The Hague meeting travelled safe and well back home. 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. <SSAD Light Impact Council Response - upd 16 June 2022.docx>_______________________________________________ council mailing list council@gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ 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. _________________________________________________________________________________________________________________________ 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. _________________________________________________________________________________________________________________________ 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.
