From mesumbeslin at gmail.com Sat Jul 2 00:59:56 2022 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Sat, 2 Jul 2022 07:59:56 +1000 Subject: [NCSG-PC] Fwd: Human Rights Analysis of SSAD & ODA Reports In-Reply-To: References: <22924cc4-d32d-2df5-9b1d-983cb1235b66@ekenyanito.com> Message-ID: Dear PC, Bringing this to the top of your inboxes for discussion. Ephraim has requested that we transmit the below HRIA on behalf of CCWP-HR. As PC, we need to decide if it meets/aligns with our policy objectives or any edits/adds we'll like to add to the document before the executive committee can proceed with it. Do let us know if you have any objections or concerns with the report as provided by Next week Friday 8th July please. Warmly, Tomslin ---------- Forwarded message --------- From: Ephraim Percy Kenyanito Date: Wed, 22 Jun 2022 at 01:33 Subject: Re: Human Rights Analysis of SSAD & ODA Reports To: Dear NCSG and SG & PC, I would like to request that NCSG transmits the research to the board on behalf of CCWP-HR. This report has adopted the use of the human rights impact assessments (HRIA) methodology as proposed in the FOI-HR. This methodology has been used in the October 2019 Trial HRIA for ICANN PDPs ? Final Report. We note that, the FOI-HR requires that various Supporting Organizations and Advisory Committees that comprise the ICANN community should be responsible for developing their own policies and frameworks to fulfill the Human Rights Core Value. However, the FOI-HR suggests HRIAs as a potential means of incorporating human rights considerations into policy development processes. HRIAs are rooted in the international human rights framework and used increasingly by companies, governments, and civil society alike as a tool to document a broader range of actual and potential impacts as part of a larger system of due diligence. Therefore, this report uses the Comprehensive HRIA format, which was developed by the CCWP-HR in 2019, as it provides the opportunity for stakeholders with divergent positions and opinions to engage constructively through the collection and comparison of empirical evidence, anecdotes, and general observations. This report provides the completed HRIA as an annex at the end of the report. Second, extensive desk research was also undertaken in compiling the final report to not just identify applicable legal instruments but also review relevant cases with a view to understanding what is legal, feasible, permissible and acceptable within the confines of ICANN?s Articles of Incorporation, the Core Values and the Bylaws. Best Regards, Ephraim Percy Kenyanito On 17/06/2022 16:29, farzaneh badii wrote: Fantastic! Look forward to reading it. On Fri, Jun 17, 2022 at 3:21 PM Ephraim Percy Kenyanito < hello at ekenyanito.com> wrote: > Dear NCSG, > > Please find the below communication and a prose document here: > https://docs.google.com/document/d/1XwC5YBDViRDME4Et7wzMchCkHe6z82V83Gpcb2dJ9k4/edit?usp=sharing > > Please feel free to add any comments. > > > -- > > Best Regards, > Ephraim Percy Kenyanito > Public Policy Specialist/ Regulatory Affairs Specialist/ Project Manager- > International Trade, Technology, Media & Telecommunications Laws > Website: https://ekenyanito.com/ > Twitter: @ekenyanito > PGP Fingerprint: B0FA394AF73DEB7AA1FDC7360CFED26DE6BA8DC1 > > > -------- Forwarded Message -------- > Subject: Re: Human Rights Analysis of SSAD & ODA Reports > Date: Wed, 15 Jun 2022 19:50:31 +0300 > From: Ephraim Percy Kenyanito > > To: cc-humanrights at icann.org, Francis Monyango > > CC: Tomslin Samme-Nlar , > Bruna Martins dos Santos > > Dear CCWP-HR, > > Please find the prose document here: > https://docs.google.com/document/d/1XwC5YBDViRDME4Et7wzMchCkHe6z82V83Gpcb2dJ9k4/edit?usp=sharing > > Please feel free to add any comments. > > > -- > > Best Regards, > Ephraim Percy Kenyanito > Public Policy Specialist/ Regulatory Affairs Specialist/ Project Manager- > International Trade, Technology, Media & Telecommunications Laws > Website: https://ekenyanito.com/ > Twitter: @ekenyanito > PGP Fingerprint: B0FA394AF73DEB7AA1FDC7360CFED26DE6BA8DC1 > On 29/05/2022 15:23, Ephraim Percy Kenyanito wrote: > > Dear team, > > Hope you are all well. > > This is in reference to previous conversations on the topic. > > Franc (copied here in this email) has been helpful in looking through the > documents. > Please find attached the analysis here: > https://docs.google.com/spreadsheets/d/1R0j8RwbUrxbPxVIe_5Hgc4CRNUaXkSoyZ-xXNF1N5h8/edit?usp=sharing > > The document contains two sheets; > > First, EPDP HRIA- analyses the EPDP Phase 2 Recommendations which inform > the ODA Report. > > Second, ODA HRIA- analyses the ODA Recommendations which aims to implement > the EPDP Report. > > > FYI- The ODA Report is informed by the EPDP Report though in some > instances ICANN might have misunderstood the EPDP Report and ICANN Board > wrote to the GNSO Council raising this questions: > > 1. > > Whether the ODA has correctly interpreted the intent of the SSAD > recommendations in the proposed implementation; > 2. > > Whether the ODA has overlooked any key aspects of the SSAD > recommendations that should be factored in by the ICANN Board when it > considers the recommendations; > 3. > > Its view on the concerns identified by the ICANN Board and potential > options that could be considered, either in the form of changes to the > proposed implementation or the policy recommendations themselves, to > address these concerns (note, these are expected to be high level > suggestions at this stage); > 4. > > Any other aspects that help inform the Council?s deliberations and > consultation with the ICANN Board. > > > For background here are the original documents that were being analysed: > > 1. > > EPDP Phase 2 Final Report: > https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phase-2-temp-spec-gtld-registration-data-2-31jul20-en.pdf > 2. > > ODA Final Report: > https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf > > I look forward to your feedback as I begin working on the prose report > which I hope to complete the first version by June 7th and will be > scheduled to be maximum 10 pages for transmission to the board via NCSG > (which CCWP-HR is seated). > > Please feel free to let me know in case of any questions. > > > --- > > Best Regards, > > *EPK* > > > -- Farzaneh -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Thu Jul 7 15:10:35 2022 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Thu, 7 Jul 2022 22:10:35 +1000 Subject: [NCSG-PC] Fwd: [council] For review - PDP Improvements Tracker In-Reply-To: <327312DD-3302-472A-B226-66018A5801D5@icann.org> References: <327312DD-3302-472A-B226-66018A5801D5@icann.org> Message-ID: Hi all, See below FYI. Do let the PC know please if you have any concerns, suggestions or questions on this proposed tracker. Warmly, Tomslin @LinkedIn: https://www.linkedin.com/in/tomslin/ ---------- Forwarded message --------- From: Marika Konings via council Date: Wed, 8 Jun 2022 at 06:40 Subject: [council] For review - PDP Improvements Tracker To: council at gnso.icann.org Dear All, In preparation for agenda item #9 on the Council agenda (GNSO PDP Improvements - Tracking and Coordination Discussion Paper), please find attached a first draft of the proposed tracker. Before going into a substantive review of the items included in the tracker, there are a number of practical questions that we hope to get feedback on during the upcoming Council meeting, namely: 1. Does the tracker provide the expected information for Council to consider and keep track of the different proposed improvements? If not, what is missing? 2. At the suggestion of Council members an entry for ?impact? has been added. Council to identify who/how to determine impactfullness of each proposed improvement ? is this referring to impact on the PDP, impact on resources, a combination of both or something else? 3. As not all improvements are solely within the remit of Council, what is the best way to consult with the broader GNSO community, and possibly beyond that, about this approach and how to enable regular consultation / input? 4. How often should review / updates be planned for? 5. Where should this information be housed ? GNSO wiki? 6. How much time is needed for the Council to consider these above questions that need to be addressed before the first substantive review can commence? Following your feedback, we?ll make any updates to the tracker, as agreed, before planning for a substantive review of the proposed improvements and suggested next steps. We look forward to receiving your feedback. Best regards, Marika _______________________________________________ council mailing list council at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PDP Improvements Tracker Overview - 7 June 2022.pdf Type: application/pdf Size: 238590 bytes Desc: not available URL: From mesumbeslin at gmail.com Sun Jul 10 15:39:52 2022 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Sun, 10 Jul 2022 22:39:52 +1000 Subject: [NCSG-PC] Human Rights Analysis of SSAD & ODA Reports In-Reply-To: References: <22924cc4-d32d-2df5-9b1d-983cb1235b66@ekenyanito.com> Message-ID: Hi Bruna, With no further concerns received from the PC, I believe Ephraim has accommodated suggestions and edits provided so far by NCSG and the PC is happy for the EC to send the report to the board. Warmly, Tomslin On Sat, 2 Jul 2022 at 07:59, Tomslin Samme-Nlar wrote: > Dear PC, > > Bringing this to the top of your inboxes for discussion. Ephraim has > requested that we transmit the below HRIA on behalf of CCWP-HR. As PC, we > need to decide if it meets/aligns with our policy objectives or any > edits/adds we'll like to add to the document before the executive committee > can proceed with it. Do let us know if you have any objections or concerns > with the report as provided by Next week Friday 8th July please. > > Warmly, > Tomslin > > > ---------- Forwarded message --------- > From: Ephraim Percy Kenyanito > Date: Wed, 22 Jun 2022 at 01:33 > Subject: Re: Human Rights Analysis of SSAD & ODA Reports > To: > > > Dear NCSG and SG & PC, > > I would like to request that NCSG transmits the research to the board on > behalf of CCWP-HR. > This report has adopted the use of the human rights impact assessments > (HRIA) methodology as proposed in the FOI-HR. This methodology has been > used in the October 2019 Trial HRIA for ICANN PDPs ? Final Report. > > We note that, the FOI-HR requires that various Supporting Organizations > and Advisory Committees that comprise the ICANN community should be > responsible for developing their own policies and frameworks to fulfill the > Human Rights Core Value. However, the FOI-HR suggests HRIAs as a potential > means of incorporating human rights considerations into policy development > processes. HRIAs are rooted in the international human rights framework and > used increasingly by companies, governments, and civil society alike as a > tool to document a broader range of actual and potential impacts as part of > a larger system of due diligence. > > Therefore, this report uses the Comprehensive HRIA format, which was > developed by the CCWP-HR in 2019, as it provides the opportunity for > stakeholders with divergent positions and opinions to engage constructively > through the collection and comparison of empirical evidence, anecdotes, and > general observations. This report provides the completed HRIA as an annex > at the end of the report. > Second, extensive desk research was also undertaken in compiling the final > report to not just identify applicable legal instruments but also review > relevant cases with a view to understanding what is legal, feasible, > permissible and acceptable within the confines of ICANN?s Articles of > Incorporation, the Core Values and the Bylaws. > > Best Regards, > > Ephraim Percy Kenyanito > On 17/06/2022 16:29, farzaneh badii wrote: > > Fantastic! Look forward to reading it. > > On Fri, Jun 17, 2022 at 3:21 PM Ephraim Percy Kenyanito < > hello at ekenyanito.com> wrote: > >> Dear NCSG, >> >> Please find the below communication and a prose document here: >> https://docs.google.com/document/d/1XwC5YBDViRDME4Et7wzMchCkHe6z82V83Gpcb2dJ9k4/edit?usp=sharing >> >> Please feel free to add any comments. >> >> >> -- >> >> Best Regards, >> Ephraim Percy Kenyanito >> Public Policy Specialist/ Regulatory Affairs Specialist/ Project Manager- >> International Trade, Technology, Media & Telecommunications Laws >> Website: https://ekenyanito.com/ >> Twitter: @ekenyanito >> PGP Fingerprint: B0FA394AF73DEB7AA1FDC7360CFED26DE6BA8DC1 >> >> >> -------- Forwarded Message -------- >> Subject: Re: Human Rights Analysis of SSAD & ODA Reports >> Date: Wed, 15 Jun 2022 19:50:31 +0300 >> From: Ephraim Percy Kenyanito >> >> To: cc-humanrights at icann.org, Francis Monyango >> >> CC: Tomslin Samme-Nlar , >> Bruna Martins dos Santos >> >> Dear CCWP-HR, >> >> Please find the prose document here: >> https://docs.google.com/document/d/1XwC5YBDViRDME4Et7wzMchCkHe6z82V83Gpcb2dJ9k4/edit?usp=sharing >> >> Please feel free to add any comments. >> >> >> -- >> >> Best Regards, >> Ephraim Percy Kenyanito >> Public Policy Specialist/ Regulatory Affairs Specialist/ Project Manager- >> International Trade, Technology, Media & Telecommunications Laws >> Website: https://ekenyanito.com/ >> Twitter: @ekenyanito >> PGP Fingerprint: B0FA394AF73DEB7AA1FDC7360CFED26DE6BA8DC1 >> On 29/05/2022 15:23, Ephraim Percy Kenyanito wrote: >> >> Dear team, >> >> Hope you are all well. >> >> This is in reference to previous conversations on the topic. >> >> Franc (copied here in this email) has been helpful in looking through the >> documents. >> Please find attached the analysis here: >> https://docs.google.com/spreadsheets/d/1R0j8RwbUrxbPxVIe_5Hgc4CRNUaXkSoyZ-xXNF1N5h8/edit?usp=sharing >> >> The document contains two sheets; >> >> First, EPDP HRIA- analyses the EPDP Phase 2 Recommendations which inform >> the ODA Report. >> >> Second, ODA HRIA- analyses the ODA Recommendations which aims to >> implement the EPDP Report. >> >> >> FYI- The ODA Report is informed by the EPDP Report though in some >> instances ICANN might have misunderstood the EPDP Report and ICANN Board >> wrote to the GNSO Council raising this questions: >> >> 1. >> >> Whether the ODA has correctly interpreted the intent of the SSAD >> recommendations in the proposed implementation; >> 2. >> >> Whether the ODA has overlooked any key aspects of the SSAD >> recommendations that should be factored in by the ICANN Board when it >> considers the recommendations; >> 3. >> >> Its view on the concerns identified by the ICANN Board and potential >> options that could be considered, either in the form of changes to the >> proposed implementation or the policy recommendations themselves, to >> address these concerns (note, these are expected to be high level >> suggestions at this stage); >> 4. >> >> Any other aspects that help inform the Council?s deliberations and >> consultation with the ICANN Board. >> >> >> For background here are the original documents that were being analysed: >> >> 1. >> >> EPDP Phase 2 Final Report: >> https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phase-2-temp-spec-gtld-registration-data-2-31jul20-en.pdf >> 2. >> >> ODA Final Report: >> https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf >> >> I look forward to your feedback as I begin working on the prose report >> which I hope to complete the first version by June 7th and will be >> scheduled to be maximum 10 pages for transmission to the board via NCSG >> (which CCWP-HR is seated). >> >> Please feel free to let me know in case of any questions. >> >> >> --- >> >> Best Regards, >> >> *EPK* >> >> >> -- > Farzaneh > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruna.mrtns at gmail.com Mon Jul 11 00:25:30 2022 From: bruna.mrtns at gmail.com (Bruna Martins dos Santos) Date: Sun, 10 Jul 2022 23:25:30 +0200 Subject: [NCSG-PC] Human Rights Analysis of SSAD & ODA Reports In-Reply-To: References: <22924cc4-d32d-2df5-9b1d-983cb1235b66@ekenyanito.com> Message-ID: Thanks, Tomslin! @Ephraim Percy Kenyanito , can you transform the doc into a PDF and I will follow up tomorrow morning by writing a short letter submitting it to the board and send it afterwards ? best, B On Sun, Jul 10, 2022 at 2:40 PM Tomslin Samme-Nlar wrote: > Hi Bruna, > > With no further concerns received from the PC, I believe Ephraim has > accommodated suggestions and edits provided so far by NCSG and the PC is > happy for the EC to send the report to the board. > > Warmly, > Tomslin > > > > On Sat, 2 Jul 2022 at 07:59, Tomslin Samme-Nlar > wrote: > >> Dear PC, >> >> Bringing this to the top of your inboxes for discussion. Ephraim has >> requested that we transmit the below HRIA on behalf of CCWP-HR. As PC, we >> need to decide if it meets/aligns with our policy objectives or any >> edits/adds we'll like to add to the document before the executive committee >> can proceed with it. Do let us know if you have any objections or concerns >> with the report as provided by Next week Friday 8th July please. >> >> Warmly, >> Tomslin >> >> >> ---------- Forwarded message --------- >> From: Ephraim Percy Kenyanito >> Date: Wed, 22 Jun 2022 at 01:33 >> Subject: Re: Human Rights Analysis of SSAD & ODA Reports >> To: >> >> >> Dear NCSG and SG & PC, >> >> I would like to request that NCSG transmits the research to the board on >> behalf of CCWP-HR. >> This report has adopted the use of the human rights impact assessments >> (HRIA) methodology as proposed in the FOI-HR. This methodology has been >> used in the October 2019 Trial HRIA for ICANN PDPs ? Final Report. >> >> We note that, the FOI-HR requires that various Supporting Organizations >> and Advisory Committees that comprise the ICANN community should be >> responsible for developing their own policies and frameworks to fulfill the >> Human Rights Core Value. However, the FOI-HR suggests HRIAs as a potential >> means of incorporating human rights considerations into policy development >> processes. HRIAs are rooted in the international human rights framework and >> used increasingly by companies, governments, and civil society alike as a >> tool to document a broader range of actual and potential impacts as part of >> a larger system of due diligence. >> >> Therefore, this report uses the Comprehensive HRIA format, which was >> developed by the CCWP-HR in 2019, as it provides the opportunity for >> stakeholders with divergent positions and opinions to engage constructively >> through the collection and comparison of empirical evidence, anecdotes, and >> general observations. This report provides the completed HRIA as an annex >> at the end of the report. >> Second, extensive desk research was also undertaken in compiling the >> final report to not just identify applicable legal instruments but also >> review relevant cases with a view to understanding what is legal, feasible, >> permissible and acceptable within the confines of ICANN?s Articles of >> Incorporation, the Core Values and the Bylaws. >> >> Best Regards, >> >> Ephraim Percy Kenyanito >> On 17/06/2022 16:29, farzaneh badii wrote: >> >> Fantastic! Look forward to reading it. >> >> On Fri, Jun 17, 2022 at 3:21 PM Ephraim Percy Kenyanito < >> hello at ekenyanito.com> wrote: >> >>> Dear NCSG, >>> >>> Please find the below communication and a prose document here: >>> https://docs.google.com/document/d/1XwC5YBDViRDME4Et7wzMchCkHe6z82V83Gpcb2dJ9k4/edit?usp=sharing >>> >>> Please feel free to add any comments. >>> >>> >>> -- >>> >>> Best Regards, >>> Ephraim Percy Kenyanito >>> Public Policy Specialist/ Regulatory Affairs Specialist/ Project Manager- >>> International Trade, Technology, Media & Telecommunications Laws >>> Website: https://ekenyanito.com/ >>> Twitter: @ekenyanito >>> PGP Fingerprint: B0FA394AF73DEB7AA1FDC7360CFED26DE6BA8DC1 >>> >>> >>> -------- Forwarded Message -------- >>> Subject: Re: Human Rights Analysis of SSAD & ODA Reports >>> Date: Wed, 15 Jun 2022 19:50:31 +0300 >>> From: Ephraim Percy Kenyanito >>> >>> To: cc-humanrights at icann.org, Francis Monyango >>> >>> CC: Tomslin Samme-Nlar , >>> Bruna Martins dos Santos >>> >>> Dear CCWP-HR, >>> >>> Please find the prose document here: >>> https://docs.google.com/document/d/1XwC5YBDViRDME4Et7wzMchCkHe6z82V83Gpcb2dJ9k4/edit?usp=sharing >>> >>> Please feel free to add any comments. >>> >>> >>> -- >>> >>> Best Regards, >>> Ephraim Percy Kenyanito >>> Public Policy Specialist/ Regulatory Affairs Specialist/ Project Manager- >>> International Trade, Technology, Media & Telecommunications Laws >>> Website: https://ekenyanito.com/ >>> Twitter: @ekenyanito >>> PGP Fingerprint: B0FA394AF73DEB7AA1FDC7360CFED26DE6BA8DC1 >>> On 29/05/2022 15:23, Ephraim Percy Kenyanito wrote: >>> >>> Dear team, >>> >>> Hope you are all well. >>> >>> This is in reference to previous conversations on the topic. >>> >>> Franc (copied here in this email) has been helpful in looking through >>> the documents. >>> Please find attached the analysis here: >>> https://docs.google.com/spreadsheets/d/1R0j8RwbUrxbPxVIe_5Hgc4CRNUaXkSoyZ-xXNF1N5h8/edit?usp=sharing >>> >>> The document contains two sheets; >>> >>> First, EPDP HRIA- analyses the EPDP Phase 2 Recommendations which inform >>> the ODA Report. >>> >>> Second, ODA HRIA- analyses the ODA Recommendations which aims to >>> implement the EPDP Report. >>> >>> >>> FYI- The ODA Report is informed by the EPDP Report though in some >>> instances ICANN might have misunderstood the EPDP Report and ICANN Board >>> wrote to the GNSO Council raising this questions: >>> >>> 1. >>> >>> Whether the ODA has correctly interpreted the intent of the SSAD >>> recommendations in the proposed implementation; >>> 2. >>> >>> Whether the ODA has overlooked any key aspects of the SSAD >>> recommendations that should be factored in by the ICANN Board when it >>> considers the recommendations; >>> 3. >>> >>> Its view on the concerns identified by the ICANN Board and potential >>> options that could be considered, either in the form of changes to the >>> proposed implementation or the policy recommendations themselves, to >>> address these concerns (note, these are expected to be high level >>> suggestions at this stage); >>> 4. >>> >>> Any other aspects that help inform the Council?s deliberations and >>> consultation with the ICANN Board. >>> >>> >>> For background here are the original documents that were being analysed: >>> >>> 1. >>> >>> EPDP Phase 2 Final Report: >>> https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phase-2-temp-spec-gtld-registration-data-2-31jul20-en.pdf >>> 2. >>> >>> ODA Final Report: >>> https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf >>> >>> I look forward to your feedback as I begin working on the prose report >>> which I hope to complete the first version by June 7th and will be >>> scheduled to be maximum 10 pages for transmission to the board via NCSG >>> (which CCWP-HR is seated). >>> >>> Please feel free to let me know in case of any questions. >>> >>> >>> --- >>> >>> Best Regards, >>> >>> *EPK* >>> >>> >>> -- >> Farzaneh >> >> -- *Bruna Martins dos Santos * German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von Humboldt Foundation Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum Berlin f?r Sozialforschung (WZB) Member | Coaliz?o Direitos na Rede Chair | Non-Commercial Stakeholder Group at ICANN Co-Coordinator | Internet Governance Caucus Twitter: @boomartins // Skype: bruna.martinsantos *bruna.martinsdossantos at wzb.eu * and bruna.mrtns at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Tue Jul 12 00:52:36 2022 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Tue, 12 Jul 2022 07:52:36 +1000 Subject: [NCSG-PC] IDNs EPDP membership Message-ID: Hello PC, I would like to inform you that I would like to replace myself as a member of the IDNs EPDP with Emmanuel Vitus from NPOC executive team since the meetings have been at midnight (weekly) my time and have been difficult for me to attend. I will remain as an observer. Warmly, Tomslin -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kathy at KathyKleiman.com Tue Jul 12 19:43:25 2022 From: Kathy at KathyKleiman.com (Kathy Kleiman) Date: Tue, 12 Jul 2022 12:43:25 -0400 Subject: [NCSG-PC] IDNs EPDP membership In-Reply-To: References: Message-ID: Tx for all of your work, Tomslin, and the midnight calls! Emmanuel, good luck in this important work! Best, Kathy On 7/11/2022 5:52 PM, Tomslin Samme-Nlar wrote: > Hello PC, > > I would like to inform you that I would like to replace myself as a > member of the IDNs EPDP with Emmanuel Vitus from NPOC executive team > since the meetings have been at midnight (weekly) my time and have > been difficult for me to attend. I will remain as an observer. > > Warmly, > Tomslin > > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc -------------- next part -------------- An HTML attachment was scrubbed... URL: From hello at ekenyanito.com Tue Jul 12 14:05:34 2022 From: hello at ekenyanito.com (Ephraim Percy Kenyanito) Date: Tue, 12 Jul 2022 14:05:34 +0300 Subject: [NCSG-PC] Human Rights Analysis of SSAD & ODA Reports In-Reply-To: References: <22924cc4-d32d-2df5-9b1d-983cb1235b66@ekenyanito.com> Message-ID: <706c16f7-a3c9-8225-42e8-74ccaaa0228a@ekenyanito.com> Dear Bruna, Thank you so much. Apologies, yesterday was a public holiday here and I was away from my computer. I have now incorporated the changes as needed. I really appreciate. We can go ahead and do the letter. Best Regards, Ephraim Percy Kenyanito On 11/07/2022 00:25, Bruna Martins dos Santos wrote: > Thanks, Tomslin! > > @Ephraim Percy Kenyanito , can you > transform the doc into a PDF and I will follow up tomorrow morning by > writing a short letter submitting it to the board and send it afterwards?? > > best, > B > > On Sun, Jul 10, 2022 at 2:40 PM Tomslin Samme-Nlar > wrote: > > Hi Bruna, > > With no further concerns received from the PC, I believe Ephraim > has accommodated suggestions and edits provided so far by NCSG and > the PC is happy for the EC to send the report to the board. > > Warmly, > Tomslin > > > > On Sat, 2 Jul 2022 at 07:59, Tomslin Samme-Nlar > wrote: > > Dear PC, > > Bringing this to the top of your inboxes for discussion. > Ephraim has requested that we transmit the below HRIA on > behalf of CCWP-HR. As PC, we need to decide if it meets/aligns > with our policy objectives or any edits/adds we'll like to add > to the document before the executive committee can proceed > with it. Do let us know if you have any objections or concerns > with the report as provided by Next week Friday 8th July please. > > Warmly, > Tomslin > > > ---------- Forwarded message --------- > From: *Ephraim Percy Kenyanito* > Date: Wed, 22 Jun 2022 at 01:33 > Subject: Re: Human Rights Analysis of SSAD & ODA Reports > To: > > > Dear NCSG and SG & PC, > > I would like to request that NCSG transmits the research to > the board on behalf of CCWP-HR. > This report has adopted the use of the human rights impact > assessments (HRIA) methodology as proposed in the FOI-HR. This > methodology has been used in the October 2019 Trial HRIA for > ICANN PDPs ? Final Report. > > We note that, the FOI-HR requires that various Supporting > Organizations and Advisory Committees that comprise the ICANN > community should be responsible for developing their own > policies and frameworks to fulfill the Human Rights Core > Value. However, the FOI-HR suggests HRIAs as a potential means > of incorporating human rights considerations into policy > development processes. HRIAs are rooted in the international > human rights framework and used increasingly by companies, > governments, and civil society alike as a tool to document a > broader range of actual and potential impacts as part of a > larger system of due diligence. > > Therefore, this report uses the Comprehensive HRIA format, > which was developed by the CCWP-HR in 2019, as it provides the > opportunity for stakeholders with divergent positions and > opinions to engage constructively through the collection and > comparison of empirical evidence, anecdotes, and general > observations. This report provides the completed HRIA as an > annex at the end of the report. > Second, extensive desk research was also undertaken in > compiling the final report to not just identify applicable > legal instruments but also review relevant cases with a view > to understanding what is legal, feasible, permissible and > acceptable within the confines of ICANN?s Articles of > Incorporation, the Core Values and the Bylaws. > > Best Regards, > > Ephraim Percy Kenyanito > > On 17/06/2022 16:29, farzaneh badii wrote: >> Fantastic! Look forward to reading it. >> >> On Fri, Jun 17, 2022 at 3:21 PM Ephraim Percy Kenyanito >> wrote: >> >> Dear NCSG, >> >> Please find the below communication and a prose document >> here: >> https://docs.google.com/document/d/1XwC5YBDViRDME4Et7wzMchCkHe6z82V83Gpcb2dJ9k4/edit?usp=sharing >> >> Please feel free to add any comments. >> >> >> -- >> >> Best Regards, >> >> Ephraim Percy Kenyanito >> >> Public Policy Specialist/ Regulatory Affairs Specialist/ >> Project Manager- >> International Trade, Technology, Media & >> Telecommunications Laws >> Website: https://ekenyanito.com/ >> Twitter: @ekenyanito >> PGP Fingerprint: B0FA394AF73DEB7AA1FDC7360CFED26DE6BA8DC1 >> >> >> -------- Forwarded Message -------- >> Subject: Re: Human Rights Analysis of SSAD & ODA Reports >> Date: Wed, 15 Jun 2022 19:50:31 +0300 >> From: Ephraim Percy Kenyanito >> >> To: cc-humanrights at icann.org, Francis Monyango >> >> CC: Tomslin Samme-Nlar >> , Bruna Martins dos Santos >> >> >> >> >> Dear CCWP-HR, >> >> Please find the prose document here: >> https://docs.google.com/document/d/1XwC5YBDViRDME4Et7wzMchCkHe6z82V83Gpcb2dJ9k4/edit?usp=sharing >> >> Please feel free to add any comments. >> >> >> -- >> >> Best Regards, >> >> Ephraim Percy Kenyanito >> >> Public Policy Specialist/ Regulatory Affairs Specialist/ >> Project Manager- >> International Trade, Technology, Media & >> Telecommunications Laws >> Website: https://ekenyanito.com/ >> Twitter: @ekenyanito >> PGP Fingerprint: B0FA394AF73DEB7AA1FDC7360CFED26DE6BA8DC1 >> On 29/05/2022 15:23, Ephraim Percy Kenyanito wrote: >>> >>> Dear team, >>> >>> Hope you are all well. >>> >>> This is in reference to previous conversations on the topic. >>> >>> Franc (copied here in this email) has been helpful in >>> looking through the documents. >>> >>> Please find attached the analysis here: >>> https://docs.google.com/spreadsheets/d/1R0j8RwbUrxbPxVIe_5Hgc4CRNUaXkSoyZ-xXNF1N5h8/edit?usp=sharing >>> >>> >>> The document contains two sheets; >>> >>> First, EPDP HRIA- analyses the EPDP Phase 2 >>> Recommendations which inform the ODA Report. >>> >>> Second, ODA HRIA- analyses the ODA Recommendations which >>> aims to implement the EPDP Report. >>> >>> >>> FYI- The ODA Report is informed by the EPDP Report >>> though in some instances ICANN might have misunderstood >>> the EPDP Report and ICANN Board wrote to the GNSO >>> Council raising this questions: >>> >>> 1. >>> >>> Whether the ODA has correctly interpreted the intent >>> of the SSAD recommendations in the proposed >>> implementation; >>> >>> 2. >>> >>> Whether the ODA has overlooked any key aspects of >>> the SSAD recommendations that should be factored in >>> by the ICANN Board when it considers the >>> recommendations; >>> >>> 3. >>> >>> Its view on the concerns identified by the ICANN >>> Board and potential options that could be >>> considered, either in the form of changes to the >>> proposed implementation or the policy >>> recommendations themselves, to address these >>> concerns (note, these are expected to be high level >>> suggestions at this stage); >>> >>> 4. >>> >>> Any other aspects that help inform the Council?s >>> deliberations and consultation with the ICANN Board. >>> >>> >>> For background here are the original documents that were >>> being analysed: >>> >>> 1. >>> >>> EPDP Phase 2 Final Report: >>> https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phase-2-temp-spec-gtld-registration-data-2-31jul20-en.pdf >>> >>> >>> 2. >>> >>> ODA Final Report: >>> https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf >>> >>> >>> I look forward to your feedback as I begin working on >>> the prose report which I hope to complete the first >>> version by June 7^th and will be scheduled to be maximum >>> 10 pages for transmission to the board via NCSG (which >>> CCWP-HR is seated). >>> >>> Please feel free to let me know in case of any questions. >>> >>> >>> --- >>> >>> Best Regards, >>> >>> *EPK* >>> >>> >> -- >> Farzaneh > > > > -- > */Bruna Martins dos Santos > /* > > German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander > von Humboldt Foundation > > Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum > Berlin f?r Sozialforschung (WZB) > > Member | Coaliz?o Direitos na Rede > Chair?| Non-Commercial Stakeholder Group at ICANN > > Co-Coordinator?| Internet Governance Caucus > > Twitter: @boomartins ?// Skype: > bruna.martinsantos > _bruna.martinsdossantos at wzb.eu_?and bruna.mrtns at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From PolicyCalendar at icann.org Fri Jul 15 17:35:39 2022 From: PolicyCalendar at icann.org (ICANN Policy Calendar) Date: Fri, 15 Jul 2022 14:35:39 +0000 Subject: [NCSG-PC] REMINDER: NCSG Policy Call | 18 July at 11:30 UTC Message-ID: <4c1bf005b92741d8b2e725c8d38cbc18@icann.org> Please join the NCSG Monthly Policy call on Monday, 18 July at 11:30 UTC. Additional time zone support here. Join Zoom Meeting: https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09 Meeting ID: 988 7818 9584 Passcode: i!y7.qx+11 WANT US TO CALL YOU? Please send dial-out request and apologies to brenda.brewer at icann.org. One tap mobile +16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose) +12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma) PHONE ONLY DETAILS: Find your local number: https://icann.zoom.us/u/ayKmeftWg Meeting ID: 988 7818 9584 Phone only Passcode: 7740925615 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2558 bytes Desc: not available URL: From brenda.brewer at icann.org Fri Jul 15 17:37:47 2022 From: brenda.brewer at icann.org (Brenda Brewer) Date: Fri, 15 Jul 2022 14:37:47 +0000 Subject: [NCSG-PC] NCSG Policy Call | 18 July at 11:30 UTC In-Reply-To: <95C8A690-4836-42CB-B3A4-8CCC4D543C07@icann.org> References: <95C8A690-4836-42CB-B3A4-8CCC4D543C07@icann.org> Message-ID: <32164A2C-41CD-4501-960F-BEAC94D02B9B@icann.org> Good day all, A kind reminder of Monday?s NCSG Monthly Policy call, 18 July at 11:30 UTC. Additional time zone support here. The join details are attached and noted below for your convenience. Thank you. Best, Andrea & Brenda From: Brenda Brewer Date: Thursday, June 23, 2022 at 12:57 PM To: "ncsg-pc at lists.ncsg.is" , NCSG List Cc: Brenda Brewer , Andrea Glandon Subject: NCSG Policy Call | 18 July at 11:30 UTC Good day all, Please join the NCSG Monthly Policy call on Monday, 18 July at 11:30 UTC. Additional time zone support here. The join details are attached and noted below for your convenience. Thank you. Join Zoom Meeting: https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09 Meeting ID: 988 7818 9584 Passcode: i!y7.qx+11 One tap mobile +16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose) +12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma) Kind regards, Andrea and Brenda -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: NCSG Policy Call 18 July at 11-30 UTC.ics Type: text/calendar Size: 2558 bytes Desc: NCSG Policy Call 18 July at 11-30 UTC.ics URL: From PolicyCalendar at icann.org Fri Jul 15 19:09:23 2022 From: PolicyCalendar at icann.org (ICANN Policy Calendar) Date: Fri, 15 Jul 2022 16:09:23 +0000 Subject: [NCSG-PC] NCSG Policy Call | 22 August at 11:30 UTC Message-ID: <0a211fcb9ae44fff935a81e6e04484a1@icann.org> Please join the NCSG Monthly Policy call on Monday, 22 August at 11:30 UTC. Additional time zone support here. Join Zoom Meeting: https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09 Meeting ID: 988 7818 9584 Passcode: i!y7.qx+11 WANT US TO CALL YOU? Please send dial-out request and apologies to brenda.brewer at icann.org. One tap mobile +16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose) +12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma) PHONE ONLY DETAILS: Find your local number: https://icann.zoom.us/u/ayKmeftWg Meeting ID: 988 7818 9584 Phone only Passcode: 7740925615 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2554 bytes Desc: not available URL: From brenda.brewer at icann.org Fri Jul 15 19:12:36 2022 From: brenda.brewer at icann.org (Brenda Brewer) Date: Fri, 15 Jul 2022 16:12:36 +0000 Subject: [NCSG-PC] NCSG Policy Call | 22 August at 11:30 UTC Message-ID: <1608A28C-9D9B-46B5-AC6C-2C031BCE8026@icann.org> Good day all, Please join the NCSG Monthly Policy call on Monday, 22 August at 11:30 UTC. Additional time zone support here. The join details are attached and noted below for your convenience. Thank you. Join Zoom Meeting: https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09 Meeting ID: 988 7818 9584 Passcode: i!y7.qx+11 One tap mobile +16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose) +12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma) Kind regards, Andrea and Brenda -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: NCSG Policy Call 22 August at 11-30 UTC.ics Type: text/calendar Size: 2566 bytes Desc: NCSG Policy Call 22 August at 11-30 UTC.ics URL: From mesumbeslin at gmail.com Fri Jul 15 23:45:40 2022 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Sat, 16 Jul 2022 06:45:40 +1000 Subject: [NCSG-PC] Fwd: [council] Motion for the Initiation of the GNSO Guidance Process on Applicant Support In-Reply-To: <9152B695-958F-48B9-8FC8-D7595D8B42B3@kjpritz.com> References: <1320_1657709181_62CEA27D_1320_499_1_23015e7b359d444284612c759588f222@orange.com> <9152B695-958F-48B9-8FC8-D7595D8B42B3@kjpritz.com> Message-ID: Hi Policy committee members, I'd like to hear what you think of this counter proposal from Kurt. Specifically, he wants that rather than *a 30-member (20 active, 10 alternate) Steering Committee to complete the Applicant Support program development, the Council should form a small team that works with ICANN to retain and employ the outside skills necessary to create the Applicant Support program framework*. Warmly, Tomslin @LinkedIn: https://www.linkedin.com/in/tomslin/ ---------- Forwarded message --------- From: kurt kjpritz.com via council Date: Sat, 16 Jul 2022 at 03:11 Subject: Re: [council] Motion for the Initiation of the GNSO Guidance Process on Applicant Support To: Fouquart , council at gnso.icann.org < council at gnso.icann.org> Cc: gnso-secs at icann.org Hello Councilors: I am writing to offer an amendment to the Motion to initiate the GNSO Guidance Process (GGP). It is enough of a departure from the original that I don?t think it can / will be considered a friendly amendment. In any case, I think it?d be beneficial to the outcome if we debated the two approaches and decided on one. I think the discussion is as important as the outcome. The amendment more directly affects the GGP Initiation Request that is incorporated into the motion. It seeks to simplify the process for creating an Applicant Support Program. (An Initiation Request is a prerequisite to launching a GGP.) *Background and Recent Developments:* The SubPro Final Report recommended that a ?dedicated IRT? be created to flesh out the Applicant Support Program. In response, the ODP Team expressed concern that the work recommended by SubPro was potentially out of scope of the role for an IRT and should be returned to the GNSO. The Council recognized that this work could be accomplished using the GNSO Guidance Process (GGP), which is flexible, i.e., adaptable to the needs of various policy-related tasks. The current motion calls for the creation of a 30-member (20 active, 10 alternate) Steering Committee to complete the Applicant Support program development with the added implication that this group could be used for additional policy / implementation issues. *Recommendation:* Rather than a Steering Committee, the Council should form a small team that works with ICANN to retain and employ the outside skills necessary to create the Applicant Support program framework. *Rationale for this Recommendation:* 1. We approved the SubPro Final Report, so we should do what it says. The Report advised that a community-based team would not possess the requisite skills to develop the Applicant Support program and an issue-specific team with the necessary outside skillsets should be formed. Creating a 30-member community team is, at best, an unnecessary step and, more likely, is the antithesis of the SubPro Report direction and disrespectful of valuable volunteer time. 2. Creating a small team does not contradict the participatory, bottom-up model. The broad community discussed this topic for five years and provided the best direction it could, to take the discussion out from under the community umbrella. In any event, no GNSO stakeholder group would be precluded from sending a member to this small team, and whatever Applicant Support program is recommended, the community will have the opportunity to discuss it prior to adoption. 3. Nor is a standing 30-person Steering Committee likely to be an economical or effective approach if asked to consider additional issues. This steering committee likely would be populated by those interested in the Applicant Support program and not have the necessary skill sets for, or interest in, tackling different issues. Community members interested in subsequent issues would likely be closed out of participating because the committee would be populated by those interested in the Applicant Support program. So, the 30-member committee, already demonstrated to be inefficient for the purpose of sorting the Applicant Support issues, would also be ineffectual on the subsequent issues. 4. This is likely to be an extended commitment on the part of our depleted volunteer workforce. Cannot we, as managers of the policy process, manage these important areas of policy / implementation administration, and reserve volunteers? valuable time for substantive work? In the meantime, we can launch this first-ever GGP effort, keep it narrow to make it efficient, and learn from it. I?ve attached an alternative GGP Initiation Request. Amendments and additional discussion are welcome Sincerely, Kurt On Jul 13, 2022, at 3:46 AM, philippe.fouquart--- via council < council at gnso.icann.org> wrote: Dear Councilors, Please find attached the GNSO Guidance Process associated with the motion circulated on Monday. This version is intended to incorporate comments made in The Hague, notably on focusing on applicant support and the flexibility bw a steering group and subteams. A couple of additional things that leadership would like to draw your attention to in case you?d have an opinion: - the need for the GNSO Liaison to the ODP to be a (non voting) member (that?s under 5.) - the explicit acknowledgement that this group may deliver their results after the conclusion of the ODP or even the Board?s vote. (under 7) Thanks. Regards, Philippe *From:* FOUQUART Philippe INNOV/NET *Sent:* Monday, July 11, 2022 5:14 PM *To:* council at gnso.icann.org *Cc:* 'gnso-secs at icann.org' *Subject:* Motion for the Initiation of the GNSO Guidance Process on Applicant Support Dear Councilors, Following our discussion in The Hague, please find attached the Motion for the Initiation of the GNSO Guidance Process on Applicant Support submitted to the July 21st Council meeting. It will be updated with the link to the GGP within a few days. 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. _______________________________________________ council mailing list council at 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. _______________________________________________ council mailing list council at 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: GGP Initiation Request-Applicant Support.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 28893 bytes Desc: not available URL: From Kathy at KathyKleiman.com Mon Jul 18 05:33:50 2022 From: Kathy at KathyKleiman.com (Kathy Kleiman) Date: Sun, 17 Jul 2022 22:33:50 -0400 Subject: [NCSG-PC] Fwd: [council] Motion for the Initiation of the GNSO Guidance Process on Applicant Support In-Reply-To: References: <1320_1657709181_62CEA27D_1320_499_1_23015e7b359d444284612c759588f222@orange.com> <9152B695-958F-48B9-8FC8-D7595D8B42B3@kjpritz.com> Message-ID: <8afb544c-89f7-4c6f-feed-d4e16261f0a1@KathyKleiman.com> Hi All, Tx Tomslin for sharing!? I wish, I wish, we could take the lead on this, but I know time is stretched all round.? Do we have a good person who could serve on the Small Group? What do others think? I see some merit in Kurt's proposal.? I think this should go farther - much farther - to define "to retain and employ the outside skills?necessary to?create the Applicant Support program framework." Who?? This should be given considerable thought by NCSG and the GNSO Council. IMHO, we don't want the usual US consulting firms, but experts from and in Global South communities, indigenous peoples (in the Global South and Global North), minority communities, and likely linguists to think through IDN issues for these communities to.? (I'll call them "Applicant Support Communities"). And a separate group of technical gTLD experts. As the Subpro WG discussed and included in their recommendation and supporting language, many communities and peoples will need more than just application fees.? They'll need consulting and other support in planning to apply for and run a gTLD (including IDN gTLDs), then filling out the detailed ICANN gTLD application (a big process!), paying submission fees, then preparing for the work of managing and running a gTLD (also a lot of work!). This is not just my view, but SubPro WG's discussion. Overall, if the Applicant Support program framework, heads in this direction, it will need "outside skills" with experts who know the Applicant Support Communities and how to reach and work with them, and [a different group] technical experts to work with applicants who know what a gTLD application is (technical, operational, financial requirements) and what it takes to run one once they get the gTLD delegation from ICANN. /If you agree with the assessment above//, how can we build these details expressly into Kurt's countrproposal (he says he is receptive to amendments)./ Best and tx, Kathy On 7/15/2022 4:45 PM, Tomslin Samme-Nlar wrote: > Hi Policy committee members, > > I'd like to hear what you think of this counter proposal from Kurt. > Specifically, he wants that rather than *a 30-member (20 active, 10 > alternate) Steering Committee to complete the Applicant Support > program development, the Council should form a small team that works > with ICANN to retain and employ the outside skills necessary to create > the Applicant Support program framework*. > > Warmly, > Tomslin > @LinkedIn: https://www.linkedin.com/in/tomslin/ > > > ---------- Forwarded message --------- > From: *kurt kjpritz.com via council* > > Date: Sat, 16 Jul 2022 at 03:11 > Subject: Re: [council] Motion for the Initiation of the GNSO Guidance > Process on Applicant Support > To: Fouquart , council at gnso.icann.org > > Cc: gnso-secs at icann.org > > > Hello Councilors: > > I am writing to offer an amendment to the Motion to initiate the > GNSO?Guidance Process (GGP). It is enough of a?departure from the > original that I?don?t think it can / will be considered a friendly > amendment. In any case, I?think it?d?be beneficial to the outcome if > we debated the two approaches and?decided on one. I think the > discussion is as?important as the outcome. > > The amendment more directly affects the?GGP?Initiation Request?that is > incorporated into the motion. It seeks to?simplify the process for > creating an?Applicant Support Program. (An Initiation?Request is a > prerequisite to launching a GGP.) > > *Background and Recent Developments:*?The SubPro Final?Report > recommended that a ?dedicated IRT? be created to flesh out the > Applicant?Support?Program. In response, the ODP Team expressed concern > that the work?recommended by SubPro was potentially out of scope of > the role for an IRT and?should be returned to the GNSO. > > The Council recognized?that this work?could?be accomplished using > the?GNSO Guidance?Process?(GGP), which is flexible, i.e., adaptable to > the needs of?various policy-related?tasks. > > The current motion?calls for the creation of a 30-member (20 active, > 10 alternate) Steering Committee?to complete the?Applicant Support > program development with the added?implication that this group could > be used for additional policy?/?implementation issues. > > *Recommendation:*?Rather than a Steering Committee, the Council should > form a small?team that works with ICANN to retain and employ the > outside skills?necessary to?create the Applicant Support program > framework. > > *Rationale for this Recommendation:* > > 1.? ???We approved the SubPro Final?Report, so we should do what it > says. The Report advised that a community-based?team would not possess > the requisite?skills to develop the Applicant Support?program and an > issue-specific team with the necessary outside skillsets should?be > formed. Creating a 30-member?community team is, at best, an > unnecessary step?and, more likely, is the antithesis of the SubPro > Report direction and disrespectful?of valuable volunteer?time. > > 2.? ???Creating a small team does not?contradict the participatory, > bottom-up model. The broad community discussed?this topic for five > years and provided the best?direction it could, to take the?discussion > out from under the community umbrella. In any event, no > GNSO?stakeholder group would be precluded from sending?a member to > this small team,?and whatever Applicant Support program is > recommended, the community will have?the opportunity to discuss it > prior to?adoption. > > 3.? ???Nor is a standing 30-person Steering?Committee likely to be an > economical or effective approach if asked to consider?additional > issues. This steering?committee likely would be populated by those > interested?in the Applicant Support program and not have the necessary > skill sets for, or?interest in, tackling?different > issues.??Community?members interested in subsequent issues would > likely be closed out of?participating because the committee would be > populated?by those interested in the?Applicant Support program. So, > the 30-member committee, already demonstrated to?be inefficient for > the purpose of sorting the?Applicant Support issues, would also?be > ineffectual on the subsequent issues. > > 4.? ???This is?likely to be an extended commitment on the part of our > depleted volunteer?workforce. Cannot we, as managers of the policy > process, manage these?important?areas of policy / implementation > administration, and reserve volunteers??valuable time for substantive > work? In the meantime, we can launch this?first-ever GGP effort, keep > it narrow to make it efficient, and learn from?it. > > I?ve attached an alternative GGP Initiation?Request. Amendments and > additional discussion are welcome > > Sincerely, > > Kurt > > > > > > > >> On Jul 13, 2022, at 3:46 AM, philippe.fouquart--- via council >> wrote: >> >> Dear Councilors, >> Please find attached the GNSO Guidance Process associated with the >> motion circulated on Monday. >> This version is intended to incorporate comments made in The Hague, >> notably on focusing on applicant support and the flexibility bw a >> steering group and subteams. A couple of additional things that >> leadership would like to draw your attention to in case you?d have an >> opinion: >> >> * the need for theGNSO Liaison to the ODP to be a (non voting) >> member(that?s under 5.) >> * the explicit acknowledgement that this group may deliver their >> results after the conclusion of the ODP or even the Board?s vote. >> (under 7) >> >> Thanks. >> Regards, >> Philippe >> *From:*FOUQUART Philippe INNOV/NET >> *Sent:*Monday, July 11, 2022 5:14 PM >> *To:*council at gnso.icann.org >> *Cc:*'gnso-secs at icann.org' >> *Subject:*Motion for the Initiation of the GNSO Guidance Process on >> Applicant Support >> Dear Councilors, >> Following our discussion in The Hague, please find attached the >> Motion for the Initiation of the GNSO Guidance Process on Applicant >> Support submitted to the July 21^st Council meeting. It will be >> updated with the link to the GGP within a few days. >> 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. >> _______________________________________________ >> council mailing list >> council at 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. > > _______________________________________________ > council mailing list > council at 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. > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Mon Jul 18 11:39:20 2022 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Mon, 18 Jul 2022 18:39:20 +1000 Subject: [NCSG-PC] Fwd: [council] Motion for the Initiation of the GNSO Guidance Process on Applicant Support In-Reply-To: <8afb544c-89f7-4c6f-feed-d4e16261f0a1@KathyKleiman.com> References: <1320_1657709181_62CEA27D_1320_499_1_23015e7b359d444284612c759588f222@orange.com> <9152B695-958F-48B9-8FC8-D7595D8B42B3@kjpritz.com> <8afb544c-89f7-4c6f-feed-d4e16261f0a1@KathyKleiman.com> Message-ID: Thanks for your comments, Kathy. I am not an expert in this area but your proposal of using experts from global south, indigenous communities and minority communities on one hand and technical experts on the other sounds like a good idea to me. It'll be good to hear what others here think. Warmly, Tomslin On Mon, 18 July 2022, 12:33 Kathy Kleiman, wrote: > Hi All, > > Tx Tomslin for sharing! I wish, I wish, we could take the lead on this, > but I know time is stretched all round. Do we have a good person who could > serve on the Small Group? > > What do others think? > > I see some merit in Kurt's proposal. I think this should go farther - > much farther - to define "to retain and employ the outside skills necessary > to create the Applicant Support program framework." > > Who? This should be given considerable thought by NCSG and the GNSO > Council. IMHO, we don't want the usual US consulting firms, but experts > from and in Global South communities, indigenous peoples (in the Global > South and Global North), minority communities, and likely linguists to > think through IDN issues for these communities to. (I'll call them > "Applicant Support Communities"). > > And a separate group of technical gTLD experts. As the Subpro WG discussed > and included in their recommendation and supporting language, many > communities and peoples will need more than just application fees. They'll > need consulting and other support in planning to apply for and run a gTLD > (including IDN gTLDs), then filling out the detailed ICANN gTLD application > (a big process!), paying submission fees, then preparing for the work of > managing and running a gTLD (also a lot of work!). This is not just my > view, but SubPro WG's discussion. > > Overall, if the Applicant Support program framework, heads in this > direction, it will need "outside skills" with experts who know the > Applicant Support Communities and how to reach and work with them, and [a > different group] technical experts to work with applicants who know what a > gTLD application is (technical, operational, financial requirements) and > what it takes to run one once they get the gTLD delegation from ICANN. > > *If you agree with the assessment above**, how can we build these details > expressly into Kurt's countrproposal (he says he is receptive to > amendments).* > > Best and tx, Kathy > On 7/15/2022 4:45 PM, Tomslin Samme-Nlar wrote: > > Hi Policy committee members, > > I'd like to hear what you think of this counter proposal from Kurt. > Specifically, he wants that rather than *a 30-member (20 active, 10 > alternate) Steering Committee to complete the Applicant Support program > development, the Council should form a small team that works with ICANN to > retain and employ the outside skills necessary to create the Applicant > Support program framework*. > > Warmly, > Tomslin > @LinkedIn: https://www.linkedin.com/in/tomslin/ > > > ---------- Forwarded message --------- > From: kurt kjpritz.com via council > Date: Sat, 16 Jul 2022 at 03:11 > Subject: Re: [council] Motion for the Initiation of the GNSO Guidance > Process on Applicant Support > To: Fouquart , council at gnso.icann.org < > council at gnso.icann.org> > Cc: gnso-secs at icann.org > > > Hello Councilors: > > I am writing to offer an amendment to the Motion to initiate the > GNSO Guidance Process (GGP). It is enough of a departure from the original > that I don?t think it can / will be considered a friendly amendment. In any > case, I think it?d be beneficial to the outcome if we debated the two > approaches and decided on one. I think the discussion is as important as > the outcome. > > The amendment more directly affects the GGP Initiation Request that is > incorporated into the motion. It seeks to simplify the process for creating > an Applicant Support Program. (An Initiation Request is a prerequisite to > launching a GGP.) > > *Background and Recent Developments:* The SubPro Final Report recommended > that a ?dedicated IRT? be created to flesh out the > Applicant Support Program. In response, the ODP Team expressed concern that > the work recommended by SubPro was potentially out of scope of the role for > an IRT and should be returned to the GNSO. > > The Council recognized that this work could be accomplished using the GNSO > Guidance Process (GGP), which is flexible, i.e., adaptable to the needs > of various policy-related tasks. > > The current motion calls for the creation of a 30-member (20 active, 10 > alternate) Steering Committee to complete the Applicant Support program > development with the added implication that this group could be used for > additional policy / implementation issues. > > *Recommendation:* Rather than a Steering Committee, the Council should > form a small team that works with ICANN to retain and employ the outside > skills necessary to create the Applicant Support program framework. > > *Rationale for this Recommendation:* > > 1. We approved the SubPro Final Report, so we should do what it says. > The Report advised that a community-based team would not possess the > requisite skills to develop the Applicant Support program and an > issue-specific team with the necessary outside skillsets should be formed. > Creating a 30-member community team is, at best, an unnecessary step and, > more likely, is the antithesis of the SubPro Report direction and > disrespectful of valuable volunteer time. > > 2. Creating a small team does not contradict the participatory, > bottom-up model. The broad community discussed this topic for five years > and provided the best direction it could, to take the discussion out from > under the community umbrella. In any event, no GNSO stakeholder group would > be precluded from sending a member to this small team, and whatever > Applicant Support program is recommended, the community will have the > opportunity to discuss it prior to adoption. > > 3. Nor is a standing 30-person Steering Committee likely to be an > economical or effective approach if asked to consider additional issues. > This steering committee likely would be populated by those interested in > the Applicant Support program and not have the necessary skill sets for, > or interest in, tackling different issues. Community members interested in > subsequent issues would likely be closed out of participating because the > committee would be populated by those interested in the Applicant Support > program. So, the 30-member committee, already demonstrated to be > inefficient for the purpose of sorting the Applicant Support issues, would > also be ineffectual on the subsequent issues. > > 4. This is likely to be an extended commitment on the part of our > depleted volunteer workforce. Cannot we, as managers of the policy process, > manage these important areas of policy / implementation administration, and > reserve volunteers? valuable time for substantive work? In the meantime, we > can launch this first-ever GGP effort, keep it narrow to make it efficient, > and learn from it. > > I?ve attached an alternative GGP Initiation Request. Amendments and > additional discussion are welcome > > Sincerely, > > Kurt > > > > > > > > On Jul 13, 2022, at 3:46 AM, philippe.fouquart--- via council < > council at gnso.icann.org> wrote: > > Dear Councilors, > > Please find attached the GNSO Guidance Process associated with the motion > circulated on Monday. > > This version is intended to incorporate comments made in The Hague, > notably on focusing on applicant support and the flexibility bw a steering > group and subteams. A couple of additional things that leadership would > like to draw your attention to in case you?d have an opinion: > > - the need for the GNSO Liaison to the ODP to be a (non voting) member (that?s > under 5.) > - the explicit acknowledgement that this group may deliver their > results after the conclusion of the ODP or even the Board?s vote. (under 7) > > > Thanks. > Regards, > Philippe > > > *From:* FOUQUART Philippe INNOV/NET > *Sent:* Monday, July 11, 2022 5:14 PM > *To:* council at gnso.icann.org > *Cc:* 'gnso-secs at icann.org' > *Subject:* Motion for the Initiation of the GNSO Guidance Process on > Applicant Support > > Dear Councilors, > > Following our discussion in The Hague, please find attached the Motion for > the Initiation of the GNSO Guidance Process on Applicant Support submitted > to the July 21st Council meeting. It will be updated with the link to the > GGP within a few days. > > 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. > > > _______________________________________________ > council mailing list > council at 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. > > > _______________________________________________ > council mailing list > council at 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. > > _______________________________________________ > NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From PolicyCalendar at icann.org Mon Jul 18 14:16:37 2022 From: PolicyCalendar at icann.org (ICANN Policy Calendar) Date: Mon, 18 Jul 2022 11:16:37 +0000 Subject: [NCSG-PC] 15-minute REMINDER: NCSG Policy Call | 18 July at 11:30 UTC Message-ID: <75c771d5aebb4387af049a9ac0365423@icann.org> Please join the NCSG Monthly Policy call on Monday, 18 July at 11:30 UTC. Additional time zone support here. Join Zoom Meeting: https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09 Meeting ID: 988 7818 9584 Passcode: i!y7.qx+11 WANT US TO CALL YOU? Please send dial-out request and apologies to brenda.brewer at icann.org. One tap mobile +16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose) +12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma) PHONE ONLY DETAILS: Find your local number: https://icann.zoom.us/u/ayKmeftWg Meeting ID: 988 7818 9584 Phone only Passcode: 7740925615 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2571 bytes Desc: not available URL: From bruna.mrtns at gmail.com Mon Jul 18 14:51:56 2022 From: bruna.mrtns at gmail.com (Bruna Martins dos Santos) Date: Mon, 18 Jul 2022 13:51:56 +0200 Subject: [NCSG-PC] 15-minute REMINDER: NCSG Policy Call | 18 July at 11:30 UTC In-Reply-To: <75c771d5aebb4387af049a9ac0365423@icann.org> References: <75c771d5aebb4387af049a9ac0365423@icann.org> Message-ID: Dear all, I would like to apologize for not being able to join today's call. Im currently at another conflicting meeting and will, therefore, follow the discussions once the meeting minutes and recordings are available. Best, Bruna On Mon, Jul 18, 2022 at 1:16 PM ICANN Policy Calendar < PolicyCalendar at icann.org> wrote: > *Please join the NCSG Monthly Policy call on Monday, 18 July at 11:30 UTC.* > Additional time zone support here > > . > > > > Join Zoom Meeting: *https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09 > * > > Meeting ID: 988 7818 9584 > > Passcode: i!y7.qx+11 > > > > *WANT US TO CALL YOU?* Please send dial-out request and apologies to *brenda.brewer at icann.org > .* > > > > One tap mobile > > +16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose) > > +12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma) > > PHONE ONLY DETAILS: > > Find your local number: https://icann.zoom.us/u/ayKmeftWg > > Meeting ID: 988 7818 9584 > > Phone only Passcode: 7740925615 > > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -- *Bruna Martins dos Santos * German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von Humboldt Foundation Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum Berlin f?r Sozialforschung (WZB) Member | Coaliz?o Direitos na Rede Chair | Non-Commercial Stakeholder Group at ICANN Co-Coordinator | Internet Governance Caucus Twitter: @boomartins // Skype: bruna.martinsantos *bruna.martinsdossantos at wzb.eu * and bruna.mrtns at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From brenda.brewer at icann.org Mon Jul 18 21:49:48 2022 From: brenda.brewer at icann.org (Brenda Brewer) Date: Mon, 18 Jul 2022 18:49:48 +0000 Subject: [NCSG-PC] NCSG Policy Call - attendees, replay, chat - 18 July 2022 Message-ID: <026FEA83-151A-4115-A427-4A8520F044D9@icann.org> Good day all, Please find attendees, replay, and chat details for the NCSG Monthly Policy call held Monday, 18 July at 11:30 UTC. The transcript will be sent upon completion. Thank you! Kind regards, Andrea and Brenda ATTENDEES: Members: Amin Hacha, Benjamin Akinmoyeje, Bukola Oronti, Caleb Ogundele, Cindyneia Cantanh?de, Daniel Charles, David Morar, Ephraim Percy Kenyanito, Emmanuel Vitus, Farell Folly, Juan Manuel Rojas, Julf Helsingius, Kathy Kleiman, Kenneth Herman, Manju Chen, Mubashir Sargana, Nthabiseng Pule, Ol?vi? Kouami, Rafik Dammak, Razoana Moslam, Rudi Daniel, Shah Rahman, Stephanie Perrin, Tomslin Samme-Nlar, Wisdom Donkor | Apologies: Bruna Martins dos Santos | ICANN org: Andrea Glandon, Brenda Brewer, Carlos Reyes ZOOM Replay Link: Here ZOOM Audio Link: Here ZOOM Chat Link: Here -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Thu Jul 21 14:55:06 2022 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Thu, 21 Jul 2022 21:55:06 +1000 Subject: [NCSG-PC] [DRAFT] Public Comment on Initial Report on Transfer Policy Phase 1(a) In-Reply-To: References: Message-ID: Dear PC, Here is the initial draft of the TP initial report drafted by Farzaneh for your review and comments please. https://docs.google.com/document/d/1En5i9132e2YlNbtRqSV7Inr4qRYq6tkSA5eouwGnBq8/edit?usp=sharing Deadline for submission is August 2, so if you could review before next Friday, that would be greatly appreciated. Warmly, Tomslin On Thu, 21 Jul 2022 at 18:04, farzaneh badii wrote: > Tomslin, > > The deadline is August 2. Here is a first draft: > https://docs.google.com/document/d/1En5i9132e2YlNbtRqSV7Inr4qRYq6tkSA5eouwGnBq8/edit?usp=sharing > > Best > Farzaneh > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From brenda.brewer at icann.org Tue Jul 26 19:53:17 2022 From: brenda.brewer at icann.org (Brenda Brewer) Date: Tue, 26 Jul 2022 16:53:17 +0000 Subject: [NCSG-PC] NCSG Policy Call - attendees, replay, chat - 18 July 2022 In-Reply-To: <026FEA83-151A-4115-A427-4A8520F044D9@icann.org> References: <026FEA83-151A-4115-A427-4A8520F044D9@icann.org> Message-ID: <89617995-B284-4C83-9B22-11047FFC2CA9@icann.org> Dear NCSG members, Please see attached the transcript for NCSG Monthly Policy call held Monday, 18 July at 11:30 UTC. Thank you. Kind regards, Andrea and Brenda From: Brenda Brewer Date: Monday, July 18, 2022 at 1:49 PM To: "NCSG-DISCUSS at LISTSERV.SYR.EDU" , "ncsg-pc at lists.ncsg.is" Cc: Andrea Glandon , Brenda Brewer Subject: NCSG Policy Call - attendees, replay, chat - 18 July 2022 Good day all, Please find attendees, replay, and chat details for the NCSG Monthly Policy call held Monday, 18 July at 11:30 UTC. The transcript will be sent upon completion. Thank you! Kind regards, Andrea and Brenda ATTENDEES: Members: Amin Hacha, Benjamin Akinmoyeje, Bukola Oronti, Caleb Ogundele, Cindyneia Cantanh?de, Daniel Charles, David Morar, Ephraim Percy Kenyanito, Emmanuel Vitus, Farell Folly, Juan Manuel Rojas, Julf Helsingius, Kathy Kleiman, Kenneth Herman, Manju Chen, Mubashir Sargana, Nthabiseng Pule, Ol?vi? Kouami, Rafik Dammak, Razoana Moslam, Rudi Daniel, Shah Rahman, Stephanie Perrin, Tomslin Samme-Nlar, Wisdom Donkor | Apologies: Bruna Martins dos Santos | ICANN org: Andrea Glandon, Brenda Brewer, Carlos Reyes ZOOM Replay Link: Here ZOOM Audio Link: Here ZOOM Chat Link: Here -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Transcript_NCSG Policy_18July2022.pdf Type: application/pdf Size: 267135 bytes Desc: Transcript_NCSG Policy_18July2022.pdf URL: