From julf at Julf.com  Thu Oct  5 10:46:28 2023
From: julf at Julf.com (Johan Helsingius)
Date: Thu, 5 Oct 2023 09:46:28 +0200
Subject: [NCSG-PC] REMINDER: ICANN78 Stakeholders/Board sessions - Question
 from Board to NCSG
In-Reply-To: <6a89faa3-ebab-5c31-c3b4-bd1482c20adf@Julf.com>
References: <B9A63EA8-C18F-4621-87F0-D168BEDD7C0B@icann.org>
 <6a89faa3-ebab-5c31-c3b4-bd1482c20adf@Julf.com>
Message-ID: <85de87d5-fb6f-07f3-9b36-9f5bb8f8b9d8@Julf.com>

The deadline for this is rapidly approaching. I made a first attempt
at answering the question from the board, but don't we have any
questions to the Board?

The Google doc is at
https://docs.google.com/document/d/1MSb0xEX_hwBTzZtyhHrtcOBqW_SmCDP5DuT1X2UkjEM/edit?usp=sharing

	Julf

On 21/09/2023 09:12, Johan Helsingius via NCSG-EC wrote:
> "Looking forward over the next 3 - 5 years, what are the key
>    strategic issues ICANN and the ICANN ecosystem should be
>    addressing in the FY26-30 Strategic plan, and why?"
> 
> -------- Forwarded Message --------
> Subject: 	PLEASE READ - ICANN78 Stakeholders/Board sessions
> Date: 	Thu, 21 Sep 2023 06:34:47 +0000
> From: 	Vinciane Koenigsfeld <vinciane.koenigsfeld at icann.org>
> To: 	julf at julf.com <julf at julf.com>, benakin at gmail.com
> <benakin at gmail.com>, plommer at gmail.com <plommer at gmail.com>
> CC: 	Carlos Reyes <carlos.reyes at icann.org>, Michelle Bright
> <michelle.bright at icann.org>, Andrea Glandon <andrea.glandon at icann.org>,
> David Olive <david.olive at icann.org>, Matthew Shears
> <matthew.shears at board.icann.org>
> 
> 
> 
>           /Sent on behalf of Tripti Sinha, Chair, ICANN Board of Directors///
> 
>           //
> 
>           Dear Non-Commercial/Stakeholder Group///Leaders,
> 
>           **Please reply no later than Wednesday 1**1 October **2023**
> 
>           ICANN78 is right at our doorstep, and the Board and I couldn?t
>           be happier about the opportunity to meet with all of you in
>           Hamburg from October 21st to 26th.
> 
>           This upcoming meeting is not only a chance for us to come
>           together and discuss our common interests, but it?s also a
>           momentous occasion as we celebrate ICANN?s remarkable 25th
>           Anniversary.
> 
>           We?re diligently preparing for the upcoming Annual General
>           Meeting, and weare equally excited about the celebration that
>           awaits. Rest assured,**we will share more details with you soon.
> 
>           In the meantime, I want to remind you of the positive changes we
>           initiated during our time in Canc?n, which were favorably received:
> 
>           1.Tailored questions designed to cater to the unique needs of
>           each stakeholder group.
> 
>           2.A blog that highlighted key takeaways from the ICANN Meeting.
> 
>           3.Summaries of bilateral sessions included in the Policy
>           Outcomes Report published after the ICANN meeting.
> 
>           In the next few months, we will be suggesting additional
>           improvements that we hope will enhance our partnership?s
>           performance and transparency, all with your satisfaction in mind.
> 
>           Meanwhile though, it is important that we continue listening to
>           your specific needs and therefore here isthe question we would
>           like to ask_your_Group ahead of our joint session in Hamburg:
> 
>             * *Looking forward over the next 3 - 5 years, what are the key
>               strategic?issues ICANN and the ICANN ecosystem should be
>               addressing in the FY26-30?Strategic plan, and why**? ***
> 
>           We look forward to hearing your thoughts on this soon.
> 
>           We would be grateful if you could send to Board Operations
>           (board-ops-team at icann.org <mailto:board-ops-team at icann.org>)
>            ?the questions you would like the Board to address during our
>           face-to-face meetings.?Given the finite time available for these
>           meetings, please list your questions in order of priority.We
>           would also appreciate getting your questions no later than
>           *_Wednesday 11 October, 2023_*.
> 
>           Looking forward to engaging discussions and shared celebrations
>           in Hamburg!
> 
>           Best regards,
> 
>           Tripti Sinha
> 
>           Chair, ICANN Board of Directors
> 
> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec


From mesumbeslin at gmail.com  Thu Oct  5 13:28:59 2023
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Thu, 5 Oct 2023 21:28:59 +1100
Subject: [NCSG-PC] [Call for volunteers] Public Comment: Pilot Holistic
 Review Revised Draft Terms of Reference
Message-ID: <CAM8DdeWXn-=jU5iBYRapPEM-xGHzJrYJkFAWm8avS9KUzNQFmw@mail.gmail.com>

Dear all,

The ICANN Board is seeking the community input on the proposed Pilot
Holistic Review Revised Draft Terms of Reference. This is a review of
interest to NCSG, so it would be great to have members volunteer to draft a
comment for our SG.

The public comment is due on 27 November 2023, so if you'd like to
volunteer,  please reach out.

More information on the comment can be found from the below link:
https://www.icann.org/en/public-comment/proceeding/pilot-holistic-review-revised-terms-of-reference-tor-28-09-2023

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

From julf at Julf.com  Thu Oct  5 19:50:05 2023
From: julf at Julf.com (Johan Helsingius)
Date: Thu, 5 Oct 2023 18:50:05 +0200
Subject: [NCSG-PC] Approval Action Community Forum at ICANN78.
In-Reply-To: <7F56E795-0E72-473A-A12B-839A09677049@icann.org>
References: <7F56E795-0E72-473A-A12B-839A09677049@icann.org>
Message-ID: <04bca184-75f5-1ed3-6b65-8b3a2ee02852@Julf.com>




-------- Forwarded Message --------
Subject: FYI | FW: [Ext] RE: [council] Notice |  Approval Action 
Community Forum at ICANN78.
Date: Thu, 5 Oct 2023 16:46:26 +0000
From: Terri Agnew <terri.agnew at icann.org>
To: Johan Helsingius <julf at julf.com>, Raoul Plommer <plommer at gmail.com>, 
Benjamin Akinmoyeje <benakin at gmail.com>, chair at rysg.info 
<chair at rysg.info>, aheineman at godaddy.com <aheineman at godaddy.com>, 
mcole at perkinscoie.com <mcole at perkinscoie.com>, lschulman at inta.org 
<lschulman at inta.org>, Brian King <brian.king at clarivate.com>, 
philippe.fouquart at orange.com <philippe.fouquart at orange.com>
CC: gnso-secs at icann.org <gnso-secs at icann.org>, Brenda Brewer 
<brenda.brewer at icann.org>, Andrea Glandon <andrea.glandon at icann.org>, 
Sue Schuler <rysgsecretariat at gmail.com>, Zoe Bonython 
<secretariat at icannregistrars.org>, Wendy Profit via Gnso-chairs 
<gnso-chairs at icann.org>

FYI, see below.
From: "DiBiase, Gregory" <dibiase at amazon.com>
Date: Thursday, October 5, 2023 at 10:47 AM
To: Terri Agnew <terri.agnew at icann.org>, "liaison6c at gnso.icann.org" 
<liaison6c at gnso.icann.org>, "COUNCIL at GNSO.ICANN.ORG" 
<COUNCIL at gnso.icann.org>
Cc: "gnso-secs at icann.org" <gnso-secs at icann.org>, Ozan Sahin 
<ozan.sahin at icann.org>
Subject: [Ext] RE: [council] Notice | Approval Action Community Forum at 
ICANN78.

Hello Councilors,

I am following up on this notice as EC Admin for the GNSO.? Staff has 
helpfully prepared this input form 
(https://docs.google.com/document/d/1Cb85STPs8nHls8gJPyw6BROwysKMWiHX/edit 
) to allow GNSO stakeholder groups and constituencies to provide any 
feedback they may have in advance of the Community Forum.? The form 
includes relevant information on this process that may help guide 
input.? Please share with your constituencies as you see fit (this 
message will be sent to SG/C Chairs as well).? Deadline to provide input 
is 23:59 UTC on Wednesday 25 October 2023 (but the sooner the better 
?).? I would also note that any input added to this form does not 
preclude GNSO SG/Cs from submitting views and questions on the Approval 
Action in writing during the Approval Action Community Forum.

Thanks,
Greg

From: council <council-bounces at gnso.icann.org> On Behalf Of Terri Agnew 
via council
Sent: Tuesday, October 3, 2023 6:12 PM
To: council at gnso.icann.org; liaison6c at gnso.icann.org
Cc: gnso-secs at icann.org; Ozan Sahin <ozan.sahin at icann.org>
Subject: [EXTERNAL] [council] Notice | Approval Action Community Forum 
at ICANN78.

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,

We have information to share for ICANN78.
The Approval Action Community Forum will take place on Thursday 26 
October from 15:00 ? 15:30 Hamburg time in Hall 4 of the convention 
center (i.e., the ?GAC room?, meaning the room will be set up in the 
usual format that the GAC uses at ICANN Public Meetings). There will be 
full remote participation, interpretation, recording and technical 
support for the session.
Under the Bylaws, the Empowered Community Administration has the 
responsibility to ?manage and moderate the Approval Action Community 
Forum in a fair and neutral manner?.
Please note that the Approval Action Community Forum is not a decisional 
body and ICANN staff and Directors representing the ICANN Board are 
required to attend the forum to address any concerns or questions that 
may be raised during the session. You may also wish to note that Bylaws 
state that ?ICANN?and any?Supporting Organization?or?Advisory 
Committee?(including Decisional Participants) may deliver to 
the?EC?Administration in writing its views and questions on the Approval 
Action prior to the convening of and during the Approval Action 
Community Forum?.

Thank you.

With kind regards,
Terri
 ????????????---
Terri Agnew
Policy Team Supporting the GNSO
Policy Operations Specialist (GNSO)
Internet Corporation for Assigned Names and Numbers (ICANN)
Skype ID:? terri.agnew.icann

Find out more about the GNSO by 
visiting:?https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=o7Auz997kA-HPv9PHJCjFVZw7Pgo8krw4MxfqCwBrIU&e=
Follow @GNSO on 
Twitter:?https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNSO&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=kWw4fQPNjw2lVKy1UjTxS2F0BmjEAzaDFWNmsYywbmE&e=
Transcripts and recordings of GNSO Working Group and Council events are 
located on 
the?https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_group-2Dactivities_calendar&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=-L6chFfv0OperrXHHpTF722WnH3FZIutn4cS16IvpOg&e=



-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 14771 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20231005/420a6f37/attachment.png>

From mesumbeslin at gmail.com  Thu Oct  5 22:34:03 2023
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Fri, 6 Oct 2023 06:34:03 +1100
Subject: [NCSG-PC] [NCSG-EC] Approval Action Community Forum at ICANN78.
In-Reply-To: <04bca184-75f5-1ed3-6b65-8b3a2ee02852@Julf.com>
References: <7F56E795-0E72-473A-A12B-839A09677049@icann.org>
 <04bca184-75f5-1ed3-6b65-8b3a2ee02852@Julf.com>
Message-ID: <CAM8DdeXUjLpcjZt7RtVZL6xhEtcW0c5my_9Apju9yO=_FGjCqg@mail.gmail.com>

No objection from me

Warmly,
Tomslin



On Fri, 6 Oct 2023 at 03:50, Johan Helsingius via NCSG-EC <
ncsg-ec at lists.ncsg.is> wrote:

>
>
>
> -------- Forwarded Message --------
> Subject: FYI | FW: [Ext] RE: [council] Notice |  Approval Action
> Community Forum at ICANN78.
> Date: Thu, 5 Oct 2023 16:46:26 +0000
> From: Terri Agnew <terri.agnew at icann.org>
> To: Johan Helsingius <julf at julf.com>, Raoul Plommer <plommer at gmail.com>,
> Benjamin Akinmoyeje <benakin at gmail.com>, chair at rysg.info
> <chair at rysg.info>, aheineman at godaddy.com <aheineman at godaddy.com>,
> mcole at perkinscoie.com <mcole at perkinscoie.com>, lschulman at inta.org
> <lschulman at inta.org>, Brian King <brian.king at clarivate.com>,
> philippe.fouquart at orange.com <philippe.fouquart at orange.com>
> CC: gnso-secs at icann.org <gnso-secs at icann.org>, Brenda Brewer
> <brenda.brewer at icann.org>, Andrea Glandon <andrea.glandon at icann.org>,
> Sue Schuler <rysgsecretariat at gmail.com>, Zoe Bonython
> <secretariat at icannregistrars.org>, Wendy Profit via Gnso-chairs
> <gnso-chairs at icann.org>
>
> FYI, see below.
> From: "DiBiase, Gregory" <dibiase at amazon.com>
> Date: Thursday, October 5, 2023 at 10:47 AM
> To: Terri Agnew <terri.agnew at icann.org>, "liaison6c at gnso.icann.org"
> <liaison6c at gnso.icann.org>, "COUNCIL at GNSO.ICANN.ORG"
> <COUNCIL at gnso.icann.org>
> Cc: "gnso-secs at icann.org" <gnso-secs at icann.org>, Ozan Sahin
> <ozan.sahin at icann.org>
> Subject: [Ext] RE: [council] Notice | Approval Action Community Forum at
> ICANN78.
>
> Hello Councilors,
>
> I am following up on this notice as EC Admin for the GNSO.  Staff has
> helpfully prepared this input form
> (https://docs.google.com/document/d/1Cb85STPs8nHls8gJPyw6BROwysKMWiHX/edit
> ) to allow GNSO stakeholder groups and constituencies to provide any
> feedback they may have in advance of the Community Forum.  The form
> includes relevant information on this process that may help guide
> input.  Please share with your constituencies as you see fit (this
> message will be sent to SG/C Chairs as well).  Deadline to provide input
> is 23:59 UTC on Wednesday 25 October 2023 (but the sooner the better
> ?).  I would also note that any input added to this form does not
> preclude GNSO SG/Cs from submitting views and questions on the Approval
> Action in writing during the Approval Action Community Forum.
>
> Thanks,
> Greg
>
> From: council <council-bounces at gnso.icann.org> On Behalf Of Terri Agnew
> via council
> Sent: Tuesday, October 3, 2023 6:12 PM
> To: council at gnso.icann.org; liaison6c at gnso.icann.org
> Cc: gnso-secs at icann.org; Ozan Sahin <ozan.sahin at icann.org>
> Subject: [EXTERNAL] [council] Notice | Approval Action Community Forum
> at ICANN78.
>
> 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,
>
> We have information to share for ICANN78.
> The Approval Action Community Forum will take place on Thursday 26
> October from 15:00 ? 15:30 Hamburg time in Hall 4 of the convention
> center (i.e., the ?GAC room?, meaning the room will be set up in the
> usual format that the GAC uses at ICANN Public Meetings). There will be
> full remote participation, interpretation, recording and technical
> support for the session.
> Under the Bylaws, the Empowered Community Administration has the
> responsibility to ?manage and moderate the Approval Action Community
> Forum in a fair and neutral manner?.
> Please note that the Approval Action Community Forum is not a decisional
> body and ICANN staff and Directors representing the ICANN Board are
> required to attend the forum to address any concerns or questions that
> may be raised during the session. You may also wish to note that Bylaws
> state that ?ICANN and any Supporting Organization or Advisory
> Committee (including Decisional Participants) may deliver to
> the EC Administration in writing its views and questions on the Approval
> Action prior to the convening of and during the Approval Action
> Community Forum?.
>
> Thank you.
>
> With kind regards,
> Terri
>              ---
> Terri Agnew
> Policy Team Supporting the GNSO
> Policy Operations Specialist (GNSO)
> Internet Corporation for Assigned Names and Numbers (ICANN)
> Skype ID:  terri.agnew.icann
>
> Find out more about the GNSO by
> visiting:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=o7Auz997kA-HPv9PHJCjFVZw7Pgo8krw4MxfqCwBrIU&e=
> Follow @GNSO on
> Twitter:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNSO&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=kWw4fQPNjw2lVKy1UjTxS2F0BmjEAzaDFWNmsYywbmE&e=
> Transcripts and recordings of GNSO Working Group and Council events are
> located on
> the
> https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_group-2Dactivities_calendar&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=-L6chFfv0OperrXHHpTF722WnH3FZIutn4cS16IvpOg&e=
>
>
>
> _______________________________________________
> 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/20231006/d717d5f6/attachment.htm>

From andrea.glandon at icann.org  Fri Oct  6 18:20:01 2023
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Fri, 6 Oct 2023 15:20:01 +0000
Subject: [NCSG-PC] [Ext] Re: [NCSG-EC] ICANN78 Meet with PSWG
Message-ID: <C422B8CA-CE7C-4038-98BB-4CD1C4799820@icann.org>

Hello all,

I have just chatted with GAC staff and it seems the Sunday, 22 October meeting with PSWG will not work on their end.

What are your thoughts with scheduling this meeting during a lunch break? We can also postpone this to after ICANN78.

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: Tuesday, August 29, 2023 at 07:25
To: "ncsg-ec at lists.ncsg.is" <ncsg-ec at lists.ncsg.is>, "ncsg-pc at lists.ncsg.is" <ncsg-pc at lists.ncsg.is>
Subject: [Ext] Re: [NCSG-EC] ICANN78 Meet with PSWG

Thank you everyone!

It looks like we have support for meeting with the PSWG on Sunday, 22 October. I will reach out to the GAC staff.

Kind Regards,
Andrea


From: Andrea Glandon <andrea.glandon at icann.org>
Date: Thursday, August 24, 2023 at 13:00
To: "ncsg-ec at lists.ncsg.is" <ncsg-ec at lists.ncsg.is>, "ncsg-pc at lists.ncsg.is" <ncsg-pc at lists.ncsg.is>
Cc: Andrea Glandon <andrea.glandon at icann.org>
Subject: ICANN78 Meet with PSWG

Hello!

GAC staff support has reached out to me regarding noncommercials meeting with the PSWG group at ICANN78, if the group is interested. The dates they are looking at are Saturday, 21 October & Sunday, 22 October. On Saturday there sessions for IDNs EPDP, EPDP Phase 2 Small Team, Transfer Policy Review, Subsequent Procedures IRT, Joint At-Large & GNSO session, and GNSO celebration sessions. Sunday is a bit more open in the morning with GNSO working sessions. In the afternoon is the NCSG PC session. Please let me know first if you would like to meet and second if Saturday or Sunday sounds better.

Thanks!
Andrea Glandon
Policy Operations 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/20231006/41bd2c5b/attachment.htm>

From manju at nii.org.tw  Sun Oct  8 10:14:37 2023
From: manju at nii.org.tw (=?UTF-8?B?6Zmz5pu86Iy5IE1hbmp1IENoZW4=?=)
Date: Sun, 8 Oct 2023 15:14:37 +0800
Subject: [NCSG-PC] [Ext] Re: [NCSG-EC] ICANN78 Meet with PSWG
In-Reply-To: <C422B8CA-CE7C-4038-98BB-4CD1C4799820@icann.org>
References: <C422B8CA-CE7C-4038-98BB-4CD1C4799820@icann.org>
Message-ID: <CAMeQZi02H7Y0WVc_0errkAn-S1kAuM0=WUUwk+x0FE0kMcYuwA@mail.gmail.com>

Hi Andrea,

Thank you so much for assisting to schedule the meeting!

I'm fine with having a lunch meeting, although I find it hard to
believe they can't find a time on Sunday. As far as we can tell from the
schedule, the whole day of Sunday is dedicated to capacity building for GAC
members.

If they're not keen on meeting, is there still a need to meet?


Best,
Manju

On Fri, Oct 6, 2023 at 11:20?PM Andrea Glandon <andrea.glandon at icann.org>
wrote:

> Hello all,
>
>
>
> I have just chatted with GAC staff and it seems the Sunday, 22 October
> meeting with PSWG will not work on their end.
>
>
>
> What are your thoughts with scheduling this meeting during a lunch break?
> We can also postpone this to after ICANN78.
>
>
>
> 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: *Tuesday, August 29, 2023 at 07:25
> *To: *"ncsg-ec at lists.ncsg.is" <ncsg-ec at lists.ncsg.is>, "
> ncsg-pc at lists.ncsg.is" <ncsg-pc at lists.ncsg.is>
> *Subject: *[Ext] Re: [NCSG-EC] ICANN78 Meet with PSWG
>
>
>
> Thank you everyone!
>
>
>
> It looks like we have support for meeting with the PSWG on Sunday, 22
> October. I will reach out to the GAC staff.
>
>
>
> Kind Regards,
>
> Andrea
>
>
>
>
>
> *From: *Andrea Glandon <andrea.glandon at icann.org>
> *Date: *Thursday, August 24, 2023 at 13:00
> *To: *"ncsg-ec at lists.ncsg.is" <ncsg-ec at lists.ncsg.is>, "
> ncsg-pc at lists.ncsg.is" <ncsg-pc at lists.ncsg.is>
> *Cc: *Andrea Glandon <andrea.glandon at icann.org>
> *Subject: *ICANN78 Meet with PSWG
>
>
>
> Hello!
>
>
>
> GAC staff support has reached out to me regarding noncommercials meeting
> with the PSWG group at ICANN78, if the group is interested. The dates they
> are looking at are Saturday, 21 October & Sunday, 22 October. On Saturday
> there sessions for IDNs EPDP, EPDP Phase 2 Small Team, Transfer Policy
> Review, Subsequent Procedures IRT, Joint At-Large & GNSO session, and GNSO
> celebration sessions. Sunday is a bit more open in the morning with GNSO
> working sessions. In the afternoon is the NCSG PC session. Please let me
> know first if you would like to meet and second if Saturday or Sunday
> sounds better.
>
>
>
> Thanks!
>
> *Andrea Glandon*
>
> Policy Operations Coordinator
>
> Internet Corporation for Assigned Names and Numbers (ICANN)
>
> *Skype ID:*  acglandon76
>
>
>
>
>
>
> _______________________________________________
> 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/20231008/7a40ea0e/attachment.htm>

From manju at nii.org.tw  Sun Oct  8 10:16:47 2023
From: manju at nii.org.tw (=?UTF-8?B?6Zmz5pu86Iy5IE1hbmp1IENoZW4=?=)
Date: Sun, 8 Oct 2023 15:16:47 +0800
Subject: [NCSG-PC] [Ext] Re: [NCSG-EC] ICANN78 Meet with PSWG
In-Reply-To: <CAMeQZi02H7Y0WVc_0errkAn-S1kAuM0=WUUwk+x0FE0kMcYuwA@mail.gmail.com>
References: <C422B8CA-CE7C-4038-98BB-4CD1C4799820@icann.org>
 <CAMeQZi02H7Y0WVc_0errkAn-S1kAuM0=WUUwk+x0FE0kMcYuwA@mail.gmail.com>
Message-ID: <CAMeQZi1aUfHFN-NCCB9+KUT+2BgT1wjnZSu+bJLLtdhYBfMPeQ@mail.gmail.com>

Sorry for spamming but just wanted to clarify that everything I wrote after
expressing my gratitude to Andrea is addressed to our NCSG members.

Best,
Manju


On Sun, Oct 8, 2023 at 3:14?PM ??? Manju Chen <manju at nii.org.tw> wrote:

> Hi Andrea,
>
> Thank you so much for assisting to schedule the meeting!
>
> I'm fine with having a lunch meeting, although I find it hard to
> believe they can't find a time on Sunday. As far as we can tell from the
> schedule, the whole day of Sunday is dedicated to capacity building for GAC
> members.
>
> If they're not keen on meeting, is there still a need to meet?
>
>
> Best,
> Manju
>
> On Fri, Oct 6, 2023 at 11:20?PM Andrea Glandon <andrea.glandon at icann.org>
> wrote:
>
>> Hello all,
>>
>>
>>
>> I have just chatted with GAC staff and it seems the Sunday, 22 October
>> meeting with PSWG will not work on their end.
>>
>>
>>
>> What are your thoughts with scheduling this meeting during a lunch break?
>> We can also postpone this to after ICANN78.
>>
>>
>>
>> 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: *Tuesday, August 29, 2023 at 07:25
>> *To: *"ncsg-ec at lists.ncsg.is" <ncsg-ec at lists.ncsg.is>, "
>> ncsg-pc at lists.ncsg.is" <ncsg-pc at lists.ncsg.is>
>> *Subject: *[Ext] Re: [NCSG-EC] ICANN78 Meet with PSWG
>>
>>
>>
>> Thank you everyone!
>>
>>
>>
>> It looks like we have support for meeting with the PSWG on Sunday, 22
>> October. I will reach out to the GAC staff.
>>
>>
>>
>> Kind Regards,
>>
>> Andrea
>>
>>
>>
>>
>>
>> *From: *Andrea Glandon <andrea.glandon at icann.org>
>> *Date: *Thursday, August 24, 2023 at 13:00
>> *To: *"ncsg-ec at lists.ncsg.is" <ncsg-ec at lists.ncsg.is>, "
>> ncsg-pc at lists.ncsg.is" <ncsg-pc at lists.ncsg.is>
>> *Cc: *Andrea Glandon <andrea.glandon at icann.org>
>> *Subject: *ICANN78 Meet with PSWG
>>
>>
>>
>> Hello!
>>
>>
>>
>> GAC staff support has reached out to me regarding noncommercials meeting
>> with the PSWG group at ICANN78, if the group is interested. The dates they
>> are looking at are Saturday, 21 October & Sunday, 22 October. On Saturday
>> there sessions for IDNs EPDP, EPDP Phase 2 Small Team, Transfer Policy
>> Review, Subsequent Procedures IRT, Joint At-Large & GNSO session, and GNSO
>> celebration sessions. Sunday is a bit more open in the morning with GNSO
>> working sessions. In the afternoon is the NCSG PC session. Please let me
>> know first if you would like to meet and second if Saturday or Sunday
>> sounds better.
>>
>>
>>
>> Thanks!
>>
>> *Andrea Glandon*
>>
>> Policy Operations Coordinator
>>
>> Internet Corporation for Assigned Names and Numbers (ICANN)
>>
>> *Skype ID:*  acglandon76
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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/20231008/2bc8b233/attachment.htm>

From mesumbeslin at gmail.com  Sun Oct  8 10:54:34 2023
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Sun, 8 Oct 2023 18:54:34 +1100
Subject: [NCSG-PC] [Ext] Re: [NCSG-EC] ICANN78 Meet with PSWG
In-Reply-To: <CAMeQZi1aUfHFN-NCCB9+KUT+2BgT1wjnZSu+bJLLtdhYBfMPeQ@mail.gmail.com>
References: <C422B8CA-CE7C-4038-98BB-4CD1C4799820@icann.org>
 <CAMeQZi02H7Y0WVc_0errkAn-S1kAuM0=WUUwk+x0FE0kMcYuwA@mail.gmail.com>
 <CAMeQZi1aUfHFN-NCCB9+KUT+2BgT1wjnZSu+bJLLtdhYBfMPeQ@mail.gmail.com>
Message-ID: <CAM8DdeUYCS9GXM3PCvn7W7LLgnSWfiVGUje8H-4sPjXQz3dEbA@mail.gmail.com>

I suppose the question to us is, are there real significant benefits of
having a lunch meeting with them? It would have been helpful if there was
some sort of agenda for the meeting.

If the purpose is to keep interactions/communication lines open, then a
lunch meeting isn't so bad.

Warmly,
Tomslin

On Sun, 8 Oct 2023, 18:17 ??? Manju Chen, <manju at nii.org.tw> wrote:

