From stephanie at digitaldiscretion.ca  Thu Sep  1 16:44:44 2022
From: stephanie at digitaldiscretion.ca (Stephanie E Perrin)
Date: Thu, 1 Sep 2022 09:44:44 -0400
Subject: [NCSG-PC] Fwd: [NextGen-Alumni] Call for NextGen Mentors!
In-Reply-To: <CADAEEV0DpNkA6ByJqBLr26GFM2xmE4nmj6+5yga2_8_PciWTAw@mail.gmail.com>
References: <16729ABC-B51F-4D8B-BA11-BA594353B79E@icann.org>
 <61537153-6E12-4E37-9CC9-962EAFED0D0A@gmail.com>
 <CADAEEV0DpNkA6ByJqBLr26GFM2xmE4nmj6+5yga2_8_PciWTAw@mail.gmail.com>
Message-ID: <f567c244-4623-1cc3-5050-c72bb21271c3@digitaldiscretion.ca>

Did we define what we mean by "active member"?? I take it to mean active 
on pdps.? Perhaps I am wrong.? Nextgen mentors need to understand ICANN 
org and its constituent parts, policies, and procedures.? I am not a 
graduate of the nextgen program so perhaps those who graduate from that 
program know all they need to know, but I currently think that 
participation in the actual work of the org is a requirement.

I do not know this person so please this is not meant as a personal 
comment.? Just trying to clarify how we understand the task and the ask.

Stephanie Perrin


