From andrea.glandon at icann.org  Fri Nov  1 18:11:37 2024
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Fri, 1 Nov 2024 16:11:37 +0000
Subject: [NCSG-PC] FINAL-ICANN81 Day 0 Agenda
Message-ID: <57E07DA5-1E16-4944-A44C-BF54667A9022@icann.org>

Hello all!

Please find attached the Day 0 agenda. Please pass this along to anyone else you would like to have it.

Thanks!
Andrea Glandon
Policy Operations Sr. Coordinator
Internet Corporation for Assigned Names and Numbers (ICANN)
Skype ID:  acglandon76




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20241101/5fc9c2b3/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: MEETING AGENDA final version.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 19502 bytes
Desc: MEETING AGENDA final version.docx
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20241101/5fc9c2b3/attachment.docx>

From julf at Julf.com  Mon Nov  4 14:38:39 2024
From: julf at Julf.com (Johan Helsingius)
Date: Mon, 4 Nov 2024 13:38:39 +0100
Subject: [NCSG-PC] Proposed Revisions to Community Anti-Harassment Policy
Message-ID: <9b7d76c4-7760-436f-bc96-2eb557c065de@Julf.com>

This might affect our questions to the board.

https://www.icann.org/en/public-comment/proceeding/proposed-revisions-to-community-anti-harassment-policy-04-11-2024

	Julf


From julf at Julf.com  Mon Nov  4 14:42:23 2024
From: julf at Julf.com (Johan Helsingius)
Date: Mon, 4 Nov 2024 13:42:23 +0100
Subject: [NCSG-PC] Draft 0-day NCSG presentation to the board
Message-ID: <10d65ec8-2d22-49d2-8833-4f31532c7dc2@Julf.com>

Comments and suggestions welcome, but preferably soon.

	Julf
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NCSG board day 0.pptx
Type: application/vnd.openxmlformats-officedocument.presentationml.presentation
Size: 71840 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20241104/3dc360ba/attachment.pptx>

From stephanie at digitaldiscretion.ca  Mon Nov  4 16:41:28 2024
From: stephanie at digitaldiscretion.ca (Stephanie E Perrin)
Date: Mon, 4 Nov 2024 09:41:28 -0500
Subject: [NCSG-PC] Draft 0-day NCSG presentation to the board
In-Reply-To: <10d65ec8-2d22-49d2-8833-4f31532c7dc2@Julf.com>
References: <10d65ec8-2d22-49d2-8833-4f31532c7dc2@Julf.com>
Message-ID: <a90a8911-985b-4f8e-9055-d57a1893d64c@digitaldiscretion.ca>

I think you should add human rights impact assessments on the slide that 
talks about NCUC interests.? I also think it is worthwhile to mention 
our focus on the openness and availability of documents on ICANN 
websites (i.e. the importance of transparency in a MS organization).

cheers Stephanie Perrin

On 2024-11-04 7:42 am, Johan Helsingius via NCSG-PC wrote:
> Comments and suggestions welcome, but preferably soon.
>
> ????Julf
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc


From JFQueralt at theiofoundation.org  Mon Nov  4 17:17:44 2024
From: JFQueralt at theiofoundation.org (=?UTF-8?Q?Jean_F=2E_Qu=C3=A9ralt?=)
Date: Mon, 4 Nov 2024 23:17:44 +0800
Subject: [NCSG-PC] Draft 0-day NCSG presentation to the board
In-Reply-To: <10d65ec8-2d22-49d2-8833-4f31532c7dc2@Julf.com>
References: <10d65ec8-2d22-49d2-8833-4f31532c7dc2@Julf.com>
Message-ID: <CACuyrh_Vey+4Jd9swZ4zPSWrDRLvQh3L8snHOREAfrF7pC0yeA@mail.gmail.com>

Works for me.

Jean

On Mon, Nov 4, 2024, 20:42 Johan Helsingius <julf at julf.com> wrote:

> Comments and suggestions welcome, but preferably soon.
>
>         Julf

-- 
**DISCLAIMER**
*The content of this message, which may contain personal or 
sensitive data, is confidential. If you have received it by mistake, please 
inform the sender by replying to the email and then permanently delete the 
message, including any attachments. It is forbidden to copy, forward or in 
any way reveal the content of this message to anyone. The integrity and 
security of this email cannot be guaranteed over the Internet and, 
therefore, the sender will not be held liable for any damage caused by the 
message.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20241104/f8adf138/attachment.htm>

From farzaneh.badii at gmail.com  Mon Nov  4 17:36:30 2024
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Mon, 4 Nov 2024 10:36:30 -0500
Subject: [NCSG-PC] [NCSG-EC] Draft 0-day NCSG presentation to the board
In-Reply-To: <10d65ec8-2d22-49d2-8833-4f31532c7dc2@Julf.com>
References: <10d65ec8-2d22-49d2-8833-4f31532c7dc2@Julf.com>
Message-ID: <CAN1qJvDbuZFR7+W5Ay2yQ9PJY7pgLGvBTR_tEu7baiByhQ0MwA@mail.gmail.com>

I think we can also tell them a bit our values;
Advancing human rights
Protecting access to knowledge
Privacy
Freedom of speech

what do you think?



Farzaneh


On Mon, Nov 4, 2024 at 7:42?AM Johan Helsingius via NCSG-EC <
ncsg-ec at lists.ncsg.is> wrote:

> Comments and suggestions welcome, but preferably soon.
>
>         Julf_______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20241104/7837a679/attachment.htm>

From julf at Julf.com  Mon Nov  4 17:52:37 2024
From: julf at Julf.com (Johan Helsingius)
Date: Mon, 4 Nov 2024 16:52:37 +0100
Subject: [NCSG-PC] [NCSG-EC] Draft 0-day NCSG presentation to the board
In-Reply-To: <CAN1qJvDbuZFR7+W5Ay2yQ9PJY7pgLGvBTR_tEu7baiByhQ0MwA@mail.gmail.com>
References: <10d65ec8-2d22-49d2-8833-4f31532c7dc2@Julf.com>
 <CAN1qJvDbuZFR7+W5Ay2yQ9PJY7pgLGvBTR_tEu7baiByhQ0MwA@mail.gmail.com>
Message-ID: <4ecd5f76-3317-4363-8b26-fb123149b914@Julf.com>

Good suggestion. I will add that.

	Julf


On 11/4/24 16:36, farzaneh badii wrote:
> I think we can also tell them a bit our values;
> Advancing human rights
> Protecting access to knowledge
> Privacy
> Freedom of speech
> 
> what do you think?
> 
> 
> 
> Farzaneh
> 
> 
> On Mon, Nov 4, 2024 at 7:42?AM Johan Helsingius via NCSG-EC 
> <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>> wrote:
> 
>     Comments and suggestions welcome, but preferably soon.
> 
>      ? ? ? ? Julf_______________________________________________
>     NCSG-EC mailing list
>     NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
>     https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
> 


From farzaneh.badii at gmail.com  Mon Nov  4 17:55:14 2024
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Mon, 4 Nov 2024 10:55:14 -0500
Subject: [NCSG-PC] [NCSG-EC] Draft 0-day NCSG presentation to the board
In-Reply-To: <4ecd5f76-3317-4363-8b26-fb123149b914@Julf.com>
References: <10d65ec8-2d22-49d2-8833-4f31532c7dc2@Julf.com>
 <CAN1qJvDbuZFR7+W5Ay2yQ9PJY7pgLGvBTR_tEu7baiByhQ0MwA@mail.gmail.com>
 <4ecd5f76-3317-4363-8b26-fb123149b914@Julf.com>
Message-ID: <CAN1qJvDGw=h-XqiWgCMCZba5a1Xg45aFa0P_Wb0J8sLgmn2-0w@mail.gmail.com>

oh of course open, global Internet as well.
sorry adding to the laundry list but it's important.

Farzaneh


On Mon, Nov 4, 2024 at 10:53?AM Johan Helsingius <julf at julf.com> wrote:

> Good suggestion. I will add that.
>
>         Julf
>
>
> On 11/4/24 16:36, farzaneh badii wrote:
> > I think we can also tell them a bit our values;
> > Advancing human rights
> > Protecting access to knowledge
> > Privacy
> > Freedom of speech
> >
> > what do you think?
> >
> >
> >
> > Farzaneh
> >
> >
> > On Mon, Nov 4, 2024 at 7:42?AM Johan Helsingius via NCSG-EC
> > <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>> wrote:
> >
> >     Comments and suggestions welcome, but preferably soon.
> >
> >              Julf_______________________________________________
> >     NCSG-EC mailing list
> >     NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
> >     https://lists.ncsg.is/mailman/listinfo/ncsg-ec
> >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20241104/0a9a7144/attachment.htm>

From julf at Julf.com  Mon Nov  4 17:59:12 2024
From: julf at Julf.com (Johan Helsingius)
Date: Mon, 4 Nov 2024 16:59:12 +0100
Subject: [NCSG-PC] [NCSG-EC] Draft 0-day NCSG presentation to the board
In-Reply-To: <CAN1qJvDGw=h-XqiWgCMCZba5a1Xg45aFa0P_Wb0J8sLgmn2-0w@mail.gmail.com>
References: <10d65ec8-2d22-49d2-8833-4f31532c7dc2@Julf.com>
 <CAN1qJvDbuZFR7+W5Ay2yQ9PJY7pgLGvBTR_tEu7baiByhQ0MwA@mail.gmail.com>
 <4ecd5f76-3317-4363-8b26-fb123149b914@Julf.com>
 <CAN1qJvDGw=h-XqiWgCMCZba5a1Xg45aFa0P_Wb0J8sLgmn2-0w@mail.gmail.com>
Message-ID: <d26064ea-0b7e-429f-a001-5986cd6239fc@Julf.com>

It is important, thanks - and it supports ICANN's mission.

Will add a "Our values and priorities" slide.,
	Julf

On 11/4/24 16:55, farzaneh badii wrote:
> oh of course open, global Internet as well.
> sorry adding to the laundry list but it's important.
> 
> Farzaneh
> 
> 
> On Mon, Nov 4, 2024 at 10:53?AM Johan Helsingius <julf at julf.com 
> <mailto:julf at julf.com>> wrote:
> 
>     Good suggestion. I will add that.
> 
>      ? ? ? ? Julf
> 
> 
>     On 11/4/24 16:36, farzaneh badii wrote:
>      > I think we can also tell them a bit our values;
>      > Advancing human rights
>      > Protecting access to knowledge
>      > Privacy
>      > Freedom of speech
>      >
>      > what do you think?
>      >
>      >
>      >
>      > Farzaneh
>      >
>      >
>      > On Mon, Nov 4, 2024 at 7:42?AM Johan Helsingius via NCSG-EC
>      > <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>
>     <mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>>> wrote:
>      >
>      >? ? ?Comments and suggestions welcome, but preferably soon.
>      >
>      >? ? ? ? ? ? ? Julf_______________________________________________
>      >? ? ?NCSG-EC mailing list
>      > NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
>     <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>>
>      > https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
>      >? ? ?<https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>>
>      >
> 


From julf at Julf.com  Mon Nov  4 18:33:06 2024
From: julf at Julf.com (Johan Helsingius)
Date: Mon, 4 Nov 2024 17:33:06 +0100
Subject: [NCSG-PC] Draft 0-day NCSG presentation to the board
In-Reply-To: <a90a8911-985b-4f8e-9055-d57a1893d64c@digitaldiscretion.ca>
References: <10d65ec8-2d22-49d2-8833-4f31532c7dc2@Julf.com>
 <a90a8911-985b-4f8e-9055-d57a1893d64c@digitaldiscretion.ca>
Message-ID: <3e0f8750-6dd3-4c2b-9886-7589f69a1d82@Julf.com>

I would need NCUC approval to add to the NCUC-specific list.
I did put "Advancing human rights" and "Openness and transparency"
on a "Our [NCSG] values and priorities".

	Julf


On 11/4/24 15:41, Stephanie E Perrin via NCSG-PC wrote:
> I think you should add human rights impact assessments on the slide that
> talks about NCUC interests.? I also think it is worthwhile to mention
> our focus on the openness and availability of documents on ICANN
> websites (i.e. the importance of transparency in a MS organization).
> 
> cheers Stephanie Perrin
> 
> On 2024-11-04 7:42 am, Johan Helsingius via NCSG-PC wrote:
>> Comments and suggestions welcome, but preferably soon.
>>
>>  ????Julf
>>
>> _______________________________________________
>> 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


From julf at Julf.com  Mon Nov  4 22:33:32 2024
From: julf at Julf.com (Johan Helsingius)
Date: Mon, 4 Nov 2024 21:33:32 +0100
Subject: [NCSG-PC] Draft 0-day NCSG presentation to the board
In-Reply-To: <CAJR4JuHF8D7dQTDMiuFNyR63wVpNOA2N0vvjGDZNJJfJYygRFg@mail.gmail.com>
References: <10d65ec8-2d22-49d2-8833-4f31532c7dc2@Julf.com>
 <CAJR4JuHF8D7dQTDMiuFNyR63wVpNOA2N0vvjGDZNJJfJYygRFg@mail.gmail.com>
Message-ID: <f64b3434-4375-453e-b65c-eaee2290a9c6@Julf.com>

Will add human rights. Only counting active members, but might mention
passive/stale number too.

	Julf

On 11/4/24 21:05, Benjamin Akinmoyeje wrote:
> Dear Johan,
> Kindly include Human Rights or CCWPHRIA? in NCUC 's list.
> 
> Also, we have about?678 individual members and?66 organizational 
> members. Although 193 (active) voted.
> 
> Kind regards,
> Benjamin
> 
> On Mon, Nov 4, 2024 at 2:42?PM Johan Helsingius <julf at julf.com 
> <mailto:julf at julf.com>> wrote:
> 
>     Comments and suggestions welcome, but preferably soon.
> 
>      ? ? ? ? Julf
> 


From julf at Julf.com  Tue Nov  5 14:35:47 2024
From: julf at Julf.com (Johan Helsingius)
Date: Tue, 5 Nov 2024 13:35:47 +0100
Subject: [NCSG-PC] [NCSG-EC] Updated ICANN81 Agendas,
 NCSG Membership & NCSG PC
In-Reply-To: <CAM8DdeVzcZaxYLciPrPALULEQ1fQddaLbr7=Ai_L8eOBUMmT=g@mail.gmail.com>
References: <15EA97C4-C48A-4331-9751-7DF8C040BA49@icann.org>
 <CAM8DdeVzcZaxYLciPrPALULEQ1fQddaLbr7=Ai_L8eOBUMmT=g@mail.gmail.com>
Message-ID: <b3df73d6-b3cb-4e7c-86f4-b4d3c09d6b1d@Julf.com>

The Membership session is pretty packed, so if you need stuff for the PC
session, we could perhaps move CADE to the PC session instead?

	Julf

