August 2022 - council - lists.icann.org

FW: GAC & GNSO letter to ALAC regarding participation in Closed Generics facilitated dialogue
by philippe.fouquart＠orange.com Aug. 8, 2022

Aug. 8, 2022

Dear Councilors, Please note the attached joint letter from the GNSO and the GAC to invite our ALAC colleagues to the discussion on closed generics. Best regards, Philippe -------- Message d'origine -------- De : Mary Wong <mary.wong(a)icann.org> Date : 08/08/2022 20:49 (GMT+01:00) À : Maureen Hilyard <maureen.hilyard(a)gmail.com> Cc : gnso-chairs(a)icann.org, GACLEADERSHIP <gac-leadership(a)icann.org>, Manal Ismail <manal(a)tra.gov.eg>, FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com>, ICANN At-Large Staff <staff(a)atlarge.icann.org>, gac-staff(a)icann.org, gnso-secs(a)icann.org, Justine Chew <justine.chew.icann(a)gmail.com>, Melissa Peters Allgood <melissa.allgood(a)icann.org>, Heidi Ullrich <Heidi.Ullrich(a)icann.org> Objet : GAC & GNSO letter to ALAC regarding participation in Closed Generics facilitated dialogue Dear Maureen, On behalf of Manal Ismail (GAC Chair) and Philippe Fouquart (GNSO Chair), please find attached a joint letter inviting the ALAC to appoint one member and one alternate to participate in the forthcoming facilitated dialogue on closed generic gTLDs. Best regards, Mary (on behalf of the ICANN org staff team supporting the facilitated dialogue) _________________________________________________________________________________________________________________________ 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.

1 0

Need for an EoI for the GNSO liaison to the GAC
by philippe.fouquart＠orange.com Aug. 8, 2022

Aug. 8, 2022