On 2022-08-30 7:40 a.m., Bruna Martins dos Santos wrote:
> Dear all,
>
> I dont?think the call for NextGen mentors went around our open lists, 
> but Bolutife is putting himself?up for the job. Therefore I was 
> wondering if anyone would be against us nominating him for this position.
>
> Best,
> Bruna
>
> ---------- Forwarded message ---------
> From: *Bolutife Adisa* <adisabolutifeo at gmail.com>
> Date: Thu, May 12, 2022 at 8:51 PM
> Subject: Fwd: [NextGen-Alumni] Call for NextGen Mentors!
> To: <bruna.mrtns at gmail.com>
>
>
> Hi Bruna,
>
> I am reaching out to express my interest in being nominated by NCSG 
> community for the NextGen mentor program.
>
> I am an alumni of the NextGen program having attended the ICANN65 as a 
> NextGen participant in 2019. I am also an active community member and 
> currently serve as Communication chair in NPOC where I represent 
> Digital Grassroots org.
>
> I am not sure what the process of selection would be, however, I am 
> certain that my participation will be of immense benefit to the 
> NextGen program.
>
> I?m available to answer any questions you might have.
>
> Best regards,
> Bolutife Adisa.
>
> Begin forwarded message:
>
>> *From:* Deborah Escalera via NextGen-Alumni <nextgen-alumni at icann.org>
>> *Date:* 12. May 2022 at 18:17:39 CEST
>> *To:* nextgen-alumni at icann.org
>> *Subject:* *[NextGen-Alumni] Call for NextGen Mentors!*
>> *Reply-To:* Deborah Escalera <deborah.escalera at icann.org>
>>
>> ?
>>
>> Please be advised that a call for Mentors for the NextGen at ICANN 
>> Program went out today to the community leadership (please see 
>> below). Nominees *MUST* be appointment by your community group. Those 
>> interested must be */_active community members_/*. Please NOTE: I 
>> cannot nominate you. Active previous NextGen Ambassadors are 
>> encouraged and eligible to apply.
>>
>> *NextGen at ICANN Mentor Program Nominations*The NextGen at ICANN Program 
>> seeks nominations for the 2022-2023 Mentor Program. This appointment 
>> will serve for ICANN75, ICANN76, and ICANN77.Nominations must be 
>> submitted no later than *Monday, 1 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 
>> <https://www.icann.org/en/system/files/files/nextgen-mentoring-guidelines-14jul20-en.pdf>.Interested 
>> community groups should select their respective volunteers and notify 
>> Deborah Escalera, deborah.escalera at icann.org 
>> <mailto:deborah.escalera at icann.org>.
>>
>> _______________________________________________
>> NextGen-Alumni mailing list
>> NextGen-Alumni at icann.org
>> https://mm.icann.org/mailman/listinfo/nextgen-alumni
>>
>> _______________________________________________
>> 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.
>
>
> -- 
> */Bruna Martins dos Santos
> /*
>
> German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander 
> von Humboldt Foundation <https://www.humboldt-foundation.de/>
>
> Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum 
> Berlin f?r Sozialforschung (WZB) <https://wzb.eu/en>
>
> Member | Coaliz?o Direitos na Rede <https://direitosnarede.org.br/>
> Chair?| Non-Commercial Stakeholder Group at ICANN 
> <https://gnso.icann.org/en/about/stakeholders-constituencies/ncsg>
> Co-Coordinator?| Internet Governance Caucus <https://igcaucus.org/>
>
> Twitter: @boomartins <https://twitter.com/boomartins>?// Skype: 
> bruna.martinsantos
> _bruna.martinsdossantos at wzb.eu_?and bruna.mrtns at gmail.com
>
> _______________________________________________
> 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: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20220901/5295e31e/attachment.htm>

From adisabolutifeo at gmail.com  Thu Sep  1 17:32:51 2022
From: adisabolutifeo at gmail.com (Bolutife Adisa)
Date: Thu, 1 Sep 2022 16:32:51 +0200
Subject: [NCSG-PC] Fwd: [NextGen-Alumni] Call for NextGen Mentors!
In-Reply-To: <f567c244-4623-1cc3-5050-c72bb21271c3@digitaldiscretion.ca>
References: <f567c244-4623-1cc3-5050-c72bb21271c3@digitaldiscretion.ca>
Message-ID: <BD20B3CF-8794-4557-A951-102ABC995858@gmail.com>

Hello all,

@Stephanie Thanks for chiming in on the topic and sharing your valid concerns. 

In this case, I believe you have rightly defined what active membership is or should be ?? need to understand ICANN org and its constituent parts, policies, and procedures?. 
Having participated in multiple ICANN meetings as a NextGen participant, and ICANN fellow and an EC member in NPOC, it is clear that I understand ICANN org?s structure, procedures, and policies and I?m capable of passing on the knowledge to newcomers. 

While I might not have the wealth of experience that other colleagues may have in pen-holding for policy development process, I am aware that the role in question is not a policy development role but a mentorship/support role for newcomers in the space (otherwise I would have easily stepped aside for more policy-experienced colleagues to step in). However, I consider myself qualified for this role based on the outlined criteria. 

Being a former NextGen participant as well as ICANN fellow is only just an added advantage, as it indicates prior understanding of the program and its structure, having been through it myself. 

I would be glad to provide response to any further questions or clarifications needed. 

Best,
- Bolutife. 


> On 1. Sep 2022, at 15:44, Stephanie E Perrin <stephanie at digitaldiscretion.ca> wrote:
> ?
> Did we define what we mean by "active member"?  I take it to mean active on pdps.  Perhaps I am wrong.  Nextgen mentors need to understand ICANN org and its constituent parts, policies, and procedures.  I am not a graduate of the nextgen program so perhaps those who graduate from that program know all they need to know, but I currently think that participation in the actual work of the org is a requirement.
> 
> I do not know this person so please this is not meant as a  personal comment.  Just trying to clarify how we understand the task and the ask.
> 
> Stephanie Perrin
> 
> 
> 
> On 2022-08-30 7:40 a.m., Bruna Martins dos Santos wrote:
>> Dear all, 
>> 
>> I dont think the call for NextGen mentors went around our open lists, but Bolutife is putting himself up for the job. Therefore I was wondering if anyone would be against us nominating him for this position. 
>> 
>> Best, 
>> Bruna 
>> 
>> ---------- Forwarded message ---------
>> From: Bolutife Adisa <adisabolutifeo at gmail.com>
>> Date: Thu, May 12, 2022 at 8:51 PM
>> Subject: Fwd: [NextGen-Alumni] Call for NextGen Mentors!
>> To: <bruna.mrtns at gmail.com>
>> 
>> 
>> Hi Bruna,
>> 
>> I am reaching out to express my interest in being nominated by NCSG community for the NextGen mentor program. 
>> 
>> I am an alumni of the NextGen program having attended the ICANN65 as a NextGen participant in 2019. I am also an active community member and currently serve as Communication chair in NPOC where I represent Digital Grassroots org. 
>> 
>> I am not sure what the process of selection would be, however, I am certain that my participation will be of immense benefit to the NextGen program. 
>> 
>> I?m available to answer any questions you might have. 
>> 
>> Best regards,
>> Bolutife Adisa. 
>> 
>> Begin forwarded message:
>> 
>>> From: Deborah Escalera via NextGen-Alumni <nextgen-alumni at icann.org>
>>> Date: 12. May 2022 at 18:17:39 CEST
>>> To: nextgen-alumni at icann.org
>>> Subject: [NextGen-Alumni] Call for NextGen Mentors!
>>> Reply-To: Deborah Escalera <deborah.escalera at icann.org>
>>> 
>>> ?
>>> Please be advised that a call for Mentors for the NextGen at ICANN Program went out today to the community leadership (please see below). Nominees MUST be appointment by your community group. Those interested must be active community members. Please NOTE: I cannot nominate you. Active previous NextGen Ambassadors are encouraged and eligible to apply.
>>> 
>>>  
>>> 
>>>  
>>> 
>>>  
>>> 
>>> NextGen at ICANN Mentor Program NominationsThe NextGen at ICANN Program seeks nominations for the 2022-2023 Mentor Program. This appointment will serve for ICANN75, ICANN76, and ICANN77.Nominations must be submitted no later than Monday, 1 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.Interested community groups should select their respective volunteers and notify Deborah Escalera, deborah.escalera at icann.org. 
>>> 
>>>  
>>> 
>>>  
>>> 
>>> _______________________________________________
>>> NextGen-Alumni mailing list
>>> NextGen-Alumni at icann.org
>>> https://mm.icann.org/mailman/listinfo/nextgen-alumni
>>> 
>>> _______________________________________________
>>> 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.
>> 
>> 
>> -- 
>> 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
>> 
>> 
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
> _______________________________________________
> 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: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20220901/dd513c0b/attachment.htm>

From bruna.mrtns at gmail.com  Thu Sep  1 18:10:27 2022
From: bruna.mrtns at gmail.com (Bruna Martins dos Santos)
Date: Thu, 1 Sep 2022 17:10:27 +0200
Subject: [NCSG-PC] Fwd: [NextGen-Alumni] Call for NextGen Mentors!
In-Reply-To: <BD20B3CF-8794-4557-A951-102ABC995858@gmail.com>
References: <f567c244-4623-1cc3-5050-c72bb21271c3@digitaldiscretion.ca>
 <BD20B3CF-8794-4557-A951-102ABC995858@gmail.com>
Message-ID: <CADAEEV1Knr=z8FPi4RXEtx9_Onxndm32KT=6_TU_G0sP=020Hg@mail.gmail.com>

Dear all,

So, im writing just to let you know that we had two candidates - Pascal
Bekono and Bolutife - and, given the lack of discussion here i ended up
suggesting both to Philippe, Sebastian and Tomslin. Also, given this was
not an internal NCSG process and mostly done at the level of GNSO, its kind
of a strange position due to the lack of discussions with the broader SO on
who will be our nominees (and id even say lack of information from GNSO
leadership too).

On the "active member" discussion, I understand the points raised by Steph.
I often come across candidacies of members who are only active within one
Constituency and never really show up to PC or membership meetings, so
thats a fair question or point to raise. And maybe a matter of attention to
upcoming candidates for such positions is to be able to have a good
relationship also with the SG given that being active at NCUC or NPOC
doesnt necessarily mean the SG.

Best,
Bruna

On Thu, Sep 1, 2022 at 4:32 PM Bolutife Adisa <adisabolutifeo at gmail.com>
wrote:

> Hello all,
>
> @Stephanie Thanks for chiming in on the topic and sharing your valid
> concerns.
>
> In this case, I believe you have rightly defined what active membership is
> or should be ?? need to understand ICANN org and its constituent parts,
> policies, and procedures?.
> Having participated in multiple ICANN meetings as a NextGen participant,
> and ICANN fellow and an EC member in NPOC, it is clear that I understand
> ICANN org?s structure, procedures, and policies and I?m capable of passing
> on the knowledge to newcomers.
>
> While I might not have the wealth of experience that other colleagues may
> have in pen-holding for policy development process, I am aware that the
> role in question is not a policy development role but a mentorship/support
> role for newcomers in the space (otherwise I would have easily stepped
> aside for more policy-experienced colleagues to step in). However, I
> consider myself qualified for this role based on the outlined criteria.
>
> Being a former NextGen participant as well as ICANN fellow is only just an
> added advantage, as it indicates prior understanding of the program and its
> structure, having been through it myself.
>
> I would be glad to provide response to any further questions or
> clarifications needed.
>
> Best,
> - Bolutife.
>
>
> On 1. Sep 2022, at 15:44, Stephanie E Perrin <
> stephanie at digitaldiscretion.ca> wrote:
>
> ?
>
> Did we define what we mean by "active member"?  I take it to mean active
> on pdps.  Perhaps I am wrong.  Nextgen mentors need to understand ICANN org
> and its constituent parts, policies, and procedures.  I am not a graduate
> of the nextgen program so perhaps those who graduate from that program know
> all they need to know, but I currently think that participation in the
> actual work of the org is a requirement.
>
> I do not know this person so please this is not meant as a  personal
> comment.  Just trying to clarify how we understand the task and the ask.
>
> Stephanie Perrin
>
>
> On 2022-08-30 7:40 a.m., Bruna Martins dos Santos wrote:
>
> Dear all,
>
> I dont think the call for NextGen mentors went around our open lists, but
> Bolutife is putting himself up for the job. Therefore I was wondering if
> anyone would be against us nominating him for this position.
>
> Best,
> Bruna
>
> ---------- Forwarded message ---------
> From: Bolutife Adisa <adisabolutifeo at gmail.com>
> Date: Thu, May 12, 2022 at 8:51 PM
> Subject: Fwd: [NextGen-Alumni] Call for NextGen Mentors!
> To: <bruna.mrtns at gmail.com>
>
>
> Hi Bruna,
>
> I am reaching out to express my interest in being nominated by NCSG
> community for the NextGen mentor program.
>
> I am an alumni of the NextGen program having attended the ICANN65 as a
> NextGen participant in 2019. I am also an active community member and
> currently serve as Communication chair in NPOC where I represent Digital
> Grassroots org.
>
> I am not sure what the process of selection would be, however, I am
> certain that my participation will be of immense benefit to the NextGen
> program.
>
> I?m available to answer any questions you might have.
>
> Best regards,
> Bolutife Adisa.
>
> Begin forwarded message:
>
> *From:* Deborah Escalera via NextGen-Alumni <nextgen-alumni at icann.org>
> *Date:* 12. May 2022 at 18:17:39 CEST
> *To:* nextgen-alumni at icann.org
> *Subject:* *[NextGen-Alumni] Call for NextGen Mentors!*
> *Reply-To:* Deborah Escalera <deborah.escalera at icann.org>
>
> ?
>
> Please be advised that a call for Mentors for the NextGen at ICANN Program
> went out today to the community leadership (please see below). Nominees
> *MUST* be appointment by your community group. Those interested must be *active
> community members*. Please NOTE: I cannot nominate you. Active previous
> NextGen Ambassadors are encouraged and eligible to apply.
>
>
>
>
>
>
>
> *NextGen at ICANN Mentor Program Nominations*The NextGen at ICANN Program seeks
> nominations for the 2022-2023 Mentor Program. This appointment will serve
> for ICANN75, ICANN76, and ICANN77.Nominations must be submitted no later
> than *Monday, 1 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
> <https://www.icann.org/en/system/files/files/nextgen-mentoring-guidelines-14jul20-en.pdf>.Interested
> community groups should select their respective volunteers and notify
> Deborah Escalera, deborah.escalera at icann.org.
>
>
>
>
> _______________________________________________
> NextGen-Alumni mailing list
> NextGen-Alumni at icann.org
> https://mm.icann.org/mailman/listinfo/nextgen-alumni
>
> _______________________________________________
> 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.
>
>
>
> --
>
> *Bruna Martins dos Santos  *
>
> German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von
> Humboldt Foundation <https://www.humboldt-foundation.de/>
>
> Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum Berlin
> f?r Sozialforschung (WZB) <https://wzb.eu/en>
>
> Member | Coaliz?o Direitos na Rede <https://direitosnarede.org.br/>
> Chair | Non-Commercial Stakeholder Group at ICANN
> <https://gnso.icann.org/en/about/stakeholders-constituencies/ncsg>
> Co-Coordinator | Internet Governance Caucus  <https://igcaucus.org/>
>
> Twitter: @boomartins <https://twitter.com/boomartins> // Skype:
> bruna.martinsantos
> *bruna.martinsdossantos at wzb.eu <bruna.martinsdossantos at wzb.eu>* and
> bruna.mrtns at gmail.com
>
> _______________________________________________
> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
> _______________________________________________
> 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 <https://www.humboldt-foundation.de/>

Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum Berlin
f?r Sozialforschung (WZB) <https://wzb.eu/en>

Member | Coaliz?o Direitos na Rede <https://direitosnarede.org.br/>
Chair | Non-Commercial Stakeholder Group at ICANN
<https://gnso.icann.org/en/about/stakeholders-constituencies/ncsg>
Co-Coordinator | Internet Governance Caucus  <https://igcaucus.org/>

Twitter: @boomartins <https://twitter.com/boomartins> // Skype:
bruna.martinsantos
*bruna.martinsdossantos at wzb.eu <bruna.martinsdossantos at wzb.eu>* and
bruna.mrtns at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20220901/325e2e15/attachment.htm>

From stephanie.perrin at mail.utoronto.ca  Thu Sep  1 18:48:51 2022
From: stephanie.perrin at mail.utoronto.ca (Stephanie E Perrin)
Date: Thu, 1 Sep 2022 11:48:51 -0400
Subject: [NCSG-PC] Fwd: [NextGen-Alumni] Call for NextGen Mentors!
In-Reply-To: <BD20B3CF-8794-4557-A951-102ABC995858@gmail.com>
References: <f567c244-4623-1cc3-5050-c72bb21271c3@digitaldiscretion.ca>
 <BD20B3CF-8794-4557-A951-102ABC995858@gmail.com>
Message-ID: <14d9bac9-ceea-5745-3d29-7e1bbbacfd49@mail.utoronto.ca>

Thanks for responding Bolutife! In the light of what Bruna was saying in 
terms of who was fielding the nominations (i.e.not at GNSO level) I 
think it is a reasonable question to shoot backto the Org.? Is this 
person meant to be sort of a student mentee (for which you appear to be 
very well qualified) or is it more of a traditional mentor 
role....someone who has experience in the actual work that is done in 
committees, for instance?? I think a bit of clarification would be great.

Cheers Stephanie

On 2022-09-01 10:32 a.m., Bolutife Adisa wrote:
>
> 	
> You don't often get email from adisabolutifeo at gmail.com. Learn why 
> this is important <https://aka.ms/LearnAboutSenderIdentification>
> 	
>
> Hello all,
>
> @Stephanie Thanks for chiming in on the topic and sharing your valid 
> concerns.
>
> In this case, I believe you have rightly defined what active 
> membership is or should be ?? need to understand ICANN org and its 
> constituent parts, policies, and procedures?.
> Having participated in multiple ICANN meetings as a NextGen 
> participant, and ICANN fellow and an EC member in NPOC, it is clear 
> that I understand ICANN org?s structure, procedures, and policies and 
> I?m capable of passing on the knowledge to newcomers.
>
> While I might not have the wealth of experience that other colleagues 
> may have in pen-holding for policy development process, I am aware 
> that the role in question is not a policy development role but a 
> mentorship/support role for newcomers in the space (otherwise I would 
> have easily stepped aside for more policy-experienced colleagues to 
> step in). However, I consider myself qualified for this role based on 
> the outlined criteria.
>
> Being a former NextGen participant as well as ICANN fellow is only 
> just an added advantage, as it indicates prior understanding of the 
> program and its structure, having been through it myself.
>
> I would be glad to provide response to any further questions or 
> clarifications needed.
>
> Best,
> - Bolutife.
>
>
>> On 1. Sep 2022, at 15:44, Stephanie E Perrin 
>> <stephanie at digitaldiscretion.ca> wrote:
>>
>> ?
>>
>> Did we define what we mean by "active member"?? I take it to mean 
>> active on pdps.? Perhaps I am wrong. Nextgen mentors need to 
>> understand ICANN org and its constituent parts, policies, and 
>> procedures.? I am not a graduate of the nextgen program so perhaps 
>> those who graduate from that program know all they need to know, but 
>> I currently think that participation in the actual work of the org is 
>> a requirement.
>>
>> I do not know this person so please this is not meant as a? personal 
>> comment.? Just trying to clarify how we understand the task and the ask.
>>
>> Stephanie Perrin
>>
>>
>> On 2022-08-30 7:40 a.m., Bruna Martins dos Santos wrote:
>>> Dear all,
>>>
>>> I dont?think the call for NextGen mentors went around our open 
>>> lists, but Bolutife is putting himself?up for the job. Therefore I 
>>> was wondering if anyone would be against us nominating him for this 
>>> position.
>>>
>>> Best,
>>> Bruna
>>>
>>> ---------- Forwarded message ---------
>>> From: *Bolutife Adisa* <adisabolutifeo at gmail.com>
>>> Date: Thu, May 12, 2022 at 8:51 PM
>>> Subject: Fwd: [NextGen-Alumni] Call for NextGen Mentors!
>>> To: <bruna.mrtns at gmail.com>
>>>
>>>
>>> Hi Bruna,
>>>
>>> I am reaching out to express my interest in being nominated by NCSG 
>>> community for the NextGen mentor program.
>>>
>>> I am an alumni of the NextGen program having attended the ICANN65 as 
>>> a NextGen participant in 2019. I am also an active community member 
>>> and currently serve as Communication chair in NPOC where I represent 
>>> Digital Grassroots org.
>>>
>>> I am not sure what the process of selection would be, however, I am 
>>> certain that my participation will be of immense benefit to the 
>>> NextGen program.
>>>
>>> I?m available to answer any questions you might have.
>>>
>>> Best regards,
>>> Bolutife Adisa.
>>>
>>> Begin forwarded message:
>>>
>>>> *From:* Deborah Escalera via NextGen-Alumni <nextgen-alumni at icann.org>
>>>> *Date:* 12. May 2022 at 18:17:39 CEST
>>>> *To:* nextgen-alumni at icann.org
>>>> *Subject:* *[NextGen-Alumni] Call for NextGen Mentors!*
>>>> *Reply-To:* Deborah Escalera <deborah.escalera at icann.org>
>>>>
>>>> ?
>>>>
>>>> Please be advised that a call for Mentors for the NextGen at ICANN 
>>>> Program went out today to the community leadership (please see 
>>>> below). Nominees *MUST* be appointment by your community group. 
>>>> Those interested must be */_active community members_/*. Please 
>>>> NOTE: I cannot nominate you. Active previous NextGen Ambassadors 
>>>> are encouraged and eligible to apply.
>>>>
>>>> *NextGen at ICANN Mentor Program Nominations*The NextGen at ICANN Program 
>>>> seeks nominations for the 2022-2023 Mentor Program. This 
>>>> appointment will serve for ICANN75, ICANN76, and 
>>>> ICANN77.Nominations must be submitted no later than *Monday, 1 
>>>> 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 
>>>> <https://www.icann.org/en/system/files/files/nextgen-mentoring-guidelines-14jul20-en.pdf>.Interested 
>>>> community groups should select their respective volunteers and 
>>>> notify Deborah Escalera, deborah.escalera at icann.org 
>>>> <mailto:deborah.escalera at icann.org>.
>>>>
>>>> _______________________________________________
>>>> NextGen-Alumni mailing list
>>>> NextGen-Alumni at icann.org
>>>> https://mm.icann.org/mailman/listinfo/nextgen-alumni
>>>>
>>>> _______________________________________________
>>>> 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.
>>>
>>>
>>> -- 
>>> */Bruna Martins dos Santos
>>> /*
>>>
>>> German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | 
>>> Alexander von Humboldt Foundation <https://www.humboldt-foundation.de/>
>>>
>>> Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum 
>>> Berlin f?r Sozialforschung (WZB) <https://wzb.eu/en>
>>>
>>> Member | Coaliz?o Direitos na Rede <https://direitosnarede.org.br/>
>>> Chair?| Non-Commercial Stakeholder Group at ICANN 
>>> <https://gnso.icann.org/en/about/stakeholders-constituencies/ncsg>
>>> Co-Coordinator?| Internet Governance Caucus <https://igcaucus.org/>
>>>
>>> Twitter: @boomartins <https://twitter.com/boomartins>?// Skype: 
>>> bruna.martinsantos
>>> _bruna.martinsdossantos at wzb.eu_?and bruna.mrtns at gmail.com
>>>
>>> _______________________________________________
>>> NCSG-PC mailing list
>>> NCSG-PC at lists.ncsg.is
>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
> _______________________________________________
> 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: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20220901/9b81f642/attachment.htm>

From mesumbeslin at gmail.com  Sat Sep  3 15:19:35 2022
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Sat, 3 Sep 2022 22:19:35 +1000
Subject: [NCSG-PC] Nominations received PIR Advisory Council Members
Message-ID: <CAM8DdeUHNPTzUAqJHtFchHV8vmk9VNJjO9A=AuwrTgQyRqY0Yw@mail.gmail.com>

Hi team,

As discussed, here are the names of those who've self nominated so far:


   1. Hago Dafalla
   2. Remmy Nweke
   3. Poncelet O. Ileleji
   4. Bukola Oronti
   5. Caleb Ogundele

The criteria requested again are as follows:

   1. Either presently, or in the past, served in a leadership position
   within the NCSG or an NCSG constituency;
   2. Contributed and initiated meaningful discussion on the NCUC, NPOC,
   and/or NCSG mailing lists; and
   3. Demonstrated knowledge of, or interest in the work of, the Public
   Interest Registry, and is willing to be an active participant in Public
   Interest Registry discussions and debates.


Warmly,
Tomslin
@LinkedIn: https://www.linkedin.com/in/tomslin/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20220903/45c3ccbd/attachment.htm>

From mesumbeslin at gmail.com  Tue Sep  6 15:41:20 2022
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Tue, 6 Sep 2022 22:41:20 +1000
Subject: [NCSG-PC] Fwd: [gnso-chairs] GNSO/GAC dialogue on closed generics:
 selection of GNSO participants
In-Reply-To: <23150_1662120078_6311F08E_23150_224_1_fa943370c01643e3b2bc7375fc86e561@orange.com>
References: <23150_1662120078_6311F08E_23150_224_1_fa943370c01643e3b2bc7375fc86e561@orange.com>
Message-ID: <CAM8DdeX1py8C7wf+Wya4_99yCesi=bekspuRCMB+aL_Uz7yzvw@mail.gmail.com>

FYI, PC.

I am still waiting on guidance from Bruna but I just wanted to bring to
your attention this statement in the meantime " *This group would ideally
have a first informal meeting during ICANN 75, so we would appreciate if
you would let us know the name of your representative ideally by September
19th*."
It means we have only 2 weeks to name a representative for this. I don't
think it'll be a problem since Kathy Kleinman had indicated interest
already and was granted funding to KL based on that interest but I thought
I'd flag the urgency to the whole committee.

Warmly,
Tomslin
@LinkedIn: https://www.linkedin.com/in/tomslin/


---------- Forwarded message ---------
From: philippe.fouquart--- via Gnso-chairs <gnso-chairs at icann.org>
Date: Fri, 2 Sept 2022 at 22:01
Subject: [gnso-chairs] GNSO/GAC dialogue on closed generics: selection of
GNSO participants
To: mason.cole at appdetex.com <mason.cole at appdetex.com>,
wolf-ulrich.knoben at t-online.de <wolf-ulrich.knoben at t-online.de>,
lschulman at inta.org <lschulman at inta.org>, bruna.mrtns at gmail.com <
bruna.mrtns at gmail.com>, plommer at gmail.com <plommer at gmail.com>,
benakin at gmail.com <benakin at gmail.com>, aheineman at godaddy.com <
aheineman at godaddy.com>, sdemetriou at verisign.com <sdemetriou at verisign.com>,
chair at rysg.info <chair at rysg.info>, secretariat at rysg.info <
secretariat at rysg.info>, secretariat at icannregistrars.org <
secretariat at icannregistrars.org>
Cc: gnso-secs at icann.org <gnso-secs at icann.org>, gnso-chairs at icann.org <
gnso-chairs at icann.org>, council at gnso icann. org <council at gnso.icann.org>


Dear SG/C leaders,



Hope this email finds you all well.



As you know, following an invitation from the Board, the GNSO and the GAC
will enter into a dialogue to ?formulate a workable framework to identify
and handle closed generic applications for the immediate next round of new
gTLDs?, and in this dialogue we will be joined by ALAC.



Council leadership would like to invite each Stakeholder Group to select a
representative for this dialogue. This group is would ideally have a first
informal meeting during ICANN 75, so we would appreciate if you would let
us know the name of your representative ideally by September 19th.



The attached document provides the guidance for this appointment.



I would finally like to draw your attention to the spirit of involvement in
this effort:

   - the framework discussion will focus on options other than the two
   endpoint positions (i.e. no closed generics at all; closed generics without
   restrictions) as per the Board?s Proposed Parameters for Dialogue
   - the participants will "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.? (Council
   small team report)



Looking forward to hearing from you, and wishing you all safe travels to KL.



Best regards,

Philippe



Board/GNSO correspondence:

   - 6 Mar 2022 Letter from Maarten Botterman to Manal Ismail and Philippe
   Fouquart
   <https://www.icann.org/en/system/files/correspondence/botterman-to-ismail-fouquart-06mar22-en.pdf>
?
   including the framing paper
   - 27 April 2022 Letter from Philippe Fouquart to Maarten Botterman
   <https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-27apr22-en.pdf>
   - 19 May 2022 Letter from Maarten Botterman to Philippe Fouquart
   <https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-19may22-en.pdf>

   - 29 Jun 2022 Letter from Philippe Fouquart to Maarten Botterman and
   Manal Ismail
   <https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-ismail-29jun22-en.pdf>

   - 25 Jul 2022 Letter from Maarten Botterman to Philippe Fouquart and
   Manal Ismail
   <https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-ismail-25jul22-en.pdf>


Council small team report:
https://gnso.icann.org/sites/default/files/policy/2022/draft/draft-closed-generics-small-team-report-24jun22-en.pdf



_________________________________________________________________________________________________________________________

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.

_______________________________________________
Gnso-chairs mailing list
Gnso-chairs at icann.org
https://mm.icann.org/mailman/listinfo/gnso-chairs
_______________________________________________
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: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20220906/d866b645/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Guidance to SGs - Selection of GNSO Participants .pdf
Type: application/pdf
Size: 62922 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20220906/d866b645/attachment.pdf>

From mesumbeslin at gmail.com  Wed Sep  7 01:07:05 2022
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Wed, 7 Sep 2022 08:07:05 +1000
Subject: [NCSG-PC] Call for Volunteer: GNSO Guidance Process (GGP)
 Initiation Request for Applicant Support
Message-ID: <CAM8DdeU6wigpQ8kteetcD_ndn+x+AN=AH1YFUaPo3+Pecwk4zQ@mail.gmail.com>

Dear NCSG,

During its meeting on 25 August 2022, the GNSO Council approved the GNSO
Guidance Process (GGP) Initiation Request
<https://gnso.icann.org/sites/default/files/policy/2022/draft/draft-subpro-ggp-initiation-request-clean-24aug22-en.pdf>
to perform work on Applicant Support, a topic of interest to NCSG. Each SG
has been invited to identify *1 Representative to join this Working Group *.

Here is the criteria that the GNSO Council considers to be important for
this GGP:
*Organizations are encouraged to appoint individuals with skills, knowledge
and experience pertinent to forming an effective Applicant Support Program.
Council will provide guidance on the aggregated skill set that is needed
for the group (for example: grant and reviewing, regional DNS
participation, DNS marketplace economics, cost-benefit analyses, TLD
operations, DNS cyber-security, and TLD investment).*

If you meet the above recommended criteria, please email to me your
expression of interest and copy Andrea (andrea.glandon at icann.or),
indicating how you meet the criteria above *no later than Friday 16
September* to give the Policy Committee 2 weeks to review and select.

Members should also note that in addition to the representative we'll
appoint, the GGP permits Observers to the process. Observers are anyone
interested in the GGP, who are provided with read-only access to the
mailing list and are not invited to attend meetings. Those interested to be
an observer should directly contact the GNSO Secretariat at
gnso-secs at icann.org to sign up.

Warmly,
Tomslin
@LinkedIn: https://www.linkedin.com/in/tomslin/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20220907/dd8f4826/attachment.htm>

From Kathy at KathyKleiman.com  Wed Sep  7 17:01:43 2022
From: Kathy at KathyKleiman.com (Kathy Kleiman)
Date: Wed, 7 Sep 2022 10:01:43 -0400
Subject: [NCSG-PC] Fwd: [gnso-chairs] GNSO/GAC dialogue on closed
 generics: selection of GNSO participants
In-Reply-To: <CAM8DdeX1py8C7wf+Wya4_99yCesi=bekspuRCMB+aL_Uz7yzvw@mail.gmail.com>
References: <23150_1662120078_6311F08E_23150_224_1_fa943370c01643e3b2bc7375fc86e561@orange.com>
 <CAM8DdeX1py8C7wf+Wya4_99yCesi=bekspuRCMB+aL_Uz7yzvw@mail.gmail.com>
Message-ID: <3cb39725-0fb1-877c-1f6b-f1433f323de0@KathyKleiman.com>

Hi Tomslin and All,

I would like to recommend that I be appointed with George Sadowsky as an 
unofficial alternate. George as you know as an ICANN Board member for 
many years. But few know that before that he was a founding member of 
NCUC (NCSG would not be created for about decade after).? In 1999, 
George was with New York University as IT director and joined us in 
founding NCUC and attending early meetings. We were his initial link to 
ICANN!

He has now applied to join NCSG.? Some Board members leave ICANN 
forever, but those who remain, tend to go back to the groups they came 
from. I hope we will approve his membership. And then I hope we can 
allow him to work with me on the Closed Generics issues. He is an expert 
on this issue from his time on the Board and knows how difficult and 
complicated it is.? He helped make sure we heard from noncommercial 
organizations around the world before passing the first ban on Closed 
Generics. Later, when the Subsequent Procedures Working Group was 
looking closely at this issue, George (at my invitation) joined the 
Working Group to again share the complexities and potential problems of 
Closed Generics from his perspective (which include his more recent 
experience with many United Nations organizations).

While technically the job is supposed to be for one person, it is too 
big for one volunteer (note: some attorneys will be paid by their 
clients and law firms to participate fully in this new group and there 
is a reason for that). ALAC plans to appoint a primary person and a 
backup person if the primary person cannot attend a meeting or 
discussion.? Since I will be on book tour with my new book about the 
ENIAC Programmers, */Proving Ground, /*I think it would be good idea for 
us to have a similar arrangement. We don't want to miss a single Closed 
Generic meeting!

Best and tx,

Kathy

On 9/6/2022 8:41 AM, Tomslin Samme-Nlar wrote:
> FYI, PC.
>
> I am still waiting on guidance from Bruna but I just wanted to bring 
> to your attention this statement in the meantime " /*This group would 
> ideally have a first informal meeting during ICANN 75, so we would 
> appreciate if you would let us know the name of your representative 
> ideally by September 19^th */."
> It means we have only 2 weeks to name a representative for this. I 
> don't think it'll be a problem since Kathy Kleinman had indicated 
> interest already and was granted funding to KL based on that interest 
> but I thought I'd flag the urgency to the whole committee.
>
> Warmly,
> Tomslin
> @LinkedIn: https://www.linkedin.com/in/tomslin/
>
>
> ---------- Forwarded message ---------
> From: *philippe.fouquart--- via Gnso-chairs* <gnso-chairs at icann.org>
> Date: Fri, 2 Sept 2022 at 22:01
> Subject: [gnso-chairs] GNSO/GAC dialogue on closed generics: selection 
> of GNSO participants
> To: mason.cole at appdetex.com <mason.cole at appdetex.com>, 
> wolf-ulrich.knoben at t-online.de <wolf-ulrich.knoben at t-online.de>, 
> lschulman at inta.org <lschulman at inta.org>, bruna.mrtns at gmail.com 
> <bruna.mrtns at gmail.com>, plommer at gmail.com <plommer at gmail.com>, 
> benakin at gmail.com <benakin at gmail.com>, aheineman at godaddy.com 
> <aheineman at godaddy.com>, sdemetriou at verisign.com 
> <sdemetriou at verisign.com>, chair at rysg.info <chair at rysg.info>, 
> secretariat at rysg.info <secretariat at rysg.info>, 
> secretariat at icannregistrars.org <secretariat at icannregistrars.org>
> Cc: gnso-secs at icann.org <gnso-secs at icann.org>, gnso-chairs at icann.org 
> <gnso-chairs at icann.org>, council at gnso icann. org <council at gnso.icann.org>
>
>
> Dear SG/C leaders,
>
> Hope this email finds you all well.
>
> As you know, following an invitation from the Board, the GNSO and the 
> GAC will enter into a dialogue to ?formulate a workable framework to 
> identify and handle closed generic applications for the immediate next 
> round of new gTLDs?, and in this dialogue we will be joined by ALAC.
>
> Council leadership would like to invite each Stakeholder Group to 
> select a representative for this dialogue. This group is would ideally 
> have a first informal meeting during ICANN 75, so we would appreciate 
> if you would let us know the name of your representative ideally by 
> September 19^th .
>
> The attached document provides the guidance for this appointment.
>
> I would finally like to draw your attention to the spirit of 
> involvement in this effort:
>
>   * the framework discussion will focus on options other than the two
>     endpoint positions (i.e. no closed generics at all; closed
>     generics without restrictions) as per the Board?s Proposed
>     Parameters for Dialogue
>   * the participants will "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.? (Council small team
>     report)
>
> Looking forward to hearing from you, and wishing you all safe travels 
> to KL.
>
> Best regards,
>
> Philippe
>
> Board/GNSO correspondence:
>
>   * 6 Mar 2022 Letter from Maarten Botterman to Manal Ismail and
>     Philippe Fouquart
>     <https://www.icann.org/en/system/files/correspondence/botterman-to-ismail-fouquart-06mar22-en.pdf>??
>     including the framing paper
>   * 27 April 2022 Letter from Philippe Fouquart to Maarten Botterman
>     <https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-27apr22-en.pdf>
>   * 19 May 2022 Letter from Maarten Botterman to Philippe Fouquart
>     <https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-19may22-en.pdf>
>   * 29 Jun 2022 Letter from Philippe Fouquart to Maarten Botterman and
>     Manal Ismail
>     <https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-ismail-29jun22-en.pdf>
>   * 25 Jul 2022 Letter from Maarten Botterman to Philippe Fouquart and
>     Manal Ismail
>     <https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-ismail-25jul22-en.pdf>
>
> Council small team report: 
> https://gnso.icann.org/sites/default/files/policy/2022/draft/draft-closed-generics-small-team-report-24jun22-en.pdf 
>
>
> _________________________________________________________________________________________________________________________
>
> 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.
> _______________________________________________
> Gnso-chairs mailing list
> Gnso-chairs at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-chairs
> _______________________________________________
> 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: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20220907/9af8216e/attachment.htm>