> Sorry for spamming but just wanted to clarify that everything I wrote
> after expressing my gratitude to Andrea is addressed to our NCSG members.
>
> Best,
> Manju
>
>
> On Sun, Oct 8, 2023 at 3:14?PM ??? Manju Chen <manju at nii.org.tw> wrote:
>
>> Hi Andrea,
>>
>> Thank you so much for assisting to schedule the meeting!
>>
>> I'm fine with having a lunch meeting, although I find it hard to
>> believe they can't find a time on Sunday. As far as we can tell from the
>> schedule, the whole day of Sunday is dedicated to capacity building for GAC
>> members.
>>
>> If they're not keen on meeting, is there still a need to meet?
>>
>>
>> Best,
>> Manju
>>
>> On Fri, Oct 6, 2023 at 11:20?PM Andrea Glandon <andrea.glandon at icann.org>
>> wrote:
>>
>>> Hello all,
>>>
>>>
>>>
>>> I have just chatted with GAC staff and it seems the Sunday, 22 October
>>> meeting with PSWG will not work on their end.
>>>
>>>
>>>
>>> What are your thoughts with scheduling this meeting during a lunch
>>> break? We can also postpone this to after ICANN78.
>>>
>>>
>>>
>>> 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: *Tuesday, August 29, 2023 at 07:25
>>> *To: *"ncsg-ec at lists.ncsg.is" <ncsg-ec at lists.ncsg.is>, "
>>> ncsg-pc at lists.ncsg.is" <ncsg-pc at lists.ncsg.is>
>>> *Subject: *[Ext] Re: [NCSG-EC] ICANN78 Meet with PSWG
>>>
>>>
>>>
>>> Thank you everyone!
>>>
>>>
>>>
>>> It looks like we have support for meeting with the PSWG on Sunday, 22
>>> October. I will reach out to the GAC staff.
>>>
>>>
>>>
>>> Kind Regards,
>>>
>>> Andrea
>>>
>>>
>>>
>>>
>>>
>>> *From: *Andrea Glandon <andrea.glandon at icann.org>
>>> *Date: *Thursday, August 24, 2023 at 13:00
>>> *To: *"ncsg-ec at lists.ncsg.is" <ncsg-ec at lists.ncsg.is>, "
>>> ncsg-pc at lists.ncsg.is" <ncsg-pc at lists.ncsg.is>
>>> *Cc: *Andrea Glandon <andrea.glandon at icann.org>
>>> *Subject: *ICANN78 Meet with PSWG
>>>
>>>
>>>
>>> Hello!
>>>
>>>
>>>
>>> GAC staff support has reached out to me regarding noncommercials meeting
>>> with the PSWG group at ICANN78, if the group is interested. The dates they
>>> are looking at are Saturday, 21 October & Sunday, 22 October. On Saturday
>>> there sessions for IDNs EPDP, EPDP Phase 2 Small Team, Transfer Policy
>>> Review, Subsequent Procedures IRT, Joint At-Large & GNSO session, and GNSO
>>> celebration sessions. Sunday is a bit more open in the morning with GNSO
>>> working sessions. In the afternoon is the NCSG PC session. Please let me
>>> know first if you would like to meet and second if Saturday or Sunday
>>> sounds better.
>>>
>>>
>>>
>>> Thanks!
>>>
>>> *Andrea Glandon*
>>>
>>> Policy Operations Coordinator
>>>
>>> Internet Corporation for Assigned Names and Numbers (ICANN)
>>>
>>> *Skype ID:*  acglandon76
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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/20231008/0d39249d/attachment.htm>

From julf at Julf.com  Mon Oct  9 16:38:51 2023
From: julf at Julf.com (Johan Helsingius)
Date: Mon, 9 Oct 2023 15:38:51 +0200
Subject: [NCSG-PC] NCSG seat for ICANN Leadership Program (LP) 2024
In-Reply-To: <AFD33D5C-0161-4B49-8C05-D24815603CED@icann.org>
References: <AFD33D5C-0161-4B49-8C05-D24815603CED@icann.org>
Message-ID: <ac7edd1a-52d4-4343-9449-32df4fbde8b1@Julf.com>




-------- Forwarded Message --------
Subject: 	Invitation - RSVP - ICANN Leadership Program (LP) 2024
Date: 	Fri, 6 Oct 2023 17:43:28 +0000
From: 	Public Responsibility Support <prs at icann.org>
To: 	Johan Helsingius <julf at julf.com>
CC: 	Sandra Hoferichter <info at hoferichter.eu>, Ergys Ramaj 
<ergys.ramaj at icann.org>, Andrea Glandon <andrea.glandon at icann.org>, 
Carlos Reyes <carlos.reyes at icann.org>



Dear Julf,

It was great having you join us for the 2023 ICANN Academy Leadership 
Program (LP)!

We are now preparing for the 8^th ?edition of the LP, which is scheduled 
to take place 29 February - 1 March 2024, two days prior to the official 
start of ICANN79 in San Juan, Puerto Rico.

For this program, one seat is reserved for a representative from the 
NCSG. As you are aware, the program is designed for current 
/_and_/incoming leaders, helping to increase understanding of the 
complexity of ICANN and to develop facilitation skills, as well as 
building a network with other leaders. We are aware that understanding 
ICANN as an organization, the topics discussed within ICANN, and 
interaction within other stakeholder groups can be challenging for 
incoming leaders, but sometimes also for experienced leaders. ICANN and 
the community are making considerable efforts in order to help incoming 
leaders have a good start to their terms and to provide current leaders 
the opportunity to strengthen their leadership and facilitation skills. 
Opportunities for Leadership Program participants include the following:

   * Meet leaders from the other SOs/ACs and get an insight of the
     functionality and issues in other groups
   * Discuss current ICANN topics in an in-depth manner
   * Deepen the understanding of key ICANN processes
   * Develop facilitation and leadership skills, focused personal
     effectiveness to run meetings and foster processes

A preliminary agenda is attached to this email. Kindly note that this is 
subject to change.

Accommodation for participants will be covered between Wednesday and 
Thursday, 28-29 February 2024, and participants will receive a stipend. 
Please note that flights will*NOT*be covered under this program, as 
incoming and current leaders are normally covered by the regular ICANN 
travel support. Please ensure that the leaders you select are being 
covered by ICANN Travel Support for their flights to San Juan for ICANN79.

We would like to ask you to identify one incoming or current leader from 
your stakeholder group who is interested and available to participate in 
this program. We recommend that you also identify an alternate candidate.

*Kindly forward us the names and email addresses of the endorsed 
individuals no later than Wednesday, 15 November 2023, and ask them to 
register **here* <https://forms.gle/cvr6qt5jRXGQKQNo6>***by Friday, 17 
November 2023.*

We hope this program will meet the needs of your community. All 
participants will be encouraged to partake in an open exchange of their 
views, as this will help facilitate cross-constituency collaboration 
during their terms.

We are happy to answer any questions you may have and look forward to 
having your group?s participants confirmed.

If you would like to learn more about the program, Sandra can give a 
short presentation at the upcoming ICANN78 meeting at a time that is 
convenient for your group.

Kind regards,

Sandra Hoferichter, Chair of the ICANN Academy Working Group

Fernanda Iunes, ICANN Capacity Development Program Manager
-------------- next part --------------
A non-text attachment was scrubbed...
Name: LP Agenda 2024.pdf
Type: application/pdf
Size: 79060 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20231009/644b85e1/attachment.pdf>

From andrea.glandon at icann.org  Mon Oct  9 17:06:31 2023
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Mon, 9 Oct 2023 14:06:31 +0000
Subject: [NCSG-PC] [Ext] Re: [NCSG-EC] ICANN78 Meet with PSWG
In-Reply-To: <CAM8DdeUYCS9GXM3PCvn7W7LLgnSWfiVGUje8H-4sPjXQz3dEbA@mail.gmail.com>
References: <C422B8CA-CE7C-4038-98BB-4CD1C4799820@icann.org>
 <CAMeQZi02H7Y0WVc_0errkAn-S1kAuM0=WUUwk+x0FE0kMcYuwA@mail.gmail.com>
 <CAMeQZi1aUfHFN-NCCB9+KUT+2BgT1wjnZSu+bJLLtdhYBfMPeQ@mail.gmail.com>
 <CAM8DdeUYCS9GXM3PCvn7W7LLgnSWfiVGUje8H-4sPjXQz3dEbA@mail.gmail.com>
Message-ID: <4BE15F2C-AB53-4C46-AB6A-5C0D9DF5D530@icann.org>

Hello all,

I reached out and this is what I have for a tentative agenda. Nothing in detail until closer to the meeting, but in general ICANN Developments on DNS Abuse mitigation and WHOIS and Data Protection.

Thanks!
Kind Regards,
Andrea


From: Tomslin Samme-Nlar <mesumbeslin at gmail.com>
Date: Sunday, October 8, 2023 at 02:55
To: ??? Manju Chen <manju at nii.org.tw>
Cc: Andrea Glandon <andrea.glandon at icann.org>, ncsg-pc <ncsg-pc at lists.ncsg.is>, NCSG EC <ncsg-ec at lists.ncsg.is>
Subject: Re: [NCSG-PC] [Ext] Re: [NCSG-EC] ICANN78 Meet with PSWG

I suppose the question to us is, are there real significant benefits of having a lunch meeting with them? It would have been helpful if there was some sort of agenda for the meeting.

If the purpose is to keep interactions/communication lines open, then a lunch meeting isn't so bad.
Warmly,
Tomslin

On Sun, 8 Oct 2023, 18:17 ??? Manju Chen, <manju at nii.org.tw<mailto:manju at nii.org.tw>> wrote:
Sorry for spamming but just wanted to clarify that everything I wrote after expressing my gratitude to Andrea is addressed to our NCSG members.

Best,
Manju


On Sun, Oct 8, 2023 at 3:14?PM ??? Manju Chen <manju at nii.org.tw<mailto:manju at nii.org.tw>> wrote:
Hi Andrea,

Thank you so much for assisting to schedule the meeting!

I'm fine with having a lunch meeting, although I find it hard to believe they can't find a time on Sunday. As far as we can tell from the schedule, the whole day of Sunday is dedicated to capacity building for GAC members.

If they're not keen on meeting, is there still a need to meet?


Best,
Manju

On Fri, Oct 6, 2023 at 11:20?PM Andrea Glandon <andrea.glandon at icann.org<mailto:andrea.glandon at icann.org>> wrote:
Hello all,

I have just chatted with GAC staff and it seems the Sunday, 22 October meeting with PSWG will not work on their end.

What are your thoughts with scheduling this meeting during a lunch break? We can also postpone this to after ICANN78.

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: Tuesday, August 29, 2023 at 07:25
To: "ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>" <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>>, "ncsg-pc at lists.ncsg.is<mailto:ncsg-pc at lists.ncsg.is>" <ncsg-pc at lists.ncsg.is<mailto:ncsg-pc at lists.ncsg.is>>
Subject: [Ext] Re: [NCSG-EC] ICANN78 Meet with PSWG

Thank you everyone!

It looks like we have support for meeting with the PSWG on Sunday, 22 October. I will reach out to the GAC staff.

Kind Regards,
Andrea


From: Andrea Glandon <andrea.glandon at icann.org<mailto:andrea.glandon at icann.org>>
Date: Thursday, August 24, 2023 at 13:00
To: "ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>" <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>>, "ncsg-pc at lists.ncsg.is<mailto:ncsg-pc at lists.ncsg.is>" <ncsg-pc at lists.ncsg.is<mailto:ncsg-pc at lists.ncsg.is>>
Cc: Andrea Glandon <andrea.glandon at icann.org<mailto:andrea.glandon at icann.org>>
Subject: ICANN78 Meet with PSWG

Hello!

GAC staff support has reached out to me regarding noncommercials meeting with the PSWG group at ICANN78, if the group is interested. The dates they are looking at are Saturday, 21 October & Sunday, 22 October. On Saturday there sessions for IDNs EPDP, EPDP Phase 2 Small Team, Transfer Policy Review, Subsequent Procedures IRT, Joint At-Large & GNSO session, and GNSO celebration sessions. Sunday is a bit more open in the morning with GNSO working sessions. In the afternoon is the NCSG PC session. Please let me know first if you would like to meet and second if Saturday or Sunday sounds better.

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



_______________________________________________
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!-1If_Sz5XHnEh11ZnrVewXu9wN_4CXfgc1_WIh7FEYR2p0bEfoAqvCjAQpZAdXTlalbfo_U6hVgKsp2_TVWHqqeA6zooHg$>
_______________________________________________
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!-1If_Sz5XHnEh11ZnrVewXu9wN_4CXfgc1_WIh7FEYR2p0bEfoAqvCjAQpZAdXTlalbfo_U6hVgKsp2_TVWHqqeA6zooHg$>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20231009/132726c1/attachment.htm>

From mesumbeslin at gmail.com  Mon Oct  9 23:03:45 2023
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Tue, 10 Oct 2023 07:03:45 +1100
Subject: [NCSG-PC] NCSG seat for ICANN Leadership Program (LP) 2024
In-Reply-To: <ac7edd1a-52d4-4343-9449-32df4fbde8b1@Julf.com>
References: <AFD33D5C-0161-4B49-8C05-D24815603CED@icann.org>
 <ac7edd1a-52d4-4343-9449-32df4fbde8b1@Julf.com>
Message-ID: <CAM8DdeVOaeHLsjrKTz76g+VnPqzeo5hpAsY-KepE5iJEv_7imQ@mail.gmail.com>

Hi Julf,

Is your expectation that someone from the PC will be selected? Since I
don't believe the PC has made a selection for this before.

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


On Tue, 10 Oct 2023 at 00:38, Johan Helsingius <julf at julf.com> wrote:

