From andrea.glandon at icann.org  Thu Jan  2 18:39:08 2025
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Thu, 2 Jan 2025 16:39:08 +0000
Subject: [NCSG-PC] [Ext] Re: [NCSG-EC] ICANN82 NCSG Issue Forum
In-Reply-To: <CAH5sTh=YX1L+LvAk8XjSJMSPP1p2WM+RfUogvC84_bb=YaWUsQ@mail.gmail.com>
References: <AC0E0ABA-2D6B-427A-98DF-17A593CBE7AE@icann.org>
 <CAH5sTh=YX1L+LvAk8XjSJMSPP1p2WM+RfUogvC84_bb=YaWUsQ@mail.gmail.com>
Message-ID: <88C34156-A952-4A67-833B-0383FDB27D80@icann.org>

Hello all.

Happy New Year!

I just wanted to confirm that I will be switching the NCSG Issue Forum to Tuesday, 13:15-14:30 local time.

Thanks!
Kind Regards,
Andrea


From: Rafik Dammak <rafik.dammak at gmail.com>
Date: Friday, December 20, 2024 at 16:16
To: Andrea Glandon <andrea.glandon at icann.org>
Cc: NCSG EC <NCSG-ec at lists.ncsg.is>, ncsg-pc <ncsg-pc at lists.ncsg.is>
Subject: [Ext] Re: [NCSG-EC] ICANN82 NCSG Issue Forum

Hi Andrea,

I think the straightforward choice is to select Tuesday and that will link to other NCSG sessions in that day.

Best,

Rafik
On Sat, Dec 21, 2024, 01:19 Andrea Glandon via NCSG-EC <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>> wrote:
Hello all,

Currently the NCSG Issue Forum is scheduled on Sunday, 09 March, 1030-12. This is against a GNSO Working Session.

Here are some other possibilities for the session. I am also attaching a PDF with all sessions and sessions that NCSG will be participating in with other groups. I know it?s tiny, but you can enlarge to see better.

Tuesday, 11 March 1315-1430
Wednesday, 12 March 0900-1000, against Sub Pro IRT & PPSAI IRT
Wednesday, 12 March 1030-1200, against an RrSG session called RrSG Outreach: A registrant?s journey
Thursday, 13 March 0900-1000, against the Geopolitical Forum
Thursday, 13 March 1500-1600 against SubPro IRT

Once this session is set, then I can reach out to SSAC to try to get a session scheduled with them.

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



_______________________________________________
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!4H1MUJVGEpTfdM2OWbZfgTt5-FXJjW0Vr3xLIHfkkJznjufX_Z2TcJq00lTmeJoDVz-v64yNWxbRtYeFDA6gTRa4mK8FstM$>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250102/02f6fdf4/attachment.htm>

From andrea.glandon at icann.org  Thu Jan  2 18:59:33 2025
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Thu, 2 Jan 2025 16:59:33 +0000
Subject: [NCSG-PC] [NCSG-EC] [Ext] Re:  ICANN82 NCSG Issue Forum
In-Reply-To: <88C34156-A952-4A67-833B-0383FDB27D80@icann.org>
References: <AC0E0ABA-2D6B-427A-98DF-17A593CBE7AE@icann.org>
 <CAH5sTh=YX1L+LvAk8XjSJMSPP1p2WM+RfUogvC84_bb=YaWUsQ@mail.gmail.com>
 <88C34156-A952-4A67-833B-0383FDB27D80@icann.org>
Message-ID: <7372F653-6FD1-4BEF-BA98-3DD62B4BF30B@icann.org>

Please find attached the most updated draft ICANN82 schedule.

Kind Regards,
Andrea


From: NCSG-EC <ncsg-ec-bounces at lists.ncsg.is> on behalf of Andrea Glandon via NCSG-EC <NCSG-ec at lists.ncsg.is>
Reply-To: Andrea Glandon <andrea.glandon at icann.org>
Date: Thursday, January 2, 2025 at 10:39
To: Rafik Dammak <rafik.dammak at gmail.com>
Cc: ncsg-pc <ncsg-pc at lists.ncsg.is>, NCSG EC <NCSG-ec at lists.ncsg.is>
Subject: Re: [NCSG-EC] [Ext] Re: ICANN82 NCSG Issue Forum

Hello all.

Happy New Year!

I just wanted to confirm that I will be switching the NCSG Issue Forum to Tuesday, 13:15-14:30 local time.

Thanks!
Kind Regards,
Andrea


From: Rafik Dammak <rafik.dammak at gmail.com>
Date: Friday, December 20, 2024 at 16:16
To: Andrea Glandon <andrea.glandon at icann.org>
Cc: NCSG EC <NCSG-ec at lists.ncsg.is>, ncsg-pc <ncsg-pc at lists.ncsg.is>
Subject: [Ext] Re: [NCSG-EC] ICANN82 NCSG Issue Forum

Hi Andrea,

I think the straightforward choice is to select Tuesday and that will link to other NCSG sessions in that day.

Best,

Rafik
On Sat, Dec 21, 2024, 01:19 Andrea Glandon via NCSG-EC <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>> wrote:
Hello all,

Currently the NCSG Issue Forum is scheduled on Sunday, 09 March, 1030-12. This is against a GNSO Working Session.

Here are some other possibilities for the session. I am also attaching a PDF with all sessions and sessions that NCSG will be participating in with other groups. I know it?s tiny, but you can enlarge to see better.

Tuesday, 11 March 1315-1430
Wednesday, 12 March 0900-1000, against Sub Pro IRT & PPSAI IRT
Wednesday, 12 March 1030-1200, against an RrSG session called RrSG Outreach: A registrant?s journey
Thursday, 13 March 0900-1000, against the Geopolitical Forum
Thursday, 13 March 1500-1600 against SubPro IRT

Once this session is set, then I can reach out to SSAC to try to get a session scheduled with them.

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



_______________________________________________
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!4H1MUJVGEpTfdM2OWbZfgTt5-FXJjW0Vr3xLIHfkkJznjufX_Z2TcJq00lTmeJoDVz-v64yNWxbRtYeFDA6gTRa4mK8FstM$>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250102/bb7e4924/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ICANN82 GNSO Draft Schedule & Community requests - Draft tab.pdf
Type: application/pdf
Size: 79702 bytes
Desc: ICANN82 GNSO Draft Schedule & Community requests - Draft tab.pdf
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250102/bb7e4924/attachment.pdf>

From rafik.dammak at gmail.com  Fri Jan  3 02:46:13 2025
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Fri, 3 Jan 2025 09:46:13 +0900
Subject: [NCSG-PC] New NCUC representatives
Message-ID: <CAH5sThkDhCJAAEjt1J6V=tUMUb8VSEVuE3kLrLp_2y0kT4GkDA@mail.gmail.com>

Hi all,

Wisdom shared the appointment of new NCUC representatives to NCSG PC
:Michaela Nakayama Shapiro and Peterking Quaye. Andrea will add them to the
list. Let's welcome them and thank the previous NCUC representatives for
their service.

Best regards,

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

From rafik.dammak at gmail.com  Fri Jan  3 04:03:14 2025
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Fri, 3 Jan 2025 11:03:14 +0900
Subject: [NCSG-PC] [NCSG-EC] [Ext] Re: ICANN82 NCSG Issue Forum
In-Reply-To: <7372F653-6FD1-4BEF-BA98-3DD62B4BF30B@icann.org>
References: <AC0E0ABA-2D6B-427A-98DF-17A593CBE7AE@icann.org>
 <CAH5sTh=YX1L+LvAk8XjSJMSPP1p2WM+RfUogvC84_bb=YaWUsQ@mail.gmail.com>
 <88C34156-A952-4A67-833B-0383FDB27D80@icann.org>
 <7372F653-6FD1-4BEF-BA98-3DD62B4BF30B@icann.org>
Message-ID: <CAH5sTh=QP41BEpU-UO-60+c-YrCL4mSeHoFrccMoMxWun-ky2A@mail.gmail.com>

Hi Andrea,

Thanks for the updated schedule. can we have also listed the other joint
sessions there e.g. GAC, ALAC, SSAC for those confirmed.
FYI we also confirmed the usual breakfast meeting with Chris and Becky. We
will also have a call with Chris this month, meeting invite to be sent soon.

Best,

Rafik
Le ven. 3 janv. 2025 ? 02:02, Andrea Glandon <andrea.glandon at icann.org> a
?crit :

> Please find attached the most updated draft ICANN82 schedule.
>
>
>
> Kind Regards,
>
> Andrea
>
>
>
>
>
> *From: *NCSG-EC <ncsg-ec-bounces at lists.ncsg.is> on behalf of Andrea
> Glandon via NCSG-EC <NCSG-ec at lists.ncsg.is>
> *Reply-To: *Andrea Glandon <andrea.glandon at icann.org>
> *Date: *Thursday, January 2, 2025 at 10:39
> *To: *Rafik Dammak <rafik.dammak at gmail.com>
> *Cc: *ncsg-pc <ncsg-pc at lists.ncsg.is>, NCSG EC <NCSG-ec at lists.ncsg.is>
> *Subject: *Re: [NCSG-EC] [Ext] Re: ICANN82 NCSG Issue Forum
>
>
>
> Hello all.
>
>
>
> Happy New Year!
>
>
>
> I just wanted to confirm that I will be switching the NCSG Issue Forum to
> Tuesday, 13:15-14:30 local time.
>
>
>
> Thanks!
>
> Kind Regards,
>
> Andrea
>
>
>
>
>
> *From: *Rafik Dammak <rafik.dammak at gmail.com>
> *Date: *Friday, December 20, 2024 at 16:16
> *To: *Andrea Glandon <andrea.glandon at icann.org>
> *Cc: *NCSG EC <NCSG-ec at lists.ncsg.is>, ncsg-pc <ncsg-pc at lists.ncsg.is>
> *Subject: *[Ext] Re: [NCSG-EC] ICANN82 NCSG Issue Forum
>
>
>
> Hi Andrea,
>
>
>
> I think the straightforward choice is to select Tuesday and that will link
> to other NCSG sessions in that day.
>
>
>
> Best,
>
>
>
> Rafik
>
> On Sat, Dec 21, 2024, 01:19 Andrea Glandon via NCSG-EC <
> ncsg-ec at lists.ncsg.is> wrote:
>
> Hello all,
>
>
>
> Currently the NCSG Issue Forum is scheduled on Sunday, 09 March, 1030-12.
> This is against a GNSO Working Session.
>
>
>
> Here are some other possibilities for the session. I am also attaching a
> PDF with all sessions and sessions that NCSG will be participating in with
> other groups. I know it?s tiny, but you can enlarge to see better.
>
>
>
> Tuesday, 11 March 1315-1430
>
> Wednesday, 12 March 0900-1000, against Sub Pro IRT & PPSAI IRT
>
> Wednesday, 12 March 1030-1200, against an RrSG session called RrSG
> Outreach: A registrant?s journey
>
> Thursday, 13 March 0900-1000, against the Geopolitical Forum
>
> Thursday, 13 March 1500-1600 against SubPro IRT
>
>
>
> Once this session is set, then I can reach out to SSAC to try to get a
> session scheduled with them.
>
>
>
> Thank you!
>
> *Andrea Glandon*
>
> Policy Operations Sr. Coordinator
>
> Internet Corporation for Assigned Names and Numbers (ICANN)
>
> *Skype ID:*  acglandon76
>
>
>
>
>
>
>
> _______________________________________________
> NCSG-EC mailing list
> 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!4H1MUJVGEpTfdM2OWbZfgTt5-FXJjW0Vr3xLIHfkkJznjufX_Z2TcJq00lTmeJoDVz-v64yNWxbRtYeFDA6gTRa4mK8FstM$>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250103/267b088f/attachment.htm>

From andrea.glandon at icann.org  Fri Jan  3 16:15:33 2025
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Fri, 3 Jan 2025 14:15:33 +0000
Subject: [NCSG-PC] [NCSG-EC] [Ext] Re: ICANN82 NCSG Issue Forum
In-Reply-To: <CAH5sTh=QP41BEpU-UO-60+c-YrCL4mSeHoFrccMoMxWun-ky2A@mail.gmail.com>
References: <AC0E0ABA-2D6B-427A-98DF-17A593CBE7AE@icann.org>
 <CAH5sTh=YX1L+LvAk8XjSJMSPP1p2WM+RfUogvC84_bb=YaWUsQ@mail.gmail.com>
 <88C34156-A952-4A67-833B-0383FDB27D80@icann.org>
 <7372F653-6FD1-4BEF-BA98-3DD62B4BF30B@icann.org>
 <CAH5sTh=QP41BEpU-UO-60+c-YrCL4mSeHoFrccMoMxWun-ky2A@mail.gmail.com>
Message-ID: <7D107546-EDB9-4CC0-A544-5F933FA20720@icann.org>

Hello all,

Attached is the a draft ICANN82 schedule with the additional NCSG meetings with other groups, etc. I am still working with GAC and SSAC to see if there is a time slot that works for all.

Thanks!
Kind Regards,
Andrea


From: Rafik Dammak <rafik.dammak at gmail.com>
Date: Thursday, January 2, 2025 at 20:03
To: Andrea Glandon <andrea.glandon at icann.org>
Cc: ncsg-pc <ncsg-pc at lists.ncsg.is>, NCSG EC <ncsg-ec at lists.ncsg.is>
Subject: Re: [NCSG-EC] [Ext] Re: ICANN82 NCSG Issue Forum

Hi Andrea,

Thanks for the updated schedule. can we have also listed the other joint sessions there e.g. GAC, ALAC, SSAC for those confirmed.
FYI we also confirmed the usual breakfast meeting with Chris and Becky. We will also have a call with Chris this month, meeting invite to be sent soon.

Best,

Rafik
Le ven. 3 janv. 2025 ? 02:02, Andrea Glandon <andrea.glandon at icann.org<mailto:andrea.glandon at icann.org>> a ?crit :
Please find attached the most updated draft ICANN82 schedule.

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: Thursday, January 2, 2025 at 10:39
To: Rafik Dammak <rafik.dammak at gmail.com<mailto:rafik.dammak at gmail.com>>
Cc: ncsg-pc <ncsg-pc at lists.ncsg.is<mailto:ncsg-pc at lists.ncsg.is>>, NCSG EC <NCSG-ec at lists.ncsg.is<mailto:NCSG-ec at lists.ncsg.is>>
Subject: Re: [NCSG-EC] [Ext] Re: ICANN82 NCSG Issue Forum

Hello all.

Happy New Year!

I just wanted to confirm that I will be switching the NCSG Issue Forum to Tuesday, 13:15-14:30 local time.

Thanks!
Kind Regards,
Andrea


From: Rafik Dammak <rafik.dammak at gmail.com<mailto:rafik.dammak at gmail.com>>
Date: Friday, December 20, 2024 at 16:16
To: Andrea Glandon <andrea.glandon at icann.org<mailto:andrea.glandon at icann.org>>
Cc: NCSG EC <NCSG-ec at lists.ncsg.is<mailto:NCSG-ec at lists.ncsg.is>>, ncsg-pc <ncsg-pc at lists.ncsg.is<mailto:ncsg-pc at lists.ncsg.is>>
Subject: [Ext] Re: [NCSG-EC] ICANN82 NCSG Issue Forum

Hi Andrea,

I think the straightforward choice is to select Tuesday and that will link to other NCSG sessions in that day.

Best,

Rafik
On Sat, Dec 21, 2024, 01:19 Andrea Glandon via NCSG-EC <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>> wrote:
Hello all,

Currently the NCSG Issue Forum is scheduled on Sunday, 09 March, 1030-12. This is against a GNSO Working Session.

Here are some other possibilities for the session. I am also attaching a PDF with all sessions and sessions that NCSG will be participating in with other groups. I know it?s tiny, but you can enlarge to see better.

Tuesday, 11 March 1315-1430
Wednesday, 12 March 0900-1000, against Sub Pro IRT & PPSAI IRT
Wednesday, 12 March 1030-1200, against an RrSG session called RrSG Outreach: A registrant?s journey
Thursday, 13 March 0900-1000, against the Geopolitical Forum
Thursday, 13 March 1500-1600 against SubPro IRT

Once this session is set, then I can reach out to SSAC to try to get a session scheduled with them.

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



_______________________________________________
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!4H1MUJVGEpTfdM2OWbZfgTt5-FXJjW0Vr3xLIHfkkJznjufX_Z2TcJq00lTmeJoDVz-v64yNWxbRtYeFDA6gTRa4mK8FstM$>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250103/896ec708/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NCSG COPY ICANN82 GNSO Draft Schedule & Community requests - Draft tab.pdf
Type: application/pdf
Size: 55211 bytes
Desc: NCSG COPY ICANN82 GNSO Draft Schedule & Community requests - Draft tab.pdf
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250103/896ec708/attachment.pdf>

From wisdom.dk at gmail.com  Fri Jan  3 16:29:13 2025
From: wisdom.dk at gmail.com (Wisdom Donkor)
Date: Fri, 3 Jan 2025 14:29:13 +0000
Subject: [NCSG-PC] [NCSG-EC] [Ext] Re: ICANN82 NCSG Issue Forum
In-Reply-To: <7D107546-EDB9-4CC0-A544-5F933FA20720@icann.org>
References: <AC0E0ABA-2D6B-427A-98DF-17A593CBE7AE@icann.org>
 <CAH5sTh=YX1L+LvAk8XjSJMSPP1p2WM+RfUogvC84_bb=YaWUsQ@mail.gmail.com>
 <88C34156-A952-4A67-833B-0383FDB27D80@icann.org>
 <7372F653-6FD1-4BEF-BA98-3DD62B4BF30B@icann.org>
 <CAH5sTh=QP41BEpU-UO-60+c-YrCL4mSeHoFrccMoMxWun-ky2A@mail.gmail.com>
 <7D107546-EDB9-4CC0-A544-5F933FA20720@icann.org>
Message-ID: <CAAU+vPGPQfRsAwxTWE2iHLkReL4mR7756HTWDiRKrPfHG6wJ=Q@mail.gmail.com>

Thanks

On Fri, 3 Jan 2025, 2:17?pm Andrea Glandon, <andrea.glandon at icann.org>
wrote:

> Hello all,
>
>
>
> Attached is the a draft ICANN82 schedule with the additional NCSG meetings
> with other groups, etc. I am still working with GAC and SSAC to see if
> there is a time slot that works for all.
>
>
>
> Thanks!
>
> Kind Regards,
>
> Andrea
>
>
>
>
>
> *From: *Rafik Dammak <rafik.dammak at gmail.com>
> *Date: *Thursday, January 2, 2025 at 20:03
> *To: *Andrea Glandon <andrea.glandon at icann.org>
> *Cc: *ncsg-pc <ncsg-pc at lists.ncsg.is>, NCSG EC <ncsg-ec at lists.ncsg.is>
> *Subject: *Re: [NCSG-EC] [Ext] Re: ICANN82 NCSG Issue Forum
>
>
>
> Hi Andrea,
>
>
>
> Thanks for the updated schedule. can we have also listed the other joint
> sessions there e.g. GAC, ALAC, SSAC for those confirmed.
>
> FYI we also confirmed the usual breakfast meeting with Chris and Becky. We
> will also have a call with Chris this month, meeting invite to be sent soon.
>
>
>
> Best,
>
>
>
> Rafik
>
> Le ven. 3 janv. 2025 ? 02:02, Andrea Glandon <andrea.glandon at icann.org> a
> ?crit :
>
> Please find attached the most updated draft ICANN82 schedule.
>
>
>
> Kind Regards,
>
> Andrea
>
>
>
>
>
> *From: *NCSG-EC <ncsg-ec-bounces at lists.ncsg.is> on behalf of Andrea
> Glandon via NCSG-EC <NCSG-ec at lists.ncsg.is>
> *Reply-To: *Andrea Glandon <andrea.glandon at icann.org>
> *Date: *Thursday, January 2, 2025 at 10:39
> *To: *Rafik Dammak <rafik.dammak at gmail.com>
> *Cc: *ncsg-pc <ncsg-pc at lists.ncsg.is>, NCSG EC <NCSG-ec at lists.ncsg.is>
> *Subject: *Re: [NCSG-EC] [Ext] Re: ICANN82 NCSG Issue Forum
>
>
>
> Hello all.
>
>
>
> Happy New Year!
>
>
>
> I just wanted to confirm that I will be switching the NCSG Issue Forum to
> Tuesday, 13:15-14:30 local time.
>
>
>
> Thanks!
>
> Kind Regards,
>
> Andrea
>
>
>
>
>
> *From: *Rafik Dammak <rafik.dammak at gmail.com>
> *Date: *Friday, December 20, 2024 at 16:16
> *To: *Andrea Glandon <andrea.glandon at icann.org>
> *Cc: *NCSG EC <NCSG-ec at lists.ncsg.is>, ncsg-pc <ncsg-pc at lists.ncsg.is>
> *Subject: *[Ext] Re: [NCSG-EC] ICANN82 NCSG Issue Forum
>
>
>
> Hi Andrea,
>
>
>
> I think the straightforward choice is to select Tuesday and that will link
> to other NCSG sessions in that day.
>
>
>
> Best,
>
>
>
> Rafik
>
> On Sat, Dec 21, 2024, 01:19 Andrea Glandon via NCSG-EC <
> ncsg-ec at lists.ncsg.is> wrote:
>
> Hello all,
>
>
>
> Currently the NCSG Issue Forum is scheduled on Sunday, 09 March, 1030-12.
> This is against a GNSO Working Session.
>
>
>
> Here are some other possibilities for the session. I am also attaching a
> PDF with all sessions and sessions that NCSG will be participating in with
> other groups. I know it?s tiny, but you can enlarge to see better.
>
>
>
> Tuesday, 11 March 1315-1430
>
> Wednesday, 12 March 0900-1000, against Sub Pro IRT & PPSAI IRT
>
> Wednesday, 12 March 1030-1200, against an RrSG session called RrSG
> Outreach: A registrant?s journey
>
> Thursday, 13 March 0900-1000, against the Geopolitical Forum
>
> Thursday, 13 March 1500-1600 against SubPro IRT
>
>
>
> Once this session is set, then I can reach out to SSAC to try to get a
> session scheduled with them.
>
>
>
> Thank you!
>
> *Andrea Glandon*
>
> Policy Operations Sr. Coordinator
>
> Internet Corporation for Assigned Names and Numbers (ICANN)
>
> *Skype ID:*  acglandon76
>
>
>
>
>
>
>
> _______________________________________________
> NCSG-EC mailing list
> 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!4H1MUJVGEpTfdM2OWbZfgTt5-FXJjW0Vr3xLIHfkkJznjufX_Z2TcJq00lTmeJoDVz-v64yNWxbRtYeFDA6gTRa4mK8FstM$>
>
> _______________________________________________
> 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/20250103/4f7a164d/attachment.htm>

From andrea.glandon at icann.org  Fri Jan  3 18:12:36 2025
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Fri, 3 Jan 2025 16:12:36 +0000
Subject: [NCSG-PC] NCSG Breakfast meeting with Board members
Message-ID: <6f5b8886f8a446c18e093915fdd59883@icann.org>

A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 1740 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250103/0f618156/attachment.ics>

From andrea.glandon at icann.org  Fri Jan  3 18:13:14 2025
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Fri, 3 Jan 2025 16:13:14 +0000
Subject: [NCSG-PC] NCSG Breakfast meeting with Board members
Message-ID: <fc460e82cf8b4ceea94d657dcc8541f7@icann.org>

A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 1740 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250103/9e2219cf/attachment.ics>

From mesumbeslin at gmail.com  Fri Jan  3 18:41:35 2025
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Fri, 3 Jan 2025 19:41:35 +0300
Subject: [NCSG-PC] New NCUC representatives
In-Reply-To: <CAH5sThkDhCJAAEjt1J6V=tUMUb8VSEVuE3kLrLp_2y0kT4GkDA@mail.gmail.com>
References: <CAH5sThkDhCJAAEjt1J6V=tUMUb8VSEVuE3kLrLp_2y0kT4GkDA@mail.gmail.com>
Message-ID: <CAM8DdeWTiXPMTPP9HJBJ5LRvSs6h3EO3e93n3chc1UrJGsyK5A@mail.gmail.com>

Awesome news. Looking forward to working with them and thank you all former
PC appointees for your service and help in the last year.

Warmly,
Tomslin

On Fri, 3 Jan 2025, 03:46 Rafik Dammak, <rafik.dammak at gmail.com> wrote:

> Hi all,
>
> Wisdom shared the appointment of new NCUC representatives to NCSG PC
> :Michaela Nakayama Shapiro and Peterking Quaye. Andrea will add them to the
> list. Let's welcome them and thank the previous NCUC representatives for
> their service.
>
> Best regards,
>
> Rafik
> _______________________________________________
> 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/20250103/a4ec86ba/attachment.htm>

From mesumbeslin at gmail.com  Fri Jan  3 22:55:24 2025
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Fri, 3 Jan 2025 23:55:24 +0300
Subject: [NCSG-PC] PC meeting draft agenda
Message-ID: <CAM8DdeWGPd_tJ62WLHX4RWvm3DiTHSvuqgchG3OzipWanXdsXA@mail.gmail.com>

Hi all,

Here is a draft agenda for Monday's meeting. Please add to it.
https://docs.google.com/document/d/1ROtAj6CTteGDhX1D5c0Qu8PKN3lckkDn85Vk_gQ6OnU/edit?usp=sharing

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

From rafik.dammak at gmail.com  Sat Jan  4 10:39:54 2025
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Sat, 4 Jan 2025 17:39:54 +0900
Subject: [NCSG-PC] Fwd: [council] Call for Volunteers for SCCI | Please
 Respond by 6 January
In-Reply-To: <CAMeQZi11eFQWHt6BmJ8S_PNxnyp65AUTjOrSiFBGSLUTcBiZLQ@mail.gmail.com>
References: <698C84A1-F28A-4430-A052-E39612BAD9F5@icann.org>
 <CAM8DdeV4EFNFj3ADbcKkwxDzr2djA-M3o5ngi0BATgYA-1zmEQ@mail.gmail.com>
 <CAH5sThmMjU0fqwR2DG_RtgU+abvLMxAO4gDwNKvK50R6wEK5yQ@mail.gmail.com>
 <847580910.2455633.1733000189859@mail.yahoo.com>
 <CAMeQZi11eFQWHt6BmJ8S_PNxnyp65AUTjOrSiFBGSLUTcBiZLQ@mail.gmail.com>
Message-ID: <CAH5sThkv9o_sbDi2tqX=mENCZ-KJmv9tBtU5hJOLf=JgVkSx3Q@mail.gmail.com>

Hi all,

Can we confirm about the representative for SCCI. We got Manju and Juan
volunteering.

Best,

Rafik



On Wed, Dec 11, 2024, 17:05 ??? Manju Chen <manju at nii.org.tw> wrote:

> Hi,
>
> Happy to volunteer as the council rep for NCSG.
>
> Best,
> Manju
>
> On Sun, Dec 1, 2024 at 4:58?AM Juan Manuel Rojas via NCSG-PC <
> ncsg-pc at lists.ncsg.is> wrote:
>
>> 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 Colombia
>> NPOC Chair - NCSG/GNSO
>> M.Sc. Information Technology
>>
>> Registered Linux User No.*533108.*
>> http://www.jmanurojas.com
>>
>>
>> *Cel. +57 301 743 56 00Instagram: 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
>> <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
>>
>> _______________________________________________
>> 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/20250104/d9fc41e3/attachment.htm>

From mesumbeslin at gmail.com  Sat Jan  4 19:32:12 2025
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Sat, 4 Jan 2025 20:32:12 +0300
Subject: [NCSG-PC] Fwd: [council] Call for Volunteers for SCCI | Please
 Respond by 6 January
In-Reply-To: <CAH5sThkv9o_sbDi2tqX=mENCZ-KJmv9tBtU5hJOLf=JgVkSx3Q@mail.gmail.com>
References: <698C84A1-F28A-4430-A052-E39612BAD9F5@icann.org>
 <CAM8DdeV4EFNFj3ADbcKkwxDzr2djA-M3o5ngi0BATgYA-1zmEQ@mail.gmail.com>
 <CAH5sThmMjU0fqwR2DG_RtgU+abvLMxAO4gDwNKvK50R6wEK5yQ@mail.gmail.com>
 <847580910.2455633.1733000189859@mail.yahoo.com>
 <CAMeQZi11eFQWHt6BmJ8S_PNxnyp65AUTjOrSiFBGSLUTcBiZLQ@mail.gmail.com>
 <CAH5sThkv9o_sbDi2tqX=mENCZ-KJmv9tBtU5hJOLf=JgVkSx3Q@mail.gmail.com>
Message-ID: <CAM8DdeWWb0QA0P6Y1WBA4_ZsCxtUAHprbOkFRiG+qCqEYUPrBw@mail.gmail.com>

Hi all,

Catching up on emails. I am also checking with GNSO Secretariat on this.

Warmly,
Tomslin

On Sat, 4 Jan 2025, 11:40 Rafik Dammak, <rafik.dammak at gmail.com> wrote:

> Hi all,
>
> Can we confirm about the representative for SCCI. We got Manju and Juan
> volunteering.
>
> Best,
>
> Rafik
>
>
>
> On Wed, Dec 11, 2024, 17:05 ??? Manju Chen <manju at nii.org.tw> wrote:
>
>> Hi,
>>
>> Happy to volunteer as the council rep for NCSG.
>>
>> Best,
>> Manju
>>
>> On Sun, Dec 1, 2024 at 4:58?AM Juan Manuel Rojas via NCSG-PC <
>> ncsg-pc at lists.ncsg.is> wrote:
>>
>>> 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 Colombia
>>> NPOC Chair - NCSG/GNSO
>>> M.Sc. Information Technology
>>>
>>> Registered Linux User No.*533108.*
>>> http://www.jmanurojas.com
>>>
>>>
>>> *Cel. +57 301 743 56 00Instagram: 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
>>> <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
>>>
>>> _______________________________________________
>>> 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/20250104/7eb92b31/attachment.htm>

From mesumbeslin at gmail.com  Sun Jan  5 06:39:24 2025
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Sun, 5 Jan 2025 07:39:24 +0300
Subject: [NCSG-PC] [IMPORTANT] Volunteers Needed for Open Public Comments
Message-ID: <CAM8DdeXKe2Pzxqkx8JPGEaZ93=KkDrkU_ERLc694YS6SV8-B7Q@mail.gmail.com>

 Dear members,

ICANN org is seeking input on a number of open public comment proceedings.
Let me know if you'd like to volunteer on any one of them. The open public
comments are:

   1. *IANA 2030 Strategy: Draft PTI Strategic Plan covering 2025 to 2030 *
   - *Link*:
      https://www.icann.org/en/public-comment/proceeding/iana-2030-strategy-draft-pti-strategic-plan-covering-2025-to-2030-26-11-2024
   - *Deadline*: 25 days remaining. Closes on 29 January 2025
      - *Notes*: Pedro has noticed that in the section "3. Community
      Engagement", PTI seems to be focusing only on interacting with industry
      experts, but, if their objective is as stated ("Identify and address
      community needs for the IANA function, through enhancing existing
      relationships with the IANA customer community and improving
communication
      strategies with non-traditional stakeholders"), their focus
should include
      users who are not currently part of the ICANN ecosystem, and
this does not
      seem to be a part of the current strategy as written
   2. *Third Proceeding for Proposed Language for Draft Sections of Next
   Round AGB.*
      - *Link*:
      https://www.icann.org/en/public-comment/proceeding/third-proceeding-for-proposed-language-for-draft-sections-of-next-round-agb-19-12-2024
      - *Deadline*: 34 days remaining. Closes on 07 February 2025
      - *Notes: *
         - We already commented on the other proceedings, and this one,
         once again, seems to have at least a few problematic aspects.
         - However, this one is significantly larger, and it would be good
         to have not only newcomers working here, but also people who
have worked on
         similar topics in the past.
         - Some areas that require our attention are Privacy policy and the
         dispute (and objection) procedures.
      3. *Proposed Updates to the Operating Standards for Specific Reviews *
      - *Link*:
      https://www.icann.org/en/public-comment/proceeding/proposed-updates-to-the-operating-standards-for-specific-reviews-23-12-2024
      - *Deadline*: 37 days remaining. Closes on 10 February 2025
      - *Notes:* We submitted comments to the draft proposals back in 2019.
      The draft can be found here >
      https://docs.google.com/document/d/1pEKINvc1ltbvYKEDGtgZ1FHrvttZFI3mXBhZsTOg1G8/edit?tab=t.0
   4. *ICANN FY26?30 Operating & Financial Plan, ICANN/IANA FY26 Op Plans &
   Budgets*
      - *Link*:
      https://www.icann.org/en/public-comment/proceeding/icann-fy2630-operating-financial-plan-icanniana-fy26-op-plans-budgets-17-12-2024
      - *Deadline*: 41 days remaining. Closes on 14 February 2025.
      - *Notes*: This consultation is related to ICANN budget, operating
      planning and strategic plan. They are quite critical and impact the work
      and activities for coming years.
   5. Draft PTI FY26 Operating Plan and Budget
      - *Link*:
      https://www.icann.org/en/public-comment/proceeding/draft-pti-fy26-operating-plan-and-budget-17-12-2024
      - *Deadline*: 41 days remaining. Closes on 14 February 2025.
      - *Notes*: This consultation is related to PTI budget, operating
      planning and strategic plan. They are quite critical and impact the work
      and activities for coming years.

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


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

From julf at Julf.com  Mon Jan  6 10:57:03 2025
From: julf at Julf.com (Johan Helsingius)
Date: Mon, 6 Jan 2025 09:57:03 +0100
Subject: [NCSG-PC] Fwd: [council] Call for Volunteers for SCCI | Please
 Respond by 6 January
In-Reply-To: <CAH5sThkv9o_sbDi2tqX=mENCZ-KJmv9tBtU5hJOLf=JgVkSx3Q@mail.gmail.com>
References: <698C84A1-F28A-4430-A052-E39612BAD9F5@icann.org>
 <CAM8DdeV4EFNFj3ADbcKkwxDzr2djA-M3o5ngi0BATgYA-1zmEQ@mail.gmail.com>
 <CAH5sThmMjU0fqwR2DG_RtgU+abvLMxAO4gDwNKvK50R6wEK5yQ@mail.gmail.com>
 <847580910.2455633.1733000189859@mail.yahoo.com>
 <CAMeQZi11eFQWHt6BmJ8S_PNxnyp65AUTjOrSiFBGSLUTcBiZLQ@mail.gmail.com>
 <CAH5sThkv9o_sbDi2tqX=mENCZ-KJmv9tBtU5hJOLf=JgVkSx3Q@mail.gmail.com>
Message-ID: <d312e640-4a76-417c-b836-20e5fd7dc0e9@Julf.com>

Just checking, we are allowed 2+1 reps, right? If we need one more, I am
happy to volunteer.

	Julf


On 04/01/2025 09:39, Rafik Dammak wrote:
> Hi all,
> 
> Can we confirm about the representative for SCCI. We got Manju and Juan  
> volunteering.
> 
> Best,
> 
> Rafik
> 
> 
> 
> On Wed, Dec 11, 2024, 17:05 ??? Manju Chen <manju at nii.org.tw 
> <mailto:manju at nii.org.tw>> wrote:
> 
>     Hi,
> 
>     Happy to volunteer as the council rep for NCSG.
> 
>     Best,
>     Manju
> 
>     On Sun, Dec 1, 2024 at 4:58?AM Juan Manuel Rojas via NCSG-PC <ncsg-
>     pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>> wrote:
> 
>         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 Colombia
>         NPOC Chair - NCSG/GNSO
>         M.Sc. Information Technology
> 
>         Registered Linux User No.*533108.*
>         http://www.jmanurojas.com <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 <mailto: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 <mailto: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
>             <mailto: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 <mailto:council at gnso.icann.org>
>             <council at gnso.icann.org <mailto:council at gnso.icann.org>>
>             Cc: GNSO-Secs <gnso-secs at icann.org <mailto: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 theCouncil
>             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 theGNSO
>             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
>             thecharter <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 inArticle 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
>             thecharter <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 theGNSO?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____
>                   o One CPH Board seat #13 (1)____
>                   o One NCPH Board seat #14 (1)____
> 
>               * Nine Observers:____
>                   o One Council Chair (1)____
>                   o 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 <mailto: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 itscharter <https://
>             gnso.icann.org/sites/default/files/policy/2024/draft/scci-
>             charter-draft-update-13nov24-en.pdf>, as well as visiting
>             theCCOICI 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
>             <mailto:council at icann.org>
>             To unsubscribe send an email to council-leave at icann.org
>             <mailto: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 <https://
>             www.icann.org/privacy/policy>) and the website Terms of
>             Service (https://www.icann.org/privacy/tos <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 <mailto:NCSG-PC at lists.ncsg.is>
>             https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>             lists.ncsg.is/mailman/listinfo/ncsg-pc>
> 
>         _______________________________________________
>         NCSG-PC mailing list
>         NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>         https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>         lists.ncsg.is/mailman/listinfo/ncsg-pc>
>         _______________________________________________
>         NCSG-PC mailing list
>         NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>         https://lists.ncsg.is/mailman/listinfo/ncsg-pc <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 rafik.dammak at gmail.com  Mon Jan  6 11:28:59 2025
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Mon, 6 Jan 2025 18:28:59 +0900
Subject: [NCSG-PC] Fwd: [council] Call for Volunteers for SCCI | Please
 Respond by 6 January
In-Reply-To: <d312e640-4a76-417c-b836-20e5fd7dc0e9@Julf.com>
References: <698C84A1-F28A-4430-A052-E39612BAD9F5@icann.org>
 <CAM8DdeV4EFNFj3ADbcKkwxDzr2djA-M3o5ngi0BATgYA-1zmEQ@mail.gmail.com>
 <CAH5sThmMjU0fqwR2DG_RtgU+abvLMxAO4gDwNKvK50R6wEK5yQ@mail.gmail.com>
 <847580910.2455633.1733000189859@mail.yahoo.com>
 <CAMeQZi11eFQWHt6BmJ8S_PNxnyp65AUTjOrSiFBGSLUTcBiZLQ@mail.gmail.com>
 <CAH5sThkv9o_sbDi2tqX=mENCZ-KJmv9tBtU5hJOLf=JgVkSx3Q@mail.gmail.com>
 <d312e640-4a76-417c-b836-20e5fd7dc0e9@Julf.com>
Message-ID: <CAH5sThmUzaLU6Lmo3U7w3OekA4BdHZTJL9dytvAMTZHYMVRfoA@mail.gmail.com>

Yes it is one councillor  and 2 reps

Rafik

On Mon, Jan 6, 2025, 17:57 Johan Helsingius via NCSG-PC <
ncsg-pc at lists.ncsg.is> wrote:

> Just checking, we are allowed 2+1 reps, right? If we need one more, I am
> happy to volunteer.
>
>         Julf
>
>
> On 04/01/2025 09:39, Rafik Dammak wrote:
> > Hi all,
> >
> > Can we confirm about the representative for SCCI. We got Manju and Juan
> > volunteering.
> >
> > Best,
> >
> > Rafik
> >
> >
> >
> > On Wed, Dec 11, 2024, 17:05 ??? Manju Chen <manju at nii.org.tw
> > <mailto:manju at nii.org.tw>> wrote:
> >
> >     Hi,
> >
> >     Happy to volunteer as the council rep for NCSG.
> >
> >     Best,
> >     Manju
> >
> >     On Sun, Dec 1, 2024 at 4:58?AM Juan Manuel Rojas via NCSG-PC <ncsg-
> >     pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>> wrote:
> >
> >         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 Colombia
> >         NPOC Chair - NCSG/GNSO
> >         M.Sc. Information Technology
> >
> >         Registered Linux User No.*533108.*
> >         http://www.jmanurojas.com <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 <mailto: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 <mailto: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
> >             <mailto: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 <mailto:council at gnso.icann.org>
> >             <council at gnso.icann.org <mailto:council at gnso.icann.org>>
> >             Cc: GNSO-Secs <gnso-secs at icann.org <mailto:
> 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 theCouncil
> >             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 theGNSO
> >             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
> >             thecharter <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 inArticle 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
> >             thecharter <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 theGNSO?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____
> >                   o One CPH Board seat #13 (1)____
> >                   o One NCPH Board seat #14 (1)____
> >
> >               * Nine Observers:____
> >                   o One Council Chair (1)____
> >                   o 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 <mailto: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 itscharter <https://
> >             gnso.icann.org/sites/default/files/policy/2024/draft/scci-
> >             charter-draft-update-13nov24-en.pdf>, as well as visiting
> >             theCCOICI 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
> >             <mailto:council at icann.org>
> >             To unsubscribe send an email to council-leave at icann.org
> >             <mailto: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 <https://
> >             www.icann.org/privacy/policy>) and the website Terms of
> >             Service (https://www.icann.org/privacy/tos <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 <mailto:NCSG-PC at lists.ncsg.is>
> >             https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
> >             lists.ncsg.is/mailman/listinfo/ncsg-pc>
> >
> >         _______________________________________________
> >         NCSG-PC mailing list
> >         NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
> >         https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
> >         lists.ncsg.is/mailman/listinfo/ncsg-pc>
> >         _______________________________________________
> >         NCSG-PC mailing list
> >         NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
> >         https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
> >         lists.ncsg.is/mailman/listinfo/ncsg-pc>
> >
> >
> > _______________________________________________
> > NCSG-PC mailing list
> > NCSG-PC at lists.ncsg.is
> > https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250106/083bfc05/attachment.htm>

From julf at Julf.com  Mon Jan  6 12:36:06 2025
From: julf at Julf.com (Johan Helsingius)
Date: Mon, 6 Jan 2025 11:36:06 +0100
Subject: [NCSG-PC] Fwd: [council] Call for Volunteers for SCCI | Please
 Respond by 6 January
In-Reply-To: <CAH5sThmUzaLU6Lmo3U7w3OekA4BdHZTJL9dytvAMTZHYMVRfoA@mail.gmail.com>
References: <698C84A1-F28A-4430-A052-E39612BAD9F5@icann.org>
 <CAM8DdeV4EFNFj3ADbcKkwxDzr2djA-M3o5ngi0BATgYA-1zmEQ@mail.gmail.com>
 <CAH5sThmMjU0fqwR2DG_RtgU+abvLMxAO4gDwNKvK50R6wEK5yQ@mail.gmail.com>
 <847580910.2455633.1733000189859@mail.yahoo.com>
 <CAMeQZi11eFQWHt6BmJ8S_PNxnyp65AUTjOrSiFBGSLUTcBiZLQ@mail.gmail.com>
 <CAH5sThkv9o_sbDi2tqX=mENCZ-KJmv9tBtU5hJOLf=JgVkSx3Q@mail.gmail.com>
 <d312e640-4a76-417c-b836-20e5fd7dc0e9@Julf.com>
 <CAH5sThmUzaLU6Lmo3U7w3OekA4BdHZTJL9dytvAMTZHYMVRfoA@mail.gmail.com>
Message-ID: <ce33c08b-1d58-492a-833b-3ee04b98ccad@Julf.com>

I assume the reps can be, but don't have to be, councilors?

	Julf

On 06/01/2025 10:28, Rafik Dammak wrote:
> Yes it is one councillor? and 2 reps
> 
> Rafik
> 
> On Mon, Jan 6, 2025, 17:57 Johan Helsingius via NCSG-PC <ncsg- 
> pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>> wrote:
> 
>     Just checking, we are allowed 2+1 reps, right? If we need one more, I am
>     happy to volunteer.
> 
>      ? ? ? ? Julf
> 
> 
>     On 04/01/2025 09:39, Rafik Dammak wrote:
>      > Hi all,
>      >
>      > Can we confirm about the representative for SCCI. We got Manju
>     and Juan
>      > volunteering.
>      >
>      > Best,
>      >
>      > Rafik
>      >
>      >
>      >
>      > On Wed, Dec 11, 2024, 17:05 ??? Manju Chen <manju at nii.org.tw
>     <mailto:manju at nii.org.tw>
>      > <mailto:manju at nii.org.tw <mailto:manju at nii.org.tw>>> wrote:
>      >
>      >? ? ?Hi,
>      >
>      >? ? ?Happy to volunteer as the council rep for NCSG.
>      >
>      >? ? ?Best,
>      >? ? ?Manju
>      >
>      >? ? ?On Sun, Dec 1, 2024 at 4:58?AM Juan Manuel Rojas via NCSG-PC
>     <ncsg-
>      > pc at lists.ncsg.is <mailto:pc at lists.ncsg.is> <mailto:ncsg-
>     pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>>> wrote:
>      >
>      >? ? ? ? ?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 Colombia
>      >? ? ? ? ?NPOC Chair - NCSG/GNSO
>      >? ? ? ? ?M.Sc. Information Technology
>      >
>      >? ? ? ? ?Registered Linux User No.*533108.*
>      > http://www.jmanurojas.com <http://www.jmanurojas.com> <http://
>     www.jmanurojas.com <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
>     <mailto:rafik.dammak at gmail.com> <mailto:rafik.dammak at gmail.com
>     <mailto: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 <mailto:mesumbeslin at gmail.com>
>     <mailto:mesumbeslin at gmail.com <mailto: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
>     <mailto:council at icann.org>
>      >? ? ? ? ? ? ?<mailto:council at icann.org <mailto: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
>     <mailto:council at gnso.icann.org> <mailto:council at gnso.icann.org
>     <mailto:council at gnso.icann.org>>
>      >? ? ? ? ? ? ?<council at gnso.icann.org
>     <mailto:council at gnso.icann.org> <mailto:council at gnso.icann.org
>     <mailto:council at gnso.icann.org>>>
>      >? ? ? ? ? ? ?Cc: GNSO-Secs <gnso-secs at icann.org <mailto:gnso-
>     secs at icann.org> <mailto:gnso-secs at icann.org <mailto: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 theCouncil
>      >? ? ? ? ? ? ?Committee for Overseeing and Implementing Continuous
>      >? ? ? ? ? ? ?Improvement (CCOICI) Framework <https://
>     gnso.icann.org/ <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 theGNSO
>      >? ? ? ? ? ? ?Council?s adoption of the charter <https://
>     gnso.icann.org/ <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
>      >? ? ? ? ? ? ?thecharter <https://gnso.icann.org/sites/default/
>     files/ <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 inArticle 4.4. of the ICANN Bylaws <https://
>      > www.icann.org/resources/pages/governance/bylaws- <http://
>     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
>      >? ? ? ? ? ? ?thecharter <https://gnso.icann.org/sites/default/
>     files/ <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 theGNSO?s Program Management Tool (PMT) Suite
>      >? ? ? ? ? ? ?<https://community.icann.org/pages/viewpage.action
>     <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____
>      >? ? ? ? ? ? ? ? ? ?o One CPH Board seat #13 (1)____
>      >? ? ? ? ? ? ? ? ? ?o One NCPH Board seat #14 (1)____
>      >
>      >? ? ? ? ? ? ? ?* Nine Observers:____
>      >? ? ? ? ? ? ? ? ? ?o One Council Chair (1)____
>      >? ? ? ? ? ? ? ? ? ?o 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 <mailto:secs at icann.org> <mailto:gnso-
>     secs at icann.org <mailto: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 itscharter
>     <https://
>      > gnso.icann.org/sites/default/files/policy/2024/draft/scci-
>     <http://gnso.icann.org/sites/default/files/policy/2024/draft/scci->
>      >? ? ? ? ? ? ?charter-draft-update-13nov24-en.pdf>, as well as visiting
>      >? ? ? ? ? ? ?theCCOICI wiki page <https://community.icann.org/
>     display/ <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
>     <mailto:council at icann.org>
>      >? ? ? ? ? ? ?<mailto:council at icann.org <mailto:council at icann.org>>
>      >? ? ? ? ? ? ?To unsubscribe send an email to council-
>     leave at icann.org <mailto:council-leave at icann.org>
>      >? ? ? ? ? ? ?<mailto:council-leave at icann.org <mailto: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
>     <https://www.icann.org/privacy/policy> <https://
>      > www.icann.org/privacy/policy <http://www.icann.org/privacy/
>     policy>>) and the website Terms of
>      >? ? ? ? ? ? ?Service (https://www.icann.org/privacy/tos <https://
>     www.icann.org/privacy/tos> <https://
>      > www.icann.org/privacy/tos <http://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 <mailto:NCSG-PC at lists.ncsg.is>
>     <mailto:NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>>
>      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>     lists.ncsg.is/mailman/listinfo/ncsg-pc> <https://
>      > lists.ncsg.is/mailman/listinfo/ncsg-pc <http://lists.ncsg.is/
>     mailman/listinfo/ncsg-pc>>
>      >
>      >? ? ? ? ?_______________________________________________
>      >? ? ? ? ?NCSG-PC mailing list
>      > NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>     <mailto:NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>>
>      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>     lists.ncsg.is/mailman/listinfo/ncsg-pc> <https://
>      > lists.ncsg.is/mailman/listinfo/ncsg-pc <http://lists.ncsg.is/
>     mailman/listinfo/ncsg-pc>>
>      >? ? ? ? ?_______________________________________________
>      >? ? ? ? ?NCSG-PC mailing list
>      > NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>     <mailto:NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>>
>      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>     lists.ncsg.is/mailman/listinfo/ncsg-pc> <https://
>      > lists.ncsg.is/mailman/listinfo/ncsg-pc <http://lists.ncsg.is/
>     mailman/listinfo/ncsg-pc>>
>      >
>      >
>      > _______________________________________________
>      > NCSG-PC mailing list
>      > NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>     lists.ncsg.is/mailman/listinfo/ncsg-pc>
> 
>     _______________________________________________
>     NCSG-PC mailing list
>     NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>     https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>     lists.ncsg.is/mailman/listinfo/ncsg-pc>
> 



From michaela.shapiro at article19.org  Mon Jan  6 18:36:02 2025
From: michaela.shapiro at article19.org (Michaela Nakayama Shapiro)
Date: Mon, 6 Jan 2025 16:36:02 +0000
Subject: [NCSG-PC] New NCUC representatives
In-Reply-To: <CAM8DdeWTiXPMTPP9HJBJ5LRvSs6h3EO3e93n3chc1UrJGsyK5A@mail.gmail.com>
References: <CAH5sThkDhCJAAEjt1J6V=tUMUb8VSEVuE3kLrLp_2y0kT4GkDA@mail.gmail.com>
 <CAM8DdeWTiXPMTPP9HJBJ5LRvSs6h3EO3e93n3chc1UrJGsyK5A@mail.gmail.com>
 <03d95705-f733-4d96-bfa3-6ea2374cd25b.05b495a4-acd5-4405-a5fb-09b87eaaeafb.dc4433b6-7efb-4e81-9c3e-3c6f7e9c87cf@emailsignatures365.codetwo.com>
Message-ID: <CWXP265MB0775A67000231B477BA6534194102@CWXP265MB0775.GBRP265.PROD.OUTLOOK.COM>

INTERNAL


INTERNAL

Dear all,

Looking forward to working with Peterking and with you all!

Best,

Michaela

Michaela Nakayama Shapiro (she/her/hers)
Programme Officer - Censorship
[Logo.png]<https://www.article19.org>   Defending freedom of expression
and information
www.article19.org<https://www.article19.org>            Subscribe to our Newsletter<https://www.article19.org/ie-sign-up/>      [cid:newsletter_02744340-c607-4374-8a37-11b8b216096d.png] <https://www.article19.org/ie-sign-up>
Follow us
[Bluesky1x.png]<https://bsky.app/profile/article19.bsky.social>         [cid:facebook_2853baa0-f060-42e6-b448-6a8788c1b5dd.png] <https://www.facebook.com/article19org/>                [cid:youtube_ffe95af1-d962-4acd-ab59-4eb4ea07466e.png] <https://www.youtube.com/channel/UCDB6E_x0xRSfF62b872n9YQ>               [cid:linkedin_199dc89c-14aa-41cd-b2a7-37b8ae8d667d.png] <https://www.linkedin.com/company/article19>            [cid:instagram_05fbcc72-6df2-442b-8c34-146d0e9d8c41.png] <https://www.instagram.com/article19org/>              [cid:x_d21e0607-da5a-44a7-80c7-e2d86bc18a92.png] <https://twitter.com/intent/follow?screen_name=article19org>
[women-journalists-banner.jpeg]<https://www.article19.org/equally-safe/?mtm_campaign=Clicks%20on%20email%20signature%20banner>
From: NCSG-PC <ncsg-pc-bounces at lists.ncsg.is> on behalf of Tomslin Samme-Nlar <mesumbeslin at gmail.com>
Date: Friday, 3 January 2025 at 11:41
To: Rafik Dammak <rafik.dammak at gmail.com>
Cc: ncsg-pc <ncsg-pc at lists.ncsg.is>
Subject: Re: [NCSG-PC] New NCUC representatives
Awesome news. Looking forward to working with them and thank you all former PC appointees for your service and help in the last year.

Warmly,
Tomslin

On Fri, 3 Jan 2025, 03:46 Rafik Dammak, <rafik.dammak at gmail.com<mailto:rafik.dammak at gmail.com>> wrote:
Hi all,

Wisdom shared the appointment of new NCUC representatives to NCSG PC :Michaela Nakayama Shapiro and Peterking Quaye. Andrea will add them to the list. Let's welcome them and thank the previous NCUC representatives for their service.

Best regards,

Rafik
_______________________________________________
NCSG-PC mailing list
NCSG-PC at lists.ncsg.is<mailto: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/20250106/c83947a3/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo_1c766458-35ee-431a-9a22-e00b47cd2091.png
Type: image/png
Size: 6889 bytes
Desc: logo_1c766458-35ee-431a-9a22-e00b47cd2091.png
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250106/c83947a3/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: newsletter_02744340-c607-4374-8a37-11b8b216096d.png
Type: image/png
Size: 379 bytes
Desc: newsletter_02744340-c607-4374-8a37-11b8b216096d.png
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250106/c83947a3/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bluesky1x_864ef831-9476-4116-88b8-2a3410741630.png
Type: image/png
Size: 788 bytes
Desc: bluesky1x_864ef831-9476-4116-88b8-2a3410741630.png
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250106/c83947a3/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: facebook_2853baa0-f060-42e6-b448-6a8788c1b5dd.png
Type: image/png
Size: 670 bytes
Desc: facebook_2853baa0-f060-42e6-b448-6a8788c1b5dd.png
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250106/c83947a3/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: youtube_ffe95af1-d962-4acd-ab59-4eb4ea07466e.png
Type: image/png
Size: 678 bytes
Desc: youtube_ffe95af1-d962-4acd-ab59-4eb4ea07466e.png
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250106/c83947a3/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: linkedin_199dc89c-14aa-41cd-b2a7-37b8ae8d667d.png
Type: image/png
Size: 720 bytes
Desc: linkedin_199dc89c-14aa-41cd-b2a7-37b8ae8d667d.png
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250106/c83947a3/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: instagram_05fbcc72-6df2-442b-8c34-146d0e9d8c41.png
Type: image/png
Size: 840 bytes
Desc: instagram_05fbcc72-6df2-442b-8c34-146d0e9d8c41.png
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250106/c83947a3/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: x_d21e0607-da5a-44a7-80c7-e2d86bc18a92.png
Type: image/png
Size: 895 bytes
Desc: x_d21e0607-da5a-44a7-80c7-e2d86bc18a92.png
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250106/c83947a3/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: women-journalists-banner_b1cece5c-a86d-452f-b9f8-9e72943680f6.jpeg
Type: image/jpeg
Size: 15471 bytes
Desc: women-journalists-banner_b1cece5c-a86d-452f-b9f8-9e72943680f6.jpeg
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250106/c83947a3/attachment.jpeg>

From PolicyCalendar at icann.org  Mon Jan  6 18:42:22 2025
From: PolicyCalendar at icann.org (ICANN Policy Calendar)
Date: Mon, 6 Jan 2025 16:42:22 +0000
Subject: [NCSG-PC] TENTATIVE-Meeting with Chris Buckridge
Message-ID: <1ddf882e131b4c629d96cb0b34157672@icann.org>

Tentative meeting with Chris Buckridge. More information to follow.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250106/940a27b7/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 1773 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250106/940a27b7/attachment.ics>

From andrea.glandon at icann.org  Mon Jan  6 20:12:00 2025
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Mon, 6 Jan 2025 18:12:00 +0000
Subject: [NCSG-PC] PLEASE READ: ICANN82 Sessions with GAC, SSAC
Message-ID: <94F36738-3AC7-4353-A6E6-8F390A7F33AA@icann.org>

Hello all,

After looking at the schedule below are the slots that are open with no noncommercial sessions, although as you will see there are conflicts. Would you like me to send these days/times to GAC & SSAC and see if they are available for any of them? We will also need to find a slot for an NCSG EC Sign-up room, unless you want to do it over lunch one of the days.


Saturday, 16:30-17:30 Conflicts with SCCI
Wednesday, 09:00-10:00 Conflicts with SSAC & Board, but could be meeting with GAC if they are available. Also conflicts with Sub Pro & PPSAI IRT.
Wednesday, 1030-12:00 Conflicts with RrSG Outreach: A Registrant?s Journey
Wednesday, 16:30-17:30 Conflicts with RSRS Standing Committee
Thursday, 09:00-10:00 Conflicts with Geopolitical Forum
Thursday, 15:00-16:00 Conflicts with SubPro IRT

Thanks!
Kind Regards,
Andrea


From: NCSG-EC <ncsg-ec-bounces at lists.ncsg.is> on behalf of Andrea Glandon via NCSG-EC <ncsg-ec at lists.ncsg.is>
Reply-To: Andrea Glandon <andrea.glandon at icann.org>
Date: Friday, January 3, 2025 at 08:18
To: ncsg-pc <ncsg-pc at lists.ncsg.is>, NCSG EC <ncsg-ec at lists.ncsg.is>
Subject: Re: [NCSG-EC] [Ext] Re: ICANN82 NCSG Issue Forum

Hello all,

Attached is the a draft ICANN82 schedule with the additional NCSG meetings with other groups, etc. I am still working with GAC and SSAC to see if there is a time slot that works for all.

Thanks!
Kind Regards,
Andrea


From: Rafik Dammak <rafik.dammak at gmail.com>
Date: Thursday, January 2, 2025 at 20:03
To: Andrea Glandon <andrea.glandon at icann.org>
Cc: ncsg-pc <ncsg-pc at lists.ncsg.is>, NCSG EC <ncsg-ec at lists.ncsg.is>
Subject: Re: [NCSG-EC] [Ext] Re: ICANN82 NCSG Issue Forum

Hi Andrea,

Thanks for the updated schedule. can we have also listed the other joint sessions there e.g. GAC, ALAC, SSAC for those confirmed.
FYI we also confirmed the usual breakfast meeting with Chris and Becky. We will also have a call with Chris this month, meeting invite to be sent soon.

Best,

Rafik
Le ven. 3 janv. 2025 ? 02:02, Andrea Glandon <andrea.glandon at icann.org<mailto:andrea.glandon at icann.org>> a ?crit :
Please find attached the most updated draft ICANN82 schedule.

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: Thursday, January 2, 2025 at 10:39
To: Rafik Dammak <rafik.dammak at gmail.com<mailto:rafik.dammak at gmail.com>>
Cc: ncsg-pc <ncsg-pc at lists.ncsg.is<mailto:ncsg-pc at lists.ncsg.is>>, NCSG EC <NCSG-ec at lists.ncsg.is<mailto:NCSG-ec at lists.ncsg.is>>
Subject: Re: [NCSG-EC] [Ext] Re: ICANN82 NCSG Issue Forum

Hello all.

Happy New Year!

I just wanted to confirm that I will be switching the NCSG Issue Forum to Tuesday, 13:15-14:30 local time.

Thanks!
Kind Regards,
Andrea


From: Rafik Dammak <rafik.dammak at gmail.com<mailto:rafik.dammak at gmail.com>>
Date: Friday, December 20, 2024 at 16:16
To: Andrea Glandon <andrea.glandon at icann.org<mailto:andrea.glandon at icann.org>>
Cc: NCSG EC <NCSG-ec at lists.ncsg.is<mailto:NCSG-ec at lists.ncsg.is>>, ncsg-pc <ncsg-pc at lists.ncsg.is<mailto:ncsg-pc at lists.ncsg.is>>
Subject: [Ext] Re: [NCSG-EC] ICANN82 NCSG Issue Forum

Hi Andrea,

I think the straightforward choice is to select Tuesday and that will link to other NCSG sessions in that day.

Best,

Rafik
On Sat, Dec 21, 2024, 01:19 Andrea Glandon via NCSG-EC <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>> wrote:
Hello all,

Currently the NCSG Issue Forum is scheduled on Sunday, 09 March, 1030-12. This is against a GNSO Working Session.

Here are some other possibilities for the session. I am also attaching a PDF with all sessions and sessions that NCSG will be participating in with other groups. I know it?s tiny, but you can enlarge to see better.

Tuesday, 11 March 1315-1430
Wednesday, 12 March 0900-1000, against Sub Pro IRT & PPSAI IRT
Wednesday, 12 March 1030-1200, against an RrSG session called RrSG Outreach: A registrant?s journey
Thursday, 13 March 0900-1000, against the Geopolitical Forum
Thursday, 13 March 1500-1600 against SubPro IRT

Once this session is set, then I can reach out to SSAC to try to get a session scheduled with them.

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



_______________________________________________
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!4H1MUJVGEpTfdM2OWbZfgTt5-FXJjW0Vr3xLIHfkkJznjufX_Z2TcJq00lTmeJoDVz-v64yNWxbRtYeFDA6gTRa4mK8FstM$>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250106/c58b8bd9/attachment.htm>

From rafik.dammak at gmail.com  Tue Jan  7 02:10:12 2025
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Tue, 7 Jan 2025 09:10:12 +0900
Subject: [NCSG-PC] [NCSG-EC] PLEASE READ: ICANN82 Sessions with GAC, SSAC
In-Reply-To: <94F36738-3AC7-4353-A6E6-8F390A7F33AA@icann.org>
References: <94F36738-3AC7-4353-A6E6-8F390A7F33AA@icann.org>
Message-ID: <CAH5sThni-su9O_9xHXmamqzKiCB7m-4xK96C==WZKOg5KFC7Qw@mail.gmail.com>

Hi Andrea,

My simple criteria would be to avoid clashing sessions where we can
intervene or have a substantial number of WG members participating e.g.
SSAC-board session we will be in listening only mode but it is also
clashing against 2 IRTs.
so wednesday 10:30-12:00  would be fine since it is an outreach session.
possibly Thursday 9:00-10:00 as this session is usually a speaking panel if
I am not mistaking and not so much interaction with the audience.
there is no optimal option and we need to accept the tradeoff. Do we value
the possibility to interact with GAC and SSAC and reach them out or having
FOMO for some sessions?

Best,

Rafik

Le mar. 7 janv. 2025 ? 03:12, Andrea Glandon via NCSG-EC <
ncsg-ec at lists.ncsg.is> a ?crit :

> Hello all,
>
>
>
> After looking at the schedule below are the slots that are open with no
> noncommercial sessions, although as you will see there are conflicts. Would
> you like me to send these days/times to GAC & SSAC and see if they are
> available for any of them? We will also need to find a slot for an NCSG EC
> Sign-up room, unless you want to do it over lunch one of the days.
>
>
>
>
>
> Saturday, 16:30-17:30 Conflicts with SCCI
>
> Wednesday, 09:00-10:00 Conflicts with SSAC & Board, but could be meeting
> with GAC if they are available. Also conflicts with Sub Pro & PPSAI IRT.
>
> Wednesday, 1030-12:00 Conflicts with RrSG Outreach: A Registrant?s Journey
>
> Wednesday, 16:30-17:30 Conflicts with RSRS Standing Committee
>
> Thursday, 09:00-10:00 Conflicts with Geopolitical Forum
>
> Thursday, 15:00-16:00 Conflicts with SubPro IRT
>
>
>
> Thanks!
>
> Kind Regards,
>
> Andrea
>
>
>
>
>
> *From: *NCSG-EC <ncsg-ec-bounces at lists.ncsg.is> on behalf of Andrea
> Glandon via NCSG-EC <ncsg-ec at lists.ncsg.is>
> *Reply-To: *Andrea Glandon <andrea.glandon at icann.org>
> *Date: *Friday, January 3, 2025 at 08:18
> *To: *ncsg-pc <ncsg-pc at lists.ncsg.is>, NCSG EC <ncsg-ec at lists.ncsg.is>
> *Subject: *Re: [NCSG-EC] [Ext] Re: ICANN82 NCSG Issue Forum
>
>
>
> Hello all,
>
>
>
> Attached is the a draft ICANN82 schedule with the additional NCSG meetings
> with other groups, etc. I am still working with GAC and SSAC to see if
> there is a time slot that works for all.
>
>
>
> Thanks!
>
> Kind Regards,
>
> Andrea
>
>
>
>
>
> *From: *Rafik Dammak <rafik.dammak at gmail.com>
> *Date: *Thursday, January 2, 2025 at 20:03
> *To: *Andrea Glandon <andrea.glandon at icann.org>
> *Cc: *ncsg-pc <ncsg-pc at lists.ncsg.is>, NCSG EC <ncsg-ec at lists.ncsg.is>
> *Subject: *Re: [NCSG-EC] [Ext] Re: ICANN82 NCSG Issue Forum
>
>
>
> Hi Andrea,
>
>
>
> Thanks for the updated schedule. can we have also listed the other joint
> sessions there e.g. GAC, ALAC, SSAC for those confirmed.
>
> FYI we also confirmed the usual breakfast meeting with Chris and Becky. We
> will also have a call with Chris this month, meeting invite to be sent soon.
>
>
>
> Best,
>
>
>
> Rafik
>
> Le ven. 3 janv. 2025 ? 02:02, Andrea Glandon <andrea.glandon at icann.org> a
> ?crit :
>
> Please find attached the most updated draft ICANN82 schedule.
>
>
>
> Kind Regards,
>
> Andrea
>
>
>
>
>
> *From: *NCSG-EC <ncsg-ec-bounces at lists.ncsg.is> on behalf of Andrea
> Glandon via NCSG-EC <NCSG-ec at lists.ncsg.is>
> *Reply-To: *Andrea Glandon <andrea.glandon at icann.org>
> *Date: *Thursday, January 2, 2025 at 10:39
> *To: *Rafik Dammak <rafik.dammak at gmail.com>
> *Cc: *ncsg-pc <ncsg-pc at lists.ncsg.is>, NCSG EC <NCSG-ec at lists.ncsg.is>
> *Subject: *Re: [NCSG-EC] [Ext] Re: ICANN82 NCSG Issue Forum
>
>
>
> Hello all.
>
>
>
> Happy New Year!
>
>
>
> I just wanted to confirm that I will be switching the NCSG Issue Forum to
> Tuesday, 13:15-14:30 local time.
>
>
>
> Thanks!
>
> Kind Regards,
>
> Andrea
>
>
>
>
>
> *From: *Rafik Dammak <rafik.dammak at gmail.com>
> *Date: *Friday, December 20, 2024 at 16:16
> *To: *Andrea Glandon <andrea.glandon at icann.org>
> *Cc: *NCSG EC <NCSG-ec at lists.ncsg.is>, ncsg-pc <ncsg-pc at lists.ncsg.is>
> *Subject: *[Ext] Re: [NCSG-EC] ICANN82 NCSG Issue Forum
>
>
>
> Hi Andrea,
>
>
>
> I think the straightforward choice is to select Tuesday and that will link
> to other NCSG sessions in that day.
>
>
>
> Best,
>
>
>
> Rafik
>
> On Sat, Dec 21, 2024, 01:19 Andrea Glandon via NCSG-EC <
> ncsg-ec at lists.ncsg.is> wrote:
>
> Hello all,
>
>
>
> Currently the NCSG Issue Forum is scheduled on Sunday, 09 March, 1030-12.
> This is against a GNSO Working Session.
>
>
>
> Here are some other possibilities for the session. I am also attaching a
> PDF with all sessions and sessions that NCSG will be participating in with
> other groups. I know it?s tiny, but you can enlarge to see better.
>
>
>
> Tuesday, 11 March 1315-1430
>
> Wednesday, 12 March 0900-1000, against Sub Pro IRT & PPSAI IRT
>
> Wednesday, 12 March 1030-1200, against an RrSG session called RrSG
> Outreach: A registrant?s journey
>
> Thursday, 13 March 0900-1000, against the Geopolitical Forum
>
> Thursday, 13 March 1500-1600 against SubPro IRT
>
>
>
> Once this session is set, then I can reach out to SSAC to try to get a
> session scheduled with them.
>
>
>
> Thank you!
>
> *Andrea Glandon*
>
> Policy Operations Sr. Coordinator
>
> Internet Corporation for Assigned Names and Numbers (ICANN)
>
> *Skype ID:*  acglandon76
>
>
>
>
>
>
>
> _______________________________________________
> NCSG-EC mailing list
> 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!4H1MUJVGEpTfdM2OWbZfgTt5-FXJjW0Vr3xLIHfkkJznjufX_Z2TcJq00lTmeJoDVz-v64yNWxbRtYeFDA6gTRa4mK8FstM$>
>
> _______________________________________________
> 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/20250107/f575264e/attachment.htm>

From manju at nii.org.tw  Tue Jan  7 03:51:22 2025
From: manju at nii.org.tw (=?UTF-8?B?6Zmz5pu86Iy5IE1hbmp1IENoZW4=?=)
Date: Tue, 7 Jan 2025 09:51:22 +0800
Subject: [NCSG-PC] Fwd: [council] Call for Volunteers for SCCI | Please
 Respond by 6 January
In-Reply-To: <ce33c08b-1d58-492a-833b-3ee04b98ccad@Julf.com>
References: <698C84A1-F28A-4430-A052-E39612BAD9F5@icann.org>
 <CAM8DdeV4EFNFj3ADbcKkwxDzr2djA-M3o5ngi0BATgYA-1zmEQ@mail.gmail.com>
 <CAH5sThmMjU0fqwR2DG_RtgU+abvLMxAO4gDwNKvK50R6wEK5yQ@mail.gmail.com>
 <847580910.2455633.1733000189859@mail.yahoo.com>
 <CAMeQZi11eFQWHt6BmJ8S_PNxnyp65AUTjOrSiFBGSLUTcBiZLQ@mail.gmail.com>
 <CAH5sThkv9o_sbDi2tqX=mENCZ-KJmv9tBtU5hJOLf=JgVkSx3Q@mail.gmail.com>
 <d312e640-4a76-417c-b836-20e5fd7dc0e9@Julf.com>
 <CAH5sThmUzaLU6Lmo3U7w3OekA4BdHZTJL9dytvAMTZHYMVRfoA@mail.gmail.com>
 <ce33c08b-1d58-492a-833b-3ee04b98ccad@Julf.com>
Message-ID: <CAMeQZi0u2am4U-YaDW0KBAvBNgs-vbSNeZk_LfaWHjLqhp-=+Q@mail.gmail.com>

Correct, Julf, as long as we have one council rep it's fine. And it's not
against the rules to have another NCSG rep that happens to also be a
councilor.

Best,
Manju


On Mon, Jan 6, 2025 at 6:36?PM Johan Helsingius via NCSG-PC <
ncsg-pc at lists.ncsg.is> wrote:

> I assume the reps can be, but don't have to be, councilors?
>
>         Julf
>
> On 06/01/2025 10:28, Rafik Dammak wrote:
> > Yes it is one councillor  and 2 reps
> >
> > Rafik
> >
> > On Mon, Jan 6, 2025, 17:57 Johan Helsingius via NCSG-PC <ncsg-
> > pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>> wrote:
> >
> >     Just checking, we are allowed 2+1 reps, right? If we need one more,
> I am
> >     happy to volunteer.
> >
> >              Julf
> >
> >
> >     On 04/01/2025 09:39, Rafik Dammak wrote:
> >      > Hi all,
> >      >
> >      > Can we confirm about the representative for SCCI. We got Manju
> >     and Juan
> >      > volunteering.
> >      >
> >      > Best,
> >      >
> >      > Rafik
> >      >
> >      >
> >      >
> >      > On Wed, Dec 11, 2024, 17:05 ??? Manju Chen <manju at nii.org.tw
> >     <mailto:manju at nii.org.tw>
> >      > <mailto:manju at nii.org.tw <mailto:manju at nii.org.tw>>> wrote:
> >      >
> >      >     Hi,
> >      >
> >      >     Happy to volunteer as the council rep for NCSG.
> >      >
> >      >     Best,
> >      >     Manju
> >      >
> >      >     On Sun, Dec 1, 2024 at 4:58?AM Juan Manuel Rojas via NCSG-PC
> >     <ncsg-
> >      > pc at lists.ncsg.is <mailto:pc at lists.ncsg.is> <mailto:ncsg-
> >     pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>>> wrote:
> >      >
> >      >         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 Colombia
> >      >         NPOC Chair - NCSG/GNSO
> >      >         M.Sc. Information Technology
> >      >
> >      >         Registered Linux User No.*533108.*
> >      > http://www.jmanurojas.com <http://www.jmanurojas.com> <http://
> >     www.jmanurojas.com <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
> >     <mailto:rafik.dammak at gmail.com> <mailto:rafik.dammak at gmail.com
> >     <mailto: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 <mailto:mesumbeslin at gmail.com>
> >     <mailto:mesumbeslin at gmail.com <mailto: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
> >     <mailto:council at icann.org>
> >      >             <mailto:council at icann.org <mailto: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
> >     <mailto:council at gnso.icann.org> <mailto:council at gnso.icann.org
> >     <mailto:council at gnso.icann.org>>
> >      >             <council at gnso.icann.org
> >     <mailto:council at gnso.icann.org> <mailto:council at gnso.icann.org
> >     <mailto:council at gnso.icann.org>>>
> >      >             Cc: GNSO-Secs <gnso-secs at icann.org <mailto:gnso-
> >     secs at icann.org> <mailto:gnso-secs at icann.org <mailto: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 theCouncil
> >      >             Committee for Overseeing and Implementing Continuous
> >      >             Improvement (CCOICI) Framework <https://
> >     gnso.icann.org/ <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 theGNSO
> >      >             Council?s adoption of the charter <https://
> >     gnso.icann.org/ <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
> >      >             thecharter <https://gnso.icann.org/sites/default/
> >     files/ <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 inArticle 4.4. of the ICANN Bylaws <https://
> >      > www.icann.org/resources/pages/governance/bylaws- <http://
> >     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
> >      >             thecharter <https://gnso.icann.org/sites/default/
> >     files/ <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 theGNSO?s Program Management Tool (PMT)
> Suite
> >      >             <https://community.icann.org/pages/viewpage.action
> >     <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____
> >      >                   o One CPH Board seat #13 (1)____
> >      >                   o One NCPH Board seat #14 (1)____
> >      >
> >      >               * Nine Observers:____
> >      >                   o One Council Chair (1)____
> >      >                   o 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 <mailto:secs at icann.org> <mailto:gnso-
> >     secs at icann.org <mailto: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 itscharter
> >     <https://
> >      > gnso.icann.org/sites/default/files/policy/2024/draft/scci-
> >     <http://gnso.icann.org/sites/default/files/policy/2024/draft/scci->
> >      >             charter-draft-update-13nov24-en.pdf>, as well as
> visiting
> >      >             theCCOICI wiki page <https://community.icann.org/
> >     display/ <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
> >     <mailto:council at icann.org>
> >      >             <mailto:council at icann.org <mailto:council at icann.org>>
> >      >             To unsubscribe send an email to council-
> >     leave at icann.org <mailto:council-leave at icann.org>
> >      >             <mailto:council-leave at icann.org <mailto: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
> >     <https://www.icann.org/privacy/policy> <https://
> >      > www.icann.org/privacy/policy <http://www.icann.org/privacy/
> >     policy>>) and the website Terms of
> >      >             Service (https://www.icann.org/privacy/tos <https://
> >     www.icann.org/privacy/tos> <https://
> >      > www.icann.org/privacy/tos <http://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 <mailto:NCSG-PC at lists.ncsg.is>
> >     <mailto:NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>>
> >      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
> >     lists.ncsg.is/mailman/listinfo/ncsg-pc> <https://
> >      > lists.ncsg.is/mailman/listinfo/ncsg-pc <http://lists.ncsg.is/
> >     mailman/listinfo/ncsg-pc>>
> >      >
> >      >         _______________________________________________
> >      >         NCSG-PC mailing list
> >      > NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
> >     <mailto:NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>>
> >      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
> >     lists.ncsg.is/mailman/listinfo/ncsg-pc> <https://
> >      > lists.ncsg.is/mailman/listinfo/ncsg-pc <http://lists.ncsg.is/
> >     mailman/listinfo/ncsg-pc>>
> >      >         _______________________________________________
> >      >         NCSG-PC mailing list
> >      > NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
> >     <mailto:NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>>
> >      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
> >     lists.ncsg.is/mailman/listinfo/ncsg-pc> <https://
> >      > lists.ncsg.is/mailman/listinfo/ncsg-pc <http://lists.ncsg.is/
> >     mailman/listinfo/ncsg-pc>>
> >      >
> >      >
> >      > _______________________________________________
> >      > NCSG-PC mailing list
> >      > NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
> >      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
> >     lists.ncsg.is/mailman/listinfo/ncsg-pc>
> >
> >     _______________________________________________
> >     NCSG-PC mailing list
> >     NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
> >     https://lists.ncsg.is/mailman/listinfo/ncsg-pc <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/20250107/d8fc2b23/attachment.htm>

From rafik.dammak at gmail.com  Tue Jan  7 04:54:10 2025
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Tue, 7 Jan 2025 11:54:10 +0900
Subject: [NCSG-PC] Fwd: [council] Call for Volunteers for SCCI | Please
 Respond by 6 January
In-Reply-To: <CAMeQZi0u2am4U-YaDW0KBAvBNgs-vbSNeZk_LfaWHjLqhp-=+Q@mail.gmail.com>
References: <698C84A1-F28A-4430-A052-E39612BAD9F5@icann.org>
 <CAM8DdeV4EFNFj3ADbcKkwxDzr2djA-M3o5ngi0BATgYA-1zmEQ@mail.gmail.com>
 <CAH5sThmMjU0fqwR2DG_RtgU+abvLMxAO4gDwNKvK50R6wEK5yQ@mail.gmail.com>
 <847580910.2455633.1733000189859@mail.yahoo.com>
 <CAMeQZi11eFQWHt6BmJ8S_PNxnyp65AUTjOrSiFBGSLUTcBiZLQ@mail.gmail.com>
 <CAH5sThkv9o_sbDi2tqX=mENCZ-KJmv9tBtU5hJOLf=JgVkSx3Q@mail.gmail.com>
 <d312e640-4a76-417c-b836-20e5fd7dc0e9@Julf.com>
 <CAH5sThmUzaLU6Lmo3U7w3OekA4BdHZTJL9dytvAMTZHYMVRfoA@mail.gmail.com>
 <ce33c08b-1d58-492a-833b-3ee04b98ccad@Julf.com>
 <CAMeQZi0u2am4U-YaDW0KBAvBNgs-vbSNeZk_LfaWHjLqhp-=+Q@mail.gmail.com>
Message-ID: <CAH5sThm-zFzx84OL170A7_VzbEiZV54MG5_htGrJ55WQVRbjCA@mail.gmail.com>

The deadline was extended to 20th Jan but I want to urge that we appoint
asap and close this.

Rafik



Le mar. 7 janv. 2025 ? 10:51, ??? Manju Chen <manju at nii.org.tw> a ?crit :

> Correct, Julf, as long as we have one council rep it's fine. And it's not
> against the rules to have another NCSG rep that happens to also be a
> councilor.
>
> Best,
> Manju
>
>
> On Mon, Jan 6, 2025 at 6:36?PM Johan Helsingius via NCSG-PC <
> ncsg-pc at lists.ncsg.is> wrote:
>
>> I assume the reps can be, but don't have to be, councilors?
>>
>>         Julf
>>
>> On 06/01/2025 10:28, Rafik Dammak wrote:
>> > Yes it is one councillor  and 2 reps
>> >
>> > Rafik
>> >
>> > On Mon, Jan 6, 2025, 17:57 Johan Helsingius via NCSG-PC <ncsg-
>> > pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>> wrote:
>> >
>> >     Just checking, we are allowed 2+1 reps, right? If we need one more,
>> I am
>> >     happy to volunteer.
>> >
>> >              Julf
>> >
>> >
>> >     On 04/01/2025 09:39, Rafik Dammak wrote:
>> >      > Hi all,
>> >      >
>> >      > Can we confirm about the representative for SCCI. We got Manju
>> >     and Juan
>> >      > volunteering.
>> >      >
>> >      > Best,
>> >      >
>> >      > Rafik
>> >      >
>> >      >
>> >      >
>> >      > On Wed, Dec 11, 2024, 17:05 ??? Manju Chen <manju at nii.org.tw
>> >     <mailto:manju at nii.org.tw>
>> >      > <mailto:manju at nii.org.tw <mailto:manju at nii.org.tw>>> wrote:
>> >      >
>> >      >     Hi,
>> >      >
>> >      >     Happy to volunteer as the council rep for NCSG.
>> >      >
>> >      >     Best,
>> >      >     Manju
>> >      >
>> >      >     On Sun, Dec 1, 2024 at 4:58?AM Juan Manuel Rojas via NCSG-PC
>> >     <ncsg-
>> >      > pc at lists.ncsg.is <mailto:pc at lists.ncsg.is> <mailto:ncsg-
>> >     pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>>> wrote:
>> >      >
>> >      >         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 Colombia
>> >      >         NPOC Chair - NCSG/GNSO
>> >      >         M.Sc. Information Technology
>> >      >
>> >      >         Registered Linux User No.*533108.*
>> >      > http://www.jmanurojas.com <http://www.jmanurojas.com> <http://
>> >     www.jmanurojas.com <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
>> >     <mailto:rafik.dammak at gmail.com> <mailto:rafik.dammak at gmail.com
>> >     <mailto: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 <mailto:mesumbeslin at gmail.com>
>> >     <mailto:mesumbeslin at gmail.com <mailto: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
>> >     <mailto:council at icann.org>
>> >      >             <mailto:council at icann.org <mailto: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
>> >     <mailto:council at gnso.icann.org> <mailto:council at gnso.icann.org
>> >     <mailto:council at gnso.icann.org>>
>> >      >             <council at gnso.icann.org
>> >     <mailto:council at gnso.icann.org> <mailto:council at gnso.icann.org
>> >     <mailto:council at gnso.icann.org>>>
>> >      >             Cc: GNSO-Secs <gnso-secs at icann.org <mailto:gnso-
>> >     secs at icann.org> <mailto:gnso-secs at icann.org <mailto: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 theCouncil
>> >      >             Committee for Overseeing and Implementing Continuous
>> >      >             Improvement (CCOICI) Framework <https://
>> >     gnso.icann.org/ <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 theGNSO
>> >      >             Council?s adoption of the charter <https://
>> >     gnso.icann.org/ <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
>> >      >             thecharter <https://gnso.icann.org/sites/default/
>> >     files/ <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 inArticle 4.4. of the ICANN Bylaws <https://
>> >      > www.icann.org/resources/pages/governance/bylaws- <http://
>> >     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
>> >      >             thecharter <https://gnso.icann.org/sites/default/
>> >     files/ <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 theGNSO?s Program Management Tool (PMT)
>> Suite
>> >      >             <https://community.icann.org/pages/viewpage.action
>> >     <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____
>> >      >                   o One CPH Board seat #13 (1)____
>> >      >                   o One NCPH Board seat #14 (1)____
>> >      >
>> >      >               * Nine Observers:____
>> >      >                   o One Council Chair (1)____
>> >      >                   o 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 <mailto:secs at icann.org> <mailto:gnso-
>> >     secs at icann.org <mailto: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 itscharter
>> >     <https://
>> >      > gnso.icann.org/sites/default/files/policy/2024/draft/scci-
>> >     <http://gnso.icann.org/sites/default/files/policy/2024/draft/scci->
>> >      >             charter-draft-update-13nov24-en.pdf>, as well as
>> visiting
>> >      >             theCCOICI wiki page <https://community.icann.org/
>> >     display/ <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
>> >     <mailto:council at icann.org>
>> >      >             <mailto:council at icann.org <mailto:council at icann.org
>> >>
>> >      >             To unsubscribe send an email to council-
>> >     leave at icann.org <mailto:council-leave at icann.org>
>> >      >             <mailto:council-leave at icann.org <mailto: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
>> >     <https://www.icann.org/privacy/policy> <https://
>> >      > www.icann.org/privacy/policy <http://www.icann.org/privacy/
>> >     policy>>) and the website Terms of
>> >      >             Service (https://www.icann.org/privacy/tos <https://
>> >     www.icann.org/privacy/tos> <https://
>> >      > www.icann.org/privacy/tos <http://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 <mailto:NCSG-PC at lists.ncsg.is>
>> >     <mailto:NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>>
>> >      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>> >     lists.ncsg.is/mailman/listinfo/ncsg-pc> <https://
>> >      > lists.ncsg.is/mailman/listinfo/ncsg-pc <http://lists.ncsg.is/
>> >     mailman/listinfo/ncsg-pc>>
>> >      >
>> >      >         _______________________________________________
>> >      >         NCSG-PC mailing list
>> >      > NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>> >     <mailto:NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>>
>> >      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>> >     lists.ncsg.is/mailman/listinfo/ncsg-pc> <https://
>> >      > lists.ncsg.is/mailman/listinfo/ncsg-pc <http://lists.ncsg.is/
>> >     mailman/listinfo/ncsg-pc>>
>> >      >         _______________________________________________
>> >      >         NCSG-PC mailing list
>> >      > NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>> >     <mailto:NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>>
>> >      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>> >     lists.ncsg.is/mailman/listinfo/ncsg-pc> <https://
>> >      > lists.ncsg.is/mailman/listinfo/ncsg-pc <http://lists.ncsg.is/
>> >     mailman/listinfo/ncsg-pc>>
>> >      >
>> >      >
>> >      > _______________________________________________
>> >      > NCSG-PC mailing list
>> >      > NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>> >      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>> >     lists.ncsg.is/mailman/listinfo/ncsg-pc>
>> >
>> >     _______________________________________________
>> >     NCSG-PC mailing list
>> >     NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>> >     https://lists.ncsg.is/mailman/listinfo/ncsg-pc <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/20250107/844f4708/attachment.htm>

From mesumbeslin at gmail.com  Tue Jan  7 05:32:46 2025
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Tue, 7 Jan 2025 06:32:46 +0300
Subject: [NCSG-PC] Fwd: [council] EXTENDED DEADLINE | Call for Volunteers
 for SCCI | Please Respond by 20 January
In-Reply-To: <5C41E2E9-F9C6-4412-9B95-D8B990C44524@icann.org>
References: <5C41E2E9-F9C6-4412-9B95-D8B990C44524@icann.org>
Message-ID: <CAM8DdeUBjvXVupYdT8mF5Fb-S9TmojhJkkYzQRoVFXXqrjSBdw@mail.gmail.com>

Hi all,

The PC is seeking two (2) non-councillor volunteers to appoint as NCSG
representatives to 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). Please read the message below for
further details.

If you're interested, please send your expression of interest to me and
copy the NCSG chair and Andrea before January 14th 2025.

Warmly,
Tomslin


---------- Forwarded message ---------
From: Devan Reed via council <council at icann.org>
Date: Tue, 7 Jan 2025 at 00:17
Subject: [council] EXTENDED DEADLINE | Call for Volunteers for SCCI |
Please Respond by 20 January
To: GNSO Council List <council at gnso.icann.org>
Cc: GNSO-Secs <gnso-secs at icann.org>


** 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, 20 January 2025.*



*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 [gnso.icann.org]
<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/field-file-attach/continuous-improvement-oversight-implementation-framework-29jun21-en.pdf__;!!PtGJab4!-Wq1P5mu6Quaq809ddH-8ls4oGohg5p20yS9KuwkZH6sJU6rUiDWejIoGblCkNUeF8Fwv5IrWxGz3RgscBe_Iho$>
 (last updated 29 June 2021), which has now converted to a permanent
standing committee following the GNSO Council?s adoption of the charter
[gnso.icann.org]
<https://urldefense.com/v3/__https:/gnso.icann.org/en/council/resolutions/2020-current*202411__;Iw!!PtGJab4!-Wq1P5mu6Quaq809ddH-8ls4oGohg5p20yS9KuwkZH6sJU6rUiDWejIoGblCkNUeF8Fwv5IrWxGz3RgsEBcHu90$>
.



*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 [gnso.icann.org]
<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy/2024/draft/scci-charter-draft-update-13nov24-en.pdf__;!!PtGJab4!-Wq1P5mu6Quaq809ddH-8ls4oGohg5p20yS9KuwkZH6sJU6rUiDWejIoGblCkNUeF8Fwv5IrWxGz3Rgs5l4Bx-E$>,
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 [gnso.icann.org]
<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy/2024/draft/scci-charter-draft-update-13nov24-en.pdf__;!!PtGJab4!-Wq1P5mu6Quaq809ddH-8ls4oGohg5p20yS9KuwkZH6sJU6rUiDWejIoGblCkNUeF8Fwv5IrWxGz3Rgs5l4Bx-E$>
 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.* *Monday, 20 January 2025.*



*Background*

For more information and to better prepare for participation on this
Standing Committee, please read its charter [gnso.icann.org]
<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy/2024/draft/scci-charter-draft-update-13nov24-en.pdf__;!!PtGJab4!-Wq1P5mu6Quaq809ddH-8ls4oGohg5p20yS9KuwkZH6sJU6rUiDWejIoGblCkNUeF8Fwv5IrWxGz3Rgs5l4Bx-E$>,
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/20250107/bb30e9be/attachment.htm>
-------------- next part --------------
_______________________________________________
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.

From mesumbeslin at gmail.com  Tue Jan  7 15:22:33 2025
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Tue, 7 Jan 2025 16:22:33 +0300
Subject: [NCSG-PC] NCSG PC Chair Election
Message-ID: <CAM8DdeWtf0HXJDiMBrCnKLBa4=RrRPGcmsWM5QvcYAC-L=pdOw@mail.gmail.com>

Hi PC members,

I am writing to call for the election of the Policy Committee Chair.
Normally this is started towards the end of October but it was delayed to
ensure we have all the constituency representatives elected and added to
the list first.

..........

POSITION

Policy Committee Chair over the course of a 1 year term.  The chair tasks
can be summarized into:


   -

   Managing PC work:
   -
      -

      Acting as project manager and tracking tasks and activities;
      -

      Following closely policy discussions, initiatives and public
      comments. Liaising with drafting team for public comments;
      -

      Following closely the deadlines, ensuring NCSG has enough volunteers
      to draft comments and delivering in a timely manner;
      -

      Identify NCSG members participating in PDP WG and liaise with them
      for reporting and updates; e
      -

      Organize the appointment of NCSG representatives by PC to GNSO
      council committees, PDP WG when there is a call for members etc.


   -

   Liaising with GNSO Council work and its committees (SSC, SCBO, small
   teams);
   -

   Track progress for working groups and approaching members to get
   updates;
   -

   Planning tasks (e.g. review of public comments, selection/appointment of
   NCSG representatives), schedule the NCSG policy calls and PC meetings,
   sharing agendas with PC members for review;
   -

   Plan and schedule topic webinars on policy issue;
   -

   Liaising with NCSG chair regarding NCSG letters to board and
   communication with other SG/C;
   -

   Work with PC vice-chairs.


IMPORTANT INFO


   -

   This is a call open to all NCSG councillors and representatives from
   NCUC and NPOC to the Policy Committee;
   -

   Nominations and self-nominations are both permitted and should be sent
   to the Policy Committee List;
   -

   After the nominations, a candidate's confirmation of acceptance and
   expression of interest should be sent to the Policy Committee mailing list
   by 14th January;



TIMELINE



1- Nomination period: from 7th January to 14th January

   -

   The nominee should accept the nomination and send a short SOI by the
   14th of January.



2- Election: from 15th to 21st January

Voting is mandatory to all Policy Committee members. The GNSO support staff
will act as the election officer. The options in the ballot should be the
candidates who confirmed by the deadline and NOTA.



3- Results: should be available by 22nd January

The candidate with 2/3 of the NCSG?PC membership votes will be declared
winner.





VICE-CHAIRS APPOINTMENTS



Once the Policy Committee Chair is confirmed, a second call for interest
will be issued on this list and the PC members can elect up to 2
Vice-chairs. The appointment of the volunteers will be confirmed if there
is no objection within PC.


Warmly

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

From pedrodeperdigaolana at gmail.com  Mon Jan  6 23:48:54 2025
From: pedrodeperdigaolana at gmail.com (=?UTF-8?Q?Pedro_de_Perdig=C3=A3o_Lana?=)
Date: Mon, 6 Jan 2025 18:48:54 -0300
Subject: [NCSG-PC] [NCSG-EC] PLEASE READ: ICANN82 Sessions with GAC, SSAC
In-Reply-To: <94F36738-3AC7-4353-A6E6-8F390A7F33AA@icann.org>
References: <94F36738-3AC7-4353-A6E6-8F390A7F33AA@icann.org>
Message-ID: <CAGSP6RR+2hpS4BZ+s1texQjfSyT96GZHysvgtozupOnNQZ0LcA@mail.gmail.com>

Hi Andrea,

"Wednesday, 1030-12:00 Conflicts with RrSG Outreach: A Registrant?s
Journey" looks like the best option

Then all the other alternatives (with the exception of Wednesday,
09:00-10:00, which seems to be a bit more problematic, and Saturday,
16:30-17:30, because, correct me if I'm wrong, Caleb is on the SCCI) seem
to be kind of the same, regarding EC members commitments.

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 seg., 6 de jan. de 2025 ?s 15:12, Andrea Glandon via NCSG-EC <
ncsg-ec at lists.ncsg.is> escreveu:

> Hello all,
>
>
>
> After looking at the schedule below are the slots that are open with no
> noncommercial sessions, although as you will see there are conflicts. Would
> you like me to send these days/times to GAC & SSAC and see if they are
> available for any of them? We will also need to find a slot for an NCSG EC
> Sign-up room, unless you want to do it over lunch one of the days.
>
>
>
>
>
> Saturday, 16:30-17:30 Conflicts with SCCI
>
> Wednesday, 09:00-10:00 Conflicts with SSAC & Board, but could be meeting
> with GAC if they are available. Also conflicts with Sub Pro & PPSAI IRT.
>
> Wednesday, 1030-12:00 Conflicts with RrSG Outreach: A Registrant?s Journey
>
> Wednesday, 16:30-17:30 Conflicts with RSRS Standing Committee
>
> Thursday, 09:00-10:00 Conflicts with Geopolitical Forum
>
> Thursday, 15:00-16:00 Conflicts with SubPro IRT
>
>
>
> Thanks!
>
> Kind Regards,
>
> Andrea
>
>
>
>
>
> *From: *NCSG-EC <ncsg-ec-bounces at lists.ncsg.is> on behalf of Andrea
> Glandon via NCSG-EC <ncsg-ec at lists.ncsg.is>
> *Reply-To: *Andrea Glandon <andrea.glandon at icann.org>
> *Date: *Friday, January 3, 2025 at 08:18
> *To: *ncsg-pc <ncsg-pc at lists.ncsg.is>, NCSG EC <ncsg-ec at lists.ncsg.is>
> *Subject: *Re: [NCSG-EC] [Ext] Re: ICANN82 NCSG Issue Forum
>
>
>
> Hello all,
>
>
>
> Attached is the a draft ICANN82 schedule with the additional NCSG meetings
> with other groups, etc. I am still working with GAC and SSAC to see if
> there is a time slot that works for all.
>
>
>
> Thanks!
>
> Kind Regards,
>
> Andrea
>
>
>
>
>
> *From: *Rafik Dammak <rafik.dammak at gmail.com>
> *Date: *Thursday, January 2, 2025 at 20:03
> *To: *Andrea Glandon <andrea.glandon at icann.org>
> *Cc: *ncsg-pc <ncsg-pc at lists.ncsg.is>, NCSG EC <ncsg-ec at lists.ncsg.is>
> *Subject: *Re: [NCSG-EC] [Ext] Re: ICANN82 NCSG Issue Forum
>
>
>
> Hi Andrea,
>
>
>
> Thanks for the updated schedule. can we have also listed the other joint
> sessions there e.g. GAC, ALAC, SSAC for those confirmed.
>
> FYI we also confirmed the usual breakfast meeting with Chris and Becky. We
> will also have a call with Chris this month, meeting invite to be sent soon.
>
>
>
> Best,
>
>
>
> Rafik
>
> Le ven. 3 janv. 2025 ? 02:02, Andrea Glandon <andrea.glandon at icann.org> a
> ?crit :
>
> Please find attached the most updated draft ICANN82 schedule.
>
>
>
> Kind Regards,
>
> Andrea
>
>
>
>
>
> *From: *NCSG-EC <ncsg-ec-bounces at lists.ncsg.is> on behalf of Andrea
> Glandon via NCSG-EC <NCSG-ec at lists.ncsg.is>
> *Reply-To: *Andrea Glandon <andrea.glandon at icann.org>
> *Date: *Thursday, January 2, 2025 at 10:39
> *To: *Rafik Dammak <rafik.dammak at gmail.com>
> *Cc: *ncsg-pc <ncsg-pc at lists.ncsg.is>, NCSG EC <NCSG-ec at lists.ncsg.is>
> *Subject: *Re: [NCSG-EC] [Ext] Re: ICANN82 NCSG Issue Forum
>
>
>
> Hello all.
>
>
>
> Happy New Year!
>
>
>
> I just wanted to confirm that I will be switching the NCSG Issue Forum to
> Tuesday, 13:15-14:30 local time.
>
>
>
> Thanks!
>
> Kind Regards,
>
> Andrea
>
>
>
>
>
> *From: *Rafik Dammak <rafik.dammak at gmail.com>
> *Date: *Friday, December 20, 2024 at 16:16
> *To: *Andrea Glandon <andrea.glandon at icann.org>
> *Cc: *NCSG EC <NCSG-ec at lists.ncsg.is>, ncsg-pc <ncsg-pc at lists.ncsg.is>
> *Subject: *[Ext] Re: [NCSG-EC] ICANN82 NCSG Issue Forum
>
>
>
> Hi Andrea,
>
>
>
> I think the straightforward choice is to select Tuesday and that will link
> to other NCSG sessions in that day.
>
>
>
> Best,
>
>
>
> Rafik
>
> On Sat, Dec 21, 2024, 01:19 Andrea Glandon via NCSG-EC <
> ncsg-ec at lists.ncsg.is> wrote:
>
> Hello all,
>
>
>
> Currently the NCSG Issue Forum is scheduled on Sunday, 09 March, 1030-12.
> This is against a GNSO Working Session.
>
>
>
> Here are some other possibilities for the session. I am also attaching a
> PDF with all sessions and sessions that NCSG will be participating in with
> other groups. I know it?s tiny, but you can enlarge to see better.
>
>
>
> Tuesday, 11 March 1315-1430
>
> Wednesday, 12 March 0900-1000, against Sub Pro IRT & PPSAI IRT
>
> Wednesday, 12 March 1030-1200, against an RrSG session called RrSG
> Outreach: A registrant?s journey
>
> Thursday, 13 March 0900-1000, against the Geopolitical Forum
>
> Thursday, 13 March 1500-1600 against SubPro IRT
>
>
>
> Once this session is set, then I can reach out to SSAC to try to get a
> session scheduled with them.
>
>
>
> Thank you!
>
> *Andrea Glandon*
>
> Policy Operations Sr. Coordinator
>
> Internet Corporation for Assigned Names and Numbers (ICANN)
>
> *Skype ID:*  acglandon76
>
>
>
>
>
>
>
> _______________________________________________
> NCSG-EC mailing list
> 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!4H1MUJVGEpTfdM2OWbZfgTt5-FXJjW0Vr3xLIHfkkJznjufX_Z2TcJq00lTmeJoDVz-v64yNWxbRtYeFDA6gTRa4mK8FstM$>
>
> _______________________________________________
> 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/20250106/89b11223/attachment.htm>

From andrea.glandon at icann.org  Tue Jan  7 15:49:35 2025
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Tue, 7 Jan 2025 13:49:35 +0000
Subject: [NCSG-PC] [Ext] Re: [NCSG-EC] PLEASE READ: ICANN82 Sessions
 with GAC, SSAC
In-Reply-To: <CAH5sThni-su9O_9xHXmamqzKiCB7m-4xK96C==WZKOg5KFC7Qw@mail.gmail.com>
References: <94F36738-3AC7-4353-A6E6-8F390A7F33AA@icann.org>
 <CAH5sThni-su9O_9xHXmamqzKiCB7m-4xK96C==WZKOg5KFC7Qw@mail.gmail.com>
Message-ID: <9380F037-4D00-452B-A69A-67DB7F584F04@icann.org>

Thank you, Rafik. I do note that I believe the Geopolitical Forum will be more interactive this time around. I will send the open time that we have to GAC and SSAC and see if they are available. Once those are scheduled I will see what is available for NCSG EC sign-up room.

Kind Regards,
Andrea


From: Rafik Dammak <rafik.dammak at gmail.com>
Date: Monday, January 6, 2025 at 18:10
To: Andrea Glandon <andrea.glandon at icann.org>
Cc: ncsg-pc <ncsg-pc at lists.ncsg.is>, NCSG EC <ncsg-ec at lists.ncsg.is>
Subject: [Ext] Re: [NCSG-EC] PLEASE READ: ICANN82 Sessions with GAC, SSAC

Hi Andrea,

My simple criteria would be to avoid clashing sessions where we can intervene or have a substantial number of WG members participating e.g. SSAC-board session we will be in listening only mode but it is also clashing against 2 IRTs.
so wednesday 10:30-12:00  would be fine since it is an outreach session. possibly Thursday 9:00-10:00 as this session is usually a speaking panel if I am not mistaking and not so much interaction with the audience.
there is no optimal option and we need to accept the tradeoff. Do we value the possibility to interact with GAC and SSAC and reach them out or having FOMO for some sessions?

Best,

Rafik

Le mar. 7 janv. 2025 ? 03:12, Andrea Glandon via NCSG-EC <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>> a ?crit :
Hello all,

After looking at the schedule below are the slots that are open with no noncommercial sessions, although as you will see there are conflicts. Would you like me to send these days/times to GAC & SSAC and see if they are available for any of them? We will also need to find a slot for an NCSG EC Sign-up room, unless you want to do it over lunch one of the days.


Saturday, 16:30-17:30 Conflicts with SCCI
Wednesday, 09:00-10:00 Conflicts with SSAC & Board, but could be meeting with GAC if they are available. Also conflicts with Sub Pro & PPSAI IRT.
Wednesday, 1030-12:00 Conflicts with RrSG Outreach: A Registrant?s Journey
Wednesday, 16:30-17:30 Conflicts with RSRS Standing Committee
Thursday, 09:00-10:00 Conflicts with Geopolitical Forum
Thursday, 15:00-16:00 Conflicts with SubPro IRT

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, January 3, 2025 at 08:18
To: ncsg-pc <ncsg-pc at lists.ncsg.is<mailto:ncsg-pc at lists.ncsg.is>>, NCSG EC <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>>
Subject: Re: [NCSG-EC] [Ext] Re: ICANN82 NCSG Issue Forum

Hello all,

Attached is the a draft ICANN82 schedule with the additional NCSG meetings with other groups, etc. I am still working with GAC and SSAC to see if there is a time slot that works for all.

Thanks!
Kind Regards,
Andrea


From: Rafik Dammak <rafik.dammak at gmail.com<mailto:rafik.dammak at gmail.com>>
Date: Thursday, January 2, 2025 at 20:03
To: Andrea Glandon <andrea.glandon at icann.org<mailto:andrea.glandon at icann.org>>
Cc: ncsg-pc <ncsg-pc at lists.ncsg.is<mailto:ncsg-pc at lists.ncsg.is>>, NCSG EC <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>>
Subject: Re: [NCSG-EC] [Ext] Re: ICANN82 NCSG Issue Forum

Hi Andrea,

Thanks for the updated schedule. can we have also listed the other joint sessions there e.g. GAC, ALAC, SSAC for those confirmed.
FYI we also confirmed the usual breakfast meeting with Chris and Becky. We will also have a call with Chris this month, meeting invite to be sent soon.

Best,

Rafik
Le ven. 3 janv. 2025 ? 02:02, Andrea Glandon <andrea.glandon at icann.org<mailto:andrea.glandon at icann.org>> a ?crit :
Please find attached the most updated draft ICANN82 schedule.

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: Thursday, January 2, 2025 at 10:39
To: Rafik Dammak <rafik.dammak at gmail.com<mailto:rafik.dammak at gmail.com>>
Cc: ncsg-pc <ncsg-pc at lists.ncsg.is<mailto:ncsg-pc at lists.ncsg.is>>, NCSG EC <NCSG-ec at lists.ncsg.is<mailto:NCSG-ec at lists.ncsg.is>>
Subject: Re: [NCSG-EC] [Ext] Re: ICANN82 NCSG Issue Forum

Hello all.

Happy New Year!

I just wanted to confirm that I will be switching the NCSG Issue Forum to Tuesday, 13:15-14:30 local time.

Thanks!
Kind Regards,
Andrea


From: Rafik Dammak <rafik.dammak at gmail.com<mailto:rafik.dammak at gmail.com>>
Date: Friday, December 20, 2024 at 16:16
To: Andrea Glandon <andrea.glandon at icann.org<mailto:andrea.glandon at icann.org>>
Cc: NCSG EC <NCSG-ec at lists.ncsg.is<mailto:NCSG-ec at lists.ncsg.is>>, ncsg-pc <ncsg-pc at lists.ncsg.is<mailto:ncsg-pc at lists.ncsg.is>>
Subject: [Ext] Re: [NCSG-EC] ICANN82 NCSG Issue Forum

Hi Andrea,

I think the straightforward choice is to select Tuesday and that will link to other NCSG sessions in that day.

Best,

Rafik
On Sat, Dec 21, 2024, 01:19 Andrea Glandon via NCSG-EC <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>> wrote:
Hello all,

Currently the NCSG Issue Forum is scheduled on Sunday, 09 March, 1030-12. This is against a GNSO Working Session.

Here are some other possibilities for the session. I am also attaching a PDF with all sessions and sessions that NCSG will be participating in with other groups. I know it?s tiny, but you can enlarge to see better.

Tuesday, 11 March 1315-1430
Wednesday, 12 March 0900-1000, against Sub Pro IRT & PPSAI IRT
Wednesday, 12 March 1030-1200, against an RrSG session called RrSG Outreach: A registrant?s journey
Thursday, 13 March 0900-1000, against the Geopolitical Forum
Thursday, 13 March 1500-1600 against SubPro IRT

Once this session is set, then I can reach out to SSAC to try to get a session scheduled with them.

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



_______________________________________________
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!4H1MUJVGEpTfdM2OWbZfgTt5-FXJjW0Vr3xLIHfkkJznjufX_Z2TcJq00lTmeJoDVz-v64yNWxbRtYeFDA6gTRa4mK8FstM$>
_______________________________________________
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!6aOIZzs2GMCV3tBJs0G10JDruQ1051kO5gjSiFmMyKlbNYChRtAY4ejPM8AH16o-pCX5d7D4MYVEYO3GI5v1mVBcdaDNrNI$>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250107/1efc9904/attachment.htm>

From mesumbeslin at gmail.com  Wed Jan  8 03:58:38 2025
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Wed, 8 Jan 2025 04:58:38 +0300
Subject: [NCSG-PC] GNSO Council Accuracy Assignment - Questions to be
 answered by NCSG
In-Reply-To: <091F7CC1-8220-47D9-80BB-2F04099219D6@icann.org>
References: <091F7CC1-8220-47D9-80BB-2F04099219D6@icann.org>
Message-ID: <CAM8DdeWr=+q0sDn2aJLxzqv46Z20=rzK4=qsvke=Fc5Ri9nYjQ@mail.gmail.com>

Hi all,

If you recall, Registration data accuracy has been a topic of contention in
the community now for a while. Those who follow the the topic know that the
Accuracy Scoping team was paused by the council due to challenges of
pursuing further work on accuracy, including that

   1. It is unclear whether [the scenarios] would provide useful data to
   inform the Accuracy Scoping Team?s efforts;
   2. The scenarios are not expected to provide data as it relates to
   identity verification of the registrant or veracity of the contact
   information (i.e., the data belongs to the data subject);
   3. The costs associated with a full-scale registrar audit [Scoping Team
   Recommendation #2] may be prohibitive when taking into account the
   relatively low level of insight the audit may yield;
   4. ICANN does not have the authority to mandate collection of nonpublic
   registration data necessary to conduct reviews outside of auditing current
   contractual requirements; and
   5. ICANN may not be able to demonstrate the purpose of some of the data
   processing outweighs the rights of the impacted data subject.

As a result, deliberations on this topic on the council was deferred till
February and an assignment to ask ICANN Org some clarifying legal
questions, and thereafter ask each SG/C to respond to a set of threshold
questions that will help guide the way forward on this topic was agreed by
the council. ICANN Org came back with their response
<https://urldefense.com/v3/__https:/us-east-1.secure-attach.amazon.com/da78dbeb-dd4d-4f3f-96c2-1d5abfe7810b/d3fd2bca-021f-494b-957c-0c800d63f333__;!!PtGJab4!5ebsdR0WRUrjpIzUO8HekPbjqckThf0GWEiIM_7eVuzWwd4NAuc_-nt2-GqtwpE87UIulB_KPGxmS00M_1a2SSvlTw$>
just before the December holidays.

Now therefore, each SG/C is required to respond to the threshold questions
<https://gnso.icann.org/sites/default/files/policy/2024/draft/draft-concept-proposal-accuracy-12sep24.pdf>
by Friday 31 January 2025. We forgot to include it for discussion in our
Policy meeting earlier this week. However, I request that members provide
their input via this email thread. Once agreed, we'll forward our response
to the Council. The questions we have to answer are in the link above but
for convenience, I'll list them here below:

   1. *What are concrete and articulable examples of what inaccurate data
   DOES prevent or inhibit, and how does it do so?*
   2. *What are concrete and articulable examples of what inaccurate data
   does NOT prevent?*
   3. *Are there specific stakeholders, industries, or sectors particularly
   vulnerable to the effects of inaccurate registration data? If so, what are
   they and why?*
   4. *Given the examples provided in response to the three questions above
   (if any), please articulate a short problem statement for accuracy. The
   problem statement should consider:*
      - *What is the current problem or challenge?*
      - *What are the consequences of this problem or challenge?*
      - *What is the ultimate objective of working on this problem or
      challenge?*
      - *Considering the limitations of data processing, how do you propose
      to address this problem?*
   5. *Is now the appropriate time to address the problem? For example,
   some stakeholders have mentioned the implementation of NIS2 as an important
   precursor to understanding new accuracy requirements. Should this or other
   examples be considered prior to engaging in potential policy work?*
   6. *Are the ICANN org alternatives proposals worth exploring, such as:*
      - *Provision of historical audit data that measures registrars?
      compliance with accuracy-related provisions in the RAA.*
      - *Engagement with contracted parties and ccTLD operators on
      developments in European policymaking regarding registration
data accuracy.*
   7. *What are the limitations of the ICANN proposals? Why should or
   should they not be pursued?*
   8. *What other possibilities can be explored to move our work on
   Accuracy forward?*

I look forward to your contribution to these questions.

Warmly,
Tomslin



---------- Forwarded message ---------
From: Feodora Hamza via council <council at icann.org>
Date: Thu, 12 Dec 2024 at 23:11
Subject: [council] Re: Follow-up GNSO Council Accuracy Assignment
To: DiBiase, Gregory <dibiase at amazon.com>, council at gnso.icann.org <
council at gnso.icann.org>


Dear Councilors,



due to technical issues, please see accuracy assignment attached and linked
below.

Accuracy Assignment:
https://gnso.icann.org/sites/default/files/policy/2024/draft/draft-concept-proposal-accuracy-12sep24.pdf



Kind regards,

Feodora Hamza



*From: *"DiBiase, Gregory via council" <council at icann.org>
*Reply to: *"DiBiase, Gregory" <dibiase at amazon.com>
*Date: *Thursday, 12 December 2024 at 20:57
*To: *"council at gnso.icann.org" <council at gnso.icann.org>
*Subject: *[council] Follow-up GNSO Council Accuracy Assignment



   - *Attachments protected by Amazon: *
   - Answer to the GNSO questions on accuracy.pdf
   [us-east-1.secure-attach.amazon.com]
   <https://urldefense.com/v3/__https:/us-east-1.secure-attach.amazon.com/da78dbeb-dd4d-4f3f-96c2-1d5abfe7810b/d3fd2bca-021f-494b-957c-0c800d63f333__;!!PtGJab4!5ebsdR0WRUrjpIzUO8HekPbjqckThf0GWEiIM_7eVuzWwd4NAuc_-nt2-GqtwpE87UIulB_KPGxmS00M_1a2SSvlTw$>
|

   - ATT00001.txt [us-east-1.secure-attach.amazon.com]
   <https://urldefense.com/v3/__https:/us-east-1.secure-attach.amazon.com/da78dbeb-dd4d-4f3f-96c2-1d5abfe7810b/94d6cb3e-3ab2-446c-a385-9c201a9cffc9__;!!PtGJab4!5ebsdR0WRUrjpIzUO8HekPbjqckThf0GWEiIM_7eVuzWwd4NAuc_-nt2-GqtwpE87UIulB_KPGxmS00M_1ZAKmAJaA$>
|


Amazon has replaced the attachments in this email with download links.
Downloads will be available until January 11, 2025, 19:56 (UTC+00:00). Tell
us what you think [amazonexteu.qualtrics.com]
<https://urldefense.com/v3/__https:/amazonexteu.qualtrics.com/jfe/form/SV_ehuz6zGo8YnsRKK__;!!PtGJab4!5ebsdR0WRUrjpIzUO8HekPbjqckThf0GWEiIM_7eVuzWwd4NAuc_-nt2-GqtwpE87UIulB_KPGxmS00M_1Zzdd6ztA$>

For more information click here [docs.secure-attach.amazon.com]
<https://urldefense.com/v3/__https:/docs.secure-attach.amazon.com/guide__;!!PtGJab4!5ebsdR0WRUrjpIzUO8HekPbjqckThf0GWEiIM_7eVuzWwd4NAuc_-nt2-GqtwpE87UIulB_KPGxmS00M_1ZzNkqBbQ$>

Dear Councilors,



I am following up on the attached email from ICANN Org in which they
provided their input on the accuracy assignment.  On 25 October, we shared
the proposed accuracy assignment, which included questions for ICANN org
and the community.



Now that ICANN org has provided responses to the Council?s questions, we
are now sending the remaining questions in the attached proposal to
interested SG/C/ACs for their input. Given the proximity to the holidays,
we propose giving groups until Friday, 31 January 2025 to provide their
input to the Council.



As noted during the Council?s previous discussions on the topic of
accuracy, the Council recognizes the importance of accuracy and is
committed to making progress on this issue. Your group?s responses to these
questions are very important for the Council?s future discussion, and we
strongly encourage your groups to think about these questions and provide
candid responses.



Thank you in advance for your input.



Thanks,

Greg
_______________________________________________
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/20250108/8fc9a4fc/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: draft-concept-proposal-accuracy-12sep24 (2).pdf
Type: application/pdf
Size: 50780 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250108/8fc9a4fc/attachment.pdf>

From andrea.glandon at icann.org  Thu Jan  9 02:20:20 2025
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Thu, 9 Jan 2025 00:20:20 +0000
Subject: [NCSG-PC] ICANN82 Joint meeting with GAC
Message-ID: <FBBFD4E1-BA64-4C87-90CF-14A660B3B225@icann.org>

Hello all,

The GAC has available 30 minutes on Sunday, 09 March at the first block of 09:00-10:00. This does conflict with the NPOC Membership session and a GNSO Working Session. There is a short timeline to decide if you would like to have this meeting.

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/20250109/dc36414f/attachment.htm>

From rafik.dammak at gmail.com  Thu Jan  9 03:21:25 2025
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Thu, 9 Jan 2025 10:21:25 +0900
Subject: [NCSG-PC] [NCSG-EC] ICANN82 Joint meeting with GAC
In-Reply-To: <FBBFD4E1-BA64-4C87-90CF-14A660B3B225@icann.org>
References: <FBBFD4E1-BA64-4C87-90CF-14A660B3B225@icann.org>
Message-ID: <CAH5sTh=0q8fsoHeOV3no-bbA1g2APmEkmxh9GYaM+EKs3zCmRA@mail.gmail.com>

Hi Andrea,

Thanks for the update.
It is definitely not an optimal situation. To add more context, the next
available opportunity to meet the GAC will be in Oman if they agree. One
"workaround" is to have a small group of NCSGers who can attend and be
prepared for the outreach to GAC.

Best,

Rafik
Le jeu. 9 janv. 2025 ? 09:20, Andrea Glandon via NCSG-EC <
ncsg-ec at lists.ncsg.is> a ?crit :

> Hello all,
>
>
>
> The GAC has available 30 minutes on Sunday, 09 March at the first block of
> 09:00-10:00. This does conflict with the NPOC Membership session and a GNSO
> Working Session. There is a short timeline to decide if you would like to
> have this meeting.
>
>
>
> Thanks!
>
> *Andrea Glandon*
>
> Policy Operations Sr. Coordinator
>
> Internet Corporation for Assigned Names and Numbers (ICANN)
>
> *Skype ID:*  acglandon76
>
>
>
>
>
>
> _______________________________________________
> 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/20250109/b309c15c/attachment.htm>

From farzaneh.badii at gmail.com  Thu Jan  9 15:42:48 2025
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Thu, 9 Jan 2025 08:42:48 -0500
Subject: [NCSG-PC] [NCSG-EC] ICANN82 Joint meeting with GAC
In-Reply-To: <CAGSP6RQ_ctn8cz=m7Di_6r2QnFndmDReTcou9gKc=T0LynPk1w@mail.gmail.com>
References: <FBBFD4E1-BA64-4C87-90CF-14A660B3B225@icann.org>
 <CAH5sTh=0q8fsoHeOV3no-bbA1g2APmEkmxh9GYaM+EKs3zCmRA@mail.gmail.com>
 <CAGSP6RQ_ctn8cz=m7Di_6r2QnFndmDReTcou9gKc=T0LynPk1w@mail.gmail.com>
Message-ID: <CAN1qJvAp+GL_Gnx6O4KeeOw_fe84ZBGdkOfrGmS6B-1yEGLhhQ@mail.gmail.com>

Lets take it. We should start these conversations. Rafik, Pedro, and a few
others can go. We are just introducing ourselves at this point and letting
them know the issues.

Farzaneh


On Thu, Jan 9, 2025 at 8:36?AM Pedro de Perdig?o Lana via NCSG-EC <
ncsg-ec at lists.ncsg.is> wrote:

> Hi everyone,
>
> I don't think we have decided on this, right? Maybe we have already missed
> the window we had to decide, but I believe we may have too many agenda
> items to guarantee that we will have relevant NCSG participation in this
> meeting. If, however, we have volunteers who are interested in leading the
> dialogue with the GAC, I would support accepting this slot.
>
> 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 qua., 8 de jan. de 2025 ?s 22:21, Rafik Dammak via NCSG-EC <
> ncsg-ec at lists.ncsg.is> escreveu:
>
>>
>> Hi Andrea,
>>
>> Thanks for the update.
>> It is definitely not an optimal situation. To add more context, the next
>> available opportunity to meet the GAC will be in Oman if they agree. One
>> "workaround" is to have a small group of NCSGers who can attend and be
>> prepared for the outreach to GAC.
>>
>> Best,
>>
>> Rafik
>> Le jeu. 9 janv. 2025 ? 09:20, Andrea Glandon via NCSG-EC <
>> ncsg-ec at lists.ncsg.is> a ?crit :
>>
>>> Hello all,
>>>
>>>
>>>
>>> The GAC has available 30 minutes on Sunday, 09 March at the first block
>>> of 09:00-10:00. This does conflict with the NPOC Membership session and a
>>> GNSO Working Session. There is a short timeline to decide if you would like
>>> to have this meeting.
>>>
>>>
>>>
>>> Thanks!
>>>
>>> *Andrea Glandon*
>>>
>>> Policy Operations Sr. Coordinator
>>>
>>> Internet Corporation for Assigned Names and Numbers (ICANN)
>>>
>>> *Skype ID:*  acglandon76
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>
> _______________________________________________
> 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/20250109/58333901/attachment.htm>

From andrea.glandon at icann.org  Thu Jan  9 16:43:56 2025
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Thu, 9 Jan 2025 14:43:56 +0000
Subject: [NCSG-PC] [Ext] Re: [NCSG-EC] ICANN82 Joint meeting with GAC
In-Reply-To: <CAN1qJvAp+GL_Gnx6O4KeeOw_fe84ZBGdkOfrGmS6B-1yEGLhhQ@mail.gmail.com>
References: <FBBFD4E1-BA64-4C87-90CF-14A660B3B225@icann.org>
 <CAH5sTh=0q8fsoHeOV3no-bbA1g2APmEkmxh9GYaM+EKs3zCmRA@mail.gmail.com>
 <CAGSP6RQ_ctn8cz=m7Di_6r2QnFndmDReTcou9gKc=T0LynPk1w@mail.gmail.com>
 <CAN1qJvAp+GL_Gnx6O4KeeOw_fe84ZBGdkOfrGmS6B-1yEGLhhQ@mail.gmail.com>
Message-ID: <9C52B5FE-186C-4B9E-BE1D-C8E554461523@icann.org>

Thank you, all!

I have let GAC staff know that NCSG will accept this time slot. GAC will be reaching out with an updated list of topics given that they time slot is 30 minutes. The time slot is Sunday, 09 March 09:30-10:00 local time. From 09:00-09:30 is a GAC open mic session.

Kind Regards,
Andrea


From: NCSG-EC <ncsg-ec-bounces at lists.ncsg.is> on behalf of farzaneh badii via NCSG-EC <ncsg-ec at lists.ncsg.is>
Reply-To: farzaneh badii <farzaneh.badii at gmail.com>
Date: Thursday, January 9, 2025 at 07:43
To: Pedro de Perdig?o Lana <pedrodeperdigaolana at gmail.com>
Cc: "ncsg-pc at lists.ncsg.is" <ncsg-pc at lists.ncsg.is>, "ncsg-ec at lists.ncsg.is" <ncsg-ec at lists.ncsg.is>
Subject: [Ext] Re: [NCSG-EC] ICANN82 Joint meeting with GAC

Lets take it. We should start these conversations. Rafik, Pedro, and a few others can go. We are just introducing ourselves at this point and letting them know the issues.

Farzaneh


On Thu, Jan 9, 2025 at 8:36?AM Pedro de Perdig?o Lana via NCSG-EC <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>> wrote:
Hi everyone,

I don't think we have decided on this, right? Maybe we have already missed the window we had to decide, but I believe we may have too many agenda items to guarantee that we will have relevant NCSG participation in this meeting. If, however, we have volunteers who are interested in leading the dialogue with the GAC, I would support accepting this slot.

Cordially,

Pedro de Perdig?o Lana
Advogado - OAB/PR 90.600 [nic.br]<https://urldefense.com/v3/__https:/www.nic.br/__;!!PtGJab4!6KG4p7_nFk3o8k_tWlVj2TN8ErvDXj_cQioa3e-n971FBvUL2sap-xbyCF_QUFk4tQmc3msP6VP6VIvkOLvLVauDCtxj2A$>,  Pesquisador (GEDAI/UFPR [gedai.com.br]<https://urldefense.com/v3/__https:/www.gedai.com.br/__;!!PtGJab4!6KG4p7_nFk3o8k_tWlVj2TN8ErvDXj_cQioa3e-n971FBvUL2sap-xbyCF_QUFk4tQmc3msP6VP6VIvkOLvLVauJqJjJ3Q$>)
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!6KG4p7_nFk3o8k_tWlVj2TN8ErvDXj_cQioa3e-n971FBvUL2sap-xbyCF_QUFk4tQmc3msP6VP6VIvkOLvLVavbwq0nNQ$>, NCUC [ncuc.org]<https://urldefense.com/v3/__https:/www.ncuc.org__;!!PtGJab4!6KG4p7_nFk3o8k_tWlVj2TN8ErvDXj_cQioa3e-n971FBvUL2sap-xbyCF_QUFk4tQmc3msP6VP6VIvkOLvLVavFtQwALA$> & NCSG <https://community.icann.org/display/gnsononcomstake/Home> (ICANN), YouthLACIGF [youthlacigf.lat]<https://urldefense.com/v3/__https:/youthlacigf.lat/__;!!PtGJab4!6KG4p7_nFk3o8k_tWlVj2TN8ErvDXj_cQioa3e-n971FBvUL2sap-xbyCF_QUFk4tQmc3msP6VP6VIvkOLvLVavEe9TmEw$>, IODA [ioda.org.br]<https://urldefense.com/v3/__https:/ioda.org.br/__;!!PtGJab4!6KG4p7_nFk3o8k_tWlVj2TN8ErvDXj_cQioa3e-n971FBvUL2sap-xbyCF_QUFk4tQmc3msP6VP6VIvkOLvLVauLo2W0Lg$> e CC Brasil [br.creativecommons.net]<https://urldefense.com/v3/__https:/br.creativecommons.net/__;!!PtGJab4!6KG4p7_nFk3o8k_tWlVj2TN8ErvDXj_cQioa3e-n971FBvUL2sap-xbyCF_QUFk4tQmc3msP6VP6VIvkOLvLVatpfoc49w$>.
Essa mensagem ? restrita ao remetente e destinat?rio(s). Se recebida por engano, favor responder informando o erro.


Em qua., 8 de jan. de 2025 ?s 22:21, Rafik Dammak via NCSG-EC <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>> escreveu:

Hi Andrea,

Thanks for the update.
It is definitely not an optimal situation. To add more context, the next  available opportunity to meet the GAC will be in Oman if they agree. One "workaround" is to have a small group of NCSGers who can attend and be prepared for the outreach to GAC.

Best,

Rafik
Le jeu. 9 janv. 2025 ? 09:20, Andrea Glandon via NCSG-EC <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>> a ?crit :
Hello all,

The GAC has available 30 minutes on Sunday, 09 March at the first block of 09:00-10:00. This does conflict with the NPOC Membership session and a GNSO Working Session. There is a short timeline to decide if you would like to have this meeting.

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



_______________________________________________
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!6KG4p7_nFk3o8k_tWlVj2TN8ErvDXj_cQioa3e-n971FBvUL2sap-xbyCF_QUFk4tQmc3msP6VP6VIvkOLvLVauXkpEvrA$>
_______________________________________________
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!6KG4p7_nFk3o8k_tWlVj2TN8ErvDXj_cQioa3e-n971FBvUL2sap-xbyCF_QUFk4tQmc3msP6VP6VIvkOLvLVauXkpEvrA$>
_______________________________________________
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!6KG4p7_nFk3o8k_tWlVj2TN8ErvDXj_cQioa3e-n971FBvUL2sap-xbyCF_QUFk4tQmc3msP6VP6VIvkOLvLVauXkpEvrA$>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250109/23c3e05f/attachment.htm>

From pedrodeperdigaolana at gmail.com  Thu Jan  9 15:35:57 2025
From: pedrodeperdigaolana at gmail.com (=?UTF-8?Q?Pedro_de_Perdig=C3=A3o_Lana?=)
Date: Thu, 9 Jan 2025 10:35:57 -0300
Subject: [NCSG-PC] [NCSG-EC] ICANN82 Joint meeting with GAC
In-Reply-To: <CAH5sTh=0q8fsoHeOV3no-bbA1g2APmEkmxh9GYaM+EKs3zCmRA@mail.gmail.com>
References: <FBBFD4E1-BA64-4C87-90CF-14A660B3B225@icann.org>
 <CAH5sTh=0q8fsoHeOV3no-bbA1g2APmEkmxh9GYaM+EKs3zCmRA@mail.gmail.com>
Message-ID: <CAGSP6RQ_ctn8cz=m7Di_6r2QnFndmDReTcou9gKc=T0LynPk1w@mail.gmail.com>

Hi everyone,

I don't think we have decided on this, right? Maybe we have already missed
the window we had to decide, but I believe we may have too many agenda
items to guarantee that we will have relevant NCSG participation in this
meeting. If, however, we have volunteers who are interested in leading the
dialogue with the GAC, I would support accepting this slot.

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 qua., 8 de jan. de 2025 ?s 22:21, Rafik Dammak via NCSG-EC <
ncsg-ec at lists.ncsg.is> escreveu:

>
> Hi Andrea,
>
> Thanks for the update.
> It is definitely not an optimal situation. To add more context, the next
> available opportunity to meet the GAC will be in Oman if they agree. One
> "workaround" is to have a small group of NCSGers who can attend and be
> prepared for the outreach to GAC.
>
> Best,
>
> Rafik
> Le jeu. 9 janv. 2025 ? 09:20, Andrea Glandon via NCSG-EC <
> ncsg-ec at lists.ncsg.is> a ?crit :
>
>> Hello all,
>>
>>
>>
>> The GAC has available 30 minutes on Sunday, 09 March at the first block
>> of 09:00-10:00. This does conflict with the NPOC Membership session and a
>> GNSO Working Session. There is a short timeline to decide if you would like
>> to have this meeting.
>>
>>
>>
>> Thanks!
>>
>> *Andrea Glandon*
>>
>> Policy Operations Sr. Coordinator
>>
>> Internet Corporation for Assigned Names and Numbers (ICANN)
>>
>> *Skype ID:*  acglandon76
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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/20250109/73370a02/attachment.htm>

From andrea.glandon at icann.org  Tue Jan 14 16:36:16 2025
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Tue, 14 Jan 2025 14:36:16 +0000
Subject: [NCSG-PC] RESPONSE REQUESTED-ICANN82 Meeting with SSAC
Message-ID: <777177F5-B7E4-45E9-B444-4917BB3B8D44@icann.org>

Hello all,

The SSAC is available for a meeting during ICANN82 on Tuesday, 11 March from 15:00-16:00 local time. This will conflict with the NCUC Membership session. Would the NCSG EC & PC like to send a small contingent (similar to what is happening with the GAC) to meet with the SSAC during this time they have available? Please respond ASAP so we can confirm with SSAC.

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/20250114/2968b291/attachment.htm>

From pedrodeperdigaolana at gmail.com  Tue Jan 14 18:38:42 2025
From: pedrodeperdigaolana at gmail.com (=?UTF-8?Q?Pedro_de_Perdig=C3=A3o_Lana?=)
Date: Tue, 14 Jan 2025 13:38:42 -0300
Subject: [NCSG-PC] [NCSG-EC] RESPONSE REQUESTED-ICANN82 Meeting with SSAC
In-Reply-To: <777177F5-B7E4-45E9-B444-4917BB3B8D44@icann.org>
References: <777177F5-B7E4-45E9-B444-4917BB3B8D44@icann.org>
Message-ID: <CAGSP6RThsp+2-QM2ivr5Fc0SDHqRvoDxoLDD=sW7cC5J7dAP6Q@mail.gmail.com>

Hi Andrea,

No problem on my side, considering we are doing something similar with NPOC
regarding the GAC meeting. However, I would already give my apologies in
advance, considering I have to be at the NCUC Membership meeting.

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 ter., 14 de jan. de 2025 ?s 11:36, Andrea Glandon via NCSG-EC <
ncsg-ec at lists.ncsg.is> escreveu:

> Hello all,
>
>
>
> The SSAC is available for a meeting during ICANN82 on Tuesday, 11 March
> from 15:00-16:00 local time. This will conflict with the NCUC Membership
> session. Would the NCSG EC & PC like to send a small contingent (similar to
> what is happening with the GAC) to meet with the SSAC during this time they
> have available? Please respond ASAP so we can confirm with SSAC.
>
>
>
> Thanks!
>
> *Andrea Glandon*
>
> Policy Operations Sr. Coordinator
>
> Internet Corporation for Assigned Names and Numbers (ICANN)
>
> *Skype ID:*  acglandon76
>
>
>
>
>
>
> _______________________________________________
> 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/20250114/a88d8c51/attachment.htm>

From rafik.dammak at gmail.com  Wed Jan 15 16:18:49 2025
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Wed, 15 Jan 2025 23:18:49 +0900
Subject: [NCSG-PC] [NCSG-EC] RESPONSE REQUESTED-ICANN82 Meeting with SSAC
In-Reply-To: <777177F5-B7E4-45E9-B444-4917BB3B8D44@icann.org>
References: <777177F5-B7E4-45E9-B444-4917BB3B8D44@icann.org>
Message-ID: <CAH5sThnq6xKvSyN0shKJmYsocA7hnPsWo_M5wck+z_-k_n8Eeg@mail.gmail.com>

Hi everyone,

I think one workaround is to allocate 30min slot during NCSG membership
session to meet with SSAC. In future, we can try to alternate for some ACs
as we have limitations on finding timeslots while we will have regular
sessions with CSG and CPH.

Best,

Rafik


On Tue, Jan 14, 2025, 23:36 Andrea Glandon via NCSG-EC <
ncsg-ec at lists.ncsg.is> wrote:

> Hello all,
>
>
>
> The SSAC is available for a meeting during ICANN82 on Tuesday, 11 March
> from 15:00-16:00 local time. This will conflict with the NCUC Membership
> session. Would the NCSG EC & PC like to send a small contingent (similar to
> what is happening with the GAC) to meet with the SSAC during this time they
> have available? Please respond ASAP so we can confirm with SSAC.
>
>
>
> Thanks!
>
> *Andrea Glandon*
>
> Policy Operations Sr. Coordinator
>
> Internet Corporation for Assigned Names and Numbers (ICANN)
>
> *Skype ID:*  acglandon76
>
>
>
>
>
>
> _______________________________________________
> 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/20250115/f4ad3010/attachment.htm>

From aminhacha at gmail.com  Wed Jan 15 12:11:48 2025
From: aminhacha at gmail.com (Amin Hacha)
Date: Wed, 15 Jan 2025 11:11:48 +0100
Subject: [NCSG-PC] [NCSG-EC] RESPONSE REQUESTED-ICANN82 Meeting with SSAC
In-Reply-To: <CAGSP6RThsp+2-QM2ivr5Fc0SDHqRvoDxoLDD=sW7cC5J7dAP6Q@mail.gmail.com>
References: <777177F5-B7E4-45E9-B444-4917BB3B8D44@icann.org>
 <CAGSP6RThsp+2-QM2ivr5Fc0SDHqRvoDxoLDD=sW7cC5J7dAP6Q@mail.gmail.com>
Message-ID: <CALUKJaXdNAHSCHCgfvgv-s3_V2bJystZ6XPCd4scFB2jSgX2yg@mail.gmail.com>

Hi Andrea and everyone,

Thank you for the update, Andrea.
I like to ensure the highest possible attendance at both meetings, with my
priority on the NCUC membership session. To avoid any scheduling conflicts,
I would prefer if we explore again alternative timing options.

I suggest we approach SSAC again to request a different time.
Best regards,
Amin


<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Tue, Jan 14, 2025 at 5:39?PM Pedro de Perdig?o Lana via NCSG-EC <
ncsg-ec at lists.ncsg.is> wrote:

> Hi Andrea,
>
> No problem on my side, considering we are doing something similar with
> NPOC regarding the GAC meeting. However, I would already give my apologies
> in advance, considering I have to be at the NCUC Membership meeting.
>
> 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 ter., 14 de jan. de 2025 ?s 11:36, Andrea Glandon via NCSG-EC <
> ncsg-ec at lists.ncsg.is> escreveu:
>
>> Hello all,
>>
>>
>>
>> The SSAC is available for a meeting during ICANN82 on Tuesday, 11 March
>> from 15:00-16:00 local time. This will conflict with the NCUC Membership
>> session. Would the NCSG EC & PC like to send a small contingent (similar to
>> what is happening with the GAC) to meet with the SSAC during this time they
>> have available? Please respond ASAP so we can confirm with SSAC.
>>
>>
>>
>> Thanks!
>>
>> *Andrea Glandon*
>>
>> Policy Operations Sr. Coordinator
>>
>> Internet Corporation for Assigned Names and Numbers (ICANN)
>>
>> *Skype ID:*  acglandon76
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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/20250115/33ca13d4/attachment.htm>

From pedrodeperdigaolana at gmail.com  Wed Jan 15 14:32:03 2025
From: pedrodeperdigaolana at gmail.com (=?UTF-8?Q?Pedro_de_Perdig=C3=A3o_Lana?=)
Date: Wed, 15 Jan 2025 09:32:03 -0300
Subject: [NCSG-PC] [NCSG-EC] RESPONSE REQUESTED-ICANN82 Meeting with SSAC
In-Reply-To: <CALUKJaXdNAHSCHCgfvgv-s3_V2bJystZ6XPCd4scFB2jSgX2yg@mail.gmail.com>
References: <777177F5-B7E4-45E9-B444-4917BB3B8D44@icann.org>
 <CAGSP6RThsp+2-QM2ivr5Fc0SDHqRvoDxoLDD=sW7cC5J7dAP6Q@mail.gmail.com>
 <CALUKJaXdNAHSCHCgfvgv-s3_V2bJystZ6XPCd4scFB2jSgX2yg@mail.gmail.com>
Message-ID: <CAGSP6RSwc_zACbbm7uS7bju50xKvrWH_kk8WKe0i5-p1OD0iEw@mail.gmail.com>

Hi Amin,

Considering the comments made by Andrea before, I believe this is not a
possibility, at least for this ICANN meeting. The option provided was the
only viable one, so we have the alternative of doing it with part of our
group, or postponing.

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 qua., 15 de jan. de 2025 ?s 07:12, Amin Hacha via NCSG-EC <
ncsg-ec at lists.ncsg.is> escreveu:

> Hi Andrea and everyone,
>
> Thank you for the update, Andrea.
> I like to ensure the highest possible attendance at both meetings, with my
> priority on the NCUC membership session. To avoid any scheduling conflicts,
> I would prefer if we explore again alternative timing options.
>
> I suggest we approach SSAC again to request a different time.
> Best regards,
> Amin
>
>
>
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> Virus-free.www.avg.com
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> <#m_-5847350895821691678_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Tue, Jan 14, 2025 at 5:39?PM Pedro de Perdig?o Lana via NCSG-EC <
> ncsg-ec at lists.ncsg.is> wrote:
>
>> Hi Andrea,
>>
>> No problem on my side, considering we are doing something similar with
>> NPOC regarding the GAC meeting. However, I would already give my apologies
>> in advance, considering I have to be at the NCUC Membership meeting.
>>
>> 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 ter., 14 de jan. de 2025 ?s 11:36, Andrea Glandon via NCSG-EC <
>> ncsg-ec at lists.ncsg.is> escreveu:
>>
>>> Hello all,
>>>
>>>
>>>
>>> The SSAC is available for a meeting during ICANN82 on Tuesday, 11 March
>>> from 15:00-16:00 local time. This will conflict with the NCUC Membership
>>> session. Would the NCSG EC & PC like to send a small contingent (similar to
>>> what is happening with the GAC) to meet with the SSAC during this time they
>>> have available? Please respond ASAP so we can confirm with SSAC.
>>>
>>>
>>>
>>> Thanks!
>>>
>>> *Andrea Glandon*
>>>
>>> Policy Operations Sr. Coordinator
>>>
>>> Internet Corporation for Assigned Names and Numbers (ICANN)
>>>
>>> *Skype ID:*  acglandon76
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>
> _______________________________________________
> 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/20250115/3e0cd494/attachment.htm>

From andrea.glandon at icann.org  Wed Jan 15 18:12:59 2025
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Wed, 15 Jan 2025 16:12:59 +0000
Subject: [NCSG-PC] [Ext] Re: [NCSG-EC] RESPONSE REQUESTED-ICANN82
 Meeting with SSAC
In-Reply-To: <CAH5sThnq6xKvSyN0shKJmYsocA7hnPsWo_M5wck+z_-k_n8Eeg@mail.gmail.com>
References: <777177F5-B7E4-45E9-B444-4917BB3B8D44@icann.org>
 <CAH5sThnq6xKvSyN0shKJmYsocA7hnPsWo_M5wck+z_-k_n8Eeg@mail.gmail.com>
Message-ID: <7B75D070-7F36-418E-AA19-368CFC75E242@icann.org>

Hello all,

I am not feeling well today, but I did want to jump in for a moment. I will have to check with Kathy to see if SSAC is available during the NCSG Membership session. Please let me know ASAP if I should do this.

Kind Regards,
Andrea


From: Rafik Dammak <rafik.dammak at gmail.com>
Date: Wednesday, January 15, 2025 at 08:19
To: Andrea Glandon <andrea.glandon at icann.org>
Cc: NCSG EC <ncsg-ec at lists.ncsg.is>, ncsg-pc <ncsg-pc at lists.ncsg.is>
Subject: [Ext] Re: [NCSG-EC] RESPONSE REQUESTED-ICANN82 Meeting with SSAC

Hi everyone,

I think one workaround is to allocate 30min slot during NCSG membership session to meet with SSAC. In future, we can try to alternate for some ACs as we have limitations on finding timeslots while we will have regular sessions with CSG and CPH.

Best,

Rafik

On Tue, Jan 14, 2025, 23:36 Andrea Glandon via NCSG-EC <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>> wrote:
Hello all,

The SSAC is available for a meeting during ICANN82 on Tuesday, 11 March from 15:00-16:00 local time. This will conflict with the NCUC Membership session. Would the NCSG EC & PC like to send a small contingent (similar to what is happening with the GAC) to meet with the SSAC during this time they have available? Please respond ASAP so we can confirm with SSAC.

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



_______________________________________________
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!6951b0B0-7h1OOFN0vzCpNe4ki4dU6MCqOByn1dkTRj7Egd9WdTRZOjzdgkutZ0iRUwju_seKu6D9On18QB2FKjesiOSwgQ$>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250115/06e4df0c/attachment.htm>

From julf at julf.com  Wed Jan 15 18:20:11 2025
From: julf at julf.com (Johan Helsingius)
Date: Wed, 15 Jan 2025 17:20:11 +0100
Subject: [NCSG-PC] [Ext] Re: [NCSG-EC] RESPONSE REQUESTED-ICANN82
 Meeting with SSAC
In-Reply-To: <7B75D070-7F36-418E-AA19-368CFC75E242@icann.org>
References: <777177F5-B7E4-45E9-B444-4917BB3B8D44@icann.org>
 <CAH5sThnq6xKvSyN0shKJmYsocA7hnPsWo_M5wck+z_-k_n8Eeg@mail.gmail.com>
 <7B75D070-7F36-418E-AA19-368CFC75E242@icann.org>
Message-ID: <7f077629-a032-4c72-8916-d274168b715e@julf.com>

On 15/01/2025 17:12, Andrea Glandon wrote:
> I am not feeling well today

Sorry to hear! Wishing you quick recovery - take care
of yourself!

	Julf



From wisdom.dk at gmail.com  Wed Jan 15 20:36:11 2025
From: wisdom.dk at gmail.com (Wisdom Donkor)
Date: Wed, 15 Jan 2025 18:36:11 +0000
Subject: [NCSG-PC] [Ext] Re: [NCSG-EC] RESPONSE REQUESTED-ICANN82
 Meeting with SSAC
In-Reply-To: <7B75D070-7F36-418E-AA19-368CFC75E242@icann.org>
References: <777177F5-B7E4-45E9-B444-4917BB3B8D44@icann.org>
 <CAH5sThnq6xKvSyN0shKJmYsocA7hnPsWo_M5wck+z_-k_n8Eeg@mail.gmail.com>
 <7B75D070-7F36-418E-AA19-368CFC75E242@icann.org>
Message-ID: <CAAU+vPFcsc8PJQb_W3uaF2m0Sf_CWw5uoB0DOo5FGNUPhfZBjg@mail.gmail.com>

Sorry to hear you're not feeling well. You need some rest. I have no issue
with checking on Kathy, but let's hear what Rafik has to say.


On Wed, 15 Jan 2025, 4:13?pm Andrea Glandon, <andrea.glandon at icann.org>
wrote:

> Hello all,
>
>
>
> I am not feeling well today, but I did want to jump in for a moment. I
> will have to check with Kathy to see if SSAC is available during the NCSG
> Membership session. Please let me know ASAP if I should do this.
>
>
>
> Kind Regards,
>
> Andrea
>
>
>
>
>
> *From: *Rafik Dammak <rafik.dammak at gmail.com>
> *Date: *Wednesday, January 15, 2025 at 08:19
> *To: *Andrea Glandon <andrea.glandon at icann.org>
> *Cc: *NCSG EC <ncsg-ec at lists.ncsg.is>, ncsg-pc <ncsg-pc at lists.ncsg.is>
> *Subject: *[Ext] Re: [NCSG-EC] RESPONSE REQUESTED-ICANN82 Meeting with
> SSAC
>
>
>
> Hi everyone,
>
>
>
> I think one workaround is to allocate 30min slot during NCSG membership
> session to meet with SSAC. In future, we can try to alternate for some ACs
> as we have limitations on finding timeslots while we will have regular
> sessions with CSG and CPH.
>
>
>
> Best,
>
>
>
> Rafik
>
>
>
> On Tue, Jan 14, 2025, 23:36 Andrea Glandon via NCSG-EC <
> ncsg-ec at lists.ncsg.is> wrote:
>
> Hello all,
>
>
>
> The SSAC is available for a meeting during ICANN82 on Tuesday, 11 March
> from 15:00-16:00 local time. This will conflict with the NCUC Membership
> session. Would the NCSG EC & PC like to send a small contingent (similar to
> what is happening with the GAC) to meet with the SSAC during this time they
> have available? Please respond ASAP so we can confirm with SSAC.
>
>
>
> Thanks!
>
> *Andrea Glandon*
>
> Policy Operations Sr. Coordinator
>
> Internet Corporation for Assigned Names and Numbers (ICANN)
>
> *Skype ID:*  acglandon76
>
>
>
>
>
>
>
> _______________________________________________
> NCSG-EC mailing list
> 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!6951b0B0-7h1OOFN0vzCpNe4ki4dU6MCqOByn1dkTRj7Egd9WdTRZOjzdgkutZ0iRUwju_seKu6D9On18QB2FKjesiOSwgQ$>
>
> _______________________________________________
> 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/20250115/a99aa353/attachment.htm>

From rafik.dammak at gmail.com  Wed Jan 15 23:12:09 2025
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Thu, 16 Jan 2025 06:12:09 +0900
Subject: [NCSG-PC] [Ext] Re: [NCSG-EC] RESPONSE REQUESTED-ICANN82
 Meeting with SSAC
In-Reply-To: <7B75D070-7F36-418E-AA19-368CFC75E242@icann.org>
References: <777177F5-B7E4-45E9-B444-4917BB3B8D44@icann.org>
 <CAH5sThnq6xKvSyN0shKJmYsocA7hnPsWo_M5wck+z_-k_n8Eeg@mail.gmail.com>
 <7B75D070-7F36-418E-AA19-368CFC75E242@icann.org>
Message-ID: <CAH5sThn6VZ9GxdbSLD=+YawaVafZj2WfhD+mAy3qikDNhT7QqQ@mail.gmail.com>

Hi Andrea,

Please go ahead and reach out to Kathy with the proposal.


Best,

Rafik

On Thu, Jan 16, 2025, 01:13 Andrea Glandon <andrea.glandon at icann.org> wrote:

> Hello all,
>
>
>
> I am not feeling well today, but I did want to jump in for a moment. I
> will have to check with Kathy to see if SSAC is available during the NCSG
> Membership session. Please let me know ASAP if I should do this.
>
>
>
> Kind Regards,
>
> Andrea
>
>
>
>
>
> *From: *Rafik Dammak <rafik.dammak at gmail.com>
> *Date: *Wednesday, January 15, 2025 at 08:19
> *To: *Andrea Glandon <andrea.glandon at icann.org>
> *Cc: *NCSG EC <ncsg-ec at lists.ncsg.is>, ncsg-pc <ncsg-pc at lists.ncsg.is>
> *Subject: *[Ext] Re: [NCSG-EC] RESPONSE REQUESTED-ICANN82 Meeting with
> SSAC
>
>
>
> Hi everyone,
>
>
>
> I think one workaround is to allocate 30min slot during NCSG membership
> session to meet with SSAC. In future, we can try to alternate for some ACs
> as we have limitations on finding timeslots while we will have regular
> sessions with CSG and CPH.
>
>
>
> Best,
>
>
>
> Rafik
>
>
>
> On Tue, Jan 14, 2025, 23:36 Andrea Glandon via NCSG-EC <
> ncsg-ec at lists.ncsg.is> wrote:
>
> Hello all,
>
>
>
> The SSAC is available for a meeting during ICANN82 on Tuesday, 11 March
> from 15:00-16:00 local time. This will conflict with the NCUC Membership
> session. Would the NCSG EC & PC like to send a small contingent (similar to
> what is happening with the GAC) to meet with the SSAC during this time they
> have available? Please respond ASAP so we can confirm with SSAC.
>
>
>
> Thanks!
>
> *Andrea Glandon*
>
> Policy Operations Sr. Coordinator
>
> Internet Corporation for Assigned Names and Numbers (ICANN)
>
> *Skype ID:*  acglandon76
>
>
>
>
>
>
>
> _______________________________________________
> NCSG-EC mailing list
> 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!6951b0B0-7h1OOFN0vzCpNe4ki4dU6MCqOByn1dkTRj7Egd9WdTRZOjzdgkutZ0iRUwju_seKu6D9On18QB2FKjesiOSwgQ$>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250116/ead63231/attachment.htm>

From rafik.dammak at gmail.com  Thu Jan 16 04:12:10 2025
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Thu, 16 Jan 2025 11:12:10 +0900
Subject: [NCSG-PC] Topics/Agenda for NCPH session
Message-ID: <CAH5sThkdECWZJH545Tc7z94-7fZHvnET_TVfU5c9KgfAa0qzcg@mail.gmail.com>

Hi all,

In order to prepare for the session with CSG, do you have any suggestions
for the agenda and desired outcomes of the meeting. We can build on the
topics we discussed on day 0 in Istanbul if there is any particular
follow-up we would like. For policy topics, I assume it is in an area where
there are several divergences on some issues.
I think one topic to share an update on is the procedure for board seat 14.

Best,

Rafik
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250116/7be9bdcd/attachment.htm>

From pedrodeperdigaolana at gmail.com  Wed Jan 15 21:04:26 2025
From: pedrodeperdigaolana at gmail.com (=?UTF-8?Q?Pedro_de_Perdig=C3=A3o_Lana?=)
Date: Wed, 15 Jan 2025 16:04:26 -0300
Subject: [NCSG-PC] [NCSG-EC] [Ext] Re: RESPONSE REQUESTED-ICANN82
 Meeting with SSAC
In-Reply-To: <CAAU+vPFcsc8PJQb_W3uaF2m0Sf_CWw5uoB0DOo5FGNUPhfZBjg@mail.gmail.com>
References: <777177F5-B7E4-45E9-B444-4917BB3B8D44@icann.org>
 <CAH5sThnq6xKvSyN0shKJmYsocA7hnPsWo_M5wck+z_-k_n8Eeg@mail.gmail.com>
 <7B75D070-7F36-418E-AA19-368CFC75E242@icann.org>
 <CAAU+vPFcsc8PJQb_W3uaF2m0Sf_CWw5uoB0DOo5FGNUPhfZBjg@mail.gmail.com>
Message-ID: <CAGSP6RTwV-bbF3dGs2+bUbjX8mu_eX-RPA3k7_rjCWQCo6+d0w@mail.gmail.com>

+1 Wisdom.

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 qua., 15 de jan. de 2025 ?s 15:37, Wisdom Donkor via NCSG-EC <
ncsg-ec at lists.ncsg.is> escreveu:

> Sorry to hear you're not feeling well. You need some rest. I have no issue
> with checking on Kathy, but let's hear what Rafik has to say.
>
>
> On Wed, 15 Jan 2025, 4:13?pm Andrea Glandon, <andrea.glandon at icann.org>
> wrote:
>
>> Hello all,
>>
>>
>>
>> I am not feeling well today, but I did want to jump in for a moment. I
>> will have to check with Kathy to see if SSAC is available during the NCSG
>> Membership session. Please let me know ASAP if I should do this.
>>
>>
>>
>> Kind Regards,
>>
>> Andrea
>>
>>
>>
>>
>>
>> *From: *Rafik Dammak <rafik.dammak at gmail.com>
>> *Date: *Wednesday, January 15, 2025 at 08:19
>> *To: *Andrea Glandon <andrea.glandon at icann.org>
>> *Cc: *NCSG EC <ncsg-ec at lists.ncsg.is>, ncsg-pc <ncsg-pc at lists.ncsg.is>
>> *Subject: *[Ext] Re: [NCSG-EC] RESPONSE REQUESTED-ICANN82 Meeting with
>> SSAC
>>
>>
>>
>> Hi everyone,
>>
>>
>>
>> I think one workaround is to allocate 30min slot during NCSG membership
>> session to meet with SSAC. In future, we can try to alternate for some ACs
>> as we have limitations on finding timeslots while we will have regular
>> sessions with CSG and CPH.
>>
>>
>>
>> Best,
>>
>>
>>
>> Rafik
>>
>>
>>
>> On Tue, Jan 14, 2025, 23:36 Andrea Glandon via NCSG-EC <
>> ncsg-ec at lists.ncsg.is> wrote:
>>
>> Hello all,
>>
>>
>>
>> The SSAC is available for a meeting during ICANN82 on Tuesday, 11 March
>> from 15:00-16:00 local time. This will conflict with the NCUC Membership
>> session. Would the NCSG EC & PC like to send a small contingent (similar to
>> what is happening with the GAC) to meet with the SSAC during this time they
>> have available? Please respond ASAP so we can confirm with SSAC.
>>
>>
>>
>> Thanks!
>>
>> *Andrea Glandon*
>>
>> Policy Operations Sr. Coordinator
>>
>> Internet Corporation for Assigned Names and Numbers (ICANN)
>>
>> *Skype ID:*  acglandon76
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> NCSG-EC mailing list
>> 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!6951b0B0-7h1OOFN0vzCpNe4ki4dU6MCqOByn1dkTRj7Egd9WdTRZOjzdgkutZ0iRUwju_seKu6D9On18QB2FKjesiOSwgQ$>
>>
>> _______________________________________________
>>
> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
> _______________________________________________
> 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/20250115/b80452df/attachment.htm>

From andrea.glandon at icann.org  Thu Jan 16 15:41:36 2025
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Thu, 16 Jan 2025 13:41:36 +0000
Subject: [NCSG-PC] [Ext] Re: [NCSG-EC] RESPONSE REQUESTED-ICANN82
 Meeting with SSAC
In-Reply-To: <CAAU+vPFcsc8PJQb_W3uaF2m0Sf_CWw5uoB0DOo5FGNUPhfZBjg@mail.gmail.com>
References: <777177F5-B7E4-45E9-B444-4917BB3B8D44@icann.org>
 <CAH5sThnq6xKvSyN0shKJmYsocA7hnPsWo_M5wck+z_-k_n8Eeg@mail.gmail.com>
 <7B75D070-7F36-418E-AA19-368CFC75E242@icann.org>
 <CAAU+vPFcsc8PJQb_W3uaF2m0Sf_CWw5uoB0DOo5FGNUPhfZBjg@mail.gmail.com>
Message-ID: <EE9B13E4-0C92-4A3A-AC02-25487617ED74@icann.org>

Thank you, all!

I will check in with Kathy to see if SSAC joining for 30 min of the NCSG Membership session is possible.

Kind Regards,
Andrea


From: Wisdom Donkor <wisdom.dk at gmail.com>
Date: Wednesday, January 15, 2025 at 12:38
To: Andrea Glandon <andrea.glandon at icann.org>
Cc: Rafik Dammak <rafik.dammak at gmail.com>, ncsg-pc <ncsg-pc at lists.ncsg.is>, NCSG EC <ncsg-ec at lists.ncsg.is>
Subject: Re: [NCSG-PC] [Ext] Re: [NCSG-EC] RESPONSE REQUESTED-ICANN82 Meeting with SSAC


Sorry to hear you're not feeling well. You need some rest. I have no issue with checking on Kathy, but let's hear what Rafik has to say.


On Wed, 15 Jan 2025, 4:13?pm Andrea Glandon, <andrea.glandon at icann.org<mailto:andrea.glandon at icann.org>> wrote:
Hello all,

I am not feeling well today, but I did want to jump in for a moment. I will have to check with Kathy to see if SSAC is available during the NCSG Membership session. Please let me know ASAP if I should do this.

Kind Regards,
Andrea


From: Rafik Dammak <rafik.dammak at gmail.com<mailto:rafik.dammak at gmail.com>>
Date: Wednesday, January 15, 2025 at 08:19
To: Andrea Glandon <andrea.glandon at icann.org<mailto:andrea.glandon at icann.org>>
Cc: NCSG EC <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>>, ncsg-pc <ncsg-pc at lists.ncsg.is<mailto:ncsg-pc at lists.ncsg.is>>
Subject: [Ext] Re: [NCSG-EC] RESPONSE REQUESTED-ICANN82 Meeting with SSAC

Hi everyone,

I think one workaround is to allocate 30min slot during NCSG membership session to meet with SSAC. In future, we can try to alternate for some ACs as we have limitations on finding timeslots while we will have regular sessions with CSG and CPH.

Best,

Rafik

On Tue, Jan 14, 2025, 23:36 Andrea Glandon via NCSG-EC <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>> wrote:
Hello all,

The SSAC is available for a meeting during ICANN82 on Tuesday, 11 March from 15:00-16:00 local time. This will conflict with the NCUC Membership session. Would the NCSG EC & PC like to send a small contingent (similar to what is happening with the GAC) to meet with the SSAC during this time they have available? Please respond ASAP so we can confirm with SSAC.

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



_______________________________________________
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!6951b0B0-7h1OOFN0vzCpNe4ki4dU6MCqOByn1dkTRj7Egd9WdTRZOjzdgkutZ0iRUwju_seKu6D9On18QB2FKjesiOSwgQ$>
_______________________________________________
NCSG-PC mailing list
NCSG-PC at lists.ncsg.is<mailto:NCSG-PC at lists.ncsg.is>
https://lists.ncsg.is/mailman/listinfo/ncsg-pc [lists.ncsg.is]<https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-pc__;!!PtGJab4!5ZTnMQK0E-jDLEQFrPNV1F2kAEE6qxlZwqSJVi_SQWcC_bi9ULP9lbV5zxCZuH6dy_LrW5idaXcXRdQ1HxS33aetYyk$>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250116/688d6c94/attachment.htm>

From andrea.glandon at icann.org  Thu Jan 16 16:17:05 2025
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Thu, 16 Jan 2025 14:17:05 +0000
Subject: [NCSG-PC] [Ext] Re: [NCSG-EC] RESPONSE REQUESTED-ICANN82
 Meeting with SSAC
In-Reply-To: <CAH5sThn6VZ9GxdbSLD=+YawaVafZj2WfhD+mAy3qikDNhT7QqQ@mail.gmail.com>
References: <777177F5-B7E4-45E9-B444-4917BB3B8D44@icann.org>
 <CAH5sThnq6xKvSyN0shKJmYsocA7hnPsWo_M5wck+z_-k_n8Eeg@mail.gmail.com>
 <7B75D070-7F36-418E-AA19-368CFC75E242@icann.org>
 <CAH5sThn6VZ9GxdbSLD=+YawaVafZj2WfhD+mAy3qikDNhT7QqQ@mail.gmail.com>
Message-ID: <46F6715F-771A-4743-9DFD-ECCEEA7B018D@icann.org>

Hello all!

SSAC is not available during the NCSG membership session. Shall I move forward with original offer to join the SSAC from 15:00-16:00 which will conflict with the NCUC membership session?

Thanks!
Kind Regards,
Andrea


From: Rafik Dammak <rafik.dammak at gmail.com>
Date: Wednesday, January 15, 2025 at 15:12
To: Andrea Glandon <andrea.glandon at icann.org>
Cc: NCSG EC <ncsg-ec at lists.ncsg.is>, ncsg-pc <ncsg-pc at lists.ncsg.is>
Subject: Re: [Ext] Re: [NCSG-EC] RESPONSE REQUESTED-ICANN82 Meeting with SSAC

Hi Andrea,

Please go ahead and reach out to Kathy with the proposal.


Best,

Rafik

On Thu, Jan 16, 2025, 01:13 Andrea Glandon <andrea.glandon at icann.org<mailto:andrea.glandon at icann.org>> wrote:
Hello all,

I am not feeling well today, but I did want to jump in for a moment. I will have to check with Kathy to see if SSAC is available during the NCSG Membership session. Please let me know ASAP if I should do this.

Kind Regards,
Andrea


From: Rafik Dammak <rafik.dammak at gmail.com<mailto:rafik.dammak at gmail.com>>
Date: Wednesday, January 15, 2025 at 08:19
To: Andrea Glandon <andrea.glandon at icann.org<mailto:andrea.glandon at icann.org>>
Cc: NCSG EC <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>>, ncsg-pc <ncsg-pc at lists.ncsg.is<mailto:ncsg-pc at lists.ncsg.is>>
Subject: [Ext] Re: [NCSG-EC] RESPONSE REQUESTED-ICANN82 Meeting with SSAC

Hi everyone,

I think one workaround is to allocate 30min slot during NCSG membership session to meet with SSAC. In future, we can try to alternate for some ACs as we have limitations on finding timeslots while we will have regular sessions with CSG and CPH.

Best,

Rafik

On Tue, Jan 14, 2025, 23:36 Andrea Glandon via NCSG-EC <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>> wrote:
Hello all,

The SSAC is available for a meeting during ICANN82 on Tuesday, 11 March from 15:00-16:00 local time. This will conflict with the NCUC Membership session. Would the NCSG EC & PC like to send a small contingent (similar to what is happening with the GAC) to meet with the SSAC during this time they have available? Please respond ASAP so we can confirm with SSAC.

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



_______________________________________________
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!6951b0B0-7h1OOFN0vzCpNe4ki4dU6MCqOByn1dkTRj7Egd9WdTRZOjzdgkutZ0iRUwju_seKu6D9On18QB2FKjesiOSwgQ$>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250116/ed1b9a03/attachment.htm>

From rafik.dammak at gmail.com  Thu Jan 16 23:55:26 2025
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Fri, 17 Jan 2025 06:55:26 +0900
Subject: [NCSG-PC] [NCSG-EC] [Ext] Re: RESPONSE REQUESTED-ICANN82
 Meeting with SSAC
In-Reply-To: <46F6715F-771A-4743-9DFD-ECCEEA7B018D@icann.org>
References: <777177F5-B7E4-45E9-B444-4917BB3B8D44@icann.org>
 <CAH5sThnq6xKvSyN0shKJmYsocA7hnPsWo_M5wck+z_-k_n8Eeg@mail.gmail.com>
 <7B75D070-7F36-418E-AA19-368CFC75E242@icann.org>
 <CAH5sThn6VZ9GxdbSLD=+YawaVafZj2WfhD+mAy3qikDNhT7QqQ@mail.gmail.com>
 <46F6715F-771A-4743-9DFD-ECCEEA7B018D@icann.org>
Message-ID: <CAH5sTh=9kjDGdtYxyJXhS8-M8ntbV9J4P7o85h1uhkz9pyTK=Q@mail.gmail.com>

Hi Andrea,

I think we can drop meeting with SSAC this time and suggest meeting in
June. While for the GAC, we tried to accommodate and have a small group to
go for 30 min, this can be overstretching to miss a whole session.

Best,

Rafik

On Thu, Jan 16, 2025, 23:17 Andrea Glandon via NCSG-EC <
ncsg-ec at lists.ncsg.is> wrote:

> Hello all!
>
>
>
> SSAC is not available during the NCSG membership session. Shall I move
> forward with original offer to join the SSAC from 15:00-16:00 which will
> conflict with the NCUC membership session?
>
>
>
> Thanks!
>
> Kind Regards,
>
> Andrea
>
>
>
>
>
> *From: *Rafik Dammak <rafik.dammak at gmail.com>
> *Date: *Wednesday, January 15, 2025 at 15:12
> *To: *Andrea Glandon <andrea.glandon at icann.org>
> *Cc: *NCSG EC <ncsg-ec at lists.ncsg.is>, ncsg-pc <ncsg-pc at lists.ncsg.is>
> *Subject: *Re: [Ext] Re: [NCSG-EC] RESPONSE REQUESTED-ICANN82 Meeting
> with SSAC
>
>
>
> Hi Andrea,
>
>
>
> Please go ahead and reach out to Kathy with the proposal.
>
>
>
>
>
> Best,
>
>
>
> Rafik
>
>
>
> On Thu, Jan 16, 2025, 01:13 Andrea Glandon <andrea.glandon at icann.org>
> wrote:
>
> Hello all,
>
>
>
> I am not feeling well today, but I did want to jump in for a moment. I
> will have to check with Kathy to see if SSAC is available during the NCSG
> Membership session. Please let me know ASAP if I should do this.
>
>
>
> Kind Regards,
>
> Andrea
>
>
>
>
>
> *From: *Rafik Dammak <rafik.dammak at gmail.com>
> *Date: *Wednesday, January 15, 2025 at 08:19
> *To: *Andrea Glandon <andrea.glandon at icann.org>
> *Cc: *NCSG EC <ncsg-ec at lists.ncsg.is>, ncsg-pc <ncsg-pc at lists.ncsg.is>
> *Subject: *[Ext] Re: [NCSG-EC] RESPONSE REQUESTED-ICANN82 Meeting with
> SSAC
>
>
>
> Hi everyone,
>
>
>
> I think one workaround is to allocate 30min slot during NCSG membership
> session to meet with SSAC. In future, we can try to alternate for some ACs
> as we have limitations on finding timeslots while we will have regular
> sessions with CSG and CPH.
>
>
>
> Best,
>
>
>
> Rafik
>
>
>
> On Tue, Jan 14, 2025, 23:36 Andrea Glandon via NCSG-EC <
> ncsg-ec at lists.ncsg.is> wrote:
>
> Hello all,
>
>
>
> The SSAC is available for a meeting during ICANN82 on Tuesday, 11 March
> from 15:00-16:00 local time. This will conflict with the NCUC Membership
> session. Would the NCSG EC & PC like to send a small contingent (similar to
> what is happening with the GAC) to meet with the SSAC during this time they
> have available? Please respond ASAP so we can confirm with SSAC.
>
>
>
> Thanks!
>
> *Andrea Glandon*
>
> Policy Operations Sr. Coordinator
>
> Internet Corporation for Assigned Names and Numbers (ICANN)
>
> *Skype ID:*  acglandon76
>
>
>
>
>
>
>
> _______________________________________________
> NCSG-EC mailing list
> 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!6951b0B0-7h1OOFN0vzCpNe4ki4dU6MCqOByn1dkTRj7Egd9WdTRZOjzdgkutZ0iRUwju_seKu6D9On18QB2FKjesiOSwgQ$>
>
> _______________________________________________
> 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/20250117/6151d728/attachment.htm>

From andrea.glandon at icann.org  Fri Jan 17 03:12:47 2025
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Fri, 17 Jan 2025 01:12:47 +0000
Subject: [NCSG-PC] [NCSG-EC] [Ext] Re: RESPONSE REQUESTED-ICANN82
 Meeting with SSAC
In-Reply-To: <CAH5sTh=9kjDGdtYxyJXhS8-M8ntbV9J4P7o85h1uhkz9pyTK=Q@mail.gmail.com>
References: <777177F5-B7E4-45E9-B444-4917BB3B8D44@icann.org>
 <CAH5sThnq6xKvSyN0shKJmYsocA7hnPsWo_M5wck+z_-k_n8Eeg@mail.gmail.com>
 <7B75D070-7F36-418E-AA19-368CFC75E242@icann.org>
 <CAH5sThn6VZ9GxdbSLD=+YawaVafZj2WfhD+mAy3qikDNhT7QqQ@mail.gmail.com>
 <46F6715F-771A-4743-9DFD-ECCEEA7B018D@icann.org>
 <CAH5sTh=9kjDGdtYxyJXhS8-M8ntbV9J4P7o85h1uhkz9pyTK=Q@mail.gmail.com>
Message-ID: <A99E075F-8E67-4627-B0EC-F1BA97C7A9E9@icann.org>

Thank you, Rafik. I will let Kathy know.

Kind Regards,
Andrea


From: Rafik Dammak <rafik.dammak at gmail.com>
Date: Thursday, January 16, 2025 at 15:56
To: Andrea Glandon <andrea.glandon at icann.org>
Cc: ncsg-pc <ncsg-pc at lists.ncsg.is>, NCSG EC <ncsg-ec at lists.ncsg.is>
Subject: Re: [NCSG-EC] [Ext] Re: RESPONSE REQUESTED-ICANN82 Meeting with SSAC

Hi Andrea,

I think we can drop meeting with SSAC this time and suggest meeting in June. While for the GAC, we tried to accommodate and have a small group to go for 30 min, this can be overstretching to miss a whole session.

Best,

Rafik

On Thu, Jan 16, 2025, 23:17 Andrea Glandon via NCSG-EC <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>> wrote:
Hello all!

SSAC is not available during the NCSG membership session. Shall I move forward with original offer to join the SSAC from 15:00-16:00 which will conflict with the NCUC membership session?

Thanks!
Kind Regards,
Andrea


From: Rafik Dammak <rafik.dammak at gmail.com<mailto:rafik.dammak at gmail.com>>
Date: Wednesday, January 15, 2025 at 15:12
To: Andrea Glandon <andrea.glandon at icann.org<mailto:andrea.glandon at icann.org>>
Cc: NCSG EC <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>>, ncsg-pc <ncsg-pc at lists.ncsg.is<mailto:ncsg-pc at lists.ncsg.is>>
Subject: Re: [Ext] Re: [NCSG-EC] RESPONSE REQUESTED-ICANN82 Meeting with SSAC

Hi Andrea,

Please go ahead and reach out to Kathy with the proposal.


Best,

Rafik

On Thu, Jan 16, 2025, 01:13 Andrea Glandon <andrea.glandon at icann.org<mailto:andrea.glandon at icann.org>> wrote:
Hello all,

I am not feeling well today, but I did want to jump in for a moment. I will have to check with Kathy to see if SSAC is available during the NCSG Membership session. Please let me know ASAP if I should do this.

Kind Regards,
Andrea


From: Rafik Dammak <rafik.dammak at gmail.com<mailto:rafik.dammak at gmail.com>>
Date: Wednesday, January 15, 2025 at 08:19
To: Andrea Glandon <andrea.glandon at icann.org<mailto:andrea.glandon at icann.org>>
Cc: NCSG EC <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>>, ncsg-pc <ncsg-pc at lists.ncsg.is<mailto:ncsg-pc at lists.ncsg.is>>
Subject: [Ext] Re: [NCSG-EC] RESPONSE REQUESTED-ICANN82 Meeting with SSAC

Hi everyone,

I think one workaround is to allocate 30min slot during NCSG membership session to meet with SSAC. In future, we can try to alternate for some ACs as we have limitations on finding timeslots while we will have regular sessions with CSG and CPH.

Best,

Rafik

On Tue, Jan 14, 2025, 23:36 Andrea Glandon via NCSG-EC <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>> wrote:
Hello all,

The SSAC is available for a meeting during ICANN82 on Tuesday, 11 March from 15:00-16:00 local time. This will conflict with the NCUC Membership session. Would the NCSG EC & PC like to send a small contingent (similar to what is happening with the GAC) to meet with the SSAC during this time they have available? Please respond ASAP so we can confirm with SSAC.

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



_______________________________________________
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!6951b0B0-7h1OOFN0vzCpNe4ki4dU6MCqOByn1dkTRj7Egd9WdTRZOjzdgkutZ0iRUwju_seKu6D9On18QB2FKjesiOSwgQ$>
_______________________________________________
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!55ZIUa7WfGnSX4CCmQ6fr093enFY9BBJgJOc9-Uy8XNd2DMXz86aIiTPXRAe3BEH6kl_oz1o3PyhYVpD4eWyyOjoeifK_54$>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250117/69bd281a/attachment.htm>

From rafik.dammak at gmail.com  Fri Jan 17 07:25:28 2025
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Fri, 17 Jan 2025 14:25:28 +0900
Subject: [NCSG-PC] [NCSG-EC] Topics/Agenda for NCPH session
In-Reply-To: <CAGSP6RTmyvk-_mpGt7Z+i42x6_MnaHBJjDP+Qh9mAkQ=-nR48g@mail.gmail.com>
References: <CAH5sThkdECWZJH545Tc7z94-7fZHvnET_TVfU5c9KgfAa0qzcg@mail.gmail.com>
 <CAGSP6RTmyvk-_mpGt7Z+i42x6_MnaHBJjDP+Qh9mAkQ=-nR48g@mail.gmail.com>
Message-ID: <CAH5sThm7rjCLoeUCtdC9ASjjLvq8pzoNBtEfG+BT=EdULP_UcA@mail.gmail.com>

Hi Pedro,

Thanks for the input, looking forward policy topics.
I think that topic is already part of a follow-up action items i.e
establish a discssuion group for researching. I also reminded CSG
leadership we should work on action items. I doubt we have too much to
discuss more about it other than just housekeeping topic.

Best,

Rafik

On Fri, Jan 17, 2025, 13:09 Pedro de Perdig?o Lana <
pedrodeperdigaolana at gmail.com> wrote:

> Hi Rafik, EC, PC,
>
> I will think of other policy topics in the following days, but, regarding
> administrative ones, the membership system seems to be an important one to
> advance a bit more, considering we now will have Tapani with us in this
> meeting.
>
> 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 qua., 15 de jan. de 2025 ?s 23:12, Rafik Dammak via NCSG-EC <
> ncsg-ec at lists.ncsg.is> escreveu:
>
>> Hi all,
>>
>> In order to prepare for the session with CSG, do you have any suggestions
>> for the agenda and desired outcomes of the meeting. We can build on the
>> topics we discussed on day 0 in Istanbul if there is any particular
>> follow-up we would like. For policy topics, I assume it is in an area where
>> there are several divergences on some issues.
>> I think one topic to share an update on is the procedure for board seat
>> 14.
>>
>> Best,
>>
>> Rafik
>> _______________________________________________
>> 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/20250117/92aca345/attachment.htm>

From mesumbeslin at gmail.com  Fri Jan 17 14:21:25 2025
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Fri, 17 Jan 2025 15:21:25 +0300
Subject: [NCSG-PC] Fwd: Expression of interest - SCCI
In-Reply-To: <47636938-5d2b-4752-8458-27aa6fa57c79@Julf.com>
References: <5C41E2E9-F9C6-4412-9B95-D8B990C44524@icann.org>
 <CAM8DdeUBjvXVupYdT8mF5Fb-S9TmojhJkkYzQRoVFXXqrjSBdw@mail.gmail.com>
 <47636938-5d2b-4752-8458-27aa6fa57c79@Julf.com>
Message-ID: <CAM8DdeWnX0d52SJdudDB-k9X7eskHwtAq6AzwLz6WqyUNhpNmQ@mail.gmail.com>

FYI

Warmly,
Tomslin

---------- Forwarded message ---------
From: Johan Helsingius <julf at julf.com>
Date: Wed, 8 Jan 2025, 15:44
Subject: Expression of interest - SCCI
To: Tomslin Samme-Nlar <mesumbeslin at gmail.com>
Cc: Rafik Dammak <rafik.dammak at gmail.com>, Andrea Glandon <
andrea.glandon at icann.org>


Dear Tomslin,

I hereby express my interest in representing NCSG on the Standing
Committee on Continuous Improvement.

I think that the SCCI will be one of the most important drivers of
possible change in GNSO constituency structures (and ICANN
constituencies in general) and that we should be represented
as strongly as possible.

As you know, I have experience of not only the GNSO but also other
parts of the ICANN community, and been involved with the GNSO
for more than 10 years, so I feel I might be able to help look
after NCSG interests in the SCCI.

With kind regards,

        Julf


On 07/01/2025 04:32, Tomslin Samme-Nlar wrote:
> Hi all,
>
> The PC is seeking two (2) non-councillor volunteers to appoint as NCSG
> representatives to 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). Please
> read the message below for further details.
>
> If you're interested, please send your expression of interest to me and
> copy the NCSG chair and Andrea before January 14th 2025.
>
> Warmly,
> Tomslin
>
>
> ---------- Forwarded message ---------
> From: *Devan Reed via council* <council at icann.org
> <mailto:council at icann.org>>
> Date: Tue, 7 Jan 2025 at 00:17
> Subject: [council] EXTENDED DEADLINE | Call for Volunteers for SCCI |
> Please Respond by 20 January
> To: GNSO Council List <council at gnso.icann.org
> <mailto:council at gnso.icann.org>>
> Cc: GNSO-Secs <gnso-secs at icann.org <mailto:gnso-secs at icann.org>>
>
>
> **GNSO community members who wish to join the Standing Committee should
> contact the GNSO Secretariat at_gnso-secs at icann.org <mailto:gnso-
> secs at icann.org>_by*_Monday, 20 January 2025._*____
>
> __ __
>
> *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 theCouncil Committee for
> Overseeing and Implementing Continuous Improvement (CCOICI) Framework
> [gnso.icann.org] <https://urldefense.com/v3/__https:/gnso.icann.org/
> sites/default/files/file/field-file-attach/continuous-improvement-
> oversight-implementation-framework-29jun21-en.pdf__;!!PtGJab4!-
>
Wq1P5mu6Quaq809ddH-8ls4oGohg5p20yS9KuwkZH6sJU6rUiDWejIoGblCkNUeF8Fwv5IrWxGz3RgscBe_Iho$>(last
updated 29 June 2021), which has now converted to a permanent standing
committee following theGNSO Council?s adoption of the charter [
gnso.icann.org] <
https://urldefense.com/v3/__https:/gnso.icann.org/en/council/resolutions/2020-current*202411__;Iw!!PtGJab4!-Wq1P5mu6Quaq809ddH-8ls4oGohg5p20yS9KuwkZH6sJU6rUiDWejIoGblCkNUeF8Fwv5IrWxGz3RgsEBcHu90$
>.____
>
> ____
>
> *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 thecharter [gnso.icann.org]
> <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/
> policy/2024/draft/scci-charter-draft-update-13nov24-en.pdf__;!!PtGJab4!-
>
Wq1P5mu6Quaq809ddH-8ls4oGohg5p20yS9KuwkZH6sJU6rUiDWejIoGblCkNUeF8Fwv5IrWxGz3Rgs5l4Bx-E$>,
as to avoid frequent edits and subsequent approvals. Previous efforts were
initiated by the Council, while other changes were accomplished through
Organizational Reviews anchored inArticle 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 thecharter [gnso.icann.org] <
https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy/2024/draft/scci-charter-draft-update-13nov24-en.pdf__;!!PtGJab4!-Wq1P5mu6Quaq809ddH-8ls4oGohg5p20yS9KuwkZH6sJU6rUiDWejIoGblCkNUeF8Fwv5IrWxGz3Rgs5l4Bx-E$>and
as new projects and/or assignments are distributed and in due course,
completed, they will be managed via theGNSO?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 ____
>       o One CPH Board seat #13 (1)____
>       o One NCPH Board seat #14 (1)____
>
>   * Nine Observers: ____
>       o One Council Chair (1)____
>       o 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 <mailto:gnso-
> secs at icann.org>_by*_Monday, 6 January 2025._**__**_Monday, 20 January
> 2025._*____
>
> **____
>
> *Background*____
>
> For more information and to better prepare for participation on this
> Standing Committee, please read itscharter [gnso.icann.org] <https://
> urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/
> policy/2024/draft/scci-charter-draft-update-13nov24-en.pdf__;!!PtGJab4!-
>
Wq1P5mu6Quaq809ddH-8ls4oGohg5p20yS9KuwkZH6sJU6rUiDWejIoGblCkNUeF8Fwv5IrWxGz3Rgs5l4Bx-E$>,
as well as visiting theCCOICI 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 <mailto:council at icann.org>
> To unsubscribe send an email to council-leave at icann.org <mailto: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 <https://www.icann.org/privacy/policy>) and the website Terms of
> Service (https://www.icann.org/privacy/tos <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/20250117/86a8cc0d/attachment.htm>

From mesumbeslin at gmail.com  Fri Jan 17 14:24:38 2025
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Fri, 17 Jan 2025 15:24:38 +0300
Subject: [NCSG-PC] Fwd: [council] Call for Volunteers for SCCI | Please
 Respond by 6 January
In-Reply-To: <CAH5sThm-zFzx84OL170A7_VzbEiZV54MG5_htGrJ55WQVRbjCA@mail.gmail.com>
References: <698C84A1-F28A-4430-A052-E39612BAD9F5@icann.org>
 <CAM8DdeV4EFNFj3ADbcKkwxDzr2djA-M3o5ngi0BATgYA-1zmEQ@mail.gmail.com>
 <CAH5sThmMjU0fqwR2DG_RtgU+abvLMxAO4gDwNKvK50R6wEK5yQ@mail.gmail.com>
 <847580910.2455633.1733000189859@mail.yahoo.com>
 <CAMeQZi11eFQWHt6BmJ8S_PNxnyp65AUTjOrSiFBGSLUTcBiZLQ@mail.gmail.com>
 <CAH5sThkv9o_sbDi2tqX=mENCZ-KJmv9tBtU5hJOLf=JgVkSx3Q@mail.gmail.com>
 <d312e640-4a76-417c-b836-20e5fd7dc0e9@Julf.com>
 <CAH5sThmUzaLU6Lmo3U7w3OekA4BdHZTJL9dytvAMTZHYMVRfoA@mail.gmail.com>
 <ce33c08b-1d58-492a-833b-3ee04b98ccad@Julf.com>
 <CAMeQZi0u2am4U-YaDW0KBAvBNgs-vbSNeZk_LfaWHjLqhp-=+Q@mail.gmail.com>
 <CAH5sThm-zFzx84OL170A7_VzbEiZV54MG5_htGrJ55WQVRbjCA@mail.gmail.com>
Message-ID: <CAM8DdeUhynya5awiiS7o83mdr_CXwNLc8v1GS9M8xGfmGBti8g@mail.gmail.com>

Hi all,

So, in addition to Manju and Peter who had volunteered, we received only 1
more expression of interest from Julf.

Since the required representation is 1 councillor + 2 Reps, I suppose all
three names can be sent.
Let me know if you have any concerns with this approach.

Warmly,
Tomslin

On Tue, 7 Jan 2025, 05:54 Rafik Dammak, <rafik.dammak at gmail.com> wrote:

> The deadline was extended to 20th Jan but I want to urge that we appoint
> asap and close this.
>
> Rafik
>
>
>
> Le mar. 7 janv. 2025 ? 10:51, ??? Manju Chen <manju at nii.org.tw> a ?crit :
>
>> Correct, Julf, as long as we have one council rep it's fine. And it's not
>> against the rules to have another NCSG rep that happens to also be a
>> councilor.
>>
>> Best,
>> Manju
>>
>>
>> On Mon, Jan 6, 2025 at 6:36?PM Johan Helsingius via NCSG-PC <
>> ncsg-pc at lists.ncsg.is> wrote:
>>
>>> I assume the reps can be, but don't have to be, councilors?
>>>
>>>         Julf
>>>
>>> On 06/01/2025 10:28, Rafik Dammak wrote:
>>> > Yes it is one councillor  and 2 reps
>>> >
>>> > Rafik
>>> >
>>> > On Mon, Jan 6, 2025, 17:57 Johan Helsingius via NCSG-PC <ncsg-
>>> > pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>> wrote:
>>> >
>>> >     Just checking, we are allowed 2+1 reps, right? If we need one
>>> more, I am
>>> >     happy to volunteer.
>>> >
>>> >              Julf
>>> >
>>> >
>>> >     On 04/01/2025 09:39, Rafik Dammak wrote:
>>> >      > Hi all,
>>> >      >
>>> >      > Can we confirm about the representative for SCCI. We got Manju
>>> >     and Juan
>>> >      > volunteering.
>>> >      >
>>> >      > Best,
>>> >      >
>>> >      > Rafik
>>> >      >
>>> >      >
>>> >      >
>>> >      > On Wed, Dec 11, 2024, 17:05 ??? Manju Chen <manju at nii.org.tw
>>> >     <mailto:manju at nii.org.tw>
>>> >      > <mailto:manju at nii.org.tw <mailto:manju at nii.org.tw>>> wrote:
>>> >      >
>>> >      >     Hi,
>>> >      >
>>> >      >     Happy to volunteer as the council rep for NCSG.
>>> >      >
>>> >      >     Best,
>>> >      >     Manju
>>> >      >
>>> >      >     On Sun, Dec 1, 2024 at 4:58?AM Juan Manuel Rojas via NCSG-PC
>>> >     <ncsg-
>>> >      > pc at lists.ncsg.is <mailto:pc at lists.ncsg.is> <mailto:ncsg-
>>> >     pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>>> wrote:
>>> >      >
>>> >      >         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 Colombia
>>> >      >         NPOC Chair - NCSG/GNSO
>>> >      >         M.Sc. Information Technology
>>> >      >
>>> >      >         Registered Linux User No.*533108.*
>>> >      > http://www.jmanurojas.com <http://www.jmanurojas.com> <http://
>>> >     www.jmanurojas.com <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
>>> >     <mailto:rafik.dammak at gmail.com> <mailto:rafik.dammak at gmail.com
>>> >     <mailto: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 <mailto:mesumbeslin at gmail.com>
>>> >     <mailto:mesumbeslin at gmail.com <mailto: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
>>> >     <mailto:council at icann.org>
>>> >      >             <mailto:council at icann.org <mailto: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
>>> >     <mailto:council at gnso.icann.org> <mailto:council at gnso.icann.org
>>> >     <mailto:council at gnso.icann.org>>
>>> >      >             <council at gnso.icann.org
>>> >     <mailto:council at gnso.icann.org> <mailto:council at gnso.icann.org
>>> >     <mailto:council at gnso.icann.org>>>
>>> >      >             Cc: GNSO-Secs <gnso-secs at icann.org <mailto:gnso-
>>> >     secs at icann.org> <mailto:gnso-secs at icann.org <mailto: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
>>> theCouncil
>>> >      >             Committee for Overseeing and Implementing Continuous
>>> >      >             Improvement (CCOICI) Framework <https://
>>> >     gnso.icann.org/ <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 theGNSO
>>> >      >             Council?s adoption of the charter <https://
>>> >     gnso.icann.org/ <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
>>> >      >             thecharter <https://gnso.icann.org/sites/default/
>>> >     files/ <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 inArticle 4.4. of the ICANN Bylaws
>>> <https://
>>> >      > www.icann.org/resources/pages/governance/bylaws- <http://
>>> >     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
>>> >      >             thecharter <https://gnso.icann.org/sites/default/
>>> >     files/ <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 theGNSO?s Program Management Tool (PMT)
>>> Suite
>>> >      >             <https://community.icann.org/pages/viewpage.action
>>> >     <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____
>>> >      >                   o One CPH Board seat #13 (1)____
>>> >      >                   o One NCPH Board seat #14 (1)____
>>> >      >
>>> >      >               * Nine Observers:____
>>> >      >                   o One Council Chair (1)____
>>> >      >                   o 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 <mailto:secs at icann.org> <mailto:gnso-
>>> >     secs at icann.org <mailto: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 itscharter
>>> >     <https://
>>> >      > gnso.icann.org/sites/default/files/policy/2024/draft/scci-
>>> >     <http://gnso.icann.org/sites/default/files/policy/2024/draft/scci-
>>> >
>>> >      >             charter-draft-update-13nov24-en.pdf>, as well as
>>> visiting
>>> >      >             theCCOICI wiki page <https://community.icann.org/
>>> >     display/ <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
>>> >     <mailto:council at icann.org>
>>> >      >             <mailto:council at icann.org <mailto:council at icann.org
>>> >>
>>> >      >             To unsubscribe send an email to council-
>>> >     leave at icann.org <mailto:council-leave at icann.org>
>>> >      >             <mailto:council-leave at icann.org <mailto: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
>>> >     <https://www.icann.org/privacy/policy> <https://
>>> >      > www.icann.org/privacy/policy <http://www.icann.org/privacy/
>>> >     policy>>) and the website Terms of
>>> >      >             Service (https://www.icann.org/privacy/tos
>>> <https://
>>> >     www.icann.org/privacy/tos> <https://
>>> >      > www.icann.org/privacy/tos <http://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 <mailto:NCSG-PC at lists.ncsg.is>
>>> >     <mailto:NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>>
>>> >      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>>> >     lists.ncsg.is/mailman/listinfo/ncsg-pc> <https://
>>> >      > lists.ncsg.is/mailman/listinfo/ncsg-pc <http://lists.ncsg.is/
>>> >     mailman/listinfo/ncsg-pc>>
>>> >      >
>>> >      >         _______________________________________________
>>> >      >         NCSG-PC mailing list
>>> >      > NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>> >     <mailto:NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>>
>>> >      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>>> >     lists.ncsg.is/mailman/listinfo/ncsg-pc> <https://
>>> >      > lists.ncsg.is/mailman/listinfo/ncsg-pc <http://lists.ncsg.is/
>>> >     mailman/listinfo/ncsg-pc>>
>>> >      >         _______________________________________________
>>> >      >         NCSG-PC mailing list
>>> >      > NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>> >     <mailto:NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>>
>>> >      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>>> >     lists.ncsg.is/mailman/listinfo/ncsg-pc> <https://
>>> >      > lists.ncsg.is/mailman/listinfo/ncsg-pc <http://lists.ncsg.is/
>>> >     mailman/listinfo/ncsg-pc>>
>>> >      >
>>> >      >
>>> >      > _______________________________________________
>>> >      > NCSG-PC mailing list
>>> >      > NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>> >      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>>> >     lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>> >
>>> >     _______________________________________________
>>> >     NCSG-PC mailing list
>>> >     NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>> >     https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>>> >     lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>> >
>>>
>>> _______________________________________________
>>> NCSG-PC mailing list
>>> NCSG-PC at lists.ncsg.is
>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>
>> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250117/32a51042/attachment.htm>

From pedrodeperdigaolana at gmail.com  Fri Jan 17 06:09:37 2025
From: pedrodeperdigaolana at gmail.com (=?UTF-8?Q?Pedro_de_Perdig=C3=A3o_Lana?=)
Date: Fri, 17 Jan 2025 01:09:37 -0300
Subject: [NCSG-PC] [NCSG-EC] Topics/Agenda for NCPH session
In-Reply-To: <CAH5sThkdECWZJH545Tc7z94-7fZHvnET_TVfU5c9KgfAa0qzcg@mail.gmail.com>
References: <CAH5sThkdECWZJH545Tc7z94-7fZHvnET_TVfU5c9KgfAa0qzcg@mail.gmail.com>
Message-ID: <CAGSP6RTmyvk-_mpGt7Z+i42x6_MnaHBJjDP+Qh9mAkQ=-nR48g@mail.gmail.com>

Hi Rafik, EC, PC,

I will think of other policy topics in the following days, but, regarding
administrative ones, the membership system seems to be an important one to
advance a bit more, considering we now will have Tapani with us in this
meeting.

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 qua., 15 de jan. de 2025 ?s 23:12, Rafik Dammak via NCSG-EC <
ncsg-ec at lists.ncsg.is> escreveu:

> Hi all,
>
> In order to prepare for the session with CSG, do you have any suggestions
> for the agenda and desired outcomes of the meeting. We can build on the
> topics we discussed on day 0 in Istanbul if there is any particular
> follow-up we would like. For policy topics, I assume it is in an area where
> there are several divergences on some issues.
> I think one topic to share an update on is the procedure for board seat 14.
>
> Best,
>
> Rafik
> _______________________________________________
> 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/20250117/657e38bb/attachment.htm>

From rafik.dammak at gmail.com  Tue Jan 21 03:32:07 2025
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Tue, 21 Jan 2025 10:32:07 +0900
Subject: [NCSG-PC] Fwd: [GNSO-SG-C-Leadership] Feedback Requested: How We
 Meet Community Group
In-Reply-To: <0100019474f81e50-a3ee597c-b322-405d-a31d-c79451fb9daa-000000@email.amazonses.com>
References: <4dc64fca6b7f4193a88bf10c5b076156@amazon.com>
 <0100019474f81e50-a3ee597c-b322-405d-a31d-c79451fb9daa-000000@email.amazonses.com>
Message-ID: <CAH5sThmh2oeMUTP=p7QTj7wA_JvTbRWps+U4D6MP3xk=AOX3jg@mail.gmail.com>

Hi all,

there is some update and request for input on "How to meet". We should
review the different options proposed in the strawman document.
I will share this later with larger NCSG membership and adding some context.

Best,

Rafik

---------- Forwarded message ---------
De : DiBiase, Gregory via GNSO-SG-C-Leadership <
gnso-sg-c-leadership at icann.org>
Date: sam. 18 janv. 2025 ? 00:53
Subject: [GNSO-SG-C-Leadership] Feedback Requested: How We Meet Community
Group
To: gnso-sg-c-leadership at icann.org <gnso-sg-c-leadership at icann.org>



   - *Attachments protected by Amazon: *
   - Updated Cost Data Related To ICANN Pu...copy.pdf
   <https://us-east-1.secure-attach.amazon.com/33f1c678-96e1-4015-8dfb-f02f5c2e62ff/fceed8c9-d3da-417d-aa8d-41514592e7f0>
|

   - How We Meet - Summary of Input from C...copy.pdf
   <https://us-east-1.secure-attach.amazon.com/33f1c678-96e1-4015-8dfb-f02f5c2e62ff/3c682e35-ece6-4488-826b-6517b486832b>
|

   - 2024 Cost Analysis of ICANN Travel & ...copy.pdf
   <https://us-east-1.secure-attach.amazon.com/33f1c678-96e1-4015-8dfb-f02f5c2e62ff/0e35facb-ecde-44e8-8d07-cc01120f2420>
|

   - 2022 - 2024 Cost Analysis of ICANN In...copy.pdf
   <https://us-east-1.secure-attach.amazon.com/33f1c678-96e1-4015-8dfb-f02f5c2e62ff/483dcc57-02b6-4c29-85a3-cce7bef43c46>
|

   - Final - Charter for the Community Gro...tegy.pdf
   <https://us-east-1.secure-attach.amazon.com/33f1c678-96e1-4015-8dfb-f02f5c2e62ff/e8ebf9cf-04c4-4fcc-8f90-4a16faef4b6a>
|

   - DRAFT - How We Meet Community Group R...Docs.pdf
   <https://us-east-1.secure-attach.amazon.com/33f1c678-96e1-4015-8dfb-f02f5c2e62ff/36b9c423-0e0f-446c-8325-34689df8deb9>
|

   - ICANN
   <https://us-east-1.secure-attach.amazon.com/33f1c678-96e1-4015-8dfb-f02f5c2e62ff/865639da-f3f1-4545-a8f4-79fd73d55a9d>
|

   - ATT00001.txt
   <https://us-east-1.secure-attach.amazon.com/33f1c678-96e1-4015-8dfb-f02f5c2e62ff/89a83194-2f45-4aaa-8be7-722c893a9aad>
|


Amazon has replaced the attachments in this email with download links.
Downloads will be available until February 16, 2025, 15:53 (UTC+00:00). Tell
us what you think
<https://amazonexteu.qualtrics.com/jfe/form/SV_ehuz6zGo8YnsRKK>
For more information click here
<https://docs.secure-attach.amazon.com/guide>

Dear SG/C Chairs,



I am hoping for your help gathering feedback on ICANN?s proposals for ?How
We Meet? (a.k.a. how to make ICANN?s meetings more cost effective).



As GNSO Chair, I?ve been tasked with gathering feedback on potential
recommendations that will go out to the Community for public comment.



Attached are a number of documents breaking down the cost of ICANN
meetings, but I think the most pertinent is one titled ?How We Meet
Community Group Report?. ICANN has labeled this document as a ?draft
strawman proposal? but it?s really a menu of options for reducing cost. I
think a good first step is for each SG/C to review these options and
provide feedback on:

   1. What options are missing?
   2. What options are unacceptable/problematic? (i.e., should not be put
   out for public comment).
   3. Do you have more granular feedback on the options provided?

I think this could give me a starting point for giving feedback to ICANN. I
have already flagged to ICANN that the GNSO is a diverse body and will
likely have disagreements, so a broader public comment on the ?strawman?
will be necessary.



Please provide any other thoughts you may have as this group starts their
work.



Thank You!



Greg







*From:* Alperen Eken via How-we-meet-2025 <how-we-meet-2025 at icann.org>
*Sent:* Tuesday, January 7, 2025 1:46 PM
*To:* how-we-meet-2025 at icann.org
*Subject:* [EXTERNAL] [How-We-Meet-2025] Agenda and Documents - Meeting #1
- How We Meet Community Group



*CAUTION*: This email originated from outside of the organization. Do not
click links or open attachments unless you can confirm the sender and know
the content is safe.



Dear all,



Happy New Year! I hope this message finds you well and that you?ve had a
wonderful start to 2025.



Next week, we will hold our first meeting to discuss updates to the ICANN
Meetings Strategy. This meeting is scheduled for:
Date: 13 January 2024
Time: 1700-1800 UTC



We?re looking forward to your participation and valuable contributions.
Please find attached the meeting agenda, some documents we prepared for
this group, and background documents that were previously shared with SOAC
Chairs:

   1. Meeting invitation ICS file
   2. Agenda
   3. Final - Charter for the Community Group for the Meeting Strategy
   4. Draft - How We Meet Community Group Report

Background Documents:

   5. How We Meet - Summary of Input from Community Groups
   6. Updated Cost Data Related to ICANN Public Meetings
   7. 2024 Cost Analysis of ICANN Travel & Meetings
   8. 2022 ? 2024 Cost Analysis of ICANN Intersessional Meetings



We are aware that there are a lot of materials, therefore we are keeping a
drive folder for you where you can find all these documents, meeting
agendas, and notes of our future meetings in addition to any document that
we will be collaborating on. Here is the link:
https://drive.google.com/drive/folders/1-IGp5C4QAZjj5OJlkYRARnpsg2HBgtV_?usp=drive_link



Your input is essential as we will be working within a tight timeline.



I will serve as the project manager for this work, if you have any
questions, additional topics to propose for the agenda, or any other issue
please feel free to reach out at alperen.eken at icann.org .



We appreciate your participation and look forward to seeing everyone at the
meeting!



Kind regards,



Alp Eken

Policy Development Support Senior Specialist

Internet Corporation for Assigned Names and Numbers (ICANN)


_______________________________________________
GNSO-SG-C-Leadership mailing list -- gnso-sg-c-leadership at icann.org
To unsubscribe send an email to gnso-sg-c-leadership-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/20250121/a8d8c82d/attachment.htm>

From rafik.dammak at gmail.com  Tue Jan 21 07:44:07 2025
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Tue, 21 Jan 2025 14:44:07 +0900
Subject: [NCSG-PC] Topics/Agenda for NCPH session
In-Reply-To: <CAH5sThkdECWZJH545Tc7z94-7fZHvnET_TVfU5c9KgfAa0qzcg@mail.gmail.com>
References: <CAH5sThkdECWZJH545Tc7z94-7fZHvnET_TVfU5c9KgfAa0qzcg@mail.gmail.com>
Message-ID: <CAH5sThnexff=xhKQBTqU5WkB_MCKKoFO6A=d0jhSj0sSHA7xcQ@mail.gmail.com>

hi all,

any comment/input?

Rafik

Le jeu. 16 janv. 2025 ? 11:12, Rafik Dammak <rafik.dammak at gmail.com> a
?crit :

> Hi all,
>
> In order to prepare for the session with CSG, do you have any suggestions
> for the agenda and desired outcomes of the meeting. We can build on the
> topics we discussed on day 0 in Istanbul if there is any particular
> follow-up we would like. For policy topics, I assume it is in an area where
> there are several divergences on some issues.
> I think one topic to share an update on is the procedure for board seat 14.
>
> Best,
>
> Rafik
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250121/ca78cad4/attachment.htm>

From PolicyCalendar at icann.org  Tue Jan 21 15:59:11 2025
From: PolicyCalendar at icann.org (ICANN Policy Calendar)
Date: Tue, 21 Jan 2025 13:59:11 +0000
Subject: [NCSG-PC] NCSG Meeting with Chris Buckridge
Message-ID: <2a8065d914ad4d89a2194b18ab5e83e3@icann.org>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250121/882a17cf/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 1698 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250121/882a17cf/attachment.ics>

From mesumbeslin at gmail.com  Tue Jan 21 22:06:47 2025
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Wed, 22 Jan 2025 07:06:47 +1100
Subject: [NCSG-PC] Fwd: [council] Call for Volunteers for SCCI | Please
 Respond by 6 January
In-Reply-To: <CAM8DdeUhynya5awiiS7o83mdr_CXwNLc8v1GS9M8xGfmGBti8g@mail.gmail.com>
References: <698C84A1-F28A-4430-A052-E39612BAD9F5@icann.org>
 <CAM8DdeV4EFNFj3ADbcKkwxDzr2djA-M3o5ngi0BATgYA-1zmEQ@mail.gmail.com>
 <CAH5sThmMjU0fqwR2DG_RtgU+abvLMxAO4gDwNKvK50R6wEK5yQ@mail.gmail.com>
 <847580910.2455633.1733000189859@mail.yahoo.com>
 <CAMeQZi11eFQWHt6BmJ8S_PNxnyp65AUTjOrSiFBGSLUTcBiZLQ@mail.gmail.com>
 <CAH5sThkv9o_sbDi2tqX=mENCZ-KJmv9tBtU5hJOLf=JgVkSx3Q@mail.gmail.com>
 <d312e640-4a76-417c-b836-20e5fd7dc0e9@Julf.com>
 <CAH5sThmUzaLU6Lmo3U7w3OekA4BdHZTJL9dytvAMTZHYMVRfoA@mail.gmail.com>
 <ce33c08b-1d58-492a-833b-3ee04b98ccad@Julf.com>
 <CAMeQZi0u2am4U-YaDW0KBAvBNgs-vbSNeZk_LfaWHjLqhp-=+Q@mail.gmail.com>
 <CAH5sThm-zFzx84OL170A7_VzbEiZV54MG5_htGrJ55WQVRbjCA@mail.gmail.com>
 <CAM8DdeUhynya5awiiS7o83mdr_CXwNLc8v1GS9M8xGfmGBti8g@mail.gmail.com>
Message-ID: <CAM8DdeXoUTOJq4pgeVUk-6-CMOaR_GrPhLL+jgckyxJJBDJ3XQ@mail.gmail.com>

Hi PC,

Are we in agreement to inform ICANN staff of these names? I didn't get any
response to my email.

Warmly,
Tomslin



On Fri, 17 Jan 2025 at 23:24, Tomslin Samme-Nlar <mesumbeslin at gmail.com>
wrote:

> Hi all,
>
> So, in addition to Manju and Peter who had volunteered, we received only 1
> more expression of interest from Julf.
>
> Since the required representation is 1 councillor + 2 Reps, I suppose all
> three names can be sent.
> Let me know if you have any concerns with this approach.
>
> Warmly,
> Tomslin
>
> On Tue, 7 Jan 2025, 05:54 Rafik Dammak, <rafik.dammak at gmail.com> wrote:
>
>> The deadline was extended to 20th Jan but I want to urge that we appoint
>> asap and close this.
>>
>> Rafik
>>
>>
>>
>> Le mar. 7 janv. 2025 ? 10:51, ??? Manju Chen <manju at nii.org.tw> a ?crit :
>>
>>> Correct, Julf, as long as we have one council rep it's fine. And it's
>>> not against the rules to have another NCSG rep that happens to also be a
>>> councilor.
>>>
>>> Best,
>>> Manju
>>>
>>>
>>> On Mon, Jan 6, 2025 at 6:36?PM Johan Helsingius via NCSG-PC <
>>> ncsg-pc at lists.ncsg.is> wrote:
>>>
>>>> I assume the reps can be, but don't have to be, councilors?
>>>>
>>>>         Julf
>>>>
>>>> On 06/01/2025 10:28, Rafik Dammak wrote:
>>>> > Yes it is one councillor  and 2 reps
>>>> >
>>>> > Rafik
>>>> >
>>>> > On Mon, Jan 6, 2025, 17:57 Johan Helsingius via NCSG-PC <ncsg-
>>>> > pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>> wrote:
>>>> >
>>>> >     Just checking, we are allowed 2+1 reps, right? If we need one
>>>> more, I am
>>>> >     happy to volunteer.
>>>> >
>>>> >              Julf
>>>> >
>>>> >
>>>> >     On 04/01/2025 09:39, Rafik Dammak wrote:
>>>> >      > Hi all,
>>>> >      >
>>>> >      > Can we confirm about the representative for SCCI. We got Manju
>>>> >     and Juan
>>>> >      > volunteering.
>>>> >      >
>>>> >      > Best,
>>>> >      >
>>>> >      > Rafik
>>>> >      >
>>>> >      >
>>>> >      >
>>>> >      > On Wed, Dec 11, 2024, 17:05 ??? Manju Chen <manju at nii.org.tw
>>>> >     <mailto:manju at nii.org.tw>
>>>> >      > <mailto:manju at nii.org.tw <mailto:manju at nii.org.tw>>> wrote:
>>>> >      >
>>>> >      >     Hi,
>>>> >      >
>>>> >      >     Happy to volunteer as the council rep for NCSG.
>>>> >      >
>>>> >      >     Best,
>>>> >      >     Manju
>>>> >      >
>>>> >      >     On Sun, Dec 1, 2024 at 4:58?AM Juan Manuel Rojas via
>>>> NCSG-PC
>>>> >     <ncsg-
>>>> >      > pc at lists.ncsg.is <mailto:pc at lists.ncsg.is> <mailto:ncsg-
>>>> >     pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>>> wrote:
>>>> >      >
>>>> >      >         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 Colombia
>>>> >      >         NPOC Chair - NCSG/GNSO
>>>> >      >         M.Sc. Information Technology
>>>> >      >
>>>> >      >         Registered Linux User No.*533108.*
>>>> >      > http://www.jmanurojas.com <http://www.jmanurojas.com> <http://
>>>> >     www.jmanurojas.com <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
>>>> >     <mailto:rafik.dammak at gmail.com> <mailto:rafik.dammak at gmail.com
>>>> >     <mailto: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 <mailto:mesumbeslin at gmail.com>
>>>> >     <mailto:mesumbeslin at gmail.com <mailto: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
>>>> >     <mailto:council at icann.org>
>>>> >      >             <mailto:council at icann.org <mailto:
>>>> 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
>>>> >     <mailto:council at gnso.icann.org> <mailto:council at gnso.icann.org
>>>> >     <mailto:council at gnso.icann.org>>
>>>> >      >             <council at gnso.icann.org
>>>> >     <mailto:council at gnso.icann.org> <mailto:council at gnso.icann.org
>>>> >     <mailto:council at gnso.icann.org>>>
>>>> >      >             Cc: GNSO-Secs <gnso-secs at icann.org <mailto:gnso-
>>>> >     secs at icann.org> <mailto:gnso-secs at icann.org <mailto: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
>>>> theCouncil
>>>> >      >             Committee for Overseeing and Implementing
>>>> Continuous
>>>> >      >             Improvement (CCOICI) Framework <https://
>>>> >     gnso.icann.org/ <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 theGNSO
>>>> >      >             Council?s adoption of the charter <https://
>>>> >     gnso.icann.org/ <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
>>>> >      >             thecharter <https://gnso.icann.org/sites/default/
>>>> >     files/ <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 inArticle 4.4. of the ICANN Bylaws
>>>> <https://
>>>> >      > www.icann.org/resources/pages/governance/bylaws- <http://
>>>> >     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
>>>> >      >             thecharter <https://gnso.icann.org/sites/default/
>>>> >     files/ <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 theGNSO?s Program Management Tool
>>>> (PMT) Suite
>>>> >      >             <https://community.icann.org/pages/viewpage.action
>>>> >     <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____
>>>> >      >                   o One CPH Board seat #13 (1)____
>>>> >      >                   o One NCPH Board seat #14 (1)____
>>>> >      >
>>>> >      >               * Nine Observers:____
>>>> >      >                   o One Council Chair (1)____
>>>> >      >                   o 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 <mailto:secs at icann.org> <mailto:gnso-
>>>> >     secs at icann.org <mailto: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 itscharter
>>>> >     <https://
>>>> >      > gnso.icann.org/sites/default/files/policy/2024/draft/scci-
>>>> >     <
>>>> http://gnso.icann.org/sites/default/files/policy/2024/draft/scci->
>>>> >      >             charter-draft-update-13nov24-en.pdf>, as well as
>>>> visiting
>>>> >      >             theCCOICI wiki page <https://community.icann.org/
>>>> >     display/ <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
>>>> >     <mailto:council at icann.org>
>>>> >      >             <mailto:council at icann.org <mailto:
>>>> council at icann.org>>
>>>> >      >             To unsubscribe send an email to council-
>>>> >     leave at icann.org <mailto:council-leave at icann.org>
>>>> >      >             <mailto:council-leave at icann.org <mailto: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
>>>> >     <https://www.icann.org/privacy/policy> <https://
>>>> >      > www.icann.org/privacy/policy <http://www.icann.org/privacy/
>>>> >     policy>>) and the website Terms of
>>>> >      >             Service (https://www.icann.org/privacy/tos
>>>> <https://
>>>> >     www.icann.org/privacy/tos> <https://
>>>> >      > www.icann.org/privacy/tos <http://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 <mailto:NCSG-PC at lists.ncsg.is>
>>>> >     <mailto:NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>>
>>>> >      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>>>> >     lists.ncsg.is/mailman/listinfo/ncsg-pc> <https://
>>>> >      > lists.ncsg.is/mailman/listinfo/ncsg-pc <http://lists.ncsg.is/
>>>> >     mailman/listinfo/ncsg-pc>>
>>>> >      >
>>>> >      >         _______________________________________________
>>>> >      >         NCSG-PC mailing list
>>>> >      > NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>>> >     <mailto:NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>>
>>>> >      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>>>> >     lists.ncsg.is/mailman/listinfo/ncsg-pc> <https://
>>>> >      > lists.ncsg.is/mailman/listinfo/ncsg-pc <http://lists.ncsg.is/
>>>> >     mailman/listinfo/ncsg-pc>>
>>>> >      >         _______________________________________________
>>>> >      >         NCSG-PC mailing list
>>>> >      > NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>>> >     <mailto:NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>>
>>>> >      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>>>> >     lists.ncsg.is/mailman/listinfo/ncsg-pc> <https://
>>>> >      > lists.ncsg.is/mailman/listinfo/ncsg-pc <http://lists.ncsg.is/
>>>> >     mailman/listinfo/ncsg-pc>>
>>>> >      >
>>>> >      >
>>>> >      > _______________________________________________
>>>> >      > NCSG-PC mailing list
>>>> >      > NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>>> >      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>>>> >     lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>> >
>>>> >     _______________________________________________
>>>> >     NCSG-PC mailing list
>>>> >     NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>>> >     https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>>>> >     lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>> >
>>>>
>>>> _______________________________________________
>>>> NCSG-PC mailing list
>>>> NCSG-PC at lists.ncsg.is
>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>
>>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250122/1fe34e3b/attachment.htm>

From Kathy at KathyKleiman.com  Tue Jan 21 22:16:46 2025
From: Kathy at KathyKleiman.com (Kathy Kleiman)
Date: Tue, 21 Jan 2025 15:16:46 -0500
Subject: [NCSG-PC] Fwd: [council] Call for Volunteers for SCCI | Please
 Respond by 6 January
In-Reply-To: <CAM8DdeXoUTOJq4pgeVUk-6-CMOaR_GrPhLL+jgckyxJJBDJ3XQ@mail.gmail.com>
References: <698C84A1-F28A-4430-A052-E39612BAD9F5@icann.org>
 <CAM8DdeV4EFNFj3ADbcKkwxDzr2djA-M3o5ngi0BATgYA-1zmEQ@mail.gmail.com>
 <CAH5sThmMjU0fqwR2DG_RtgU+abvLMxAO4gDwNKvK50R6wEK5yQ@mail.gmail.com>
 <847580910.2455633.1733000189859@mail.yahoo.com>
 <CAMeQZi11eFQWHt6BmJ8S_PNxnyp65AUTjOrSiFBGSLUTcBiZLQ@mail.gmail.com>
 <CAH5sThkv9o_sbDi2tqX=mENCZ-KJmv9tBtU5hJOLf=JgVkSx3Q@mail.gmail.com>
 <d312e640-4a76-417c-b836-20e5fd7dc0e9@Julf.com>
 <CAH5sThmUzaLU6Lmo3U7w3OekA4BdHZTJL9dytvAMTZHYMVRfoA@mail.gmail.com>
 <ce33c08b-1d58-492a-833b-3ee04b98ccad@Julf.com>
 <CAMeQZi0u2am4U-YaDW0KBAvBNgs-vbSNeZk_LfaWHjLqhp-=+Q@mail.gmail.com>
 <CAH5sThm-zFzx84OL170A7_VzbEiZV54MG5_htGrJ55WQVRbjCA@mail.gmail.com>
 <CAM8DdeUhynya5awiiS7o83mdr_CXwNLc8v1GS9M8xGfmGBti8g@mail.gmail.com>
 <CAM8DdeXoUTOJq4pgeVUk-6-CMOaR_GrPhLL+jgckyxJJBDJ3XQ@mail.gmail.com>
Message-ID: <486b2fef-f92e-41fc-b8de-ca405caac847@KathyKleiman.com>

I support!

On 1/21/2025 3:06 PM, Tomslin Samme-Nlar wrote:
> Hi PC,
>
> Are we in agreement to inform ICANN staff of these names? I didn't get 
> any response to my email.
>
> Warmly,
> Tomslin
>
>
>
> On Fri, 17 Jan 2025 at 23:24, Tomslin Samme-Nlar 
> <mesumbeslin at gmail.com> wrote:
>
>     Hi all,
>
>     So, in addition to Manju and Peter who had volunteered, we
>     received only 1 more expression of interest from Julf.
>
>     Since the required representation is 1 councillor + 2 Reps, I
>     suppose all three names can be sent.
>     Let me know if you have any concerns with this approach.
>
>     Warmly,
>     Tomslin
>
>     On Tue, 7 Jan 2025, 05:54 Rafik Dammak, <rafik.dammak at gmail.com>
>     wrote:
>
>         The deadline was extended to 20th Jan but I want to urge that
>         we appoint asap and close this.
>
>         Rafik
>
>
>
>         Le?mar. 7 janv. 2025 ??10:51, ??? Manju Chen
>         <manju at nii.org.tw> a ?crit?:
>
>             Correct, Julf, as long as we have one council rep it's
>             fine. And it's not against the rules to have another NCSG
>             rep that happens to also be a councilor.
>
>             Best,
>             Manju
>
>
>             On Mon, Jan 6, 2025 at 6:36?PM Johan Helsingius via
>             NCSG-PC <ncsg-pc at lists.ncsg.is> wrote:
>
>                 I assume the reps can be, but don't have to be,
>                 councilors?
>
>                 ? ? ? ? Julf
>
>                 On 06/01/2025 10:28, Rafik Dammak wrote:
>                 > Yes it is one councillor? and 2 reps
>                 >
>                 > Rafik
>                 >
>                 > On Mon, Jan 6, 2025, 17:57 Johan Helsingius via
>                 NCSG-PC <ncsg-
>                 > pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>> wrote:
>                 >
>                 >? ? ?Just checking, we are allowed 2+1 reps, right?
>                 If we need one more, I am
>                 >? ? ?happy to volunteer.
>                 >
>                 >? ? ? ? ? ? ? Julf
>                 >
>                 >
>                 >? ? ?On 04/01/2025 09:39, Rafik Dammak wrote:
>                 >? ? ? > Hi all,
>                 >? ? ? >
>                 >? ? ? > Can we confirm about the representative for
>                 SCCI. We got Manju
>                 >? ? ?and Juan
>                 >? ? ? > volunteering.
>                 >? ? ? >
>                 >? ? ? > Best,
>                 >? ? ? >
>                 >? ? ? > Rafik
>                 >? ? ? >
>                 >? ? ? >
>                 >? ? ? >
>                 >? ? ? > On Wed, Dec 11, 2024, 17:05 ??? Manju Chen
>                 <manju at nii.org.tw
>                 >? ? ?<mailto:manju at nii.org.tw>
>                 >? ? ? > <mailto:manju at nii.org.tw
>                 <mailto:manju at nii.org.tw>>> wrote:
>                 >? ? ? >
>                 >? ? ? >? ? ?Hi,
>                 >? ? ? >
>                 >? ? ? >? ? ?Happy to volunteer as the council rep for
>                 NCSG.
>                 >? ? ? >
>                 >? ? ? >? ? ?Best,
>                 >? ? ? >? ? ?Manju
>                 >? ? ? >
>                 >? ? ? >? ? ?On Sun, Dec 1, 2024 at 4:58?AM Juan
>                 Manuel Rojas via NCSG-PC
>                 >? ? ?<ncsg-
>                 >? ? ? > pc at lists.ncsg.is <mailto:pc at lists.ncsg.is>
>                 <mailto:ncsg-
>                 > pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>>> wrote:
>                 >? ? ? >
>                 >? ? ? >? ? ? ? ?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 Colombia
>                 >? ? ? >? ? ? ? ?NPOC Chair - NCSG/GNSO
>                 >? ? ? >? ? ? ? ?M.Sc. Information Technology
>                 >? ? ? >
>                 >? ? ? >? ? ? ? ?Registered Linux User No.*533108.*
>                 >? ? ? > http://www.jmanurojas.com
>                 <http://www.jmanurojas.com> <http://
>                 > www.jmanurojas.com <http://www.jmanurojas.com>
>                 <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
>                 >? ? ?<mailto:rafik.dammak at gmail.com>
>                 <mailto:rafik.dammak at gmail.com
>                 >? ? ?<mailto: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
>                 <mailto:mesumbeslin at gmail.com>
>                 >? ? ?<mailto:mesumbeslin at gmail.com
>                 <mailto: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
>                 >? ? ?<mailto:council at icann.org>
>                 >? ? ? >? ? ? ? ? ? ?<mailto:council at icann.org
>                 <mailto: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
>                 >? ? ?<mailto:council at gnso.icann.org>
>                 <mailto:council at gnso.icann.org
>                 >? ? ?<mailto:council at gnso.icann.org>>
>                 >? ? ? >? ? ? ? ? ? ?<council at gnso.icann.org
>                 >? ? ?<mailto:council at gnso.icann.org>
>                 <mailto:council at gnso.icann.org
>                 >? ? ?<mailto:council at gnso.icann.org>>>
>                 >? ? ? >? ? ? ? ? ? ?Cc: GNSO-Secs
>                 <gnso-secs at icann.org <mailto:gnso-
>                 > secs at icann.org> <mailto:gnso-secs at icann.org
>                 <mailto: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 theCouncil
>                 >? ? ? >? ? ? ? ? ? ?Committee for Overseeing and
>                 Implementing Continuous
>                 >? ? ? >? ? ? ? ? ? ?Improvement (CCOICI) Framework
>                 <https://
>                 > gnso.icann.org/ <http://gnso.icann.org/>
>                 <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 theGNSO
>                 >? ? ? >? ? ? ? ? ? ?Council?s adoption of the charter
>                 <https://
>                 > gnso.icann.org/ <http://gnso.icann.org/>
>                 <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
>                 >? ? ? >? ? ? ? ? ? ?thecharter
>                 <https://gnso.icann.org/sites/default/
>                 >? ? ?files/ <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 inArticle 4.4. of the
>                 ICANN Bylaws <https://
>                 >? ? ? >
>                 www.icann.org/resources/pages/governance/bylaws-
>                 <http://www.icann.org/resources/pages/governance/bylaws->
>                 <http://
>                 > www.icann.org/resources/pages/governance/bylaws-
>                 <http://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
>                 >? ? ? >? ? ? ? ? ? ?thecharter
>                 <https://gnso.icann.org/sites/default/
>                 >? ? ?files/ <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 theGNSO?s Program
>                 Management Tool (PMT) Suite
>                 >? ? ? >? ? ? ? ? ?
>                 ?<https://community.icann.org/pages/viewpage.action
>                 >? ? ?<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____
>                 >? ? ? >? ? ? ? ? ? ? ? ? ?o One CPH Board seat #13
>                 (1)____
>                 >? ? ? >? ? ? ? ? ? ? ? ? ?o One NCPH Board seat #14
>                 (1)____
>                 >? ? ? >
>                 >? ? ? >? ? ? ? ? ? ? ?* Nine Observers:____
>                 >? ? ? >? ? ? ? ? ? ? ? ? ?o One Council Chair (1)____
>                 >? ? ? >? ? ? ? ? ? ? ? ? ?o 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 <mailto:secs at icann.org>
>                 <mailto:gnso-
>                 > secs at icann.org
>                 <mailto: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 itscharter
>                 >? ? ?<https://
>                 >? ? ? >
>                 gnso.icann.org/sites/default/files/policy/2024/draft/scci-
>                 <http://gnso.icann.org/sites/default/files/policy/2024/draft/scci->
>                 >? ?
>                 ?<http://gnso.icann.org/sites/default/files/policy/2024/draft/scci->
>                 >? ? ? > ?charter-draft-update-13nov24-en.pdf>, as
>                 well as visiting
>                 >? ? ? >? ? ? ? ? ? ?theCCOICI wiki page
>                 <https://community.icann.org/
>                 >? ? ?display/ <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
>                 >? ? ?<mailto:council at icann.org>
>                 >? ? ? >? ? ? ? ? ? ?<mailto:council at icann.org
>                 <mailto:council at icann.org>>
>                 >? ? ? >? ? ? ? ? ? ?To unsubscribe send an email to
>                 council-
>                 > leave at icann.org <mailto:council-leave at icann.org>
>                 >? ? ? >? ? ? ? ? ? ?<mailto:council-leave at icann.org
>                 <mailto: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
>                 >? ? ?<https://www.icann.org/privacy/policy> <https://
>                 >? ? ? > www.icann.org/privacy/policy
>                 <http://www.icann.org/privacy/policy>
>                 <http://www.icann.org/privacy/
>                 >? ? ?policy>>) and the website Terms of
>                 >? ? ? >? ? ? ? ? ? ?Service
>                 (https://www.icann.org/privacy/tos <https://
>                 > www.icann.org/privacy/tos
>                 <http://www.icann.org/privacy/tos>> <https://
>                 >? ? ? > www.icann.org/privacy/tos
>                 <http://www.icann.org/privacy/tos>
>                 <http://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
>                 <mailto:NCSG-PC at lists.ncsg.is>
>                 >? ? ?<mailto:NCSG-PC at lists.ncsg.is
>                 <mailto:NCSG-PC at lists.ncsg.is>>
>                 >? ? ? >
>                 https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>                 > lists.ncsg.is/mailman/listinfo/ncsg-pc
>                 <http://lists.ncsg.is/mailman/listinfo/ncsg-pc>> <https://
>                 >? ? ? > lists.ncsg.is/mailman/listinfo/ncsg-pc
>                 <http://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>                 <http://lists.ncsg.is/
>                 >? ? ?mailman/listinfo/ncsg-pc>>
>                 >? ? ? >
>                 >? ? ? > ?_______________________________________________
>                 >? ? ? >? ? ? ? ?NCSG-PC mailing list
>                 >? ? ? > NCSG-PC at lists.ncsg.is
>                 <mailto:NCSG-PC at lists.ncsg.is>
>                 >? ? ?<mailto:NCSG-PC at lists.ncsg.is
>                 <mailto:NCSG-PC at lists.ncsg.is>>
>                 >? ? ? >
>                 https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>                 > lists.ncsg.is/mailman/listinfo/ncsg-pc
>                 <http://lists.ncsg.is/mailman/listinfo/ncsg-pc>> <https://
>                 >? ? ? > lists.ncsg.is/mailman/listinfo/ncsg-pc
>                 <http://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>                 <http://lists.ncsg.is/
>                 >? ? ?mailman/listinfo/ncsg-pc>>
>                 >? ? ? > ?_______________________________________________
>                 >? ? ? >? ? ? ? ?NCSG-PC mailing list
>                 >? ? ? > NCSG-PC at lists.ncsg.is
>                 <mailto:NCSG-PC at lists.ncsg.is>
>                 >? ? ?<mailto:NCSG-PC at lists.ncsg.is
>                 <mailto:NCSG-PC at lists.ncsg.is>>
>                 >? ? ? >
>                 https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>                 > lists.ncsg.is/mailman/listinfo/ncsg-pc
>                 <http://lists.ncsg.is/mailman/listinfo/ncsg-pc>> <https://
>                 >? ? ? > lists.ncsg.is/mailman/listinfo/ncsg-pc
>                 <http://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>                 <http://lists.ncsg.is/
>                 >? ? ?mailman/listinfo/ncsg-pc>>
>                 >? ? ? >
>                 >? ? ? >
>                 >? ? ? > _______________________________________________
>                 >? ? ? > NCSG-PC mailing list
>                 >? ? ? > NCSG-PC at lists.ncsg.is
>                 <mailto:NCSG-PC at lists.ncsg.is>
>                 >? ? ? >
>                 https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>                 > lists.ncsg.is/mailman/listinfo/ncsg-pc
>                 <http://lists.ncsg.is/mailman/listinfo/ncsg-pc>>
>                 >
>                 > ?_______________________________________________
>                 >? ? ?NCSG-PC mailing list
>                 > NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>                 > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>                 > lists.ncsg.is/mailman/listinfo/ncsg-pc
>                 <http://lists.ncsg.is/mailman/listinfo/ncsg-pc>>
>                 >
>
>                 _______________________________________________
>                 NCSG-PC mailing list
>                 NCSG-PC at lists.ncsg.is
>                 https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
>         _______________________________________________
>         NCSG-PC mailing list
>         NCSG-PC at lists.ncsg.is
>         https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
>
> _______________________________________________
> 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/20250121/1191175c/attachment.htm>

From rafik.dammak at gmail.com  Wed Jan 22 00:48:51 2025
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Wed, 22 Jan 2025 07:48:51 +0900
Subject: [NCSG-PC] Fwd: [council] Call for Volunteers for SCCI | Please
 Respond by 6 January
In-Reply-To: <CAM8DdeXoUTOJq4pgeVUk-6-CMOaR_GrPhLL+jgckyxJJBDJ3XQ@mail.gmail.com>
References: <698C84A1-F28A-4430-A052-E39612BAD9F5@icann.org>
 <CAM8DdeV4EFNFj3ADbcKkwxDzr2djA-M3o5ngi0BATgYA-1zmEQ@mail.gmail.com>
 <CAH5sThmMjU0fqwR2DG_RtgU+abvLMxAO4gDwNKvK50R6wEK5yQ@mail.gmail.com>
 <847580910.2455633.1733000189859@mail.yahoo.com>
 <CAMeQZi11eFQWHt6BmJ8S_PNxnyp65AUTjOrSiFBGSLUTcBiZLQ@mail.gmail.com>
 <CAH5sThkv9o_sbDi2tqX=mENCZ-KJmv9tBtU5hJOLf=JgVkSx3Q@mail.gmail.com>
 <d312e640-4a76-417c-b836-20e5fd7dc0e9@Julf.com>
 <CAH5sThmUzaLU6Lmo3U7w3OekA4BdHZTJL9dytvAMTZHYMVRfoA@mail.gmail.com>
 <ce33c08b-1d58-492a-833b-3ee04b98ccad@Julf.com>
 <CAMeQZi0u2am4U-YaDW0KBAvBNgs-vbSNeZk_LfaWHjLqhp-=+Q@mail.gmail.com>
 <CAH5sThm-zFzx84OL170A7_VzbEiZV54MG5_htGrJ55WQVRbjCA@mail.gmail.com>
 <CAM8DdeUhynya5awiiS7o83mdr_CXwNLc8v1GS9M8xGfmGBti8g@mail.gmail.com>
 <CAM8DdeXoUTOJq4pgeVUk-6-CMOaR_GrPhLL+jgckyxJJBDJ3XQ@mail.gmail.com>
Message-ID: <CAH5sThmtrH6nQc+w5z0-1qrfFaisJ7tmQ0Sj7THqW4O27QgGFw@mail.gmail.com>

Hi Tomslin,

Not seeing objection, I think we can go with this selection.

Best,

Rafik

On Wed, Jan 22, 2025, 05:07 Tomslin Samme-Nlar <mesumbeslin at gmail.com>
wrote:

> Hi PC,
>
> Are we in agreement to inform ICANN staff of these names? I didn't get any
> response to my email.
>
> Warmly,
> Tomslin
>
>
>
> On Fri, 17 Jan 2025 at 23:24, Tomslin Samme-Nlar <mesumbeslin at gmail.com>
> wrote:
>
>> Hi all,
>>
>> So, in addition to Manju and Peter who had volunteered, we received only
>> 1 more expression of interest from Julf.
>>
>> Since the required representation is 1 councillor + 2 Reps, I suppose all
>> three names can be sent.
>> Let me know if you have any concerns with this approach.
>>
>> Warmly,
>> Tomslin
>>
>> On Tue, 7 Jan 2025, 05:54 Rafik Dammak, <rafik.dammak at gmail.com> wrote:
>>
>>> The deadline was extended to 20th Jan but I want to urge that we appoint
>>> asap and close this.
>>>
>>> Rafik
>>>
>>>
>>>
>>> Le mar. 7 janv. 2025 ? 10:51, ??? Manju Chen <manju at nii.org.tw> a
>>> ?crit :
>>>
>>>> Correct, Julf, as long as we have one council rep it's fine. And it's
>>>> not against the rules to have another NCSG rep that happens to also be a
>>>> councilor.
>>>>
>>>> Best,
>>>> Manju
>>>>
>>>>
>>>> On Mon, Jan 6, 2025 at 6:36?PM Johan Helsingius via NCSG-PC <
>>>> ncsg-pc at lists.ncsg.is> wrote:
>>>>
>>>>> I assume the reps can be, but don't have to be, councilors?
>>>>>
>>>>>         Julf
>>>>>
>>>>> On 06/01/2025 10:28, Rafik Dammak wrote:
>>>>> > Yes it is one councillor  and 2 reps
>>>>> >
>>>>> > Rafik
>>>>> >
>>>>> > On Mon, Jan 6, 2025, 17:57 Johan Helsingius via NCSG-PC <ncsg-
>>>>> > pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>> wrote:
>>>>> >
>>>>> >     Just checking, we are allowed 2+1 reps, right? If we need one
>>>>> more, I am
>>>>> >     happy to volunteer.
>>>>> >
>>>>> >              Julf
>>>>> >
>>>>> >
>>>>> >     On 04/01/2025 09:39, Rafik Dammak wrote:
>>>>> >      > Hi all,
>>>>> >      >
>>>>> >      > Can we confirm about the representative for SCCI. We got Manju
>>>>> >     and Juan
>>>>> >      > volunteering.
>>>>> >      >
>>>>> >      > Best,
>>>>> >      >
>>>>> >      > Rafik
>>>>> >      >
>>>>> >      >
>>>>> >      >
>>>>> >      > On Wed, Dec 11, 2024, 17:05 ??? Manju Chen <manju at nii.org.tw
>>>>> >     <mailto:manju at nii.org.tw>
>>>>> >      > <mailto:manju at nii.org.tw <mailto:manju at nii.org.tw>>> wrote:
>>>>> >      >
>>>>> >      >     Hi,
>>>>> >      >
>>>>> >      >     Happy to volunteer as the council rep for NCSG.
>>>>> >      >
>>>>> >      >     Best,
>>>>> >      >     Manju
>>>>> >      >
>>>>> >      >     On Sun, Dec 1, 2024 at 4:58?AM Juan Manuel Rojas via
>>>>> NCSG-PC
>>>>> >     <ncsg-
>>>>> >      > pc at lists.ncsg.is <mailto:pc at lists.ncsg.is> <mailto:ncsg-
>>>>> >     pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>>> wrote:
>>>>> >      >
>>>>> >      >         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 Colombia
>>>>> >      >         NPOC Chair - NCSG/GNSO
>>>>> >      >         M.Sc. Information Technology
>>>>> >      >
>>>>> >      >         Registered Linux User No.*533108.*
>>>>> >      > http://www.jmanurojas.com <http://www.jmanurojas.com>
>>>>> <http://
>>>>> >     www.jmanurojas.com <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
>>>>> >     <mailto:rafik.dammak at gmail.com> <mailto:rafik.dammak at gmail.com
>>>>> >     <mailto: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 <mailto:mesumbeslin at gmail.com>
>>>>> >     <mailto:mesumbeslin at gmail.com <mailto: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
>>>>> >     <mailto:council at icann.org>
>>>>> >      >             <mailto:council at icann.org <mailto:
>>>>> 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
>>>>> >     <mailto:council at gnso.icann.org> <mailto:council at gnso.icann.org
>>>>> >     <mailto:council at gnso.icann.org>>
>>>>> >      >             <council at gnso.icann.org
>>>>> >     <mailto:council at gnso.icann.org> <mailto:council at gnso.icann.org
>>>>> >     <mailto:council at gnso.icann.org>>>
>>>>> >      >             Cc: GNSO-Secs <gnso-secs at icann.org <mailto:gnso-
>>>>> >     secs at icann.org> <mailto:gnso-secs at icann.org <mailto: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
>>>>> theCouncil
>>>>> >      >             Committee for Overseeing and Implementing
>>>>> Continuous
>>>>> >      >             Improvement (CCOICI) Framework <https://
>>>>> >     gnso.icann.org/ <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
>>>>> theGNSO
>>>>> >      >             Council?s adoption of the charter <https://
>>>>> >     gnso.icann.org/ <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
>>>>> >      >             thecharter <https://gnso.icann.org/sites/default/
>>>>> >     files/ <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 inArticle 4.4. of the ICANN Bylaws
>>>>> <https://
>>>>> >      > www.icann.org/resources/pages/governance/bylaws- <http://
>>>>> >     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
>>>>> >      >             thecharter <https://gnso.icann.org/sites/default/
>>>>> >     files/ <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 theGNSO?s Program Management Tool
>>>>> (PMT) Suite
>>>>> >      >             <
>>>>> https://community.icann.org/pages/viewpage.action
>>>>> >     <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____
>>>>> >      >                   o One CPH Board seat #13 (1)____
>>>>> >      >                   o One NCPH Board seat #14 (1)____
>>>>> >      >
>>>>> >      >               * Nine Observers:____
>>>>> >      >                   o One Council Chair (1)____
>>>>> >      >                   o 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 <mailto:secs at icann.org> <mailto:gnso-
>>>>> >     secs at icann.org <mailto: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 itscharter
>>>>> >     <https://
>>>>> >      > gnso.icann.org/sites/default/files/policy/2024/draft/scci-
>>>>> >     <
>>>>> http://gnso.icann.org/sites/default/files/policy/2024/draft/scci->
>>>>> >      >             charter-draft-update-13nov24-en.pdf>, as well as
>>>>> visiting
>>>>> >      >             theCCOICI wiki page <https://community.icann.org/
>>>>> >     display/ <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
>>>>> >     <mailto:council at icann.org>
>>>>> >      >             <mailto:council at icann.org <mailto:
>>>>> council at icann.org>>
>>>>> >      >             To unsubscribe send an email to council-
>>>>> >     leave at icann.org <mailto:council-leave at icann.org>
>>>>> >      >             <mailto:council-leave at icann.org <mailto: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
>>>>> >     <https://www.icann.org/privacy/policy> <https://
>>>>> >      > www.icann.org/privacy/policy <http://www.icann.org/privacy/
>>>>> >     policy>>) and the website Terms of
>>>>> >      >             Service (https://www.icann.org/privacy/tos
>>>>> <https://
>>>>> >     www.icann.org/privacy/tos> <https://
>>>>> >      > www.icann.org/privacy/tos <http://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 <mailto:NCSG-PC at lists.ncsg.is>
>>>>> >     <mailto:NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>>
>>>>> >      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>>>>> >     lists.ncsg.is/mailman/listinfo/ncsg-pc> <https://
>>>>> >      > lists.ncsg.is/mailman/listinfo/ncsg-pc <http://lists.ncsg.is/
>>>>> >     mailman/listinfo/ncsg-pc>>
>>>>> >      >
>>>>> >      >         _______________________________________________
>>>>> >      >         NCSG-PC mailing list
>>>>> >      > NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>>>> >     <mailto:NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>>
>>>>> >      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>>>>> >     lists.ncsg.is/mailman/listinfo/ncsg-pc> <https://
>>>>> >      > lists.ncsg.is/mailman/listinfo/ncsg-pc <http://lists.ncsg.is/
>>>>> >     mailman/listinfo/ncsg-pc>>
>>>>> >      >         _______________________________________________
>>>>> >      >         NCSG-PC mailing list
>>>>> >      > NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>>>> >     <mailto:NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>>
>>>>> >      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>>>>> >     lists.ncsg.is/mailman/listinfo/ncsg-pc> <https://
>>>>> >      > lists.ncsg.is/mailman/listinfo/ncsg-pc <http://lists.ncsg.is/
>>>>> >     mailman/listinfo/ncsg-pc>>
>>>>> >      >
>>>>> >      >
>>>>> >      > _______________________________________________
>>>>> >      > NCSG-PC mailing list
>>>>> >      > NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>>>> >      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>>>>> >     lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>>> >
>>>>> >     _______________________________________________
>>>>> >     NCSG-PC mailing list
>>>>> >     NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>>>> >     https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://
>>>>> >     lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>>> >
>>>>>
>>>>> _______________________________________________
>>>>> NCSG-PC mailing list
>>>>> NCSG-PC at lists.ncsg.is
>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>
>>>> _______________________________________________
>>> NCSG-PC mailing list
>>> NCSG-PC at lists.ncsg.is
>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250122/d47e400d/attachment.htm>

From rafik.dammak at gmail.com  Wed Jan 22 01:01:55 2025
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Wed, 22 Jan 2025 08:01:55 +0900
Subject: [NCSG-PC] ICANN83 | Prague | Supported Travelers Database Due |
 Monday, 10 February 2025
In-Reply-To: <66C19F06-C253-4192-87B8-A4EB396BCECD@icann.org>
References: <66C19F06-C253-4192-87B8-A4EB396BCECD@icann.org>
Message-ID: <CAH5sThnSt_+XL0a0qrtH8H3iEcq-owibbymvp8=E22VuFUDm-Q@mail.gmail.com>

Dear councillors,


We need to confirm who from travel supported councillors will be able
attend ICANN meeting in Prague. Please respond within the next 7 days.


Best,

Rafik

---------- Forwarded message ---------
Dear all,

In order to service your travel needs for ICANN83 Prague in a timely
fashion, please submit your meeting database to gnso-secs at icann.org by *Monday,
10 February 2025. *It is important all funded travel air booking is
completed by due date given in ICANN Travel emails. There seems to be some
struggle in this area, if you could please make sure all names put forward
understand the deadlines.

Please share with all funded travelers, the travel support guidelines wiki
space: https://community.icann.org/x/lgvxAg and highlight the
communications responsibilities section:

ICANN Travel Support attempts to reach a supported traveler four times
before deeming the supported traveler unresponsive:

   1. ICANN Travel Support sends ?welcome email.?
   2. If there is no response after seven business days, ICANN Travel
   Support sends a second email, copying ICANN support staff.
   3. If there is no response five business days after the second email,
   ICANN Travel Support sends a third email, copying ICANN support staff and
   the community group chair.
   4. If there is no response five business days after the third email,
   ICANN Travel Support sends a fourth email, copying ICANN support staff and
   the community group chair.

If there is no response three days after the fourth attempt to reach the
supported traveler, the community group may substitute another traveler.



A timely response would be appreciated in view of visa issues and the OFAC
review. The deadline for submissions is critical to allow for confirmed
reservation numbers as required for visa and travel arrangements.

 *TRAVEL BOOKING PROCESS*



In order for Funded Travelers to start booking travel, they MUST complete
Steps 1, 2, and 3.



*WHO*

*WHAT*

1

Funded Traveler

Register for meeting using the Funded Traveler Registration Link provided
by ICANN Travel Support

2

Funded Traveler

Approved for Trade Regulations Review

3

Funded Traveler

Receive Travel Funding Confirmation Email from ICANN Travel Support

4

*Funded Traveler*

*Book Air Travel for meeting*















 *Approved dates of Arrival and Departure*

*ARRIVAL DATE*

*DEPARTURE DATE*

*Sunday, 08 June *

*Friday, 13 June*



For air, this must be booked using either via our online booking platform
(Concur) or official travel agency (FCM). ICANN org does not allow
self-booking.



Please note that when requesting travel support, in the interest of
fairness and in light of budget restrictions we would like you to take the
following into consideration:



1.               Respond timely to ICANN Travel regarding your upcoming
travel and book by deadline given in email.

2.               If you require a visa to enter the country, please make
sure to acquire your visa immediately. Follow link here
<https://community.icann.org/x/fSfxAg> for assistance.

3.               Friday, 25 April 2025* (45 days before travel)* is the
last day to submit additions/replacements.

4.               Requests past the deadline will be handled on a
case-by-case basis by ICANN. All additional travelers added after the
90-day deadline are subject to availability, may NOT be placed in the same
hotel as their funded traveler groups, and may not be able to attend due to
visa issues.

5.               If possible, please book direct travel requests. Detours
and multi-stop trips are unfortunately not guaranteed.

6.               If travelers want to extend their stay this must be done
at their own expense and should contact the hotel directly once the ICANN
hotel confirmation has be sent to them.

7.               *Privately Booked Reservations*: ICANN will not refund or
take over accommodations directly booked by the funded traveler. If a
replacement has an existing hotel reservation, they will need to cancel
their reservation and ICANN will not be able to take over their reservation.



Reminder:

   - GNSO supported traveler with a designated hotel accommodation funding,
   a hotel room is automatically secured for you, please *DO NOT* book your
   own hotel as it is un-reimbursable.
   - All personal data provided to ICANN org in for purposes of providing
   travel support for participants related to ICANN events will be processed
   in accordance with the ICANN Privacy Policy [icann.org]
   <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=A_rkvV7hcBAIOU12pQX6fSkWBC6-P-bPaQDowX2oR_A&s=WwqcPGGS1mvkGHO5BjVc3E9ewPva_WoF-Snq25kq0OM&e=>.
   Should you have any questions or concerns about this Privacy Policy and our
   privacy practices, you may contact us at privacy at icann.org.
   - As a reminder, for the AGM meeting only, incoming Councilors get
   funding, as well as the then-incumbent Councilors.



 Many thanks for your cooperation!

 Thank you.



Kind regards,



Terri

Policy Team Supporting the GNSO
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250122/39ba7498/attachment.htm>

From julf at Julf.com  Wed Jan 22 08:45:46 2025
From: julf at Julf.com (Johan Helsingius)
Date: Wed, 22 Jan 2025 07:45:46 +0100
Subject: [NCSG-PC] ICANN83 | Prague | Supported Travelers Database Due |
 Monday, 10 February 2025
In-Reply-To: <CAH5sThnSt_+XL0a0qrtH8H3iEcq-owibbymvp8=E22VuFUDm-Q@mail.gmail.com>
References: <66C19F06-C253-4192-87B8-A4EB396BCECD@icann.org>
 <CAH5sThnSt_+XL0a0qrtH8H3iEcq-owibbymvp8=E22VuFUDm-Q@mail.gmail.com>
Message-ID: <0e3611ab-0dd1-401e-b6cb-cb053259b5e2@Julf.com>

Count me in!

	Julf


On 22/01/2025 00:01, Rafik Dammak wrote:
> Dear councillors,
> 
> 
> We need to confirm who from travel supported councillors will be able 
> attend ICANN meeting in Prague. Please respond within the next 7 days.
> 
> 
> Best,
> 
> Rafik
> 
> ---------- Forwarded message ---------
> Dear all,
> 
> In order to service your travel needs for ICANN83Prague?in a timely 
> fashion, please submit your meeting database tognso-secs at icann.org 
> <mailto:gnso-secs at icann.org>by*Monday, 10 February 2025. *It is 
> important all funded travel air booking is completed by due date given 
> in ICANN Travel emails. There seems to be some struggle in this area, if 
> you could please make sure all names put forward understand the 
> deadlines. ____
> 
> Please share with all funded travelers, the travel support guidelines 
> wiki space: https://community.icann.org/x/lgvxAg <https:// 
> community.icann.org/x/lgvxAg>and highlight the communications 
> responsibilities section:____
> 
> ICANN Travel Support attempts to reach a supported traveler four times 
> before deeming the supported traveler unresponsive:____
> 
>  1. ICANN Travel Support sends ?welcome email.?____
>  2. If there is no response after seven business days, ICANN Travel
>     Support sends a second email, copying ICANN support staff.____
>  3. If there is no response five business days after the second email,
>     ICANN Travel Support sends a third email, copying ICANN support
>     staff and the community group chair.____
>  4. If there is no response five business days after the third email,
>     ICANN Travel Support sends a fourth email, copying ICANN support
>     staff and the community group chair.____
> 
> If there is no response three days after the fourth attempt to reach the 
> supported traveler, the community group may substitute another traveler.____
> 
> __ __
> 
> A timely response would be appreciated in view of visa issues and the 
> OFAC review. The deadline for submissions is critical to allow for 
> confirmed reservation numbers as required for visa and travel 
> arrangements.____
> 
> *TRAVEL BOOKING PROCESS*____
> 
> ____
> 
> In order for Funded Travelers to start booking travel, they MUST 
> complete Steps 1, 2, and 3.____
> 
> ____
> 
> 	
> 
> *WHO*____
> 
> 	
> 
> *WHAT*____
> 
> 1____
> 
> 	
> 
> Funded Traveler____
> 
> 	
> 
> Register for meeting using the Funded Traveler Registration Link 
> provided by ICANN Travel Support____
> 
> 2____
> 
> 	
> 
> Funded Traveler____
> 
> 	
> 
> Approved for Trade Regulations Review____
> 
> 3____
> 
> 	
> 
> Funded Traveler____
> 
> 	
> 
> Receive Travel Funding Confirmation Email from ICANN Travel Support____
> 
> 4____
> 
> 	
> 
> *Funded Traveler*____
> 
> 	
> 
> *Book Air Travel for meeting*____
> 
> __ __
> 
> 	
> 
> __ __
> 
> __ __
> 
> 	
> 
> __ __
> 
> __ __
> 
> 	
> 
> __ __
> 
> 	
> 
> __ __
> 
> *Approved dates of Arrival and Departure*____
> 
> *ARRIVAL DATE*____
> 
> 	
> 
> *DEPARTURE DATE*____
> 
> *Sunday, 08 June *____
> 
> 	
> 
> *Friday, 13 June*____
> 
> __ __
> 
> For air, this must be booked using either via our online booking 
> platform (Concur) or official travel agency (FCM). ICANN org does not 
> allow self-booking.____
> 
> ____
> 
> Please note that when requesting travel support, in the interest of 
> fairness and in light of budget restrictions?we would like you to take 
> the following into consideration:____
> 
> ____
> 
> __1.__Respond?timely to ICANN Travel regarding your upcoming travel and 
> book by deadline given in email. ____
> 
> __2.__If you require a visa to enter the country, please make sure to 
> acquire your visa immediately.Follow link here <https:// 
> community.icann.org/x/fSfxAg>for assistance. ____
> 
> __3.__Friday, 25 April 2025*(45 days before travel)*is the last day to 
> submit additions/replacements. ____
> 
> __4.__Requests past the deadline will be handled on a case-by-case basis 
> by ICANN. All additional travelers added after the 90-day deadline are 
> subject to availability, may NOT be placed in the same hotel as their 
> funded traveler groups, and may not be able to attend due to visa 
> issues. ____
> 
> __5.__If possible, please book?direct travel requests.?Detours and 
> multi-stop trips are unfortunately not guaranteed.____
> 
> __6.__If travelers want to extend their stay this must be done at their 
> own expense and should contact the hotel directly once the ICANN hotel 
> confirmation has be sent to them.____
> 
> __7.__*Privately Booked Reservations*: ICANN will not refund or take 
> over accommodations directly booked by the funded traveler. If a 
> replacement has an existing hotel reservation, they will need to cancel 
> their reservation and ICANN will not be able to take over their 
> reservation.____
> 
> __ __
> 
> Reminder:____
> 
>   * GNSO supported traveler with a designated hotel accommodation
>     funding, a hotel room is automatically secured for you, please *DO
>     NOT* book your own hotel as it is un-reimbursable. ____
>   * All personal data provided to ICANN org in for purposes of providing
>     travel support for participants related to ICANN events will be
>     processed in accordance with the ICANN Privacy Policy [icann.org]
>     <https://urldefense.proofpoint.com/v2/url?
>     u=https-3A__www.icann.org_privacy_policy&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=A_rkvV7hcBAIOU12pQX6fSkWBC6-P-bPaQDowX2oR_A&s=WwqcPGGS1mvkGHO5BjVc3E9ewPva_WoF-Snq25kq0OM&e=>.? Should you have any questions or concerns about this Privacy Policy and our privacy practices, you may contact us at privacy at icann.org <mailto:privacy at icann.org>.____
>   * As a reminder, for the AGM meeting only, incoming Councilors get
>     funding, as well as the then-incumbent Councilors. ____
> 
> ____
> 
>  ?Many thanks for your cooperation!____
> 
> Thank you.____
> 
> __ __
> 
> Kind regards,____
> 
> ____
> 
> Terri____
> 
> Policy Team Supporting the GNSO____
> 
> __ __
> 
> __ __
> 
> __ __
> 
> __
> __
> 
> 
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc



From mesumbeslin at gmail.com  Wed Jan 22 15:00:52 2025
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Thu, 23 Jan 2025 00:00:52 +1100
Subject: [NCSG-PC] ICANN83 | Prague | Supported Travelers Database Due |
 Monday, 10 February 2025
In-Reply-To: <CAH5sThnSt_+XL0a0qrtH8H3iEcq-owibbymvp8=E22VuFUDm-Q@mail.gmail.com>
References: <66C19F06-C253-4192-87B8-A4EB396BCECD@icann.org>
 <CAH5sThnSt_+XL0a0qrtH8H3iEcq-owibbymvp8=E22VuFUDm-Q@mail.gmail.com>
Message-ID: <CAM8DdeWsBfiPdXGMbZxyM8iYs9yE6JXTK4zZgv=BtefiUJW7Dg@mail.gmail.com>

I am going

Warmly,
Tomslin

On Wed, 22 Jan 2025, 10:02 Rafik Dammak, <rafik.dammak at gmail.com> wrote:

> Dear councillors,
>
>
> We need to confirm who from travel supported councillors will be able
> attend ICANN meeting in Prague. Please respond within the next 7 days.
>
>
> Best,
>
> Rafik
>
> ---------- Forwarded message ---------
> Dear all,
>
> In order to service your travel needs for ICANN83 Prague in a timely
> fashion, please submit your meeting database to gnso-secs at icann.org by *Monday,
> 10 February 2025. *It is important all funded travel air booking is
> completed by due date given in ICANN Travel emails. There seems to be some
> struggle in this area, if you could please make sure all names put forward
> understand the deadlines.
>
> Please share with all funded travelers, the travel support guidelines wiki
> space: https://community.icann.org/x/lgvxAg and highlight the
> communications responsibilities section:
>
> ICANN Travel Support attempts to reach a supported traveler four times
> before deeming the supported traveler unresponsive:
>
>    1. ICANN Travel Support sends ?welcome email.?
>    2. If there is no response after seven business days, ICANN Travel
>    Support sends a second email, copying ICANN support staff.
>    3. If there is no response five business days after the second email,
>    ICANN Travel Support sends a third email, copying ICANN support staff and
>    the community group chair.
>    4. If there is no response five business days after the third email,
>    ICANN Travel Support sends a fourth email, copying ICANN support staff and
>    the community group chair.
>
> If there is no response three days after the fourth attempt to reach the
> supported traveler, the community group may substitute another traveler.
>
>
>
> A timely response would be appreciated in view of visa issues and the OFAC
> review. The deadline for submissions is critical to allow for confirmed
> reservation numbers as required for visa and travel arrangements.
>
>  *TRAVEL BOOKING PROCESS*
>
>
>
> In order for Funded Travelers to start booking travel, they MUST complete
> Steps 1, 2, and 3.
>
>
>
> *WHO*
>
> *WHAT*
>
> 1
>
> Funded Traveler
>
> Register for meeting using the Funded Traveler Registration Link provided
> by ICANN Travel Support
>
> 2
>
> Funded Traveler
>
> Approved for Trade Regulations Review
>
> 3
>
> Funded Traveler
>
> Receive Travel Funding Confirmation Email from ICANN Travel Support
>
> 4
>
> *Funded Traveler*
>
> *Book Air Travel for meeting*
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>  *Approved dates of Arrival and Departure*
>
> *ARRIVAL DATE*
>
> *DEPARTURE DATE*
>
> *Sunday, 08 June *
>
> *Friday, 13 June*
>
>
>
> For air, this must be booked using either via our online booking platform
> (Concur) or official travel agency (FCM). ICANN org does not allow
> self-booking.
>
>
>
> Please note that when requesting travel support, in the interest of
> fairness and in light of budget restrictions we would like you to take the
> following into consideration:
>
>
>
> 1.               Respond timely to ICANN Travel regarding your upcoming
> travel and book by deadline given in email.
>
> 2.               If you require a visa to enter the country, please make
> sure to acquire your visa immediately. Follow link here
> <https://community.icann.org/x/fSfxAg> for assistance.
>
> 3.               Friday, 25 April 2025* (45 days before travel)* is the
> last day to submit additions/replacements.
>
> 4.               Requests past the deadline will be handled on a
> case-by-case basis by ICANN. All additional travelers added after the
> 90-day deadline are subject to availability, may NOT be placed in the same
> hotel as their funded traveler groups, and may not be able to attend due to
> visa issues.
>
> 5.               If possible, please book direct travel requests. Detours
> and multi-stop trips are unfortunately not guaranteed.
>
> 6.               If travelers want to extend their stay this must be done
> at their own expense and should contact the hotel directly once the ICANN
> hotel confirmation has be sent to them.
>
> 7.               *Privately Booked Reservations*: ICANN will not refund
> or take over accommodations directly booked by the funded traveler. If a
> replacement has an existing hotel reservation, they will need to cancel
> their reservation and ICANN will not be able to take over their reservation.
>
>
>
> Reminder:
>
>    - GNSO supported traveler with a designated hotel accommodation
>    funding, a hotel room is automatically secured for you, please *DO NOT*
>    book your own hotel as it is un-reimbursable.
>    - All personal data provided to ICANN org in for purposes of providing
>    travel support for participants related to ICANN events will be processed
>    in accordance with the ICANN Privacy Policy [icann.org]
>    <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=A_rkvV7hcBAIOU12pQX6fSkWBC6-P-bPaQDowX2oR_A&s=WwqcPGGS1mvkGHO5BjVc3E9ewPva_WoF-Snq25kq0OM&e=>.
>    Should you have any questions or concerns about this Privacy Policy and our
>    privacy practices, you may contact us at privacy at icann.org.
>    - As a reminder, for the AGM meeting only, incoming Councilors get
>    funding, as well as the then-incumbent Councilors.
>
>
>
>  Many thanks for your cooperation!
>
>  Thank you.
>
>
>
> Kind regards,
>
>
>
> Terri
>
> Policy Team Supporting the GNSO
>
>
>
>
>
>
>
>
> _______________________________________________
> 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/20250123/3983d93c/attachment.htm>

From bruna.mrtns at gmail.com  Wed Jan 22 16:03:00 2025
From: bruna.mrtns at gmail.com (Bruna Martins dos Santos)
Date: Wed, 22 Jan 2025 15:03:00 +0100
Subject: [NCSG-PC] ICANN83 | Prague | Supported Travelers Database Due |
 Monday, 10 February 2025
In-Reply-To: <CAM8DdeWsBfiPdXGMbZxyM8iYs9yE6JXTK4zZgv=BtefiUJW7Dg@mail.gmail.com>
References: <66C19F06-C253-4192-87B8-A4EB396BCECD@icann.org>
 <CAH5sThnSt_+XL0a0qrtH8H3iEcq-owibbymvp8=E22VuFUDm-Q@mail.gmail.com>
 <CAM8DdeWsBfiPdXGMbZxyM8iYs9yE6JXTK4zZgv=BtefiUJW7Dg@mail.gmail.com>
Message-ID: <CADAEEV393oZZ0COMYHC1vj_-rkY=Q7pwWCiQ_ViwgsV1WBd7wQ@mail.gmail.com>

Also count me in !


On Wed, Jan 22, 2025 at 2:01?PM Tomslin Samme-Nlar <mesumbeslin at gmail.com>
wrote:

> I am going
>
> Warmly,
> Tomslin
>
> On Wed, 22 Jan 2025, 10:02 Rafik Dammak, <rafik.dammak at gmail.com> wrote:
>
>> Dear councillors,
>>
>>
>> We need to confirm who from travel supported councillors will be able
>> attend ICANN meeting in Prague. Please respond within the next 7 days.
>>
>>
>> Best,
>>
>> Rafik
>>
>> ---------- Forwarded message ---------
>> Dear all,
>>
>> In order to service your travel needs for ICANN83 Prague in a timely
>> fashion, please submit your meeting database to gnso-secs at icann.org by *Monday,
>> 10 February 2025. *It is important all funded travel air booking is
>> completed by due date given in ICANN Travel emails. There seems to be some
>> struggle in this area, if you could please make sure all names put forward
>> understand the deadlines.
>>
>> Please share with all funded travelers, the travel support guidelines
>> wiki space: https://community.icann.org/x/lgvxAg and highlight the
>> communications responsibilities section:
>>
>> ICANN Travel Support attempts to reach a supported traveler four times
>> before deeming the supported traveler unresponsive:
>>
>>    1. ICANN Travel Support sends ?welcome email.?
>>    2. If there is no response after seven business days, ICANN Travel
>>    Support sends a second email, copying ICANN support staff.
>>    3. If there is no response five business days after the second email,
>>    ICANN Travel Support sends a third email, copying ICANN support staff and
>>    the community group chair.
>>    4. If there is no response five business days after the third email,
>>    ICANN Travel Support sends a fourth email, copying ICANN support staff and
>>    the community group chair.
>>
>> If there is no response three days after the fourth attempt to reach the
>> supported traveler, the community group may substitute another traveler.
>>
>>
>>
>> A timely response would be appreciated in view of visa issues and the
>> OFAC review. The deadline for submissions is critical to allow for
>> confirmed reservation numbers as required for visa and travel arrangements.
>>
>>  *TRAVEL BOOKING PROCESS*
>>
>>
>>
>> In order for Funded Travelers to start booking travel, they MUST complete
>> Steps 1, 2, and 3.
>>
>>
>>
>> *WHO*
>>
>> *WHAT*
>>
>> 1
>>
>> Funded Traveler
>>
>> Register for meeting using the Funded Traveler Registration Link provided
>> by ICANN Travel Support
>>
>> 2
>>
>> Funded Traveler
>>
>> Approved for Trade Regulations Review
>>
>> 3
>>
>> Funded Traveler
>>
>> Receive Travel Funding Confirmation Email from ICANN Travel Support
>>
>> 4
>>
>> *Funded Traveler*
>>
>> *Book Air Travel for meeting*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>  *Approved dates of Arrival and Departure*
>>
>> *ARRIVAL DATE*
>>
>> *DEPARTURE DATE*
>>
>> *Sunday, 08 June *
>>
>> *Friday, 13 June*
>>
>>
>>
>> For air, this must be booked using either via our online booking platform
>> (Concur) or official travel agency (FCM). ICANN org does not allow
>> self-booking.
>>
>>
>>
>> Please note that when requesting travel support, in the interest of
>> fairness and in light of budget restrictions we would like you to take the
>> following into consideration:
>>
>>
>>
>> 1.               Respond timely to ICANN Travel regarding your upcoming
>> travel and book by deadline given in email.
>>
>> 2.               If you require a visa to enter the country, please make
>> sure to acquire your visa immediately. Follow link here
>> <https://community.icann.org/x/fSfxAg> for assistance.
>>
>> 3.               Friday, 25 April 2025* (45 days before travel)* is the
>> last day to submit additions/replacements.
>>
>> 4.               Requests past the deadline will be handled on a
>> case-by-case basis by ICANN. All additional travelers added after the
>> 90-day deadline are subject to availability, may NOT be placed in the same
>> hotel as their funded traveler groups, and may not be able to attend due to
>> visa issues.
>>
>> 5.               If possible, please book direct travel
>> requests. Detours and multi-stop trips are unfortunately not guaranteed.
>>
>> 6.               If travelers want to extend their stay this must be
>> done at their own expense and should contact the hotel directly once the
>> ICANN hotel confirmation has be sent to them.
>>
>> 7.               *Privately Booked Reservations*: ICANN will not refund
>> or take over accommodations directly booked by the funded traveler. If a
>> replacement has an existing hotel reservation, they will need to cancel
>> their reservation and ICANN will not be able to take over their reservation.
>>
>>
>>
>> Reminder:
>>
>>    - GNSO supported traveler with a designated hotel accommodation
>>    funding, a hotel room is automatically secured for you, please *DO
>>    NOT* book your own hotel as it is un-reimbursable.
>>    - All personal data provided to ICANN org in for purposes of
>>    providing travel support for participants related to ICANN events will be
>>    processed in accordance with the ICANN Privacy Policy [icann.org]
>>    <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=A_rkvV7hcBAIOU12pQX6fSkWBC6-P-bPaQDowX2oR_A&s=WwqcPGGS1mvkGHO5BjVc3E9ewPva_WoF-Snq25kq0OM&e=>.
>>    Should you have any questions or concerns about this Privacy Policy and our
>>    privacy practices, you may contact us at privacy at icann.org.
>>    - As a reminder, for the AGM meeting only, incoming Councilors get
>>    funding, as well as the then-incumbent Councilors.
>>
>>
>>
>>  Many thanks for your cooperation!
>>
>>  Thank you.
>>
>>
>>
>> Kind regards,
>>
>>
>>
>> Terri
>>
>> Policy Team Supporting the GNSO
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>


-- 

*Bruna Martins dos Santos *

German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von
Humboldt Foundation <https://www.humboldt-foundation.de/>
MAG Member 2022, 2023 and 2024

Member | Coaliz?o Direitos na Rede <https://direitosnarede.org.br/>
Co-Coordinator | Internet Governance Caucus  <https://igcaucus.org/>

Twitter: @boomartins <https://twitter.com/boomartins> // Skype:
bruna.martinsantos
Email: bruna.mrtns at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250122/fde384fb/attachment.htm>

From farzaneh.badii at gmail.com  Wed Jan 22 17:10:23 2025
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Wed, 22 Jan 2025 10:10:23 -0500
Subject: [NCSG-PC] [NCSG-EC] Topics/Agenda for NCPH session
In-Reply-To: <CAH5sThnexff=xhKQBTqU5WkB_MCKKoFO6A=d0jhSj0sSHA7xcQ@mail.gmail.com>
References: <CAH5sThkdECWZJH545Tc7z94-7fZHvnET_TVfU5c9KgfAa0qzcg@mail.gmail.com>
 <CAH5sThnexff=xhKQBTqU5WkB_MCKKoFO6A=d0jhSj0sSHA7xcQ@mail.gmail.com>
Message-ID: <CAN1qJvCwG2ZaACToW0SQuyQgxREFPA2EtX9sXLi_yg8o+S5S-g@mail.gmail.com>

Hi

I was thinking we should discuss the future of ?dns abuse? and talk about
our positions and plans.

Farzaneh


On Tue, Jan 21, 2025 at 12:44?AM Rafik Dammak via NCSG-EC <
ncsg-ec at lists.ncsg.is> wrote:

> hi all,
>
> any comment/input?
>
> Rafik
>
> Le jeu. 16 janv. 2025 ? 11:12, Rafik Dammak <rafik.dammak at gmail.com> a
> ?crit :
>
>> Hi all,
>>
>> In order to prepare for the session with CSG, do you have any suggestions
>> for the agenda and desired outcomes of the meeting. We can build on the
>> topics we discussed on day 0 in Istanbul if there is any particular
>> follow-up we would like. For policy topics, I assume it is in an area where
>> there are several divergences on some issues.
>> I think one topic to share an update on is the procedure for board seat
>> 14.
>>
>> Best,
>>
>> Rafik
>>
> _______________________________________________
> 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/20250122/6a4ce6a6/attachment.htm>

From mesumbeslin at gmail.com  Thu Jan 23 01:18:57 2025
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Thu, 23 Jan 2025 10:18:57 +1100
Subject: [NCSG-PC] Fwd: FW: [GNSO-TPR] Transfer PDP Concensus Call
In-Reply-To: <003101db6d04$42ffaab0$c8ff0010$@kherman.com>
References: <DS0PR02MB94996BB1BEBEAA160AB4FC16B1E12@DS0PR02MB9499.namprd02.prod.outlook.com>
 <003101db6d04$42ffaab0$c8ff0010$@kherman.com>
Message-ID: <CAM8DdeW7ym09boSo-JF_-E9oYpp_Ej1a8P1VqFUiee-_344HjA@mail.gmail.com>

Dear PC members,

Please see Ken's (one of our reps to TPR PDP) message below. Let me know as
soon as you can if you have any objection to NCSG accepting the consensus
designations as per Ken's suggestion below.

Warmly,
Tomslin

---------- Forwarded message ---------
From: Ken Herman <ken at kherman.com>
Date: Thu, 23 Jan 2025, 06:31
Subject: FW: [GNSO-TPR] Transfer PDP Concensus Call
To: Tomslin Samme-Nlar <mesumbeslin at gmail.com>
Cc: Juan Manuel Rojas <jumaropi at yahoo.com>


Hello Tomslin.



I received this email today (presumably Juan also received it), and as you
can see we are being asked to confirm our acceptance of the recommendations.



While we (NCSG) did not achieve everything we suggested in the public
comment period, some of our suggestions were accepted. At this point, as I
pointed out in my recent message, I do not see any reason to object to any
of the recommendations.



Does this need a discussion/approval with the policy committee?



Let me know the appropriate procedure so I can respond accordingly.



Thanks!



Ken



*From:* rcarney--- via GNSO-TPR <gnso-tpr at icann.org>
*Sent:* Wednesday, January 22, 2025 11:10 AM
*To:* gnso-tpr at icann.org
*Subject:* [GNSO-TPR] Transfer PDP Concensus Call



Dear TPR Working Group members,



As discussed during our meeting on 21 January 2025, this message is to
notify you of the opening of the Consensus Call process on the TPR final
policy recommendations.



The TPR leadership team has proposed a consensus designation for every
final recommendation that the working group has finalized. These consensus
designations are contained in the attached document entitled, ?*TPR WG
Consensus Call - Leadership Proposed Consensus Designations*.?



This Consensus Call process opens today, 22 January 2025 at 00:00 UTC and
closing on 31 January 2025 at 23:59 UTC. In accordance with the *GNSO
Working Group Guidelines
<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-1-gnso-wg-guidelines-15mar23-en.pdf>*,
working group members are required to indicate via reply to this message
whether they accept, or do not accept, the leadership team?s proposed
consensus designations. If no objection is raised by any member, the
consensus designation is considered accepted by that working group member.
If you do not respond before 31 January 2025 at 23:59 UTC, the leadership
team will take this as acceptance of the consensus designations. If any
objection is raised for any specific final recommendation, the leadership
team is expected to reevaluate the consensus designation of such
recommendation and publish an updated designation to be reviewed by the
working group.



In the event there is no disagreement by the working group with the
proposed consensus designations, TPR Policy Support Staff will incorporate
the designations into the Phase 2 Final Report.



As set out in the *TPR Working Group Charter
<https://gnso.icann.org/sites/default/files/policy/2023/correspondence/novoa-et-al-to-council-et-al-06feb23-en.pdf>*,
only Members appointed by their representative groups are expected to
participate in the Consensus Call process. Participants and observers will
not be able to participate.



For reference, please also see the attached document entitled ?*TPR FINAL
RECOMMENDATIONS (ONLY)*? that contains the forty-seven (47) recommendations
to be included in the Final Report.



For more information about the Consensus Call, you may review the *GNSO
Working Group Guidelines
<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-1-gnso-wg-guidelines-15mar23-en.pdf>*
or
the *Working Group Charter
<https://gnso.icann.org/sites/default/files/policy/2023/correspondence/novoa-et-al-to-council-et-al-06feb23-en.pdf>*
(Section
VI: Decision Making Methodologies).





Best regards,

Roger Carney, TPR WG Chair
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250123/e7133e80/attachment.htm>
-------------- next part --------------
_______________________________________________
GNSO-TPR mailing list -- gnso-tpr at icann.org
To unsubscribe send an email to gnso-tpr-leave at icann.org
%(web_page_url)slistinfo/%(_internal_name)s
-------------- next part --------------
A non-text attachment was scrubbed...
Name: TPR WG Consensus Call - Leadership Proposed Consensus Designations.pdf
Type: application/pdf
Size: 186622 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250123/e7133e80/attachment.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: TPR FINAL RECOMMENDATIONS (ONLY).pdf
Type: application/pdf
Size: 963538 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250123/e7133e80/attachment-0001.pdf>

From manju at nii.org.tw  Thu Jan 23 15:52:02 2025
From: manju at nii.org.tw (=?UTF-8?B?6Zmz5pu86Iy5IE1hbmp1IENoZW4=?=)
Date: Thu, 23 Jan 2025 21:52:02 +0800
Subject: [NCSG-PC] ICANN83 | Prague | Supported Travelers Database Due |
 Monday, 10 February 2025
In-Reply-To: <CADAEEV393oZZ0COMYHC1vj_-rkY=Q7pwWCiQ_ViwgsV1WBd7wQ@mail.gmail.com>
References: <66C19F06-C253-4192-87B8-A4EB396BCECD@icann.org>
 <CAH5sThnSt_+XL0a0qrtH8H3iEcq-owibbymvp8=E22VuFUDm-Q@mail.gmail.com>
 <CAM8DdeWsBfiPdXGMbZxyM8iYs9yE6JXTK4zZgv=BtefiUJW7Dg@mail.gmail.com>
 <CADAEEV393oZZ0COMYHC1vj_-rkY=Q7pwWCiQ_ViwgsV1WBd7wQ@mail.gmail.com>
Message-ID: <CAMeQZi0+aOywoocOSkQQQtXG8sHO1kCUQHE-qBD7MJg0LJ=yEQ@mail.gmail.com>

Hi,

I intend to be there.

Best,
Manju

On Wed, Jan 22, 2025 at 10:03?PM Bruna Martins dos Santos <
bruna.mrtns at gmail.com> wrote:

> Also count me in !
>
>
> On Wed, Jan 22, 2025 at 2:01?PM Tomslin Samme-Nlar <mesumbeslin at gmail.com>
> wrote:
>
>> I am going
>>
>> Warmly,
>> Tomslin
>>
>> On Wed, 22 Jan 2025, 10:02 Rafik Dammak, <rafik.dammak at gmail.com> wrote:
>>
>>> Dear councillors,
>>>
>>>
>>> We need to confirm who from travel supported councillors will be able
>>> attend ICANN meeting in Prague. Please respond within the next 7 days.
>>>
>>>
>>> Best,
>>>
>>> Rafik
>>>
>>> ---------- Forwarded message ---------
>>> Dear all,
>>>
>>> In order to service your travel needs for ICANN83 Prague in a timely
>>> fashion, please submit your meeting database to gnso-secs at icann.org by *Monday,
>>> 10 February 2025. *It is important all funded travel air booking is
>>> completed by due date given in ICANN Travel emails. There seems to be some
>>> struggle in this area, if you could please make sure all names put forward
>>> understand the deadlines.
>>>
>>> Please share with all funded travelers, the travel support guidelines
>>> wiki space: https://community.icann.org/x/lgvxAg and highlight the
>>> communications responsibilities section:
>>>
>>> ICANN Travel Support attempts to reach a supported traveler four times
>>> before deeming the supported traveler unresponsive:
>>>
>>>    1. ICANN Travel Support sends ?welcome email.?
>>>    2. If there is no response after seven business days, ICANN Travel
>>>    Support sends a second email, copying ICANN support staff.
>>>    3. If there is no response five business days after the second
>>>    email, ICANN Travel Support sends a third email, copying ICANN support
>>>    staff and the community group chair.
>>>    4. If there is no response five business days after the third email,
>>>    ICANN Travel Support sends a fourth email, copying ICANN support staff and
>>>    the community group chair.
>>>
>>> If there is no response three days after the fourth attempt to reach the
>>> supported traveler, the community group may substitute another traveler.
>>>
>>>
>>>
>>> A timely response would be appreciated in view of visa issues and the
>>> OFAC review. The deadline for submissions is critical to allow for
>>> confirmed reservation numbers as required for visa and travel arrangements.
>>>
>>>  *TRAVEL BOOKING PROCESS*
>>>
>>>
>>>
>>> In order for Funded Travelers to start booking travel, they MUST
>>> complete Steps 1, 2, and 3.
>>>
>>>
>>>
>>> *WHO*
>>>
>>> *WHAT*
>>>
>>> 1
>>>
>>> Funded Traveler
>>>
>>> Register for meeting using the Funded Traveler Registration Link
>>> provided by ICANN Travel Support
>>>
>>> 2
>>>
>>> Funded Traveler
>>>
>>> Approved for Trade Regulations Review
>>>
>>> 3
>>>
>>> Funded Traveler
>>>
>>> Receive Travel Funding Confirmation Email from ICANN Travel Support
>>>
>>> 4
>>>
>>> *Funded Traveler*
>>>
>>> *Book Air Travel for meeting*
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>  *Approved dates of Arrival and Departure*
>>>
>>> *ARRIVAL DATE*
>>>
>>> *DEPARTURE DATE*
>>>
>>> *Sunday, 08 June *
>>>
>>> *Friday, 13 June*
>>>
>>>
>>>
>>> For air, this must be booked using either via our online booking
>>> platform (Concur) or official travel agency (FCM). ICANN org does not allow
>>> self-booking.
>>>
>>>
>>>
>>> Please note that when requesting travel support, in the interest of
>>> fairness and in light of budget restrictions we would like you to take the
>>> following into consideration:
>>>
>>>
>>>
>>> 1.               Respond timely to ICANN Travel regarding your upcoming
>>> travel and book by deadline given in email.
>>>
>>> 2.               If you require a visa to enter the country, please
>>> make sure to acquire your visa immediately. Follow link here
>>> <https://community.icann.org/x/fSfxAg> for assistance.
>>>
>>> 3.               Friday, 25 April 2025* (45 days before travel)* is the
>>> last day to submit additions/replacements.
>>>
>>> 4.               Requests past the deadline will be handled on a
>>> case-by-case basis by ICANN. All additional travelers added after the
>>> 90-day deadline are subject to availability, may NOT be placed in the same
>>> hotel as their funded traveler groups, and may not be able to attend due to
>>> visa issues.
>>>
>>> 5.               If possible, please book direct travel
>>> requests. Detours and multi-stop trips are unfortunately not guaranteed.
>>>
>>> 6.               If travelers want to extend their stay this must be
>>> done at their own expense and should contact the hotel directly once the
>>> ICANN hotel confirmation has be sent to them.
>>>
>>> 7.               *Privately Booked Reservations*: ICANN will not refund
>>> or take over accommodations directly booked by the funded traveler. If a
>>> replacement has an existing hotel reservation, they will need to cancel
>>> their reservation and ICANN will not be able to take over their reservation.
>>>
>>>
>>>
>>> Reminder:
>>>
>>>    - GNSO supported traveler with a designated hotel accommodation
>>>    funding, a hotel room is automatically secured for you, please *DO
>>>    NOT* book your own hotel as it is un-reimbursable.
>>>    - All personal data provided to ICANN org in for purposes of
>>>    providing travel support for participants related to ICANN events will be
>>>    processed in accordance with the ICANN Privacy Policy [icann.org]
>>>    <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=A_rkvV7hcBAIOU12pQX6fSkWBC6-P-bPaQDowX2oR_A&s=WwqcPGGS1mvkGHO5BjVc3E9ewPva_WoF-Snq25kq0OM&e=>.
>>>    Should you have any questions or concerns about this Privacy Policy and our
>>>    privacy practices, you may contact us at privacy at icann.org.
>>>    - As a reminder, for the AGM meeting only, incoming Councilors get
>>>    funding, as well as the then-incumbent Councilors.
>>>
>>>
>>>
>>>  Many thanks for your cooperation!
>>>
>>>  Thank you.
>>>
>>>
>>>
>>> Kind regards,
>>>
>>>
>>>
>>> Terri
>>>
>>> Policy Team Supporting the GNSO
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> NCSG-PC mailing list
>>> NCSG-PC at lists.ncsg.is
>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
>
>
> --
>
> *Bruna Martins dos Santos *
>
> German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von
> Humboldt Foundation <https://www.humboldt-foundation.de/>
> MAG Member 2022, 2023 and 2024
>
> Member | Coaliz?o Direitos na Rede <https://direitosnarede.org.br/>
> Co-Coordinator | Internet Governance Caucus  <https://igcaucus.org/>
>
> Twitter: @boomartins <https://twitter.com/boomartins> // Skype:
> bruna.martinsantos
> Email: bruna.mrtns at gmail.com
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250123/262895f6/attachment.htm>

From pedrodeperdigaolana at gmail.com  Wed Jan 22 17:25:12 2025
From: pedrodeperdigaolana at gmail.com (=?UTF-8?Q?Pedro_de_Perdig=C3=A3o_Lana?=)
Date: Wed, 22 Jan 2025 12:25:12 -0300
Subject: [NCSG-PC] [NCSG-EC] Topics/Agenda for NCPH session
In-Reply-To: <CAN1qJvCwG2ZaACToW0SQuyQgxREFPA2EtX9sXLi_yg8o+S5S-g@mail.gmail.com>
References: <CAH5sThkdECWZJH545Tc7z94-7fZHvnET_TVfU5c9KgfAa0qzcg@mail.gmail.com>
 <CAH5sThnexff=xhKQBTqU5WkB_MCKKoFO6A=d0jhSj0sSHA7xcQ@mail.gmail.com>
 <CAN1qJvCwG2ZaACToW0SQuyQgxREFPA2EtX9sXLi_yg8o+S5S-g@mail.gmail.com>
Message-ID: <CAGSP6RS3ZYLwzacNBiosxVFHWe8hC9FTFNem_4u5wH-rQb5JWQ@mail.gmail.com>

Hi Rafik,

Sorry, forgot about the policy question. It was related to the UDRP, but,
as mentioned in the call today, this seems to be solely being discussed at
the GNSO Council level and I don't think there has been any contact from
these other organizations (mostly WIPO and INTA) trying to rush the process
- which is good, considering that rushing it right now would not be a good
thing for us and for the community, because there would be too many other
heated and important discussions going on to allow for an appropriate focus
on this matter.

Cordialmente,

*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 qua., 22 de jan. de 2025 ?s 12:10, farzaneh badii via NCSG-EC <
ncsg-ec at lists.ncsg.is> escreveu:

> Hi
>
> I was thinking we should discuss the future of ?dns abuse? and talk about
> our positions and plans.
>
> Farzaneh
>
>
> On Tue, Jan 21, 2025 at 12:44?AM Rafik Dammak via NCSG-EC <
> ncsg-ec at lists.ncsg.is> wrote:
>
>> hi all,
>>
>> any comment/input?
>>
>> Rafik
>>
>> Le jeu. 16 janv. 2025 ? 11:12, Rafik Dammak <rafik.dammak at gmail.com> a
>> ?crit :
>>
>>> Hi all,
>>>
>>> In order to prepare for the session with CSG, do you have any
>>> suggestions for the agenda and desired outcomes of the meeting. We can
>>> build on the topics we discussed on day 0 in Istanbul if there is any
>>> particular follow-up we would like. For policy topics, I assume it is in an
>>> area where there are several divergences on some issues.
>>> I think one topic to share an update on is the procedure for board seat
>>> 14.
>>>
>>> Best,
>>>
>>> Rafik
>>>
>> _______________________________________________
>> 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/20250122/99e354b4/attachment.htm>

From pedrodeperdigaolana at gmail.com  Fri Jan 24 13:38:10 2025
From: pedrodeperdigaolana at gmail.com (=?UTF-8?Q?Pedro_de_Perdig=C3=A3o_Lana?=)
Date: Fri, 24 Jan 2025 08:38:10 -0300
Subject: [NCSG-PC] [NCSG-EC] Fwd: [GNSO-SG-C-Leadership] Feedback
 Requested: How We Meet Community Group
In-Reply-To: <CAH5sThmh2oeMUTP=p7QTj7wA_JvTbRWps+U4D6MP3xk=AOX3jg@mail.gmail.com>
References: <4dc64fca6b7f4193a88bf10c5b076156@amazon.com>
 <0100019474f81e50-a3ee597c-b322-405d-a31d-c79451fb9daa-000000@email.amazonses.com>
 <CAH5sThmh2oeMUTP=p7QTj7wA_JvTbRWps+U4D6MP3xk=AOX3jg@mail.gmail.com>
Message-ID: <CAGSP6RQV5-F9XFOQ=WOOmAVUaJyZnUoQhR3BKUH1L8nRpQK57Q@mail.gmail.com>

Hi Rafik,

Just as a first comment before reading through all documents (focusing (for
now) only on the graphs and shorter docs), although this may be deeply
unpopular, comparing the budget for other events that I participated in one
way or another of the organization and/or supervision, hotel accommodation
seems to be in a higher percentage (meaning it looks a bit
disproportionate), especially if we take into account that flight costs
refer to the participation of (many) people from all over the world. I
note, however, that this may be caused by the large amount of days some
ICANN meetings have.

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 seg., 20 de jan. de 2025 ?s 22:32, Rafik Dammak via NCSG-EC <
ncsg-ec at lists.ncsg.is> escreveu:

> Hi all,
>
> there is some update and request for input on "How to meet". We should
> review the different options proposed in the strawman document.
> I will share this later with larger NCSG membership and adding some
> context.
>
> Best,
>
> Rafik
>
> ---------- Forwarded message ---------
> De : DiBiase, Gregory via GNSO-SG-C-Leadership <
> gnso-sg-c-leadership at icann.org>
> Date: sam. 18 janv. 2025 ? 00:53
> Subject: [GNSO-SG-C-Leadership] Feedback Requested: How We Meet Community
> Group
> To: gnso-sg-c-leadership at icann.org <gnso-sg-c-leadership at icann.org>
>
>
>
>    - *Attachments protected by Amazon: *
>    - Updated Cost Data Related To ICANN Pu...copy.pdf
>    <https://us-east-1.secure-attach.amazon.com/33f1c678-96e1-4015-8dfb-f02f5c2e62ff/fceed8c9-d3da-417d-aa8d-41514592e7f0> |
>
>    - How We Meet - Summary of Input from C...copy.pdf
>    <https://us-east-1.secure-attach.amazon.com/33f1c678-96e1-4015-8dfb-f02f5c2e62ff/3c682e35-ece6-4488-826b-6517b486832b> |
>
>    - 2024 Cost Analysis of ICANN Travel & ...copy.pdf
>    <https://us-east-1.secure-attach.amazon.com/33f1c678-96e1-4015-8dfb-f02f5c2e62ff/0e35facb-ecde-44e8-8d07-cc01120f2420> |
>
>    - 2022 - 2024 Cost Analysis of ICANN In...copy.pdf
>    <https://us-east-1.secure-attach.amazon.com/33f1c678-96e1-4015-8dfb-f02f5c2e62ff/483dcc57-02b6-4c29-85a3-cce7bef43c46> |
>
>    - Final - Charter for the Community Gro...tegy.pdf
>    <https://us-east-1.secure-attach.amazon.com/33f1c678-96e1-4015-8dfb-f02f5c2e62ff/e8ebf9cf-04c4-4fcc-8f90-4a16faef4b6a> |
>
>    - DRAFT - How We Meet Community Group R...Docs.pdf
>    <https://us-east-1.secure-attach.amazon.com/33f1c678-96e1-4015-8dfb-f02f5c2e62ff/36b9c423-0e0f-446c-8325-34689df8deb9> |
>
>    - ICANN
>    <https://us-east-1.secure-attach.amazon.com/33f1c678-96e1-4015-8dfb-f02f5c2e62ff/865639da-f3f1-4545-a8f4-79fd73d55a9d> |
>
>    - ATT00001.txt
>    <https://us-east-1.secure-attach.amazon.com/33f1c678-96e1-4015-8dfb-f02f5c2e62ff/89a83194-2f45-4aaa-8be7-722c893a9aad> |
>
>
> Amazon has replaced the attachments in this email with download links.
> Downloads will be available until February 16, 2025, 15:53 (UTC+00:00). Tell
> us what you think
> <https://amazonexteu.qualtrics.com/jfe/form/SV_ehuz6zGo8YnsRKK>
> For more information click here
> <https://docs.secure-attach.amazon.com/guide>
>
> Dear SG/C Chairs,
>
>
>
> I am hoping for your help gathering feedback on ICANN?s proposals for ?How
> We Meet? (a.k.a. how to make ICANN?s meetings more cost effective).
>
>
>
> As GNSO Chair, I?ve been tasked with gathering feedback on potential
> recommendations that will go out to the Community for public comment.
>
>
>
> Attached are a number of documents breaking down the cost of ICANN
> meetings, but I think the most pertinent is one titled ?How We Meet
> Community Group Report?. ICANN has labeled this document as a ?draft
> strawman proposal? but it?s really a menu of options for reducing cost. I
> think a good first step is for each SG/C to review these options and
> provide feedback on:
>
>    1. What options are missing?
>    2. What options are unacceptable/problematic? (i.e., should not be put
>    out for public comment).
>    3. Do you have more granular feedback on the options provided?
>
> I think this could give me a starting point for giving feedback to ICANN.
> I have already flagged to ICANN that the GNSO is a diverse body and will
> likely have disagreements, so a broader public comment on the ?strawman?
> will be necessary.
>
>
>
> Please provide any other thoughts you may have as this group starts their
> work.
>
>
>
> Thank You!
>
>
>
> Greg
>
>
>
>
>
>
>
> *From:* Alperen Eken via How-we-meet-2025 <how-we-meet-2025 at icann.org>
> *Sent:* Tuesday, January 7, 2025 1:46 PM
> *To:* how-we-meet-2025 at icann.org
> *Subject:* [EXTERNAL] [How-We-Meet-2025] Agenda and Documents - Meeting
> #1 - How We Meet Community Group
>
>
>
> *CAUTION*: This email originated from outside of the organization. Do not
> click links or open attachments unless you can confirm the sender and know
> the content is safe.
>
>
>
> Dear all,
>
>
>
> Happy New Year! I hope this message finds you well and that you?ve had a
> wonderful start to 2025.
>
>
>
> Next week, we will hold our first meeting to discuss updates to the ICANN
> Meetings Strategy. This meeting is scheduled for:
> Date: 13 January 2024
> Time: 1700-1800 UTC
>
>
>
> We?re looking forward to your participation and valuable contributions.
> Please find attached the meeting agenda, some documents we prepared for
> this group, and background documents that were previously shared with SOAC
> Chairs:
>
>    1. Meeting invitation ICS file
>    2. Agenda
>    3. Final - Charter for the Community Group for the Meeting Strategy
>    4. Draft - How We Meet Community Group Report
>
> Background Documents:
>
>    5. How We Meet - Summary of Input from Community Groups
>    6. Updated Cost Data Related to ICANN Public Meetings
>    7. 2024 Cost Analysis of ICANN Travel & Meetings
>    8. 2022 ? 2024 Cost Analysis of ICANN Intersessional Meetings
>
>
>
> We are aware that there are a lot of materials, therefore we are keeping a
> drive folder for you where you can find all these documents, meeting
> agendas, and notes of our future meetings in addition to any document that
> we will be collaborating on. Here is the link:
> https://drive.google.com/drive/folders/1-IGp5C4QAZjj5OJlkYRARnpsg2HBgtV_?usp=drive_link
>
>
>
> Your input is essential as we will be working within a tight timeline.
>
>
>
> I will serve as the project manager for this work, if you have any
> questions, additional topics to propose for the agenda, or any other issue
> please feel free to reach out at alperen.eken at icann.org .
>
>
>
> We appreciate your participation and look forward to seeing everyone at
> the meeting!
>
>
>
> Kind regards,
>
>
>
> Alp Eken
>
> Policy Development Support Senior Specialist
>
> Internet Corporation for Assigned Names and Numbers (ICANN)
>
>
> _______________________________________________
> GNSO-SG-C-Leadership mailing list -- gnso-sg-c-leadership at icann.org
> To unsubscribe send an email to gnso-sg-c-leadership-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/20250124/b618d0bb/attachment.htm>

From mesumbeslin at gmail.com  Sat Jan 25 12:46:56 2025
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Sat, 25 Jan 2025 21:46:56 +1100
Subject: [NCSG-PC] NCSG PC Chair Election
In-Reply-To: <CAM8DdeWtf0HXJDiMBrCnKLBa4=RrRPGcmsWM5QvcYAC-L=pdOw@mail.gmail.com>
References: <CAM8DdeWtf0HXJDiMBrCnKLBa4=RrRPGcmsWM5QvcYAC-L=pdOw@mail.gmail.com>
Message-ID: <CAM8DdeUf_g47bzQz=uh=SkoZ6v7uf8B4vyRfzTnj1ycajiQAsQ@mail.gmail.com>

Hi all,

There were no nominations received. I suppose the PC is choosing to leave
things as they are?

Warmly,
Tomslin

On Wed, 8 Jan 2025, 00:22 Tomslin Samme-Nlar, <mesumbeslin at gmail.com> wrote:

> Hi PC members,
>
> I am writing to call for the election of the Policy Committee Chair.
> Normally this is started towards the end of October but it was delayed to
> ensure we have all the constituency representatives elected and added to
> the list first.
>
> ..........
>
> POSITION
>
> Policy Committee Chair over the course of a 1 year term.  The chair tasks
> can be summarized into:
>
>
>    -
>
>    Managing PC work:
>    -
>       -
>
>       Acting as project manager and tracking tasks and activities;
>       -
>
>       Following closely policy discussions, initiatives and public
>       comments. Liaising with drafting team for public comments;
>       -
>
>       Following closely the deadlines, ensuring NCSG has enough
>       volunteers to draft comments and delivering in a timely manner;
>       -
>
>       Identify NCSG members participating in PDP WG and liaise with them
>       for reporting and updates; e
>       -
>
>       Organize the appointment of NCSG representatives by PC to GNSO
>       council committees, PDP WG when there is a call for members etc.
>
>
>    -
>
>    Liaising with GNSO Council work and its committees (SSC, SCBO, small
>    teams);
>    -
>
>    Track progress for working groups and approaching members to get
>    updates;
>    -
>
>    Planning tasks (e.g. review of public comments, selection/appointment
>    of NCSG representatives), schedule the NCSG policy calls and PC meetings,
>    sharing agendas with PC members for review;
>    -
>
>    Plan and schedule topic webinars on policy issue;
>    -
>
>    Liaising with NCSG chair regarding NCSG letters to board and
>    communication with other SG/C;
>    -
>
>    Work with PC vice-chairs.
>
>
> IMPORTANT INFO
>
>
>    -
>
>    This is a call open to all NCSG councillors and representatives from
>    NCUC and NPOC to the Policy Committee;
>    -
>
>    Nominations and self-nominations are both permitted and should be sent
>    to the Policy Committee List;
>    -
>
>    After the nominations, a candidate's confirmation of acceptance and
>    expression of interest should be sent to the Policy Committee mailing list
>    by 14th January;
>
>
>
> TIMELINE
>
>
>
> 1- Nomination period: from 7th January to 14th January
>
>    -
>
>    The nominee should accept the nomination and send a short SOI by the
>    14th of January.
>
>
>
> 2- Election: from 15th to 21st January
>
> Voting is mandatory to all Policy Committee members. The GNSO support
> staff will act as the election officer. The options in the ballot should be
> the candidates who confirmed by the deadline and NOTA.
>
>
>
> 3- Results: should be available by 22nd January
>
> The candidate with 2/3 of the NCSG?PC membership votes will be declared
> winner.
>
>
>
>
>
> VICE-CHAIRS APPOINTMENTS
>
>
>
> Once the Policy Committee Chair is confirmed, a second call for interest
> will be issued on this list and the PC members can elect up to 2
> Vice-chairs. The appointment of the volunteers will be confirmed if there
> is no objection within PC.
>
>
> Warmly
>
> Tomslin
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250125/7d5dc265/attachment.htm>

From rafik.dammak at gmail.com  Mon Jan 27 02:46:46 2025
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Mon, 27 Jan 2025 09:46:46 +0900
Subject: [NCSG-PC] ICANN83 | Prague | Supported Travelers Database Due |
 Monday, 10 February 2025
In-Reply-To: <CAMeQZi0+aOywoocOSkQQQtXG8sHO1kCUQHE-qBD7MJg0LJ=yEQ@mail.gmail.com>
References: <66C19F06-C253-4192-87B8-A4EB396BCECD@icann.org>
 <CAH5sThnSt_+XL0a0qrtH8H3iEcq-owibbymvp8=E22VuFUDm-Q@mail.gmail.com>
 <CAM8DdeWsBfiPdXGMbZxyM8iYs9yE6JXTK4zZgv=BtefiUJW7Dg@mail.gmail.com>
 <CADAEEV393oZZ0COMYHC1vj_-rkY=Q7pwWCiQ_ViwgsV1WBd7wQ@mail.gmail.com>
 <CAMeQZi0+aOywoocOSkQQQtXG8sHO1kCUQHE-qBD7MJg0LJ=yEQ@mail.gmail.com>
Message-ID: <CAH5sTh=jybdNNHp7+huj=R9Xb-tOiuWDQTD78_1WSa8JZROdoQ@mail.gmail.com>

Thanks all for your confirmation.
@farzaneh badii <farzaneh.badii at gmail.com>  @Akinremi Peter Taiwo
<compsoftnet at gmail.com>  can you please confirm ?

Best,

Rafik

Le jeu. 23 janv. 2025 ? 22:52, ??? Manju Chen <manju at nii.org.tw> a ?crit :

> Hi,
>
> I intend to be there.
>
> Best,
> Manju
>
> On Wed, Jan 22, 2025 at 10:03?PM Bruna Martins dos Santos <
> bruna.mrtns at gmail.com> wrote:
>
>> Also count me in !
>>
>>
>> On Wed, Jan 22, 2025 at 2:01?PM Tomslin Samme-Nlar <mesumbeslin at gmail.com>
>> wrote:
>>
>>> I am going
>>>
>>> Warmly,
>>> Tomslin
>>>
>>> On Wed, 22 Jan 2025, 10:02 Rafik Dammak, <rafik.dammak at gmail.com> wrote:
>>>
>>>> Dear councillors,
>>>>
>>>>
>>>> We need to confirm who from travel supported councillors will be able
>>>> attend ICANN meeting in Prague. Please respond within the next 7 days.
>>>>
>>>>
>>>> Best,
>>>>
>>>> Rafik
>>>>
>>>> ---------- Forwarded message ---------
>>>> Dear all,
>>>>
>>>> In order to service your travel needs for ICANN83 Prague in a timely
>>>> fashion, please submit your meeting database to gnso-secs at icann.org by *Monday,
>>>> 10 February 2025. *It is important all funded travel air booking is
>>>> completed by due date given in ICANN Travel emails. There seems to be some
>>>> struggle in this area, if you could please make sure all names put forward
>>>> understand the deadlines.
>>>>
>>>> Please share with all funded travelers, the travel support guidelines
>>>> wiki space: https://community.icann.org/x/lgvxAg and highlight the
>>>> communications responsibilities section:
>>>>
>>>> ICANN Travel Support attempts to reach a supported traveler four times
>>>> before deeming the supported traveler unresponsive:
>>>>
>>>>    1. ICANN Travel Support sends ?welcome email.?
>>>>    2. If there is no response after seven business days, ICANN Travel
>>>>    Support sends a second email, copying ICANN support staff.
>>>>    3. If there is no response five business days after the second
>>>>    email, ICANN Travel Support sends a third email, copying ICANN support
>>>>    staff and the community group chair.
>>>>    4. If there is no response five business days after the third
>>>>    email, ICANN Travel Support sends a fourth email, copying ICANN support
>>>>    staff and the community group chair.
>>>>
>>>> If there is no response three days after the fourth attempt to reach
>>>> the supported traveler, the community group may substitute another traveler.
>>>>
>>>>
>>>>
>>>> A timely response would be appreciated in view of visa issues and the
>>>> OFAC review. The deadline for submissions is critical to allow for
>>>> confirmed reservation numbers as required for visa and travel arrangements.
>>>>
>>>>  *TRAVEL BOOKING PROCESS*
>>>>
>>>>
>>>>
>>>> In order for Funded Travelers to start booking travel, they MUST
>>>> complete Steps 1, 2, and 3.
>>>>
>>>>
>>>>
>>>> *WHO*
>>>>
>>>> *WHAT*
>>>>
>>>> 1
>>>>
>>>> Funded Traveler
>>>>
>>>> Register for meeting using the Funded Traveler Registration Link
>>>> provided by ICANN Travel Support
>>>>
>>>> 2
>>>>
>>>> Funded Traveler
>>>>
>>>> Approved for Trade Regulations Review
>>>>
>>>> 3
>>>>
>>>> Funded Traveler
>>>>
>>>> Receive Travel Funding Confirmation Email from ICANN Travel Support
>>>>
>>>> 4
>>>>
>>>> *Funded Traveler*
>>>>
>>>> *Book Air Travel for meeting*
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>  *Approved dates of Arrival and Departure*
>>>>
>>>> *ARRIVAL DATE*
>>>>
>>>> *DEPARTURE DATE*
>>>>
>>>> *Sunday, 08 June *
>>>>
>>>> *Friday, 13 June*
>>>>
>>>>
>>>>
>>>> For air, this must be booked using either via our online booking
>>>> platform (Concur) or official travel agency (FCM). ICANN org does not allow
>>>> self-booking.
>>>>
>>>>
>>>>
>>>> Please note that when requesting travel support, in the interest of
>>>> fairness and in light of budget restrictions we would like you to take the
>>>> following into consideration:
>>>>
>>>>
>>>>
>>>> 1.               Respond timely to ICANN Travel regarding your
>>>> upcoming travel and book by deadline given in email.
>>>>
>>>> 2.               If you require a visa to enter the country, please
>>>> make sure to acquire your visa immediately. Follow link here
>>>> <https://community.icann.org/x/fSfxAg> for assistance.
>>>>
>>>> 3.               Friday, 25 April 2025* (45 days before travel)* is
>>>> the last day to submit additions/replacements.
>>>>
>>>> 4.               Requests past the deadline will be handled on a
>>>> case-by-case basis by ICANN. All additional travelers added after the
>>>> 90-day deadline are subject to availability, may NOT be placed in the same
>>>> hotel as their funded traveler groups, and may not be able to attend due to
>>>> visa issues.
>>>>
>>>> 5.               If possible, please book direct travel
>>>> requests. Detours and multi-stop trips are unfortunately not guaranteed.
>>>>
>>>> 6.               If travelers want to extend their stay this must be
>>>> done at their own expense and should contact the hotel directly once the
>>>> ICANN hotel confirmation has be sent to them.
>>>>
>>>> 7.               *Privately Booked Reservations*: ICANN will not
>>>> refund or take over accommodations directly booked by the funded traveler.
>>>> If a replacement has an existing hotel reservation, they will need to
>>>> cancel their reservation and ICANN will not be able to take over their
>>>> reservation.
>>>>
>>>>
>>>>
>>>> Reminder:
>>>>
>>>>    - GNSO supported traveler with a designated hotel accommodation
>>>>    funding, a hotel room is automatically secured for you, please *DO
>>>>    NOT* book your own hotel as it is un-reimbursable.
>>>>    - All personal data provided to ICANN org in for purposes of
>>>>    providing travel support for participants related to ICANN events will be
>>>>    processed in accordance with the ICANN Privacy Policy [icann.org]
>>>>    <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=A_rkvV7hcBAIOU12pQX6fSkWBC6-P-bPaQDowX2oR_A&s=WwqcPGGS1mvkGHO5BjVc3E9ewPva_WoF-Snq25kq0OM&e=>.
>>>>    Should you have any questions or concerns about this Privacy Policy and our
>>>>    privacy practices, you may contact us at privacy at icann.org.
>>>>    - As a reminder, for the AGM meeting only, incoming Councilors get
>>>>    funding, as well as the then-incumbent Councilors.
>>>>
>>>>
>>>>
>>>>  Many thanks for your cooperation!
>>>>
>>>>  Thank you.
>>>>
>>>>
>>>>
>>>> Kind regards,
>>>>
>>>>
>>>>
>>>> Terri
>>>>
>>>> Policy Team Supporting the GNSO
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> NCSG-PC mailing list
>>>> NCSG-PC at lists.ncsg.is
>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>
>>> _______________________________________________
>>> NCSG-PC mailing list
>>> NCSG-PC at lists.ncsg.is
>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>
>>
>>
>> --
>>
>> *Bruna Martins dos Santos *
>>
>> German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander
>> von Humboldt Foundation <https://www.humboldt-foundation.de/>
>> MAG Member 2022, 2023 and 2024
>>
>> Member | Coaliz?o Direitos na Rede <https://direitosnarede.org.br/>
>> Co-Coordinator | Internet Governance Caucus  <https://igcaucus.org/>
>>
>> Twitter: @boomartins <https://twitter.com/boomartins> // Skype:
>> bruna.martinsantos
>> Email: bruna.mrtns at gmail.com
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250127/f05d2071/attachment.htm>

From rafik.dammak at gmail.com  Mon Jan 27 02:49:53 2025
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Mon, 27 Jan 2025 09:49:53 +0900
Subject: [NCSG-PC] [NCSG-EC] Topics/Agenda for NCPH session
In-Reply-To: <CAGSP6RS3ZYLwzacNBiosxVFHWe8hC9FTFNem_4u5wH-rQb5JWQ@mail.gmail.com>
References: <CAH5sThkdECWZJH545Tc7z94-7fZHvnET_TVfU5c9KgfAa0qzcg@mail.gmail.com>
 <CAH5sThnexff=xhKQBTqU5WkB_MCKKoFO6A=d0jhSj0sSHA7xcQ@mail.gmail.com>
 <CAN1qJvCwG2ZaACToW0SQuyQgxREFPA2EtX9sXLi_yg8o+S5S-g@mail.gmail.com>
 <CAGSP6RS3ZYLwzacNBiosxVFHWe8hC9FTFNem_4u5wH-rQb5JWQ@mail.gmail.com>
Message-ID: <CAH5sThmZm5AaTFfVqQm1dJQ6M7OtkAJkjGDBJiEsRvNvAeu+Hg@mail.gmail.com>

Hi Farzaneh, Pedro,

Thanks for sharing those topics,
so till now as draft topics we have one admin about membership system
follow-up, board seat 14, DNS abuse positions and plan, and about UDRP
review.
It can be a starter list for discussion with CSG. It is a one hour session
so we might drop some issues.
to the rest of PC and EC members, any other topic for NCPH meeting?

 Best,

Rafik

Le jeu. 23 janv. 2025 ? 00:25, Pedro de Perdig?o Lana <
pedrodeperdigaolana at gmail.com> a ?crit :

> Hi Rafik,
>
> Sorry, forgot about the policy question. It was related to the UDRP, but,
> as mentioned in the call today, this seems to be solely being discussed at
> the GNSO Council level and I don't think there has been any contact from
> these other organizations (mostly WIPO and INTA) trying to rush the process
> - which is good, considering that rushing it right now would not be a good
> thing for us and for the community, because there would be too many other
> heated and important discussions going on to allow for an appropriate focus
> on this matter.
>
> Cordialmente,
>
> *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 qua., 22 de jan. de 2025 ?s 12:10, farzaneh badii via NCSG-EC <
> ncsg-ec at lists.ncsg.is> escreveu:
>
>> Hi
>>
>> I was thinking we should discuss the future of ?dns abuse? and talk about
>> our positions and plans.
>>
>> Farzaneh
>>
>>
>> On Tue, Jan 21, 2025 at 12:44?AM Rafik Dammak via NCSG-EC <
>> ncsg-ec at lists.ncsg.is> wrote:
>>
>>> hi all,
>>>
>>> any comment/input?
>>>
>>> Rafik
>>>
>>> Le jeu. 16 janv. 2025 ? 11:12, Rafik Dammak <rafik.dammak at gmail.com> a
>>> ?crit :
>>>
>>>> Hi all,
>>>>
>>>> In order to prepare for the session with CSG, do you have any
>>>> suggestions for the agenda and desired outcomes of the meeting. We can
>>>> build on the topics we discussed on day 0 in Istanbul if there is any
>>>> particular follow-up we would like. For policy topics, I assume it is in an
>>>> area where there are several divergences on some issues.
>>>> I think one topic to share an update on is the procedure for board seat
>>>> 14.
>>>>
>>>> Best,
>>>>
>>>> Rafik
>>>>
>>> _______________________________________________
>>> 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/20250127/1618525b/attachment.htm>

From farzaneh.badii at gmail.com  Mon Jan 27 02:49:59 2025
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Sun, 26 Jan 2025 19:49:59 -0500
Subject: [NCSG-PC] ICANN83 | Prague | Supported Travelers Database Due |
 Monday, 10 February 2025
In-Reply-To: <CAH5sTh=jybdNNHp7+huj=R9Xb-tOiuWDQTD78_1WSa8JZROdoQ@mail.gmail.com>
References: <66C19F06-C253-4192-87B8-A4EB396BCECD@icann.org>
 <CAH5sThnSt_+XL0a0qrtH8H3iEcq-owibbymvp8=E22VuFUDm-Q@mail.gmail.com>
 <CAM8DdeWsBfiPdXGMbZxyM8iYs9yE6JXTK4zZgv=BtefiUJW7Dg@mail.gmail.com>
 <CADAEEV393oZZ0COMYHC1vj_-rkY=Q7pwWCiQ_ViwgsV1WBd7wQ@mail.gmail.com>
 <CAMeQZi0+aOywoocOSkQQQtXG8sHO1kCUQHE-qBD7MJg0LJ=yEQ@mail.gmail.com>
 <CAH5sTh=jybdNNHp7+huj=R9Xb-tOiuWDQTD78_1WSa8JZROdoQ@mail.gmail.com>
Message-ID: <CAN1qJvBBMTVNGtoyxV4JB6QxwZLuNUxwAzqF6XF9imq990SQsQ@mail.gmail.com>

oh sorry I already confirmed with Andrea.


Farzaneh


On Sun, Jan 26, 2025 at 7:46?PM Rafik Dammak <rafik.dammak at gmail.com> wrote:

>
> Thanks all for your confirmation.
> @farzaneh badii <farzaneh.badii at gmail.com>  @Akinremi Peter Taiwo
> <compsoftnet at gmail.com>  can you please confirm ?
>
> Best,
>
> Rafik
>
> Le jeu. 23 janv. 2025 ? 22:52, ??? Manju Chen <manju at nii.org.tw> a ?crit :
>
>> Hi,
>>
>> I intend to be there.
>>
>> Best,
>> Manju
>>
>> On Wed, Jan 22, 2025 at 10:03?PM Bruna Martins dos Santos <
>> bruna.mrtns at gmail.com> wrote:
>>
>>> Also count me in !
>>>
>>>
>>> On Wed, Jan 22, 2025 at 2:01?PM Tomslin Samme-Nlar <
>>> mesumbeslin at gmail.com> wrote:
>>>
>>>> I am going
>>>>
>>>> Warmly,
>>>> Tomslin
>>>>
>>>> On Wed, 22 Jan 2025, 10:02 Rafik Dammak, <rafik.dammak at gmail.com>
>>>> wrote:
>>>>
>>>>> Dear councillors,
>>>>>
>>>>>
>>>>> We need to confirm who from travel supported councillors will be able
>>>>> attend ICANN meeting in Prague. Please respond within the next 7 days.
>>>>>
>>>>>
>>>>> Best,
>>>>>
>>>>> Rafik
>>>>>
>>>>> ---------- Forwarded message ---------
>>>>> Dear all,
>>>>>
>>>>> In order to service your travel needs for ICANN83 Prague in a timely
>>>>> fashion, please submit your meeting database to gnso-secs at icann.org by
>>>>>  *Monday, 10 February 2025. *It is important all funded travel air
>>>>> booking is completed by due date given in ICANN Travel emails. There seems
>>>>> to be some struggle in this area, if you could please make sure all names
>>>>> put forward understand the deadlines.
>>>>>
>>>>> Please share with all funded travelers, the travel support guidelines
>>>>> wiki space: https://community.icann.org/x/lgvxAg and highlight the
>>>>> communications responsibilities section:
>>>>>
>>>>> ICANN Travel Support attempts to reach a supported traveler four times
>>>>> before deeming the supported traveler unresponsive:
>>>>>
>>>>>    1. ICANN Travel Support sends ?welcome email.?
>>>>>    2. If there is no response after seven business days, ICANN Travel
>>>>>    Support sends a second email, copying ICANN support staff.
>>>>>    3. If there is no response five business days after the second
>>>>>    email, ICANN Travel Support sends a third email, copying ICANN support
>>>>>    staff and the community group chair.
>>>>>    4. If there is no response five business days after the third
>>>>>    email, ICANN Travel Support sends a fourth email, copying ICANN support
>>>>>    staff and the community group chair.
>>>>>
>>>>> If there is no response three days after the fourth attempt to reach
>>>>> the supported traveler, the community group may substitute another traveler.
>>>>>
>>>>>
>>>>>
>>>>> A timely response would be appreciated in view of visa issues and the
>>>>> OFAC review. The deadline for submissions is critical to allow for
>>>>> confirmed reservation numbers as required for visa and travel arrangements.
>>>>>
>>>>>  *TRAVEL BOOKING PROCESS*
>>>>>
>>>>>
>>>>>
>>>>> In order for Funded Travelers to start booking travel, they MUST
>>>>> complete Steps 1, 2, and 3.
>>>>>
>>>>>
>>>>>
>>>>> *WHO*
>>>>>
>>>>> *WHAT*
>>>>>
>>>>> 1
>>>>>
>>>>> Funded Traveler
>>>>>
>>>>> Register for meeting using the Funded Traveler Registration Link
>>>>> provided by ICANN Travel Support
>>>>>
>>>>> 2
>>>>>
>>>>> Funded Traveler
>>>>>
>>>>> Approved for Trade Regulations Review
>>>>>
>>>>> 3
>>>>>
>>>>> Funded Traveler
>>>>>
>>>>> Receive Travel Funding Confirmation Email from ICANN Travel Support
>>>>>
>>>>> 4
>>>>>
>>>>> *Funded Traveler*
>>>>>
>>>>> *Book Air Travel for meeting*
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>  *Approved dates of Arrival and Departure*
>>>>>
>>>>> *ARRIVAL DATE*
>>>>>
>>>>> *DEPARTURE DATE*
>>>>>
>>>>> *Sunday, 08 June *
>>>>>
>>>>> *Friday, 13 June*
>>>>>
>>>>>
>>>>>
>>>>> For air, this must be booked using either via our online booking
>>>>> platform (Concur) or official travel agency (FCM). ICANN org does not allow
>>>>> self-booking.
>>>>>
>>>>>
>>>>>
>>>>> Please note that when requesting travel support, in the interest of
>>>>> fairness and in light of budget restrictions we would like you to take the
>>>>> following into consideration:
>>>>>
>>>>>
>>>>>
>>>>> 1.               Respond timely to ICANN Travel regarding your
>>>>> upcoming travel and book by deadline given in email.
>>>>>
>>>>> 2.               If you require a visa to enter the country, please
>>>>> make sure to acquire your visa immediately. Follow link here
>>>>> <https://community.icann.org/x/fSfxAg> for assistance.
>>>>>
>>>>> 3.               Friday, 25 April 2025* (45 days before travel)* is
>>>>> the last day to submit additions/replacements.
>>>>>
>>>>> 4.               Requests past the deadline will be handled on a
>>>>> case-by-case basis by ICANN. All additional travelers added after the
>>>>> 90-day deadline are subject to availability, may NOT be placed in the same
>>>>> hotel as their funded traveler groups, and may not be able to attend due to
>>>>> visa issues.
>>>>>
>>>>> 5.               If possible, please book direct travel
>>>>> requests. Detours and multi-stop trips are unfortunately not guaranteed.
>>>>>
>>>>> 6.               If travelers want to extend their stay this must be
>>>>> done at their own expense and should contact the hotel directly once the
>>>>> ICANN hotel confirmation has be sent to them.
>>>>>
>>>>> 7.               *Privately Booked Reservations*: ICANN will not
>>>>> refund or take over accommodations directly booked by the funded traveler.
>>>>> If a replacement has an existing hotel reservation, they will need to
>>>>> cancel their reservation and ICANN will not be able to take over their
>>>>> reservation.
>>>>>
>>>>>
>>>>>
>>>>> Reminder:
>>>>>
>>>>>    - GNSO supported traveler with a designated hotel accommodation
>>>>>    funding, a hotel room is automatically secured for you, please *DO
>>>>>    NOT* book your own hotel as it is un-reimbursable.
>>>>>    - All personal data provided to ICANN org in for purposes of
>>>>>    providing travel support for participants related to ICANN events will be
>>>>>    processed in accordance with the ICANN Privacy Policy [icann.org]
>>>>>    <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=A_rkvV7hcBAIOU12pQX6fSkWBC6-P-bPaQDowX2oR_A&s=WwqcPGGS1mvkGHO5BjVc3E9ewPva_WoF-Snq25kq0OM&e=>.
>>>>>    Should you have any questions or concerns about this Privacy Policy and our
>>>>>    privacy practices, you may contact us at privacy at icann.org.
>>>>>    - As a reminder, for the AGM meeting only, incoming Councilors get
>>>>>    funding, as well as the then-incumbent Councilors.
>>>>>
>>>>>
>>>>>
>>>>>  Many thanks for your cooperation!
>>>>>
>>>>>  Thank you.
>>>>>
>>>>>
>>>>>
>>>>> Kind regards,
>>>>>
>>>>>
>>>>>
>>>>> Terri
>>>>>
>>>>> Policy Team Supporting the GNSO
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> NCSG-PC mailing list
>>>>> NCSG-PC at lists.ncsg.is
>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>
>>>> _______________________________________________
>>>> NCSG-PC mailing list
>>>> NCSG-PC at lists.ncsg.is
>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>
>>>
>>>
>>> --
>>>
>>> *Bruna Martins dos Santos *
>>>
>>> German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander
>>> von Humboldt Foundation <https://www.humboldt-foundation.de/>
>>> MAG Member 2022, 2023 and 2024
>>>
>>> Member | Coaliz?o Direitos na Rede <https://direitosnarede.org.br/>
>>> Co-Coordinator | Internet Governance Caucus  <https://igcaucus.org/>
>>>
>>> Twitter: @boomartins <https://twitter.com/boomartins> // Skype:
>>> bruna.martinsantos
>>> Email: bruna.mrtns at gmail.com
>>> _______________________________________________
>>> NCSG-PC mailing list
>>> NCSG-PC at lists.ncsg.is
>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250126/5a07e7df/attachment.htm>

From pedrodeperdigaolana at gmail.com  Mon Jan 27 14:59:39 2025
From: pedrodeperdigaolana at gmail.com (=?UTF-8?Q?Pedro_de_Perdig=C3=A3o_Lana?=)
Date: Mon, 27 Jan 2025 09:59:39 -0300
Subject: [NCSG-PC] [NCSG-EC] Topics/Agenda for NCPH session
In-Reply-To: <CAH5sThmZm5AaTFfVqQm1dJQ6M7OtkAJkjGDBJiEsRvNvAeu+Hg@mail.gmail.com>
References: <CAH5sThkdECWZJH545Tc7z94-7fZHvnET_TVfU5c9KgfAa0qzcg@mail.gmail.com>
 <CAH5sThnexff=xhKQBTqU5WkB_MCKKoFO6A=d0jhSj0sSHA7xcQ@mail.gmail.com>
 <CAN1qJvCwG2ZaACToW0SQuyQgxREFPA2EtX9sXLi_yg8o+S5S-g@mail.gmail.com>
 <CAGSP6RS3ZYLwzacNBiosxVFHWe8hC9FTFNem_4u5wH-rQb5JWQ@mail.gmail.com>
 <CAH5sThmZm5AaTFfVqQm1dJQ6M7OtkAJkjGDBJiEsRvNvAeu+Hg@mail.gmail.com>
Message-ID: <CAGSP6RQr_2obSq8v1HJJSy5f2qA3JwJyf-VXqLrnq1kkQ+_gUw@mail.gmail.com>

Hi Rafik!

Sorry, I re-read my message and noticed I was a tad confusing: I believe we
already got the info that we needed related to the UDRP review during
Chris's meeting, which was that the pressure for this policy work to come
through isn't too high. I think it is better we keep it that way (i.e. not
giving it too much attention) and avoid discussing this subject within the
NCPH for now because I fear other constituencies could use this as an
argument to push for it even more.

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 dom., 26 de jan. de 2025 ?s 21:50, Rafik Dammak <rafik.dammak at gmail.com>
escreveu:

> Hi Farzaneh, Pedro,
>
> Thanks for sharing those topics,
> so till now as draft topics we have one admin about membership system
> follow-up, board seat 14, DNS abuse positions and plan, and about UDRP
> review.
> It can be a starter list for discussion with CSG. It is a one hour session
> so we might drop some issues.
> to the rest of PC and EC members, any other topic for NCPH meeting?
>
>  Best,
>
> Rafik
>
> Le jeu. 23 janv. 2025 ? 00:25, Pedro de Perdig?o Lana <
> pedrodeperdigaolana at gmail.com> a ?crit :
>
>> Hi Rafik,
>>
>> Sorry, forgot about the policy question. It was related to the UDRP, but,
>> as mentioned in the call today, this seems to be solely being discussed at
>> the GNSO Council level and I don't think there has been any contact from
>> these other organizations (mostly WIPO and INTA) trying to rush the process
>> - which is good, considering that rushing it right now would not be a good
>> thing for us and for the community, because there would be too many other
>> heated and important discussions going on to allow for an appropriate focus
>> on this matter.
>>
>> Cordialmente,
>>
>> *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 qua., 22 de jan. de 2025 ?s 12:10, farzaneh badii via NCSG-EC <
>> ncsg-ec at lists.ncsg.is> escreveu:
>>
>>> Hi
>>>
>>> I was thinking we should discuss the future of ?dns abuse? and talk
>>> about our positions and plans.
>>>
>>> Farzaneh
>>>
>>>
>>> On Tue, Jan 21, 2025 at 12:44?AM Rafik Dammak via NCSG-EC <
>>> ncsg-ec at lists.ncsg.is> wrote:
>>>
>>>> hi all,
>>>>
>>>> any comment/input?
>>>>
>>>> Rafik
>>>>
>>>> Le jeu. 16 janv. 2025 ? 11:12, Rafik Dammak <rafik.dammak at gmail.com> a
>>>> ?crit :
>>>>
>>>>> Hi all,
>>>>>
>>>>> In order to prepare for the session with CSG, do you have any
>>>>> suggestions for the agenda and desired outcomes of the meeting. We can
>>>>> build on the topics we discussed on day 0 in Istanbul if there is any
>>>>> particular follow-up we would like. For policy topics, I assume it is in an
>>>>> area where there are several divergences on some issues.
>>>>> I think one topic to share an update on is the procedure for board
>>>>> seat 14.
>>>>>
>>>>> Best,
>>>>>
>>>>> Rafik
>>>>>
>>>> _______________________________________________
>>>> 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/20250127/e3ade804/attachment.htm>

From farzaneh.badii at gmail.com  Mon Jan 27 21:51:24 2025
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Mon, 27 Jan 2025 14:51:24 -0500
Subject: [NCSG-PC] NCSG PC Chair Election
In-Reply-To: <CAM8DdeUf_g47bzQz=uh=SkoZ6v7uf8B4vyRfzTnj1ycajiQAsQ@mail.gmail.com>
References: <CAM8DdeWtf0HXJDiMBrCnKLBa4=RrRPGcmsWM5QvcYAC-L=pdOw@mail.gmail.com>
 <CAM8DdeUf_g47bzQz=uh=SkoZ6v7uf8B4vyRfzTnj1ycajiQAsQ@mail.gmail.com>
Message-ID: <CAN1qJvDZm-nmcU5e9c++ru2uHYS_0HWdwYCBrdwM93r-3K3A+w@mail.gmail.com>

Hi Tomslin

I am sorry I overlooked this email. I think it's best practice if we
actually do the election every year even if there is no contestant. But for
this year we can leave things as they are. :) Thanks for your hard work.






Farzaneh


On Sat, Jan 25, 2025 at 5:47?AM Tomslin Samme-Nlar <mesumbeslin at gmail.com>
wrote:

> Hi all,
>
> There were no nominations received. I suppose the PC is choosing to leave
> things as they are?
>
> Warmly,
> Tomslin
>
> On Wed, 8 Jan 2025, 00:22 Tomslin Samme-Nlar, <mesumbeslin at gmail.com>
> wrote:
>
>> Hi PC members,
>>
>> I am writing to call for the election of the Policy Committee Chair.
>> Normally this is started towards the end of October but it was delayed to
>> ensure we have all the constituency representatives elected and added to
>> the list first.
>>
>> ..........
>>
>> POSITION
>>
>> Policy Committee Chair over the course of a 1 year term.  The chair tasks
>> can be summarized into:
>>
>>
>>    -
>>
>>    Managing PC work:
>>    -
>>       -
>>
>>       Acting as project manager and tracking tasks and activities;
>>       -
>>
>>       Following closely policy discussions, initiatives and public
>>       comments. Liaising with drafting team for public comments;
>>       -
>>
>>       Following closely the deadlines, ensuring NCSG has enough
>>       volunteers to draft comments and delivering in a timely manner;
>>       -
>>
>>       Identify NCSG members participating in PDP WG and liaise with them
>>       for reporting and updates; e
>>       -
>>
>>       Organize the appointment of NCSG representatives by PC to GNSO
>>       council committees, PDP WG when there is a call for members etc.
>>
>>
>>    -
>>
>>    Liaising with GNSO Council work and its committees (SSC, SCBO, small
>>    teams);
>>    -
>>
>>    Track progress for working groups and approaching members to get
>>    updates;
>>    -
>>
>>    Planning tasks (e.g. review of public comments, selection/appointment
>>    of NCSG representatives), schedule the NCSG policy calls and PC meetings,
>>    sharing agendas with PC members for review;
>>    -
>>
>>    Plan and schedule topic webinars on policy issue;
>>    -
>>
>>    Liaising with NCSG chair regarding NCSG letters to board and
>>    communication with other SG/C;
>>    -
>>
>>    Work with PC vice-chairs.
>>
>>
>> IMPORTANT INFO
>>
>>
>>    -
>>
>>    This is a call open to all NCSG councillors and representatives from
>>    NCUC and NPOC to the Policy Committee;
>>    -
>>
>>    Nominations and self-nominations are both permitted and should be
>>    sent to the Policy Committee List;
>>    -
>>
>>    After the nominations, a candidate's confirmation of acceptance and
>>    expression of interest should be sent to the Policy Committee mailing list
>>    by 14th January;
>>
>>
>>
>> TIMELINE
>>
>>
>>
>> 1- Nomination period: from 7th January to 14th January
>>
>>    -
>>
>>    The nominee should accept the nomination and send a short SOI by the
>>    14th of January.
>>
>>
>>
>> 2- Election: from 15th to 21st January
>>
>> Voting is mandatory to all Policy Committee members. The GNSO support
>> staff will act as the election officer. The options in the ballot should be
>> the candidates who confirmed by the deadline and NOTA.
>>
>>
>>
>> 3- Results: should be available by 22nd January
>>
>> The candidate with 2/3 of the NCSG?PC membership votes will be declared
>> winner.
>>
>>
>>
>>
>>
>> VICE-CHAIRS APPOINTMENTS
>>
>>
>>
>> Once the Policy Committee Chair is confirmed, a second call for interest
>> will be issued on this list and the PC members can elect up to 2
>> Vice-chairs. The appointment of the volunteers will be confirmed if there
>> is no objection within PC.
>>
>>
>> Warmly
>>
>> Tomslin
>>
>>
>> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250127/16cdc7b2/attachment.htm>

From mesumbeslin at gmail.com  Tue Jan 28 12:08:00 2025
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Tue, 28 Jan 2025 21:08:00 +1100
Subject: [NCSG-PC] NCSG PC Chair Election
In-Reply-To: <CAN1qJvDZm-nmcU5e9c++ru2uHYS_0HWdwYCBrdwM93r-3K3A+w@mail.gmail.com>
References: <CAM8DdeWtf0HXJDiMBrCnKLBa4=RrRPGcmsWM5QvcYAC-L=pdOw@mail.gmail.com>
 <CAM8DdeUf_g47bzQz=uh=SkoZ6v7uf8B4vyRfzTnj1ycajiQAsQ@mail.gmail.com>
 <CAN1qJvDZm-nmcU5e9c++ru2uHYS_0HWdwYCBrdwM93r-3K3A+w@mail.gmail.com>
Message-ID: <CAM8DdeVnaO0oifc44X9CrQD8tQckzFwq7jnhbfB=thK5PJjA-Q@mail.gmail.com>

Hi Farzi,

Thanks for responding. I agree and also believe it is good practice to hold
it as required by the procedures. Noted on how we should proceed for this
year. I'll give my best to it :-)

Warmly,
Tomslin

On Tue, 28 Jan 2025, 06:52 farzaneh badii, <farzaneh.badii at gmail.com> wrote:

> Hi Tomslin
>
> I am sorry I overlooked this email. I think it's best practice if we
> actually do the election every year even if there is no contestant. But for
> this year we can leave things as they are. :) Thanks for your hard work.
>
>
>
>
>
>
> Farzaneh
>
>
> On Sat, Jan 25, 2025 at 5:47?AM Tomslin Samme-Nlar <mesumbeslin at gmail.com>
> wrote:
>
>> Hi all,
>>
>> There were no nominations received. I suppose the PC is choosing to leave
>> things as they are?
>>
>> Warmly,
>> Tomslin
>>
>> On Wed, 8 Jan 2025, 00:22 Tomslin Samme-Nlar, <mesumbeslin at gmail.com>
>> wrote:
>>
>>> Hi PC members,
>>>
>>> I am writing to call for the election of the Policy Committee Chair.
>>> Normally this is started towards the end of October but it was delayed to
>>> ensure we have all the constituency representatives elected and added to
>>> the list first.
>>>
>>> ..........
>>>
>>> POSITION
>>>
>>> Policy Committee Chair over the course of a 1 year term.  The chair tasks
>>> can be summarized into:
>>>
>>>
>>>    -
>>>
>>>    Managing PC work:
>>>    -
>>>       -
>>>
>>>       Acting as project manager and tracking tasks and activities;
>>>       -
>>>
>>>       Following closely policy discussions, initiatives and public
>>>       comments. Liaising with drafting team for public comments;
>>>       -
>>>
>>>       Following closely the deadlines, ensuring NCSG has enough
>>>       volunteers to draft comments and delivering in a timely manner;
>>>       -
>>>
>>>       Identify NCSG members participating in PDP WG and liaise with
>>>       them for reporting and updates; e
>>>       -
>>>
>>>       Organize the appointment of NCSG representatives by PC to GNSO
>>>       council committees, PDP WG when there is a call for members etc.
>>>
>>>
>>>    -
>>>
>>>    Liaising with GNSO Council work and its committees (SSC, SCBO, small
>>>    teams);
>>>    -
>>>
>>>    Track progress for working groups and approaching members to get
>>>    updates;
>>>    -
>>>
>>>    Planning tasks (e.g. review of public comments,
>>>    selection/appointment of NCSG representatives), schedule the NCSG policy
>>>    calls and PC meetings, sharing agendas with PC members for review;
>>>    -
>>>
>>>    Plan and schedule topic webinars on policy issue;
>>>    -
>>>
>>>    Liaising with NCSG chair regarding NCSG letters to board and
>>>    communication with other SG/C;
>>>    -
>>>
>>>    Work with PC vice-chairs.
>>>
>>>
>>> IMPORTANT INFO
>>>
>>>
>>>    -
>>>
>>>    This is a call open to all NCSG councillors and representatives from
>>>    NCUC and NPOC to the Policy Committee;
>>>    -
>>>
>>>    Nominations and self-nominations are both permitted and should be
>>>    sent to the Policy Committee List;
>>>    -
>>>
>>>    After the nominations, a candidate's confirmation of acceptance and
>>>    expression of interest should be sent to the Policy Committee mailing list
>>>    by 14th January;
>>>
>>>
>>>
>>> TIMELINE
>>>
>>>
>>>
>>> 1- Nomination period: from 7th January to 14th January
>>>
>>>    -
>>>
>>>    The nominee should accept the nomination and send a short SOI by the
>>>    14th of January.
>>>
>>>
>>>
>>> 2- Election: from 15th to 21st January
>>>
>>> Voting is mandatory to all Policy Committee members. The GNSO support
>>> staff will act as the election officer. The options in the ballot should be
>>> the candidates who confirmed by the deadline and NOTA.
>>>
>>>
>>>
>>> 3- Results: should be available by 22nd January
>>>
>>> The candidate with 2/3 of the NCSG?PC membership votes will be declared
>>> winner.
>>>
>>>
>>>
>>>
>>>
>>> VICE-CHAIRS APPOINTMENTS
>>>
>>>
>>>
>>> Once the Policy Committee Chair is confirmed, a second call for
>>> interest will be issued on this list and the PC members can elect up to
>>> 2 Vice-chairs. The appointment of the volunteers will be confirmed if there
>>> is no objection within PC.
>>>
>>>
>>> Warmly
>>>
>>> Tomslin
>>>
>>>
>>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250128/80514030/attachment.htm>

From mesumbeslin at gmail.com  Tue Jan 28 22:30:26 2025
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Wed, 29 Jan 2025 07:30:26 +1100
Subject: [NCSG-PC] GNSO Council Accuracy Assignment - Questions to be
 answered by NCSG
In-Reply-To: <CAN1qJvA9SVVi4ReWBTVN5GGjkENUakahEYmdjYFyRb7puosLjw@mail.gmail.com>
References: <091F7CC1-8220-47D9-80BB-2F04099219D6@icann.org>
 <CAM8DdeWr=+q0sDn2aJLxzqv46Z20=rzK4=qsvke=Fc5Ri9nYjQ@mail.gmail.com>
 <CAN1qJvA9SVVi4ReWBTVN5GGjkENUakahEYmdjYFyRb7puosLjw@mail.gmail.com>
Message-ID: <CAM8DdeUg+yDXduDCORw1pkCZn1sB7yvYMSndOabqXRV9_xiwuw@mail.gmail.com>

Hi Farzi,

Thanks for the contribution. It is timely!

@everyone, are there any other suggested contributions to these questions?

I am also re-attaching the ICANN Org response here since it appears the
previous link is now broken.

Warmly,
Tomslin



On Tue, 28 Jan 2025 at 15:17, farzaneh badii <farzaneh.badii at gmail.com>
wrote:

> Thanks Tomslin. Please see my responses below:
>
> Farzaneh
>
>
> On Tue, Jan 7, 2025 at 8:58?PM Tomslin Samme-Nlar <mesumbeslin at gmail.com>
> wrote:
>
>> Hi all,
>>
>> If you recall, Registration data accuracy has been a topic of contention
>> in the community now for a while. Those who follow the the topic know that
>> the Accuracy Scoping team was paused by the council due to challenges of
>> pursuing further work on accuracy, including that
>>
>>    1. It is unclear whether [the scenarios] would provide useful data to
>>    inform the Accuracy Scoping Team?s efforts;
>>    2. The scenarios are not expected to provide data as it relates to
>>    identity verification of the registrant or veracity of the contact
>>    information (i.e., the data belongs to the data subject);
>>    3. The costs associated with a full-scale registrar audit [Scoping
>>    Team Recommendation #2] may be prohibitive when taking into account the
>>    relatively low level of insight the audit may yield;
>>    4. ICANN does not have the authority to mandate collection of
>>    nonpublic registration data necessary to conduct reviews outside of
>>    auditing current contractual requirements; and
>>    5. ICANN may not be able to demonstrate the purpose of some of the
>>    data processing outweighs the rights of the impacted data subject.
>>
>> As a result, deliberations on this topic on the council was deferred till
>> February and an assignment to ask ICANN Org some clarifying legal
>> questions, and thereafter ask each SG/C to respond to a set of threshold
>> questions that will help guide the way forward on this topic was agreed by
>> the council. ICANN Org came back with their response
>> <https://urldefense.com/v3/__https:/us-east-1.secure-attach.amazon.com/da78dbeb-dd4d-4f3f-96c2-1d5abfe7810b/d3fd2bca-021f-494b-957c-0c800d63f333__;!!PtGJab4!5ebsdR0WRUrjpIzUO8HekPbjqckThf0GWEiIM_7eVuzWwd4NAuc_-nt2-GqtwpE87UIulB_KPGxmS00M_1a2SSvlTw$>
>> just before the December holidays.
>>
>> Now therefore, each SG/C is required to respond to the threshold
>> questions
>> <https://gnso.icann.org/sites/default/files/policy/2024/draft/draft-concept-proposal-accuracy-12sep24.pdf>
>> by Friday 31 January 2025. We forgot to include it for discussion in our
>> Policy meeting earlier this week. However, I request that members provide
>> their input via this email thread. Once agreed, we'll forward our response
>> to the Council. The questions we have to answer are in the link above but
>> for convenience, I'll list them here below:
>>
>>    1. *What are concrete and articulable examples of what inaccurate
>>    data DOES prevent or inhibit, and how does it do so?*
>>
>> Inaccurate domain name registrant data should be defined based on the
> purpose of accuracy within the scope of ICANN's mandate: ensuring that the
> registrant is 'contactable.' If the registrant cannot be reached due to
> undeliverable messages caused by errors in the provided contact details,
> the data should be deemed inaccurate.
>
>>
>>    1. *What are concrete and articulable examples of what inaccurate
>>    data does NOT prevent?*
>>
>>
>>    1. *Are there specific stakeholders, industries, or sectors
>>    particularly vulnerable to the effects of inaccurate registration data? If
>>    so, what are they and why?*
>>
>> Domain name registrants can be affected by insisting on having even more
> "accuracy" requirements. In order to ensure accuracy suggestions could be
> made to "identify" domain name registrants which goes against the principle
> of respecting anonymity should the domain name registrant want to remain
> anonymous and identification of registrants can have an adverse impact on
> data protection and access to domain names globally.
>
>
>
>>    1. *Given the examples provided in response to the three questions
>>    above (if any), please articulate a short problem statement for accuracy.
>>    The problem statement should consider:*
>>       - *What is the current problem or challenge?*
>>       - *What are the consequences of this problem or challenge?*
>>       - *What is the ultimate objective of working on this problem or
>>       challenge?*
>>       - *Considering the limitations of data processing, how do you
>>       propose to address this problem?*
>>
>> We don't believe there are many challenges facing data accuracy. There
> are already requirements in place for domain name registrants to keep their
> data accurate, and there is an ultimate punishment for that: losing their
> domain name if they don't do so. Please refer to registrants obligation
> here:
> https://www.icann.org/resources/pages/registration-data-accurate-2023-11-02-en?utm_source=chatgpt.com
>
>
>>
>>    1. *Is now the appropriate time to address the problem? For example,
>>    some stakeholders have mentioned the implementation of NIS2 as an important
>>    precursor to understanding new accuracy requirements. Should this or other
>>    examples be considered prior to engaging in potential policy work?*
>>
>> it's crucial to remember that NIS2 is a directive, not a regulation. Its
> implementation will vary across European jurisdictions, and it shouldn't
> set the accuracy standard for ICANN. This is due to two key reasons:
>
> 1. NIS2's provisions concerning domain names were influenced by specific
> stakeholder groups, not by multistakeholder consensus.
> 2. Some transposing laws (e.g., Germany) aim to identify registrants
> through data accuracy to prevent fraud. However, we believe that accuracy
> at ICANN should not necessitate registrant identification.
>
>>
>>    1. *Are the ICANN org alternatives proposals worth exploring, such
>>    as:*
>>       - *Provision of historical audit data that measures registrars?
>>       compliance with accuracy-related provisions in the RAA.*
>>       - *Engagement with contracted parties and ccTLD operators on
>>       developments in European policymaking regarding registration data accuracy.*
>>    2. *What are the limitations of the ICANN proposals? Why should or
>>    should they not be pursued?*
>>    3. *What other possibilities can be explored to move our work on
>>    Accuracy forward?*
>>
>> I look forward to your contribution to these questions.
>>
>> Warmly,
>> Tomslin
>>
>>
>>
>> ---------- Forwarded message ---------
>> From: Feodora Hamza via council <council at icann.org>
>> Date: Thu, 12 Dec 2024 at 23:11
>> Subject: [council] Re: Follow-up GNSO Council Accuracy Assignment
>> To: DiBiase, Gregory <dibiase at amazon.com>, council at gnso.icann.org <
>> council at gnso.icann.org>
>>
>>
>> Dear Councilors,
>>
>>
>>
>> due to technical issues, please see accuracy assignment attached and
>> linked below.
>>
>> Accuracy Assignment:
>> https://gnso.icann.org/sites/default/files/policy/2024/draft/draft-concept-proposal-accuracy-12sep24.pdf
>>
>>
>>
>> Kind regards,
>>
>> Feodora Hamza
>>
>>
>>
>> *From: *"DiBiase, Gregory via council" <council at icann.org>
>> *Reply to: *"DiBiase, Gregory" <dibiase at amazon.com>
>> *Date: *Thursday, 12 December 2024 at 20:57
>> *To: *"council at gnso.icann.org" <council at gnso.icann.org>
>> *Subject: *[council] Follow-up GNSO Council Accuracy Assignment
>>
>>
>>
>>    - *Attachments protected by Amazon: *
>>    - Answer to the GNSO questions on accuracy.pdf
>>    [us-east-1.secure-attach.amazon.com]
>>    <https://urldefense.com/v3/__https:/us-east-1.secure-attach.amazon.com/da78dbeb-dd4d-4f3f-96c2-1d5abfe7810b/d3fd2bca-021f-494b-957c-0c800d63f333__;!!PtGJab4!5ebsdR0WRUrjpIzUO8HekPbjqckThf0GWEiIM_7eVuzWwd4NAuc_-nt2-GqtwpE87UIulB_KPGxmS00M_1a2SSvlTw$> |
>>
>>    - ATT00001.txt [us-east-1.secure-attach.amazon.com]
>>    <https://urldefense.com/v3/__https:/us-east-1.secure-attach.amazon.com/da78dbeb-dd4d-4f3f-96c2-1d5abfe7810b/94d6cb3e-3ab2-446c-a385-9c201a9cffc9__;!!PtGJab4!5ebsdR0WRUrjpIzUO8HekPbjqckThf0GWEiIM_7eVuzWwd4NAuc_-nt2-GqtwpE87UIulB_KPGxmS00M_1ZAKmAJaA$> |
>>
>>
>> Amazon has replaced the attachments in this email with download links.
>> Downloads will be available until January 11, 2025, 19:56 (UTC+00:00). Tell
>> us what you think [amazonexteu.qualtrics.com]
>> <https://urldefense.com/v3/__https:/amazonexteu.qualtrics.com/jfe/form/SV_ehuz6zGo8YnsRKK__;!!PtGJab4!5ebsdR0WRUrjpIzUO8HekPbjqckThf0GWEiIM_7eVuzWwd4NAuc_-nt2-GqtwpE87UIulB_KPGxmS00M_1Zzdd6ztA$>
>>
>> For more information click here [docs.secure-attach.amazon.com]
>> <https://urldefense.com/v3/__https:/docs.secure-attach.amazon.com/guide__;!!PtGJab4!5ebsdR0WRUrjpIzUO8HekPbjqckThf0GWEiIM_7eVuzWwd4NAuc_-nt2-GqtwpE87UIulB_KPGxmS00M_1ZzNkqBbQ$>
>>
>> Dear Councilors,
>>
>>
>>
>> I am following up on the attached email from ICANN Org in which they
>> provided their input on the accuracy assignment.  On 25 October, we shared
>> the proposed accuracy assignment, which included questions for ICANN org
>> and the community.
>>
>>
>>
>> Now that ICANN org has provided responses to the Council?s questions, we
>> are now sending the remaining questions in the attached proposal to
>> interested SG/C/ACs for their input. Given the proximity to the holidays,
>> we propose giving groups until Friday, 31 January 2025 to provide their
>> input to the Council.
>>
>>
>>
>> As noted during the Council?s previous discussions on the topic of
>> accuracy, the Council recognizes the importance of accuracy and is
>> committed to making progress on this issue. Your group?s responses to these
>> questions are very important for the Council?s future discussion, and we
>> strongly encourage your groups to think about these questions and provide
>> candid responses.
>>
>>
>>
>> Thank you in advance for your input.
>>
>>
>>
>> Thanks,
>>
>> Greg
>> _______________________________________________
>> 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/20250129/611df1b8/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Answer to the GNSO questions on accuracy-2.pdf
Type: application/pdf
Size: 145338 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250129/611df1b8/attachment.pdf>

From andrea.glandon at icann.org  Wed Jan 29 16:41:14 2025
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Wed, 29 Jan 2025 14:41:14 +0000
Subject: [NCSG-PC] ICANN82 NCSG PC Membership Agendas
Message-ID: <AE4FFF71-825F-4366-B172-612A219DE4EA@icann.org>

Hello all,

I wanted to start the conversation about the NCSG PC agendas for ICANN82. I have created a Google doc below. Reminder that there are 2 NCSG PC sessions at ICANN82. The first session is on Saturday, 1500-1600 local time. The second session is on Tuesday, 1030-1200 local time. Both agendas can be added to this Google doc.

https://docs.google.com/document/d/1-0AkNo5pDklLaPB-C5BHPrQSEOKQc57rLdrfPO8GObg/edit?usp=sharing

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/20250129/067d9681/attachment.htm>

From mesumbeslin at gmail.com  Fri Jan 31 11:39:46 2025
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Fri, 31 Jan 2025 20:39:46 +1100
Subject: [NCSG-PC] GNSO Council Accuracy Assignment - Questions to be
 answered by NCSG
In-Reply-To: <CAM8DdeUg+yDXduDCORw1pkCZn1sB7yvYMSndOabqXRV9_xiwuw@mail.gmail.com>
References: <091F7CC1-8220-47D9-80BB-2F04099219D6@icann.org>
 <CAM8DdeWr=+q0sDn2aJLxzqv46Z20=rzK4=qsvke=Fc5Ri9nYjQ@mail.gmail.com>
 <CAN1qJvA9SVVi4ReWBTVN5GGjkENUakahEYmdjYFyRb7puosLjw@mail.gmail.com>
 <CAM8DdeUg+yDXduDCORw1pkCZn1sB7yvYMSndOabqXRV9_xiwuw@mail.gmail.com>
Message-ID: <CAM8DdeVWsjERqn0U_zSvsa=QEmbYzUqpnkOFQjLuK7r+ZhT2ug@mail.gmail.com>

Hi all,

Since there are no further inputs or comments, I will proceed to submit
what I have here to the council as NCSG response, since today is the
deadline for submission.

Thanks again Farzi for your contribution to this.

Warmly,
Tomslin

On Wed, 29 Jan 2025, 07:30 Tomslin Samme-Nlar, <mesumbeslin at gmail.com>
wrote:

> Hi Farzi,
>
> Thanks for the contribution. It is timely!
>
> @everyone, are there any other suggested contributions to these questions?
>
> I am also re-attaching the ICANN Org response here since it appears the
> previous link is now broken.
>
> Warmly,
> Tomslin
>
>
>
> On Tue, 28 Jan 2025 at 15:17, farzaneh badii <farzaneh.badii at gmail.com>
> wrote:
>
>> Thanks Tomslin. Please see my responses below:
>>
>> Farzaneh
>>
>>
>> On Tue, Jan 7, 2025 at 8:58?PM Tomslin Samme-Nlar <mesumbeslin at gmail.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> If you recall, Registration data accuracy has been a topic of contention
>>> in the community now for a while. Those who follow the the topic know that
>>> the Accuracy Scoping team was paused by the council due to challenges of
>>> pursuing further work on accuracy, including that
>>>
>>>    1. It is unclear whether [the scenarios] would provide useful data
>>>    to inform the Accuracy Scoping Team?s efforts;
>>>    2. The scenarios are not expected to provide data as it relates to
>>>    identity verification of the registrant or veracity of the contact
>>>    information (i.e., the data belongs to the data subject);
>>>    3. The costs associated with a full-scale registrar audit [Scoping
>>>    Team Recommendation #2] may be prohibitive when taking into account the
>>>    relatively low level of insight the audit may yield;
>>>    4. ICANN does not have the authority to mandate collection of
>>>    nonpublic registration data necessary to conduct reviews outside of
>>>    auditing current contractual requirements; and
>>>    5. ICANN may not be able to demonstrate the purpose of some of the
>>>    data processing outweighs the rights of the impacted data subject.
>>>
>>> As a result, deliberations on this topic on the council was deferred
>>> till February and an assignment to ask ICANN Org some clarifying legal
>>> questions, and thereafter ask each SG/C to respond to a set of threshold
>>> questions that will help guide the way forward on this topic was agreed by
>>> the council. ICANN Org came back with their response
>>> <https://urldefense.com/v3/__https:/us-east-1.secure-attach.amazon.com/da78dbeb-dd4d-4f3f-96c2-1d5abfe7810b/d3fd2bca-021f-494b-957c-0c800d63f333__;!!PtGJab4!5ebsdR0WRUrjpIzUO8HekPbjqckThf0GWEiIM_7eVuzWwd4NAuc_-nt2-GqtwpE87UIulB_KPGxmS00M_1a2SSvlTw$>
>>> just before the December holidays.
>>>
>>> Now therefore, each SG/C is required to respond to the threshold
>>> questions
>>> <https://gnso.icann.org/sites/default/files/policy/2024/draft/draft-concept-proposal-accuracy-12sep24.pdf>
>>> by Friday 31 January 2025. We forgot to include it for discussion in our
>>> Policy meeting earlier this week. However, I request that members provide
>>> their input via this email thread. Once agreed, we'll forward our response
>>> to the Council. The questions we have to answer are in the link above but
>>> for convenience, I'll list them here below:
>>>
>>>    1. *What are concrete and articulable examples of what inaccurate
>>>    data DOES prevent or inhibit, and how does it do so?*
>>>
>>> Inaccurate domain name registrant data should be defined based on the
>> purpose of accuracy within the scope of ICANN's mandate: ensuring that the
>> registrant is 'contactable.' If the registrant cannot be reached due to
>> undeliverable messages caused by errors in the provided contact details,
>> the data should be deemed inaccurate.
>>
>>>
>>>    1. *What are concrete and articulable examples of what inaccurate
>>>    data does NOT prevent?*
>>>
>>>
>>>    1. *Are there specific stakeholders, industries, or sectors
>>>    particularly vulnerable to the effects of inaccurate registration data? If
>>>    so, what are they and why?*
>>>
>>> Domain name registrants can be affected by insisting on having even more
>> "accuracy" requirements. In order to ensure accuracy suggestions could be
>> made to "identify" domain name registrants which goes against the principle
>> of respecting anonymity should the domain name registrant want to remain
>> anonymous and identification of registrants can have an adverse impact on
>> data protection and access to domain names globally.
>>
>>
>>
>>>    1. *Given the examples provided in response to the three questions
>>>    above (if any), please articulate a short problem statement for accuracy.
>>>    The problem statement should consider:*
>>>       - *What is the current problem or challenge?*
>>>       - *What are the consequences of this problem or challenge?*
>>>       - *What is the ultimate objective of working on this problem or
>>>       challenge?*
>>>       - *Considering the limitations of data processing, how do you
>>>       propose to address this problem?*
>>>
>>> We don't believe there are many challenges facing data accuracy. There
>> are already requirements in place for domain name registrants to keep their
>> data accurate, and there is an ultimate punishment for that: losing their
>> domain name if they don't do so. Please refer to registrants obligation
>> here:
>> https://www.icann.org/resources/pages/registration-data-accurate-2023-11-02-en?utm_source=chatgpt.com
>>
>>
>>>
>>>    1. *Is now the appropriate time to address the problem? For example,
>>>    some stakeholders have mentioned the implementation of NIS2 as an important
>>>    precursor to understanding new accuracy requirements. Should this or other
>>>    examples be considered prior to engaging in potential policy work?*
>>>
>>> it's crucial to remember that NIS2 is a directive, not a regulation. Its
>> implementation will vary across European jurisdictions, and it shouldn't
>> set the accuracy standard for ICANN. This is due to two key reasons:
>>
>> 1. NIS2's provisions concerning domain names were influenced by specific
>> stakeholder groups, not by multistakeholder consensus.
>> 2. Some transposing laws (e.g., Germany) aim to identify registrants
>> through data accuracy to prevent fraud. However, we believe that accuracy
>> at ICANN should not necessitate registrant identification.
>>
>>>
>>>    1. *Are the ICANN org alternatives proposals worth exploring, such
>>>    as:*
>>>       - *Provision of historical audit data that measures registrars?
>>>       compliance with accuracy-related provisions in the RAA.*
>>>       - *Engagement with contracted parties and ccTLD operators on
>>>       developments in European policymaking regarding registration data accuracy.*
>>>    2. *What are the limitations of the ICANN proposals? Why should or
>>>    should they not be pursued?*
>>>    3. *What other possibilities can be explored to move our work on
>>>    Accuracy forward?*
>>>
>>> I look forward to your contribution to these questions.
>>>
>>> Warmly,
>>> Tomslin
>>>
>>>
>>>
>>> ---------- Forwarded message ---------
>>> From: Feodora Hamza via council <council at icann.org>
>>> Date: Thu, 12 Dec 2024 at 23:11
>>> Subject: [council] Re: Follow-up GNSO Council Accuracy Assignment
>>> To: DiBiase, Gregory <dibiase at amazon.com>, council at gnso.icann.org <
>>> council at gnso.icann.org>
>>>
>>>
>>> Dear Councilors,
>>>
>>>
>>>
>>> due to technical issues, please see accuracy assignment attached and
>>> linked below.
>>>
>>> Accuracy Assignment:
>>> https://gnso.icann.org/sites/default/files/policy/2024/draft/draft-concept-proposal-accuracy-12sep24.pdf
>>>
>>>
>>>
>>> Kind regards,
>>>
>>> Feodora Hamza
>>>
>>>
>>>
>>> *From: *"DiBiase, Gregory via council" <council at icann.org>
>>> *Reply to: *"DiBiase, Gregory" <dibiase at amazon.com>
>>> *Date: *Thursday, 12 December 2024 at 20:57
>>> *To: *"council at gnso.icann.org" <council at gnso.icann.org>
>>> *Subject: *[council] Follow-up GNSO Council Accuracy Assignment
>>>
>>>
>>>
>>>    - *Attachments protected by Amazon: *
>>>    - Answer to the GNSO questions on accuracy.pdf
>>>    [us-east-1.secure-attach.amazon.com]
>>>    <https://urldefense.com/v3/__https:/us-east-1.secure-attach.amazon.com/da78dbeb-dd4d-4f3f-96c2-1d5abfe7810b/d3fd2bca-021f-494b-957c-0c800d63f333__;!!PtGJab4!5ebsdR0WRUrjpIzUO8HekPbjqckThf0GWEiIM_7eVuzWwd4NAuc_-nt2-GqtwpE87UIulB_KPGxmS00M_1a2SSvlTw$> |
>>>
>>>    - ATT00001.txt [us-east-1.secure-attach.amazon.com]
>>>    <https://urldefense.com/v3/__https:/us-east-1.secure-attach.amazon.com/da78dbeb-dd4d-4f3f-96c2-1d5abfe7810b/94d6cb3e-3ab2-446c-a385-9c201a9cffc9__;!!PtGJab4!5ebsdR0WRUrjpIzUO8HekPbjqckThf0GWEiIM_7eVuzWwd4NAuc_-nt2-GqtwpE87UIulB_KPGxmS00M_1ZAKmAJaA$> |
>>>
>>>
>>> Amazon has replaced the attachments in this email with download links.
>>> Downloads will be available until January 11, 2025, 19:56 (UTC+00:00). Tell
>>> us what you think [amazonexteu.qualtrics.com]
>>> <https://urldefense.com/v3/__https:/amazonexteu.qualtrics.com/jfe/form/SV_ehuz6zGo8YnsRKK__;!!PtGJab4!5ebsdR0WRUrjpIzUO8HekPbjqckThf0GWEiIM_7eVuzWwd4NAuc_-nt2-GqtwpE87UIulB_KPGxmS00M_1Zzdd6ztA$>
>>>
>>> For more information click here [docs.secure-attach.amazon.com]
>>> <https://urldefense.com/v3/__https:/docs.secure-attach.amazon.com/guide__;!!PtGJab4!5ebsdR0WRUrjpIzUO8HekPbjqckThf0GWEiIM_7eVuzWwd4NAuc_-nt2-GqtwpE87UIulB_KPGxmS00M_1ZzNkqBbQ$>
>>>
>>> Dear Councilors,
>>>
>>>
>>>
>>> I am following up on the attached email from ICANN Org in which they
>>> provided their input on the accuracy assignment.  On 25 October, we shared
>>> the proposed accuracy assignment, which included questions for ICANN org
>>> and the community.
>>>
>>>
>>>
>>> Now that ICANN org has provided responses to the Council?s questions, we
>>> are now sending the remaining questions in the attached proposal to
>>> interested SG/C/ACs for their input. Given the proximity to the holidays,
>>> we propose giving groups until Friday, 31 January 2025 to provide their
>>> input to the Council.
>>>
>>>
>>>
>>> As noted during the Council?s previous discussions on the topic of
>>> accuracy, the Council recognizes the importance of accuracy and is
>>> committed to making progress on this issue. Your group?s responses to these
>>> questions are very important for the Council?s future discussion, and we
>>> strongly encourage your groups to think about these questions and provide
>>> candid responses.
>>>
>>>
>>>
>>> Thank you in advance for your input.
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Greg
>>> _______________________________________________
>>> 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/20250131/b87119b2/attachment.htm>