From mesumbeslin at gmail.com  Wed Sep  7 23:54:25 2022
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Thu, 8 Sep 2022 06:54:25 +1000
Subject: [NCSG-PC] Fwd: [gnso-chairs] GNSO/GAC dialogue on closed
 generics: selection of GNSO participants
In-Reply-To: <3cb39725-0fb1-877c-1f6b-f1433f323de0@KathyKleiman.com>
References: <23150_1662120078_6311F08E_23150_224_1_fa943370c01643e3b2bc7375fc86e561@orange.com>
 <CAM8DdeX1py8C7wf+Wya4_99yCesi=bekspuRCMB+aL_Uz7yzvw@mail.gmail.com>
 <3cb39725-0fb1-877c-1f6b-f1433f323de0@KathyKleiman.com>
Message-ID: <CAM8DdeXjXp0mOUR-mumSt9OgkGCUCHx6oXt3naumsKN922HTPA@mail.gmail.com>

Hi Kathy,

Thanks for volunteering. Really appreciate it because with the short window
and skills required,  it would have been very difficult to get a volunteer.
So, thank you!

Regarding your recommendation that we appoint an official alternate, I am
afraid that is not possible as stipulated on the candidate guidance
document I attached to my previous email. And more we are now also past the
negotiation phase in the Council. The guidance document is now the rule
book for appointing members. What we could do is to pull you out as member
in the event that you can't attend and appoint George instead.

Please let us know and apologies that Manju and I were unable to secure an
official alternate for NCSG during the drafting and discussion of the text.

Warmly,
Tomslin

On Thu, 8 Sept 2022, 00:01 Kathy Kleiman, <Kathy at kathykleiman.com> wrote:

> Hi Tomslin and All,
>
> I would like to recommend that I be appointed with George Sadowsky as an
> unofficial alternate. George as you know as an ICANN Board member for many
> years. But few know that before that he was a founding member of NCUC (NCSG
> would not be created for about decade after).  In 1999, George was with New
> York University as IT director and joined us in founding NCUC and attending
> early meetings. We were his initial link to ICANN!
>
> He has now applied to join NCSG.  Some Board members leave ICANN forever,
> but those who remain, tend to go back to the groups they came from. I hope
> we will approve his membership. And then I hope we can allow him to work
> with me on the Closed Generics issues. He is an expert on this issue from
> his time on the Board and knows how difficult and complicated it is.  He
> helped make sure we heard from noncommercial organizations around the world
> before passing the first ban on Closed Generics. Later, when the Subsequent
> Procedures Working Group was looking closely at this issue, George (at my
> invitation) joined the Working Group to again share the complexities and
> potential problems of Closed Generics from his perspective (which include
> his more recent experience with many United Nations organizations).
>
> While technically the job is supposed to be for one person, it is too big
> for one volunteer (note: some attorneys will be paid by their clients and
> law firms to participate fully in this new group and there is a reason for
> that). ALAC plans to appoint a primary person and a backup person if the
> primary person cannot attend a meeting or discussion.  Since I will be on
> book tour with my new book about the ENIAC Programmers, *Proving Ground, *I
> think it would be good idea for us to have a similar arrangement. We don't
> want to miss a single Closed Generic meeting!
>
> Best and tx,
>
> Kathy
> On 9/6/2022 8:41 AM, Tomslin Samme-Nlar wrote:
>
> FYI, PC.
>
> I am still waiting on guidance from Bruna but I just wanted to bring to
> your attention this statement in the meantime " *This group would ideally
> have a first informal meeting during ICANN 75, so we would appreciate if
> you would let us know the name of your representative ideally by September
> 19th*."
> It means we have only 2 weeks to name a representative for this. I don't
> think it'll be a problem since Kathy Kleinman had indicated interest
> already and was granted funding to KL based on that interest but I thought
> I'd flag the urgency to the whole committee.
>
> Warmly,
> Tomslin
> @LinkedIn: https://www.linkedin.com/in/tomslin/
>
>
> ---------- Forwarded message ---------
> From: philippe.fouquart--- via Gnso-chairs <gnso-chairs at icann.org>
> Date: Fri, 2 Sept 2022 at 22:01
> Subject: [gnso-chairs] GNSO/GAC dialogue on closed generics: selection of
> GNSO participants
> To: mason.cole at appdetex.com <mason.cole at appdetex.com>,
> wolf-ulrich.knoben at t-online.de <wolf-ulrich.knoben at t-online.de>,
> lschulman at inta.org <lschulman at inta.org>, bruna.mrtns at gmail.com <
> bruna.mrtns at gmail.com>, plommer at gmail.com <plommer at gmail.com>,
> benakin at gmail.com <benakin at gmail.com>, aheineman at godaddy.com <
> aheineman at godaddy.com>, sdemetriou at verisign.com <sdemetriou at verisign.com>,
> chair at rysg.info <chair at rysg.info>, secretariat at rysg.info <
> secretariat at rysg.info>, secretariat at icannregistrars.org <
> secretariat at icannregistrars.org>
> Cc: gnso-secs at icann.org <gnso-secs at icann.org>, gnso-chairs at icann.org <
> gnso-chairs at icann.org>, council at gnso icann. org <council at gnso.icann.org>
>
>
> Dear SG/C leaders,
>
>
>
> Hope this email finds you all well.
>
>
>
> As you know, following an invitation from the Board, the GNSO and the GAC
> will enter into a dialogue to ?formulate a workable framework to identify
> and handle closed generic applications for the immediate next round of new
> gTLDs?, and in this dialogue we will be joined by ALAC.
>
>
>
> Council leadership would like to invite each Stakeholder Group to select a
> representative for this dialogue. This group is would ideally have a first
> informal meeting during ICANN 75, so we would appreciate if you would let
> us know the name of your representative ideally by September 19th.
>
>
>
> The attached document provides the guidance for this appointment.
>
>
>
> I would finally like to draw your attention to the spirit of involvement
> in this effort:
>
>    - the framework discussion will focus on options other than the two
>    endpoint positions (i.e. no closed generics at all; closed generics without
>    restrictions) as per the Board?s Proposed Parameters for Dialogue
>    - the participants will "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.? (Council
>    small team report)
>
>
>
> Looking forward to hearing from you, and wishing you all safe travels to
> KL.
>
>
>
> Best regards,
>
> Philippe
>
>
>
> Board/GNSO correspondence:
>
>    - 6 Mar 2022 Letter from Maarten Botterman to Manal Ismail and
>    Philippe Fouquart
>    <https://www.icann.org/en/system/files/correspondence/botterman-to-ismail-fouquart-06mar22-en.pdf> ?
>    including the framing paper
>    - 27 April 2022 Letter from Philippe Fouquart to Maarten Botterman
>    <https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-27apr22-en.pdf>
>    - 19 May 2022 Letter from Maarten Botterman to Philippe Fouquart
>    <https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-19may22-en.pdf>
>
>    - 29 Jun 2022 Letter from Philippe Fouquart to Maarten Botterman and
>    Manal Ismail
>    <https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-ismail-29jun22-en.pdf>
>
>    - 25 Jul 2022 Letter from Maarten Botterman to Philippe Fouquart and
>    Manal Ismail
>    <https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-ismail-25jul22-en.pdf>
>
>
> Council small team report:
> https://gnso.icann.org/sites/default/files/policy/2022/draft/draft-closed-generics-small-team-report-24jun22-en.pdf
>
>
>
> _________________________________________________________________________________________________________________________
>
> 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.
>
> _______________________________________________
> Gnso-chairs mailing list
> Gnso-chairs at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-chairs
> _______________________________________________
> 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
>
> _______________________________________________
> 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: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20220908/764f964e/attachment.htm>

From bruna.mrtns at gmail.com  Thu Sep  8 19:19:20 2022
From: bruna.mrtns at gmail.com (Bruna Martins dos Santos)
Date: Thu, 8 Sep 2022 18:19:20 +0200
Subject: [NCSG-PC] Fwd: [gnso-chairs] GNSO/GAC dialogue on closed
 generics: selection of GNSO participants
In-Reply-To: <CAM8DdeXjXp0mOUR-mumSt9OgkGCUCHx6oXt3naumsKN922HTPA@mail.gmail.com>
References: <23150_1662120078_6311F08E_23150_224_1_fa943370c01643e3b2bc7375fc86e561@orange.com>
 <CAM8DdeX1py8C7wf+Wya4_99yCesi=bekspuRCMB+aL_Uz7yzvw@mail.gmail.com>
 <3cb39725-0fb1-877c-1f6b-f1433f323de0@KathyKleiman.com>
 <CAM8DdeXjXp0mOUR-mumSt9OgkGCUCHx6oXt3naumsKN922HTPA@mail.gmail.com>
Message-ID: <CADAEEV0wY-j0K_GH_Cp3waaO+c-AANNTrPA0QN5jduY2XTA2vA@mail.gmail.com>

Hello all,

Jumping in here just to ask whether we know about the final date for the
meeting at ICANN75 if theres one. I think Kathy wont be there for the full
meeting, right @Kathy Kleiman <kathy at dnrc.tech> ?

best,
B

On Wed, Sep 7, 2022 at 10:54 PM Tomslin Samme-Nlar <mesumbeslin at gmail.com>
wrote:

> Hi Kathy,
>
> Thanks for volunteering. Really appreciate it because with the short
> window and skills required,  it would have been very difficult to get a
> volunteer. So, thank you!
>
> Regarding your recommendation that we appoint an official alternate, I am
> afraid that is not possible as stipulated on the candidate guidance
> document I attached to my previous email. And more we are now also past the
> negotiation phase in the Council. The guidance document is now the rule
> book for appointing members. What we could do is to pull you out as member
> in the event that you can't attend and appoint George instead.
>
> Please let us know and apologies that Manju and I were unable to secure an
> official alternate for NCSG during the drafting and discussion of the text.
>
> Warmly,
> Tomslin
>
> On Thu, 8 Sept 2022, 00:01 Kathy Kleiman, <Kathy at kathykleiman.com> wrote:
>
>> Hi Tomslin and All,
>>
>> I would like to recommend that I be appointed with George Sadowsky as an
>> unofficial alternate. George as you know as an ICANN Board member for many
>> years. But few know that before that he was a founding member of NCUC (NCSG
>> would not be created for about decade after).  In 1999, George was with New
>> York University as IT director and joined us in founding NCUC and attending
>> early meetings. We were his initial link to ICANN!
>>
>> He has now applied to join NCSG.  Some Board members leave ICANN forever,
>> but those who remain, tend to go back to the groups they came from. I hope
>> we will approve his membership. And then I hope we can allow him to work
>> with me on the Closed Generics issues. He is an expert on this issue from
>> his time on the Board and knows how difficult and complicated it is.  He
>> helped make sure we heard from noncommercial organizations around the world
>> before passing the first ban on Closed Generics. Later, when the Subsequent
>> Procedures Working Group was looking closely at this issue, George (at my
>> invitation) joined the Working Group to again share the complexities and
>> potential problems of Closed Generics from his perspective (which include
>> his more recent experience with many United Nations organizations).
>>
>> While technically the job is supposed to be for one person, it is too big
>> for one volunteer (note: some attorneys will be paid by their clients and
>> law firms to participate fully in this new group and there is a reason for
>> that). ALAC plans to appoint a primary person and a backup person if the
>> primary person cannot attend a meeting or discussion.  Since I will be on
>> book tour with my new book about the ENIAC Programmers, *Proving Ground,
>> *I think it would be good idea for us to have a similar arrangement. We
>> don't want to miss a single Closed Generic meeting!
>>
>> Best and tx,
>>
>> Kathy
>> On 9/6/2022 8:41 AM, Tomslin Samme-Nlar wrote:
>>
>> FYI, PC.
>>
>> I am still waiting on guidance from Bruna but I just wanted to bring to
>> your attention this statement in the meantime " *This group would
>> ideally have a first informal meeting during ICANN 75, so we would
>> appreciate if you would let us know the name of your representative ideally
>> by September 19th*."
>> It means we have only 2 weeks to name a representative for this. I don't
>> think it'll be a problem since Kathy Kleinman had indicated interest
>> already and was granted funding to KL based on that interest but I thought
>> I'd flag the urgency to the whole committee.
>>
>> Warmly,
>> Tomslin
>> @LinkedIn: https://www.linkedin.com/in/tomslin/
>>
>>
>> ---------- Forwarded message ---------
>> From: philippe.fouquart--- via Gnso-chairs <gnso-chairs at icann.org>
>> Date: Fri, 2 Sept 2022 at 22:01
>> Subject: [gnso-chairs] GNSO/GAC dialogue on closed generics: selection of
>> GNSO participants
>> To: mason.cole at appdetex.com <mason.cole at appdetex.com>,
>> wolf-ulrich.knoben at t-online.de <wolf-ulrich.knoben at t-online.de>,
>> lschulman at inta.org <lschulman at inta.org>, bruna.mrtns at gmail.com <
>> bruna.mrtns at gmail.com>, plommer at gmail.com <plommer at gmail.com>,
>> benakin at gmail.com <benakin at gmail.com>, aheineman at godaddy.com <
>> aheineman at godaddy.com>, sdemetriou at verisign.com <sdemetriou at verisign.com>,
>> chair at rysg.info <chair at rysg.info>, secretariat at rysg.info <
>> secretariat at rysg.info>, secretariat at icannregistrars.org <
>> secretariat at icannregistrars.org>
>> Cc: gnso-secs at icann.org <gnso-secs at icann.org>, gnso-chairs at icann.org <
>> gnso-chairs at icann.org>, council at gnso icann. org <council at gnso.icann.org>
>>
>>
>> Dear SG/C leaders,
>>
>>
>>
>> Hope this email finds you all well.
>>
>>
>>
>> As you know, following an invitation from the Board, the GNSO and the GAC
>> will enter into a dialogue to ?formulate a workable framework to identify
>> and handle closed generic applications for the immediate next round of new
>> gTLDs?, and in this dialogue we will be joined by ALAC.
>>
>>
>>
>> Council leadership would like to invite each Stakeholder Group to select
>> a representative for this dialogue. This group is would ideally have a
>> first informal meeting during ICANN 75, so we would appreciate if you would
>> let us know the name of your representative ideally by September 19th.
>>
>>
>>
>> The attached document provides the guidance for this appointment.
>>
>>
>>
>> I would finally like to draw your attention to the spirit of involvement
>> in this effort:
>>
>>    - the framework discussion will focus on options other than the two
>>    endpoint positions (i.e. no closed generics at all; closed generics without
>>    restrictions) as per the Board?s Proposed Parameters for Dialogue
>>    - the participants will "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.? (Council
>>    small team report)
>>
>>
>>
>> Looking forward to hearing from you, and wishing you all safe travels to
>> KL.
>>
>>
>>
>> Best regards,
>>
>> Philippe
>>
>>
>>
>> Board/GNSO correspondence:
>>
>>    - 6 Mar 2022 Letter from Maarten Botterman to Manal Ismail and
>>    Philippe Fouquart
>>    <https://www.icann.org/en/system/files/correspondence/botterman-to-ismail-fouquart-06mar22-en.pdf> ?
>>    including the framing paper
>>    - 27 April 2022 Letter from Philippe Fouquart to Maarten Botterman
>>    <https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-27apr22-en.pdf>
>>    - 19 May 2022 Letter from Maarten Botterman to Philippe Fouquart
>>    <https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-19may22-en.pdf>
>>
>>    - 29 Jun 2022 Letter from Philippe Fouquart to Maarten Botterman and
>>    Manal Ismail
>>    <https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-ismail-29jun22-en.pdf>
>>
>>    - 25 Jul 2022 Letter from Maarten Botterman to Philippe Fouquart and
>>    Manal Ismail
>>    <https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-ismail-25jul22-en.pdf>
>>
>>
>> Council small team report:
>> https://gnso.icann.org/sites/default/files/policy/2022/draft/draft-closed-generics-small-team-report-24jun22-en.pdf
>>
>>
>>
>> _________________________________________________________________________________________________________________________
>>
>> 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.
>>
>> _______________________________________________
>> Gnso-chairs mailing list
>> Gnso-chairs at icann.org
>> https://mm.icann.org/mailman/listinfo/gnso-chairs
>> _______________________________________________
>> 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
>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
> _______________________________________________
> 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 <https://www.humboldt-foundation.de/>

Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum Berlin
f?r Sozialforschung (WZB) <https://wzb.eu/en>

Member | Coaliz?o Direitos na Rede <https://direitosnarede.org.br/>
Chair | Non-Commercial Stakeholder Group at ICANN
<https://gnso.icann.org/en/about/stakeholders-constituencies/ncsg>
Co-Coordinator | Internet Governance Caucus  <https://igcaucus.org/>

Twitter: @boomartins <https://twitter.com/boomartins> // Skype:
bruna.martinsantos
*bruna.martinsdossantos at wzb.eu <bruna.martinsdossantos at wzb.eu>* and
bruna.mrtns at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20220908/93b00b5f/attachment.htm>

From stephanie.perrin at mail.utoronto.ca  Thu Sep  8 22:38:52 2022
From: stephanie.perrin at mail.utoronto.ca (Stephanie E Perrin)
Date: Thu, 8 Sep 2022 15:38:52 -0400
Subject: [NCSG-PC] Fwd: [gnso-chairs] GNSO/GAC dialogue on closed
 generics: selection of GNSO participants
In-Reply-To: <3cb39725-0fb1-877c-1f6b-f1433f323de0@KathyKleiman.com>
References: <23150_1662120078_6311F08E_23150_224_1_fa943370c01643e3b2bc7375fc86e561@orange.com>
 <CAM8DdeX1py8C7wf+Wya4_99yCesi=bekspuRCMB+aL_Uz7yzvw@mail.gmail.com>
 <3cb39725-0fb1-877c-1f6b-f1433f323de0@KathyKleiman.com>
Message-ID: <a5727076-f937-7783-9737-23b31652698c@mail.utoronto.ca>

Sounds like a great idea to me.? Did your group ever get opinions from 
government Competition Bureaus and/or departments when you were working 
on closed generics?

cheers Stephanie