>
>
>
> -------- Forwarded Message --------
> Subject:        Invitation - RSVP - ICANN Leadership Program (LP) 2024
> Date:   Fri, 6 Oct 2023 17:43:28 +0000
> From:   Public Responsibility Support <prs at icann.org>
> To:     Johan Helsingius <julf at julf.com>
> CC:     Sandra Hoferichter <info at hoferichter.eu>, Ergys Ramaj
> <ergys.ramaj at icann.org>, Andrea Glandon <andrea.glandon at icann.org>,
> Carlos Reyes <carlos.reyes at icann.org>
>
>
>
> Dear Julf,
>
> It was great having you join us for the 2023 ICANN Academy Leadership
> Program (LP)!
>
> We are now preparing for the 8^th  edition of the LP, which is scheduled
> to take place 29 February - 1 March 2024, two days prior to the official
> start of ICANN79 in San Juan, Puerto Rico.
>
> For this program, one seat is reserved for a representative from the
> NCSG. As you are aware, the program is designed for current
> /_and_/incoming leaders, helping to increase understanding of the
> complexity of ICANN and to develop facilitation skills, as well as
> building a network with other leaders. We are aware that understanding
> ICANN as an organization, the topics discussed within ICANN, and
> interaction within other stakeholder groups can be challenging for
> incoming leaders, but sometimes also for experienced leaders. ICANN and
> the community are making considerable efforts in order to help incoming
> leaders have a good start to their terms and to provide current leaders
> the opportunity to strengthen their leadership and facilitation skills.
> Opportunities for Leadership Program participants include the following:
>
>    * Meet leaders from the other SOs/ACs and get an insight of the
>      functionality and issues in other groups
>    * Discuss current ICANN topics in an in-depth manner
>    * Deepen the understanding of key ICANN processes
>    * Develop facilitation and leadership skills, focused personal
>      effectiveness to run meetings and foster processes
>
> A preliminary agenda is attached to this email. Kindly note that this is
> subject to change.
>
> Accommodation for participants will be covered between Wednesday and
> Thursday, 28-29 February 2024, and participants will receive a stipend.
> Please note that flights will*NOT*be covered under this program, as
> incoming and current leaders are normally covered by the regular ICANN
> travel support. Please ensure that the leaders you select are being
> covered by ICANN Travel Support for their flights to San Juan for ICANN79.
>
> We would like to ask you to identify one incoming or current leader from
> your stakeholder group who is interested and available to participate in
> this program. We recommend that you also identify an alternate candidate.
>
> *Kindly forward us the names and email addresses of the endorsed
> individuals no later than Wednesday, 15 November 2023, and ask them to
> register **here* <https://forms.gle/cvr6qt5jRXGQKQNo6>***by Friday, 17
> November 2023.*
>
> We hope this program will meet the needs of your community. All
> participants will be encouraged to partake in an open exchange of their
> views, as this will help facilitate cross-constituency collaboration
> during their terms.
>
> We are happy to answer any questions you may have and look forward to
> having your group?s participants confirmed.
>
> If you would like to learn more about the program, Sandra can give a
> short presentation at the upcoming ICANN78 meeting at a time that is
> convenient for your group.
>
> Kind regards,
>
> Sandra Hoferichter, Chair of the ICANN Academy Working Group
>
> Fernanda Iunes, ICANN Capacity Development Program Manager
> _______________________________________________
> 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/20231010/e2cf3157/attachment.htm>

From jumaropi at yahoo.com  Mon Oct  9 23:09:57 2023
From: jumaropi at yahoo.com (Juan Manuel Rojas)
Date: Mon, 9 Oct 2023 20:09:57 +0000 (UTC)
Subject: [NCSG-PC] NCSG seat for ICANN Leadership Program (LP) 2024
In-Reply-To: <CAM8DdeVOaeHLsjrKTz76g+VnPqzeo5hpAsY-KepE5iJEv_7imQ@mail.gmail.com>
References: <AFD33D5C-0161-4B49-8C05-D24815603CED@icann.org>
 <ac7edd1a-52d4-4343-9449-32df4fbde8b1@Julf.com>
 <CAM8DdeVOaeHLsjrKTz76g+VnPqzeo5hpAsY-KepE5iJEv_7imQ@mail.gmail.com>
Message-ID: <1269942523.7051892.1696882197311@mail.yahoo.com>

HI Julf and everyone, 
This time is just one for SG? Previous years we have had one representative per Constituency, and the names were suggested by every EC. 

Best Regards,

JUAN MANUEL ROJAS P.
Director - MINKA DIGITAL ColombiaNPOC Policy Chair - NCSG/GNSO
Master IT candidate, UNAD
Registered Linux User No.533108.
http://www.jmanurojas.com 

Cel. +57 301 743 56 00
Instagram/Twitter:?@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 lunes, 9 de octubre de 2023, 03:04:03 p.?m. GMT-5, Tomslin Samme-Nlar <mesumbeslin at gmail.com> escribi?:  
 
 Hi Julf,
Is your expectation that someone from the PC will be selected? Since I don't believe the PC has made a selection for this before.

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


On Tue, 10 Oct 2023 at 00:38, Johan Helsingius <julf at julf.com> wrote:




-------- Forwarded Message --------
Subject:? ? ? ? Invitation - RSVP - ICANN Leadership Program (LP) 2024
Date:? ?Fri, 6 Oct 2023 17:43:28 +0000
From:? ?Public Responsibility Support <prs at icann.org>
To:? ? ?Johan Helsingius <julf at julf.com>
CC:? ? ?Sandra Hoferichter <info at hoferichter.eu>, Ergys Ramaj 
<ergys.ramaj at icann.org>, Andrea Glandon <andrea.glandon at icann.org>, 
Carlos Reyes <carlos.reyes at icann.org>



Dear Julf,

It was great having you join us for the 2023 ICANN Academy Leadership 
Program (LP)!

We are now preparing for the 8^th ?edition of the LP, which is scheduled 
to take place 29 February - 1 March 2024, two days prior to the official 
start of ICANN79 in San Juan, Puerto Rico.

For this program, one seat is reserved for a representative from the 
NCSG. As you are aware, the program is designed for current 
/_and_/incoming leaders, helping to increase understanding of the 
complexity of ICANN and to develop facilitation skills, as well as 
building a network with other leaders. We are aware that understanding 
ICANN as an organization, the topics discussed within ICANN, and 
interaction within other stakeholder groups can be challenging for 
incoming leaders, but sometimes also for experienced leaders. ICANN and 
the community are making considerable efforts in order to help incoming 
leaders have a good start to their terms and to provide current leaders 
the opportunity to strengthen their leadership and facilitation skills. 
Opportunities for Leadership Program participants include the following:

? ?* Meet leaders from the other SOs/ACs and get an insight of the
? ? ?functionality and issues in other groups
? ?* Discuss current ICANN topics in an in-depth manner
? ?* Deepen the understanding of key ICANN processes
? ?* Develop facilitation and leadership skills, focused personal
? ? ?effectiveness to run meetings and foster processes

A preliminary agenda is attached to this email. Kindly note that this is 
subject to change.

Accommodation for participants will be covered between Wednesday and 
Thursday, 28-29 February 2024, and participants will receive a stipend. 
Please note that flights will*NOT*be covered under this program, as 
incoming and current leaders are normally covered by the regular ICANN 
travel support. Please ensure that the leaders you select are being 
covered by ICANN Travel Support for their flights to San Juan for ICANN79.

We would like to ask you to identify one incoming or current leader from 
your stakeholder group who is interested and available to participate in 
this program. We recommend that you also identify an alternate candidate.

*Kindly forward us the names and email addresses of the endorsed 
individuals no later than Wednesday, 15 November 2023, and ask them to 
register **here* <https://forms.gle/cvr6qt5jRXGQKQNo6>***by Friday, 17 
November 2023.*

We hope this program will meet the needs of your community. All 
participants will be encouraged to partake in an open exchange of their 
views, as this will help facilitate cross-constituency collaboration 
during their terms.

We are happy to answer any questions you may have and look forward to 
having your group?s participants confirmed.

If you would like to learn more about the program, Sandra can give a 
short presentation at the upcoming ICANN78 meeting at a time that is 
convenient for your group.

Kind regards,

Sandra Hoferichter, Chair of the ICANN Academy Working Group

Fernanda Iunes, ICANN Capacity Development Program Manager
_______________________________________________
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/20231009/6ae02d73/attachment.htm>

From julf at Julf.com  Tue Oct 10 18:25:53 2023
From: julf at Julf.com (Johan Helsingius)
Date: Tue, 10 Oct 2023 17:25:53 +0200
Subject: [NCSG-PC] ICANN78 NCPH 0-day agenda
Message-ID: <afb1560b-6f64-4d13-a565-db8afdf01ec4@Julf.com>

Here is the current proposed agenda for the NCPH 0-day.

	Julf
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NCPH Day Zero Agenda-ICANN78.pdf
Type: application/pdf
Size: 30940 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20231010/524e3e9e/attachment.pdf>

From julf at Julf.com  Wed Oct 11 18:40:33 2023
From: julf at Julf.com (Johan Helsingius)
Date: Wed, 11 Oct 2023 17:40:33 +0200
Subject: [NCSG-PC] NCSG seat for ICANN Leadership Program (LP) 2024
In-Reply-To: <CAM8DdeVOaeHLsjrKTz76g+VnPqzeo5hpAsY-KepE5iJEv_7imQ@mail.gmail.com>
References: <AFD33D5C-0161-4B49-8C05-D24815603CED@icann.org>
 <ac7edd1a-52d4-4343-9449-32df4fbde8b1@Julf.com>
 <CAM8DdeVOaeHLsjrKTz76g+VnPqzeo5hpAsY-KepE5iJEv_7imQ@mail.gmail.com>
Message-ID: <20323972-1bfd-48bb-871e-80e8ce003e8e@Julf.com>

Typically it would be the incoming NCSG chair, but when a chair gets
re-elected, someone else in our (future) leadership should get
to do it - PC chair, for example.

	Julf


On 09/10/2023 22:03, Tomslin Samme-Nlar wrote:
> Hi Julf,
> 
> Is your expectation that someone from the PC will be selected? Since I 
> don't believe the PC has made a selection for this before.
> 
> Warmly,
> Tomslin
> @LinkedIn: https://www.linkedin.com/in/tomslin/ 
> <https://www.linkedin.com/in/tomslin/>
> 
> 
> On Tue, 10 Oct 2023 at 00:38, Johan Helsingius <julf at julf.com 
> <mailto:julf at julf.com>> wrote:
> 
> 
> 
> 
>     -------- Forwarded Message --------
>     Subject:? ? ? ? Invitation - RSVP - ICANN Leadership Program (LP) 2024
>     Date:? ?Fri, 6 Oct 2023 17:43:28 +0000
>     From:? ?Public Responsibility Support <prs at icann.org
>     <mailto:prs at icann.org>>
>     To:? ? ?Johan Helsingius <julf at julf.com <mailto:julf at julf.com>>
>     CC:? ? ?Sandra Hoferichter <info at hoferichter.eu
>     <mailto:info at hoferichter.eu>>, Ergys Ramaj
>     <ergys.ramaj at icann.org <mailto:ergys.ramaj at icann.org>>, Andrea
>     Glandon <andrea.glandon at icann.org <mailto:andrea.glandon at icann.org>>,
>     Carlos Reyes <carlos.reyes at icann.org <mailto:carlos.reyes at icann.org>>
> 
> 
> 
>     Dear Julf,
> 
>     It was great having you join us for the 2023 ICANN Academy Leadership
>     Program (LP)!
> 
>     We are now preparing for the 8^th ?edition of the LP, which is
>     scheduled
>     to take place 29 February - 1 March 2024, two days prior to the
>     official
>     start of ICANN79 in San Juan, Puerto Rico.
> 
>     For this program, one seat is reserved for a representative from the
>     NCSG. As you are aware, the program is designed for current
>     /_and_/incoming leaders, helping to increase understanding of the
>     complexity of ICANN and to develop facilitation skills, as well as
>     building a network with other leaders. We are aware that understanding
>     ICANN as an organization, the topics discussed within ICANN, and
>     interaction within other stakeholder groups can be challenging for
>     incoming leaders, but sometimes also for experienced leaders. ICANN and
>     the community are making considerable efforts in order to help incoming
>     leaders have a good start to their terms and to provide current leaders
>     the opportunity to strengthen their leadership and facilitation skills.
>     Opportunities for Leadership Program participants include the following:
> 
>      ? ?* Meet leaders from the other SOs/ACs and get an insight of the
>      ? ? ?functionality and issues in other groups
>      ? ?* Discuss current ICANN topics in an in-depth manner
>      ? ?* Deepen the understanding of key ICANN processes
>      ? ?* Develop facilitation and leadership skills, focused personal
>      ? ? ?effectiveness to run meetings and foster processes
> 
>     A preliminary agenda is attached to this email. Kindly note that
>     this is
>     subject to change.
> 
>     Accommodation for participants will be covered between Wednesday and
>     Thursday, 28-29 February 2024, and participants will receive a stipend.
>     Please note that flights will*NOT*be covered under this program, as
>     incoming and current leaders are normally covered by the regular ICANN
>     travel support. Please ensure that the leaders you select are being
>     covered by ICANN Travel Support for their flights to San Juan for
>     ICANN79.
> 
>     We would like to ask you to identify one incoming or current leader
>     from
>     your stakeholder group who is interested and available to
>     participate in
>     this program. We recommend that you also identify an alternate
>     candidate.
> 
>     *Kindly forward us the names and email addresses of the endorsed
>     individuals no later than Wednesday, 15 November 2023, and ask them to
>     register **here* <https://forms.gle/cvr6qt5jRXGQKQNo6
>     <https://forms.gle/cvr6qt5jRXGQKQNo6>>***by Friday, 17
>     November 2023.*
> 
>     We hope this program will meet the needs of your community. All
>     participants will be encouraged to partake in an open exchange of their
>     views, as this will help facilitate cross-constituency collaboration
>     during their terms.
> 
>     We are happy to answer any questions you may have and look forward to
>     having your group?s participants confirmed.
> 
>     If you would like to learn more about the program, Sandra can give a
>     short presentation at the upcoming ICANN78 meeting at a time that is
>     convenient for your group.
> 
>     Kind regards,
> 
>     Sandra Hoferichter, Chair of the ICANN Academy Working Group
> 
>     Fernanda Iunes, ICANN Capacity Development Program Manager
>     _______________________________________________
>     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 julf at Julf.com  Wed Oct 11 18:41:30 2023
From: julf at Julf.com (Johan Helsingius)
Date: Wed, 11 Oct 2023 17:41:30 +0200
Subject: [NCSG-PC] NCSG seat for ICANN Leadership Program (LP) 2024
In-Reply-To: <1269942523.7051892.1696882197311@mail.yahoo.com>
References: <AFD33D5C-0161-4B49-8C05-D24815603CED@icann.org>
 <ac7edd1a-52d4-4343-9449-32df4fbde8b1@Julf.com>
 <CAM8DdeVOaeHLsjrKTz76g+VnPqzeo5hpAsY-KepE5iJEv_7imQ@mail.gmail.com>
 <1269942523.7051892.1696882197311@mail.yahoo.com>
