Thanks Pam. We have the same understanding and I agree, it makes more sense to keep it this broad – and since these are minutes, you’re right I don’t think it was restricted during the discussion. Best Regards, Philippe From: council [mailto:council-bounces@gnso.icann.org] On Behalf Of Pam Little Sent: Friday, February 01, 2019 3:49 AM To: Nathalie Peregrine; council@gnso.icann.org; council Cc: gnso-secs@icann.org Subject: Re: [council] Draft minutes of the GNSO Council meeting 24 January 2019 Dear Philippe and Councilors, Re: Item 6: COUNCIL DISCUSSION – Managing the EPDP Implementation Gap and Back-up Plans My understanding of a possible implementation gap is the time between the expiration of the Temporary Specification and when the recommendations in the Final Report are implemented (i.e., when the new policy recommendations become effective). I would also note implementation of some of the recommendations is likely to involve other parties, not only the contracted parties. It seems reasonable to assume that the ICANN Board will reaffirm the Temporary Specification once more (https://www.icann.org/news/announcement-2019-01-29-en). If so, the Temporary Specification will expire on 25 May 2019. Based on the above, I would suggest a couple more edits: Redline: "Given the considerable advance undertaken by the EPDP Team in Toronto, concerns have now shifted to a possible gap between the finalization of the Final Report and its recommendations, approval by the Council and Board before, the expiration of the Temporary Specification and the implementation of the recommendations by the contracted parties. What is the solution if contracted parties need more time to be able to implement the recommendations in the Final Report? This would not be of the GNSO Council’s remit but lies within the EPDP team and potentially contractual negotiations between the contracted parties and ICANN." Clean: "Given the considerable advance undertaken by the EPDP Team in Toronto, concerns have now shifted to a possible gap between the expiration of the Temporary Specification and the implementation of the recommendation. What is the solution if contracted parties need more time to be able to implement the recommendations in the Final Report? This would not be of the GNSO Council’s remit but lies within the EPDP team and potentially contractual negotiations between the contracted parties and ICANN." I hope these edits make sense. Let me know if anyone has any concerns or other suggested edits. Kind regards, Pam ------------------------------------------------------------------ Sender:philippe.fouquart <philippe.fouquart@orange.com> Sent At:2019 Jan. 30 (Wed.) 22:09 Recipient:Nathalie Peregrine <nathalie.peregrine@icann.org>; council@gnso.icann.org <council@gnso.icann.org> Cc:gnso-secs@icann.org <gnso-secs@icann.org> Subject:Re: [council] Draft minutes of the GNSO Council meeting 24 January 2019 Thanks for this Nathalie. Maybe this is just my misreading this but regarding the discussion on the EPDP I believe the concern was the potential gap between finalization+approval(s) of the final report on one hand and the implementation of the recommendations by contracted parties on the other (which may indeed require some time). To me the first sentence of current text reads as if it were (still) between approvals and expiration of the temp spec. […] concerns have now shifted to a possible implementation gap between the finalization of the Final Report and its recommendations, approval by the Council, approval by the Board and the expiration of the Temporary Specification. A couple of additional edits on the CSC effectiveness, as attached. Regards, Philippe From: council [mailto:council-bounces@gnso.icann.org] On Behalf Of Nathalie Peregrine Sent: Monday, January 28, 2019 9:47 PM To: council@gnso.icann.org Cc: gnso-secs@icann.org Subject: [council] Draft minutes of the GNSO Council meeting 24 January 2019 Dear Councilors, Attached, please find the draft minutes of the GNSO Council meeting Thursday 24 January 2019 for your review. If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_counc...> section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 7 February 2019. Thank you very much. Kind regards, Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine@icann.org <nathalie.peregrine@icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gns...> _________________________________________________________________________________________________________________________ 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.