On 2022-09-07 10:01 a.m., Kathy Kleiman wrote:
>
> Hi Tomslin and All,
>
> I would like to recommend that I be appointed with George Sadowsky as 
> an unofficial alternate. George as you know as an ICANN Board member 
> for many years. But few know that before that he was a founding member 
> of NCUC (NCSG would not be created for about decade after).? In 1999, 
> George was with New York University as IT director and joined us in 
> founding NCUC and attending early meetings. We were his initial link 
> to ICANN!
>
> He has now applied to join NCSG.? Some Board members leave ICANN 
> forever, but those who remain, tend to go back to the groups they came 
> from. I hope we will approve his membership. And then I hope we can 
> allow him to work with me on the Closed Generics issues. He is an 
> expert on this issue from his time on the Board and knows how 
> difficult and complicated it is.? He helped make sure we heard from 
> noncommercial organizations around the world before passing the first 
> ban on Closed Generics. Later, when the Subsequent Procedures Working 
> Group was looking closely at this issue, George (at my invitation) 
> joined the Working Group to again share the complexities and potential 
> problems of Closed Generics from his perspective (which include his 
> more recent experience with many United Nations organizations).
>
> While technically the job is supposed to be for one person, it is too 
> big for one volunteer (note: some attorneys will be paid by their 
> clients and law firms to participate fully in this new group and there 
> is a reason for that). ALAC plans to appoint a primary person and a 
> backup person if the primary person cannot attend a meeting or 
> discussion.? Since I will be on book tour with my new book about the 
> ENIAC Programmers, */Proving Ground, /*I think it would be good idea 
> for us to have a similar arrangement. We don't want to miss a single 
> Closed Generic meeting!
>
> Best and tx,
>
> Kathy
>
> On 9/6/2022 8:41 AM, Tomslin Samme-Nlar wrote:
>> FYI, PC.
>>
>> I am still waiting on guidance from Bruna but I just wanted to bring 
>> to your attention this statement in the meantime " /*This group would 
>> ideally have a first informal meeting during ICANN 75, so we would 
>> appreciate if you would let us know the name of your representative 
>> ideally by September 19^th */."
>> It means we have only 2 weeks to name a representative for this. I 
>> don't think it'll be a problem since Kathy Kleinman had indicated 
>> interest already and was granted funding to KL based on that interest 
>> but I thought I'd flag the urgency to the whole committee.
>>
>> Warmly,
>> Tomslin
>> @LinkedIn: https://www.linkedin.com/in/tomslin/
>>
>>
>> ---------- Forwarded message ---------
>> From: *philippe.fouquart--- via Gnso-chairs* <gnso-chairs at icann.org>
>> Date: Fri, 2 Sept 2022 at 22:01
>> Subject: [gnso-chairs] GNSO/GAC dialogue on closed generics: 
>> selection of GNSO participants
>> To: mason.cole at appdetex.com <mason.cole at appdetex.com>, 
>> wolf-ulrich.knoben at t-online.de <wolf-ulrich.knoben at t-online.de>, 
>> lschulman at inta.org <lschulman at inta.org>, bruna.mrtns at gmail.com 
>> <bruna.mrtns at gmail.com>, plommer at gmail.com <plommer at gmail.com>, 
>> benakin at gmail.com <benakin at gmail.com>, aheineman at godaddy.com 
>> <aheineman at godaddy.com>, sdemetriou at verisign.com 
>> <sdemetriou at verisign.com>, chair at rysg.info <chair at rysg.info>, 
>> secretariat at rysg.info <secretariat at rysg.info>, 
>> secretariat at icannregistrars.org <secretariat at icannregistrars.org>
>> Cc: gnso-secs at icann.org <gnso-secs at icann.org>, gnso-chairs at icann.org 
>> <gnso-chairs at icann.org>, council at gnso icann. org <council at gnso.icann.org>
>>
>>
>> Dear SG/C leaders,
>>
>> Hope this email finds you all well.
>>
>> As you know, following an invitation from the Board, the GNSO and the 
>> GAC will enter into a dialogue to ?formulate a workable framework to 
>> identify and handle closed generic applications for the immediate 
>> next round of new gTLDs?, and in this dialogue we will be joined by 
>> ALAC.
>>
>> Council leadership would like to invite each Stakeholder Group to 
>> select a representative for this dialogue. This group is would 
>> ideally have a first informal meeting during ICANN 75, so we would 
>> appreciate if you would let us know the name of your representative 
>> ideally by September 19^th .
>>
>> The attached document provides the guidance for this appointment.
>>
>> I would finally like to draw your attention to the spirit of 
>> involvement in this effort:
>>
>>   * the framework discussion will focus on options other than the two
>>     endpoint positions (i.e. no closed generics at all; closed
>>     generics without restrictions) as per the Board?s Proposed
>>     Parameters for Dialogue
>>   * the participants will "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.? (Council small
>>     team report)
>>
>> Looking forward to hearing from you, and wishing you all safe travels 
>> to KL.
>>
>> Best regards,
>>
>> Philippe
>>
>> Board/GNSO correspondence:
>>
>>   * 6 Mar 2022 Letter from Maarten Botterman to Manal Ismail and
>>     Philippe Fouquart
>>     <https://www.icann.org/en/system/files/correspondence/botterman-to-ismail-fouquart-06mar22-en.pdf>??
>>     including the framing paper
>>   * 27 April 2022 Letter from Philippe Fouquart to Maarten Botterman
>>     <https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-27apr22-en.pdf>
>>   * 19 May 2022 Letter from Maarten Botterman to Philippe Fouquart
>>     <https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-19may22-en.pdf>
>>   * 29 Jun 2022 Letter from Philippe Fouquart to Maarten Botterman
>>     and Manal Ismail
>>     <https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-ismail-29jun22-en.pdf>
>>   * 25 Jul 2022 Letter from Maarten Botterman to Philippe Fouquart
>>     and Manal Ismail
>>     <https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-ismail-25jul22-en.pdf>
>>
>> Council small team report: 
>> https://gnso.icann.org/sites/default/files/policy/2022/draft/draft-closed-generics-small-team-report-24jun22-en.pdf 
>>
>>
>> _________________________________________________________________________________________________________________________
>>
>> 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.
>> _______________________________________________
>> Gnso-chairs mailing list
>> Gnso-chairs at icann.org
>> https://mm.icann.org/mailman/listinfo/gnso-chairs
>> _______________________________________________
>> 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
>
> _______________________________________________
> 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: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20220908/b65fd8ce/attachment.htm>

From mesumbeslin at gmail.com  Thu Sep  8 23:20:30 2022
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Fri, 9 Sep 2022 06:20:30 +1000
Subject: [NCSG-PC] Fwd: [gnso-chairs] GNSO/GAC dialogue on closed
 generics: selection of GNSO participants
In-Reply-To: <CADAEEV0wY-j0K_GH_Cp3waaO+c-AANNTrPA0QN5jduY2XTA2vA@mail.gmail.com>
References: <23150_1662120078_6311F08E_23150_224_1_fa943370c01643e3b2bc7375fc86e561@orange.com>
 <CAM8DdeX1py8C7wf+Wya4_99yCesi=bekspuRCMB+aL_Uz7yzvw@mail.gmail.com>
 <3cb39725-0fb1-877c-1f6b-f1433f323de0@KathyKleiman.com>
 <CAM8DdeXjXp0mOUR-mumSt9OgkGCUCHx6oXt3naumsKN922HTPA@mail.gmail.com>
 <CADAEEV0wY-j0K_GH_Cp3waaO+c-AANNTrPA0QN5jduY2XTA2vA@mail.gmail.com>
Message-ID: <CAM8DdeXtK3PP40phV7FvcuESBk0GhFOzBLz0GfiGh3zdHfvRiw@mail.gmail.com>

Hi Bruna,

No we don't yet know. In fact, the staff team working on this was still
asking for feedback from SGs regarding their appointment progress to
determine if they will be able to have enough folks present in KL for an
informal meeting of the group.

Warmly,
Tomslin
@LinkedIn: https://www.linkedin.com/in/tomslin/


On Fri, 9 Sept 2022 at 02:19, Bruna Martins dos Santos <
bruna.mrtns at gmail.com> wrote:

> Hello all,
>
> Jumping in here just to ask whether we know about the final date for the
> meeting at ICANN75 if theres one. I think Kathy wont be there for the full
> meeting, right @Kathy Kleiman <kathy at dnrc.tech> ?
>
> best,
> B
>
> On Wed, Sep 7, 2022 at 10:54 PM Tomslin Samme-Nlar <mesumbeslin at gmail.com>
> wrote:
>
>> Hi Kathy,
>>
>> Thanks for volunteering. Really appreciate it because with the short
>> window and skills required,  it would have been very difficult to get a
>> volunteer. So, thank you!
>>
>> Regarding your recommendation that we appoint an official alternate, I am
>> afraid that is not possible as stipulated on the candidate guidance
>> document I attached to my previous email. And more we are now also past the
>> negotiation phase in the Council. The guidance document is now the rule
>> book for appointing members. What we could do is to pull you out as member
>> in the event that you can't attend and appoint George instead.
>>
>> Please let us know and apologies that Manju and I were unable to secure
>> an official alternate for NCSG during the drafting and discussion of the
>> text.
>>
>> Warmly,
>> Tomslin
>>
>> On Thu, 8 Sept 2022, 00:01 Kathy Kleiman, <Kathy at kathykleiman.com> wrote:
>>
>>> Hi Tomslin and All,
>>>
>>> I would like to recommend that I be appointed with George Sadowsky as an
>>> unofficial alternate. George as you know as an ICANN Board member for many
>>> years. But few know that before that he was a founding member of NCUC (NCSG
>>> would not be created for about decade after).  In 1999, George was with New
>>> York University as IT director and joined us in founding NCUC and attending
>>> early meetings. We were his initial link to ICANN!
>>>
>>> He has now applied to join NCSG.  Some Board members leave ICANN
>>> forever, but those who remain, tend to go back to the groups they came
>>> from. I hope we will approve his membership. And then I hope we can allow
>>> him to work with me on the Closed Generics issues. He is an expert on this
>>> issue from his time on the Board and knows how difficult and complicated it
>>> is.  He helped make sure we heard from noncommercial organizations around
>>> the world before passing the first ban on Closed Generics. Later, when the
>>> Subsequent Procedures Working Group was looking closely at this issue,
>>> George (at my invitation) joined the Working Group to again share the
>>> complexities and potential problems of Closed Generics from his perspective
>>> (which include his more recent experience with many United Nations
>>> organizations).
>>>
>>> While technically the job is supposed to be for one person, it is too
>>> big for one volunteer (note: some attorneys will be paid by their clients
>>> and law firms to participate fully in this new group and there is a reason
>>> for that). ALAC plans to appoint a primary person and a backup person if
>>> the primary person cannot attend a meeting or discussion.  Since I will be
>>> on book tour with my new book about the ENIAC Programmers, *Proving
>>> Ground, *I think it would be good idea for us to have a similar
>>> arrangement. We don't want to miss a single Closed Generic meeting!
>>>
>>> Best and tx,
>>>
>>> Kathy
>>> On 9/6/2022 8:41 AM, Tomslin Samme-Nlar wrote:
>>>
>>> FYI, PC.
>>>
>>> I am still waiting on guidance from Bruna but I just wanted to bring to
>>> your attention this statement in the meantime " *This group would
>>> ideally have a first informal meeting during ICANN 75, so we would
>>> appreciate if you would let us know the name of your representative ideally
>>> by September 19th*."
>>> It means we have only 2 weeks to name a representative for this. I don't
>>> think it'll be a problem since Kathy Kleinman had indicated interest
>>> already and was granted funding to KL based on that interest but I thought
>>> I'd flag the urgency to the whole committee.
>>>
>>> Warmly,
>>> Tomslin
>>> @LinkedIn: https://www.linkedin.com/in/tomslin/
>>>
>>>
>>> ---------- Forwarded message ---------
>>> From: philippe.fouquart--- via Gnso-chairs <gnso-chairs at icann.org>
>>> Date: Fri, 2 Sept 2022 at 22:01
>>> Subject: [gnso-chairs] GNSO/GAC dialogue on closed generics: selection
>>> of GNSO participants
>>> To: mason.cole at appdetex.com <mason.cole at appdetex.com>,
>>> wolf-ulrich.knoben at t-online.de <wolf-ulrich.knoben at t-online.de>,
>>> lschulman at inta.org <lschulman at inta.org>, bruna.mrtns at gmail.com <
>>> bruna.mrtns at gmail.com>, plommer at gmail.com <plommer at gmail.com>,
>>> benakin at gmail.com <benakin at gmail.com>, aheineman at godaddy.com <
>>> aheineman at godaddy.com>, sdemetriou at verisign.com <sdemetriou at verisign.com>,
>>> chair at rysg.info <chair at rysg.info>, secretariat at rysg.info <
>>> secretariat at rysg.info>, secretariat at icannregistrars.org <
>>> secretariat at icannregistrars.org>
>>> Cc: gnso-secs at icann.org <gnso-secs at icann.org>, gnso-chairs at icann.org <
>>> gnso-chairs at icann.org>, council at gnso icann. org <council at gnso.icann.org>
>>>
>>>
>>> Dear SG/C leaders,
>>>
>>>
>>>
>>> Hope this email finds you all well.
>>>
>>>
>>>
>>> As you know, following an invitation from the Board, the GNSO and the
>>> GAC will enter into a dialogue to ?formulate a workable framework to
>>> identify and handle closed generic applications for the immediate next
>>> round of new gTLDs?, and in this dialogue we will be joined by ALAC.
>>>
>>>
>>>
>>> Council leadership would like to invite each Stakeholder Group to select
>>> a representative for this dialogue. This group is would ideally have a
>>> first informal meeting during ICANN 75, so we would appreciate if you would
>>> let us know the name of your representative ideally by September 19th.
>>>
>>>
>>>
>>> The attached document provides the guidance for this appointment.
>>>
>>>
>>>
>>> I would finally like to draw your attention to the spirit of involvement
>>> in this effort:
>>>
>>>    - the framework discussion will focus on options other than the two
>>>    endpoint positions (i.e. no closed generics at all; closed generics without
>>>    restrictions) as per the Board?s Proposed Parameters for Dialogue
>>>    - the participants will "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.? (Council
>>>    small team report)
>>>
>>>
>>>
>>> Looking forward to hearing from you, and wishing you all safe travels to
>>> KL.
>>>
>>>
>>>
>>> Best regards,
>>>
>>> Philippe
>>>
>>>
>>>
>>> Board/GNSO correspondence:
>>>
>>>    - 6 Mar 2022 Letter from Maarten Botterman to Manal Ismail and
>>>    Philippe Fouquart
>>>    <https://www.icann.org/en/system/files/correspondence/botterman-to-ismail-fouquart-06mar22-en.pdf> ?
>>>    including the framing paper
>>>    - 27 April 2022 Letter from Philippe Fouquart to Maarten Botterman
>>>    <https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-27apr22-en.pdf>
>>>    - 19 May 2022 Letter from Maarten Botterman to Philippe Fouquart
>>>    <https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-19may22-en.pdf>
>>>
>>>    - 29 Jun 2022 Letter from Philippe Fouquart to Maarten Botterman and
>>>    Manal Ismail
>>>    <https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-ismail-29jun22-en.pdf>
>>>
>>>    - 25 Jul 2022 Letter from Maarten Botterman to Philippe Fouquart and
>>>    Manal Ismail
>>>    <https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-ismail-25jul22-en.pdf>
>>>
>>>
>>> Council small team report:
>>> https://gnso.icann.org/sites/default/files/policy/2022/draft/draft-closed-generics-small-team-report-24jun22-en.pdf
>>>
>>>
>>>
>>> _________________________________________________________________________________________________________________________
>>>
>>> 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.
>>>
>>> _______________________________________________
>>> Gnso-chairs mailing list
>>> Gnso-chairs at icann.org
>>> https://mm.icann.org/mailman/listinfo/gnso-chairs
>>> _______________________________________________
>>> 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
>>>
>>> _______________________________________________
>>> NCSG-PC mailing list
>>> NCSG-PC at lists.ncsg.is
>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>
>> _______________________________________________
>> 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 <https://www.humboldt-foundation.de/>
>
> Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum Berlin
> f?r Sozialforschung (WZB) <https://wzb.eu/en>
>
> Member | Coaliz?o Direitos na Rede <https://direitosnarede.org.br/>
> Chair | Non-Commercial Stakeholder Group at ICANN
> <https://gnso.icann.org/en/about/stakeholders-constituencies/ncsg>
> Co-Coordinator | Internet Governance Caucus  <https://igcaucus.org/>
>
> Twitter: @boomartins <https://twitter.com/boomartins> // Skype:
> bruna.martinsantos
> *bruna.martinsdossantos at wzb.eu <bruna.martinsdossantos at wzb.eu>* and
> bruna.mrtns at gmail.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20220909/5a2c41e4/attachment.htm>

From mesumbeslin at gmail.com  Fri Sep  9 02:53:52 2022
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Fri, 9 Sep 2022 09:53:52 +1000
Subject: [NCSG-PC] GNSO Standing Selection Committee (SSC)
 representative from NCSG
In-Reply-To: <942bcd25-18ab-e4de-ca8b-ec4d086360a2@gmail.com>
References: <942bcd25-18ab-e4de-ca8b-ec4d086360a2@gmail.com>
Message-ID: <CAM8DdeUq5RXK3DWw5mexn=9eAO3YK=oqnboKTo0=JrsNLZiy5Q@mail.gmail.com>

Hi Sam,

I have no objection to all NCSG members who are still eligible and are
willing to continue serving SSC. Hopefully the rest of leadership agrees.

Warmly,
Tomslin
@LinkedIn: https://www.linkedin.com/in/tomslin/


On Wed, 7 Sept 2022 at 01:33, Sam Lanfranco <samlanfranco at gmail.com> wrote:

> NCSG Officers,
>
> I serve on the GNSO Standing Selection Committee (SSC) as the
> representative from NCSG. Membership is to be re-confirmed annually after
> the ICANN AGM. I am eligible to continue serving and am willing to continue
> serving if that is the wish of NCSG. ICANN Policy Development Support
> needs me to either confirm my continuation, or identify replacements, where
> appropriate. The deadline for this response is October 14th. Please
> advise me as to the wishes of NCSG.
>
> Below is the communication from ICANN Policy Development Support.
>
> Sam Lanfranco
> ------------------------------
> Dear colleagues, This message provides a brief update about the GNSO
> Standing Selection Committee (SSC) and an action item for your SG/C.
>
> Since the last AGM, the SSC successfully completed the one assignment it
> received from the GNSO Council, the annual selection process for the
> GNSO-appointed mentor for the ICANN Fellowship Program.
>
> In addition, the SSC completed a successful charter review process this
> year. The resulting charter updates were approved
> <https://community.icann.org/display/gnsocouncilmeetings/Motions+2022-05-19>
> by the GNSO Council in May.
>
> The next anticipated SSC assignment is again the annual selection the
> ICANN Fellowship Program mentor, to be selected around the end of the
> calendar year. In addition, as a Standing Committee, the Council may call
> on the SSC at any time to identify replacement candidates for those who
> step down from appointed positions. Therefore, it is important to have a
> Committee ready on an ongoing basis.
>
> According to the SSC Charter, ?The membership is expected to be confirmed
> by each Stakeholder Group and Constituency and the nominating committee
> appointees within 3 weeks after the end of the ICANN AGM.? Members may
> serve a maximum of two consecutive terms. With ICANN75 approaching, *I am
> reaching out to you to re-confirm members that are eligible to remain on
> the SSC and/or identify replacements, where appropriate.* The members of
> the SSC are:
>
> *Name*
>
> *Appointed by*
>
> *Member Since*
>
> *Status*
>
> Alan Woods
>
> RySG
>
> November 2021
>
> Eligible to continue serving.
>
> Arinola Akinyemi(Ms) (Chair)
>
> BC
>
> October 2021
>
> Eligible to continue serving.
>
> Brian Winterfeldt
>
> IPC
>
> January 2022
>
> Eligible to continue serving.
>
> Glen de Saint G?ry
>
> IPC Alternate
>
> March 2022
>
> Eligible to continue serving.
>
> Olivier Kouami
>
> NCSG
>
> November 2021
>
> Eligible to continue serving.
>
> Osvaldo Novoa
>
> ISPCP
>
> November 2020 (re-confirmed November 2021)
>
> Requires replacement.
>
> Paul McGrady
>
> NomCom
>
> November 2021
>
> Eligible to continue serving.
>
> Peter Akinremi Taiwo (Vice-Chair)
>
> NCSG
>
> November 2021
>
> Eligible to continue serving.
>
> Q Misell
>
> RrSG
>
> November 2021
>
> Eligible to continue serving.
>
> Sam Lanfranco
>
> NCSG
>
> November 2021
>
> Eligible to continue serving.
>
> Tomslin Samme-Nlar
>
> Ex-Officio Member Representing GNSO Council Leadership
>
> Ex-Officio Member Representing GNSO Council Leadership Since November 2021
>
> TBD
>
>  For additional information about the SSC, please see the wiki page:
> https://community.icann.org/x/aL-RAw
>
>  P*lease send confirmations no later than 14 October 2022.* Do not
> hesitate to get in touch if you have any questions.
>
>  Kind regards,
>   Julie and Emily
>  Emily Barabas
> Policy Development Support Senior Manager
> Internet Corporation for Assigned Names and Numbers (ICANN)
> Phone: +31 (0)6 84507976
> www.icann.org
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20220909/c7660909/attachment.htm>