On 10/29/24 20:43, Tomslin Samme-Nlar wrote:
> Hi PC,
> 
> Just a reminder that your suggestions for the ICANN81 PC agenda are 
> welcomed.
> I won't be attending ICANN81, so Peter will lead the meeting.
> Here is the link again > 
> https://docs.google.com/document/d/1XU5zc__Zwnmo7l21RKrtHwKk0xnuAvK6eVki2S4G8e8/edit?tab=t.0 <https://docs.google.com/document/d/1XU5zc__Zwnmo7l21RKrtHwKk0xnuAvK6eVki2S4G8e8/edit?tab=t.0>
> 
> Warmly,
> Tomslin
> 
> 
> 
> On Wed, 23 Oct 2024 at 02:28, Andrea Glandon via NCSG-EC 
> <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>> wrote:
> 
>     Hello!____
> 
>     __ __
> 
>     I wanted to provide an updated agenda for the NCSG Membership
>     session. Julf, I heard from Adam Peake that you want to add the CADE
>     project to the agenda so I have added it. ____
> 
>     __ __
> 
>     https://docs.google.com/document/d/1XU9tPC4oi0ESztpV9MJyb9a7-PbnbxAgPYIi6oQpwR0/edit?usp=sharing <https://docs.google.com/document/d/1XU9tPC4oi0ESztpV9MJyb9a7-PbnbxAgPYIi6oQpwR0/edit?usp=sharing>____
> 
>     __ __
> 
>     And below is the NCSG PC agenda link:____
> 
>     __ __
> 
>     https://docs.google.com/document/d/1XU5zc__Zwnmo7l21RKrtHwKk0xnuAvK6eVki2S4G8e8/edit?usp=sharing <https://docs.google.com/document/d/1XU5zc__Zwnmo7l21RKrtHwKk0xnuAvK6eVki2S4G8e8/edit?usp=sharing>____
> 
>     __ __
> 
>     Please let me know if you would like me to update anything. The docs
>     are also open for others to make changes.____
> 
>     __ __
> 
>     Thanks!____
> 
>     Kind Regards,____
> 
>     Andrea____
> 
>     __ __
> 
>     __ __
> 
>     *From: *NCSG-EC <ncsg-ec-bounces at lists.ncsg.is
>     <mailto:ncsg-ec-bounces at lists.ncsg.is>> on behalf of Andrea Glandon
>     via NCSG-EC <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>>
>     *Reply-To: *Andrea Glandon <andrea.glandon at icann.org
>     <mailto:andrea.glandon at icann.org>>
>     *Date: *Friday, September 20, 2024 at 07:51
>     *To: *Pedro de Perdig?o Lana <pedrodeperdigaolana at gmail.com
>     <mailto:pedrodeperdigaolana at gmail.com>>, Caleb Ogundele
>     <muyiwacaleb at gmail.com <mailto:muyiwacaleb at gmail.com>>
>     *Cc: *NCSG EC <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>>
>     *Subject: *Re: [NCSG-EC] [NCUC-EC] [Ext] Re: ICANN81-Reviews Team
>     Available for Engagement during ICANN81____
> 
>     __ __
> 
>     Great! I will update the NCSG Membership agenda and let the Reviews
>     Team know.____
> 
>     __ __
> 
>     Thanks!____
> 
>     Kind Regards,____
> 
>     Andrea____
> 
>     __ __
> 
>     __ __
> 
>     *From: *Pedro de Perdig?o Lana <pedrodeperdigaolana at gmail.com
>     <mailto:pedrodeperdigaolana at gmail.com>>
>     *Date: *Tuesday, September 17, 2024 at 10:09
>     *To: *Caleb Ogundele <muyiwacaleb at gmail.com
>     <mailto:muyiwacaleb at gmail.com>>
>     *Cc: *Andrea Glandon <andrea.glandon at icann.org
>     <mailto:andrea.glandon at icann.org>>, NCSG EC <ncsg-ec at lists.ncsg.is
>     <mailto:ncsg-ec at lists.ncsg.is>>
>     *Subject: *Re: [NCSG-EC] [NCUC-EC] [Ext] Re: ICANN81-Reviews Team
>     Available for Engagement during ICANN81____
> 
>     __ __
> 
>     I also agree with this choice, Julf.____
> 
>     __ __
> 
>     Cordially,____
> 
>     __ __
> 
>     *Pedro de Perdig?o Lana*____
> 
>     Advogado - OAB/PR 90.600 [nic.br]
>     <https://urldefense.com/v3/__https:/www.nic.br/__;!!PtGJab4!8dkx-FSdONldiKA9vQErEd3aWV6xwgq-Jv8uY2q1cdOf7E5jLQSSJo5emKgkcO2AWZorYw_ZmJcotQzKLpF2j3koD9bPD_7MGjJ0$>,? Pesquisador (GEDAI/UFPR [gedai.com.br] <https://urldefense.com/v3/__https:/www.gedai.com.br/__;!!PtGJab4!8dkx-FSdONldiKA9vQErEd3aWV6xwgq-Jv8uY2q1cdOf7E5jLQSSJo5emKgkcO2AWZorYw_ZmJcotQzKLpF2j3koD9bPD6vifNVY$>)____
> 
>     Doutorando em Direito (UFPR), Mestre em Direito Empresarial
>     (UCoimbra), ____
> 
>     Coordena??o/Diretoria/EC @ ISOC BR [isoc.org.br]
>     <https://urldefense.com/v3/__https:/isoc.org.br/__;!!PtGJab4!8dkx-FSdONldiKA9vQErEd3aWV6xwgq-Jv8uY2q1cdOf7E5jLQSSJo5emKgkcO2AWZorYw_ZmJcotQzKLpF2j3koD9bPD-69ViTV$>, NCUC [ncuc.org] <https://urldefense.com/v3/__https:/www.ncuc.org__;!!PtGJab4!8dkx-FSdONldiKA9vQErEd3aWV6xwgq-Jv8uY2q1cdOf7E5jLQSSJo5emKgkcO2AWZorYw_ZmJcotQzKLpF2j3koD9bPD03Sp54C$> & NCSG <https://community.icann.org/display/gnsononcomstake/Home>(ICANN), YouthLACIGF [youthlacigf.lat] <https://urldefense.com/v3/__https:/youthlacigf.lat/__;!!PtGJab4!8dkx-FSdONldiKA9vQErEd3aWV6xwgq-Jv8uY2q1cdOf7E5jLQSSJo5emKgkcO2AWZorYw_ZmJcotQzKLpF2j3koD9bPD_F6BtYR$>, IODA [ioda.org.br] <https://urldefense.com/v3/__https:/ioda.org.br/__;!!PtGJab4!8dkx-FSdONldiKA9vQErEd3aWV6xwgq-Jv8uY2q1cdOf7E5jLQSSJo5emKgkcO2AWZorYw_ZmJcotQzKLpF2j3koD9bPD0fUdXZe$> e CC Brasil [br.creativecommons.net] <https://urldefense.com/v3/__https:/br.creativecommons.net/__;!!PtGJab4!8dkx-FSdONldiKA9vQErEd3aWV6xwgq-Jv8uY2q1cdOf7E5jLQSSJo5emKgkcO2AWZorYw_ZmJcotQzKLpF2j3koD9bPD47VEWOV$>.____
> 
>     Essa mensagem ? restrita ao remetente e destinat?rio(s). Se recebida
>     por engano, favor responder informando o erro.____
> 
>     __ __
> 
>     __ __
> 
>     Em ter., 17 de set. de 2024 ?s 11:38, Caleb Ogundele via NCSG-EC
>     <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>> escreveu:____
> 
>         This is fine with?me. ____
> 
>         __ __
> 
>         On Mon, Sep 16, 2024, 11:26?AM Andrea Glandon via NCSG-EC
>         <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>> wrote:____
> 
>             Hello again,
> 
>             I heard back from the reviews team. Please see below. Please
>             let me know if the group would like to give more time and
>             also discuss Planning for the Fourth Accountability and
>             Transparency Review.
> 
>             "Please let us know if there is a particular topic that
>             would most interest the NCSG but in the 25 minutes offered
>             we would most likely present on the Continuous Improvement
>             Project and the Pilot Holistic Review, leaving time for
>             pertinent questions from the group."
> 
>             Thanks!
>             Kind Regards,
>             Andrea
> 
> 
> 
> 
>             On 9/12/24, 07:57, "NCSG-EC on behalf of Andrea Glandon via
>             NCSG-EC" <ncsg-ec-bounces at lists.ncsg.is
>             <mailto:ncsg-ec-bounces at lists.ncsg.is>
>             <mailto:ncsg-ec-bounces at lists.ncsg.is
>             <mailto:ncsg-ec-bounces at lists.ncsg.is>> on behalf of
>             ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>
>             <mailto:ncsg-ec at lists.ncsg.is
>             <mailto:ncsg-ec at lists.ncsg.is>>> wrote:
> 
> 
>             Hello all,
> 
> 
>             Here is a draft agenda for the NCSG Membership Session:
>             https://urldefense.com/v3/__https://docs.google.com/document/d/1XU9tPC4oi0ESztpV9MJyb9a7-PbnbxAgPYIi6oQpwR0/edit?usp=sharing__;!!PtGJab4!4UGPt5Upryc5tbA77oTJX7-mHO7MNkhLNwLZVTxBdpBB61_ZEvOgyG2qr9VMZFA_NTf8G9DEvxOd12S9aAgB2I7uGYL1Mw$ <https://urldefense.com/v3/__https:/docs.google.com/document/d/1XU9tPC4oi0ESztpV9MJyb9a7-PbnbxAgPYIi6oQpwR0/edit?usp=sharing__;!!PtGJab4!4UGPt5Upryc5tbA77oTJX7-mHO7MNkhLNwLZVTxBdpBB61_ZEvOgyG2qr9VMZFA_NTf8G9DEvxOd12S9aAgB2I7uGYL1Mw$> <https://urldefense.com/v3/__https://docs.google.com/document/d/1XU9tPC4oi0ESztpV9MJyb9a7-PbnbxAgPYIi6oQpwR0/edit?usp=sharing__;!!PtGJab4!4UGPt5Upryc5tbA77oTJX7-mHO7MNkhLNwLZVTxBdpBB61_ZEvOgyG2qr9VMZFA_NTf8G9DEvxOd12S9aAgB2I7uGYL1Mw$ <https://urldefense.com/v3/__https:/docs.google.com/document/d/1XU9tPC4oi0ESztpV9MJyb9a7-PbnbxAgPYIi6oQpwR0/edit?usp=sharing__;!!PtGJab4!4UGPt5Upryc5tbA77oTJX7-mHO7MNkhLNwLZVTxBdpBB61_ZEvOgyG2qr9VMZFA_NTf8G9DEvxOd12S9aAgB2I7uGYL1Mw$>> [docs[.]google[.]com]
> 
> 
>             Thanks!
>             Kind Regards,
>             Andrea
> 
> 
> 
> 
> 
> 
> 
> 
>             On 9/12/24, 06:46, "NCSG-EC on behalf of Johan Helsingius
>             via NCSG-EC" <ncsg-ec-bounces at lists.ncsg.is
>             <mailto:ncsg-ec-bounces at lists.ncsg.is>
>             <mailto:ncsg-ec-bounces at lists.ncsg.is
>             <mailto:ncsg-ec-bounces at lists.ncsg.is>>
>             <mailto:ncsg-ec-bounces at lists.ncsg.is
>             <mailto:ncsg-ec-bounces at lists.ncsg.is>
>             <mailto:ncsg-ec-bounces at lists.ncsg.is
>             <mailto:ncsg-ec-bounces at lists.ncsg.is>>> on behalf of
>             ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>
>             <mailto:ncsg-ec at lists.ncsg.is
>             <mailto:ncsg-ec at lists.ncsg.is>>
>             <mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>
>             <mailto:ncsg-ec at lists.ncsg.is
>             <mailto:ncsg-ec at lists.ncsg.is>>>> wrote:
> 
> 
> 
> 
>             Farzaneh,
> 
> 
> 
> 
>             Happy for you to have 15 or 20 minutes for HR impact assessment
>             and DNS abuse. Getting supported travellers to talk is a great
>             idea, it is just a shame that our session is pretty early in
>             the week.
> 
> 
> 
> 
>             Julf
> 
> 
> 
> 
> 
> 
> 
> 
>             On 12/09/2024 08:57, farzaneh badii wrote:
>             > I think it will be tiresome for our members to sit through reviews after 
>             > reviews presentations. Why don?t we pick one that we care about the most 
>             > and npoc and ncuc could invite others too so that it wont be a 
>             > duplicate. Give max 30 mins
>             > I would like to update people on human rights impact assessment and dns 
>             > abuse. If you could allocate 15 mins that would be great. Would be good 
>             > to give a few mins to the supported travelers to talk about their 
>             > experience.
>             > 
>             > Farzaneh
>             > 
>             > 
>             > On Thu, Sep 12, 2024 at 2:36 AM Johan Helsingius via NCSG-EC 
>             > <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>
>             <mailto:ncsg-ec at lists.ncsg.is
>             <mailto:ncsg-ec at lists.ncsg.is>>
>             <mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>
>             <mailto:ncsg-ec at lists.ncsg.is
>             <mailto:ncsg-ec at lists.ncsg.is>>>
>             <mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>
>             <mailto:ncsg-ec at lists.ncsg.is
>             <mailto:ncsg-ec at lists.ncsg.is>>
>             <mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>
>             <mailto:ncsg-ec at lists.ncsg.is
>             <mailto:ncsg-ec at lists.ncsg.is>>>>> wrote:
>             > 
>             > On 11/09/2024 17:42, Caleb Ogundele wrote:
>             > > @Johan Helsingius <mailto:julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com
>             <mailto:julf at julf.com>> <mailto:julf at julf.com
>             <mailto:julf at julf.com> <mailto:julf at julf.com
>             <mailto:julf at julf.com>>> <mailto:julf at julf.com
>             <mailto:julf at julf.com> <mailto:julf at julf.com
>             <mailto:julf at julf.com>> <mailto:julf at julf.com
>             <mailto:julf at julf.com> <mailto:julf at julf.com
>             <mailto:julf at julf.com>>>>>
>             > Do we have our agenda for
>             > > NCSG?
>             > 
>             > Not yet - suggestions for agenda items welcomed!
>             > 
>             > > We can look at all topics and make time allocations. 30mins and
>             > > ensuing discussions might not be enough.
>             > 
>             > I'd be happy to give the Reviews team more some time.
>             > 
>             > Julf
>             > _______________________________________________
>             > NCSG-EC mailing list
>             > NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
>             <mailto:NCSG-EC at lists.ncsg.is
>             <mailto:NCSG-EC at lists.ncsg.is>>
>             <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
>             <mailto:NCSG-EC at lists.ncsg.is
>             <mailto:NCSG-EC at lists.ncsg.is>>>
>             <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
>             <mailto:NCSG-EC at lists.ncsg.is
>             <mailto:NCSG-EC at lists.ncsg.is>>
>             <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
>             <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>>>>
>             > https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!9r9k3_UqWp1NMNTfq-tSbjuSpkLGwLj1Z98_q6KvdAJUgZCJmHYrGW0xfQO5HlOd3oUwahJQPd-sDPOFBg8h49QUUwnygQ$ <https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!9r9k3_UqWp1NMNTfq-tSbjuSpkLGwLj1Z98_q6KvdAJUgZCJmHYrGW0xfQO5HlOd3oUwahJQPd-sDPOFBg8h49QUUwnygQ$> <https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!9r9k3_UqWp1NMNTfq-tSbjuSpkLGwLj1Z98_q6KvdAJUgZCJmHYrGW0xfQO5HlOd3oUwahJQPd-sDPOFBg8h49QUUwnygQ$ <https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!9r9k3_UqWp1NMNTfq-tSbjuSpkLGwLj1Z98_q6KvdAJUgZCJmHYrGW0xfQO5HlOd3oUwahJQPd-sDPOFBg8h49QUUwnygQ$>> <https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!9r9k3_UqWp1NMNTfq-tSbjuSpkLGwLj1Z98_q6KvdAJUgZCJmHYrGW0xfQO5HlOd3oUwahJQPd-sDPOFBg8h49QUUwnygQ$ <https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!9r9k3_UqWp1NMNTfq-tSbjuSpkLGwLj1Z98_q6KvdAJUgZCJmHYrGW0xfQO5HlOd3oUwahJQPd-sDPOFBg8h49QUUwnygQ$> <https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!9r9k3_UqWp1NMNTfq-tSbjuSpkLGwLj1Z98_q6KvdAJUgZCJmHYrGW0xfQO5HlOd3oUwahJQPd-sDPOFBg8h49QUUwnygQ$ <https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!9r9k3_UqWp1NMNTfq-tSbjuSpkLGwLj1Z98_q6KvdAJUgZCJmHYrGW0xfQO5HlOd3oUwahJQPd-sDPOFBg8h49QUUwnygQ$>>> [lists[.]ncsg[.]is]
>             > <https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!9r9k3_UqWp1NMNTfq-tSbjuSpkLGwLj1Z98_q6KvdAJUgZCJmHYrGW0xfQO5HlOd3oUwahJQPd-sDPOFBg8h49QUUwnygQ$ <https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!9r9k3_UqWp1NMNTfq-tSbjuSpkLGwLj1Z98_q6KvdAJUgZCJmHYrGW0xfQO5HlOd3oUwahJQPd-sDPOFBg8h49QUUwnygQ$> <https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!9r9k3_UqWp1NMNTfq-tSbjuSpkLGwLj1Z98_q6KvdAJUgZCJmHYrGW0xfQO5HlOd3oUwahJQPd-sDPOFBg8h49QUUwnygQ$ <https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!9r9k3_UqWp1NMNTfq-tSbjuSpkLGwLj1Z98_q6KvdAJUgZCJmHYrGW0xfQO5HlOd3oUwahJQPd-sDPOFBg8h49QUUwnygQ$>> <https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!9r9k3_UqWp1NMNTfq-tSbjuSpkLGwLj1Z98_q6KvdAJUgZCJmHYrGW0xfQO5HlOd3oUwahJQPd-sDPOFBg8h49QUUwnygQ$ <https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!9r9k3_UqWp1NMNTfq-tSbjuSpkLGwLj1Z98_q6KvdAJUgZCJmHYrGW0xfQO5HlOd3oUwahJQPd-sDPOFBg8h49QUUwnygQ$> <https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!9r9k3_UqWp1NMNTfq-tSbjuSpkLGwLj1Z98_q6KvdAJUgZCJmHYrGW0xfQO5HlOd3oUwahJQPd-sDPOFBg8h49QUUwnygQ$ <https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!9r9k3_UqWp1NMNTfq-tSbjuSpkLGwLj1Z98_q6KvdAJUgZCJmHYrGW0xfQO5HlOd3oUwahJQPd-sDPOFBg8h49QUUwnygQ$>>> [lists[.]ncsg[.]is]>
>             > 
>             _______________________________________________
>             NCSG-EC mailing list
>             NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
>             <mailto:NCSG-EC at lists.ncsg.is
>             <mailto:NCSG-EC at lists.ncsg.is>>
>             <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
>             <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>>>
>             https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!9r9k3_UqWp1NMNTfq-tSbjuSpkLGwLj1Z98_q6KvdAJUgZCJmHYrGW0xfQO5HlOd3oUwahJQPd-sDPOFBg8h49QUUwnygQ$ <https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!9r9k3_UqWp1NMNTfq-tSbjuSpkLGwLj1Z98_q6KvdAJUgZCJmHYrGW0xfQO5HlOd3oUwahJQPd-sDPOFBg8h49QUUwnygQ$> <https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!9r9k3_UqWp1NMNTfq-tSbjuSpkLGwLj1Z98_q6KvdAJUgZCJmHYrGW0xfQO5HlOd3oUwahJQPd-sDPOFBg8h49QUUwnygQ$ <https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!9r9k3_UqWp1NMNTfq-tSbjuSpkLGwLj1Z98_q6KvdAJUgZCJmHYrGW0xfQO5HlOd3oUwahJQPd-sDPOFBg8h49QUUwnygQ$>> <https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!9r9k3_UqWp1NMNTfq-tSbjuSpkLGwLj1Z98_q6KvdAJUgZCJmHYrGW0xfQO5HlOd3oUwahJQPd-sDPOFBg8h49QUUwnygQ$ <https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!9r9k3_UqWp1NMNTfq-tSbjuSpkLGwLj1Z98_q6KvdAJUgZCJmHYrGW0xfQO5HlOd3oUwahJQPd-sDPOFBg8h49QUUwnygQ$> <https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!9r9k3_UqWp1NMNTfq-tSbjuSpkLGwLj1Z98_q6KvdAJUgZCJmHYrGW0xfQO5HlOd3oUwahJQPd-sDPOFBg8h49QUUwnygQ$ <https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!9r9k3_UqWp1NMNTfq-tSbjuSpkLGwLj1Z98_q6KvdAJUgZCJmHYrGW0xfQO5HlOd3oUwahJQPd-sDPOFBg8h49QUUwnygQ$>>> [lists[.]ncsg[.]is]
> 
> 
> 
> 
> 
> 
>             _______________________________________________
>             NCSG-EC mailing list
>             NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
>             <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>>
>             https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!4UGPt5Upryc5tbA77oTJX7-mHO7MNkhLNwLZVTxBdpBB61_ZEvOgyG2qr9VMZFA_NTf8G9DEvxOd12S9aAgB2I70ynxEqw$ <https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!4UGPt5Upryc5tbA77oTJX7-mHO7MNkhLNwLZVTxBdpBB61_ZEvOgyG2qr9VMZFA_NTf8G9DEvxOd12S9aAgB2I70ynxEqw$> <https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!4UGPt5Upryc5tbA77oTJX7-mHO7MNkhLNwLZVTxBdpBB61_ZEvOgyG2qr9VMZFA_NTf8G9DEvxOd12S9aAgB2I70ynxEqw$ <https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!4UGPt5Upryc5tbA77oTJX7-mHO7MNkhLNwLZVTxBdpBB61_ZEvOgyG2qr9VMZFA_NTf8G9DEvxOd12S9aAgB2I70ynxEqw$>> [lists[.]ncsg[.]is]
> 
> 
> 
>             _______________________________________________
>             NCSG-EC mailing list
>             NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
>             https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>             [lists.ncsg.is]
>             <https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!8dkx-FSdONldiKA9vQErEd3aWV6xwgq-Jv8uY2q1cdOf7E5jLQSSJo5emKgkcO2AWZorYw_ZmJcotQzKLpF2j3koD9bPDwPpWvMm$>____
> 
>         _______________________________________________
>         NCSG-EC mailing list
>         NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
>         https://lists.ncsg.is/mailman/listinfo/ncsg-ec [lists.ncsg.is]
>         <https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!8dkx-FSdONldiKA9vQErEd3aWV6xwgq-Jv8uY2q1cdOf7E5jLQSSJo5emKgkcO2AWZorYw_ZmJcotQzKLpF2j3koD9bPDwPpWvMm$>____
> 
>     _______________________________________________
>     NCSG-EC mailing list
>     NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
>     https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
> 
> 
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc

From benakin at gmail.com  Mon Nov  4 22:05:42 2024
From: benakin at gmail.com (Benjamin Akinmoyeje)
Date: Mon, 4 Nov 2024 22:05:42 +0200
Subject: [NCSG-PC] Draft 0-day NCSG presentation to the board
In-Reply-To: <10d65ec8-2d22-49d2-8833-4f31532c7dc2@Julf.com>
References: <10d65ec8-2d22-49d2-8833-4f31532c7dc2@Julf.com>
Message-ID: <CAJR4JuHF8D7dQTDMiuFNyR63wVpNOA2N0vvjGDZNJJfJYygRFg@mail.gmail.com>

Dear Johan,
Kindly include Human Rights or CCWPHRIA  in NCUC 's list.

Also, we have about 678 individual members and 66 organizational members.
Although 193 (active) voted.

Kind regards,
Benjamin

On Mon, Nov 4, 2024 at 2:42?PM Johan Helsingius <julf at julf.com> wrote:

> Comments and suggestions welcome, but preferably soon.
>
>         Julf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20241104/138d7fbd/attachment.htm>

From benakin at gmail.com  Tue Nov  5 03:09:27 2024
From: benakin at gmail.com (Benjamin Akinmoyeje)
Date: Tue, 5 Nov 2024 03:09:27 +0200
Subject: [NCSG-PC] Draft 0-day NCSG presentation to the board
In-Reply-To: <f64b3434-4375-453e-b65c-eaee2290a9c6@Julf.com>
References: <10d65ec8-2d22-49d2-8833-4f31532c7dc2@Julf.com>
 <CAJR4JuHF8D7dQTDMiuFNyR63wVpNOA2N0vvjGDZNJJfJYygRFg@mail.gmail.com>
 <f64b3434-4375-453e-b65c-eaee2290a9c6@Julf.com>
Message-ID: <CAJR4JuEswHp1rpbWHnEVb7t7=HWCH_JY0_KN1mruZPeAToayrA@mail.gmail.com>

Great!

On Mon, Nov 4, 2024 at 10:33?PM Johan Helsingius <julf at julf.com> wrote:

> Will add human rights. Only counting active members, but might mention
> passive/stale number too.
>
>         Julf
>
> On 11/4/24 21:05, Benjamin Akinmoyeje wrote:
> > Dear Johan,
> > Kindly include Human Rights or CCWPHRIA  in NCUC 's list.
> >
> > Also, we have about 678 individual members and 66 organizational
> > members. Although 193 (active) voted.
> >
> > Kind regards,
> > Benjamin
> >
> > On Mon, Nov 4, 2024 at 2:42?PM Johan Helsingius <julf at julf.com
> > <mailto:julf at julf.com>> wrote:
> >
> >     Comments and suggestions welcome, but preferably soon.
> >
> >              Julf
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20241105/c44c019d/attachment.htm>

From mesumbeslin at gmail.com  Tue Nov  5 21:16:56 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Wed, 6 Nov 2024 06:16:56 +1100
Subject: [NCSG-PC] My ICANN81 Attendance
Message-ID: <CAM8DdeU1nWH+W3SQBEAxY1Cpme+df4Co_aF4odY7S1paK-eAgQ@mail.gmail.com>

Hi team,

As you know, due to a family event, I could not be in Istanbul. I will be
unable to attend most of the sessions remotely as well.

Thanks for your understanding.

Warmly,
Tomslin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20241106/06af20a2/attachment.htm>

From julf at Julf.com  Wed Nov  6 11:25:37 2024
From: julf at Julf.com (Johan Helsingius)
Date: Wed, 6 Nov 2024 10:25:37 +0100
Subject: [NCSG-PC] Fwd: Agenda for CSG-NCSG Meeting
In-Reply-To: <BL1PR12MB503065FE4C1517A8DE6E3D59D3522@BL1PR12MB5030.namprd12.prod.outlook.com>
References: <BL1PR12MB503065FE4C1517A8DE6E3D59D3522@BL1PR12MB5030.namprd12.prod.outlook.com>
Message-ID: <8954eec1-ac56-4a46-bbdd-c4e69c117e1c@Julf.com>

Latest agenda for the open NCPH meeting on Tuesday.

	Julf
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Agenda CSG NCSG ICANN81 Corrected.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 16872 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20241106/af8de044/attachment.docx>

From andrea.glandon at icann.org  Fri Nov  8 15:31:34 2024
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Fri, 8 Nov 2024 13:31:34 +0000
Subject: [NCSG-PC] GNSO Council Vice Chair-Tomslin
Message-ID: <9449F2FE-FE16-47D9-91F8-2A7405872155@icann.org>

Hello!

I just heard from the GNSO Secretariat that an official email was not received regarding Tomslin continuing as vice chair of the GNSO Council. If an email can be sent to GNSO Secs with this confirmation that would be great.

Thanks!
Andrea Glandon
Policy Operations Sr. Coordinator
Internet Corporation for Assigned Names and Numbers (ICANN)
Skype ID:  acglandon76



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20241108/c59137cb/attachment.htm>

From lschulman at inta.org  Sat Nov  9 21:49:05 2024
From: lschulman at inta.org (Lori Schulman)
Date: Sat, 9 Nov 2024 19:49:05 +0000
Subject: [NCSG-PC] GNSO Council Vice Chair-Tomslin
In-Reply-To: <9449F2FE-FE16-47D9-91F8-2A7405872155@icann.org>
References: <9449F2FE-FE16-47D9-91F8-2A7405872155@icann.org>
Message-ID: <BL1PR12MB5030CD18A877B8AFAC6C44E9D35E2@BL1PR12MB5030.namprd12.prod.outlook.com>