Message-ID: <4e521aa4-f694-4744-83fc-4b0056412a1f@Julf.com>

Hi Juan,

Seems there is one seat for NCSG and one for NPOC, not sure what logic
that is based on.

	Julf


On 09/10/2023 22:09, Juan Manuel Rojas wrote:
> HI Julf and everyone,
> This time is just one for SG? Previous years we have had one 
> representative per Constituency, and the names were suggested by every EC.
> 
> Best Regards,
> 
> *JUAN MANUEL ROJAS P.*
> Director - MINKA DIGITAL Colombia
> NPOC Policy Chair - NCSG/GNSO
> Master IT candidate, UNAD
> Registered Linux User No.*533108.*
> http://www.jmanurojas.com <http://www.jmanurojas.com>
> 
> /Cel. +57 301 743 56 00
> Instagram/Twitter: @JmanuRojas <http://www.twitter.com/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 lunes, 9 de octubre de 2023, 03:04:03 p.?m. GMT-5, Tomslin Samme-Nlar 
> <mesumbeslin at gmail.com> escribi?:
> 
> 
> Hi Julf,
> 
> Is your expectation that someone from the PC will be selected? Since I 
> don't believe the PC has made a selection for this before.
> 
> Warmly,
> Tomslin
> @LinkedIn: https://www.linkedin.com/in/tomslin/ 
> <https://www.linkedin.com/in/tomslin/>
> 
> 
> On Tue, 10 Oct 2023 at 00:38, Johan Helsingius <julf at julf.com 
> <mailto:julf at julf.com>> wrote:
> 
> 
> 
> 
>     -------- Forwarded Message --------
>     Subject:? ? ? ? Invitation - RSVP - ICANN Leadership Program (LP) 2024
>     Date:? ?Fri, 6 Oct 2023 17:43:28 +0000
>     From:? ?Public Responsibility Support <prs at icann.org
>     <mailto:prs at icann.org>>
>     To:? ? ?Johan Helsingius <julf at julf.com <mailto:julf at julf.com>>
>     CC:? ? ?Sandra Hoferichter <info at hoferichter.eu
>     <mailto:info at hoferichter.eu>>, Ergys Ramaj
>     <ergys.ramaj at icann.org <mailto:ergys.ramaj at icann.org>>, Andrea
>     Glandon <andrea.glandon at icann.org <mailto:andrea.glandon at icann.org>>,
>     Carlos Reyes <carlos.reyes at icann.org <mailto:carlos.reyes at icann.org>>
> 
> 
> 
>     Dear Julf,
> 
>     It was great having you join us for the 2023 ICANN Academy Leadership
>     Program (LP)!
> 
>     We are now preparing for the 8^th ?edition of the LP, which is
>     scheduled
>     to take place 29 February - 1 March 2024, two days prior to the
>     official
>     start of ICANN79 in San Juan, Puerto Rico.
> 
>     For this program, one seat is reserved for a representative from the
>     NCSG. As you are aware, the program is designed for current
>     /_and_/incoming leaders, helping to increase understanding of the
>     complexity of ICANN and to develop facilitation skills, as well as
>     building a network with other leaders. We are aware that understanding
>     ICANN as an organization, the topics discussed within ICANN, and
>     interaction within other stakeholder groups can be challenging for
>     incoming leaders, but sometimes also for experienced leaders. ICANN and
>     the community are making considerable efforts in order to help incoming
>     leaders have a good start to their terms and to provide current leaders
>     the opportunity to strengthen their leadership and facilitation skills.
>     Opportunities for Leadership Program participants include the following:
> 
>      ? ?* Meet leaders from the other SOs/ACs and get an insight of the
>      ? ? ?functionality and issues in other groups
>      ? ?* Discuss current ICANN topics in an in-depth manner
>      ? ?* Deepen the understanding of key ICANN processes
>      ? ?* Develop facilitation and leadership skills, focused personal
>      ? ? ?effectiveness to run meetings and foster processes
> 
>     A preliminary agenda is attached to this email. Kindly note that
>     this is
>     subject to change.
> 
>     Accommodation for participants will be covered between Wednesday and
>     Thursday, 28-29 February 2024, and participants will receive a stipend.
>     Please note that flights will*NOT*be covered under this program, as
>     incoming and current leaders are normally covered by the regular ICANN
>     travel support. Please ensure that the leaders you select are being
>     covered by ICANN Travel Support for their flights to San Juan for
>     ICANN79.
> 
>     We would like to ask you to identify one incoming or current leader
>     from
>     your stakeholder group who is interested and available to
>     participate in
>     this program. We recommend that you also identify an alternate
>     candidate.
> 
>     *Kindly forward us the names and email addresses of the endorsed
>     individuals no later than Wednesday, 15 November 2023, and ask them to
>     register **here* <https://forms.gle/cvr6qt5jRXGQKQNo6
>     <https://forms.gle/cvr6qt5jRXGQKQNo6>>***by Friday, 17
>     November 2023.*
> 
>     We hope this program will meet the needs of your community. All
>     participants will be encouraged to partake in an open exchange of their
>     views, as this will help facilitate cross-constituency collaboration
>     during their terms.
> 
>     We are happy to answer any questions you may have and look forward to
>     having your group?s participants confirmed.
> 
>     If you would like to learn more about the program, Sandra can give a
>     short presentation at the upcoming ICANN78 meeting at a time that is
>     convenient for your group.
> 
>     Kind regards,
> 
>     Sandra Hoferichter, Chair of the ICANN Academy Working Group
> 
>     Fernanda Iunes, ICANN Capacity Development Program Manager
>     _______________________________________________
>     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 andrea.glandon at icann.org  Wed Oct 11 19:12:49 2023
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Wed, 11 Oct 2023 16:12:49 +0000
Subject: [NCSG-PC] [Ext] Re: NCSG seat for ICANN Leadership Program (LP)
 2024
In-Reply-To: <4e521aa4-f694-4744-83fc-4b0056412a1f@Julf.com>
References: <AFD33D5C-0161-4B49-8C05-D24815603CED@icann.org>
 <ac7edd1a-52d4-4343-9449-32df4fbde8b1@Julf.com>
 <CAM8DdeVOaeHLsjrKTz76g+VnPqzeo5hpAsY-KepE5iJEv_7imQ@mail.gmail.com>
 <1269942523.7051892.1696882197311@mail.yahoo.com>
 <4e521aa4-f694-4744-83fc-4b0056412a1f@Julf.com>
Message-ID: <CF975402-6CA5-4986-A3B4-9B4726DC8701@icann.org>

Hello!

There is a seat for NCSG, NPOC and NCUC. Raoul and Benjamin received the emails for their groups.

Kind Regards, 
Andrea 




?On 10/11/23, 10:42, "NCSG-PC on behalf of Johan Helsingius" <ncsg-pc-bounces at lists.ncsg.is <mailto:ncsg-pc-bounces at lists.ncsg.is> on behalf of julf at Julf.com <mailto:julf at Julf.com>> wrote:


Hi Juan,


Seems there is one seat for NCSG and one for NPOC, not sure what logic
that is based on.


Julf




On 09/10/2023 22:09, Juan Manuel Rojas wrote:
> HI Julf and everyone,
> This time is just one for SG? Previous years we have had one 
> representative per Constituency, and the names were suggested by every EC.
> 
> Best Regards,
> 
> *JUAN MANUEL ROJAS P.*
> Director - MINKA DIGITAL Colombia
> NPOC Policy Chair - NCSG/GNSO
> Master IT candidate, UNAD
> Registered Linux User No.*533108.*
> https://urldefense.com/v3/__http://www.jmanurojas.com__;!!PtGJab4!9V5TBWdwE9edAIdfBky0aEYvt7zx6W64sBisXpQXliAeRNeL8bFDI7gTa3TkI9KjPbwqG3CTUzt2ZhWZkW-d$ <https://urldefense.com/v3/__http://www.jmanurojas.com__;!!PtGJab4!9V5TBWdwE9edAIdfBky0aEYvt7zx6W64sBisXpQXliAeRNeL8bFDI7gTa3TkI9KjPbwqG3CTUzt2ZhWZkW-d$> [jmanurojas[.]com] <https://urldefense.com/v3/__http://www.jmanurojas.com__;!!PtGJab4!9V5TBWdwE9edAIdfBky0aEYvt7zx6W64sBisXpQXliAeRNeL8bFDI7gTa3TkI9KjPbwqG3CTUzt2ZhWZkW-d$ <https://urldefense.com/v3/__http://www.jmanurojas.com__;!!PtGJab4!9V5TBWdwE9edAIdfBky0aEYvt7zx6W64sBisXpQXliAeRNeL8bFDI7gTa3TkI9KjPbwqG3CTUzt2ZhWZkW-d$> [jmanurojas[.]com]>
> 
> /Cel. +57 301 743 56 00
> Instagram/Twitter: @JmanuRojas <https://urldefense.com/v3/__http://www.twitter.com/jmanurojas__;!!PtGJab4!9V5TBWdwE9edAIdfBky0aEYvt7zx6W64sBisXpQXliAeRNeL8bFDI7gTa3TkI9KjPbwqG3CTUzt2ZiP9sMEX$ <https://urldefense.com/v3/__http://www.twitter.com/jmanurojas__;!!PtGJab4!9V5TBWdwE9edAIdfBky0aEYvt7zx6W64sBisXpQXliAeRNeL8bFDI7gTa3TkI9KjPbwqG3CTUzt2ZiP9sMEX$> [twitter[.]com]>/
> 
> -----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 lunes, 9 de octubre de 2023, 03:04:03 p. m. GMT-5, Tomslin Samme-Nlar 
> <mesumbeslin at gmail.com <mailto:mesumbeslin at gmail.com>> escribi?:
> 
> 
> Hi Julf,
> 
> Is your expectation that someone from the PC will be selected? Since I 
> don't believe the PC has made a selection for this before.
> 
> Warmly,
> Tomslin
> @LinkedIn: https://urldefense.com/v3/__https://www.linkedin.com/in/tomslin/__;!!PtGJab4!9V5TBWdwE9edAIdfBky0aEYvt7zx6W64sBisXpQXliAeRNeL8bFDI7gTa3TkI9KjPbwqG3CTUzt2ZhhyhZxB$ <https://urldefense.com/v3/__https://www.linkedin.com/in/tomslin/__;!!PtGJab4!9V5TBWdwE9edAIdfBky0aEYvt7zx6W64sBisXpQXliAeRNeL8bFDI7gTa3TkI9KjPbwqG3CTUzt2ZhhyhZxB$> [linkedin[.]com] 
> <https://urldefense.com/v3/__https://www.linkedin.com/in/tomslin/__;!!PtGJab4!9V5TBWdwE9edAIdfBky0aEYvt7zx6W64sBisXpQXliAeRNeL8bFDI7gTa3TkI9KjPbwqG3CTUzt2ZhhyhZxB$ <https://urldefense.com/v3/__https://www.linkedin.com/in/tomslin/__;!!PtGJab4!9V5TBWdwE9edAIdfBky0aEYvt7zx6W64sBisXpQXliAeRNeL8bFDI7gTa3TkI9KjPbwqG3CTUzt2ZhhyhZxB$> [linkedin[.]com]>
> 
> 
> On Tue, 10 Oct 2023 at 00:38, Johan Helsingius <julf at julf.com <mailto:julf at julf.com> 
> <mailto:julf at julf.com <mailto:julf at julf.com>>> wrote:
> 
> 
> 
> 
> -------- Forwarded Message --------
> Subject: Invitation - RSVP - ICANN Leadership Program (LP) 2024
> Date: Fri, 6 Oct 2023 17:43:28 +0000
> From: Public Responsibility Support <prs at icann.org <mailto:prs at icann.org>
> <mailto:prs at icann.org <mailto:prs at icann.org>>>
> To: Johan Helsingius <julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>>>
> CC: Sandra Hoferichter <info at hoferichter.eu <mailto:info at hoferichter.eu>
> <mailto:info at hoferichter.eu <mailto:info at hoferichter.eu>>>, Ergys Ramaj
> <ergys.ramaj at icann.org <mailto:ergys.ramaj at icann.org> <mailto:ergys.ramaj at icann.org <mailto:ergys.ramaj at icann.org>>>, Andrea
> Glandon <andrea.glandon at icann.org <mailto:andrea.glandon at icann.org> <mailto:andrea.glandon at icann.org <mailto:andrea.glandon at icann.org>>>,
> Carlos Reyes <carlos.reyes at icann.org <mailto:carlos.reyes at icann.org> <mailto:carlos.reyes at icann.org <mailto:carlos.reyes at icann.org>>>
> 
> 
> 
> Dear Julf,
> 
> It was great having you join us for the 2023 ICANN Academy Leadership
> Program (LP)!
> 
> We are now preparing for the 8^th edition of the LP, which is
> scheduled
> to take place 29 February - 1 March 2024, two days prior to the
> official
> start of ICANN79 in San Juan, Puerto Rico.
> 
> For this program, one seat is reserved for a representative from the
> NCSG. As you are aware, the program is designed for current
> /_and_/incoming leaders, helping to increase understanding of the
> complexity of ICANN and to develop facilitation skills, as well as
> building a network with other leaders. We are aware that understanding
> ICANN as an organization, the topics discussed within ICANN, and
> interaction within other stakeholder groups can be challenging for
> incoming leaders, but sometimes also for experienced leaders. ICANN and
> the community are making considerable efforts in order to help incoming
> leaders have a good start to their terms and to provide current leaders
> the opportunity to strengthen their leadership and facilitation skills.
> Opportunities for Leadership Program participants include the following:
> 
> * Meet leaders from the other SOs/ACs and get an insight of the
> functionality and issues in other groups
> * Discuss current ICANN topics in an in-depth manner
> * Deepen the understanding of key ICANN processes
> * Develop facilitation and leadership skills, focused personal
> effectiveness to run meetings and foster processes
> 
> A preliminary agenda is attached to this email. Kindly note that
> this is
> subject to change.
> 
> Accommodation for participants will be covered between Wednesday and
> Thursday, 28-29 February 2024, and participants will receive a stipend.
> Please note that flights will*NOT*be covered under this program, as
> incoming and current leaders are normally covered by the regular ICANN
> travel support. Please ensure that the leaders you select are being
> covered by ICANN Travel Support for their flights to San Juan for
> ICANN79.
> 
> We would like to ask you to identify one incoming or current leader
> from
> your stakeholder group who is interested and available to
> participate in
> this program. We recommend that you also identify an alternate
> candidate.
> 
> *Kindly forward us the names and email addresses of the endorsed
> individuals no later than Wednesday, 15 November 2023, and ask them to
> register **here* <https://urldefense.com/v3/__https://forms.gle/cvr6qt5jRXGQKQNo6__;!!PtGJab4!9V5TBWdwE9edAIdfBky0aEYvt7zx6W64sBisXpQXliAeRNeL8bFDI7gTa3TkI9KjPbwqG3CTUzt2ZuRH1-a5$ <https://urldefense.com/v3/__https://forms.gle/cvr6qt5jRXGQKQNo6__;!!PtGJab4!9V5TBWdwE9edAIdfBky0aEYvt7zx6W64sBisXpQXliAeRNeL8bFDI7gTa3TkI9KjPbwqG3CTUzt2ZuRH1-a5$> [forms[.]gle]
> <https://urldefense.com/v3/__https://forms.gle/cvr6qt5jRXGQKQNo6__;!!PtGJab4!9V5TBWdwE9edAIdfBky0aEYvt7zx6W64sBisXpQXliAeRNeL8bFDI7gTa3TkI9KjPbwqG3CTUzt2ZuRH1-a5$ <https://urldefense.com/v3/__https://forms.gle/cvr6qt5jRXGQKQNo6__;!!PtGJab4!9V5TBWdwE9edAIdfBky0aEYvt7zx6W64sBisXpQXliAeRNeL8bFDI7gTa3TkI9KjPbwqG3CTUzt2ZuRH1-a5$> [forms[.]gle]>>***by Friday, 17
> November 2023.*
> 
> We hope this program will meet the needs of your community. All
> participants will be encouraged to partake in an open exchange of their
> views, as this will help facilitate cross-constituency collaboration
> during their terms.
> 
> We are happy to answer any questions you may have and look forward to
> having your group?s participants confirmed.
> 
> If you would like to learn more about the program, Sandra can give a
> short presentation at the upcoming ICANN78 meeting at a time that is
> convenient for your group.
> 
> Kind regards,
> 
> Sandra Hoferichter, Chair of the ICANN Academy Working Group
> 
> Fernanda Iunes, ICANN Capacity Development Program Manager
> _______________________________________________
> 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://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-pc__;!!PtGJab4!9V5TBWdwE9edAIdfBky0aEYvt7zx6W64sBisXpQXliAeRNeL8bFDI7gTa3TkI9KjPbwqG3CTUzt2Zl2CoMXw$ <https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-pc__;!!PtGJab4!9V5TBWdwE9edAIdfBky0aEYvt7zx6W64sBisXpQXliAeRNeL8bFDI7gTa3TkI9KjPbwqG3CTUzt2Zl2CoMXw$> [lists[.]ncsg[.]is]
> <https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-pc__;!!PtGJab4!9V5TBWdwE9edAIdfBky0aEYvt7zx6W64sBisXpQXliAeRNeL8bFDI7gTa3TkI9KjPbwqG3CTUzt2Zl2CoMXw$ <https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-pc__;!!PtGJab4!9V5TBWdwE9edAIdfBky0aEYvt7zx6W64sBisXpQXliAeRNeL8bFDI7gTa3TkI9KjPbwqG3CTUzt2Zl2CoMXw$> [lists[.]ncsg[.]is]>
> 
> _______________________________________________
> 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://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-pc__;!!PtGJab4!9V5TBWdwE9edAIdfBky0aEYvt7zx6W64sBisXpQXliAeRNeL8bFDI7gTa3TkI9KjPbwqG3CTUzt2Zl2CoMXw$ <https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-pc__;!!PtGJab4!9V5TBWdwE9edAIdfBky0aEYvt7zx6W64sBisXpQXliAeRNeL8bFDI7gTa3TkI9KjPbwqG3CTUzt2Zl2CoMXw$> [lists[.]ncsg[.]is] 
> <https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-pc__;!!PtGJab4!9V5TBWdwE9edAIdfBky0aEYvt7zx6W64sBisXpQXliAeRNeL8bFDI7gTa3TkI9KjPbwqG3CTUzt2Zl2CoMXw$ <https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-pc__;!!PtGJab4!9V5TBWdwE9edAIdfBky0aEYvt7zx6W64sBisXpQXliAeRNeL8bFDI7gTa3TkI9KjPbwqG3CTUzt2Zl2CoMXw$> [lists[.]ncsg[.]is]>
_______________________________________________
NCSG-PC mailing list
NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-pc__;!!PtGJab4!9V5TBWdwE9edAIdfBky0aEYvt7zx6W64sBisXpQXliAeRNeL8bFDI7gTa3TkI9KjPbwqG3CTUzt2Zl2CoMXw$ <https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-pc__;!!PtGJab4!9V5TBWdwE9edAIdfBky0aEYvt7zx6W64sBisXpQXliAeRNeL8bFDI7gTa3TkI9KjPbwqG3CTUzt2Zl2CoMXw$> [lists[.]ncsg[.]is]