From Kathy at KathyKleiman.com  Fri Sep  9 17:47:23 2022
From: Kathy at KathyKleiman.com (Kathy Kleiman)
Date: Fri, 9 Sep 2022 10:47:23 -0400
Subject: [NCSG-PC] Fwd: [gnso-chairs] GNSO/GAC dialogue on closed
 generics: selection of GNSO participants
In-Reply-To: <CAM8DdeXjXp0mOUR-mumSt9OgkGCUCHx6oXt3naumsKN922HTPA@mail.gmail.com>
References: <23150_1662120078_6311F08E_23150_224_1_fa943370c01643e3b2bc7375fc86e561@orange.com>
 <CAM8DdeX1py8C7wf+Wya4_99yCesi=bekspuRCMB+aL_Uz7yzvw@mail.gmail.com>
 <3cb39725-0fb1-877c-1f6b-f1433f323de0@KathyKleiman.com>
 <CAM8DdeXjXp0mOUR-mumSt9OgkGCUCHx6oXt3naumsKN922HTPA@mail.gmail.com>
Message-ID: <bfa31191-6909-cffe-24c3-c15329caf63d@KathyKleiman.com>

Hi Tomslin and All,

Tx for your support and your response.? I should note that my request 
below is not for an "official alternate," but an "/unofficial 
alternate/*" *and I'm glad Stephanie supports.? ALAC is already planning 
to do so, and it is a very wise thing for us to do as well. I'm afraid I 
must insist.

ICANN in these small groups can be all consuming and many people who 
participate on these teams are paid fulltime to do so (as I was when I 
was Director of Policy for .ORG). Our IPC friend, when they appoint Paul 
McGrady, will certainly be paid for his participation - and he does work 
for Amazon.

Like ALAC, we are really the only true volunteers in this process.? 
Accordingly, we cannot drop everything and abandon the work that we do 
to put bread on our tables.? We also can't go crazy trying to make 
meetings that may conflict with requirements of our jobs and families.? 
Unfair requirements is why NCSG and NCUC over the years has not 
participated in many roles of leadership and involvement across ICANN.

So the only thing that makes sense is reasonable backup- an /unofficial/ 
alternate.? It may not be part of the official rules, but it is a 
"reasonable accommodation" for parents and mothers and "reasonable 
accommodation" is a legal term of art in the US - for making sure that 
everyone can participate regardless of circumstances.

ALAC will be taking these approach - an informal alternate. Together 
(and this is not your job or Manju's), we can make the sound argument 
that true volunteers need informal alternates to cover meetings the main 
representative simply can't make - and meetings too important to miss 
(which is any of them).? ICANN needs its "watchers" in place...

For my peace of mind, as I start a busy book tour (we launched on 
Wednesday in NYC at the engineering school of Cooper Union!), we will 
need this unofficial alternate.? It is the right thing to do for NCSG 
and good precedent for days to come.

Best, Kathy

On 9/7/2022 4:54 PM, Tomslin Samme-Nlar wrote:
> Hi Kathy,
>
> Thanks for volunteering. Really?appreciate it because with the short 
> window and skills required,? it would have been very difficult to get 
> a volunteer. So, thank you!
>
> Regarding your recommendation that we appoint an official alternate, I 
> am afraid that is not possible as stipulated on the candidate guidance 
> document I attached to my previous email. And more?we are now also 
> past the negotiation phase in the Council. The guidance document is 
> now the rule book for appointing members. What we could do is to pull 
> you out as member in the event that you can't attend and appoint 
> George instead.
>
> Please let us know and apologies that Manju and I were unable to 
> secure an official alternate for NCSG during the drafting and 
> discussion of the text.
>
> Warmly,
> Tomslin
>
> On Thu, 8 Sept 2022, 00:01 Kathy Kleiman, <Kathy at kathykleiman.com> wrote:
>
>     Hi Tomslin and All,
>
>     I would like to recommend that I be appointed with George Sadowsky
>     as an unofficial alternate. George as you know as an ICANN Board
>     member for many years. But few know that before that he was a
>     founding member of NCUC (NCSG would not be created for about
>     decade after).? In 1999, George was with New York University as IT
>     director and joined us in founding NCUC and attending early
>     meetings. We were his initial link to ICANN!
>
>     He has now applied to join NCSG.? Some Board members leave ICANN
>     forever, but those who remain, tend to go back to the groups they
>     came from. I hope we will approve his membership. And then I hope
>     we can allow him to work with me on the Closed Generics issues. He
>     is an expert on this issue from his time on the Board and knows
>     how difficult and complicated it is.? He helped make sure we heard
>     from noncommercial organizations around the world before passing
>     the first ban on Closed Generics. Later, when the Subsequent
>     Procedures Working Group was looking closely at this issue, George
>     (at my invitation) joined the Working Group to again share the
>     complexities and potential problems of Closed Generics from his
>     perspective (which include his more recent experience with many
>     United Nations organizations).
>
>     While technically the job is supposed to be for one person, it is
>     too big for one volunteer (note: some attorneys will be paid by
>     their clients and law firms to participate fully in this new group
>     and there is a reason for that). ALAC plans to appoint a primary
>     person and a backup person if the primary person cannot attend a
>     meeting or discussion.? Since I will be on book tour with my new
>     book about the ENIAC Programmers, */Proving Ground, /*I think it
>     would be good idea for us to have a similar arrangement. We don't
>     want to miss a single Closed Generic meeting!
>
>     Best and tx,
>
>     Kathy
>
>     On 9/6/2022 8:41 AM, Tomslin Samme-Nlar wrote:
>>     FYI, PC.
>>
>>     I am still waiting on guidance from Bruna but I just wanted to
>>     bring to your attention this statement in the meantime " /*This
>>     group would ideally have a first informal meeting during ICANN
>>     75, so we would appreciate if you would let us know the name of
>>     your representative ideally by September 19^th */."
>>     It means we have only 2 weeks to name a representative for this.
>>     I don't think it'll be a problem since Kathy Kleinman had
>>     indicated interest already and was granted funding to KL based on
>>     that interest but I thought I'd flag the urgency to the whole
>>     committee.
>>
>>     Warmly,
>>     Tomslin
>>     @LinkedIn: https://www.linkedin.com/in/tomslin/
>>
>>
>>     ---------- Forwarded message ---------
>>     From: *philippe.fouquart--- via Gnso-chairs* <gnso-chairs at icann.org>
>>     Date: Fri, 2 Sept 2022 at 22:01
>>     Subject: [gnso-chairs] GNSO/GAC dialogue on closed generics:
>>     selection of GNSO participants
>>     To: mason.cole at appdetex.com <mason.cole at appdetex.com>,
>>     wolf-ulrich.knoben at t-online.de <wolf-ulrich.knoben at t-online.de>,
>>     lschulman at inta.org <lschulman at inta.org>, bruna.mrtns at gmail.com
>>     <bruna.mrtns at gmail.com>, plommer at gmail.com <plommer at gmail.com>,
>>     benakin at gmail.com <benakin at gmail.com>, aheineman at godaddy.com
>>     <aheineman at godaddy.com>, sdemetriou at verisign.com
>>     <sdemetriou at verisign.com>, chair at rysg.info <chair at rysg.info>,
>>     secretariat at rysg.info <secretariat at rysg.info>,
>>     secretariat at icannregistrars.org <secretariat at icannregistrars.org>
>>     Cc: gnso-secs at icann.org <gnso-secs at icann.org>,
>>     gnso-chairs at icann.org <gnso-chairs at icann.org>, council at gnso
>>     icann. org <council at gnso.icann.org>
>>
>>
>>     Dear SG/C leaders,
>>
>>     Hope this email finds you all well.
>>
>>     As you know, following an invitation from the Board, the GNSO and
>>     the GAC will enter into a dialogue to ?formulate a workable
>>     framework to identify and handle closed generic applications for
>>     the immediate next round of new gTLDs?, and in this dialogue we
>>     will be joined by ALAC.
>>
>>     Council leadership would like to invite each Stakeholder Group to
>>     select a representative for this dialogue. This group is would
>>     ideally have a first informal meeting during ICANN 75, so we
>>     would appreciate if you would let us know the name of your
>>     representative ideally by September 19^th .
>>
>>     The attached document provides the guidance for this appointment.
>>
>>     I would finally like to draw your attention to the spirit of
>>     involvement in this effort:
>>
>>       * the framework discussion will focus on options other than the
>>         two endpoint positions (i.e. no closed generics at all;
>>         closed generics without restrictions) as per the Board?s
>>         Proposed Parameters for Dialogue
>>       * the participants will "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.? (Council small team report)
>>
>>     Looking forward to hearing from you, and wishing you all safe
>>     travels to KL.
>>
>>     Best regards,
>>
>>     Philippe
>>
>>     Board/GNSO correspondence:
>>
>>       * 6 Mar 2022 Letter from Maarten Botterman to Manal Ismail and
>>         Philippe Fouquart
>>         <https://www.icann.org/en/system/files/correspondence/botterman-to-ismail-fouquart-06mar22-en.pdf>??
>>         including the framing paper
>>       * 27 April 2022 Letter from Philippe Fouquart to Maarten
>>         Botterman
>>         <https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-27apr22-en.pdf>
>>       * 19 May 2022 Letter from Maarten Botterman to Philippe
>>         Fouquart
>>         <https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-19may22-en.pdf>
>>       * 29 Jun 2022 Letter from Philippe Fouquart to Maarten
>>         Botterman and Manal Ismail
>>         <https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-ismail-29jun22-en.pdf>
>>       * 25 Jul 2022 Letter from Maarten Botterman to Philippe
>>         Fouquart and Manal Ismail
>>         <https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-ismail-25jul22-en.pdf>
>>
>>     Council small team report:
>>     https://gnso.icann.org/sites/default/files/policy/2022/draft/draft-closed-generics-small-team-report-24jun22-en.pdf
>>
>>
>>     _________________________________________________________________________________________________________________________
>>
>>     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.
>>     _______________________________________________
>>     Gnso-chairs mailing list
>>     Gnso-chairs at icann.org
>>     https://mm.icann.org/mailman/listinfo/gnso-chairs
>>     _______________________________________________
>>     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
>     _______________________________________________
>     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: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20220909/e7316900/attachment.htm>

From mesumbeslin at gmail.com  Mon Sep 12 11:25:30 2022
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Mon, 12 Sep 2022 18:25:30 +1000
Subject: [NCSG-PC] Fwd: [gnso-chairs] GNSO/GAC dialogue on closed
 generics: selection of GNSO participants
In-Reply-To: <bfa31191-6909-cffe-24c3-c15329caf63d@KathyKleiman.com>
References: <23150_1662120078_6311F08E_23150_224_1_fa943370c01643e3b2bc7375fc86e561@orange.com>
 <CAM8DdeX1py8C7wf+Wya4_99yCesi=bekspuRCMB+aL_Uz7yzvw@mail.gmail.com>
 <3cb39725-0fb1-877c-1f6b-f1433f323de0@KathyKleiman.com>
 <CAM8DdeXjXp0mOUR-mumSt9OgkGCUCHx6oXt3naumsKN922HTPA@mail.gmail.com>
 <bfa31191-6909-cffe-24c3-c15329caf63d@KathyKleiman.com>
Message-ID: <CAM8DdeWowM9aOKdvtN0tDEjk+Xc8YHntQ4d6fG1Dz70-vaKTNQ@mail.gmail.com>

Hi Kathy,

My bad. I misunderstood the request. I am happy with the proposal of an
unofficial alternate.

Warmly,
Tomslin

On Sat, 10 Sept 2022, 00:47 Kathy Kleiman, <Kathy at kathykleiman.com> wrote:

> Hi Tomslin and All,
>
> Tx for your support and your response.  I should note that my request
> below is not for an "official alternate," but an "*unofficial alternate**"
> *and I'm glad Stephanie supports.  ALAC is already planning to do so, and
> it is a very wise thing for us to do as well. I'm afraid I must insist.
>
> ICANN in these small groups can be all consuming and many people who
> participate on these teams are paid fulltime to do so (as I was when I was
> Director of Policy for .ORG). Our IPC friend, when they appoint Paul
> McGrady, will certainly be paid for his participation - and he does work
> for Amazon.
>
> Like ALAC, we are really the only true volunteers in this process.
> Accordingly, we cannot drop everything and abandon the work that we do to
> put bread on our tables.  We also can't go crazy trying to make meetings
> that may conflict with requirements of our jobs and families.  Unfair
> requirements is why NCSG and NCUC over the years has not participated in
> many roles of leadership and involvement across ICANN.
>
> So the only thing that makes sense is reasonable backup- an *unofficial*
> alternate.  It may not be part of the official rules, but it is a
> "reasonable accommodation" for parents and mothers and "reasonable
> accommodation" is a legal term of art in the US - for making sure that
> everyone can participate regardless of circumstances.
>
> ALAC will be taking these approach - an informal alternate. Together (and
> this is not your job or Manju's), we can make the sound argument that true
> volunteers need informal alternates to cover meetings the main
> representative simply can't make - and meetings too important to miss
> (which is any of them).  ICANN needs its "watchers" in place...
>
> For my peace of mind, as I start a busy book tour (we launched on
> Wednesday in NYC at the engineering school of Cooper Union!), we will need
> this unofficial alternate.  It is the right thing to do for NCSG and good
> precedent for days to come.
>
> Best, Kathy
> On 9/7/2022 4:54 PM, Tomslin Samme-Nlar wrote:
>
> Hi Kathy,
>
> Thanks for volunteering. Really appreciate it because with the short
> window and skills required,  it would have been very difficult to get a
> volunteer. So, thank you!
>
> Regarding your recommendation that we appoint an official alternate, I am
> afraid that is not possible as stipulated on the candidate guidance
> document I attached to my previous email. And more we are now also past the
> negotiation phase in the Council. The guidance document is now the rule
> book for appointing members. What we could do is to pull you out as member
> in the event that you can't attend and appoint George instead.
>
> Please let us know and apologies that Manju and I were unable to secure an
> official alternate for NCSG during the drafting and discussion of the text.
>
> Warmly,
> Tomslin
>
> On Thu, 8 Sept 2022, 00:01 Kathy Kleiman, <Kathy at kathykleiman.com> wrote:
>
>> Hi Tomslin and All,
>>
>> I would like to recommend that I be appointed with George Sadowsky as an
>> unofficial alternate. George as you know as an ICANN Board member for many
>> years. But few know that before that he was a founding member of NCUC (NCSG
>> would not be created for about decade after).  In 1999, George was with New
>> York University as IT director and joined us in founding NCUC and attending
>> early meetings. We were his initial link to ICANN!
>>
>> He has now applied to join NCSG.  Some Board members leave ICANN forever,
>> but those who remain, tend to go back to the groups they came from. I hope
>> we will approve his membership. And then I hope we can allow him to work
>> with me on the Closed Generics issues. He is an expert on this issue from
>> his time on the Board and knows how difficult and complicated it is.  He
>> helped make sure we heard from noncommercial organizations around the world
>> before passing the first ban on Closed Generics. Later, when the Subsequent
>> Procedures Working Group was looking closely at this issue, George (at my
>> invitation) joined the Working Group to again share the complexities and
>> potential problems of Closed Generics from his perspective (which include
>> his more recent experience with many United Nations organizations).
>>
>> While technically the job is supposed to be for one person, it is too big
>> for one volunteer (note: some attorneys will be paid by their clients and
>> law firms to participate fully in this new group and there is a reason for
>> that). ALAC plans to appoint a primary person and a backup person if the
>> primary person cannot attend a meeting or discussion.  Since I will be on
>> book tour with my new book about the ENIAC Programmers, *Proving Ground,
>> *I think it would be good idea for us to have a similar arrangement. We
>> don't want to miss a single Closed Generic meeting!
>>
>> Best and tx,
>>
>> Kathy
>> On 9/6/2022 8:41 AM, Tomslin Samme-Nlar wrote:
>>
>> FYI, PC.
>>
>> I am still waiting on guidance from Bruna but I just wanted to bring to
>> your attention this statement in the meantime " *This group would
>> ideally have a first informal meeting during ICANN 75, so we would
>> appreciate if you would let us know the name of your representative ideally
>> by September 19th*."
>> It means we have only 2 weeks to name a representative for this. I don't
>> think it'll be a problem since Kathy Kleinman had indicated interest
>> already and was granted funding to KL based on that interest but I thought
>> I'd flag the urgency to the whole committee.
>>
>> Warmly,
>> Tomslin
>> @LinkedIn: https://www.linkedin.com/in/tomslin/
>>
>>
>> ---------- Forwarded message ---------
>> From: philippe.fouquart--- via Gnso-chairs <gnso-chairs at icann.org>
>> Date: Fri, 2 Sept 2022 at 22:01
>> Subject: [gnso-chairs] GNSO/GAC dialogue on closed generics: selection of
>> GNSO participants
>> To: mason.cole at appdetex.com <mason.cole at appdetex.com>,
>> wolf-ulrich.knoben at t-online.de <wolf-ulrich.knoben at t-online.de>,
>> lschulman at inta.org <lschulman at inta.org>, bruna.mrtns at gmail.com <
>> bruna.mrtns at gmail.com>, plommer at gmail.com <plommer at gmail.com>,
>> benakin at gmail.com <benakin at gmail.com>, aheineman at godaddy.com <
>> aheineman at godaddy.com>, sdemetriou at verisign.com <sdemetriou at verisign.com>,
>> chair at rysg.info <chair at rysg.info>, secretariat at rysg.info <
>> secretariat at rysg.info>, secretariat at icannregistrars.org <
>> secretariat at icannregistrars.org>
>> Cc: gnso-secs at icann.org <gnso-secs at icann.org>, gnso-chairs at icann.org <
>> gnso-chairs at icann.org>, council at gnso icann. org <council at gnso.icann.org>
>>
>>
>> Dear SG/C leaders,
>>
>>
>>
>> Hope this email finds you all well.
>>
>>
>>
>> As you know, following an invitation from the Board, the GNSO and the GAC
>> will enter into a dialogue to ?formulate a workable framework to identify
>> and handle closed generic applications for the immediate next round of new
>> gTLDs?, and in this dialogue we will be joined by ALAC.
>>
>>
>>
>> Council leadership would like to invite each Stakeholder Group to select
>> a representative for this dialogue. This group is would ideally have a
>> first informal meeting during ICANN 75, so we would appreciate if you would
>> let us know the name of your representative ideally by September 19th.
>>
>>
>>
>> The attached document provides the guidance for this appointment.
>>
>>
>>
>> I would finally like to draw your attention to the spirit of involvement
>> in this effort:
>>
>>    - the framework discussion will focus on options other than the two
>>    endpoint positions (i.e. no closed generics at all; closed generics without
>>    restrictions) as per the Board?s Proposed Parameters for Dialogue
>>    - the participants will "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.? (Council
>>    small team report)
>>
>>
>>
>> Looking forward to hearing from you, and wishing you all safe travels to
>> KL.
>>
>>
>>
>> Best regards,
>>
>> Philippe
>>
>>
>>
>> Board/GNSO correspondence:
>>
>>    - 6 Mar 2022 Letter from Maarten Botterman to Manal Ismail and
>>    Philippe Fouquart
>>    <https://www.icann.org/en/system/files/correspondence/botterman-to-ismail-fouquart-06mar22-en.pdf> ?
>>    including the framing paper
>>    - 27 April 2022 Letter from Philippe Fouquart to Maarten Botterman
>>    <https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-27apr22-en.pdf>
>>    - 19 May 2022 Letter from Maarten Botterman to Philippe Fouquart
>>    <https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-19may22-en.pdf>
>>
>>    - 29 Jun 2022 Letter from Philippe Fouquart to Maarten Botterman and
>>    Manal Ismail
>>    <https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-ismail-29jun22-en.pdf>
>>
>>    - 25 Jul 2022 Letter from Maarten Botterman to Philippe Fouquart and
>>    Manal Ismail
>>    <https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-ismail-25jul22-en.pdf>
>>
>>
>> Council small team report:
>> https://gnso.icann.org/sites/default/files/policy/2022/draft/draft-closed-generics-small-team-report-24jun22-en.pdf
>>
>>
>>
>> _________________________________________________________________________________________________________________________
>>
>> 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.
>>
>> _______________________________________________
>> Gnso-chairs mailing list
>> Gnso-chairs at icann.org
>> https://mm.icann.org/mailman/listinfo/gnso-chairs
>> _______________________________________________
>> 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
>>
>> _______________________________________________
>> 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: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20220912/59d71dd5/attachment.htm>