Dear GNSO Secretariat,

Please consider this an official email from NCPH in support of a renewed term for Tomslin Samme-Nlar as Vice Chair of the GNSO Council.  I am sending in my capacity as CSG Chair with the agreement from Julf Helsingus NCSG Chair.

Please advise as to whether Julf or I can be of further assistance.

Thank you.


With kind regards,

[cid:image001.png at 01DB322B.F955E4A0]<http://www.inta.org/>
Lori Schulman
Senior Director, Internet Policy
International Trademark Association
LSchulman at inta.org<mailto:rodonnell at Inta.org?subject=Hello>
inta.org<https://www.inta.org/>  |  Locations<https://www.inta.org/about/contact-us/>  |  Social Media<https://www.inta.org/about/social-media/>


From: Andrea Glandon via Csg-excomm <csg-excomm at icann.org>
Sent: Friday, November 8, 2024 4:32 PM
To: csg-excomm at icann.org; ncsg-ec at lists.ncsg.is; ncsg-pc at lists.ncsg.is
Subject: [Csg-excomm] GNSO Council Vice Chair-Tomslin

Hello!

I just heard from the GNSO Secretariat that an official email was not received regarding Tomslin continuing as vice chair of the GNSO Council. If an email can be sent to GNSO Secs with this confirmation that would be great.

Thanks!
Andrea Glandon
Policy Operations Sr. Coordinator
Internet Corporation for Assigned Names and Numbers (ICANN)
Skype ID:  acglandon76



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20241109/e873a1ea/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 6960 bytes
Desc: image001.png
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20241109/e873a1ea/attachment.png>

From julie.bisland at icann.org  Sun Nov 10 04:50:09 2024
From: julie.bisland at icann.org (Julie Bisland)
Date: Sun, 10 Nov 2024 02:50:09 +0000
Subject: [NCSG-PC] GNSO Council Vice Chair-Tomslin
In-Reply-To: <BL1PR12MB5030CD18A877B8AFAC6C44E9D35E2@BL1PR12MB5030.namprd12.prod.outlook.com>
References: <9449F2FE-FE16-47D9-91F8-2A7405872155@icann.org>
 <BL1PR12MB5030CD18A877B8AFAC6C44E9D35E2@BL1PR12MB5030.namprd12.prod.outlook.com>
Message-ID: <B221BC8B-9702-4754-9ADD-A3B71E53CFCD@icann.org>

Thank you, Lori! We will announce to the GNSO Council mailing list.

All the best,

Julie

--
Julie Bisland
Policy Team Supporting the GNSO


From: Lori Schulman <lschulman at inta.org>
Date: Saturday, November 9, 2024 at 1:50?PM
To: GNSO-Secs <gnso-secs at icann.org>
Cc: Andrea Glandon <andrea.glandon at icann.org>, "csg-excomm at icann.org" <csg-excomm at icann.org>, "ncsg-ec at lists.ncsg.is" <ncsg-ec at lists.ncsg.is>, "ncsg-pc at lists.ncsg.is" <ncsg-pc at lists.ncsg.is>, Tomslin Samme-Nlar <mesumbeslin at gmail.com>, Johan Helsingius <julf.helsingius at gmail.com>, "julf at julf.com" <julf at Julf.com>
Subject: RE: GNSO Council Vice Chair-Tomslin

Dear GNSO Secretariat,

Please consider this an official email from NCPH in support of a renewed term for Tomslin Samme-Nlar as Vice Chair of the GNSO Council.  I am sending in my capacity as CSG Chair with the agreement from Julf Helsingus NCSG Chair.

Please advise as to whether Julf or I can be of further assistance.

Thank you.


With kind regards,

[cid:image001.png at 01DB32E8.F662E780]<http://www.inta.org/>

Lori Schulman
Senior Director, Internet Policy
International Trademark Association
LSchulman at inta.org<mailto:rodonnell at Inta.org?subject=Hello>
inta.org<https://www.inta.org/>  |  Locations<https://www.inta.org/about/contact-us/>  |  Social Media<https://www.inta.org/about/social-media/>



From: Andrea Glandon via Csg-excomm <csg-excomm at icann.org>
Sent: Friday, November 8, 2024 4:32 PM
To: csg-excomm at icann.org; ncsg-ec at lists.ncsg.is; ncsg-pc at lists.ncsg.is
Subject: [Csg-excomm] GNSO Council Vice Chair-Tomslin

Hello!

I just heard from the GNSO Secretariat that an official email was not received regarding Tomslin continuing as vice chair of the GNSO Council. If an email can be sent to GNSO Secs with this confirmation that would be great.

Thanks!
Andrea Glandon
Policy Operations Sr. Coordinator
Internet Corporation for Assigned Names and Numbers (ICANN)
Skype ID:  acglandon76



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20241110/5de9ab4a/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 6961 bytes
Desc: image001.png
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20241110/5de9ab4a/attachment.png>

From pedrodeperdigaolana at gmail.com  Wed Nov 13 13:17:33 2024
From: pedrodeperdigaolana at gmail.com (=?UTF-8?Q?Pedro_de_Perdig=C3=A3o_Lana?=)
Date: Wed, 13 Nov 2024 14:17:33 +0300
Subject: [NCSG-PC] COUNCIL DISCUSSION - PSR on RPM PDP Phase 2
Message-ID: <CAGSP6RRmfykMvZCjObuj9O5VQDpQpULPJERXdQd=iLyGREb-zA@mail.gmail.com>

Hi everyone,

I was following Item 7 (*COUNCIL DISCUSSION - Policy Status Report (PSR) on
Rights Protection Mechanisms PDP Phase 2*) of the GNSO Council Meeting and
got a bit concerned about what a few people from other groups were saying
there (btw, thanks Stephanie for commenting in the chat, which also
prompted a very positive comment from Paul).

I understand that we are going to, in the near future, designate council
members to work on this issue. I would like to ask which of our councilors
intend to follow this issue, and I would like to already volunteer to help
on this task - of course, if the designated councilor accepts this help.

Cordially,

*Pedro de Perdig?o Lana*
Lawyer <https://www.nic.br/>, GEDAI/UFPR <https://www.gedai.com.br/>
Researcher
PhD Candidate (UFPR), LLM in Business Law (UCoimbra)
Coordination/Board/EC @ ISOC BR <https://isoc.org.br/>, NCUC
<https://www.ncuc.org> & NCSG
<https://community.icann.org/display/gnsononcomstake/Home>(ICANN),
YouthLACIGF <https://youthlacigf.lat/>, IODA <https://ioda.org.br/> and CC
Brasil <https://br.creativecommons.net/>
This message is restricted to the sender and recipient(s). If received by
mistake, please reply informing it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20241113/c66f9554/attachment.htm>

From rafik.dammak at gmail.com  Thu Nov 21 07:23:34 2024
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Thu, 21 Nov 2024 14:23:34 +0900
Subject: [NCSG-PC] Fwd: Please Respond by 18 December | Annual SSC Refresh
In-Reply-To: <F7B86CAF-A4AB-4687-BC63-A667E299877B@icann.org>
References: <F7B86CAF-A4AB-4687-BC63-A667E299877B@icann.org>
Message-ID: <CAH5sTh=N66NsY-_qk4bwPzsazv=vZDdTRA1X38GQ4Gy02n4DYQ@mail.gmail.com>

Hi all,

The cycle to confirm/appoint NCSG representatives to SSC just started  and
we have to send the names by 18th December giving us roughly one month.

@Tomslin Samme-Nlar <mesumbeslin at gmail.com> can the PC confirm with current
representatives  and issue call for candidates adaptation.
This is a critical selection as I understand the concerns about some of
selections made by SSC.

Best,

Rafik




---------- Forwarded message ---------
From: Julie Bisland <julie.bisland at icann.org>
Date: Thu, Nov 21, 2024, 01:14
Subject: Please Respond by 18 December | Annual SSC Refresh
To: Mason Cole (Preferred email) <MCole at perkinscoie.com>, John McElwaine <
john.mcelwaine at nelsonmullins.com>, Philippe Fouquart <
philippe.fouquart at orange.com>, Wisdom Donkor <wisdom.dk at gmail.com>, Juan
Manuel Rojas <jumaropi at yahoo.com>, Owen Smigelski <
owen.smigelski at namecheap.com>, Elizabeth Bacon <beth at pir.org>, Rafik Dammak
<rafik.dammak at gmail.com>
Cc: Sue Schuler <secretariat at rysg.info>, GNSO-Secs <gnso-secs at icann.org>,
Zoe Bonython <secretariat at icannregistrars.org>, Andrea Glandon <
andrea.glandon at icann.org>, gnso-chairs at icann.org <gnso-chairs at icann.org>


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 assignments it
received from the GNSO Council:


GNSO Appointed Mentor - ICANN Fellowship Program - 2024
<https://community.icann.org/display/GSSC/GNSO+Appointed+Mentor+-+ICANN+Fellowship+Program+-+2024>

GAC Liaison - 2024
<https://community.icann.org/display/GSSC/GAC+Liaison+-+2024>

Pilot Holistic Review - 2024
<https://community.icann.org/display/GSSC/Pilot+Holistic+Review+-+2024>



The next anticipated SSC assignment is again the annual selection the ICANN
Fellowship Program mentor, to be selected by the end of January. 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, members may serve a maximum of two
consecutive terms. *We are reaching out to you to re-confirm members that
are eligible to continue serving on the SSC and/or identify replacements
for those members who are not eligible, as noted in the status column in
the table below:*





*Name*

*Appointed by*

*SOI*

*Member/Alternate Since:*

*Status*

Karen Day (Chair)

RySG

Karen Day SOI <https://community.icann.org/x/vQWAAw>

January 2024

Eligible for another term

Jothan Frakes

RrSG

Jothan Frakes SOI <https://community.icann.org/x/Gb-hAg>

January 2024

Eligible for another term

Segunfunmi Olajide (Vice-Chair)

BC

Segunfunmi Olajide SOI <https://community.icann.org/x/7YoFDQ>

January 2024

Eligible for another term

Marie Pattullo

BC Alternate

Marie Pattullo SOI <https://community.icann.org/x/OTWAAw>

January 2024

Eligible for another term

Christian Dawson

ISPCP

Christian Dawson SOI <https://community.icann.org/x/NivRAg>

October 2022

*Not eligible for another term*

Mike Rodenbaugh

IPC

Mike Rodenbaugh SOI <https://community.icann.org/x/Ah9-Ag>

February 2024

Eligible for another term

Remmy Nweke

NCSG

Remmy Nweke SOI <https://community.icann.org/x/3MXRAw>

February 2024

Eligible for another term

Arsene Tungali

NCSG

Arsene Tungali SOI <https://community.icann.org/x/vmjwAw>

December 2022

*Not eligible for another term*

Bruna Martins dos Santos

NCSG

Bruna Martins dos Santos SOI <https://community.icann.org/x/iBvwAw>

February 2024

Eligible for another term

Desiree Miloshevic Evans

NomCom

Desiree Miloshevic Evans SOI <https://community.icann.org/x/zAJyCg>

February 2024

Eligible for another term

Tomslin Samme-Nlar

Ex-Officio Member Representing GNSO Council Leadership

Tomslin Samme-Nlar SOI <https://community.icann.org/x/8ZxEB>

Ex-Officio Member Representing GNSO Council Leadership Since January 2024

GNSO Council leadership appointment



For information about the SSC, please see the wiki page
<https://community.icann.org/display/GSSC/GNSO+Standing+Selection+Committee+Home>
.



*Please send confirmations and/or new appointments as soon as possible, but
no later than Wednesday, 18 December 2024, if possible.*



Do not hesitate to get in touch if you have any questions.



Kind regards,

Saewon and Julie

SSC Support Staff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20241121/d32dd01f/attachment.htm>

From mesumbeslin at gmail.com  Thu Nov 21 21:40:13 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Fri, 22 Nov 2024 06:40:13 +1100
Subject: [NCSG-PC] Fwd: [council] Reminder: Input welcome on GNSO Council
 agenda for 2024 meetings
In-Reply-To: <76739BD0-3080-43BF-971A-7B165227AB1A@icann.org>
References: <1955DFD7-FA6E-4B2E-B7E0-57F7BEC333CD@icann.org>
 <0D837D31-4A7E-49DC-92F6-42DFF96B3F52@icann.org>
 <4F1A9987-466F-41B1-B4FA-AF4F8725A2E8@icann.org>
 <B5067A42-0F07-4466-B1CE-CCB2BA88122B@icann.org>
 <B232F541-A875-491F-AD9B-7B1F4927778F@icann.org>
 <2347C19B-51BA-4807-88BA-8E355D042B41@icann.org>
 <C818F36B-4E40-4F86-A92F-77A3A3230BDA@icann.org>
 <76739BD0-3080-43BF-971A-7B165227AB1A@icann.org>
Message-ID: <CAM8DdeVAs1UBZSYtEJytY43hPJJv=gU+QFLXL0sr0Kh5e8T4qA@mail.gmail.com>

NCSG Councillors,

Coming off the back of the discussion in Istanbul about the agenda of the
meeting, I wanted to also point out that this is another way councillors
themselves can influence the council agenda. I encourage you to contribute
to the agenda setting every month and for every physical meeting.

Warmly,
Tomslin



---------- Forwarded message ---------
From: Terri Agnew via council <council at icann.org>
Date: Fri, 22 Nov 2024 at 06:35
Subject: [council] Reminder: Input welcome on GNSO Council agenda for 2024
meetings
To: council at gnso.icann.org <council at gnso.icann.org>
Cc: GNSO-Secs <gnso-secs at icann.org>


Dear councilors,



A reminder to all that a Google doc
<https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAzKcfltI7SWwzXda1NtKxfQ2k-t0oiGr8/edit?usp=sharing__;!!PtGJab4!pxvIXA-OvQqR_dwjUMla69QRKF6XSAek3rpvt8Zf314kYza33ELe-N7uhgpFx2Mtm1X1qPm3WSSt$>
is open for all to add their suggestions and comments to the upcoming GNSO
Council meeting agendas. This does not have to be in the form of a full
agenda item proposal, simple comments and questions are equally welcome!



You are welcome to add to the document
<https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAzKcfltI7SWwzXda1NtKxfQ2k-t0oiGr8/edit*heading=h.unjpfxy4jex9__;Iw!!PtGJab4!tRxZkeQOaKGyiE0RgSSqu6ntCNMQ7z_mKxbpmK0f6BPXvRjS1hWCT0IVu681uBQIXNewd6bVSSbG$>
via the comments feature.



Thank you!



Kind regards,



Terri

Policy Team Supporting the GNSO






_______________________________________________
council mailing list -- council at icann.org
To unsubscribe send an email to council-leave at icann.org

_______________________________________________
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/20241122/cc6ad60f/attachment.htm>

From mesumbeslin at gmail.com  Thu Nov 21 22:18:38 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Fri, 22 Nov 2024 07:18:38 +1100
Subject: [NCSG-PC] Fwd: Please Respond by 18 December | Annual SSC
 Refresh
In-Reply-To: <CAH5sTh=N66NsY-_qk4bwPzsazv=vZDdTRA1X38GQ4Gy02n4DYQ@mail.gmail.com>
References: <F7B86CAF-A4AB-4687-BC63-A667E299877B@icann.org>
 <CAH5sTh=N66NsY-_qk4bwPzsazv=vZDdTRA1X38GQ4Gy02n4DYQ@mail.gmail.com>
Message-ID: <CAM8DdeXR6zaF9iiW6HMTD0by9unUn5+ZkLT38i0bduap7roW5A@mail.gmail.com>

Thanks, Rafik. Working on it.

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


On Thu, 21 Nov 2024 at 16:23, Rafik Dammak <rafik.dammak at gmail.com> wrote:

> Hi all,
>
> The cycle to confirm/appoint NCSG representatives to SSC just started  and
> we have to send the names by 18th December giving us roughly one month.
>
> @Tomslin Samme-Nlar <mesumbeslin at gmail.com> can the PC confirm with
> current representatives  and issue call for candidates adaptation.
> This is a critical selection as I understand the concerns about some of
> selections made by SSC.
>
> Best,
>
> Rafik
>
>
>
>
> ---------- Forwarded message ---------
> From: Julie Bisland <julie.bisland at icann.org>
> Date: Thu, Nov 21, 2024, 01:14
> Subject: Please Respond by 18 December | Annual SSC Refresh
> To: Mason Cole (Preferred email) <MCole at perkinscoie.com>, John McElwaine <
> john.mcelwaine at nelsonmullins.com>, Philippe Fouquart <
> philippe.fouquart at orange.com>, Wisdom Donkor <wisdom.dk at gmail.com>, Juan
> Manuel Rojas <jumaropi at yahoo.com>, Owen Smigelski <
> owen.smigelski at namecheap.com>, Elizabeth Bacon <beth at pir.org>, Rafik
> Dammak <rafik.dammak at gmail.com>
> Cc: Sue Schuler <secretariat at rysg.info>, GNSO-Secs <gnso-secs at icann.org>,
> Zoe Bonython <secretariat at icannregistrars.org>, Andrea Glandon <
> andrea.glandon at icann.org>, gnso-chairs at icann.org <gnso-chairs at icann.org>
>
>
> 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 assignments it
> received from the GNSO Council:
>
>
> GNSO Appointed Mentor - ICANN Fellowship Program - 2024
> <https://community.icann.org/display/GSSC/GNSO+Appointed+Mentor+-+ICANN+Fellowship+Program+-+2024>
>
> GAC Liaison - 2024
> <https://community.icann.org/display/GSSC/GAC+Liaison+-+2024>
>
> Pilot Holistic Review - 2024
> <https://community.icann.org/display/GSSC/Pilot+Holistic+Review+-+2024>
>
>
>
> The next anticipated SSC assignment is again the annual selection the ICANN
> Fellowship Program mentor, to be selected by the end of January. 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, members may serve a maximum of two
> consecutive terms. *We are reaching out to you to re-confirm members that
> are eligible to continue serving on the SSC and/or identify replacements
> for those members who are not eligible, as noted in the status column in
> the table below:*
>
>
>
>
>
> *Name*
>
> *Appointed by*
>
> *SOI*
>
> *Member/Alternate Since:*
>
> *Status*
>
> Karen Day (Chair)
>
> RySG
>
> Karen Day SOI <https://community.icann.org/x/vQWAAw>
>
> January 2024
>
> Eligible for another term
>
> Jothan Frakes
>
> RrSG
>
> Jothan Frakes SOI <https://community.icann.org/x/Gb-hAg>
>
> January 2024
>
> Eligible for another term
>
> Segunfunmi Olajide (Vice-Chair)
>
> BC
>
> Segunfunmi Olajide SOI <https://community.icann.org/x/7YoFDQ>
>
> January 2024
>
> Eligible for another term
>
> Marie Pattullo
>
> BC Alternate
>
> Marie Pattullo SOI <https://community.icann.org/x/OTWAAw>
>
> January 2024
>
> Eligible for another term
>
> Christian Dawson
>
> ISPCP
>
> Christian Dawson SOI <https://community.icann.org/x/NivRAg>
>
> October 2022
>
> *Not eligible for another term*
>
> Mike Rodenbaugh
>
> IPC
>
> Mike Rodenbaugh SOI <https://community.icann.org/x/Ah9-Ag>
>
> February 2024
>
> Eligible for another term
>
> Remmy Nweke
>
> NCSG
>
> Remmy Nweke SOI <https://community.icann.org/x/3MXRAw>
>
> February 2024
>
> Eligible for another term
>
> Arsene Tungali
>
> NCSG
>
> Arsene Tungali SOI <https://community.icann.org/x/vmjwAw>
>
> December 2022
>
> *Not eligible for another term*
>
> Bruna Martins dos Santos
>
> NCSG
>
> Bruna Martins dos Santos SOI <https://community.icann.org/x/iBvwAw>
>
> February 2024
>
> Eligible for another term
>
> Desiree Miloshevic Evans
>
> NomCom
>
> Desiree Miloshevic Evans SOI <https://community.icann.org/x/zAJyCg>
>
> February 2024
>
> Eligible for another term
>
> Tomslin Samme-Nlar
>
> Ex-Officio Member Representing GNSO Council Leadership
>
> Tomslin Samme-Nlar SOI <https://community.icann.org/x/8ZxEB>
>
> Ex-Officio Member Representing GNSO Council Leadership Since January 2024
>
> GNSO Council leadership appointment
>
>
>
> For information about the SSC, please see the wiki page
> <https://community.icann.org/display/GSSC/GNSO+Standing+Selection+Committee+Home>
> .
>
>
>
> *Please send confirmations and/or new appointments as soon as possible,
> but no later than Wednesday, 18 December 2024, if possible.*
>
>
>
> Do not hesitate to get in touch if you have any questions.
>
>
>
> Kind regards,
>
> Saewon and Julie
>
> SSC Support Staff
> _______________________________________________
> 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/20241122/49ac9ef4/attachment.htm>

From manju at nii.org.tw  Fri Nov 22 01:36:01 2024
From: manju at nii.org.tw (=?UTF-8?B?6Zmz5pu86Iy5IE1hbmp1IENoZW4=?=)
Date: Fri, 22 Nov 2024 10:36:01 +1100
Subject: [NCSG-PC] Fwd: [council] Reminder: Input welcome on GNSO
 Council agenda for 2024 meetings