Dear councilors, Following up from this thread, I would like to wrap up on the next steps for a potential EoI for the role of GNSO liaison to the GAC. Most concerns were relative to having a limit and a more thorough annual review. A limit of 4 years will be included in the next EoI if last week’s proposal is accepted, as well as an early report from the liaison. With the limited support for an EoI by ICANN75, with that notion of 4 years with the role and the fact that Jeff has been with the role for 2 years, I’m tempted to conclude that the group doesn’t see the need for an EoI _now_, and Jeff is expected to stay for another year in the role. I put this proposal candidly to the group - as Paul notes, silence may mean anything and everything, and there’s been limited support to launching an immediate EoI. If I missed something, or if with hindsight anyone has a concern with this (and duly noting that Manju expressed a preference), and would like an EoI to be launched, please say so by August 19th. Thank you, Best Regards, Philippe Orange Restricted From: council <council-bounces(a)gnso.icann.org> On Behalf Of McGrady, Jr., Paul D. via council Sent: Monday, August 1, 2022 4:59 PM To: council@gnso icann. org <council(a)gnso.icann.org> Subject: Re: [council] Regarding GAC liaison position Thanks Jeff. Hi Fellow Councilors, Shortly after Manju’s email I put out a request on the NCPH Councilor’s list seeking input into whether or not others shared her concerns. I did not hear from anyone in the CSG expressing a concern. In fairness, I have no idea whether or not the CPH has any such concerns, but I note their silence on the Council list. Of course, silence may equal assent or it may equal dissent - who can say? Regarding Manju’s proposal, I think it would be counterproductive to swap Jeff out under the theory that the liaison for SubPro and GAC should not be the same person. A few thoughts: 1. I haven’t seen any indication that Jeff isn’t handling both roles with great competency (and Manju seems to agree with that, i.e. “amazing job”). 2. I don’t see any inherent conflict in having the same person in both roles - both roles represent Council. Council to Staff (SubPro) and Council to GAC. I’m not sure what neutrality has to do with anything - we don’t want Jeff neutral. We want Jeff passing along and explaining to Staff and GAC, as the case may be, what Council is thinking and bringing back to Council what the other group is thinking and helping us think through it all, not being neutral on the issues. If the concern is that Jeff is going rogue and pushing his own views on to Staff and GAC, well, I’ve not seen any evidence of that and it would be very inconsistent with the amazing job that Manjo notes he is doing. 3. As Jeff notes, this issue was discussed before Jeff was selected as the ODP Liaison. At the time there was no objection and the Standing Selection Committee knew this (and so did we on the Council) when Jeff was appointed as well. 4. The SubPro Liaison position is supposed to end in December, a blink of the eye in our ICANNland glacial timeframe. I doubt we could even get a replacement in place by then even if we wanted to, which I don’t think we do. There does seem to be at least some support for the idea of term limits for the GAC Liaison (as for term limits on Councilors, I think that is an issue best left to each constituency and we shouldn’t conflate that with the question before us related to liaison positions). We should consider that the term limits for liaisons issue without entangling it in trying to replace Jeff this fall. It is two different issues, and only one of them seems to have legs to me. Looking forward to the thoughts of others. Best, Paul Taft / Paul D. McGrady, Jr. Partner PMcGrady(a)taftlaw.com<mailto:PMcGrady@taftlaw.com> Dir: 312.836.4094 | Cell: 312.882.5020 Tel: 312.527.4000 | Fax: 312.754.2354 111 E. Wacker Drive, Suite 2800 Chicago, Illinois 60601-3713 Download vCard<http://www.taftlaw.com/vcard/PMcGrady@taftlaw.com> taftlaw.com<http://www.taftlaw.com> This message may contain information that is attorney-client privileged, attorney work product or otherwise confidential. If you are not an intended recipient, use and disclosure of this message are prohibited. If you received this transmission in error, please notify the sender by reply e-mail and delete the message and any attachments. From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Jeff Neuman via council Sent: Monday, August 1, 2022 8:33 AM To: desiree-me <desiree-me(a)protonmail.com<mailto:desiree-me@protonmail.com>>; 陳曼茹 Manju Chen <manju(a)nii.org.tw<mailto:manju@nii.org.tw>> Cc: council@gnso icann. org <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: Re: [council] Regarding GAC liaison position [EXTERNAL MESSAGE] Dear Desiree, Manju and Council, I believe term limits are a great discussion item and I wholeheartedly support having them. I was instrumental in getting the original term limits for DNSO/GNSO Councilors way back when so I completely understand the rationale for having them. To make things less complicated, I would propose similar term limits to GNSO Councilors (namely 4 years). Perhaps even consider two 2-year terms as opposed to having to renew every year. Most persons take a good 6-9 months to get comfortable in a position (about 2 ICANN meetings), so having 1-year terms never really made sense to me. By the time a person is comfortable in that role, it is time to get re-appointed. As I stated at the last GNSO Council meeting I do not believe my role as the ODP Liaison conflicts with my role as the GNSO Liaison to the GAC. In fact, I brought this up when I initially applied for the GNSO ODP Liaison position and both the CSC and the Council agreed that they saw no conflict. It was after the Council declared that there was no conflict that I took the ODP Position. Of course the Council can always take a different position this year with new Councilors based on actual events and performance. In any case, the ODP will be complete in December (about 2 months after the annual meeting). I am not sure there is a role for the ODP Liaison once the ODA is released. I would be happy to continue working on behalf of the Council on SubPro if there were such a position. And if there were I would gladly have someone else take the role of GAC liaison. But my understanding is that once an IRT is created, the GNSO Council can have a liaison to the IRT, but I think that may be limited to Councilors (which I am not one). I am happy to serve the Council as you all see fit. I like to see and help work actually get done. So please just let me know what you would like for me to do and I am happy to oblige. Sincerely, Jeff [cid:image001.png@01D8AB54.9016DE50] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of desiree-me via council Sent: Saturday, July 30, 2022 4:01 AM To: 陳曼茹 Manju Chen <manju(a)nii.org.tw<mailto:manju@nii.org.tw>> Cc: council@gnso icann. org <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: Re: [council] Regarding GAC liaison position Manju Thanks for the follow up and putting things in the perspective again. We didn't have much time to discuss this issue last time as it was in the AOB part of the call. As I said on the GNSO call, I support your views that from the governance point of view. It is important to review the term limits for the GNSO GAC liaison seat. I recall that the previous GAC GNSO liaison term was five years in total and it must have been extended because of the great job that the person did. The candidate can be doing a great job and her/his term can be extended, but it would be healthy to review and agree on those terms and any other possible considerations and circumstances we ought to take into consideration, I'd certainly like to discuss this more with fellow Council members and find a good working governance framework. Desiree -- On Tue, Jul 26, 2022 at 10:09, 陳曼茹 Manju Chen via council <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Hi all, I'd like to follow up with our discussions in last week's Council meeting regarding opening the call for GAC liaison position. As emphasized in my intervention, this proposal shall not be seen as unsatisfaction for the current GAC liaison. Jeff has done an amazing job and we are extremely grateful for his time and devotion. However, I believe we as Council should not have one individual carrying out 2 critical liaison roles-the GAC liaison and SupPro liaison, both require impeccable neutrality. Again, this is not about the capability/performance of the individual but the Council's responsibility of making the two jobs clearly separated. We have obligations to ensure transparency and accountability of such processes and appointments. I proposed we open the position of GAC liaison and call for volunteers. As the deadline for SubPro ODA has been pushed to December this year, it goes without saying that subsequent work and discussions will continue until next year. I think we can all agree that the Council will feel crippled without Jeff as our SubPro ODP liaison. I've also suggested during last week's meeting that it is time for the Council to review the job description of GAC liaison, specifically, considering adding term limits for the role. I believe this will be another step towards better accountability and transparency of the GNSO Council. Thank you for reading this lengthy email. I look forward to further discussions! Best, Manju _________________________________________________________________________________________________________________________ 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.