From mesumbeslin at gmail.com  Mon Sep 12 11:28:14 2022
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Mon, 12 Sep 2022 18:28:14 +1000
Subject: [NCSG-PC] Fwd: [council] Proposed Agenda | GNSO Council Meetings -
 Public & Admin - Wednesday 21 September 2022
In-Reply-To: <852D0011-FFBD-493F-88D7-338CAC25E795@icann.org>
References: <852D0011-FFBD-493F-88D7-338CAC25E795@icann.org>
Message-ID: <CAM8DdeUNS0S_A4bHzeJOz7_S2rLHfA=gWpTCh_qhTad5X5yOCQ@mail.gmail.com>

Hi everyone,

Here is the draft Agenda for the September council meeting.

Warmly,
Tomslin

---------- Forwarded message ---------
From: Nathalie Peregrine via council <council at gnso.icann.org>
Date: Mon, 12 Sept 2022, 06:24
Subject: [council] Proposed Agenda | GNSO Council Meetings - Public & Admin
- Wednesday 21 September 2022
To: council at gnso.icann.org <council at gnso.icann.org>,
liaison6c at gnso.icann.org <liaison6c at gnso.icann.org>
Cc: gnso-secs at icann.org <gnso-secs at icann.org>


Dear all,



Please find below the final proposed agenda for the GNSO Council Meeting on 21
September  2022.
Draft GNSO Council Agenda 21 September 2022 -

*Part I*

Please note that all documents referenced in the agenda have been gathered
on a Wiki page for convenience and easier access:
https://community.icann.org/x/kIJJD.



This agenda was established according to the GNSO Operating Procedures
<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-procedures-24oct19-en.pdf>
v3.5, updated on 24 October 2019

For convenience:

   - An excerpt of the ICANN Bylaws defining the voting thresholds is
   provided in Appendix 1 at the end of this agenda.
   - An excerpt from the Council Operating Procedures defining the absentee
   voting procedures is provided in Appendix 2 at the end of this agenda.



GNSO Council meeting held in Kuala Lumpur, Malaysia 13:15-15:15 MYT:
https://tinyurl.com/bdpud5r3



Coordinated Universal Time: 05:15-07:15 UTC



(Tuesday) 22:15 Los Angeles; (Wednesday) 01:15 Washington DC; 06:15 London;
07:15 Paris; 08:15 Moscow; 15:15 Melbourne



*GNSO Council Meeting Remote Participation: (TBD)*

Councilors should notify the GNSO Secretariat in advance if they will not
be able to attend and/or need a dial out call.

___________________________________

*Item 1: Administrative Matters (10 minutes)*

1.1 - Roll Call

1.2 - Updates to Statements of Interest

1.3 - Review / Amend Agenda

1.4 - Note the status of minutes for the previous Council meetings per the
GNSO Operating Procedures:

Minutes
<https://gnso.icann.org/sites/default/files/policy/2022/minutes/minutes-gnso-council-21jul22-en.pdf>
of the GNSO Council meeting on 21 July 2022 were posted on 05 August 2022.

Minutes
<https://gnso.icann.org/sites/default/files/policy/2022/minutes/minutes-gnso-council-25aug22-en.pdf>
of the GNSO Council meeting on 25 August 2022 were posted on 07 September
2022.



*Item 2: Opening Remarks / Review of Projects & Action List (5 minutes)*

2.1 - Review focus areas and provide updates on specific key themes /
topics, to include review of Projects List
<https://gnso.icann.org/en/council/project>and Action Item List.
<https://community.icann.org/x/RgZlAg>



*Item 3: Consent Agenda (0 minutes) *

   - None



*Item 4: COUNCIL UPDATE - Update From Public Technical Identifiers (PTI)
IANA (10 minutes)*

As noted on the relevant webpage <https://pti.icann.org/>, ?Public
Technical Identifiers (PTI) is responsible for the operational aspects of
coordinating the Internet?s unique identifiers and maintaining the trust of
the community to provide these services in an unbiased, responsible and
effective manner. Mainly, PTI is responsible for the operation of the IANA
function,? as it relates to domain names, number resources, and protocol
parameter assignments. As PTI performs the IANA functions on behalf of
ICANN, it plays a critical role in the ICANN ecosystem.

The PTI Board collaborated with IANA staff, ICANN org, and members of the
community to develop an inaugural strategic plan for July 2020 to June
2024, which as Lise Fuhr, Chair of the PTI Board of Directors notes in her blog
post
<https://www.icann.org/en/blogs/details/a-roadmap-for-success-icann-affiliate-pti-publishes-first-strategic-plan-15-9-2020-en>,
provides ?IANA-related strategic objectives that will help PTI continue to
provide secure and accountable management of the Internet's unique
identifier systems.?

Here, the Council will receive an update on PTI.

4.1 ? Introduction of topic (Council leadership)

4.2 ? Presentation (Lise Fuhr)

4.3 ? Discussion

4.4 - Next steps



*Item 5: COUNCIL DISCUSSION - Registration Data Accuracy Scoping Team -
Assignments #1 (Enforcement and Reporting) and #2 (Measurement of Accuracy)
Write Up & Process for Finding a New Chair (20 minutes)*

The Registration Data Accuracy (RDA) Scoping Team was initiated by the GNSO
Council in July 2021 per the formation instructions
<https://gnso.icann.org/sites/default/files/file/field-file-attach/registration-data-accuracy-scoping-team-formation-instructions-09jul21-en.pdf>.
The Scoping Team was tasked with considering a number of accuracy-related
factors such as the current enforcement, reporting, measurement, and
overall effectiveness of accuracy-related efforts. These considerations are
expected to help inform its deliberations and the development of
recommendations to the GNSO Council on whether any changes are recommended
to improve accuracy levels, and, if so, how and by whom these changes would
need to be developed (for example, if changes to existing contractual
requirements are recommended, a PDP or contractual negotiations may be
necessary to effect a change).

The RDA Scoping Team submitted a Project Change Request (PCR)
<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/palage-to-gnso-council-10may22-en.pdf>
to Council on 10 May 2022. The Scoping Team has since completed Assignment
#1 (enforcement and reporting) and Assignment #2 (measurement of accuracy)
and submitted its write up
<https://mm.icann.org/pipermail/council/2022-September/025950.html> to the
Council on 5 September 2022. In the write up, the group is suggesting
moving forward with two proposals that would not require access to
registration data, namely a registrar survey and a possible registrar audit
that may help further inform the team?s work on assignment #3
(effectiveness) and #4 (impact & improvements), while it awaits the outcome
of the outreach to the European Data Protection Board (EDPB) by ICANN org
in relation to proposals that would require access to registration data.

As has been communicated previously, Michael Palage will be confirming his
resignation as Chair of this group to the Council.

Here, the Council will discuss the write up and consider next steps,
including the approach to identifying a new Chair.

5.1 ? Introduction of topic (Michael Palage, Chair of the Registration Data
Accuracy Scoping Team)

5.2 - Discussion

5.3 ? Next steps



*Item 6. COUNCIL DISCUSSION - Proposed updates to the GNSO Operating
Procedures - Working Group Self-Assessment & GNSO Statement of Interest
Procedures (15 minutes)*

In order to perform work that is focused on structural, procedural, and
process improvements, and specifically not policy development, the GNSO
Council initiated the Council Committee for Overseeing and Implementing
Continuous Improvement (CCOICI) pilot to focus on work that falls into
these areas. The pilot specifically consists of two topics: a review of the
Working Group Self-Assessment and a review of the GNSO Statements of
Interest (SOI) requirements .

The CCOICI has reviewed the GNSO Working Group Self-Assessment (WGSA)
survey and has proposed several recommendations and updates to the
documentation. The CCOICI tasked the GNSO Statement of Interest (SOI) Task
Force (TF) to review the current Statement of Interest (SOI) requirements
and as a result of its review it is recommending a different structure. The
CCOICI?s and Task Force proposed recommendations require amendments to the
GNSO Operating Procedures, which requires a public comment
<https://www.icann.org/en/public-comment/proceeding/updates-to-the-gnso-statement-of-interest-soi-procedures-and-requirements-09-09-2022>
proceeding.

Here, the Council will receive a briefing on the recommended changes and
potential changes to the GNSO Operating Procedures.

6.1 ? Introduction of topic (Olga Cavalli, Chair of the CCOICI and CCOICI
liaison to the GNSO SOI TF)

6.2 ? Council discussion

6.3 ? Next steps



*Item 7: COUNCIL DISCUSSION - PDP Improvements Tracker - Review of Format
(10 minutes)*

During the ICANN73 wrap up, the Council discussed a number of parallel
conversations that have emerged since implementing PDP 3.0, identifying
other aspects of the PDP where improvements could be considered. In
addition, there are a number of projects on the Council?s Action Decision
Radar (ADR) related to PDP improvements which will need to be addressed at
some point in the future.

To provide the Council with a clear picture of these different parallel
initiatives and projects, and to avoid overlap and ensure complementarity,
the staff support team developed a discussion paper
<https://gnso.icann.org/sites/default/files/policy/2022/draft/draft-gnso-pdp-improvements-discussion-paper-25apr22-en.pdf>.
In addition to an overview of the different initiatives and projects, the
paper also suggests a possible approach for managing these different
initiatives by focusing on 1) which elements could be implemented with
relatively minimal effort, 2) which elements could be implemented with some
effort, 3) which elements need careful planning and consideration before
these can be implemented. After reviewing a draft of the PDP Improvements
Tracker
<https://gnso.icann.org/sites/default/files/policy/2022/draft/draft-pdp-improvements-tracker-overview-7jun22-en.pdf>
during a series of Council meetings, no objections were received to track
and manage the work in the suggested manner.

As a first step towards the substantive review of the items in the tracker,
Council leadership worked with the staff support team to develop a survey
to obtain initial input from Council members as well as Stakeholder Group
and Constituency leadership that will help inform the substantive review of
the proposed improvements and next steps. A sample of the survey was
circulated to the Council list in advance of the August meeting where the
survey, approach, and next steps were discussed.

Having heard no disagreement, the survey was launched shortly after the
Council meeting. The results of the survey are expected to be considered
during the GNSO working session at ICANN75.

Here, the Council, having discussed the topic during the working session,
will consider next steps.

7.1 ? Introduction of topic (Council leadership)

7.2 ? Council discussion

7.3 ? Next steps



*Item 8: COUNCIL DISCUSSION - Whois Disclosure System (15 minutes)*

The proposed design of the Whois Disclosure System will have been published
prior to ICANN75 and will be presented on Saturday of ICANN75, and the
small team and Council will have had an initial discussion during the
session immediately following the ICANN Org presentation in order to review
the proposed design and consider next steps.

The Council is scheduled to discuss the Whois Disclosure System with the
Board during its joint session on Tuesday.

Here, the Council will seek to distill and discuss the conversations with
ICANN org, the small team, GAC, and the Board and determine next steps.

8.1 ? Introduction of topic (Sebastien Ducos, Council vice-chair and lead
of the EPDP Phase 2 small team)

8.2 ? Council discussion

8.3 ? Next steps



*Item 9: COUNCIL DISCUSSION - Update from the UASG (15 minutes)*

The mission of the Universal Acceptance Steering Group (UASG) is to promote
and work towards a future where all domain names and all email addresses
work in all software applications. With the GNSO?s work on enabling the
application for new gTLDs and developing policy recommendations related to
internationalized domain names, universal acceptance is an important factor
for the work of the GNSO.

The UASG is planning a Universal Acceptance (UA) day in February 2023 and
is seeking the participation of the various community groups. The UASG is
hopeful that the GNSO will be able to contribute to the effort and help
promote UA adoption.

Here, Dr. Ajay Data, Chair of the UASG, will provide an update on the
progress of the UASG and discuss the ways in which the GNSO might be able
to help support the planned UA day.

9.1 ? Introduction of topic (Council leadership)

9.2 ? Presentation (Dr. Ajay Data, Chair of the UASG)

9.3 ? Council discussion

9.4 ? Next steps



*Item 10: ANY OTHER BUSINESS (20 minutes)*

10.1 ? Confirmation of approach for term limits for the GNSO liaison to the
GAC

10.2 ? Update - Potential changes to the Standing Committee for ICANN
Budget & Operations (SCBO)

10.3 ? Farewell to outgoing Councilors (*Flip Petillion, Juan Manuel Rojas,
Maxim Alzoba, Olga Cavalli, Philippe* *Fouquart*)

10.4 - Open microphone



_______________________________

Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11,
Section 11.3(i))

See https://www.icann.org/resources/pages/governance/bylaws-en/#article11.

Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating
Procedures, Section 4.4)

See
https://gnso.icann.org/sites/default/files/file/field-file-attach/op-procedures-30jan18-en.pdf



References for Coordinated Universal Time of 05:15 UTC

Local time between March and November in the NORTHERN hemisphere

----------------------------------------------------------------------------

California, USA (PDT) UTC-7  (Tuesday) 22:15

San Jos?, Costa Rica (CST) UTC-6  (Tuesday) 23:15

New York/Washington DC, USA (EDT) UTC-4  01:15

Buenos Aires, Argentina (ART) UTC-3  02:15

Rio de Janeiro, Brazil (BRT) UTC-3  02:15

London, United Kingdom (BST) UTC+1 06:15

Kinshasa, Democratic Republic of Congo (WAT) UTC+1 06:15

Paris, France (CEST) UTC+2 07:15

Moscow, Russia (MSK) UTC+3 08:15

Singapore (SGT) UTC+8  13:15

Melbourne, Australia (AEST) UTC+10  15:15

 ----------------------------------------------------------------------------

DST starts on Sunday 27 March 2022, 2:00 or 3:00 local time (with
exceptions) for EU countries and on Sunday 13 March 2022 for the US.

DST ends on Sunday 30 October 2022 for EU countries, and on Sunday 06
November 2022 for the US.

----------------------------------------------------------------------

For other places see http://www.timeanddate.com and
https://tinyurl.com/bdpud5r3.
Draft GNSO Council Agenda 21 September 2022 -

*Part II (Admin)*



Please note that all documents referenced in the agenda have been gathered
on a Wiki page for convenience and easier access:
https://community.icann.org/x/jYGkD.



This agenda was established according to the GNSO Operating Procedures
<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-procedures-24oct19-en.pdf>
v3.5, updated on 24 October 2019

For convenience:

   - An excerpt of the ICANN Bylaws defining the voting thresholds is
   provided in Appendix 1 at the end of this agenda.
   - An excerpt from the Council Operating Procedures defining the absentee
   voting procedures is provided in Appendix 2 at the end of this agenda.



GNSO Council meeting held in Kuala Lumpur, Malaysia 15:30-16:00 MYT:
https://tinyurl.com/yc2uwm9z



Coordinated Universal Time: 07:30-08:00 UTC



00:30 Los Angeles; 03:30 Washington DC; 08:30 London; 09:30 Paris; 10:30
Moscow; 17:30 Melbourne



*GNSO Council Meeting Remote Participation: (TBD)*

Councilors should notify the GNSO Secretariat in advance if they will not
be able to attend and/or need a dial out call.

___________________________________

*Item 1: Seating of the 2022-2023 Council (20 minutes)*



1.1 - Roll Call



1.2 - Statements of Interest



INCOMING COUNCILORS:



Anne Aikman-Scalese: SOI <https://community.icann.org/x/W4MKAQ> Non-Voting
NomCom Appointee

Bruna Martins dos Santos: SOI <https://community.icann.org/x/iBvwAw>
Non-Commercial Stakeholder Group (NCSG)

Nacho Amadoz: SOI <https://community.icann.org/x/tYIlBw> Registries
Stakeholder Group (RySG)

Osvaldo Novoa: SOI <https://community.icann.org/x/HgbPAQ> Internet Service
Providers and Connectivity Providers (ISPCP)

Susan Payne: SOI <https://community.icann.org/x/sLbhAg> Intellectual
Property Constituency (IPC)



1.3 - Review / Amend Agenda



*Item 2. Election of the Chair (20 minutes)*



One nomination was received for this position from Sebastien Ducos of the
Contracted Party House. Sebastien circulated his candidate statement to the
GNSO Council on [date]. Here the GNSO Council will proceed to hold the
election for its Chair for 2022-2023, according to the GNSO Operating
Procedures (note Section 2.2 of the GNSO Operating Procedures on Officer
Elections: Chair and Vice-Chairs (see Appendix 1 below)).



*Item 3. Election of GNSO Council Vice Chair 2021-2022 (5 minutes)*

Non-Contracted Party House - TBD

Contracted Party House - Greg DiBiase



*Item 4. ANY OTHER BUSINESS (10 minutes)*



4.1 - TBD



*Appendix 1: Excerpt from GNSO Operating Procedures (Section 2.2)*

2.2        https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf

Officer Elections:  Chair and Vice-Chairs



The GNSO Council shall select the GNSO Chair and two Vice-Chairs as follows:

   1. The GNSO Chair shall be elected by a 60 percent vote of each house.
   2. Each house will be allowed to nominate one candidate for GNSO Council
   Chair. Each house is responsible for determining how to nominate its
   candidate.  A candidate for GNSO Council Chair does not need to be a member
   of a house, but must be a current or incoming member of the GNSO Council.
   Should a Chair be elected from outside of the houses that Chair will be a
   non-voting Chair.

a.                   All ballots will include the ?none of the above?
option.  In the event that a 60 percent vote of each house selects the
?none of the above? option, each house will commence a new nomination
period of not longer than 15 days. An election for the new nominees will be
scheduled for no sooner than 30 days after the unsuccessful vote.

b.                   In the case of a tie for the most votes between the
two candidates, or between a candidate and ?none of above,? a second
election will be held no sooner than 30 days.  The candidates shall remain
the same for this second election.  In the case this second election also
results in a tie, each house will commence a new nomination period of not
longer than 15 days. An election for the new nominees will be rescheduled
for no sooner than 30 days after the unsuccessful vote.

c.                   The leading candidate will be defined as the one with
the highest score. The score is calculated by adding together the voting
percentages attained from each house.  The highest percentage attainable in
each house is 100. Thus, the maximum score a candidate can achieve is 200
as a result of attaining 100 percent of the votes from the contracted party
house and 100 percent from the non-contracted party house (100 percent +
100 percent = score of 200).  In case neither candidate reaches the 60
percent of each house threshold, a second ballot will be held between the
leading candidate and ?none of the above.?