From mesumbeslin at gmail.com  Wed Oct 11 19:29:27 2023
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Thu, 12 Oct 2023 03:29:27 +1100
Subject: [NCSG-PC] NCSG seat for ICANN Leadership Program (LP) 2024
In-Reply-To: <20323972-1bfd-48bb-871e-80e8ce003e8e@Julf.com>
References: <AFD33D5C-0161-4B49-8C05-D24815603CED@icann.org>
 <ac7edd1a-52d4-4343-9449-32df4fbde8b1@Julf.com>
 <CAM8DdeVOaeHLsjrKTz76g+VnPqzeo5hpAsY-KepE5iJEv_7imQ@mail.gmail.com>
 <20323972-1bfd-48bb-871e-80e8ce003e8e@Julf.com>
Message-ID: <CAM8DdeUdphPHF-8v_v89nvm_fXHVNtK8a685G=PAYE97zZGgmg@mail.gmail.com>

I get it now. Makes sense.

Warmly,
Tomslin

On Thu, 12 Oct 2023, 02:40 Johan Helsingius, <julf at julf.com> wrote:

> Typically it would be the incoming NCSG chair, but when a chair gets
> re-elected, someone else in our (future) leadership should get
> to do it - PC chair, for example.
>
>         Julf
>
>
> On 09/10/2023 22:03, Tomslin Samme-Nlar wrote:
> > Hi Julf,
> >
> > Is your expectation that someone from the PC will be selected? Since I
> > don't believe the PC has made a selection for this before.
> >
> > Warmly,
> > Tomslin
> > @LinkedIn: https://www.linkedin.com/in/tomslin/
> > <https://www.linkedin.com/in/tomslin/>
> >
> >
> > On Tue, 10 Oct 2023 at 00:38, Johan Helsingius <julf at julf.com
> > <mailto:julf at julf.com>> wrote:
> >
> >
> >
> >
> >     -------- Forwarded Message --------
> >     Subject:        Invitation - RSVP - ICANN Leadership Program (LP)
> 2024
> >     Date:   Fri, 6 Oct 2023 17:43:28 +0000
> >     From:   Public Responsibility Support <prs at icann.org
> >     <mailto:prs at icann.org>>
> >     To:     Johan Helsingius <julf at julf.com <mailto:julf at julf.com>>
> >     CC:     Sandra Hoferichter <info at hoferichter.eu
> >     <mailto:info at hoferichter.eu>>, Ergys Ramaj
> >     <ergys.ramaj at icann.org <mailto:ergys.ramaj at icann.org>>, Andrea
> >     Glandon <andrea.glandon at icann.org <mailto:andrea.glandon at icann.org
> >>,
> >     Carlos Reyes <carlos.reyes at icann.org <mailto:carlos.reyes at icann.org
> >>
> >
> >
> >
> >     Dear Julf,
> >
> >     It was great having you join us for the 2023 ICANN Academy Leadership
> >     Program (LP)!
> >
> >     We are now preparing for the 8^th  edition of the LP, which is
> >     scheduled
> >     to take place 29 February - 1 March 2024, two days prior to the
> >     official
> >     start of ICANN79 in San Juan, Puerto Rico.
> >
> >     For this program, one seat is reserved for a representative from the
> >     NCSG. As you are aware, the program is designed for current
> >     /_and_/incoming leaders, helping to increase understanding of the
> >     complexity of ICANN and to develop facilitation skills, as well as
> >     building a network with other leaders. We are aware that
> understanding
> >     ICANN as an organization, the topics discussed within ICANN, and
> >     interaction within other stakeholder groups can be challenging for
> >     incoming leaders, but sometimes also for experienced leaders. ICANN
> and
> >     the community are making considerable efforts in order to help
> incoming
> >     leaders have a good start to their terms and to provide current
> leaders
> >     the opportunity to strengthen their leadership and facilitation
> skills.
> >     Opportunities for Leadership Program participants include the
> following:
> >
> >         * Meet leaders from the other SOs/ACs and get an insight of the
> >           functionality and issues in other groups
> >         * Discuss current ICANN topics in an in-depth manner
> >         * Deepen the understanding of key ICANN processes
> >         * Develop facilitation and leadership skills, focused personal
> >           effectiveness to run meetings and foster processes
> >
> >     A preliminary agenda is attached to this email. Kindly note that
> >     this is
> >     subject to change.
> >
> >     Accommodation for participants will be covered between Wednesday and
> >     Thursday, 28-29 February 2024, and participants will receive a
> stipend.
> >     Please note that flights will*NOT*be covered under this program, as
> >     incoming and current leaders are normally covered by the regular
> ICANN
> >     travel support. Please ensure that the leaders you select are being
> >     covered by ICANN Travel Support for their flights to San Juan for
> >     ICANN79.
> >
> >     We would like to ask you to identify one incoming or current leader
> >     from
> >     your stakeholder group who is interested and available to
> >     participate in
> >     this program. We recommend that you also identify an alternate
> >     candidate.
> >
> >     *Kindly forward us the names and email addresses of the endorsed
> >     individuals no later than Wednesday, 15 November 2023, and ask them
> to
> >     register **here* <https://forms.gle/cvr6qt5jRXGQKQNo6
> >     <https://forms.gle/cvr6qt5jRXGQKQNo6>>***by Friday, 17
> >     November 2023.*
> >
> >     We hope this program will meet the needs of your community. All
> >     participants will be encouraged to partake in an open exchange of
> their
> >     views, as this will help facilitate cross-constituency collaboration
> >     during their terms.
> >
> >     We are happy to answer any questions you may have and look forward to
> >     having your group?s participants confirmed.
> >
> >     If you would like to learn more about the program, Sandra can give a
> >     short presentation at the upcoming ICANN78 meeting at a time that is
> >     convenient for your group.
> >
> >     Kind regards,
> >
> >     Sandra Hoferichter, Chair of the ICANN Academy Working Group
> >
> >     Fernanda Iunes, ICANN Capacity Development Program Manager
> >     _______________________________________________
> >     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>
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20231012/2e82d765/attachment.htm>

From PolicyCalendar at icann.org  Fri Oct 13 19:05:13 2023
From: PolicyCalendar at icann.org (ICANN Policy Calendar)
Date: Fri, 13 Oct 2023 16:05:13 +0000
Subject: [NCSG-PC] NCSG Policy Call | 13 November at 11:30 UTC
Message-ID: <84e85d8f23254525b1fbf22549f28063@icann.org>

Please join the NCSG Monthly Policy call on Monday, 13 November at 11:30 UTC.

Join Zoom Meeting: https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09
Meeting ID: 988 7818 9584
Passcode: i!y7.qx&#43;11

One tap mobile
&#43;16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose)
&#43;12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma)
PHONE ONLY DETAILS:
Find your local number: https://icann.zoom.us/u/ayKmeftWg
Meeting ID: 988 7818 9584
Phone only Passcode: 7740925615

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

From PolicyCalendar at icann.org  Fri Oct 13 19:05:21 2023
From: PolicyCalendar at icann.org (ICANN Policy Calendar)
Date: Fri, 13 Oct 2023 16:05:21 +0000
Subject: [NCSG-PC] NCSG Policy Call | 18 December at 11:30 UTC
Message-ID: <5d22a8b079514c2f814b3bf9410ccfab@icann.org>

Please join the NCSG Monthly Policy call on Monday, 18 December at 11:30 UTC.

Join Zoom Meeting: https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09
Meeting ID: 988 7818 9584
Passcode: i!y7.qx&#43;11

One tap mobile
&#43;16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose)
&#43;12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma)
PHONE ONLY DETAILS:
Find your local number: https://icann.zoom.us/u/ayKmeftWg
Meeting ID: 988 7818 9584
Phone only Passcode: 7740925615

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

From mesumbeslin at gmail.com  Tue Oct 17 10:08:16 2023
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Tue, 17 Oct 2023 18:08:16 +1100
Subject: [NCSG-PC] [Call for volunteers] Public Comment: Pilot Holistic
 Review Revised Draft Terms of Reference
In-Reply-To: <CAM8DdeWXn-=jU5iBYRapPEM-xGHzJrYJkFAWm8avS9KUzNQFmw@mail.gmail.com>
References: <CAM8DdeWXn-=jU5iBYRapPEM-xGHzJrYJkFAWm8avS9KUzNQFmw@mail.gmail.com>
Message-ID: <CAM8DdeXd5+TtGVXXOVa=rfPzyKajXURz2-8cQ+SbNRHXFL9zEg@mail.gmail.com>

Hi all,

Just bringing this to your attention again.
If you'd like to volunteer to draft a comment, please do not hesitate to
let me know.

Warmly,
Tomslin

On Thu, 5 Oct 2023, 21:28 Tomslin Samme-Nlar, <mesumbeslin at gmail.com> wrote:

> Dear all,
>
> The ICANN Board is seeking the community input on the proposed Pilot
> Holistic Review Revised Draft Terms of Reference. This is a review of
> interest to NCSG, so it would be great to have members volunteer to draft a
> comment for our SG.
>
> The public comment is due on 27 November 2023, so if you'd like to
> volunteer,  please reach out.
>
> More information on the comment can be found from the below link:
>
> https://www.icann.org/en/public-comment/proceeding/pilot-holistic-review-revised-terms-of-reference-tor-28-09-2023
>
> Warmly,
> Tomslin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20231017/bae61c26/attachment.htm>

