Thank you, Marika. Regarding Recommendation #1, my recollection is that the GDS Guidelines for GDS Liaisons to PDPs is quite thorough. Could you please send these around again via link or pdf before tomorrow’s meeting? A concern here is that participation by the Liaison should be active and timely. In the past, we have had active participation but I believe there may have been reluctance to provide too much concrete input because the Working Group had not reached a final conclusion during its deliberations as to where the policy development was headed. This is a bit of a “chicken and egg” problem. I’m sure Karen Lentz could be helpful in providing comments as to how the GDS Liaison can deal with that dynamic. What we absolutely must avoid is late-breaking advice from GDS as to whether policies under discussion can be executed or not. The feasibility of any policy under discussion by the WG needs to be addressed at the policy development stage. Otherwise, this improvement could become a “roadblock”. Regarding Recommendation #2 as to Council sharing anticipated time frames with the Board. Can we be more specific as to what is required of Council in connection with adopting this improvement? The verb, “consider” is pretty vague. Do we mean that Council should “endeavor to share time frames with the Board as early as possible”? Recommendation #3 looks solid and attainable to me. Recommendation #4 – As I commented in the survey, it would be unfair for the Chair and WG members to be tasked with identifying all policies that might be affected by their work on a specific PDP. If staff identifies the policies that need to be reviewed by the WG in advance, that is a task that is well-defined and attainable. A “general” instruction to the PDP Working Group to “identify other policies that are affected” is unworkable. In addition to staff identification of possible implications, would it not be incumbent on the GDS Liaison to raise any new or late-breaking effects on existing policies as the work progresses in the WG and to bring that question to the attention of the WG Chairs? Could we say that (1) existing policies to be reviewed by the WG should be specifically identified and (2) WG should also review any existing policies that are identified by the GDS Liaison as needing to be analyzed in the course of the WG’s Deliberations? Recommendation #5 – For the WG to include in the Final Report “any direct or indirect” effect on existing policies. Again, this is overly broad in scope. If a particular policy has been identified in the Charter as requiring review OR if the GDS Liaison has identified an existing policy that is affected, then it makes sense to require the Working Group to address that in the Final Report. As we all know, policy development and implementation is an ongoing and iterative process. We should not be creating obligations on the Working Group that lend themselves to getting mired down in processes that ultimately should be handled at the IRT level. Recommendation #6 re Role of Board Liaison to the PDP looks good to me. Recommendation #7 – not sure how we can approve this without knowing the future of the Operational Design Phase. When you update the Consensus Policy Implementation Framework as recommended, how do you account for the possible duplication of effort if the PDP Outcomes have already been reviewed by ICANN Org in the Operational Design Phase? For example, you now have an Operational Design Assessment that will be coming from ICANN Org on the Sub Pro Recommendations. If you update the CPIF as recommended here, does that mean ICANN Org comes back again at the IRT phase and does additional assessments? How would the amendment to the CPIF interact with the ODP and ODA process created by the Board which is still being assessed? It seems to me that this Recommendation is subject to and has to be put on hold until Recommendation 9 is accomplished – #9 is Review of ODP process. Recommendation #8 – Review of the Policy Status Report details certainly makes sense. How do we fit this work into the list of priorities? Is this a Small Team assignment for Council? (Maybe I don’t understand the proposed execution of this improvement. If so, I apologize.) Recommendation #9 – Review of ODP - Support this one and believe that the proposed survey should be expanded to a wide audience in the community. Thank you, Anne Anne E. Aikman-Scalese Of Counsel AAikman@lewisroca.com<mailto:AAikman@lewisroca.com> D. 520.629.4428 [cid:image002.png@01D8E85B.D68E0810] From: council <council-bounces@gnso.icann.org> On Behalf Of Marika Konings via council Sent: Tuesday, October 25, 2022 3:10 AM To: Demetriou, Samantha <sdemetriou@verisign.com>; Ashley Heineman <aheineman@godaddy.com>; Johan Helsingius <julf@Julf.com>; Cole, Mason (Perkins Coie) <MCole@perkinscoie.com>; Lori Schulman <lschulman@inta.org>; wuknoben@gmail.com; Benjamin Akinmoyeje <benakin@gmail.com>; Raoul Plommer <plommer@gmail.com>; council@gnso.icann.org Cc: Andrea Glandon <andrea.glandon@icann.org>; Brenda Brewer <brenda.brewer@icann.org> Subject: [council] GNSO Council & SC/G Chairs call: PDP Improvements & Next Steps Standing Committee on SCBO [EXTERNAL] ________________________________ Sent on behalf of Sebastien Ducos **************** Dear All, Based on the survey results<https://community.icann.org/download/attachments/206144128/PDP%20Improvements%20-%20Survey%20Report%20-%2016%20September%202022.pdf?version=1&modificationDate=1663427586000&api=v2> and the subsequent discussion during the ICANN75 session, the Council leadership team is recommending moving forward with the following PDP Improvements as outlined in the table below. Please note that the proposed next steps represent an incremental step – once this step has been implemented, there will be another opportunity for the GNSO community to consider how to proceed. For the upcoming meeting, Council leadership suggests focusing on those next steps that Council or SG/C Chairs do not support so we can focus on those during the meeting and start moving forward with items that do not raise any concerns. As such, please flag in advance of the meeting which items you would like to discuss further. As a reminder, the meeting is scheduled for Wednesday 25 October at 19.00 UTC. The first half of the meeting will be dedicated to the PDP Improvements discussion, the second half will focus on the next steps ​​concerning the Standing Committee on ICANN Budget and Operations (SCBO). On behalf of Council leadership, Sebastien Improvement Next Step Who is responsible for next step #1 - Enable a process during the PDP to share relevant information and analysis on potential impacts to existing policies, to support consideration by PDP working groups (define this process as part of the GDS liaison role) Council to review Guidelines for GDS Liaisons to PDPs and determine whether anything further is needed to consider this improvement complete GNSO Council #2 - The Council should consider sharing with the ICANN Board when certain items are expected to move from Council to Board to facilitate advance planning by the ICANN Board Derive from the project list and ADR items expected to be delivered to the ICANN Board in the coming year. In combination with sharing its SPS report, the Council communicates to the Board which items are expected to be forwarded to the ICANN Board for its consideration during that year to allow the ICANN Board to anticipate as part of its planning when it may need to consider GNSO policy recommendations. GNSO Staff Support Team GNSO Council #3 - Following adoption of a PDP Final Report by the GNSO Council, schedule a meeting with the ICANN Board to allow the GNSO Council, with the assistance of the PDP Chair(s), to present the Final Report and recommendations to the ICANN Board and allow for Q & A. An invitation has been sent to the ICANN Board to provide a briefing on the IGO Curative Rights EPDP recommendations. Proposed presentation / slides are to be shared in advance of the meeting with the Board to ensure that it is a neutral representation of the results and does not interfere with independent review. Following meeting, debrief with Council & GNSO appointed Board members to determine if this was helpful and/or whether it should be continued Council & GNSO Appointed Board members #4 - Add to the charter template a general or specific provision / question regarding consideration of impact on existing consensus policies Staff support team to create for Council review proposed addition for charter template that would highlight the expectation that a PDP WG is to consider the impact of its recommendation on existing consensus policies. Review proposed addition (note, the template can always be modified as needed to ensure that it is fit for purpose, including calling out specific existing policies that should be factored in) GNSO Staff Support Team GNSO Council #5 - Include in the Final Report template a section to address any direct or indirect implications for existing policies, to support full consideration by the PDP working groups and the GNSO Council. This may include implementation guidance where appropriate. Staff support team to include in the Final Report template a section to address any direct or indirect implications for existing Policies. Inclusion of this section by a PDP Team will be linked to any charter requirement in this regard. Review proposed addition to Final Report template Staff Support Team GNSO Council #6 - Consider if/how the role of the Board liaison of a PDP can contribute to more effective communication. This could, for example, be done by communicating clearly at the outset of a PDP the expected role of the Board liaison. Include link to Board Liaison guidelines in charter template so that if Board liaison is included as part of the charter, the role and expectations can be considered in the context of the review of the charter Review proposed update to charter template GNSO Staff Support Team GNSO Council #7 - Update CPIF to note that as part of implementing a new policy, ICANN org and the IRT review updates to other policies and incorporate as part of the implementation plan Requests GDS to provide an indication of possible timing & consultation of such updates to the CPIF (note, last round of updates were made in 2018 and involved consultation with the GNSO Council / community – the communication should confirm that the expectation is that the same approach would be used). Council Leadership #8 - Review of Policy & Implementation Recommendations Provide further detail on what a policy status review (PSR) would be expected to cover and confirm that a PSR does not mean that a review is initiated but it allows Council to consider whether or not a review is appropriate, and what should be considered as part of a review, if initiated. Review PSR details and decide if/how to proceed. GNSO Staff Support GNSO Council #9 – Review of the Operational Design Phase Develop straightforward survey that can be used to solicit input from the GNSO Council liaison to the SSAD ODP as well as the small team that was tasked to review the ODP to document its findings so that these can be shared when the review takes place after the second ODP completes. Review proposed survey. Notify the Council Liaison to the SubPro ODP that there will be the expectation to provide input on the experience with the ODP so that he can prepare and document his findings accordingly. GNSO Staff Support Team GNSO Council Council Leadership ________________________________ This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.