d.                   In case neither candidate reaches the 60 percent of
each house threshold and the candidates do not tie, a second runoff ballot
will be held between the leading candidate and ?none of the above.?

e.                   If the single candidate does not reach the 60 percent
of each house threshold in the runoff ballot, then each house will commence
a new nomination period of not longer than 15 days.  An election for the
new nominees will be rescheduled for no sooner than 30 days after the
unsuccessful runoff ballot.

   1. Each house shall select a Council Vice-Chair from within its
   respective house.
   2. A Chair may not be a member of the same Stakeholder Group of either
   of the Vice-Chairs.
   3. The Chair and Vice-Chairs shall retain their votes (if any) in their
   respective houses (if any).
   4. In the event that the GNSO Council has not elected a GNSO Council
   Chair by the end of the previous Chair?s term, the Vice-Chairs will serve
   as Interim GNSO Co- Chairs to jointly oversee the new Chair election and
   conduct Council business until a successful election can be held.   In the
   event that one or both Vice-Chairs? terms ends concurrently with the term
   of the previous Chair, the procedures described in Section 2.2.1 below
   shall apply.
   5. The Council shall inform the Board and the Community appropriately
   and post the election results on the GNSO website within 2 business days
   following each election and runoff ballot, whether successful or
   unsuccessful.



*Appendix 2: GNSO Council Voting Thresholds (**ICANN Bylaws,*
<https://www.icann.org/resources/pages/governance/bylaws-en/#article11>*
Article 11, Section 3)*

(i) Except as otherwise specified in these Bylaws, Annex A, Annex A-1 or
Annex A-2 hereto, or the GNSO Operating Procedures, the default threshold
to pass a GNSO Council motion or other voting action requires a simple
majority vote of each House. The voting thresholds described below shall
apply to the following GNSO actions:

(i) Create an Issues Report: requires an affirmative vote of more than
one-fourth (1/4) vote of each House or majority of one House.

(ii) Initiate a Policy Development Process ("*PDP*") Within Scope (as
described in Annex A): requires an affirmative vote of more than one-third
(1/3) of each House or more than two-thirds (2/3) of one House.

(iii) Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO
Supermajority (as defined in Section 11.3(i)(xix)).

(iv) Approve a PDP Team Charter for a PDP Within Scope: requires an
affirmative vote of more than one-third (1/3) of each House or more than
two-thirds (2/3) of one House.

(v) Approve a PDP Team Charter for a PDP Not Within Scope: requires an
affirmative vote of a GNSO Supermajority.

(vi) Changes to an Approved PDP Team Charter: For any PDP Team Charter
approved under (iv) or (v) above, the GNSO Council may approve an amendment
to the Charter through a simple majority vote of each House.

(vii) Terminate a PDP: Once initiated, and prior to the publication of a
Final Report, the GNSO Council may terminate a PDP only for significant
cause, upon a motion that passes with a GNSO Supermajority Vote in favor of
termination.

(viii) Approve a PDP Recommendation Without a GNSO Supermajority: requires
an affirmative vote of a majority of each House and further requires that
one GNSO Council member representative of at least 3 of the 4 Stakeholder
Groups supports the Recommendation.

(ix) Approve a PDP Recommendation With a GNSO Supermajority: requires an
affirmative vote of a GNSO Supermajority,

(x) Approve a PDP Recommendation Imposing New Obligations on Certain
Contracting Parties: where an ICANN contract provision specifies that "a
two-thirds vote of the council" demonstrates the presence of a consensus,
the GNSO Supermajority vote threshold will have to be met or exceeded.

(xi) Modification of Approved PDP Recommendation: Prior to Final Approval
by the Board, an Approved PDP Recommendation may be modified or amended by
the GNSO Council with a GNSO Supermajority vote.

(xii) Initiation of an Expedited Policy Development Process ("*EPDP*"):
requires an affirmative vote of a GNSO Supermajority.

(xiii) Approve an EPDP Team Charter: requires an affirmative vote of a GNSO
Supermajority.

(xiv) Approval of EPDP Recommendations: requires an affirmative vote of a
GNSO Supermajority.

(xv) Approve an EPDP Recommendation Imposing New Obligations on Certain
Contracting Parties: where an ICANN contract provision specifies that "a
two-thirds vote of the council" demonstrates the presence of a consensus,
the GNSO Supermajority vote threshold will have to be met or exceeded.

(xvi) Initiation of a GNSO Guidance Process ("*GGP*"): requires an
affirmative vote of more than one-third (1/3) of each House or more than
two-thirds (2/3) of one House.

(xvii) Rejection of Initiation of a GGP Requested by the Board: requires an
affirmative vote of a GNSO Supermajority.

(xviii) Approval of GGP Recommendations: requires an affirmative vote of a
GNSO Supermajority.

(xix) A "*GNSO Supermajority*" shall mean: (A) two-thirds (2/3) of the
Council members of each House, or (B) three-fourths (3/4) of the Council
members of one House and a majority of the Council members of the other
House.

https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf

Appendix 1 GNSO Council Voting Results table

*Absentee Voting Procedures *
*https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf*
<https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf>

*4.4 Absentee Voting*

4.1.1        Applicability



Absentee voting is permitted for the following limited number of Council
motions or measures.

   1. Initiate a Policy Development Process (PDP);
   2. Approve a PDP recommendation;
   3. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN
   Bylaws;
   4. Fill a Council position open for election.



4.1.2    Absentee ballots, when permitted, must be submitted within the
announced time limit, which shall be 72 hours from the meeting?s
adjournment.  In exceptional circumstances, announced at the time of the
vote, the Chair may reduce this time to 24 hours or extend the time to 7
calendar days, provided such amendment is verbally confirmed by all
Vice-Chairs present.

4.1.3    The GNSO Secretariat will administer, record, and tabulate
absentee votes according to these procedures and will provide reasonable
means for transmitting and authenticating absentee ballots, which could
include voting by telephone, e- mail, web-based interface, or other
technologies as may become available.

4.1.4    Absentee balloting does not affect quorum requirements.













_______________________________________________
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: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20220912/864ede17/attachment.htm>

From Kathy at KathyKleiman.com  Mon Sep 12 16:35:23 2022
From: Kathy at KathyKleiman.com (Kathy Kleiman)
Date: Mon, 12 Sep 2022 09:35:23 -0400
Subject: [NCSG-PC] Fwd: [gnso-chairs] GNSO/GAC dialogue on closed
 generics: selection of GNSO participants
In-Reply-To: <CADAEEV0wY-j0K_GH_Cp3waaO+c-AANNTrPA0QN5jduY2XTA2vA@mail.gmail.com>
References: <23150_1662120078_6311F08E_23150_224_1_fa943370c01643e3b2bc7375fc86e561@orange.com>
 <CAM8DdeX1py8C7wf+Wya4_99yCesi=bekspuRCMB+aL_Uz7yzvw@mail.gmail.com>
 <3cb39725-0fb1-877c-1f6b-f1433f323de0@KathyKleiman.com>
 <CAM8DdeXjXp0mOUR-mumSt9OgkGCUCHx6oXt3naumsKN922HTPA@mail.gmail.com>
 <CADAEEV0wY-j0K_GH_Cp3waaO+c-AANNTrPA0QN5jduY2XTA2vA@mail.gmail.com>
Message-ID: <42c10ea8-b704-ead6-3977-bbc4b26bfbb1@KathyKleiman.com>

Hi Bruna and All,

Apologies for the delay.? I am now "on the road" with the book tour.? 
Just finished two big event with lots of travel in between (why does the 
US have to be so big?).? Everyone loved the story of the six women who 
programmed the world's first general-purpose, programmable, 
all-electronic computer, so all is well!? Lots of teachers, librarians, 
students, tech folks and community members which was great.

Since Closed Generics was supposed to be on the agenda for KL and then 
was removed from the agenda for KL, I talked with Bruna and we agreed 
that I did not have to cancel my speech commitments in the US (tx you!)? 
I tried to fly out on Saturday, but could not, so I am flying out Sunday 
and will arrive on Monday night. I will be at the meeting on Tuesday, 
Wednesday, Thursday and have already started setting up post-meeting 
discussions on Friday (I'm there until almost midnight).

/*Now that an informal Closed Generics meeting appears to be back on the 
agenda for KL, could our Councilors ask it be scheduled on Wednesday or 
Thursday? */Both days are not as busy as earlier days and should have 
ample room for a meet and greet (which appears to be the idea for the 
Closed Generic meeting to take place). With the short notice, I am sure 
ICANN Staff will want to organize when incoming members can join the 
meeting...? I hope so!? Tx so much for letting them know.

Tx for asking, Bruna!

Best regards and looking forward to seeing you in KL,

Kathy

On 9/8/2022 12:19 PM, Bruna Martins dos Santos wrote:
> Hello all,
>
> Jumping in here just to ask whether we know about?the final date for 
> the meeting at ICANN75 if theres one. I think Kathy wont be there for 
> the full meeting, right @Kathy Kleiman <mailto:kathy at dnrc.tech>??
>
> best,
> B
>
> On Wed, Sep 7, 2022 at 10:54 PM Tomslin Samme-Nlar 
> <mesumbeslin at gmail.com> wrote:
>
>     Hi Kathy,
>
>     Thanks for volunteering. Really?appreciate it because with the
>     short window and skills required,? it would have been very
>     difficult to get a volunteer. So, thank you!
>
>     Regarding your recommendation that we appoint an official
>     alternate, I am afraid that is not possible as stipulated on the
>     candidate guidance document I attached to my previous email. And
>     more?we are now also past the negotiation phase in the Council.
>     The guidance document is now the rule book for appointing members.
>     What we could do is to pull you out as member in the event that
>     you can't attend and appoint George instead.
>
>     Please let us know and apologies that Manju and I were unable to
>     secure an official alternate for NCSG during the drafting and
>     discussion of the text.
>
>     Warmly,
>     Tomslin
>
>     On Thu, 8 Sept 2022, 00:01 Kathy Kleiman, <Kathy at kathykleiman.com>
>     wrote:
>
>         Hi Tomslin and All,
>
>         I would like to recommend that I be appointed with George
>         Sadowsky as an unofficial alternate. George as you know as an
>         ICANN Board member for many years. But few know that before
>         that he was a founding member of NCUC (NCSG would not be
>         created for about decade after).? In 1999, George was with New
>         York University as IT director and joined us in founding NCUC
>         and attending early meetings. We were his initial link to ICANN!
>
>         He has now applied to join NCSG.? Some Board members leave
>         ICANN forever, but those who remain, tend to go back to the
>         groups they came from. I hope we will approve his membership.
>         And then I hope we can allow him to work with me on the Closed
>         Generics issues. He is an expert on this issue from his time
>         on the Board and knows how difficult and complicated it is.?
>         He helped make sure we heard from noncommercial organizations
>         around the world before passing the first ban on Closed
>         Generics. Later, when the Subsequent Procedures Working Group
>         was looking closely at this issue, George (at my invitation)
>         joined the Working Group to again share the complexities and
>         potential problems of Closed Generics from his perspective
>         (which include his more recent experience with many United
>         Nations organizations).
>
>         While technically the job is supposed to be for one person, it
>         is too big for one volunteer (note: some attorneys will be
>         paid by their clients and law firms to participate fully in
>         this new group and there is a reason for that). ALAC plans to
>         appoint a primary person and a backup person if the primary
>         person cannot attend a meeting or discussion.? Since I will be
>         on book tour with my new book about the ENIAC Programmers,
>         */Proving Ground, /*I think it would be good idea for us to
>         have a similar arrangement. We don't want to miss a single
>         Closed Generic meeting!
>
>         Best and tx,
>
>         Kathy
>
>         On 9/6/2022 8:41 AM, Tomslin Samme-Nlar wrote:
>>         FYI, PC.
>>
>>         I am still waiting on guidance from Bruna but I just wanted
>>         to bring to your attention this statement in the meantime "
>>         /*This group would ideally have a first informal meeting
>>         during ICANN 75, so we would appreciate if you would let us
>>         know the name of your representative ideally by September
>>         19^th */."
>>         It means we have only 2 weeks to name a representative for
>>         this. I don't think it'll be a problem since Kathy Kleinman
>>         had indicated interest already and was granted funding to KL
>>         based on that interest but I thought I'd flag the urgency to
>>         the whole committee.
>>
>>         Warmly,
>>         Tomslin
>>         @LinkedIn: https://www.linkedin.com/in/tomslin/
>>
>>
>>         ---------- Forwarded message ---------
>>         From: *philippe.fouquart--- via Gnso-chairs*
>>         <gnso-chairs at icann.org>
>>         Date: Fri, 2 Sept 2022 at 22:01
>>         Subject: [gnso-chairs] GNSO/GAC dialogue on closed generics:
>>         selection of GNSO participants
>>         To: mason.cole at appdetex.com <mason.cole at appdetex.com>,
>>         wolf-ulrich.knoben at t-online.de
>>         <wolf-ulrich.knoben at t-online.de>, lschulman at inta.org
>>         <lschulman at inta.org>, bruna.mrtns at gmail.com
>>         <bruna.mrtns at gmail.com>, plommer at gmail.com
>>         <plommer at gmail.com>, benakin at gmail.com <benakin at gmail.com>,
>>         aheineman at godaddy.com <aheineman at godaddy.com>,
>>         sdemetriou at verisign.com <sdemetriou at verisign.com>,
>>         chair at rysg.info <chair at rysg.info>, secretariat at rysg.info
>>         <secretariat at rysg.info>, secretariat at icannregistrars.org
>>         <secretariat at icannregistrars.org>
>>         Cc: gnso-secs at icann.org <gnso-secs at icann.org>,
>>         gnso-chairs at icann.org <gnso-chairs at icann.org>, council at gnso
>>         icann. org <council at gnso.icann.org>
>>
>>
>>         Dear SG/C leaders,
>>
>>         Hope this email finds you all well.
>>
>>         As you know, following an invitation from the Board, the GNSO
>>         and the GAC will enter into a dialogue to ?formulate a
>>         workable framework to identify and handle closed generic
>>         applications for the immediate next round of new gTLDs?, and
>>         in this dialogue we will be joined by ALAC.
>>
>>         Council leadership would like to invite each Stakeholder
>>         Group to select a representative for this dialogue. This
>>         group is would ideally have a first informal meeting during
>>         ICANN 75, so we would appreciate if you would let us know the
>>         name of your representative ideally by September 19^th .
>>
>>         The attached document provides the guidance for this
>>         appointment.
>>
>>         I would finally like to draw your attention to the spirit of
>>         involvement in this effort:
>>
>>           * the framework discussion will focus on options other than
>>             the two endpoint positions (i.e. no closed generics at
>>             all; closed generics without restrictions) as per the
>>             Board?s Proposed Parameters for Dialogue
>>           * the participants will "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.? (Council
>>             small team report)
>>
>>         Looking forward to hearing from you, and wishing you all safe
>>         travels to KL.
>>
>>         Best regards,
>>
>>         Philippe
>>
>>         Board/GNSO correspondence:
>>
>>           * 6 Mar 2022 Letter from Maarten Botterman to Manal Ismail
>>             and Philippe Fouquart
>>             <https://www.icann.org/en/system/files/correspondence/botterman-to-ismail-fouquart-06mar22-en.pdf>??
>>             including the framing paper
>>           * 27 April 2022 Letter from Philippe Fouquart to Maarten
>>             Botterman
>>             <https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-27apr22-en.pdf>
>>           * 19 May 2022 Letter from Maarten Botterman to Philippe
>>             Fouquart
>>             <https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-19may22-en.pdf>
>>           * 29 Jun 2022 Letter from Philippe Fouquart to Maarten
>>             Botterman and Manal Ismail
>>             <https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-ismail-29jun22-en.pdf>
>>           * 25 Jul 2022 Letter from Maarten Botterman to Philippe
>>             Fouquart and Manal Ismail
>>             <https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-ismail-25jul22-en.pdf>
>>
>>         Council small team report:
>>         https://gnso.icann.org/sites/default/files/policy/2022/draft/draft-closed-generics-small-team-report-24jun22-en.pdf
>>
>>
>>         _________________________________________________________________________________________________________________________
>>
>>         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.
>>         _______________________________________________
>>         Gnso-chairs mailing list
>>         Gnso-chairs at icann.org
>>         https://mm.icann.org/mailman/listinfo/gnso-chairs
>>         _______________________________________________
>>         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
>         _______________________________________________
>         NCSG-PC mailing list
>         NCSG-PC at lists.ncsg.is
>         https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
>     _______________________________________________
>     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 <https://www.humboldt-foundation.de/>
>
> Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum 
> Berlin f?r Sozialforschung (WZB) <https://wzb.eu/en>
>
> Member | Coaliz?o Direitos na Rede <https://direitosnarede.org.br/>
> Chair?| Non-Commercial Stakeholder Group at ICANN 
> <https://gnso.icann.org/en/about/stakeholders-constituencies/ncsg>
> Co-Coordinator?| Internet Governance Caucus <https://igcaucus.org/>
>
> Twitter: @boomartins <https://twitter.com/boomartins>?// Skype: 
> bruna.martinsantos
> _bruna.martinsdossantos at wzb.eu_?and bruna.mrtns at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20220912/80df8921/attachment.htm>

From Kathy at KathyKleiman.com  Mon Sep 12 17:40:49 2022
From: Kathy at KathyKleiman.com (Kathy Kleiman)
Date: Mon, 12 Sep 2022 10:40:49 -0400
Subject: [NCSG-PC] Fwd: [gnso-chairs] GNSO/GAC dialogue on closed
 generics: selection of GNSO participants
In-Reply-To: <CAM8DdeWowM9aOKdvtN0tDEjk+Xc8YHntQ4d6fG1Dz70-vaKTNQ@mail.gmail.com>
References: <23150_1662120078_6311F08E_23150_224_1_fa943370c01643e3b2bc7375fc86e561@orange.com>
 <CAM8DdeX1py8C7wf+Wya4_99yCesi=bekspuRCMB+aL_Uz7yzvw@mail.gmail.com>
 <3cb39725-0fb1-877c-1f6b-f1433f323de0@KathyKleiman.com>
 <CAM8DdeXjXp0mOUR-mumSt9OgkGCUCHx6oXt3naumsKN922HTPA@mail.gmail.com>
 <bfa31191-6909-cffe-24c3-c15329caf63d@KathyKleiman.com>
 <CAM8DdeWowM9aOKdvtN0tDEjk+Xc8YHntQ4d6fG1Dz70-vaKTNQ@mail.gmail.com>
Message-ID: <474b9052-cf58-6d9c-bdf9-db4c1254353d@KathyKleiman.com>

Great Tomslin, and tx you!

Please pass my name along - with a special request for the first meeting 
(or informal meeting) of this group on Wednesday or Thursday of the 
ICANN meeting!

Best, Kathy