From julf at Julf.com  Wed Oct 18 12:52:36 2023
From: julf at Julf.com (Johan Helsingius)
Date: Wed, 18 Oct 2023 11:52:36 +0200
Subject: [NCSG-PC] Fwd: Vice chair selection
In-Reply-To: <BY5PR04MB71241927F9BC65C871CD3853A5D6A@BY5PR04MB7124.namprd04.prod.outlook.com>
References: <BY5PR04MB71241927F9BC65C871CD3853A5D6A@BY5PR04MB7124.namprd04.prod.outlook.com>
Message-ID: <1f36261f-c9e3-47fa-a43e-dea18387fe10@Julf.com>

FYI

	Julf

-------- Forwarded Message --------
Subject: RE: Vice chair selection
Date: Tue, 17 Oct 2023 20:51:39 +0000
From: Cole, Mason (Perkins Coie) <MCole at perkinscoie.com>
To: Johan Helsingius <julf at Julf.com>

Julf --

As noted, the CSG accepts Tomslin as vice chair for the upcoming term. 
We agree that he is qualified and we are willing to reappoint him as 
vice chair as an act of good faith and our ongoing efforts at 
cooperation between our SGs.  Thank you for notifying Andrea of this 
appointment.

As you know, the CSG has strong concerns that going forward the CSG and 
NCSG cannot effectively consider new appointments until a new, 
well-articulated agreement is reached.  We look forward to discussion of 
that subject as part of our Day 0 agenda.

Safe travels and see you in Hamburg.

Mason

Mason Cole | Perkins Coie LLP
INTERNET GOVERNANCE ADVISOR
1120 N.W. Couch Street Tenth Floor
D. +1.503.727.2074
E. MCole at perkinscoie.com


-----Original Message-----
From: Johan Helsingius <julf at Julf.com>
Sent: Monday, October 16, 2023 4:39 AM
To: Cole, Mason (POR) <MCole at perkinscoie.com>
Subject: Vice chair selection

Hi Mason,

The NCSG leadership has discussed the VC selection situation over the 
weekend. We feel that Tomslin has the best experience and background for 
the VC position, so we continue to propose and support him. We are more 
than happy to start a discussion about the VC selection process, but 
feel that the successful appointment of Chris Buckridge shows that the 
Board Seat 14 process works as it is, as long as the process is started 
early enough, and all parties work in good faith.

I am happy to discuss the situation - I am available today until
17:00 UTC (10 am PDT).

         Julf


________________________________

NOTICE: This communication may contain privileged or other confidential 
information. If you have received it in error, please advise the sender 
by reply email and immediately delete the message and any attachments 
without copying or disclosing the contents. Thank you.


From mesumbeslin at gmail.com  Thu Oct 19 19:17:16 2023
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Thu, 19 Oct 2023 18:17:16 +0200
Subject: [NCSG-PC] [NCSG-EC] Fwd: Vice chair selection
In-Reply-To: <1f36261f-c9e3-47fa-a43e-dea18387fe10@Julf.com>
References: <BY5PR04MB71241927F9BC65C871CD3853A5D6A@BY5PR04MB7124.namprd04.prod.outlook.com>
 <1f36261f-c9e3-47fa-a43e-dea18387fe10@Julf.com>
Message-ID: <CAM8DdeXaZgmjG_BvLVK13okt13CRrTMfkzSnzg9iCQoX7AJNqw@mail.gmail.com>

Thanks, Julf.

Looking forward to serve GNSO.

Warmly,
Tomslin

On Wed, 18 Oct 2023, 11:52 Johan Helsingius via NCSG-EC, <
ncsg-ec at lists.ncsg.is> wrote:

> FYI
>
>         Julf
>
> -------- Forwarded Message --------
> Subject: RE: Vice chair selection
> Date: Tue, 17 Oct 2023 20:51:39 +0000
> From: Cole, Mason (Perkins Coie) <MCole at perkinscoie.com>
> To: Johan Helsingius <julf at Julf.com>
>
> Julf --
>
> As noted, the CSG accepts Tomslin as vice chair for the upcoming term.
> We agree that he is qualified and we are willing to reappoint him as
> vice chair as an act of good faith and our ongoing efforts at
> cooperation between our SGs.  Thank you for notifying Andrea of this
> appointment.
>
> As you know, the CSG has strong concerns that going forward the CSG and
> NCSG cannot effectively consider new appointments until a new,
> well-articulated agreement is reached.  We look forward to discussion of
> that subject as part of our Day 0 agenda.
>
> Safe travels and see you in Hamburg.
>
> Mason
>
> Mason Cole | Perkins Coie LLP
> INTERNET GOVERNANCE ADVISOR
> 1120 N.W. Couch Street Tenth Floor
> D. +1.503.727.2074
> E. MCole at perkinscoie.com
>
>
> -----Original Message-----
> From: Johan Helsingius <julf at Julf.com>
> Sent: Monday, October 16, 2023 4:39 AM
> To: Cole, Mason (POR) <MCole at perkinscoie.com>
> Subject: Vice chair selection
>
> Hi Mason,
>
> The NCSG leadership has discussed the VC selection situation over the
> weekend. We feel that Tomslin has the best experience and background for
> the VC position, so we continue to propose and support him. We are more
> than happy to start a discussion about the VC selection process, but
> feel that the successful appointment of Chris Buckridge shows that the
> Board Seat 14 process works as it is, as long as the process is started
> early enough, and all parties work in good faith.
>
> I am happy to discuss the situation - I am available today until
> 17:00 UTC (10 am PDT).
>
>          Julf
>
>
> ________________________________
>
> NOTICE: This communication may contain privileged or other confidential
> information. If you have received it in error, please advise the sender
> by reply email and immediately delete the message and any attachments
> without copying or disclosing the contents. Thank you.
> _______________________________________________
> 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/20231019/4a0cef3c/attachment.htm>

From mesumbeslin at gmail.com  Fri Oct 20 15:00:35 2023
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Fri, 20 Oct 2023 23:00:35 +1100
Subject: [NCSG-PC] NCSG Comment on Proposed Updates to Existing Rights
 Protection Mechanisms Documentation
Message-ID: <CAM8DdeVAX5J4ZEFuffV9J1qVGjyWM107eTSPdJcSbkm+mw2MBQ@mail.gmail.com>

Hi team,

Here is a draft comment for your review, on the Proposed Updates to
Existing Rights Protection Mechanisms Documentation that Pedro and Kathy
have kindly volunteered to put together.
https://docs.google.com/document/d/16v95g6hzBe168FRQdFBf5PIhJ43GIZVhimulcjICHrY/edit#heading=h.cmnkyohhrwk7

Please review and provide feedback (if any).

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

From mesumbeslin at gmail.com  Sun Oct 22 06:37:05 2023
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Sun, 22 Oct 2023 05:37:05 +0200
Subject: [NCSG-PC] Fwd: [council] Proposed Agenda | GNSO Council Meeting |
 Wednesday, 25 October 2023 Part 1 and 2
In-Reply-To: <CD4F560A-0E3E-416A-B98A-0BFB449A768C@icann.org>
References: <CD4F560A-0E3E-416A-B98A-0BFB449A768C@icann.org>
Message-ID: <CAM8DdeWk4QbgapxxVQ4pwMQNsz3J8YKKrqRR5a+m5W9fB=Q+4w@mail.gmail.com>

FYI.
We'll walk through this agenda during the Policy Committee meeting
today at 15:00
Hamburg (UTC +2)

Warmly,
Tomslin



---------- Forwarded message ---------
From: Terri Agnew via council <council at gnso.icann.org>
Date: Sun, 15 Oct 2023 at 14:59
Subject: [council] Proposed Agenda | GNSO Council Meeting | Wednesday, 25
October 2023 Part 1 and 2
To: council at gnso.icann.org <council at gnso.icann.org>,
liaison6c at gnso.icann.org <liaison6c at gnso.icann.org>
Cc: gnso-secs at icann.org <gnso-secs at icann.org>


Dear all,



Please find below the final proposed agenda for the GNSO Council Meeting
taking place on Wednesday, 25 October 2023 at 11:00 UTC for 2 hours (Part
1) and 13:15 for 30 minutes (Part 2). This has been posted on the agenda
wiki pages, part 1 <https://community.icann.org/x/vYXxDg> and part 2
<https://community.icann.org/x/tIXxDg>.



Thank you.



Kind regards,



Terri



Part 1



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



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

For convenience:

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



GNSO Council meeting held in Hamburg, Germany 13:00 - 15:00 CEST:
https://tinyurl.com/ycktn6se



Coordinated Universal Time: 11:00 - 13:00 UTC



04:00 Los Angeles; 07:00 Washington DC; 12:00 London; 13:00 Paris; 14:00
Moscow; 22:00 Melbourne



*GNSO Council Meeting Remote Participation:*

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

___________________________________

*Item 1: Administrative Matters (5 minutes)*

1.1 - Roll Call

1.2 - Updates to Statements of Interest

1.3 - Review / Amend Agenda

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

Minutes
<https://gnso.icann.org/sites/default/files/policy/2023/minutes/minutes-gnso-council-24aug23-en.pdf>of
the GNSO Council meeting on 24 August 2023 were posted on 09 September 2023.

Minutes
<https://gnso.icann.org/sites/default/files/policy/2023/minutes/minutes-gnso-council-21sep23-en.pdf>
of the GNSO Council Meeting on 21 September 2023 were posted on 08 October
2023.



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

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



*Item 3: Consent Agenda (5 minutes) *

   - Confirmation of Appointment of Ashley Heineman as GNSO-appointed
   Co-Chair of the IANA Naming Function Review Team

*Item 4: COUNCIL VOTE - GNSO Council Committee for Overseeing and
Implementing Continuous Improvement (CCOICI) Recommendations Report on
Review of the Statement of Interest (SOI) Requirements (15 minutes)*

The GNSO Framework for Continuous Improvement Pilot was initiated in June
2021 to determine whether the framework, as outlined here
<https://gnso.icann.org/en/drafts/continuous-improvement-oversight-implementation-framework-29jun21-en.pdf>,
could serve as an approach for dealing with the various projects that are
focused on improvements to GNSO processes and procedures.

The CCOICI tasked <https://community.icann.org/x/NAAiCw> the GNSO Statement
of Interest (SOI) Task Force to address the following questions:

   1. Is the original objective of the SOI, as stated in the BGC WG Report,
   still valid? If not, why not and what should the current objective be?
   2. Based on the response to question 1), is the requested information to
   be provided as part of the SOI still fit for purpose? If not, why not, and
   what would need to be changed to make it fit for purpose?
   3. Are there any further measures that should be considered from an
   enforcement / escalation perspective, in addition or instead of those
   already included in the requirements?

The Council Committee for Overseeing and Implementing Continuous
Improvement (CCOICI) submitted to the GNSO Council for consideration its
Recommendations Report following its review of the Recommendations Report
submitted to the CCOICI by the GNSO Statement of Interest Task Force based
on their review of the GNSO Statement of Interest (SOI) Requirements as
well as their review of the input received in response to the public
comment forum. During the meeting in August 2023, Manju Chen presented an
overview of the CCOICI Recommendations Report
<https://gnso.icann.org/sites/default/files/policy/2023/correspondence/chen-to-gnso-council-14aug23-en.pdf>
on the SOI Requirements



Here, the Council will vote on the CCOICI Recommendations Report
<https://gnso.icann.org/sites/default/files/policy/2023/correspondence/chen-to-gnso-council-14aug23-en.pdf>
on the SOI Requirements.

4.1 ? Presentation of motion <https://community.icann.org/x/sYXxDg> (Manju
Chen, CCOICI Chair)

4.2 ? Council discussion

4.3 ? Council Vote (voting threshold: simple majority)



*Item 5: COUNCIL DISCUSSION - Optional Topics for Potential Council
Response (30 minutes)*

*(i) Pilot Holistic Review Revised Draft Terms of Reference *

The ICANN Board is currently seeking the community's input on the
proposed Pilot
Holistic Review Revised Draft Terms of Reference
<https://www.icann.org/en/system/files/files/pilot-holistic-review-draft-tor-18sep23-en.pdf>.
This is an update to the first version posted for Public Comment in August
2022 and has been modified to reflect community input. The primary focus of
the Pilot Holistic Review Draft Terms of Reference (ToR) is to address the
four primary issues raised during the first Public Comment proceeding:

   - The scope of Holistic Review is unclear
   - There is a lack of independent examination in the Holistic Review
   - There is a lack of identified dependencies
   - The community might not have the ability to support the Pilot Holistic
   Review work

The ToR Development Team also shortened and revised the ToR document to
include more direct language and clearer deliverables.

Considering the potential implications on the ICANN structures and work,
the Board is seeking input on whether the revised Draft ToR
<https://gnso.icann.org/sites/default/files/policy/2023/correspondence/gurnick-to-soac-leadership-cip-ccg-et-al-13oct23-en.pdf>
seems fit for purpose, and whether it sufficiently addresses the issues
identified in the first Public Comment proceeding.

The following questions are designed to aid responders in formulating their
views:

   1. Do you support the Pilot Holistic Review Revised Terms of Reference
   as drafted?
   2. Does the Pilot Holistic Review Revised Terms of Reference
   sufficiently address the four primary issues identified in the first Public
   Comment proceeding?
   3. Does the Pilot Holistic Review Revised Terms of Reference
   sufficiently clarify the deliverables for the Pilot Holistic Review?
   4. Do you support the next steps for the Pilot Holistic Review (as noted
   below)?

For more background information, Councilors are invited to listen to the
webinar
<https://community.icann.org/display/atrt/Pilot+Holistic+Review+-+Revised+Draft+Terms+of+Reference+Webinar+-+21+August+2023>
on this topic.

Deadline for feedback is *27 November 2023*.

*(ii)* *Proposed Process for the Retirement of Non-Policy Recommendations *