In-Reply-To: <CAM8DdeVAs1UBZSYtEJytY43hPJJv=gU+QFLXL0sr0Kh5e8T4qA@mail.gmail.com>
References: <1955DFD7-FA6E-4B2E-B7E0-57F7BEC333CD@icann.org>
 <0D837D31-4A7E-49DC-92F6-42DFF96B3F52@icann.org>
 <4F1A9987-466F-41B1-B4FA-AF4F8725A2E8@icann.org>
 <B5067A42-0F07-4466-B1CE-CCB2BA88122B@icann.org>
 <B232F541-A875-491F-AD9B-7B1F4927778F@icann.org>
 <2347C19B-51BA-4807-88BA-8E355D042B41@icann.org>
 <C818F36B-4E40-4F86-A92F-77A3A3230BDA@icann.org>
 <76739BD0-3080-43BF-971A-7B165227AB1A@icann.org>
 <CAM8DdeVAs1UBZSYtEJytY43hPJJv=gU+QFLXL0sr0Kh5e8T4qA@mail.gmail.com>
Message-ID: <CAMeQZi0seLLRYkBwr68LDZkpEHVj9snu_DW2uoJOYwX7mBS9fw@mail.gmail.com>

Hi Tomslin,

Thank you so much!!

But we were talking about the agenda of the working sessions and our
session with the Board, which was not shared with the councilors in advance
and we had zero control over.

We were saying that we should?ve discussed the agenda of our session with
the Board during our working sessions, which were unfortunately packed with
updates that councilors were forced to be only be in a listening mode. And
again, councilors were not involved in the agenda setting of the working
sessions.

But yes, we should always be more alert of the ways where we can contribute
and exercise influences. Thank you again for the reminder!


Best,
Manju


On Fri, Nov 22, 2024 at 06:40 Tomslin Samme-Nlar <mesumbeslin at gmail.com>
wrote:

> NCSG Councillors,
>
> Coming off the back of the discussion in Istanbul about the agenda of the
> meeting, I wanted to also point out that this is another way councillors
> themselves can influence the council agenda. I encourage you to contribute
> to the agenda setting every month and for every physical meeting.
>
> Warmly,
> Tomslin
>
>
>
> ---------- Forwarded message ---------
> From: Terri Agnew via council <council at icann.org>
> Date: Fri, 22 Nov 2024 at 06:35
> Subject: [council] Reminder: Input welcome on GNSO Council agenda for 2024
> meetings
> To: council at gnso.icann.org <council at gnso.icann.org>
> Cc: GNSO-Secs <gnso-secs at icann.org>
>
>
> Dear councilors,
>
>
>
> A reminder to all that a Google doc
> <https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAzKcfltI7SWwzXda1NtKxfQ2k-t0oiGr8/edit?usp=sharing__;!!PtGJab4!pxvIXA-OvQqR_dwjUMla69QRKF6XSAek3rpvt8Zf314kYza33ELe-N7uhgpFx2Mtm1X1qPm3WSSt$>
> is open for all to add their suggestions and comments to the upcoming GNSO
> Council meeting agendas. This does not have to be in the form of a full
> agenda item proposal, simple comments and questions are equally welcome!
>
>
>
> You are welcome to add to the document
> <https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAzKcfltI7SWwzXda1NtKxfQ2k-t0oiGr8/edit*heading=h.unjpfxy4jex9__;Iw!!PtGJab4!tRxZkeQOaKGyiE0RgSSqu6ntCNMQ7z_mKxbpmK0f6BPXvRjS1hWCT0IVu681uBQIXNewd6bVSSbG$>
> via the comments feature.
>
>
>
> Thank you!
>
>
>
> Kind regards,
>
>
>
> Terri
>
> Policy Team Supporting the GNSO
>
>
>
>
>
>
> _______________________________________________
> council mailing list -- council at icann.org
> To unsubscribe send an email to council-leave at icann.org
>
> _______________________________________________
> 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/20241122/16ce624d/attachment.htm>

From mesumbeslin at gmail.com  Fri Nov 22 02:05:36 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Fri, 22 Nov 2024 11:05:36 +1100
Subject: [NCSG-PC] Fwd: [council] Reminder: Input welcome on GNSO
 Council agenda for 2024 meetings
In-Reply-To: <CAMeQZi0seLLRYkBwr68LDZkpEHVj9snu_DW2uoJOYwX7mBS9fw@mail.gmail.com>
References: <1955DFD7-FA6E-4B2E-B7E0-57F7BEC333CD@icann.org>
 <0D837D31-4A7E-49DC-92F6-42DFF96B3F52@icann.org>
 <4F1A9987-466F-41B1-B4FA-AF4F8725A2E8@icann.org>
 <B5067A42-0F07-4466-B1CE-CCB2BA88122B@icann.org>
 <B232F541-A875-491F-AD9B-7B1F4927778F@icann.org>
 <2347C19B-51BA-4807-88BA-8E355D042B41@icann.org>
 <C818F36B-4E40-4F86-A92F-77A3A3230BDA@icann.org>
 <76739BD0-3080-43BF-971A-7B165227AB1A@icann.org>
 <CAM8DdeVAs1UBZSYtEJytY43hPJJv=gU+QFLXL0sr0Kh5e8T4qA@mail.gmail.com>
 <CAMeQZi0seLLRYkBwr68LDZkpEHVj9snu_DW2uoJOYwX7mBS9fw@mail.gmail.com>
Message-ID: <CAM8DdeXCpocBF2PyPaMTdyB1bEhuNRqnr=YjqpJZE5OJV5dM2g@mail.gmail.com>

Thanks for the clarification, Manju.

I can also confirm that today, I raised the issue with council leadership
and staff planning team regarding having atleast one council working
session before any council bilateral meetings for the purpose of whole
council discussing and contributing to the agendas of the bilaterals. Staff
has gone away to plan accordingly. I will keep you posted.

Warmly,
Tomslin

On Fri, 22 Nov 2024, 10:36 ??? Manju Chen, <manju at nii.org.tw> wrote:

> Hi Tomslin,
>
> Thank you so much!!
>
> But we were talking about the agenda of the working sessions and our
> session with the Board, which was not shared with the councilors in advance
> and we had zero control over.
>
> We were saying that we should?ve discussed the agenda of our session with
> the Board during our working sessions, which were unfortunately packed with
> updates that councilors were forced to be only be in a listening mode. And
> again, councilors were not involved in the agenda setting of the working
> sessions.
>
> But yes, we should always be more alert of the ways where we can
> contribute and exercise influences. Thank you again for the reminder!
>
>
> Best,
> Manju
>
>
> On Fri, Nov 22, 2024 at 06:40 Tomslin Samme-Nlar <mesumbeslin at gmail.com>
> wrote:
>
>> NCSG Councillors,
>>
>> Coming off the back of the discussion in Istanbul about the agenda of the
>> meeting, I wanted to also point out that this is another way councillors
>> themselves can influence the council agenda. I encourage you to contribute
>> to the agenda setting every month and for every physical meeting.
>>
>> Warmly,
>> Tomslin
>>
>>
>>
>> ---------- Forwarded message ---------
>> From: Terri Agnew via council <council at icann.org>
>> Date: Fri, 22 Nov 2024 at 06:35
>> Subject: [council] Reminder: Input welcome on GNSO Council agenda for
>> 2024 meetings
>> To: council at gnso.icann.org <council at gnso.icann.org>
>> Cc: GNSO-Secs <gnso-secs at icann.org>
>>
>>
>> Dear councilors,
>>
>>
>>
>> A reminder to all that a Google doc
>> <https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAzKcfltI7SWwzXda1NtKxfQ2k-t0oiGr8/edit?usp=sharing__;!!PtGJab4!pxvIXA-OvQqR_dwjUMla69QRKF6XSAek3rpvt8Zf314kYza33ELe-N7uhgpFx2Mtm1X1qPm3WSSt$>
>> is open for all to add their suggestions and comments to the upcoming GNSO
>> Council meeting agendas. This does not have to be in the form of a full
>> agenda item proposal, simple comments and questions are equally welcome!
>>
>>
>>
>> You are welcome to add to the document
>> <https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAzKcfltI7SWwzXda1NtKxfQ2k-t0oiGr8/edit*heading=h.unjpfxy4jex9__;Iw!!PtGJab4!tRxZkeQOaKGyiE0RgSSqu6ntCNMQ7z_mKxbpmK0f6BPXvRjS1hWCT0IVu681uBQIXNewd6bVSSbG$>
>> via the comments feature.
>>
>>
>>
>> Thank you!
>>
>>
>>
>> Kind regards,
>>
>>
>>
>> Terri
>>
>> Policy Team Supporting the GNSO
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> council mailing list -- council at icann.org
>> To unsubscribe send an email to council-leave at icann.org
>>
>> _______________________________________________
>> 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/20241122/050b487e/attachment.htm>

From mesumbeslin at gmail.com  Tue Nov 26 21:14:10 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Wed, 27 Nov 2024 06:14:10 +1100
Subject: [NCSG-PC] Fwd: [council] Call for Volunteers for SCCI | Please
 Respond by 6 January
In-Reply-To: <698C84A1-F28A-4430-A052-E39612BAD9F5@icann.org>
References: <698C84A1-F28A-4430-A052-E39612BAD9F5@icann.org>
Message-ID: <CAM8DdeV4EFNFj3ADbcKkwxDzr2djA-M3o5ngi0BATgYA-1zmEQ@mail.gmail.com>

Hi Councillors,

Who would like to volunteer as our rep to the newly formed SCCI?

Warmly,
Tomslin



---------- Forwarded message ---------
From: Devan Reed via council <council at icann.org>
Date: Wed, 27 Nov 2024 at 01:05
Subject: [council] Call for Volunteers for SCCI | Please Respond by 6
January
To: council at gnso.icann.org <council at gnso.icann.org>
Cc: GNSO-Secs <gnso-secs at icann.org>


*Dear Councilors,*



The Generic Names Supporting Organization (GNSO) Council seeks volunteers
to serve on the Standing Committee on Continuous Improvement (SCCI). The
SCCI will be in charge of continuous improvement related projects that are
focused on the GNSO?s structural, procedural, and process improvements to
the Policy Development Process (PDP). This work originally commenced
through a pilot under the Council Committee for Overseeing and Implementing
Continuous Improvement (CCOICI) Framework
<https://gnso.icann.org/sites/default/files/file/field-file-attach/continuous-improvement-oversight-implementation-framework-29jun21-en.pdf>
 (last updated 29 June 2021), which has now converted to a permanent
standing committee following the GNSO Council?s adoption of the charter
<https://gnso.icann.org/en/council/resolutions/2020-current#202411>.



*What This Standing Committee Will Do*

The SCCI and its dedicated Task Forces (TFs), populated by the Councilors
and representatives of each Stakeholder Group (SG) and Constituency (C)
(hereafter ?SG/C?), will execute a continuous improvement program that aims
to improve the GNSO?s process and procedures over time through gradual
changes. The goal is to achieve measurable improvements in the efficiency,
effectiveness, performance, outcomes, accountability, transparency, and
other indicators of quality for the GNSO. Notably, this work affects the
GNSO community more broadly and is not limited to that of the Council.



Considering that this is a permanent standing committee, the specific scope
of work across the varying projects that the SCCI and TFs will execute is
not overly prescribed within the charter
<https://gnso.icann.org/sites/default/files/policy/2024/draft/scci-charter-draft-update-13nov24-en.pdf>,
as to avoid frequent edits and subsequent approvals. Previous efforts were
initiated by the Council, while other changes were accomplished through
Organizational Reviews anchored in Article 4.4. of the ICANN Bylaws
<https://www.icann.org/resources/pages/governance/bylaws-en#article4.4>. As
the ICANN community evolves towards a larger continuous improvement
program, the GNSO?s SCCI and its TFs will be heavily involved in these
efforts. While broad, GNSO project assignments will be limited to any
processes and procedures that would have a GNSO-wide impact only. For
avoidance of doubt, all assignments of the SCCI and TFs shall be first
approved by the Council. Subsequently, any outcomes of the SCCI and TFs?
project related work will be sent to the Council for their consideration
and follow-up actions, if any. More details on the scope of projects can be
found in Section II of the charter
<https://gnso.icann.org/sites/default/files/policy/2024/draft/scci-charter-draft-update-13nov24-en.pdf>
 and as new projects and/or assignments are distributed and in due course,
completed, they will be managed via the GNSO?s Program Management Tool
(PMT) Suite
<https://community.icann.org/pages/viewpage.action?pageId=150178769>.



*Who Should Join*

SCCI is a representative model which shall consist of *a total of 21
Members, 2 Board Liaisons, and 9 Observers.* All those that join will serve
in representative capacity, where applicable, and as such, be responsible
for consulting with their respective groups on a regular basis:

   - A maximum of two members from each SG/C (14)
   - One Council member from the Registrar Stakeholder Group (RrSG) (1)
   - One Council member from the Registry Stakeholder Group (RySG) (1)
   - One Council member from the Commercial Stakeholder Group (CSG) (1)
   - One Council member from the Non-Commercial Stakeholder Group (NCSG) (1)
   - One Council NomCom Appointee (NCA) from each house (2)
   - One Council NomCom Appointee, non-voting (1)
   - Two GNSO Board Liaisons
      - One CPH Board seat #13 (1)
      - One NCPH Board seat #14 (1)


   - Nine Observers:
      - One Council Chair (1)
      - One Chair from each SG/C (8)



Members that are not a part of the Council will not have terms. Councilors,
Observers, and Liaisons will turn-over naturally as their terms, defined in
the ICANN Bylaws, conclude and are replaced by new representatives.
However, SG/Cs who nominate members to participate should frequently assess
and refresh their designated representatives to ensure active
participation. Members must be appointed and/or reconfirmed by the
leadership of the appointing SG/C and notification to the SCCI Chair and
support staff.



*How to Join*

GNSO community members who wish to join the Standing Committee should
contact the GNSO Secretariat at *gnso-secs at icann.org <gnso-secs at icann.org>*
by *Monday, 6 January 2025.*



*Background*

For more information and to better prepare for participation on this
Standing Committee, please read its charter
<https://gnso.icann.org/sites/default/files/policy/2024/draft/scci-charter-draft-update-13nov24-en.pdf>,
as well as visiting the CCOICI wiki page
<https://community.icann.org/display/CCFOICI>.



Please do not hesitate to get in touch if you have any questions.



Kind regards,

Julie H., Berry, and Saewon

SCCI Support Staff


_______________________________________________
council mailing list -- council at icann.org
To unsubscribe send an email to council-leave at icann.org

_______________________________________________
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/20241127/edb0c158/attachment.htm>

From compsoftnet at gmail.com  Tue Nov 26 22:49:12 2024
From: compsoftnet at gmail.com (Akinremi Peter Taiwo)
Date: Tue, 26 Nov 2024 15:49:12 -0500
Subject: [NCSG-PC] Fwd: [council] Call for Volunteers for SCCI | Please
 Respond by 6 January
In-Reply-To: <CAM8DdeV4EFNFj3ADbcKkwxDzr2djA-M3o5ngi0BATgYA-1zmEQ@mail.gmail.com>
References: <698C84A1-F28A-4430-A052-E39612BAD9F5@icann.org>
 <CAM8DdeV4EFNFj3ADbcKkwxDzr2djA-M3o5ngi0BATgYA-1zmEQ@mail.gmail.com>
Message-ID: <CAGK4d0-FkL0PbKae1Kd9QnUCeTpEd68hA7K2sMQfiWUmWuc3CQ@mail.gmail.com>

Hi Tomslin,

I am hoping Manju will serve as the chair of the SCCI, if yes, I would like
to volunteer as the NCSG Rep

Kind regards

On Tue, Nov 26, 2024 at 2:14?PM Tomslin Samme-Nlar <mesumbeslin at gmail.com>
wrote:

> Hi Councillors,
>
> Who would like to volunteer as our rep to the newly formed SCCI?
>
> Warmly,
> Tomslin
>
>
>
> ---------- Forwarded message ---------
> From: Devan Reed via council <council at icann.org>
> Date: Wed, 27 Nov 2024 at 01:05
> Subject: [council] Call for Volunteers for SCCI | Please Respond by 6
> January
> To: council at gnso.icann.org <council at gnso.icann.org>
> Cc: GNSO-Secs <gnso-secs at icann.org>
>
>
> *Dear Councilors,*
>
>
>
> The Generic Names Supporting Organization (GNSO) Council seeks volunteers
> to serve on the Standing Committee on Continuous Improvement (SCCI). The
> SCCI will be in charge of continuous improvement related projects that are
> focused on the GNSO?s structural, procedural, and process improvements to
> the Policy Development Process (PDP). This work originally commenced
> through a pilot under the Council Committee for Overseeing and
> Implementing Continuous Improvement (CCOICI) Framework
> <https://gnso.icann.org/sites/default/files/file/field-file-attach/continuous-improvement-oversight-implementation-framework-29jun21-en.pdf>
>  (last updated 29 June 2021), which has now converted to a permanent
> standing committee following the GNSO Council?s adoption of the charter
> <https://gnso.icann.org/en/council/resolutions/2020-current#202411>.
>
>
>
> *What This Standing Committee Will Do*
>
> The SCCI and its dedicated Task Forces (TFs), populated by the Councilors
> and representatives of each Stakeholder Group (SG) and Constituency (C)
> (hereafter ?SG/C?), will execute a continuous improvement program that aims
> to improve the GNSO?s process and procedures over time through gradual
> changes. The goal is to achieve measurable improvements in the efficiency,
> effectiveness, performance, outcomes, accountability, transparency, and
> other indicators of quality for the GNSO. Notably, this work affects the
> GNSO community more broadly and is not limited to that of the Council.
>
>
>
> Considering that this is a permanent standing committee, the specific
> scope of work across the varying projects that the SCCI and TFs will
> execute is not overly prescribed within the charter
> <https://gnso.icann.org/sites/default/files/policy/2024/draft/scci-charter-draft-update-13nov24-en.pdf>,
> as to avoid frequent edits and subsequent approvals. Previous efforts were
> initiated by the Council, while other changes were accomplished through
> Organizational Reviews anchored in Article 4.4. of the ICANN Bylaws
> <https://www.icann.org/resources/pages/governance/bylaws-en#article4.4>.
> As the ICANN community evolves towards a larger continuous improvement
> program, the GNSO?s SCCI and its TFs will be heavily involved in these
> efforts. While broad, GNSO project assignments will be limited to any
> processes and procedures that would have a GNSO-wide impact only. For
> avoidance of doubt, all assignments of the SCCI and TFs shall be first
> approved by the Council. Subsequently, any outcomes of the SCCI and TFs?
> project related work will be sent to the Council for their consideration
> and follow-up actions, if any. More details on the scope of projects can be
> found in Section II of the charter
> <https://gnso.icann.org/sites/default/files/policy/2024/draft/scci-charter-draft-update-13nov24-en.pdf>
>  and as new projects and/or assignments are distributed and in due
> course, completed, they will be managed via the GNSO?s Program Management
> Tool (PMT) Suite
> <https://community.icann.org/pages/viewpage.action?pageId=150178769>.
>
>
>
> *Who Should Join*
>
> SCCI is a representative model which shall consist of *a total of 21
> Members, 2 Board Liaisons, and 9 Observers.* All those that join will
> serve in representative capacity, where applicable, and as such, be
> responsible for consulting with their respective groups on a regular basis:
>
>    - A maximum of two members from each SG/C (14)
>    - One Council member from the Registrar Stakeholder Group (RrSG) (1)
>    - One Council member from the Registry Stakeholder Group (RySG) (1)
>    - One Council member from the Commercial Stakeholder Group (CSG) (1)
>    - One Council member from the Non-Commercial Stakeholder Group (NCSG)
>    (1)
>    - One Council NomCom Appointee (NCA) from each house (2)
>    - One Council NomCom Appointee, non-voting (1)
>    - Two GNSO Board Liaisons
>       - One CPH Board seat #13 (1)
>       - One NCPH Board seat #14 (1)
>
>
>    - Nine Observers:
>       - One Council Chair (1)
>       - One Chair from each SG/C (8)
>
>
>
> Members that are not a part of the Council will not have terms.
> Councilors, Observers, and Liaisons will turn-over naturally as their
> terms, defined in the ICANN Bylaws, conclude and are replaced by new
> representatives. However, SG/Cs who nominate members to participate should
> frequently assess and refresh their designated representatives to ensure
> active participation. Members must be appointed and/or reconfirmed by the
> leadership of the appointing SG/C and notification to the SCCI Chair and
> support staff.
>
>
>
> *How to Join*
>
> GNSO community members who wish to join the Standing Committee should
> contact the GNSO Secretariat at *gnso-secs at icann.org
> <gnso-secs at icann.org>* by *Monday, 6 January 2025.*
>
>
>
> *Background*
>
> For more information and to better prepare for participation on this
> Standing Committee, please read its charter
> <https://gnso.icann.org/sites/default/files/policy/2024/draft/scci-charter-draft-update-13nov24-en.pdf>,
> as well as visiting the CCOICI wiki page
> <https://community.icann.org/display/CCFOICI>.
>
>
>
> Please do not hesitate to get in touch if you have any questions.
>
>
>
> Kind regards,
>
> Julie H., Berry, and Saewon
>
> SCCI Support Staff
>
>
> _______________________________________________
> council mailing list -- council at icann.org
> To unsubscribe send an email to council-leave at icann.org
>
> _______________________________________________
> 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
>


-- 
Best regards

*Taiwo Peter Akinremi*
------ ------ -------  ------ ------ -------  ------ ------ ------- ------
------ -------  ------ ------
*Policy Advisory | Data Governance and Privacy Consultant | Information
Security & Cybersecurity | Certified Salesforce Administrator*
*Phone*; +2348117714345, +2347063830177 *Skype*: akinremi.taiwo
*Email:* compsoftnet at gmail.com, peterexecute at gmail.com
___________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20241126/8dbec889/attachment.htm>