1 0

FW: Next steps on closed generics - Facilitator role -
by philippe.fouquart＠orange.com Aug. 8, 2022

Aug. 8, 2022

Dear Councilors, This is for your information, regarding the letter from the Board and the role of facilitator. Regards, Philippe -------- Message d'origine -------- De : FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com> Date : 02/08/2022 10:44 (GMT+01:00) À : Maarten Botterman <maarten.botterman(a)board.icann.org> Cc : gnso-chairs(a)icann.org, gnso-secs(a)icann.org Objet : Next steps on closed generics - Facilitator role - Dear Maarten, I trust this finds you well. Thank you for your letter of July 25th regarding next steps on closed generics. The GNSO Council has no objections to Ms. Allgood serving in the facilitator role. Mindful of the exchanges within the Council closed generics Small Team on this role, I would like to thank you and the Board for confirming in your letter the expectation of neutrality of all staff, including Ms. Allgood, in supporting the dialogue. We will come back to you shortly on the size of the team that will participate. The GNSO Council is looking forward to starting the work with Melissa and our GAC and ALAC colleagues. Kind 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.

1 0

FW: [Ext] Application Process opens for Pandemic Internet Access Reimbursement Program
by Julie Bisland Aug. 8, 2022

Aug. 8, 2022

FYI From: ICANN Community Digest <david.olive(a)icann.org> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Monday, August 8, 2022 at 10:02 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] Application Process opens for Pandemic Internet Access Reimbursement Program [https://r20.rs6.net/on.jsp?ca=e16a0dff-968b-4738-b2f6-f1018ff08c5a&a=112202…] Monday, 08 August 2022 ICANN Community Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. How Domain Name System Policy is Developed, and How You Can Get Involved [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001E6xtXvj9xKsF_7au…> Table of Contents ICANN75 · NEW: ICANN Continues the Pandemic Internet Access Reimbursement Program · NEW: ICANN75 Health and Safety · REMINDER: Registration for ICANN75 in Kuala Lumpur, Malaysia is Now Open · REMINDER: Implementation Operations Team Interactive Update on the "Enhancing ICANN’s Multistakeholder Model" Project Information Sharing · REMINDER: Register for the FY24 IANA Functions and PTI Planning Webinar · REMINDER: ICANN76 Fellowship Application Round Now Open · REMINDER: NextGen@ICANN Mentor Program Nominations · REMINDER: NextGen@ICANN Program Selection Committee Nominations Public Comment Proceedings · Initial Report on the Transfer Policy Review - Phase 1(a) ICANN75 NEW: ICANN Continues the Pandemic Internet Access Reimbursement Program ICANN announced the continuation of the Pandemic Internet Access Reimbursement Program for ICANN75. The hybrid I [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001E6xtXvj9xKsF_7au…>CANN75 Annual General Meeting [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001E6xtXvj9xKsF_7au…> is being held 17–22 September 2022. The deadline for reimbursement program applications is 2 September 2022. Interested ICANN community members must apply in advance of ICANN75, and those who meet the eligibility requirements will be selected to participate. The application process opens Monday, 08 August 2022. The application deadline is Friday, 02 September 2022 at 23:59 UTC. The goal of this program is to facilitate participation in ICANN Public Meetings during the pandemic. It offers community members who have limited Internet capacity financial assistance to increase their Internet bandwidth. Since ICANN75 will be conducted as a hybrid meeting, only applicants that attend virtually are eligible for this program. Apply here. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001E6xtXvj9xKsF_7au…> Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001E6xtXvj9xKsF_7au…> NEW: ICANN75 Health and Safety As we prepare to bring the community together in Kuala Lumpur, Malaysia for the ICANN75 Annual General Meeting, we remain vigilant and plan to maintain the high level of health and safety protocols that contributed to a successful event in The Hague. While there are few differences between the health and safety measures in place for ICANN75 when compared to those in force for ICANN74, some requirements for ICANN75 are legally mandated by the Malaysian government. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001E6xtXvj9xKsF_7au…> REMINDER: Registration for ICANN75 in Kuala Lumpur, Malaysia is Now Open ICANN announced that the dedicated website [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001E6xtXvj9xKsF_7au…> for the ICANN75 Annual General Meeting in Kuala Lumpur, Malaysia is live and registration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001E6xtXvj9xKsF_7au…> for the meeting is open. All participants must be pre-registered by 14 September 2022 to attend the meeting in person. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001E6xtXvj9xKsF_7au…> REMINDER: Implementation Operations Team Interactive Update on the "Enhancing ICANN’s Multistakeholder Model" Project In 2019, the ICANN Board initiated a project aimed at enhancing the effectiveness of ICANN's multistakeholder model – one of the strategic objectives outlined in ICANN's Strategic Plan for Fiscal Years (FY) 2021-2025. This effort is critical to ensuring that the multistakeholder model evolves and meets the changing needs of the ICANN community. The Implementation Operations team is offering an up to 30 minute interactive update on this project, more specifically on the evaluation methodology, which is used to assess the current projects/initiatives that are supporting the multistakeholder model. If you like this update to be part of your constituency/committee ICANN75 agenda, please email giovanni.seppia(a)icann.org<mailto:giovanni.seppia@icann.org> and/or negar.farzinnia(a)icann.org<mailto:negar.farzinnia@icann.org>. We look forward to working together to enhance the ICANN multistakeholder model. Information Sharing REMINDER: Register for the FY24 IANA Functions and PTI Planning Webinar The Internet Corporation for Assigned Names and Numbers (ICANN), along with its affiliate Public Technical Identifiers (PTI), invite the community to join a public webinar to discuss planning for the fiscal year 2024 (FY24) Operating Plan and Budget for delivering the Internet Assigned Numbers Authority (IANA) functions. This webinar will explain the planning process, the proposed IANA operational priorities for FY24, key assumptions, and timelines. Please join one of the two scheduled webinars to learn more: 11 August 2022 at 16:00 UTC: Register here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001E6xtXvj9xKsF_7au…>. 12 August at 00:00 UTC: Register here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001E6xtXvj9xKsF_7au…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001E6xtXvj9xKsF_7au…> REMINDER: ICANN76 Fellowship Application Round Now Open ICANN opened the application round for the ICANN Fellowship Program for the ICANN76 Community Forum which will take place in Cancún, Mexico from 11–16 March 2023. The application deadline is 19 August 2022, 23:59 UTC. If ICANN76 is held virtually, the Fellowship Program will also be held virtually. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001E6xtXvj9xKsF_7au…> REMINDER: NextGen@ICANN Mentor Program Nominations The NextGen@ICANN Program seeks nominations for the 2023 Mentor Program. This appointment will serve for the ICANN76-78 meetings. Nominations must be submitted no later than Tuesday 31 August 2022. The community-nominated mentor will be responsible for overseeing the mentor process. Communities may choose to appoint program alumni and are encouraged to appoint active community members who have an interest in mentoring students. Guidelines for the program can be found here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001E6xtXvj9xKsF_7au…>. I Interested community groups should select their respective volunteers and notify Deborah Escalera, deborah.escalera(a)icann.org<mailto:deborah.escalera@icann.org>. REMINDER: NextGen@ICANN Program Selection Committee Nominations The NextGen@ICANN Program is seeking nominations to fill 3-5 slots for selection committee members. Each SO/AC is asked to nominate candidates for these positions. Individual self-nominations will not be considered. Interested community groups should select their respective NextGen@ICANN volunteers by Friday, 16 September 2022. Interested community groups should select their respective volunteers and notify Deborah Escalera, deborah.escalera(a)icann.org<mailto:deborah.escalera@icann.org>. Each selection committee member will serve for a period of 2 years beginning with ICANN76. For program details please visit our page [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001E6xtXvj9xKsF_7au…>. Public Comment Initial Report on the Transfer Policy Review - Phase 1(a) [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001E6xtXvj9xKsF_7au…> Open for Submissions Date: Tuesday, 21 June 2022 Closed for Submissions Date: Tuesday, 16 August 2022 See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001E6xtXvj9xKsF_7au…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001E6xtXvj9xKsF_7au…>. Volume 4, Issue 58 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001E6xtXvj9xKsF_7au…> | Next Issue: Thursday, 11 August 2022 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001E6xtXvj9xKsF_7au…>

1 0

Next step on closed generics
by philippe.fouquart＠orange.com Aug. 5, 2022

Aug. 5, 2022

Dear Councilors, As we proceed with preparing for the Closed Generics facilitated dialogue and as noted in the Board's recent letter, the next step for the GNSO is to assemble a group of individuals who will participate in the dialogue. Noting that the Council small group suggested that no more than 6-8 individuals from the GNSO participate, and acknowledging that there are benefits to keeping the group as small as possible, Council leadership would like to propose that we aim for 6 seats, as follows: * 1 seat from Council leadership (ex-officio) * 1 seat from the SubPro PDP leadership team * 1 seat from each GNSO Stakeholder Group o A Stakeholder Group can give its seat to another Stakeholder Group if it chooses to do so o Council will provide Stakeholder Groups with the criteria from the Small Team to support selection of individuals o Stakeholder Group's will make a selection according to their own procedures With this proposal, the GAC would also have the opportunity to fill an equal number of seats (6), bringing total participation to 13 individuals (which is inclusive of the one member from the ALAC). (The GAC may obviously also choose to appoint less than 6 members) It is important to note that while the proposed approach is seemingly representative in nature, the Council has provided expectations that members should, "...contribute as independent individuals, bringing their individual experiences and expertise, and not serve as representatives of their respective community organization(s). The participants must commit to focusing on successfully developing a framework for closed generics, even if the end product is inconsistent with the goals or priorities of the participant or the participant's SO/AC/SG/C." There is also an expectation that the facilitated discussion will avoid discussion of the "edge outcomes" (i.e., of allowing closed generics without restrictions or limitations or prohibiting closed generics under any circumstance) and members should be prepared to engage accordingly. Understanding that there may not be a perfect solution that all groups support equally, we hope that this proposal can be acceptable to all. If you are unable to support the proposal, please raise your concerns on the mailing list no later than August 17th (2 weeks from now). Thank you. Kind 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.

3 3

FW: 2022 CSC slate for approval
by philippe.fouquart＠orange.com Aug. 4, 2022

Aug. 4, 2022

Dear Councilors, Please note Jennifer's note below in advance of a consent agenda item at our next Council call intended to endorse this 2022 CSC slate. Thank you. Philippe -------- Message d'origine -------- De : Jennifer Bryce <jennifer.bryce(a)icann.org> Date : 04/08/2022 10:37 (GMT+01:00) À : alejandra.reynoso(a)cctld.gt, FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com> Cc : John Crain <john.crain(a)icann.org>, Kim Davies <kim.davies(a)iana.org>, Bart Boswinkel <bart.boswinkel(a)icann.org>, David Olive <david.olive(a)icann.org>, Steve Chan <steve.chan(a)icann.org> Objet : 2022 CSC slate for approval Dear Alejandra and Philippe, Attached, please find a letter requesting that the GNSO and ccNSO Councils approve the 2022 CSC slate of members and liaisons. For additional reference I’ve also attached the key activities and dates of the election process. Please let me know if you have any questions. Thank you, Jennifer -- Jennifer Bryce Project Manager, Office of the Chief Technology Officer (OCTO) Internet Corporation for Assigned Names and Numbers (ICANN) Skype: jennifer.bryce.icann Email: jennifer.bryce(a)icann.org _________________________________________________________________________________________________________________________ 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.

1 0

FYI: FW: [Ext] DEADLINE EXTENDED: Initial Report on the Transfer Policy Review - Phase 1(a)
by Terri Agnew Aug. 4, 2022

Aug. 4, 2022

FYI [https://r20.rs6.net/on.jsp?ca=f8fb5b5d-7dbd-4e43-9bc7-bc9216771427&a=112202…] Thursday, 04 August 2022 ICANN Community Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. How Domain Name System Policy is Developed, and How You Can Get Involved [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012slatiz8awK9mw2B…> Table of Contents ICANN75 · REMINDER: Registration for ICANN75 in Kuala Lumpur, Malaysia is Now Open · REMINDER: Implementation Operations Team Interactive Update on the "Enhancing ICANN’s Multistakeholder Model" Project Information Sharing · REMINDER: Register for the FY24 IANA Functions and PTI Planning Webinar · REMINDER: ICANN76 Fellowship Application Round Now Open · REMINDER: NextGen@ICANN Mentor Program Nominations · NEW: NextGen@ICANN Program Selection Committee Nominations Public Comment Proceedings · DEADLINE EXTENDED: Initial Report on the Transfer Policy Review - Phase 1(a) ICANN75 REMINDER: Registration for ICANN75 in Kuala Lumpur, Malaysia is Now Open ICANN announced that the dedicated website [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012slatiz8awK9mw2B…> for the ICANN75 Annual General Meeting in Kuala Lumpur, Malaysia is live and registration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012slatiz8awK9mw2B…> for the meeting is open. All participants must be pre-registered by 14 September 2022 to attend the meeting in person. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012slatiz8awK9mw2B…> REMINDER: Implementation Operations Team Interactive Update on the "Enhancing ICANN’s Multistakeholder Model" Project In 2019, the ICANN Board initiated a project aimed at enhancing the effectiveness of ICANN's multistakeholder model – one of the strategic objectives outlined in ICANN's Strategic Plan for Fiscal Years (FY) 2021-2025. This effort is critical to ensuring that the multistakeholder model evolves and meets the changing needs of the ICANN community. The Implementation Operations team is offering an up to 30 minute interactive update on this project, more specifically on the evaluation methodology, which is used to assess the current projects/initiatives that are supporting the multistakeholder model. If you like this update to be part of your constituency/committee ICANN75 agenda, please email giovanni.seppia(a)icann.org<mailto:giovanni.seppia@icann.org> and/or negar.farzinnia(a)icann.org<mailto:negar.farzinnia@icann.org>. We look forward to working together to enhance the ICANN multistakeholder model. Information Sharing REMINDER: Register for the FY24 IANA Functions and PTI Planning Webinar The Internet Corporation for Assigned Names and Numbers (ICANN), along with its affiliate Public Technical Identifiers (PTI), invite the community to join a public webinar to discuss planning for the fiscal year 2024 (FY24) Operating Plan and Budget for delivering the Internet Assigned Numbers Authority (IANA) functions. This webinar will explain the planning process, the proposed IANA operational priorities for FY24, key assumptions, and timelines. Please join one of the two scheduled webinars to learn more: 11 August 2022 at 16:00 UTC: Register here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012slatiz8awK9mw2B…>. 12 August at 00:00 UTC: Register here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012slatiz8awK9mw2B…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012slatiz8awK9mw2B…> REMINDER: ICANN76 Fellowship Application Round Now Open ICANN opened the application round for the ICANN Fellowship Program for the ICANN76 Community Forum which will take place in Cancún, Mexico from 11–16 March 2023. The application deadline is 19 August 2022, 23:59 UTC. If ICANN76 is held virtually, the Fellowship Program will also be held virtually. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012slatiz8awK9mw2B…> REMINDER: NextGen@ICANN Mentor Program Nominations The NextGen@ICANN Program seeks nominations for the 2023 Mentor Program. This appointment will serve for the ICANN76-78 meetings. Nominations must be submitted no later than Tuesday 31 August 2022. The community-nominated mentor will be responsible for overseeing the mentor process. Communities may choose to appoint program alumni and are encouraged to appoint active community members who have an interest in mentoring students. Guidelines for the program can be found here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012slatiz8awK9mw2B…>. I Interested community groups should select their respective volunteers and notify Deborah Escalera, deborah.escalera(a)icann.org<mailto:deborah.escalera@icann.org>. NEW: NextGen@ICANN Program Selection Committee Nominations The NextGen@ICANN Program is seeking nominations to fill 3-5 slots for selection committee members. Each SO/AC is asked to nominate candidates for these positions. Individual self-nominations will not be considered. Interested community groups should select their respective NextGen@ICANN volunteers by Friday, 16 September 2022. Interested community groups should select their respective volunteers and notify Deborah Escalera, deborah.escalera(a)icann.org<mailto:deborah.escalera@icann.org>. Each selection committee member will serve for a period of 2 years beginning with ICANN76. For program details please visit our page [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012slatiz8awK9mw2B…>. Public Comment DEADLINE EXTENDED: Initial Report on the Transfer Policy Review - Phase 1(a) [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012slatiz8awK9mw2B…> Open for Submissions Date: Tuesday, 21 June 2022 Closed for Submissions Date: Tuesday, 16 August 2022 See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012slatiz8awK9mw2B…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012slatiz8awK9mw2B…>. Volume 4, Issue 57 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012slatiz8awK9mw2B…> | Next Issue: Monday, 08 August 2022 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012slatiz8awK9mw2B…>

1 0

REMINDER: Proposed Responses to SubPro Question Set 5 (DUE 03 August)
by Julie Hedlund Aug. 2, 2022

Aug. 2, 2022

Dear Councilors, This is a reminder to see the attached proposed responses to Question Set #5 for your review. Please also note the following action items from the GNSO Council meeting on 21 July: Action Items: GNSO Councilors to provide input on the list, if any, in one week (by Wednesday, 27 July) for SubPro Question Set #4 [DONE] and in two weeks (by Wednesday, 03 August) for Question Set #5. Per the action items, your input, if any, on the proposed responses to Question Set #5 is due tomorrow, Wednesday, 03 August. With kind regards, Julie Julie Hedlund, Policy Director From: council <council-bounces(a)gnso.icann.org> on behalf of "philippe.fouquart--- via council" <council(a)gnso.icann.org> Reply-To: "philippe.fouquart(a)orange.com" <philippe.fouquart(a)orange.com> Date: Wednesday, July 20, 2022 at 9:15 AM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] FW: Small Team Responses to SubPro Question Set 4 and New Question Set 5 Dear Councilors, Please see the small team’s proposed responses to Question Set 4 for your review. Many thanks to Jeff and the small team members. See also Question Set 5 as provided by the ODP team. Regards, Philippe Orange Restricted From: Jeff Neuman <jeff(a)jjnsolutions.com> Sent: Tuesday, July 19, 2022 3:30 PM To: FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com>; Sebastien(a)registry.godaddy; Tomslin Samme-Nlar (mesumbeslin(a)gmail.com) <mesumbeslin(a)gmail.com> Cc: Steve Chan <steve.chan(a)icann.org>; Emily Barabas <emily.barabas(a)icann.org>; Julie Hedlund <julie.hedlund(a)icann.org> Subject: Small Team Responses to SubPro Question Set 4 and New Question Set 5 Dear Council Leadership, Please find attached a copy of the small team proposed responses to SubPro Question Set No. 4 (the google link can be found here [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1EQDDfNprHYWW…>). The small team worked diligently to go through the numerous questions and I believe this is ready to be sent to the ICANN ODP Team if the Council agrees. In addition, please find enclosed a short Question Set 5 just sent to me by the ICANN ODP Team. This can be found at the following Google Link: https://docs.google.com/document/d/1CvMjmuC9CFEk2Nc09XVoL9kB7F_hXUJPq10mhx8… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1CvMjmuC9CFEk…>. Since this question set is short, I am hoping we can have it back to the ODP team in the next two weeks. I will be putting my answers in the Google Doc shortly. Can you please send this note to the Council and I can provide an update on the call this week. Sincerely, Jeff Neuman GNSO Liaison to SubPro ODP [cid:image001.png@01D8A655.D1FC6640] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com [jjnsolutions.com]<https://urldefense.com/v3/__http:/jjnsolutions.com__;!!PtGJab4!9Mrp3SxCVehb…> _________________________________________________________________________________________________________________________ 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.

1 0

FW: Final Question Set 4 and Update
by philippe.fouquart＠orange.com Aug. 2, 2022

Aug. 2, 2022

Dear Councilors, Please see Jeff's email below with the responses to Question Set 4 and other items, and in particular the question of a SubPro session at the next ICANN meeting, either in plenary or with the ODP team and individual constituencies. As Jeff notes the setup of the new council at the AGM and approaching completion of the ODP would also be a good opportunity to think about the timing and planning of the IRT(s). Please have a look at the suggested topics. Thank you. Philippe Orange Restricted From: Jeff Neuman <jeff(a)jjnsolutions.com> Sent: Friday, July 29, 2022 6:02 PM To: FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com>; Sebastien(a)registry.godaddy; Tomslin Samme-Nlar (mesumbeslin(a)gmail.com) <mesumbeslin(a)gmail.com> Cc: Steve Chan <steve.chan(a)icann.org>; Julie Hedlund <julie.hedlund(a)icann.org>; Emily Barabas <emily.barabas(a)icann.org> Subject: Final Question Set 4 and Update Dear Council Leadership, Please let the Council know that the responses to Question Set 4 have been submitted. A big thank you to the small team of Councilors that helped me with the responses including Paul, Justine, Desiree, Flip and of course ICANN support. First, just a reminder that the responses to Question Set 5 are due on Wednesday next week. Justine and Paul have weighed in on it, so thanks to them again! Second, I had a call this week with the ICANN SubPro Team (minus Karen who was on a well deserved vacation). In addition to discussing the Question Sets, I wanted to relay the following: 1. The ODP Team informed me that the SO/AC leaders did not seem to have any interest in a SubPro session at ICANN 75 in KL. I wanted to verify that this was the case since I had not heard anything from the SO/AC leaders on this. I also wanted to say that this could be an important missed opportunity for us to start some of the needed discussions including on the complete set of ODP Assumptions (See next item). There is a lot of work ahead of us, so I just wanted to verify that the community did or did not want a SubPro session. 1. At some point in August, ICANN will publish its final set of assumptions that will be included in the Operational Design Analysis (ODA). This sets the basis for setting the budget and dictating the resources that will be needed to implement and Launch the next round(s). As this would be timely, I do believe it may be worth discussing with the Community at ICANN 75 if that is something the community were interested in. 1. Whether or not there is a session at ICANN 75, the ODP Team has reminded me to let you all know that they are available to meet with any constituency, SG or AC at ICANN 75 to discuss the status of the project. 1. At this point Question Set 5 is the last set of questions that the ODP team has. This does not mean that there will not be other questions later, but they believe they have a handle on all of the Outputs of the GNSO Final Report, the Recommendations and Implementation Guidance. 1. However, there is still a lot of work ahead of us as the GNSO Community. We need to start planning for the Implementation Review Team and additional work. To do this, I would propose: * Having this is a discussion item at the GNSO Council SPS since there will be some new Councilors and it will likely have an impact on the work that the Council is going to be responsible for starting next Calendar Year. The F2F session in LA in December is a great time to discuss the impacts of this on the Council work load. * If the ODA is delivered in December, the Board could likely vote on it in February or March, which means that the ICANN staff could kick off an IRT shortly thereafter. The Council should determine whether this IRT will be like normal IRTs that are completely open or whether it will be a limited representative group. If the later, then I would propose starting off the discussion on the composition of this group in January so that when it is approved, we do not lose a month or two discussing this and getting the logistics set up. * Although we are likely kicking off the GGP on Applicant Support in August (hopefully), there are going to be other discreet topics that will need to be addressed and they may be a lot for a single IRT. This includes: i. Finalizing the structure and rules for the SPIRT ii. Implementing the Pre-Evaluation Program for Back-End Registry Service Providers iii. Finalizing and implementing the Outreach and Communication Strategy iv. Drafting the Applicant Guidebook v. Finalize the Process/Procedures for Private/Specialized Domain Names (SSAC 113) vi. Confirm Maximum Delegation Rate of TLDs (Affirmation/Recommendations in Section 26 of Final Report) vii. Challenge / Appeals Mechanisms for Evaluations / Objections (Section 32 of the Final Report) * There are a lot of external Dependencies that can also impact the next round, including: i. IDN ePDP Work ii. Implementation of the Revisions to the RPMs iii. Name Collision work by the NCAP / SSAC 1. All of this is a reminder to state that once the ODA is done and the Board votes on approving the policies, even assuming they approve it in March 2023, there is still a ton of things for the community to do before an application window can open. I personally believe planning should begin ASAP, but it is up to the Council and the Community to determine what happened and when. Please let me know if you have any questions. Sincerely, Jeff [cid:image001.png@01D8A341.251A1E20] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com _________________________________________________________________________________________________________________________ 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.

1 0

EXTENDED TO 16 AUGUST: Public comment period on Transfer Policy Review Phase 1(a) Initial Report
by Emily Barabas Aug. 1, 2022

Aug. 1, 2022

Dear Councilors, In response to requests received for additional time, the public comment period<https://www.icann.org/en/public-comment/proceeding/initial-report-on-the-tr…> on the Transfer Policy Review Phase 1(a) Initial Report has been extended by two weeks and will now close on 16 August. Please assist with spreading the word to your groups and others who might be interested. Kind regards, Emily Emily Barabas Policy Development Support Senior Manager Internet Corporation for Assigned Names and Numbers (ICANN) Phone: +31 (0)6 84507976 www.icann.org<http://www.icann.org/>

1 0