To implement the Board-approved Third Accountability and Transparency
Review (ATRT3)
<https://www.icann.org/resources/reviews/specific-reviews/atrt>
Recommendation 5, and considering the numerous times the ATRT3 Final Report
stresses the procedural gap of not having a process to retire approved
recommendations, ICANN org is proposing a process for the retirement of
community-developed Board-approved *non-policy* recommendations in
exceptional cases and according to specific criteria.

Non-policy recommendations refer to community recommendations developed
outside of a policy development process, such as Specific Reviews or
Cross-Community Working Groups. The process will be publicly documented in
the planning prioritization framework, and referenced in relevant
documentation, such as the revised version of the Operating Standards for
Specific Reviews.

Here, the Council will discuss the Proposed Process
<https://mm.icann.org/pipermail/council/attachments/20231003/12d244b4/DraftProcesstoRetireRecommendations-25Sept20234-0001.pdf>
and determine whether input on the proposed process is needed.

The deadline for input is *30 November 2023 *and can be sent directly to
giovanni.seppia at icann.org and alice.jansen at icann.org.

*(iii) Continuous Improvement Program Community Coordination Group
(CIP-CCG)*

The Third Accountability and Transparency Review (ATRT3) Recommendation 3.6
calls for Organizational Reviews to be evolved into a Continuous
Improvement Program (CIP). The recommendation to create a Continuous
Improvement Program states that ICANN org shall work with each Supporting
Organization (SO), Advisory Committee (AC) and their stakeholder groups,
and the Nominating Committee (NomCom) to establish a Continuous Improvement
Program. It will include an annual satisfaction survey of
members/participants, and a regular assessment, including a summary of
continuous improvements published at least every three years.

As the ICANN Community considers the implementation of ATRT3 Recommendation
3.6 as it relates to each community structure and for the ICANN Community
overall, the CIP Community Coordination Group is intended to serve as a
forum to exchange best practices, lessons learned, as well as for sharing
information and progress related to already existing community continuous
improvement activities. The representatives in the CIP-CCG will share best
practices and collaborate on community-wide implementation of ATRT3
Recommendation 3.6, while relaying information back to their constituencies
to inform the process and voice decisions.



ICANN org plans to proceed with the approach outlined in its letter
<https://gnso.icann.org/sites/default/files/policy/2023/correspondence/gurnick-to-soac-leadership-et-al-13oct23-en.pdf>
by the end of November; however, if there are objections, concerns, or
further feedback/questions, input should be directed to
larisa.gurnick at icann.org and evin.erdogdu at icann.org and is due by *30
November 2023*.



Here, the Council will discuss if it would like to provide further feedback
on the three above topics.

5.1 ? Introduction of topic (Greg DiBiase, Vice-Chair of the GNSO Council)

5.2 - Discussion

5.3 ? Next steps



*Item 6: COUNCIL DISCUSSION - GNSO Liaison to the Governmental Advisory
Committee (GAC) Annual Report (10 minutes)*

The GNSO Liaison to the GAC role was first piloted from 1 July 2014 to 30
June 2016 as part of a broader initiative of the GAC-GNSO Consultation
Group to facilitate early engagement of the GAC in GNSO policy development
activities. Due to the success of the pilot, the GNSO Liaison to the GAC is
now a permanent role and an integral part of communications between the GAC
and GNSO.

The Liaison is primarily responsible for providing timely updates to the
GAC on GNSO policy development activities in order to complement the
existing notification processes; the Liaison is also a resource for
answering questions in relation to these (GNSO) activities that GAC members
may have. Furthermore, the Liaison is responsible for providing the GNSO
Council with regular updates on progress, including on GAC activities,
specifically in so far as these relate to issues of interest to the GNSO.
The objective of the liaison mechanism, in combination with other
mechanisms and early engagement tools, is to facilitate effective early
engagement of the GAC and assist with the flow of information between the
GAC and the GNSO.

The Liaison is responsible for delivering to the Council an annual report,
which includes updates on relevant engagement activities and progress.



Here, the Council will receive a presentation on the annual report
<https://gnso.icann.org/sites/default/files/policy/2023/correspondence/newman-to-gnso-council-et-al-09oct23-en.pdf>
from the Liaison.

6.1 ? Introduction of topic (Jeff Neuman, GNSO Liaison to the GAC)

6.2 ? Council discussion

6.3 ? Next steps



*Item 7: COUNCIL DISCUSSION - Diacritics Issue in Latin Script (20 minutes)*

PointQu?bec, CORE Association, and the At-Large Advisory Committee raised
an issue to the GNSO Council attention with regard to the challenge
affecting future applied-for strings in the Latin script containing
diacritics that may be confusingly similar to ASCII strings and are
non-variants.

For background, an applied-for IDN gTLD string in the Latin script
containing diacritics, which is NOT an allocatable variant label of the
base ASCII string (existing or applied-for) according to RZ-LGR, is widely
recognized by users as its ?equivalence? and may be determined to be
confusingly similar (i.e., in which case, it would not pass the String
Similarity Review).

One notable example of this problem known to the ICANN community is the
string ?qu?bec?. PointQu?bec Inc, the Registry of .quebec, has long held an
interest in applying for this string, but it may face challenges obtaining
it. PointQu?bec regards the string ?.qu?bec? a necessity for serving the
French speaking community in Quebec, Canada. Quebec is the only province in
Canada whose sole official language is French; 71.2% of Quebecers are first
language francophones. In the 2012 round, PointQu?bec was advised not to
apply for ?.qu?bec? due to considerations for technical readiness and
financial predictability for an IDN gTLD. Hence it applied for the ASCII
string without diacritics ?.quebec? first, but has been waiting to submit
an application for the IDN string in the next round.

A similar problem could happen to other existing Registries that currently
manage ASCII gTLDs but may wish to apply for their IDN equivalence that are
not deemed as allocatable variant labels according to the RZ-LGR. Future
applicants may also be affected by this challenge.

To consider the development of an exception procedure for handling the
consequence of String Similarity Review and create a potential path for
future applications such as the ?.qu?bec? string, a GNSO Policy Development
Process is likely the necessary avenue to do so. Understanding the
seriousness of the issue and the potential harm to the interests or needs
of the intended language committees, the GNSO Council agrees that
requesting an Issue Report to thoroughly research and scope the problem is
the appropriate step forward. The Issue Report will serve as the basis for
launching a dedicated PDP on this topic, should the GNSO Council consider
this path in the future.



Here, this briefing will serve the purpose of the initial issue
identification and scoping in preparation for the Council?s consideration
for requesting the Issue Report.

7.1 ? Introduction of topic (Sebastien Ducos, GNSO Council Chair)

7.2 ? Council discussion

7.3 ? Next steps



*Item 8: ANY OTHER BUSINESS (30 minutes)*

8.1 ? Farewell to outgoing Councilors

8.2 ? Update - Open Contracted Party House DNS Abuse Calls (Greg DiBiase)

8.3 ? GNSO Framework for Continuous Improvement Pilot Review (Manju Chen)

8.4 ? Open microphone (Continuation of anniversary session discussion /
input)





_______________________________

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

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

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

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



*References for Coordinated Universal Time of 11:00 UTC*

Local time between March and October in the NORTHERN hemisphere

See https://www.timeanddate.com/time/change/ for Dates for Daylight Saving
Time and Clock Changes

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

California, USA (PDT) UTC-7  04:00

San Jos?, Costa Rica (CDT) UTC-6  05:00

New York/Washington DC, USA (EDT) UTC-4  07:00

Buenos Aires, Argentina (ART) UTC-3  08:00

Kinshasa, Democratic Republic of Congo (WAT) UTC+1 12:00

Paris, France (CEST) UTC+2   13:00

Moscow, Russia (MSK) UTC+3  14:00

Singapore (SGT) UTC+8 19:00

Melbourne, Australia (AEST) UTC+11 22:00

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

US and Canada: DST starts on Sunday 12 March 2023 (with exceptions)

European countries: DST starts on Sunday 26 March 2023 (with exceptions)

DST ends on Sunday 29 October 2023 for most European countries

DST ends on Sunday 05 November 2023 for most of the US and Canada

Some parts of Australia: DST ends on Sunday 02 April 2023

Some parts of Australia: DST starts on Sunday 01 October 2023

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

For other places see http://www.timeanddate.com and
https://tinyurl.com/ycktn6se





Part 2



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



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

For convenience:

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



GNSO Council meeting held in Hamburg, Germany 15:15-15:45 CEST:
https://tinyurl.com/3t7zh8f6



Coordinated Universal Time: 13:15-13:45 UTC



06:15 Los Angeles; 09:15 Washington DC; 14:15 London; 15:15 Paris; 16:15
Moscow; (Thursday) 00:15 Melbourne



*GNSO Council Meeting Remote Participation:** (TBD)*

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

___________________________________

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



1.1 - Roll Call



1.2 - Statements of Interest



INCOMING COUNCILORS:



Jennifer Chung: SOI <https://community.icann.org/x/6AOuAg> Registries
Stakeholder Group (RySG)

Lawrence Olawale-Roberts: SOI <https://community.icann.org/x/PAF1Aw>
Commercial Stakeholder Group (CSG - BC)

Damon Ashcroft: SOI <https://community.icann.org/x/WEqAAw> Commercial
Stakeholder Group (CSG - IPC)

Peter Akinremi: SOI <https://community.icann.org/x/squjBg> Non-commercial
Stakeholder Group (NCSG)



1.3 - Review / Amend Agenda



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



One nomination was received for this position from Gregory DiBiase of the
Contracted Party House. Gregory circulated his candidate statement
<https://gnso.icann.org/sites/default/files/file/field-file-attach/dibiase-statement-07oct23-en.pdf>
to the GNSO Council on 5 October 2023. Here the GNSO Council will proceed
to hold the election for its Chair for 2022-2023, according to the GNSO
Operating Procedures (note Section 2.2 of the GNSO Operating Procedures on
Officer Elections: Chair and Vice-Chairs (see Appendix 1 below)).



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

Non-Contracted Party House - TBD

Contracted Party House - TBD



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



4.1 - TBD



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

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

Officer Elections:  Chair and Vice-Chairs



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

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


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


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


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


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


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


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



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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Appendix 1 GNSO Council Voting Results table

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

*4.4 Absentee Voting*

4.1.1        Applicability



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

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



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

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

4.1.4    Absentee balloting does not affect quorum requirements.







_______________________________________________
council mailing list
council at gnso.icann.org
https://mm.icann.org/mailman/listinfo/council

_______________________________________________
By submitting your personal data, you consent to the processing of your
personal data for purposes of subscribing to this mailing list accordance
with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
the website Terms of Service (https://www.icann.org/privacy/tos). You can
visit the Mailman link above to change your membership status or
configuration, including unsubscribing, setting digest-style delivery or
disabling delivery altogether (e.g., for a vacation), and so on.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20231022/e1654887/attachment.htm>

From julf at julf.com  Wed Oct 25 15:27:49 2023
From: julf at julf.com (Johan Helsingius)
Date: Wed, 25 Oct 2023 14:27:49 +0200
Subject: [NCSG-PC] Fwd: [GNSO-SG-C-Leadership] Regarding the Formation of a
 CIP-CCG
In-Reply-To: <6C115E39-A0D5-4923-9587-61F215B33E79@icann.org>
References: <6C115E39-A0D5-4923-9587-61F215B33E79@icann.org>
Message-ID: <cb8b32ff-14bf-49f7-8669-f02ba2d4cee8@julf.com>




-------- Forwarded Message --------
Subject: 	[GNSO-SG-C-Leadership] Regarding the Formation of a CIP-CCG
Date: 	Wed, 25 Oct 2023 09:48:02 +0000
From: 	Alperen Eken <alperen.eken at icann.org>
To: 	gnso-sg-c-leadership at icann.org <gnso-sg-c-leadership at icann.org>
CC: 	Evin Erdogdu <evin.erdogdu at icann.org>



Dear Stakeholder Group and Constituency Leaders,

On behalf of the ICANN organization Review Support and Accountability 
team, I reached out to leadership of the ICANN Supporting Organizations 
(SOs) and Advisory Committees (ACs) on 13 October 2023 to plan for 
implementation of the Third Accountability and Transparency Review 
(ATRT3) Recommendation 3.6, to evolve Organizational Reviews into a 
Continuous Improvement Program (CIP).

The GNSO Council will discuss this item today during their first 
afternoon session. I am reaching out to you today to inform you of the 
attached proposed Terms of Reference for a CIP Community Coordination 
Group and a full letter from ICANN Review Support and Accountability 
team as they were shared with SO/AC Chairs recently. ICANN org proposes 
the formation of a CIP-CCG to convene in December 2023, with the goal of 
developing a framework for implementation of ATRT3 Recommendation 3.6.

We will be looking forward to having some representatives with 
familiarity with Organizational Reviews, but also representatives with 
knowledge of continuous improvement work outside of ICANN; those that 
can contribute new and innovative ideas for improving the effectiveness 
and the accountability of the different ICANN structures. There is the 
importance of striking a balance between representatives with deep ICANN 
experience, and those that bring new perspectives.

The next step is to proceed with this approach by the end of Novemberas 
mentioned in the letter. We will be happy to address any question or 
input that your organizations? members may have by then, and invite you 
to submit themto larisa.gurnick at icann.org 
<mailto:larisa.gurnick at icann.org>and evin.erdogdu at icann.org 
<mailto:evin.erdogdu at icann.org>. For transparency of the process, input 
received will be posted on a community page 
athttps://community.icann.org/x/WJRME <https://community.icann.org/x/WJRME>.

As indicated, we are happy to join any discussions you may have on this 
topic at the forthcoming ICANN meeting or at any other time.

Thank you for your time,

*-On behalf of **Reviews Support and Accountability*

Alp Eken

Policy Development Support Senior Specialist

Internet Corporation for Assigned Names and Numbers (ICANN)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CIP Community Coordination Group (CIP-CCG) Terms of Reference.pdf
Type: application/pdf
Size: 70771 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20231025/b69b77de/attachment.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SOAC Leadership Email (CIP-CCG), 13 October 2023.pdf
Type: application/pdf
Size: 199311 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20231025/b69b77de/attachment-0001.pdf>
-------------- next part --------------
_______________________________________________
GNSO-SG-C-Leadership mailing list
GNSO-SG-C-Leadership at icann.org
https://mm.icann.org/mailman/listinfo/gnso-sg-c-leadership

_______________________________________________
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.