From rafik.dammak at gmail.com  Thu Nov 28 06:49:39 2024
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Thu, 28 Nov 2024 13:49:39 +0900
Subject: [NCSG-PC] Fwd: [SOAC-Leaders-ICANNMeeting-Planning] Action Items
 from ICANN82 Production call #1 and Doodle next call
In-Reply-To: <508DACC7-A620-46B1-94C3-D32D954E37ED@icann.org>
References: <508DACC7-A620-46B1-94C3-D32D954E37ED@icann.org>
Message-ID: <CAH5sThmEWy48k1GhepeJGkd-Lhn7C2JhZnSb5PO4b4ZxPE6LCw@mail.gmail.com>

Hi all,

Those are points from the ICANN planning meeting.
Any comment/feedback would be appreciated.

Best regards,


Rafik

---------- Forwarded message ---------
From: Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning <
soac-leaders-icannmeeting-planning at icann.org>
Date: Tue, Nov 26, 2024, 20:08
Subject: [SOAC-Leaders-ICANNMeeting-Planning] Action Items from ICANN82
Production call #1 and Doodle next call
To: soac-leaders-icannmeeting-planning at icann.org <
soac-leaders-icannmeeting-planning at icann.org>


 Dear all,



Thank you for attending the ICANN82 Production call held today on Monday 25
November 2024. For those of you unable to attend, please find the Zoom
recording.
<https://icann.zoom.us/rec/play/8T35m0TfR__yA7AMW6Gd6MTBWohYihNwuh8Z83xBpX26ti8jCGbAHS6O7ZXZgPjmMVTCXumEWsHn4mRi.JEDmOcygROqh-Pec?autoplay=true&startTime=1732557795000>




?? Please complete the Doodle poll for a next call next week:
https://doodle.com/meeting/participate/id/dGzny05b ??



*ICANN81 Feedback:*

The feedback from ICANN81 was mainly positive. The venue location with
hotels close by, as well as restaurants and caf?s, was appreciated. The
abundance of seating areas allowed for additional conversations. Having
food stalls available at the venue was extremely helpful. However, certain
room sizes and seating were deemed insufficient as several sessions were
held with standing room only given high attendance. The height of speaker
screens in the GAC room will need adjusting to avoid speaker discomfort.
The issue of session conflicts whilst improved upon, needs continued focus.
The suggestion was made to add a Zoom poll at the end of the Community
Session to gather immediate feedback.



Here are the main items raised for consideration for ICANN82:



*Areas needing improvement based on ICANN81 feedback:  *

   1. room size information,
   2. speaker screen height,
   3. session conflicts,
   4. adding a Zoom poll to the end of the Community Session.

These items have been duly noted as action items for staff support.



*ICANN83 Block schedule:*

   - The geopolitical forum is well attended, but lacking in interaction
   opportunities. The suggestion was made to hold the update section of the
   session during Prep Week, and a shorter, interactive section during the
   ICANN meeting. This would also free up a 90-min slot which will assist with
   SO/AC scheduling.
   - Most on the call were in favour of keeping the Community Session, but
   agreed that the topic decision would need to be made closer to the time.
   - The Q&A with the ICANN Executive team is a useful session, especially
   in the light of the new CEO coming onboard in the next few weeks. Sally
   will confirm the format of the community/CEO exchange with Kurtis and will
   come back to the group.
   - The joint ccNSO/ ICANN Board session will ideally take place on
   Tuesday or Wednesday, instead of the current slot on Thursday.



If community leaders would be so kind as to socialize these points with
their members ahead of the call next week, this would be extremely helpful.
An updated Block Schedule will be circulated ahead of the call
incorporating the input received.



Thank you all!



Best,



Nathalie

_______________________________________________
SOAC-Leaders-ICANNMeeting-Planning mailing list --
soac-leaders-icannmeeting-planning at icann.org
To unsubscribe send an email to
soac-leaders-icannmeeting-planning-leave at icann.org

_______________________________________________
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/20241128/8ca5ad0d/attachment.htm>

From farzaneh.badii at gmail.com  Thu Nov 28 07:10:49 2024
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Thu, 28 Nov 2024 00:10:49 -0500
Subject: [NCSG-PC] [NCSG-EC] Fwd: [SOAC-Leaders-ICANNMeeting-Planning]
 Action Items from ICANN82 Production call #1 and Doodle next call
In-Reply-To: <CAH5sThmEWy48k1GhepeJGkd-Lhn7C2JhZnSb5PO4b4ZxPE6LCw@mail.gmail.com>
References: <508DACC7-A620-46B1-94C3-D32D954E37ED@icann.org>
 <CAH5sThmEWy48k1GhepeJGkd-Lhn7C2JhZnSb5PO4b4ZxPE6LCw@mail.gmail.com>
Message-ID: <CAN1qJvD2VgSaX2uAiOB4BUJviMqN1jCCvrFz8_11fPHyjffb5Q@mail.gmail.com>

Thanks Rafik.

It was a very well organized meeting and I appreciated the brewed tea
instead of a terrible tea bag!
I have to first thank Andrea for all the support for the HRIA session. She
went above and beyond to provide us with our last minute requests.

The geopolitical forum is always a monologue. I don't know why. so
I support the suggestion to have a webinar before and just have Q&A but I
also think we don't need Q&A we need issues that need to be addressed and
give the community a chance to express it at the mic.

For the community sessions, I don't know what we want to do with these
cross community sessions but they are so time intensive that you have to
attend all the organizing calls to be able to put the name of a
noncommercial in. Also the topics, they were not very up to date I have to
say. Can we invite some external experts as well to talk about
geopolitics.They need a total revamp otherwise each session every meeting
is going to have the same representative covering the same talking points.

I liked the half an hour/an hour reception after each day in
other meetings, it really allows us to hang out with other members of the
community before we go to our receptions, dinners etc and we can have
informal policy conversations. Is that something that we do only during
Community or policy forum? If too hard to have a reception, maybe we can do
networking breakfasts? They don't have to do the catering, I just think we
can get more chances to talk to other community members.

I didn't know they had switched the public forum to the morning and I
missed it. Well my fault for not checking the agenda carefully but then the
switch didn't make sense, it always made better sense to have it right
before the Board AGM. But I don't know how others felt about it.

This is again my bad, but our session on human rights and dns abuse was
packed. So if we want to do some similar stuff we should specify a larger
capacity.

The transcription of this meeting was a bit off. Maybe I just paid more
attention. Also I don't know if it's my ears or the equipment, but I
sometimes had difficulty hearing people and others told me that audio
quality has been poor in the rooms in recent ICANN meetings (so it's not
venue related).





Farzaneh


On Wed, Nov 27, 2024 at 11:49?PM Rafik Dammak via NCSG-EC <
ncsg-ec at lists.ncsg.is> wrote:

> Hi all,
>
> Those are points from the ICANN planning meeting.
> Any comment/feedback would be appreciated.
>
> Best regards,
>
>
> Rafik
>
> ---------- Forwarded message ---------
> From: Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning <
> soac-leaders-icannmeeting-planning at icann.org>
> Date: Tue, Nov 26, 2024, 20:08
> Subject: [SOAC-Leaders-ICANNMeeting-Planning] Action Items from ICANN82
> Production call #1 and Doodle next call
> To: soac-leaders-icannmeeting-planning at icann.org <
> soac-leaders-icannmeeting-planning at icann.org>
>
>
>  Dear all,
>
>
>
> Thank you for attending the ICANN82 Production call held today on Monday
> 25 November 2024. For those of you unable to attend, please find the Zoom
> recording.
> <https://icann.zoom.us/rec/play/8T35m0TfR__yA7AMW6Gd6MTBWohYihNwuh8Z83xBpX26ti8jCGbAHS6O7ZXZgPjmMVTCXumEWsHn4mRi.JEDmOcygROqh-Pec?autoplay=true&startTime=1732557795000>
>
>
>
>
> ?? Please complete the Doodle poll for a next call next week:
> https://doodle.com/meeting/participate/id/dGzny05b ??
>
>
>
> *ICANN81 Feedback:*
>
> The feedback from ICANN81 was mainly positive. The venue location with
> hotels close by, as well as restaurants and caf?s, was appreciated. The
> abundance of seating areas allowed for additional conversations. Having
> food stalls available at the venue was extremely helpful. However, certain
> room sizes and seating were deemed insufficient as several sessions were
> held with standing room only given high attendance. The height of speaker
> screens in the GAC room will need adjusting to avoid speaker discomfort.
> The issue of session conflicts whilst improved upon, needs continued focus.
> The suggestion was made to add a Zoom poll at the end of the Community
> Session to gather immediate feedback.
>
>
>
> Here are the main items raised for consideration for ICANN82:
>
>
>
> *Areas needing improvement based on ICANN81 feedback:  *
>
>    1. room size information,
>    2. speaker screen height,
>    3. session conflicts,
>    4. adding a Zoom poll to the end of the Community Session.
>
> These items have been duly noted as action items for staff support.
>
>
>
> *ICANN83 Block schedule:*
>
>    - The geopolitical forum is well attended, but lacking in interaction
>    opportunities. The suggestion was made to hold the update section of the
>    session during Prep Week, and a shorter, interactive section during the
>    ICANN meeting. This would also free up a 90-min slot which will assist with
>    SO/AC scheduling.
>    - Most on the call were in favour of keeping the Community Session,
>    but agreed that the topic decision would need to be made closer to the
>    time.
>    - The Q&A with the ICANN Executive team is a useful session,
>    especially in the light of the new CEO coming onboard in the next few
>    weeks. Sally will confirm the format of the community/CEO exchange with
>    Kurtis and will come back to the group.
>    - The joint ccNSO/ ICANN Board session will ideally take place on
>    Tuesday or Wednesday, instead of the current slot on Thursday.
>
>
>
> If community leaders would be so kind as to socialize these points with
> their members ahead of the call next week, this would be extremely helpful.
> An updated Block Schedule will be circulated ahead of the call
> incorporating the input received.
>
>
>
> Thank you all!
>
>
>
> Best,
>
>
>
> Nathalie
>
> _______________________________________________
> SOAC-Leaders-ICANNMeeting-Planning mailing list --
> soac-leaders-icannmeeting-planning at icann.org
> To unsubscribe send an email to
> soac-leaders-icannmeeting-planning-leave at icann.org
>
> _______________________________________________
> 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-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20241128/84bed994/attachment.htm>

From mesumbeslin at gmail.com  Thu Nov 28 13:55:15 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Thu, 28 Nov 2024 22:55:15 +1100
Subject: [NCSG-PC] Fwd: Empowered Community Approval Action on Fundamental
 Bylaws Amendments to Article 4 Accountability and Review,
 4.2 Reconsideration
In-Reply-To: <CAM8DdeXh0R5L4XrXkogL4hAyrNJ+Hw4yamdUcUXCD1YgcxPEkA@mail.gmail.com>
References: <CAM8DdeXh0R5L4XrXkogL4hAyrNJ+Hw4yamdUcUXCD1YgcxPEkA@mail.gmail.com>
Message-ID: <CAM8DdeVv_XKpOGuTk5g1hSvaCt-j4TikwePMEYZgn+AjnAji6g@mail.gmail.com>

Hi all,

Please read the below regarding the Empowered Community Approval Action on
Fundamental Bylaws Amendments to Article 4 Accountability and Review, 4.2
Reconsideration. Let us know if you have any objections or concerns to this
amendment.

Warmly,
Tomslin



---------- Forwarded message ---------
From: Tomslin Samme-Nlar <mesumbeslin at gmail.com>
Date: Tue, 26 Nov 2024 at 15:43
Subject: Empowered Community Approval Action on Fundamental Bylaws
Amendments to Article 4 Accountability and Review, 4.2 Reconsideration
To: GNSO Council List <council at gnso.icann.org>
Cc: Julie Bisland via Gnso-secs <gnso-secs at icann.org>


Dear Councilors,

As you may know, at ICANN81 ICANN Org held an Empowered Community Approval
Action Community Forum
<https://www.icann.org/en/ec/fundamental-bylaws-amendment-to-accountability-mechanisms>
on Fundamental Bylaws Amendments to Article 4 Accountability and Review,
4.2 Reconsideration.
<https://itp.cdn.icann.org/en/files/governance/uppdates-to-article-4-icann-grant-program-07-08-2024-en.pdf>

The Fundamental Bylaws Amendments will only become effective if approved by
the Empowered Community using the process set forth at Section 25.2(f)
<https://www.icann.org/resources/pages/governance/bylaws-en/#article25>
and Annex
D <https://www.icann.org/resources/pages/governance/bylaws-en/#annexD>,
Article 1 of the ICANN Bylaws. The convening of the Approval Action
Community Forum is part of this process.

Following the Approval Action Community Forum, the GNSO Stakeholder Groups
and Constituencies will be asked to provide feedback, opinions or comments
on their support for, objection to, or abstention from the Approval Action
under consideration. The GNSO Council must decide and inform the EC
Administration of its decision within twenty-one (21) days after the
expiration of the Community Forum whether to support, object to, or abstain
from the Approval Action by affirmative vote of a GNSO Supermajority.

A discussion and vote on the Approval Action  is scheduled for the next
GNSO Council meeting on 19 December. If more time is needed a placeholder
for an email vote will be scheduled for Monday, 23 December.  In any case,
we will need to hold the vote in December because the Empowered Community
decision is due before the January GNSO Council meeting.

Please provide feedback, if any, to the GNSO Council list on your group?s
opinions or comments on your support for, objection to, or abstention from
the Approval Action under consideration at your earliest convenience, but
not later than Wednesday, 18 December.

We appreciate your prompt attention to this matter.

Kind regards,


Tomslin Samme-Nlar, GNSO Vice-Chair & GNSO Empowered Community
Administration Representative

on behalf of the GNSO Council Leadership Team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20241128/e153ff07/attachment.htm>

From mesumbeslin at gmail.com  Thu Nov 28 14:07:40 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Thu, 28 Nov 2024 23:07:40 +1100
Subject: [NCSG-PC] Fwd: [council] EPDP Phase 1 RegData Implementation -
 Billing Contact Issue Summary
In-Reply-To: <B5CDB18C-C185-4060-993B-926D36FEF3E2@icann.org>
References: <B5CDB18C-C185-4060-993B-926D36FEF3E2@icann.org>
Message-ID: <CAM8DdeVdBq-k1_fbigWU1TpK12PKBWSX_7QPL-knhf+CcuwU=Q@mail.gmail.com>

Hi all

Here is another summary I would like you to read and provide feedback on.
The details are well summarised in the below message but it is regarding
how the EPDP Phase 1 IRT believes  the billing contact data should be
treated in the Registration Data Policy.

Specifically, we as NCSG have to answer the following question: *does your
group believe that (1) billing contact data was in scope for the EPDP Temp
Spec policy development? If yes, does your group agree that because billing
contact data was within the EPDP Team?s scope, (2) there was a drafting
error in the EPDP Phase 1 Final Report because the intention of the
recommendations, by not including a recommendation concerning the
collection, escrow, etc of billing contact data was that the collection and
retention of billing contact data should be optional and not mandatory?*

Our NCUC members to the IRT are  Stephanie Perrin, Afi Edoh and Wisdom
Donkor who might perhaps be able to help provide more details if anyone has
questions.

Warmly,
Tomslin



---------- Forwarded message ---------
From: Caitlin Tubergen via council <council at icann.org>
Date: Thu, 28 Nov 2024 at 09:42
Subject: [council] EPDP Phase 1 RegData Implementation - Billing Contact
Issue Summary
To: council at gnso.icann.org <council at gnso.icann.org>


Dear Councilors,



During the ICANN81 GNSO Council Wrap-Up
<https://icann81.sched.com/event/1p2Gu/gnso-council-wrap-up>, Thomas
Rickert provided an update regarding the implementation of EPDP Temp Spec
Phase 1 recommendations. Thomas is the current GNSO Council Liaison to the
EPDP Temp Spec Phase 1 Implementation Review Team (IRT).



For background, the Registration Data Policy
<https://www.icann.org/resources/pages/registration-data-policy-2024-02-21-en>
was published on 21 February 2024, and the policy has an effective date of
21 August 2025.



The EPDP Phase 1 policy recommendations
<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-gtld-registration-data-specs-final-2-20feb19-en.pdf>
do not reference billing contact data, and the Registration Data Policy
<https://www.icann.org/resources/pages/registration-data-policy-2024-02-21-en>
also makes no reference to billing contact data.



Billing contact data, however, is referenced in the Registrar Accreditation
Agreement
<https://www.icann.org/en/system/files/files/registrar-accreditation-agreement-21jan24-en.html>
(RAA) in ? 3.4.1.3 and in the Data Retention Specification
<https://www.icann.org/en/system/files/files/registrar-accreditation-agreement-21jan24-en.html#data-retention>
in ?1.1.2 ? ?1.1.5. The billing contact data is also referenced in the
existing Registrar Data Escrow Specifications
<https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf>.
ICANN?s publication of updated Registrar Data Escrow Specifications
<https://www.icann.org/en/system/files/files/rde-specs-14aug24-en.pdf> in
August triggered a discussion within the EPDP Phase 1 IRT regarding the
Registration Data Policy?s intended impact on the RAA requirements
concerning the billing contact data fields.



Generally speaking, unless in conflict with or otherwise modified by a
policy recommendation, current contractual requirements and consensus
policy requirements remain in place following the publication of a new
policy. For that reason, ICANN org informed the IRT on 8 August 2024 that
billing contact data must still be collected and retained pursuant to
current RAA requirements.



In response, some registrar members of the IRT expressed the view that the
absence of a reference to billing contact data was a drafting error, and
the EPDP Team intended for the collection of billing contact data to be
optional and not mandatory. The registrar IRT members noted the reference
to ?billing contact? within charter question b1, which provides, ?b1) What
data should registrars be required to collect for each of the following
contacts: Registrant, Tech, Admin, Billing?? Because billing contact is
referenced in this charter question but the EPDP Team did not provide a
recommendation regarding mandatory (or optional) collection of the billing
contact, the registrar position is that the billing contact is no longer
required to be collected.



On 25 September 2024, there was a special meeting of the IRT
<https://community.icann.org/display/RDPIRT/2024-09-25+Registration+Data+Policy+Implementation+IRT+Meeting>
to discuss the topic of billing contact. While no objection to the
registrar view was raised during the special meeting, it is unclear at this
stage whether this is a broadly supported view of the IRT, as the majority
of stakeholder groups did not have IRT members present at the special
meeting. Specifically, members from the BC, GAC, IPC, ISPCP, IPC, NCSG, and
SSAC were not in attendance
<https://community.icann.org/display/RDPIRT/2024-09-25+Registration+Data+Policy+Implementation+IRT+Meeting?preview=/375914530/379191359/Attendance%20Reg%20Data%20Pol%20IRT%2025%20Sep%2024.pdf>
.



It is worth noting that billing contact information is not referenced in
the Temporary Specification, nor is it part of the RDDS specification in
the RAA, so it could be argued that billing contact data was not in scope
for EPDP Temp Spec Phase 1 policy development. It could also be argued that
the drafting error was in the EPDP charter, as billing contact should not
have been referenced since it is not part of the Temporary Specification.
It is also worth noting that there are other elements within the RAA and
Data Retention Specification that were not part of the Temporary
Specification and are still required.



Thomas provided a high-level overview during the wrap-up session, and noted
that some IRT members believe this drafting error is noncontroversial.
However, Thomas noted that in the interest of transparency, all Councilors
should consult with their respective groups to ensure that others are
properly informed and agree with the interpretation raised by the
registrars within the IRT. Thomas has also requested that further
discussion of billing contact data within the Registration Data Policy be
added as a discussion item to the GNSO Council?s December meeting.



Accordingly, please check in with your groups regarding the treatment of
billing contact data in the Registration Data Policy
<https://www.icann.org/resources/pages/registration-data-policy-2024-02-21-en>.
*Specifically, does your group believe that (1) billing contact data was in
scope for the EPDP Temp Spec policy development? If yes, does your group
agree that because billing contact data was within the EPDP Team?s scope,
(2) there was a drafting error in the EPDP Phase 1 Final Report because the
intention of the recommendations, by not including a recommendation
concerning the collection, escrow, etc of billing contact data was that the
collection and retention of billing contact data should be optional and not
mandatory? Note: If, as a matter of ICANN Consensus Policy this was the
intended outcome, this interpretation would change current contractual
requirements for registrars. *



We invite Thomas and other councilors to provide additional context. Please
feel free to provide thoughts via the list in advance of the December
meeting, and please be prepared to discuss next steps during the 19
December Council meeting.



Kind regards, and Happy Thanksgiving to those who celebrate,

Caitlin




_______________________________________________
council mailing list -- council at icann.org
To unsubscribe send an email to council-leave at icann.org

_______________________________________________
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/20241128/72d67d27/attachment.htm>

From julf at Julf.com  Thu Nov 28 14:41:50 2024
From: julf at Julf.com (Johan Helsingius)
Date: Thu, 28 Nov 2024 13:41:50 +0100
Subject: [NCSG-PC] A week off signal...
Message-ID: <0d8fb826-0e42-4e30-8cf5-4df4763dba63@Julf.com>