On 9/12/2022 4:25 AM, Tomslin Samme-Nlar wrote:
> Hi Kathy,
>
> My bad. I misunderstood the request. I am happy with the proposal of 
> an unofficial alternate.
>
> Warmly,
> Tomslin
>
> On Sat, 10 Sept 2022, 00:47 Kathy Kleiman, <Kathy at kathykleiman.com> wrote:
>
>     Hi Tomslin and All,
>
>     Tx for your support and your response.? I should note that my
>     request below is not for an "official alternate," but an
>     "/unofficial alternate/*" *and I'm glad Stephanie supports.? ALAC
>     is already planning to do so, and it is a very wise thing for us
>     to do as well. I'm afraid I must insist.
>
>     ICANN in these small groups can be all consuming and many people
>     who participate on these teams are paid fulltime to do so (as I
>     was when I was Director of Policy for .ORG). Our IPC friend, when
>     they appoint Paul McGrady, will certainly be paid for his
>     participation - and he does work for Amazon.
>
>     Like ALAC, we are really the only true volunteers in this
>     process.? Accordingly, we cannot drop everything and abandon the
>     work that we do to put bread on our tables.? We also can't go
>     crazy trying to make meetings that may conflict with requirements
>     of our jobs and families.? Unfair requirements is why NCSG and
>     NCUC over the years has not participated in many roles of
>     leadership and involvement across ICANN.
>
>     So the only thing that makes sense is reasonable backup- an
>     /unofficial/ alternate.? It may not be part of the official rules,
>     but it is a "reasonable accommodation" for parents and mothers and
>     "reasonable accommodation" is a legal term of art in the US - for
>     making sure that everyone can participate regardless of circumstances.
>
>     ALAC will be taking these approach - an informal alternate.
>     Together (and this is not your job or Manju's), we can make the
>     sound argument that true volunteers need informal alternates to
>     cover meetings the main representative simply can't make - and
>     meetings too important to miss (which is any of them).? ICANN
>     needs its "watchers" in place...
>
>     For my peace of mind, as I start a busy book tour (we launched on
>     Wednesday in NYC at the engineering school of Cooper Union!), we
>     will need this unofficial alternate.? It is the right thing to do
>     for NCSG and good precedent for days to come.
>
>     Best, Kathy
>
>     On 9/7/2022 4:54 PM, Tomslin Samme-Nlar wrote:
>>     Hi Kathy,
>>
>>     Thanks for volunteering. Really?appreciate it because with the
>>     short window and skills required,? it would have been very
>>     difficult to get a volunteer. So, thank you!
>>
>>     Regarding your recommendation that we appoint an official
>>     alternate, I am afraid that is not possible as stipulated on the
>>     candidate guidance document I attached to my previous email. And
>>     more?we are now also past the negotiation phase in the Council.
>>     The guidance document is now the rule book for appointing
>>     members. What we could do is to pull you out as member in the
>>     event that you can't attend and appoint George instead.
>>
>>     Please let us know and apologies that Manju and I were unable to
>>     secure an official alternate for NCSG during the drafting and
>>     discussion of the text.
>>
>>     Warmly,
>>     Tomslin
>>
>>     On Thu, 8 Sept 2022, 00:01 Kathy Kleiman,
>>     <Kathy at kathykleiman.com> wrote:
>>
>>         Hi Tomslin and All,
>>
>>         I would like to recommend that I be appointed with George
>>         Sadowsky as an unofficial alternate. George as you know as an
>>         ICANN Board member for many years. But few know that before
>>         that he was a founding member of NCUC (NCSG would not be
>>         created for about decade after).? In 1999, George was with
>>         New York University as IT director and joined us in founding
>>         NCUC and attending early meetings. We were his initial link
>>         to ICANN!
>>
>>         He has now applied to join NCSG.? Some Board members leave
>>         ICANN forever, but those who remain, tend to go back to the
>>         groups they came from. I hope we will approve his membership.
>>         And then I hope we can allow him to work with me on the
>>         Closed Generics issues. He is an expert on this issue from
>>         his time on the Board and knows how difficult and complicated
>>         it is.? He helped make sure we heard from noncommercial
>>         organizations around the world before passing the first ban
>>         on Closed Generics. Later, when the Subsequent Procedures
>>         Working Group was looking closely at this issue, George (at
>>         my invitation) joined the Working Group to again share the
>>         complexities and potential problems of Closed Generics from
>>         his perspective (which include his more recent experience
>>         with many United Nations organizations).
>>
>>         While technically the job is supposed to be for one person,
>>         it is too big for one volunteer (note: some attorneys will be
>>         paid by their clients and law firms to participate fully in
>>         this new group and there is a reason for that). ALAC plans to
>>         appoint a primary person and a backup person if the primary
>>         person cannot attend a meeting or discussion. Since I will be
>>         on book tour with my new book about the ENIAC Programmers,
>>         */Proving Ground, /*I think it would be good idea for us to
>>         have a similar arrangement. We don't want to miss a single
>>         Closed Generic meeting!
>>
>>         Best and tx,
>>
>>         Kathy
>>
>>         On 9/6/2022 8:41 AM, Tomslin Samme-Nlar wrote:
>>>         FYI, PC.
>>>
>>>         I am still waiting on guidance from Bruna but I just wanted
>>>         to bring to your attention this statement in the meantime "
>>>         /*This group would ideally have a first informal meeting
>>>         during ICANN 75, so we would appreciate if you would let us
>>>         know the name of your representative ideally by September
>>>         19^th */."
>>>         It means we have only 2 weeks to name a representative for
>>>         this. I don't think it'll be a problem since Kathy Kleinman
>>>         had indicated interest already and was granted funding to KL
>>>         based on that interest but I thought I'd flag the urgency to
>>>         the whole committee.
>>>
>>>         Warmly,
>>>         Tomslin
>>>         @LinkedIn: https://www.linkedin.com/in/tomslin/
>>>
>>>
>>>         ---------- Forwarded message ---------
>>>         From: *philippe.fouquart--- via Gnso-chairs*
>>>         <gnso-chairs at icann.org>
>>>         Date: Fri, 2 Sept 2022 at 22:01
>>>         Subject: [gnso-chairs] GNSO/GAC dialogue on closed generics:
>>>         selection of GNSO participants
>>>         To: mason.cole at appdetex.com <mason.cole at appdetex.com>,
>>>         wolf-ulrich.knoben at t-online.de
>>>         <wolf-ulrich.knoben at t-online.de>, lschulman at inta.org
>>>         <lschulman at inta.org>, bruna.mrtns at gmail.com
>>>         <bruna.mrtns at gmail.com>, plommer at gmail.com
>>>         <plommer at gmail.com>, benakin at gmail.com <benakin at gmail.com>,
>>>         aheineman at godaddy.com <aheineman at godaddy.com>,
>>>         sdemetriou at verisign.com <sdemetriou at verisign.com>,
>>>         chair at rysg.info <chair at rysg.info>, secretariat at rysg.info
>>>         <secretariat at rysg.info>, secretariat at icannregistrars.org
>>>         <secretariat at icannregistrars.org>
>>>         Cc: gnso-secs at icann.org <gnso-secs at icann.org>,
>>>         gnso-chairs at icann.org <gnso-chairs at icann.org>, council at gnso
>>>         icann. org <council at gnso.icann.org>
>>>
>>>
>>>         Dear SG/C leaders,
>>>
>>>         Hope this email finds you all well.
>>>
>>>         As you know, following an invitation from the Board, the
>>>         GNSO and the GAC will enter into a dialogue to ?formulate a
>>>         workable framework to identify and handle closed generic
>>>         applications for the immediate next round of new gTLDs?, and
>>>         in this dialogue we will be joined by ALAC.
>>>
>>>         Council leadership would like to invite each Stakeholder
>>>         Group to select a representative for this dialogue. This
>>>         group is would ideally have a first informal meeting during
>>>         ICANN 75, so we would appreciate if you would let us know
>>>         the name of your representative ideally by September 19^th .
>>>
>>>         The attached document provides the guidance for this
>>>         appointment.
>>>
>>>         I would finally like to draw your attention to the spirit of
>>>         involvement in this effort:
>>>
>>>           * the framework discussion will focus on options other
>>>             than the two endpoint positions (i.e. no closed generics
>>>             at all; closed generics without restrictions) as per the
>>>             Board?s Proposed Parameters for Dialogue
>>>           * the participants will "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.? (Council
>>>             small team report)
>>>
>>>         Looking forward to hearing from you, and wishing you all
>>>         safe travels to KL.
>>>
>>>         Best regards,
>>>
>>>         Philippe
>>>
>>>         Board/GNSO correspondence:
>>>
>>>           * 6 Mar 2022 Letter from Maarten Botterman to Manal Ismail
>>>             and Philippe Fouquart
>>>             <https://www.icann.org/en/system/files/correspondence/botterman-to-ismail-fouquart-06mar22-en.pdf>??
>>>             including the framing paper
>>>           * 27 April 2022 Letter from Philippe Fouquart to Maarten
>>>             Botterman
>>>             <https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-27apr22-en.pdf>
>>>           * 19 May 2022 Letter from Maarten Botterman to Philippe
>>>             Fouquart
>>>             <https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-19may22-en.pdf>
>>>           * 29 Jun 2022 Letter from Philippe Fouquart to Maarten
>>>             Botterman and Manal Ismail
>>>             <https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-ismail-29jun22-en.pdf>
>>>           * 25 Jul 2022 Letter from Maarten Botterman to Philippe
>>>             Fouquart and Manal Ismail
>>>             <https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-ismail-25jul22-en.pdf>
>>>
>>>         Council small team report:
>>>         https://gnso.icann.org/sites/default/files/policy/2022/draft/draft-closed-generics-small-team-report-24jun22-en.pdf
>>>
>>>
>>>         _________________________________________________________________________________________________________________________
>>>
>>>         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.
>>>         _______________________________________________
>>>         Gnso-chairs mailing list
>>>         Gnso-chairs at icann.org
>>>         https://mm.icann.org/mailman/listinfo/gnso-chairs
>>>         _______________________________________________
>>>         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
>>         _______________________________________________
>>         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: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20220912/7bc606de/attachment.htm>

From mesumbeslin at gmail.com  Tue Sep 20 03:12:07 2022
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Tue, 20 Sep 2022 08:12:07 +0800
Subject: [NCSG-PC] Call for Volunteer: GNSO Guidance Process (GGP)
 Initiation Request for Applicant Support
In-Reply-To: <CAM8DdeU6wigpQ8kteetcD_ndn+x+AN=AH1YFUaPo3+Pecwk4zQ@mail.gmail.com>
References: <CAM8DdeU6wigpQ8kteetcD_ndn+x+AN=AH1YFUaPo3+Pecwk4zQ@mail.gmail.com>
Message-ID: <CAM8DdeXfo+KgukgqTiZcaoJP3MuP2rv-hKTcOJO0doGg9uAcdQ@mail.gmail.com>

Hi PC members,

The deadline for this is now past and the only volunteer who submitted an
interest in this is *Rafik Dammak*

If there are no objections, I will submit his name to staff as our
representative to the GGP. Please let me know by the end of the week since
we're expected to submit the name of the rep next week.

Warmly,
Tomslin

On Wed, 7 Sept 2022, 06:07 Tomslin Samme-Nlar, <mesumbeslin at gmail.com>
wrote:

> Dear NCSG,
>
> During its meeting on 25 August 2022, the GNSO Council approved the GNSO
> Guidance Process (GGP) Initiation Request
> <https://gnso.icann.org/sites/default/files/policy/2022/draft/draft-subpro-ggp-initiation-request-clean-24aug22-en.pdf>
> to perform work on Applicant Support, a topic of interest to NCSG. Each SG
> has been invited to identify *1 Representative to join this Working Group
> *.
>
> Here is the criteria that the GNSO Council considers to be important for
> this GGP:
> *Organizations are encouraged to appoint individuals with skills,
> knowledge and experience pertinent to forming an effective Applicant
> Support Program. Council will provide guidance on the aggregated skill set
> that is needed for the group (for example: grant and reviewing, regional
> DNS participation, DNS marketplace economics, cost-benefit analyses, TLD
> operations, DNS cyber-security, and TLD investment).*
>
> If you meet the above recommended criteria, please email to me your
> expression of interest and copy Andrea (andrea.glandon at icann.or),
> indicating how you meet the criteria above *no later than Friday 16
> September* to give the Policy Committee 2 weeks to review and select.
>
> Members should also note that in addition to the representative we'll
> appoint, the GGP permits Observers to the process. Observers are anyone
> interested in the GGP, who are provided with read-only access to the
> mailing list and are not invited to attend meetings. Those interested to be
> an observer should directly contact the GNSO Secretariat at
> gnso-secs at icann.org to sign up.
>
> Warmly,
> Tomslin
> @LinkedIn: https://www.linkedin.com/in/tomslin/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20220920/f239b33f/attachment.htm>

From adisabolutifeo at gmail.com  Wed Sep 21 07:40:52 2022
From: adisabolutifeo at gmail.com (Bolutife Adisa)
Date: Wed, 21 Sep 2022 05:40:52 +0100
Subject: [NCSG-PC] Nominations received PIR Advisory Council Members
In-Reply-To: <CAM8DdeUHNPTzUAqJHtFchHV8vmk9VNJjO9A=AuwrTgQyRqY0Yw@mail.gmail.com>
References: <CAM8DdeUHNPTzUAqJHtFchHV8vmk9VNJjO9A=AuwrTgQyRqY0Yw@mail.gmail.com>
Message-ID: <087B53A1-D7FA-4EF0-8C68-F356212C95EC@gmail.com>

Hi Tomslin,

Thanks for sharing. 

Seeing they are all excellent candidates, my vote would be for Caleb Ogundele. I believe he can perform in that role.

Best,
Bolutife. 

> On 3. Sep 2022, at 13:19, Tomslin Samme-Nlar <mesumbeslin at gmail.com> wrote:
> 
> ?
> Hi team,
> 
> As discussed, here are the names of those who've self nominated so far:
> 
> Hago Dafalla
> Remmy Nweke
> Poncelet O. Ileleji
> Bukola Oronti
> Caleb Ogundele
> The criteria requested again are as follows:
> Either presently, or in the past, served in a leadership position within the NCSG or an NCSG constituency;
> Contributed and initiated meaningful discussion on the NCUC, NPOC, and/or NCSG mailing lists; and
> Demonstrated knowledge of, or interest in the work of, the Public Interest Registry, and is willing to be an active participant in Public Interest Registry discussions and debates.
>  
> Warmly,
> Tomslin
> @LinkedIn: https://www.linkedin.com/in/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: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20220921/764ab45e/attachment.htm>

From mesumbeslin at gmail.com  Thu Sep 22 12:10:47 2022
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Thu, 22 Sep 2022 17:10:47 +0800
Subject: [NCSG-PC] [Public Comment] Call for volunteers - Registration
 Data Consensus Policy for gTLDs
In-Reply-To: <CAM8DdeUBvPv+VM-h6BNYbJCQMu3RGjfcFRF79NOkakA4tqTmuQ@mail.gmail.com>
References: <CAM8DdeUBvPv+VM-h6BNYbJCQMu3RGjfcFRF79NOkakA4tqTmuQ@mail.gmail.com>
Message-ID: <CAM8DdeVYs05J_ngRZXhPUx3C+=npjbkn216tOchZXcHWnmfjFw@mail.gmail.com>

Hi all,

Just reminding folks that this public comment is open and we are still in
need of volunteers.

Warmly,
Tomslin
@LinkedIn: https://www.linkedin.com/in/tomslin/


On Sun, 28 Aug 2022 at 05:17, Tomslin Samme-Nlar <mesumbeslin at gmail.com>
wrote:

> Dear members,
>
> The public comment period on a proposed Registration Data Consensus Policy
> for gTLDs is now open.
>
> If you still remember, the genesis of this policy is the first-ever
> Expedited Policy Development Process (EPDP) initiated by the GNSO Council
> to determine if the Temp Spec for gTLD Registration Data should become an
> ICANN consensus policy as-is or with modifications, whose recommendations
> ICANN board adopted in 2019. As ICANN Org rightly notes, this "draft
> Registration Data Policy is like no other policy in ICANN's history.... The
> policy touches on some of the most important, complex, and challenging
> issues facing the Internet ecosystem".
>
> The Registration Data Policy Implementation Plan Public Comment
> encompasses 34 policy recommendations from 3 ICANN Board Resolutions:
>
>
>    1.     EPDP Phase 1: Board Resolution in May 2019 (29 recommendations)
>    2.     EPDP Phase 2: Board Resolution in June 2021 (4 recommendations)
>    3.     Supplemental Recommendation 12: Board Resolution in February
>    2022 (1 recommendation)
>
> NCSG was very active and vocal about its positions on these WGs.
>
> The Policy Committee is now calling for volunteers to draft an NCSG
> comment/response for this proceeding which is due for consideration on
> Thursday 20 October 2022 to allow time for filling and submitting the new
> public comment form.
>
> Please let me know off-list if you'd like to volunteer for the comment
> drafting. It'll be nice to have more than one volunteer, including
> new-commers who can use this as an opportunity to learn and be familiar
> with policy work.
>
> More information about the policy status report can be found here :
> https://www.icann.org/en/public-comment/proceeding/registration-data-consensus-policy-for-gtlds-24-08-2022
>
> A draft Google doc for the comment in the guided format can be found here:
> https://docs.google.com/document/d/1LLeXNvC1wba47TTloZi73zwxs22tJWRvCiFBjtO-8Kg/edit?usp=sharing
>
> You can find previous NCSG comments here:
> https://community.icann.org/display/gnsononcomstake/Public+Comments+-+2022
>
> See below some best practices for the penholder:
>
>
>    -     Provide the first draft on the mailing list in by day 21 of the
>    comment period
>    -     Try to resolve the comments throughout the duration of comment
>    period
>    -     Make sure that the commenter has seen how comment has been
>    resolved (contact them directly if necessary)
>
>
> Warmly,
> Tomslin
> @LinkedIn: https://www.linkedin.com/in/tomslin/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20220922/995b8a44/attachment.htm>

From mesumbeslin at gmail.com  Thu Sep 22 12:39:02 2022
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Thu, 22 Sep 2022 17:39:02 +0800
Subject: [NCSG-PC] [Public Comment] Call for volunteers - Pilot Holistic
 Review Draft Terms of Reference
Message-ID: <CAM8DdeWKyHyVtcvMYMBBh=LPgq8mtu48faqMB_1gyhZ2FmSfyg@mail.gmail.com>

Hi all,

The public comment period on the Pilot Holistic Review Draft Terms of
Reference is open. The Third Accountability and Transparency Review Team
(ATRT3) recommended that a Holistic Review be initiated by ICANN Org. The
review will have implications for various community structures and groups,
including potential implications on how the various SO/AC structures are
organized and evaluated in the future.

Considering the potential implications on the ICANN structures and work,
the Board is seeking input on whether the Draft Terms of Reference seems
fit for purpose, and whether it is tailored to the community?s expectations
based upon ATRT3 recommendation 3.5, including scheduling and timing in
light of other community and stakeholder work.

The Policy Committee is now calling for volunteers to draft an NCSG
comment/response for this proceeding which is due for consideration on
Thursday 03 October 2022 to allow time for filling and submitting the new
public comment form.

Please let me know off-list if you'd like to volunteer for the comment
drafting. It'll be nice to have more than one volunteer, including
new-commers who can use this as an opportunity to learn and be familiar
with policy work.

More information about the policy status report can be found here :
https://www.icann.org/en/public-comment/proceeding/pilot-holistic-review-draft-terms-of-reference-30-08-2022

A draft Google doc for the comment in the guided format can be found here:
https://docs.google.com/document/d/1DtxcgIneTH8pwpfvV4sTAoGBi9h6I-EVKos7ZU8Xb7g/edit?usp=sharing

You can find previous NCSG comments here:
https://community.icann.org/display/gnsononcomstake/Public+Comments+-+2022

See below some best practices for the penholder:

        Provide the first draft on the mailing list in by day 21 of the
comment period
        Try to resolve the comments throughout the duration of comment
period
        Make sure that the commenter has seen how comment has been resolved
(contact them directly if necessary)

Warmly,
Tomslin
@LinkedIn: https://www.linkedin.com/in/tomslin/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20220922/ac0062f2/attachment.htm>