Thanks for circulating this, and thanks to colleagues for the comments so far. I wanted to add a couple: Improvement #3 I agree with Anne that this looks solid and attainable, and I’m not opposing the proposal of effectively trialling this with the IGO Curative Rights, but I am a little concerned that this may just be another step that builds-in delay. If I understand correctly, the final report on IGO Curative Rights was adopted by Council in June, sent to the Board in July, followed by an invitation meet, but that as at late October this meeting has not actually taken place or been scheduled, is that correct? Adding in steps which then generate scheduling delays does not seem like an improvement to the process. Improvement #9 Without wishing to overly complicate things, I do think the wider community should be offered some opportunity to provide feedback on the two ODPs to date. I don’t think this necessarily needs to be a community survey, it could be as simple as a call for input to run alongside the more formal feedback being sought from the liaisons and Council small teams. I am participating in the Prioritization Framework exercise at present, and the existence of an ODP has a clear impact on that process in terms of what is considered to be eligible to be prioritised (recommendations must have been board-approved). Community feedback from other work efforts which are affected by the ODP process needs to be captured. Thanks Susan Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 Ext 255 [cid:image001.png@01D8E95B.297EC820]<https://comlaude.com/> From: council <council-bounces@gnso.icann.org> On Behalf Of Marika Konings via council Sent: 25 October 2022 11:10 To: Demetriou, Samantha <sdemetriou@verisign.com>; Ashley Heineman <aheineman@godaddy.com>; Johan Helsingius <julf@Julf.com>; M Cole <MCole@perkinscoie.com>; Lori Schulman <lschulman@inta.org>; wuknoben@gmail.com; Benjamin Akinmoyeje <benakin@gmail.com>; Raoul Plommer <plommer@gmail.com>; council@gnso.icann.org Cc: Andrea Glandon <andrea.glandon@icann.org>; Brenda Brewer <brenda.brewer@icann.org> Subject: [council] GNSO Council & SC/G Chairs call: PDP Improvements & Next Steps Standing Committee on SCBO Sent on behalf of Sebastien Ducos **************** Dear All, Based on the survey results<https://community.icann.org/download/attachments/206144128/PDP%20Improvements%20-%20Survey%20Report%20-%2016%20September%202022.pdf?version=1&modificationDate=1663427586000&api=v2> and the subsequent discussion during the ICANN75 session, the Council leadership team is recommending moving forward with the following PDP Improvements as outlined in the table below. Please note that the proposed next steps represent an incremental step – once this step has been implemented, there will be another opportunity for the GNSO community to consider how to proceed. For the upcoming meeting, Council leadership suggests focusing on those next steps that Council or SG/C Chairs do not support so we can focus on those during the meeting and start moving forward with items that do not raise any concerns. As such, please flag in advance of the meeting which items you would like to discuss further. As a reminder, the meeting is scheduled for Wednesday 25 October at 19.00 UTC. The first half of the meeting will be dedicated to the PDP Improvements discussion, the second half will focus on the next steps ​​concerning the Standing Committee on ICANN Budget and Operations (SCBO). On behalf of Council leadership, Sebastien Improvement Next Step Who is responsible for next step #1 - Enable a process during the PDP to share relevant information and analysis on potential impacts to existing policies, to support consideration by PDP working groups (define this process as part of the GDS liaison role) Council to review Guidelines for GDS Liaisons to PDPs and determine whether anything further is needed to consider this improvement complete GNSO Council #2 - The Council should consider sharing with the ICANN Board when certain items are expected to move from Council to Board to facilitate advance planning by the ICANN Board Derive from the project list and ADR items expected to be delivered to the ICANN Board in the coming year. In combination with sharing its SPS report, the Council communicates to the Board which items are expected to be forwarded to the ICANN Board for its consideration during that year to allow the ICANN Board to anticipate as part of its planning when it may need to consider GNSO policy recommendations. GNSO Staff Support Team GNSO Council #3 - Following adoption of a PDP Final Report by the GNSO Council, schedule a meeting with the ICANN Board to allow the GNSO Council, with the assistance of the PDP Chair(s), to present the Final Report and recommendations to the ICANN Board and allow for Q & A. An invitation has been sent to the ICANN Board to provide a briefing on the IGO Curative Rights EPDP recommendations. Proposed presentation / slides are to be shared in advance of the meeting with the Board to ensure that it is a neutral representation of the results and does not interfere with independent review. Following meeting, debrief with Council & GNSO appointed Board members to determine if this was helpful and/or whether it should be continued Council & GNSO Appointed Board members #4 - Add to the charter template a general or specific provision / question regarding consideration of impact on existing consensus policies Staff support team to create for Council review proposed addition for charter template that would highlight the expectation that a PDP WG is to consider the impact of its recommendation on existing consensus policies. Review proposed addition (note, the template can always be modified as needed to ensure that it is fit for purpose, including calling out specific existing policies that should be factored in) GNSO Staff Support Team GNSO Council #5 - Include in the Final Report template a section to address any direct or indirect implications for existing policies, to support full consideration by the PDP working groups and the GNSO Council. This may include implementation guidance where appropriate. Staff support team to include in the Final Report template a section to address any direct or indirect implications for existing Policies. Inclusion of this section by a PDP Team will be linked to any charter requirement in this regard. Review proposed addition to Final Report template Staff Support Team GNSO Council #6 - Consider if/how the role of the Board liaison of a PDP can contribute to more effective communication. This could, for example, be done by communicating clearly at the outset of a PDP the expected role of the Board liaison. Include link to Board Liaison guidelines in charter template so that if Board liaison is included as part of the charter, the role and expectations can be considered in the context of the review of the charter Review proposed update to charter template GNSO Staff Support Team GNSO Council #7 - Update CPIF to note that as part of implementing a new policy, ICANN org and the IRT review updates to other policies and incorporate as part of the implementation plan Requests GDS to provide an indication of possible timing & consultation of such updates to the CPIF (note, last round of updates were made in 2018 and involved consultation with the GNSO Council / community – the communication should confirm that the expectation is that the same approach would be used). Council Leadership #8 - Review of Policy & Implementation Recommendations Provide further detail on what a policy status review (PSR) would be expected to cover and confirm that a PSR does not mean that a review is initiated but it allows Council to consider whether or not a review is appropriate, and what should be considered as part of a review, if initiated. Review PSR details and decide if/how to proceed. GNSO Staff Support GNSO Council #9 – Review of the Operational Design Phase Develop straightforward survey that can be used to solicit input from the GNSO Council liaison to the SSAD ODP as well as the small team that was tasked to review the ODP to document its findings so that these can be shared when the review takes place after the second ODP completes. Review proposed survey. Notify the Council Liaison to the SubPro ODP that there will be the expectation to provide input on the experience with the ODP so that he can prepare and document his findings accordingly. GNSO Staff Support Team GNSO Council Council Leadership ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com>