Oh great. Somehow "registration lock" got enabled on my Signal account, 
so switching to a new phone caused me to be locked out for 7 days - even 
on the old phone. Thus you won't be able to reach me on Signal until end
of next week :(

	Julf


From mesumbeslin at gmail.com  Sat Nov 30 00:15:37 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Sat, 30 Nov 2024 09:15:37 +1100
Subject: [NCSG-PC] Fwd: Please Respond by 18 December | Annual SSC
 Refresh
In-Reply-To: <CAM8DdeXR6zaF9iiW6HMTD0by9unUn5+ZkLT38i0bduap7roW5A@mail.gmail.com>
References: <F7B86CAF-A4AB-4687-BC63-A667E299877B@icann.org>
 <CAH5sTh=N66NsY-_qk4bwPzsazv=vZDdTRA1X38GQ4Gy02n4DYQ@mail.gmail.com>
 <CAM8DdeXR6zaF9iiW6HMTD0by9unUn5+ZkLT38i0bduap7roW5A@mail.gmail.com>
Message-ID: <CAM8DdeUizwa3eRb-WNzA+29coogmcy20PWry-xU4Z9JQCrK5qA@mail.gmail.com>

Hi team,

I sent an email out to the members who are still elegible (Bruna and Remy)
to confirm if they would like to continue. Only Bruna has responded, so
with your permission, I would like to immediately request for volunteers
for 2 SSC reps positions.

Let me know if any concerns please.

Tomslin


On Fri, 22 Nov 2024 at 07:18, Tomslin Samme-Nlar <mesumbeslin at gmail.com>
wrote:

> Thanks, Rafik. Working on it.
>
> Warmly,
> Tomslin
> @LinkedIn: https://www.linkedin.com/in/tomslin/
>
>
> On Thu, 21 Nov 2024 at 16:23, Rafik Dammak <rafik.dammak at gmail.com> wrote:
>
>> Hi all,
>>
>> The cycle to confirm/appoint NCSG representatives to SSC just started
>> and we have to send the names by 18th December giving us roughly one month.
>>
>> @Tomslin Samme-Nlar <mesumbeslin at gmail.com> can the PC confirm with
>> current representatives  and issue call for candidates adaptation.
>> This is a critical selection as I understand the concerns about some of
>> selections made by SSC.
>>
>> Best,
>>
>> Rafik
>>
>>
>>
>>
>> ---------- Forwarded message ---------
>> From: Julie Bisland <julie.bisland at icann.org>
>> Date: Thu, Nov 21, 2024, 01:14
>> Subject: Please Respond by 18 December | Annual SSC Refresh
>> To: Mason Cole (Preferred email) <MCole at perkinscoie.com>, John McElwaine
>> <john.mcelwaine at nelsonmullins.com>, Philippe Fouquart <
>> philippe.fouquart at orange.com>, Wisdom Donkor <wisdom.dk at gmail.com>, Juan
>> Manuel Rojas <jumaropi at yahoo.com>, Owen Smigelski <
>> owen.smigelski at namecheap.com>, Elizabeth Bacon <beth at pir.org>, Rafik
>> Dammak <rafik.dammak at gmail.com>
>> Cc: Sue Schuler <secretariat at rysg.info>, GNSO-Secs <gnso-secs at icann.org>,
>> Zoe Bonython <secretariat at icannregistrars.org>, Andrea Glandon <
>> andrea.glandon at icann.org>, gnso-chairs at icann.org <gnso-chairs at icann.org>
>>
>>
>> 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 assignments it
>> received from the GNSO Council:
>>
>>
>> GNSO Appointed Mentor - ICANN Fellowship Program - 2024
>> <https://community.icann.org/display/GSSC/GNSO+Appointed+Mentor+-+ICANN+Fellowship+Program+-+2024>
>>
>> GAC Liaison - 2024
>> <https://community.icann.org/display/GSSC/GAC+Liaison+-+2024>
>>
>> Pilot Holistic Review - 2024
>> <https://community.icann.org/display/GSSC/Pilot+Holistic+Review+-+2024>
>>
>>
>>
>> The next anticipated SSC assignment is again the annual selection the ICANN
>> Fellowship Program mentor, to be selected by the end of January. 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, members may serve a maximum of two
>> consecutive terms. *We are reaching out to you to re-confirm members
>> that are eligible to continue serving on the SSC and/or identify
>> replacements for those members who are not eligible, as noted in the status
>> column in the table below:*
>>
>>
>>
>>
>>
>> *Name*
>>
>> *Appointed by*
>>
>> *SOI*
>>
>> *Member/Alternate Since:*
>>
>> *Status*
>>
>> Karen Day (Chair)
>>
>> RySG
>>
>> Karen Day SOI <https://community.icann.org/x/vQWAAw>
>>
>> January 2024
>>
>> Eligible for another term
>>
>> Jothan Frakes
>>
>> RrSG
>>
>> Jothan Frakes SOI <https://community.icann.org/x/Gb-hAg>
>>
>> January 2024
>>
>> Eligible for another term
>>
>> Segunfunmi Olajide (Vice-Chair)
>>
>> BC
>>
>> Segunfunmi Olajide SOI <https://community.icann.org/x/7YoFDQ>
>>
>> January 2024
>>
>> Eligible for another term
>>
>> Marie Pattullo
>>
>> BC Alternate
>>
>> Marie Pattullo SOI <https://community.icann.org/x/OTWAAw>
>>
>> January 2024
>>
>> Eligible for another term
>>
>> Christian Dawson
>>
>> ISPCP
>>
>> Christian Dawson SOI <https://community.icann.org/x/NivRAg>
>>
>> October 2022
>>
>> *Not eligible for another term*
>>
>> Mike Rodenbaugh
>>
>> IPC
>>
>> Mike Rodenbaugh SOI <https://community.icann.org/x/Ah9-Ag>
>>
>> February 2024
>>
>> Eligible for another term
>>
>> Remmy Nweke
>>
>> NCSG
>>
>> Remmy Nweke SOI <https://community.icann.org/x/3MXRAw>
>>
>> February 2024
>>
>> Eligible for another term
>>
>> Arsene Tungali
>>
>> NCSG
>>
>> Arsene Tungali SOI <https://community.icann.org/x/vmjwAw>
>>
>> December 2022
>>
>> *Not eligible for another term*
>>
>> Bruna Martins dos Santos
>>
>> NCSG
>>
>> Bruna Martins dos Santos SOI <https://community.icann.org/x/iBvwAw>
>>
>> February 2024
>>
>> Eligible for another term
>>
>> Desiree Miloshevic Evans
>>
>> NomCom
>>
>> Desiree Miloshevic Evans SOI <https://community.icann.org/x/zAJyCg>
>>
>> February 2024
>>
>> Eligible for another term
>>
>> Tomslin Samme-Nlar
>>
>> Ex-Officio Member Representing GNSO Council Leadership
>>
>> Tomslin Samme-Nlar SOI <https://community.icann.org/x/8ZxEB>
>>
>> Ex-Officio Member Representing GNSO Council Leadership Since January 2024
>>
>> GNSO Council leadership appointment
>>
>>
>>
>> For information about the SSC, please see the wiki page
>> <https://community.icann.org/display/GSSC/GNSO+Standing+Selection+Committee+Home>
>> .
>>
>>
>>
>> *Please send confirmations and/or new appointments as soon as possible,
>> but no later than Wednesday, 18 December 2024, if possible.*
>>
>>
>>
>> Do not hesitate to get in touch if you have any questions.
>>
>>
>>
>> Kind regards,
>>
>> Saewon and Julie
>>
>> SSC Support Staff
>> _______________________________________________
>> 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/20241130/c85933b8/attachment.htm>

From mesumbeslin at gmail.com  Sat Nov 30 00:24:55 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Sat, 30 Nov 2024 09:24:55 +1100
Subject: [NCSG-PC] Fwd: Please Respond by 18 December | Annual SSC
 Refresh
In-Reply-To: <CAM8DdeUizwa3eRb-WNzA+29coogmcy20PWry-xU4Z9JQCrK5qA@mail.gmail.com>
References: <F7B86CAF-A4AB-4687-BC63-A667E299877B@icann.org>
 <CAH5sTh=N66NsY-_qk4bwPzsazv=vZDdTRA1X38GQ4Gy02n4DYQ@mail.gmail.com>
 <CAM8DdeXR6zaF9iiW6HMTD0by9unUn5+ZkLT38i0bduap7roW5A@mail.gmail.com>
 <CAM8DdeUizwa3eRb-WNzA+29coogmcy20PWry-xU4Z9JQCrK5qA@mail.gmail.com>
Message-ID: <CAM8DdeXzVVtdm=zQpBW534YaM9xK4wP6=RCM8ZmeR7vkKmCU+g@mail.gmail.com>

To clarify,

Bruna has confirmed she would love to continue. Remy hasn't.

Warmly,
Tomslin

On Sat, 30 Nov 2024, 09:15 Tomslin Samme-Nlar, <mesumbeslin at gmail.com>
wrote:

> Hi team,
>
> I sent an email out to the members who are still elegible (Bruna and Remy)
> to confirm if they would like to continue. Only Bruna has responded, so
> with your permission, I would like to immediately request for volunteers
> for 2 SSC reps positions.
>
> Let me know if any concerns please.
>
> Tomslin
>
>
> On Fri, 22 Nov 2024 at 07:18, Tomslin Samme-Nlar <mesumbeslin at gmail.com>
> wrote:
>
>> Thanks, Rafik. Working on it.
>>
>> Warmly,
>> Tomslin
>> @LinkedIn: https://www.linkedin.com/in/tomslin/
>>
>>
>> On Thu, 21 Nov 2024 at 16:23, Rafik Dammak <rafik.dammak at gmail.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> The cycle to confirm/appoint NCSG representatives to SSC just started
>>> and we have to send the names by 18th December giving us roughly one month.
>>>
>>> @Tomslin Samme-Nlar <mesumbeslin at gmail.com> can the PC confirm with
>>> current representatives  and issue call for candidates adaptation.
>>> This is a critical selection as I understand the concerns about some of
>>> selections made by SSC.
>>>
>>> Best,
>>>
>>> Rafik
>>>
>>>
>>>
>>>
>>> ---------- Forwarded message ---------
>>> From: Julie Bisland <julie.bisland at icann.org>
>>> Date: Thu, Nov 21, 2024, 01:14
>>> Subject: Please Respond by 18 December | Annual SSC Refresh
>>> To: Mason Cole (Preferred email) <MCole at perkinscoie.com>, John
>>> McElwaine <john.mcelwaine at nelsonmullins.com>, Philippe Fouquart <
>>> philippe.fouquart at orange.com>, Wisdom Donkor <wisdom.dk at gmail.com>,
>>> Juan Manuel Rojas <jumaropi at yahoo.com>, Owen Smigelski <
>>> owen.smigelski at namecheap.com>, Elizabeth Bacon <beth at pir.org>, Rafik
>>> Dammak <rafik.dammak at gmail.com>
>>> Cc: Sue Schuler <secretariat at rysg.info>, GNSO-Secs <gnso-secs at icann.org>,
>>> Zoe Bonython <secretariat at icannregistrars.org>, Andrea Glandon <
>>> andrea.glandon at icann.org>, gnso-chairs at icann.org <gnso-chairs at icann.org>
>>>
>>>
>>> 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 assignments it
>>> received from the GNSO Council:
>>>
>>>
>>> GNSO Appointed Mentor - ICANN Fellowship Program - 2024
>>> <https://community.icann.org/display/GSSC/GNSO+Appointed+Mentor+-+ICANN+Fellowship+Program+-+2024>
>>>
>>> GAC Liaison - 2024
>>> <https://community.icann.org/display/GSSC/GAC+Liaison+-+2024>
>>>
>>> Pilot Holistic Review - 2024
>>> <https://community.icann.org/display/GSSC/Pilot+Holistic+Review+-+2024>
>>>
>>>
>>>
>>> The next anticipated SSC assignment is again the annual selection the ICANN
>>> Fellowship Program mentor, to be selected by the end of January. 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, members may serve a maximum of two
>>> consecutive terms. *We are reaching out to you to re-confirm members
>>> that are eligible to continue serving on the SSC and/or identify
>>> replacements for those members who are not eligible, as noted in the status
>>> column in the table below:*
>>>
>>>
>>>
>>>
>>>
>>> *Name*
>>>
>>> *Appointed by*
>>>
>>> *SOI*
>>>
>>> *Member/Alternate Since:*
>>>
>>> *Status*
>>>
>>> Karen Day (Chair)
>>>
>>> RySG
>>>
>>> Karen Day SOI <https://community.icann.org/x/vQWAAw>
>>>
>>> January 2024
>>>
>>> Eligible for another term
>>>
>>> Jothan Frakes
>>>
>>> RrSG
>>>
>>> Jothan Frakes SOI <https://community.icann.org/x/Gb-hAg>
>>>
>>> January 2024
>>>
>>> Eligible for another term
>>>
>>> Segunfunmi Olajide (Vice-Chair)
>>>
>>> BC
>>>
>>> Segunfunmi Olajide SOI <https://community.icann.org/x/7YoFDQ>
>>>
>>> January 2024
>>>
>>> Eligible for another term
>>>
>>> Marie Pattullo
>>>
>>> BC Alternate
>>>
>>> Marie Pattullo SOI <https://community.icann.org/x/OTWAAw>
>>>
>>> January 2024
>>>
>>> Eligible for another term
>>>
>>> Christian Dawson
>>>
>>> ISPCP
>>>
>>> Christian Dawson SOI <https://community.icann.org/x/NivRAg>
>>>
>>> October 2022
>>>
>>> *Not eligible for another term*
>>>
>>> Mike Rodenbaugh
>>>
>>> IPC
>>>
>>> Mike Rodenbaugh SOI <https://community.icann.org/x/Ah9-Ag>
>>>
>>> February 2024
>>>
>>> Eligible for another term
>>>
>>> Remmy Nweke
>>>
>>> NCSG
>>>
>>> Remmy Nweke SOI <https://community.icann.org/x/3MXRAw>
>>>
>>> February 2024
>>>
>>> Eligible for another term
>>>
>>> Arsene Tungali
>>>
>>> NCSG
>>>
>>> Arsene Tungali SOI <https://community.icann.org/x/vmjwAw>
>>>
>>> December 2022
>>>
>>> *Not eligible for another term*
>>>
>>> Bruna Martins dos Santos
>>>
>>> NCSG
>>>
>>> Bruna Martins dos Santos SOI <https://community.icann.org/x/iBvwAw>
>>>
>>> February 2024
>>>
>>> Eligible for another term
>>>
>>> Desiree Miloshevic Evans
>>>
>>> NomCom
>>>
>>> Desiree Miloshevic Evans SOI <https://community.icann.org/x/zAJyCg>
>>>
>>> February 2024
>>>
>>> Eligible for another term
>>>
>>> Tomslin Samme-Nlar
>>>
>>> Ex-Officio Member Representing GNSO Council Leadership
>>>
>>> Tomslin Samme-Nlar SOI <https://community.icann.org/x/8ZxEB>
>>>
>>> Ex-Officio Member Representing GNSO Council Leadership Since January 2024
>>>
>>> GNSO Council leadership appointment
>>>
>>>
>>>
>>> For information about the SSC, please see the wiki page
>>> <https://community.icann.org/display/GSSC/GNSO+Standing+Selection+Committee+Home>
>>> .
>>>
>>>
>>>
>>> *Please send confirmations and/or new appointments as soon as possible,
>>> but no later than Wednesday, 18 December 2024, if possible.*
>>>
>>>
>>>
>>> Do not hesitate to get in touch if you have any questions.
>>>
>>>
>>>
>>> Kind regards,
>>>
>>> Saewon and Julie
>>>
>>> SSC Support Staff
>>> _______________________________________________
>>> 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/20241130/7ff3fab4/attachment.htm>

From rafik.dammak at gmail.com  Sat Nov 30 01:26:45 2024
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Sat, 30 Nov 2024 08:26:45 +0900
Subject: [NCSG-PC] Fwd: Please Respond by 18 December | Annual SSC
 Refresh
In-Reply-To: <CAM8DdeUizwa3eRb-WNzA+29coogmcy20PWry-xU4Z9JQCrK5qA@mail.gmail.com>
References: <F7B86CAF-A4AB-4687-BC63-A667E299877B@icann.org>
 <CAH5sTh=N66NsY-_qk4bwPzsazv=vZDdTRA1X38GQ4Gy02n4DYQ@mail.gmail.com>
 <CAM8DdeXR6zaF9iiW6HMTD0by9unUn5+ZkLT38i0bduap7roW5A@mail.gmail.com>
 <CAM8DdeUizwa3eRb-WNzA+29coogmcy20PWry-xU4Z9JQCrK5qA@mail.gmail.com>
Message-ID: <CAH5sTh=qZu6Zsi5pb84Z0sgtFHQYTbWaV52=gXJZt_tEj92s5A@mail.gmail.com>

Hi Tomslin,

Yes let's start the process.

Best,

Rafik

On Sat, Nov 30, 2024, 07:15 Tomslin Samme-Nlar <mesumbeslin at gmail.com>
wrote:

> Hi team,
>
> I sent an email out to the members who are still elegible (Bruna and Remy)
> to confirm if they would like to continue. Only Bruna has responded, so
> with your permission, I would like to immediately request for volunteers
> for 2 SSC reps positions.
>
> Let me know if any concerns please.
>
> Tomslin
>
>
> On Fri, 22 Nov 2024 at 07:18, Tomslin Samme-Nlar <mesumbeslin at gmail.com>
> wrote:
>
>> Thanks, Rafik. Working on it.
>>
>> Warmly,
>> Tomslin
>> @LinkedIn: https://www.linkedin.com/in/tomslin/
>>
>>
>> On Thu, 21 Nov 2024 at 16:23, Rafik Dammak <rafik.dammak at gmail.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> The cycle to confirm/appoint NCSG representatives to SSC just started
>>> and we have to send the names by 18th December giving us roughly one month.
>>>
>>> @Tomslin Samme-Nlar <mesumbeslin at gmail.com> can the PC confirm with
>>> current representatives  and issue call for candidates adaptation.
>>> This is a critical selection as I understand the concerns about some of
>>> selections made by SSC.
>>>
>>> Best,
>>>
>>> Rafik
>>>
>>>
>>>
>>>
>>> ---------- Forwarded message ---------
>>> From: Julie Bisland <julie.bisland at icann.org>
>>> Date: Thu, Nov 21, 2024, 01:14
>>> Subject: Please Respond by 18 December | Annual SSC Refresh
>>> To: Mason Cole (Preferred email) <MCole at perkinscoie.com>, John
>>> McElwaine <john.mcelwaine at nelsonmullins.com>, Philippe Fouquart <
>>> philippe.fouquart at orange.com>, Wisdom Donkor <wisdom.dk at gmail.com>,
>>> Juan Manuel Rojas <jumaropi at yahoo.com>, Owen Smigelski <
>>> owen.smigelski at namecheap.com>, Elizabeth Bacon <beth at pir.org>, Rafik
>>> Dammak <rafik.dammak at gmail.com>
>>> Cc: Sue Schuler <secretariat at rysg.info>, GNSO-Secs <gnso-secs at icann.org>,
>>> Zoe Bonython <secretariat at icannregistrars.org>, Andrea Glandon <
>>> andrea.glandon at icann.org>, gnso-chairs at icann.org <gnso-chairs at icann.org>
>>>
>>>
>>> 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 assignments it
>>> received from the GNSO Council:
>>>
>>>
>>> GNSO Appointed Mentor - ICANN Fellowship Program - 2024
>>> <https://community.icann.org/display/GSSC/GNSO+Appointed+Mentor+-+ICANN+Fellowship+Program+-+2024>
>>>
>>> GAC Liaison - 2024
>>> <https://community.icann.org/display/GSSC/GAC+Liaison+-+2024>
>>>
>>> Pilot Holistic Review - 2024
>>> <https://community.icann.org/display/GSSC/Pilot+Holistic+Review+-+2024>
>>>
>>>
>>>
>>> The next anticipated SSC assignment is again the annual selection the ICANN
>>> Fellowship Program mentor, to be selected by the end of January. 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, members may serve a maximum of two
>>> consecutive terms. *We are reaching out to you to re-confirm members
>>> that are eligible to continue serving on the SSC and/or identify
>>> replacements for those members who are not eligible, as noted in the status
>>> column in the table below:*
>>>
>>>
>>>
>>>
>>>
>>> *Name*
>>>
>>> *Appointed by*
>>>
>>> *SOI*
>>>
>>> *Member/Alternate Since:*
>>>
>>> *Status*
>>>
>>> Karen Day (Chair)
>>>
>>> RySG
>>>
>>> Karen Day SOI <https://community.icann.org/x/vQWAAw>
>>>
>>> January 2024
>>>
>>> Eligible for another term
>>>
>>> Jothan Frakes
>>>
>>> RrSG
>>>
>>> Jothan Frakes SOI <https://community.icann.org/x/Gb-hAg>
>>>
>>> January 2024
>>>
>>> Eligible for another term
>>>
>>> Segunfunmi Olajide (Vice-Chair)
>>>
>>> BC
>>>
>>> Segunfunmi Olajide SOI <https://community.icann.org/x/7YoFDQ>
>>>
>>> January 2024
>>>
>>> Eligible for another term
>>>
>>> Marie Pattullo
>>>
>>> BC Alternate
>>>
>>> Marie Pattullo SOI <https://community.icann.org/x/OTWAAw>
>>>
>>> January 2024
>>>
>>> Eligible for another term
>>>
>>> Christian Dawson
>>>
>>> ISPCP
>>>
>>> Christian Dawson SOI <https://community.icann.org/x/NivRAg>
>>>
>>> October 2022
>>>
>>> *Not eligible for another term*
>>>
>>> Mike Rodenbaugh
>>>
>>> IPC
>>>
>>> Mike Rodenbaugh SOI <https://community.icann.org/x/Ah9-Ag>
>>>
>>> February 2024
>>>
>>> Eligible for another term
>>>
>>> Remmy Nweke
>>>
>>> NCSG
>>>
>>> Remmy Nweke SOI <https://community.icann.org/x/3MXRAw>
>>>
>>> February 2024
>>>
>>> Eligible for another term
>>>
>>> Arsene Tungali
>>>
>>> NCSG
>>>
>>> Arsene Tungali SOI <https://community.icann.org/x/vmjwAw>
>>>
>>> December 2022
>>>
>>> *Not eligible for another term*
>>>
>>> Bruna Martins dos Santos
>>>
>>> NCSG
>>>
>>> Bruna Martins dos Santos SOI <https://community.icann.org/x/iBvwAw>
>>>
>>> February 2024
>>>
>>> Eligible for another term
>>>
>>> Desiree Miloshevic Evans
>>>
>>> NomCom
>>>
>>> Desiree Miloshevic Evans SOI <https://community.icann.org/x/zAJyCg>
>>>
>>> February 2024
>>>
>>> Eligible for another term
>>>
>>> Tomslin Samme-Nlar
>>>
>>> Ex-Officio Member Representing GNSO Council Leadership
>>>
>>> Tomslin Samme-Nlar SOI <https://community.icann.org/x/8ZxEB>
>>>
>>> Ex-Officio Member Representing GNSO Council Leadership Since January 2024
>>>
>>> GNSO Council leadership appointment
>>>
>>>
>>>
>>> For information about the SSC, please see the wiki page
>>> <https://community.icann.org/display/GSSC/GNSO+Standing+Selection+Committee+Home>
>>> .
>>>
>>>
>>>
>>> *Please send confirmations and/or new appointments as soon as possible,
>>> but no later than Wednesday, 18 December 2024, if possible.*
>>>
>>>
>>>
>>> Do not hesitate to get in touch if you have any questions.
>>>
>>>
>>>
>>> Kind regards,
>>>
>>> Saewon and Julie
>>>
>>> SSC Support Staff
>>> _______________________________________________
>>> 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/20241130/47c15ad0/attachment.htm>

From rafik.dammak at gmail.com  Sat Nov 30 15:09:04 2024
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Sat, 30 Nov 2024 22:09:04 +0900
Subject: [NCSG-PC] Fwd: [council] Call for Volunteers for SCCI | Please
 Respond by 6 January
In-Reply-To: <CAM8DdeV4EFNFj3ADbcKkwxDzr2djA-M3o5ngi0BATgYA-1zmEQ@mail.gmail.com>
References: <698C84A1-F28A-4430-A052-E39612BAD9F5@icann.org>
 <CAM8DdeV4EFNFj3ADbcKkwxDzr2djA-M3o5ngi0BATgYA-1zmEQ@mail.gmail.com>
Message-ID: <CAH5sThmMjU0fqwR2DG_RtgU+abvLMxAO4gDwNKvK50R6wEK5yQ@mail.gmail.com>

Hi Tomslin,

It seems that we vmcab have 1 councilor from NCSG and 2 additional
representatives from NCSG ( not sure how they end up with 14 reps from
SG/C).
So I assume there will be a call for candidates to appoint 2
representatives.

Best,

Rafik

On Wed, Nov 27, 2024, 04:14 Tomslin Samme-Nlar <mesumbeslin at gmail.com>
wrote:

> Hi Councillors,
>
> Who would like to volunteer as our rep to the newly formed SCCI?
>
> Warmly,
> Tomslin
>
>
>
> ---------- Forwarded message ---------
> From: Devan Reed via council <council at icann.org>
> Date: Wed, 27 Nov 2024 at 01:05
> Subject: [council] Call for Volunteers for SCCI | Please Respond by 6
> January
> To: council at gnso.icann.org <council at gnso.icann.org>
> Cc: GNSO-Secs <gnso-secs at icann.org>
>
>
> *Dear Councilors,*
>
>
>
> The Generic Names Supporting Organization (GNSO) Council seeks volunteers
> to serve on the Standing Committee on Continuous Improvement (SCCI). The
> SCCI will be in charge of continuous improvement related projects that are
> focused on the GNSO?s structural, procedural, and process improvements to
> the Policy Development Process (PDP). This work originally commenced
> through a pilot under the Council Committee for Overseeing and
> Implementing Continuous Improvement (CCOICI) Framework
> <https://gnso.icann.org/sites/default/files/file/field-file-attach/continuous-improvement-oversight-implementation-framework-29jun21-en.pdf>
>  (last updated 29 June 2021), which has now converted to a permanent
> standing committee following the GNSO Council?s adoption of the charter
> <https://gnso.icann.org/en/council/resolutions/2020-current#202411>.
>
>
>
> *What This Standing Committee Will Do*
>
> The SCCI and its dedicated Task Forces (TFs), populated by the Councilors
> and representatives of each Stakeholder Group (SG) and Constituency (C)
> (hereafter ?SG/C?), will execute a continuous improvement program that aims
> to improve the GNSO?s process and procedures over time through gradual
> changes. The goal is to achieve measurable improvements in the efficiency,
> effectiveness, performance, outcomes, accountability, transparency, and
> other indicators of quality for the GNSO. Notably, this work affects the
> GNSO community more broadly and is not limited to that of the Council.
>
>
>
> Considering that this is a permanent standing committee, the specific
> scope of work across the varying projects that the SCCI and TFs will
> execute is not overly prescribed within the charter
> <https://gnso.icann.org/sites/default/files/policy/2024/draft/scci-charter-draft-update-13nov24-en.pdf>,
> as to avoid frequent edits and subsequent approvals. Previous efforts were
> initiated by the Council, while other changes were accomplished through
> Organizational Reviews anchored in Article 4.4. of the ICANN Bylaws
> <https://www.icann.org/resources/pages/governance/bylaws-en#article4.4>.
> As the ICANN community evolves towards a larger continuous improvement
> program, the GNSO?s SCCI and its TFs will be heavily involved in these
> efforts. While broad, GNSO project assignments will be limited to any
> processes and procedures that would have a GNSO-wide impact only. For
> avoidance of doubt, all assignments of the SCCI and TFs shall be first
> approved by the Council. Subsequently, any outcomes of the SCCI and TFs?
> project related work will be sent to the Council for their consideration
> and follow-up actions, if any. More details on the scope of projects can be
> found in Section II of the charter
> <https://gnso.icann.org/sites/default/files/policy/2024/draft/scci-charter-draft-update-13nov24-en.pdf>
>  and as new projects and/or assignments are distributed and in due
> course, completed, they will be managed via the GNSO?s Program Management
> Tool (PMT) Suite
> <https://community.icann.org/pages/viewpage.action?pageId=150178769>.
>
>
>
> *Who Should Join*
>
> SCCI is a representative model which shall consist of *a total of 21
> Members, 2 Board Liaisons, and 9 Observers.* All those that join will
> serve in representative capacity, where applicable, and as such, be
> responsible for consulting with their respective groups on a regular basis:
>
>    - A maximum of two members from each SG/C (14)
>    - One Council member from the Registrar Stakeholder Group (RrSG) (1)
>    - One Council member from the Registry Stakeholder Group (RySG) (1)
>    - One Council member from the Commercial Stakeholder Group (CSG) (1)
>    - One Council member from the Non-Commercial Stakeholder Group (NCSG)
>    (1)
>    - One Council NomCom Appointee (NCA) from each house (2)
>    - One Council NomCom Appointee, non-voting (1)
>    - Two GNSO Board Liaisons
>       - One CPH Board seat #13 (1)
>       - One NCPH Board seat #14 (1)
>
>
>    - Nine Observers:
>       - One Council Chair (1)
>       - One Chair from each SG/C (8)
>
>
>
> Members that are not a part of the Council will not have terms.
> Councilors, Observers, and Liaisons will turn-over naturally as their
> terms, defined in the ICANN Bylaws, conclude and are replaced by new
> representatives. However, SG/Cs who nominate members to participate should
> frequently assess and refresh their designated representatives to ensure
> active participation. Members must be appointed and/or reconfirmed by the
> leadership of the appointing SG/C and notification to the SCCI Chair and
> support staff.
>
>
>
> *How to Join*
>
> GNSO community members who wish to join the Standing Committee should
> contact the GNSO Secretariat at *gnso-secs at icann.org
> <gnso-secs at icann.org>* by *Monday, 6 January 2025.*
>
>
>
> *Background*
>
> For more information and to better prepare for participation on this
> Standing Committee, please read its charter
> <https://gnso.icann.org/sites/default/files/policy/2024/draft/scci-charter-draft-update-13nov24-en.pdf>,
> as well as visiting the CCOICI wiki page
> <https://community.icann.org/display/CCFOICI>.
>
>
>
> Please do not hesitate to get in touch if you have any questions.
>
>
>
> Kind regards,
>
> Julie H., Berry, and Saewon
>
> SCCI Support Staff
>
>
> _______________________________________________
> council mailing list -- council at icann.org
> To unsubscribe send an email to council-leave at icann.org
>
> _______________________________________________
> 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/20241130/22da73f5/attachment.htm>

From jumaropi at yahoo.com  Sat Nov 30 22:56:29 2024
From: jumaropi at yahoo.com (Juan Manuel Rojas)
Date: Sat, 30 Nov 2024 20:56:29 +0000 (UTC)
Subject: [NCSG-PC] Fwd: [council] Call for Volunteers for SCCI | Please
 Respond by 6 January
In-Reply-To: <CAH5sThmMjU0fqwR2DG_RtgU+abvLMxAO4gDwNKvK50R6wEK5yQ@mail.gmail.com>
References: <698C84A1-F28A-4430-A052-E39612BAD9F5@icann.org>
 <CAM8DdeV4EFNFj3ADbcKkwxDzr2djA-M3o5ngi0BATgYA-1zmEQ@mail.gmail.com>
 <CAH5sThmMjU0fqwR2DG_RtgU+abvLMxAO4gDwNKvK50R6wEK5yQ@mail.gmail.com>
Message-ID: <847580910.2455633.1733000189859@mail.yahoo.com>

Dear all,?
I would like to be one of representatives from NCSG. I was part of COICCI and that background could be helpful.?

Best Regards,?
JUAN MANUEL ROJAS, M.Sc.
Director - MINKA DIGITAL ColombiaNPOC Chair - NCSG/GNSO
M.Sc. Information Technology

Registered Linux User No.533108.
http://www.jmanurojas.com 

Cel. +57 301 743 56 00
Instagram: jmanurojas

-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT d- s: a+ C+++ UL P+ L+++ !E !W+++ !N !o K+++ w-- !O M- V PS+ PE-- Y+ PGP+ t+ 5 X++ R tv+ b+ DI D G e+++(+++)>+++ h+ r++ y+
------END GEEK CODE BLOCK------




? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 

    El s?bado, 30 de noviembre de 2024, 08:09:22 a.m. GMT-5, Rafik Dammak <rafik.dammak at gmail.com> escribi?:  
 
 Hi Tomslin,
It seems that we vmcab have 1 councilor from NCSG and 2 additional representatives from NCSG ( not sure how they end up with 14 reps from SG/C).?
So I assume there will be a call for candidates to appoint 2 representatives.
Best,
Rafik
On Wed, Nov 27, 2024, 04:14 Tomslin Samme-Nlar <mesumbeslin at gmail.com> wrote:

Hi Councillors,
Who would like to volunteer as our rep to the newly formed SCCI?

Warmly,
Tomslin


---------- Forwarded message ---------
From: Devan Reed via council <council at icann.org>
Date: Wed, 27 Nov 2024 at 01:05
Subject: [council] Call for Volunteers for SCCI | Please Respond by 6 January
To: council at gnso.icann.org <council at gnso.icann.org>
Cc: GNSO-Secs <gnso-secs at icann.org>



Dear Councilors,

?

The Generic Names Supporting Organization (GNSO) Council seeks volunteers to serve on the Standing Committee on Continuous Improvement (SCCI). The SCCI will be in charge of continuous improvement related projects that are focused on the GNSO?s structural, procedural, and process improvements to the Policy Development Process (PDP). This work originally commenced through a pilot under the?Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) Framework?(last updated 29 June 2021), which has now converted to a permanent standing committee following the?GNSO Council?s adoption of the charter.

?

What This Standing Committee Will Do

The SCCI and its dedicated Task Forces (TFs), populated by the Councilors and representatives of each Stakeholder Group (SG) and Constituency (C) (hereafter ?SG/C?), will execute a continuous improvement program that aims to improve the GNSO?s process and procedures over time through gradual changes. The goal is to achieve measurable improvements in the efficiency, effectiveness, performance, outcomes, accountability, transparency, and other indicators of quality for the GNSO. Notably, this work affects the GNSO community more broadly and is not limited to that of the Council.

?

Considering that this is a permanent standing committee, the specific scope of work across the varying projects that the SCCI and TFs will execute is not overly prescribed within the?charter, as to avoid frequent edits and subsequent approvals. Previous efforts were initiated by the Council, while other changes were accomplished through Organizational Reviews anchored in?Article 4.4. of the ICANN Bylaws. As the ICANN community evolves towards a larger continuous improvement program, the GNSO?s SCCI and its TFs will be heavily involved in these efforts. While broad, GNSO project assignments will be limited to any processes and procedures that would have a GNSO-wide impact only. For avoidance of doubt, all assignments of the SCCI and TFs shall be first approved by the Council. Subsequently, any outcomes of the SCCI and TFs? project related work will be sent to the Council for their consideration and follow-up actions, if any. More details on the scope of projects can be found in Section II of the?charter?and as new projects and/or assignments are distributed and in due course, completed, they will be managed via the?GNSO?s Program Management Tool (PMT) Suite.

?

Who Should Join

SCCI is a representative model which shall consist of?a total of 21 Members, 2 Board Liaisons, and 9 Observers.?All those that join will serve in representative capacity, where applicable, and as such, be responsible for consulting with their respective groups on a regular basis:
   
   - A maximum of two members from each SG/C (14)
   - One Council member from the Registrar Stakeholder Group (RrSG) (1)
   - One Council member from the Registry Stakeholder Group (RySG) (1)
   - One Council member from the Commercial Stakeholder Group (CSG) (1)
   - One Council member from the Non-Commercial Stakeholder Group (NCSG) (1)
   - One Council NomCom Appointee (NCA) from each house (2)
   - One Council NomCom Appointee, non-voting (1)
   - Two GNSO Board Liaisons      
      - One CPH Board seat #13 (1)
      - One NCPH Board seat #14 (1)

   
   - Nine Observers:      
      - One Council Chair (1)
      - One Chair from each SG/C (8)


?

Members that are not a part of the Council will not have terms. Councilors, Observers, and Liaisons will turn-over naturally as their terms, defined in the ICANN Bylaws, conclude and are replaced by new representatives. However, SG/Cs who nominate members to participate should frequently assess and refresh their designated representatives to ensure active participation. Members must be appointed and/or reconfirmed by the leadership of the appointing SG/C and notification to the SCCI Chair and support staff.

?

How to Join

GNSO community members who wish to join the Standing Committee should contact the GNSO Secretariat at?gnso-secs at icann.org?by?Monday, 6 January 2025.

?

Background

For more information and to better prepare for participation on this Standing Committee, please read its?charter, as well as visiting the?CCOICI wiki page.

?

Please do not hesitate to get in touch if you have any questions.

?

Kind regards,

Julie H., Berry, and Saewon

SCCI?Support Staff

?
_______________________________________________
council mailing list -- council at icann.org
To unsubscribe send an email to council-leave at icann.org

_______________________________________________
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/20241130/8a33fe14/attachment.htm>

From mesumbeslin at gmail.com  Sat Nov 30 23:06:39 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Sun, 1 Dec 2024 08:06:39 +1100
Subject: [NCSG-PC] [NCUC-DISCUSS] Fwd: [council] EPDP Phase 1 RegData
 Implementation - Billing Contact Issue Summary
In-Reply-To: <CAGSP6RSQOOkWabNryfDA92q7YV2LEDvgP6H-9OjBrC7R6NDJoQ@mail.gmail.com>
References: <B5CDB18C-C185-4060-993B-926D36FEF3E2@icann.org>
 <CAM8DdeVdBq-k1_fbigWU1TpK12PKBWSX_7QPL-knhf+CcuwU=Q@mail.gmail.com>
 <CAGSP6RSQOOkWabNryfDA92q7YV2LEDvgP6H-9OjBrC7R6NDJoQ@mail.gmail.com>
Message-ID: <CAM8DdeVgqFtkhb2e3tig1q1L+G=DxHFgqpHr7_fw6HvuDwK3HA@mail.gmail.com>

Good question @Pedro de Perdig?o Lana <pedrodeperdigaolana at gmail.com> .
Such has never been brought up in my 4 years as councillor. But I will
check with staff if there has been a similar situation in the past.

I am also keen to hear the thoughts of other members.

Warmly,
Tomslin

On Sat, 30 Nov 2024, 08:04 Pedro de Perdig?o Lana, <
pedrodeperdigaolana at gmail.com> wrote:

> Hi everyone,
>
> Just one doubt I had reading this: does the IRT formally have the
> competence to decide issues like this? In this case, to presume the
> interpretation related to a potential drafting error. Although on the
> merits there is an argument for improving privacy, it looks important to
> understand whether there are similar precedents in relation to past ICANN
> procedures or whether this would be a new situation. If the answer is "this
> is new", wouldn't referring the issue to the GNSO Council be more
> (procedurally) appropriate, to avoid opening doors that would possibly
> expand IRTs remit?
>
> Cordially,
>
> *Pedro de Perdig?o Lana*
> Lawyer <https://www.nic.br/>, GEDAI/UFPR <https://www.gedai.com.br/>
> Researcher
> PhD Candidate (UFPR), LLM in Business Law (UCoimbra)
> Coordination/Board/EC @ ISOC BR <https://isoc.org.br/>, NCUC
> <https://www.ncuc.org> & NCSG
> <https://community.icann.org/display/gnsononcomstake/Home>(ICANN),
> YouthLACIGF <https://youthlacigf.lat/>, IODA <https://ioda.org.br/> and CC
> Brasil <https://br.creativecommons.net/>
> This message is restricted to the sender and recipient(s). If received by
> mistake, please reply informing it.
>
>
> Em qui., 28 de nov. de 2024 ?s 09:07, Tomslin Samme-Nlar <
> mesumbeslin at gmail.com> escreveu:
>
>> Hi all
>>
>> Here is another summary I would like you to read and provide feedback on.
>> The details are well summarised in the below message but it is regarding
>> how the EPDP Phase 1 IRT believes  the billing contact data should be
>> treated in the Registration Data Policy.
>>
>> Specifically, we as NCSG have to answer the following question: *does
>> your group believe that (1) billing contact data was in scope for the EPDP
>> Temp Spec policy development? If yes, does your group agree that because
>> billing contact data was within the EPDP Team?s scope, (2) there was a
>> drafting error in the EPDP Phase 1 Final Report because the intention of
>> the recommendations, by not including a recommendation concerning the
>> collection, escrow, etc of billing contact data was that the collection and
>> retention of billing contact data should be optional and not mandatory?*
>>
>> Our NCUC members to the IRT are  Stephanie Perrin, Afi Edoh and Wisdom
>> Donkor who might perhaps be able to help provide more details if anyone has
>> questions.
>>
>> Warmly,
>> Tomslin
>>
>>
>>
>> ---------- Forwarded message ---------
>> From: Caitlin Tubergen via council <council at icann.org>
>> Date: Thu, 28 Nov 2024 at 09:42
>> Subject: [council] EPDP Phase 1 RegData Implementation - Billing Contact
>> Issue Summary
>> To: council at gnso.icann.org <council at gnso.icann.org>
>>
>>
>> Dear Councilors,
>>
>>
>>
>> During the ICANN81 GNSO Council Wrap-Up
>> <https://icann81.sched.com/event/1p2Gu/gnso-council-wrap-up>, Thomas
>> Rickert provided an update regarding the implementation of EPDP Temp Spec
>> Phase 1 recommendations. Thomas is the current GNSO Council Liaison to the
>> EPDP Temp Spec Phase 1 Implementation Review Team (IRT).
>>
>>
>>
>> For background, the Registration Data Policy
>> <https://www.icann.org/resources/pages/registration-data-policy-2024-02-21-en>
>> was published on 21 February 2024, and the policy has an effective date of
>> 21 August 2025.
>>
>>
>>
>> The EPDP Phase 1 policy recommendations
>> <https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-gtld-registration-data-specs-final-2-20feb19-en.pdf>
>> do not reference billing contact data, and the Registration Data Policy
>> <https://www.icann.org/resources/pages/registration-data-policy-2024-02-21-en>
>> also makes no reference to billing contact data.
>>
>>
>>
>> Billing contact data, however, is referenced in the Registrar
>> Accreditation Agreement
>> <https://www.icann.org/en/system/files/files/registrar-accreditation-agreement-21jan24-en.html>
>> (RAA) in ? 3.4.1.3 and in the Data Retention Specification
>> <https://www.icann.org/en/system/files/files/registrar-accreditation-agreement-21jan24-en.html#data-retention>
>> in ?1.1.2 ? ?1.1.5. The billing contact data is also referenced in the
>> existing Registrar Data Escrow Specifications
>> <https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf>.
>> ICANN?s publication of updated Registrar Data Escrow Specifications
>> <https://www.icann.org/en/system/files/files/rde-specs-14aug24-en.pdf>
>> in August triggered a discussion within the EPDP Phase 1 IRT regarding the
>> Registration Data Policy?s intended impact on the RAA requirements
>> concerning the billing contact data fields.
>>
>>
>>
>> Generally speaking, unless in conflict with or otherwise modified by a
>> policy recommendation, current contractual requirements and consensus
>> policy requirements remain in place following the publication of a new
>> policy. For that reason, ICANN org informed the IRT on 8 August 2024 that
>> billing contact data must still be collected and retained pursuant to
>> current RAA requirements.
>>
>>
>>
>> In response, some registrar members of the IRT expressed the view that
>> the absence of a reference to billing contact data was a drafting error,
>> and the EPDP Team intended for the collection of billing contact data to be
>> optional and not mandatory. The registrar IRT members noted the reference
>> to ?billing contact? within charter question b1, which provides, ?b1) What
>> data should registrars be required to collect for each of the following
>> contacts: Registrant, Tech, Admin, Billing?? Because billing contact is
>> referenced in this charter question but the EPDP Team did not provide a
>> recommendation regarding mandatory (or optional) collection of the billing
>> contact, the registrar position is that the billing contact is no longer
>> required to be collected.
>>
>>
>>
>> On 25 September 2024, there was a special meeting of the IRT
>> <https://community.icann.org/display/RDPIRT/2024-09-25+Registration+Data+Policy+Implementation+IRT+Meeting>
>> to discuss the topic of billing contact. While no objection to the
>> registrar view was raised during the special meeting, it is unclear at this
>> stage whether this is a broadly supported view of the IRT, as the majority
>> of stakeholder groups did not have IRT members present at the special
>> meeting. Specifically, members from the BC, GAC, IPC, ISPCP, IPC, NCSG, and
>> SSAC were not in attendance
>> <https://community.icann.org/display/RDPIRT/2024-09-25+Registration+Data+Policy+Implementation+IRT+Meeting?preview=/375914530/379191359/Attendance%20Reg%20Data%20Pol%20IRT%2025%20Sep%2024.pdf>
>> .
>>
>>
>>
>> It is worth noting that billing contact information is not referenced in
>> the Temporary Specification, nor is it part of the RDDS specification in
>> the RAA, so it could be argued that billing contact data was not in scope
>> for EPDP Temp Spec Phase 1 policy development. It could also be argued that
>> the drafting error was in the EPDP charter, as billing contact should not
>> have been referenced since it is not part of the Temporary Specification.
>> It is also worth noting that there are other elements within the RAA and
>> Data Retention Specification that were not part of the Temporary
>> Specification and are still required.
>>
>>
>>
>> Thomas provided a high-level overview during the wrap-up session, and
>> noted that some IRT members believe this drafting error is
>> noncontroversial. However, Thomas noted that in the interest of
>> transparency, all Councilors should consult with their respective groups to
>> ensure that others are properly informed and agree with the interpretation
>> raised by the registrars within the IRT. Thomas has also requested that
>> further discussion of billing contact data within the Registration Data
>> Policy be added as a discussion item to the GNSO Council?s December meeting.
>>
>>
>>
>> Accordingly, please check in with your groups regarding the treatment of
>> billing contact data in the Registration Data Policy
>> <https://www.icann.org/resources/pages/registration-data-policy-2024-02-21-en>.
>> *Specifically, does your group believe that (1) billing contact data was
>> in scope for the EPDP Temp Spec policy development? If yes, does your group
>> agree that because billing contact data was within the EPDP Team?s scope,
>> (2) there was a drafting error in the EPDP Phase 1 Final Report because the
>> intention of the recommendations, by not including a recommendation
>> concerning the collection, escrow, etc of billing contact data was that the
>> collection and retention of billing contact data should be optional and not
>> mandatory? Note: If, as a matter of ICANN Consensus Policy this was the
>> intended outcome, this interpretation would change current contractual
>> requirements for registrars. *
>>
>>
>>
>> We invite Thomas and other councilors to provide additional context.
>> Please feel free to provide thoughts via the list in advance of the
>> December meeting, and please be prepared to discuss next steps during the
>> 19 December Council meeting.
>>
>>
>>
>> Kind regards, and Happy Thanksgiving to those who celebrate,
>>
>> Caitlin
>>
>>
>>
>>
>> _______________________________________________
>> council mailing list -- council at icann.org
>> To unsubscribe send an email to council-leave at icann.org
>>
>> _______________________________________________
>> 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.
>> _______________________________________________
>> Ncuc-discuss mailing list
>> Ncuc-discuss at lists.ncuc.org
>> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20241201/59bf5777/attachment.htm>

From pedrodeperdigaolana at gmail.com  Fri Nov 29 17:48:00 2024
From: pedrodeperdigaolana at gmail.com (=?UTF-8?Q?Pedro_de_Perdig=C3=A3o_Lana?=)
Date: Fri, 29 Nov 2024 12:48:00 -0300
Subject: [NCSG-PC] [NCSG-EC] Fwd: [SOAC-Leaders-ICANNMeeting-Planning]
 Action Items from ICANN82 Production call #1 and Doodle next call
In-Reply-To: <CAN1qJvD2VgSaX2uAiOB4BUJviMqN1jCCvrFz8_11fPHyjffb5Q@mail.gmail.com>
References: <508DACC7-A620-46B1-94C3-D32D954E37ED@icann.org>
 <CAH5sThmEWy48k1GhepeJGkd-Lhn7C2JhZnSb5PO4b4ZxPE6LCw@mail.gmail.com>
 <CAN1qJvD2VgSaX2uAiOB4BUJviMqN1jCCvrFz8_11fPHyjffb5Q@mail.gmail.com>
Message-ID: <CAGSP6RTeuBSKbgCfRqO3VTacbLybNi8y-9x7vtWkaYGev=W0hA@mail.gmail.com>

Hi,

I think my only real discomfort was that the community session on emerging
technologies seemed very superficial, and quite a few people commented on
this. We do need to be sure that the people who speak in those spaces are
real experts on the themes, to avoid delegitimizing these spaces.

Cordially,

*Pedro de Perdig?o Lana*
Advogado - OAB/PR 90.600 <https://www.nic.br/>,  Pesquisador (GEDAI/UFPR
<https://www.gedai.com.br/>)
Doutorando em Direito (UFPR), Mestre em Direito Empresarial (UCoimbra),
Coordena??o/Diretoria/EC @ ISOC BR <https://isoc.org.br/>, NCUC
<https://www.ncuc.org> & NCSG
<https://community.icann.org/display/gnsononcomstake/Home>(ICANN),
YouthLACIGF <https://youthlacigf.lat/>, IODA <https://ioda.org.br/> e CC
Brasil <https://br.creativecommons.net/>.
Essa mensagem ? restrita ao remetente e destinat?rio(s). Se recebida por
engano, favor responder informando o erro.


Em qui., 28 de nov. de 2024 ?s 02:11, farzaneh badii via NCSG-EC <
ncsg-ec at lists.ncsg.is> escreveu:

> Thanks Rafik.
>
> It was a very well organized meeting and I appreciated the brewed tea
> instead of a terrible tea bag!
> I have to first thank Andrea for all the support for the HRIA session. She
> went above and beyond to provide us with our last minute requests.
>
> The geopolitical forum is always a monologue. I don't know why. so
> I support the suggestion to have a webinar before and just have Q&A but I
> also think we don't need Q&A we need issues that need to be addressed and
> give the community a chance to express it at the mic.
>
> For the community sessions, I don't know what we want to do with these
> cross community sessions but they are so time intensive that you have to
> attend all the organizing calls to be able to put the name of a
> noncommercial in. Also the topics, they were not very up to date I have to
> say. Can we invite some external experts as well to talk about
> geopolitics.They need a total revamp otherwise each session every meeting
> is going to have the same representative covering the same talking points.
>
> I liked the half an hour/an hour reception after each day in
> other meetings, it really allows us to hang out with other members of the
> community before we go to our receptions, dinners etc and we can have
> informal policy conversations. Is that something that we do only during
> Community or policy forum? If too hard to have a reception, maybe we can do
> networking breakfasts? They don't have to do the catering, I just think we
> can get more chances to talk to other community members.
>
> I didn't know they had switched the public forum to the morning and I
> missed it. Well my fault for not checking the agenda carefully but then the
> switch didn't make sense, it always made better sense to have it right
> before the Board AGM. But I don't know how others felt about it.
>
> This is again my bad, but our session on human rights and dns abuse was
> packed. So if we want to do some similar stuff we should specify a larger
> capacity.
>
> The transcription of this meeting was a bit off. Maybe I just paid more
> attention. Also I don't know if it's my ears or the equipment, but I
> sometimes had difficulty hearing people and others told me that audio
> quality has been poor in the rooms in recent ICANN meetings (so it's not
> venue related).
>
>
>
>
>
> Farzaneh
>
>
> On Wed, Nov 27, 2024 at 11:49?PM Rafik Dammak via NCSG-EC <
> ncsg-ec at lists.ncsg.is> wrote:
>
>> Hi all,
>>
>> Those are points from the ICANN planning meeting.
>> Any comment/feedback would be appreciated.
>>
>> Best regards,
>>
>>
>> Rafik
>>
>> ---------- Forwarded message ---------
>> From: Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning <
>> soac-leaders-icannmeeting-planning at icann.org>
>> Date: Tue, Nov 26, 2024, 20:08
>> Subject: [SOAC-Leaders-ICANNMeeting-Planning] Action Items from ICANN82
>> Production call #1 and Doodle next call
>> To: soac-leaders-icannmeeting-planning at icann.org <
>> soac-leaders-icannmeeting-planning at icann.org>
>>
>>
>>  Dear all,
>>
>>
>>
>> Thank you for attending the ICANN82 Production call held today on Monday
>> 25 November 2024. For those of you unable to attend, please find the
>> Zoom recording.
>> <https://icann.zoom.us/rec/play/8T35m0TfR__yA7AMW6Gd6MTBWohYihNwuh8Z83xBpX26ti8jCGbAHS6O7ZXZgPjmMVTCXumEWsHn4mRi.JEDmOcygROqh-Pec?autoplay=true&startTime=1732557795000>
>>
>>
>>
>>
>> ?? Please complete the Doodle poll for a next call next week:
>> https://doodle.com/meeting/participate/id/dGzny05b ??
>>
>>
>>
>> *ICANN81 Feedback:*
>>
>> The feedback from ICANN81 was mainly positive. The venue location with
>> hotels close by, as well as restaurants and caf?s, was appreciated. The
>> abundance of seating areas allowed for additional conversations. Having
>> food stalls available at the venue was extremely helpful. However, certain
>> room sizes and seating were deemed insufficient as several sessions were
>> held with standing room only given high attendance. The height of speaker
>> screens in the GAC room will need adjusting to avoid speaker discomfort.
>> The issue of session conflicts whilst improved upon, needs continued focus.
>> The suggestion was made to add a Zoom poll at the end of the Community
>> Session to gather immediate feedback.
>>
>>
>>
>> Here are the main items raised for consideration for ICANN82:
>>
>>
>>
>> *Areas needing improvement based on ICANN81 feedback:  *
>>
>>    1. room size information,
>>    2. speaker screen height,
>>    3. session conflicts,
>>    4. adding a Zoom poll to the end of the Community Session.
>>
>> These items have been duly noted as action items for staff support.
>>
>>
>>
>> *ICANN83 Block schedule:*
>>
>>    - The geopolitical forum is well attended, but lacking in interaction
>>    opportunities. The suggestion was made to hold the update section of the
>>    session during Prep Week, and a shorter, interactive section during the
>>    ICANN meeting. This would also free up a 90-min slot which will assist with
>>    SO/AC scheduling.
>>    - Most on the call were in favour of keeping the Community Session,
>>    but agreed that the topic decision would need to be made closer to the
>>    time.
>>    - The Q&A with the ICANN Executive team is a useful session,
>>    especially in the light of the new CEO coming onboard in the next few
>>    weeks. Sally will confirm the format of the community/CEO exchange with
>>    Kurtis and will come back to the group.
>>    - The joint ccNSO/ ICANN Board session will ideally take place on
>>    Tuesday or Wednesday, instead of the current slot on Thursday.
>>
>>
>>
>> If community leaders would be so kind as to socialize these points with
>> their members ahead of the call next week, this would be extremely helpful.
>> An updated Block Schedule will be circulated ahead of the call
>> incorporating the input received.
>>
>>
>>
>> Thank you all!
>>
>>
>>
>> Best,
>>
>>
>>
>> Nathalie
>>
>> _______________________________________________
>> SOAC-Leaders-ICANNMeeting-Planning mailing list --
>> soac-leaders-icannmeeting-planning at icann.org
>> To unsubscribe send an email to
>> soac-leaders-icannmeeting-planning-leave at icann.org
>>
>> _______________________________________________
>> 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-EC mailing list
>> NCSG-EC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>>
> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20241129/1b063267/attachment.htm>

From pedrodeperdigaolana at gmail.com  Fri Nov 29 23:03:00 2024
From: pedrodeperdigaolana at gmail.com (=?UTF-8?Q?Pedro_de_Perdig=C3=A3o_Lana?=)
Date: Fri, 29 Nov 2024 18:03:00 -0300
Subject: [NCSG-PC] [NCUC-DISCUSS] Fwd: [council] EPDP Phase 1 RegData
 Implementation - Billing Contact Issue Summary
In-Reply-To: <CAM8DdeVdBq-k1_fbigWU1TpK12PKBWSX_7QPL-knhf+CcuwU=Q@mail.gmail.com>
References: <B5CDB18C-C185-4060-993B-926D36FEF3E2@icann.org>
 <CAM8DdeVdBq-k1_fbigWU1TpK12PKBWSX_7QPL-knhf+CcuwU=Q@mail.gmail.com>
Message-ID: <CAGSP6RSQOOkWabNryfDA92q7YV2LEDvgP6H-9OjBrC7R6NDJoQ@mail.gmail.com>

Hi everyone,

Just one doubt I had reading this: does the IRT formally have the
competence to decide issues like this? In this case, to presume the
interpretation related to a potential drafting error. Although on the
merits there is an argument for improving privacy, it looks important to
understand whether there are similar precedents in relation to past ICANN
procedures or whether this would be a new situation. If the answer is "this
is new", wouldn't referring the issue to the GNSO Council be more
(procedurally) appropriate, to avoid opening doors that would possibly
expand IRTs remit?

Cordially,

*Pedro de Perdig?o Lana*
Lawyer <https://www.nic.br/>, GEDAI/UFPR <https://www.gedai.com.br/>
Researcher
PhD Candidate (UFPR), LLM in Business Law (UCoimbra)
Coordination/Board/EC @ ISOC BR <https://isoc.org.br/>, NCUC
<https://www.ncuc.org> & NCSG
<https://community.icann.org/display/gnsononcomstake/Home>(ICANN),
YouthLACIGF <https://youthlacigf.lat/>, IODA <https://ioda.org.br/> and CC
Brasil <https://br.creativecommons.net/>
This message is restricted to the sender and recipient(s). If received by
mistake, please reply informing it.


Em qui., 28 de nov. de 2024 ?s 09:07, Tomslin Samme-Nlar <
mesumbeslin at gmail.com> escreveu:

> Hi all
>
> Here is another summary I would like you to read and provide feedback on.
> The details are well summarised in the below message but it is regarding
> how the EPDP Phase 1 IRT believes  the billing contact data should be
> treated in the Registration Data Policy.
>
> Specifically, we as NCSG have to answer the following question: *does
> your group believe that (1) billing contact data was in scope for the EPDP
> Temp Spec policy development? If yes, does your group agree that because
> billing contact data was within the EPDP Team?s scope, (2) there was a
> drafting error in the EPDP Phase 1 Final Report because the intention of
> the recommendations, by not including a recommendation concerning the
> collection, escrow, etc of billing contact data was that the collection and
> retention of billing contact data should be optional and not mandatory?*
>
> Our NCUC members to the IRT are  Stephanie Perrin, Afi Edoh and Wisdom
> Donkor who might perhaps be able to help provide more details if anyone has
> questions.
>
> Warmly,
> Tomslin
>
>
>
> ---------- Forwarded message ---------
> From: Caitlin Tubergen via council <council at icann.org>
> Date: Thu, 28 Nov 2024 at 09:42
> Subject: [council] EPDP Phase 1 RegData Implementation - Billing Contact
> Issue Summary
> To: council at gnso.icann.org <council at gnso.icann.org>
>
>
> Dear Councilors,
>
>
>
> During the ICANN81 GNSO Council Wrap-Up
> <https://icann81.sched.com/event/1p2Gu/gnso-council-wrap-up>, Thomas
> Rickert provided an update regarding the implementation of EPDP Temp Spec
> Phase 1 recommendations. Thomas is the current GNSO Council Liaison to the
> EPDP Temp Spec Phase 1 Implementation Review Team (IRT).
>
>
>
> For background, the Registration Data Policy
> <https://www.icann.org/resources/pages/registration-data-policy-2024-02-21-en>
> was published on 21 February 2024, and the policy has an effective date of
> 21 August 2025.
>
>
>
> The EPDP Phase 1 policy recommendations
> <https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-gtld-registration-data-specs-final-2-20feb19-en.pdf>
> do not reference billing contact data, and the Registration Data Policy
> <https://www.icann.org/resources/pages/registration-data-policy-2024-02-21-en>
> also makes no reference to billing contact data.
>
>
>
> Billing contact data, however, is referenced in the Registrar
> Accreditation Agreement
> <https://www.icann.org/en/system/files/files/registrar-accreditation-agreement-21jan24-en.html>
> (RAA) in ? 3.4.1.3 and in the Data Retention Specification
> <https://www.icann.org/en/system/files/files/registrar-accreditation-agreement-21jan24-en.html#data-retention>
> in ?1.1.2 ? ?1.1.5. The billing contact data is also referenced in the
> existing Registrar Data Escrow Specifications
> <https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf>.
> ICANN?s publication of updated Registrar Data Escrow Specifications
> <https://www.icann.org/en/system/files/files/rde-specs-14aug24-en.pdf> in
> August triggered a discussion within the EPDP Phase 1 IRT regarding the
> Registration Data Policy?s intended impact on the RAA requirements
> concerning the billing contact data fields.
>
>
>
> Generally speaking, unless in conflict with or otherwise modified by a
> policy recommendation, current contractual requirements and consensus
> policy requirements remain in place following the publication of a new
> policy. For that reason, ICANN org informed the IRT on 8 August 2024 that
> billing contact data must still be collected and retained pursuant to
> current RAA requirements.
>
>
>
> In response, some registrar members of the IRT expressed the view that the
> absence of a reference to billing contact data was a drafting error, and
> the EPDP Team intended for the collection of billing contact data to be
> optional and not mandatory. The registrar IRT members noted the reference
> to ?billing contact? within charter question b1, which provides, ?b1) What
> data should registrars be required to collect for each of the following
> contacts: Registrant, Tech, Admin, Billing?? Because billing contact is
> referenced in this charter question but the EPDP Team did not provide a
> recommendation regarding mandatory (or optional) collection of the billing
> contact, the registrar position is that the billing contact is no longer
> required to be collected.
>
>
>
> On 25 September 2024, there was a special meeting of the IRT
> <https://community.icann.org/display/RDPIRT/2024-09-25+Registration+Data+Policy+Implementation+IRT+Meeting>
> to discuss the topic of billing contact. While no objection to the
> registrar view was raised during the special meeting, it is unclear at this
> stage whether this is a broadly supported view of the IRT, as the majority
> of stakeholder groups did not have IRT members present at the special
> meeting. Specifically, members from the BC, GAC, IPC, ISPCP, IPC, NCSG, and
> SSAC were not in attendance
> <https://community.icann.org/display/RDPIRT/2024-09-25+Registration+Data+Policy+Implementation+IRT+Meeting?preview=/375914530/379191359/Attendance%20Reg%20Data%20Pol%20IRT%2025%20Sep%2024.pdf>
> .
>
>
>
> It is worth noting that billing contact information is not referenced in
> the Temporary Specification, nor is it part of the RDDS specification in
> the RAA, so it could be argued that billing contact data was not in scope
> for EPDP Temp Spec Phase 1 policy development. It could also be argued that
> the drafting error was in the EPDP charter, as billing contact should not
> have been referenced since it is not part of the Temporary Specification.
> It is also worth noting that there are other elements within the RAA and
> Data Retention Specification that were not part of the Temporary
> Specification and are still required.
>
>
>
> Thomas provided a high-level overview during the wrap-up session, and
> noted that some IRT members believe this drafting error is
> noncontroversial. However, Thomas noted that in the interest of
> transparency, all Councilors should consult with their respective groups to
> ensure that others are properly informed and agree with the interpretation
> raised by the registrars within the IRT. Thomas has also requested that
> further discussion of billing contact data within the Registration Data
> Policy be added as a discussion item to the GNSO Council?s December meeting.
>
>
>
> Accordingly, please check in with your groups regarding the treatment of
> billing contact data in the Registration Data Policy
> <https://www.icann.org/resources/pages/registration-data-policy-2024-02-21-en>.
> *Specifically, does your group believe that (1) billing contact data was
> in scope for the EPDP Temp Spec policy development? If yes, does your group
> agree that because billing contact data was within the EPDP Team?s scope,
> (2) there was a drafting error in the EPDP Phase 1 Final Report because the
> intention of the recommendations, by not including a recommendation
> concerning the collection, escrow, etc of billing contact data was that the
> collection and retention of billing contact data should be optional and not
> mandatory? Note: If, as a matter of ICANN Consensus Policy this was the
> intended outcome, this interpretation would change current contractual
> requirements for registrars. *
>
>
>
> We invite Thomas and other councilors to provide additional context.
> Please feel free to provide thoughts via the list in advance of the
> December meeting, and please be prepared to discuss next steps during the
> 19 December Council meeting.
>
>
>
> Kind regards, and Happy Thanksgiving to those who celebrate,
>
> Caitlin
>
>
>
>
> _______________________________________________
> council mailing list -- council at icann.org
> To unsubscribe send an email to council-leave at icann.org
>
> _______________________________________________
> 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.
> _______________________________________________
> Ncuc-discuss mailing list
> Ncuc-discuss at lists.ncuc.org
> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20241129/086fa6e0/attachment.htm>