From stephanie at digitaldiscretion.ca  Sat Jun  1 13:30:44 2024
From: stephanie at digitaldiscretion.ca (Stephanie E Perrin)
Date: Sat, 1 Jun 2024 06:30:44 -0400
Subject: [NCSG-PC] Fwd: NomCom changes
In-Reply-To: <aa680b0b-ee62-4297-a704-da8f03cb43ba@julf.com>
References: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
 <aa680b0b-ee62-4297-a704-da8f03cb43ba@julf.com>
Message-ID: <f1f28108-04d0-4a7f-8f9b-c5d038d4582c@digitaldiscretion.ca>

Well they sure didnt give us long to think about that one....

Seems ok in our case.

cheers SP

On 2024-05-31 1:56 pm, Johan Helsingius via NCSG-PC wrote:
>
>
>
> -------- Forwarded Message --------
> Subject:???? NomCom changes
> Date:???? Fri, 31 May 2024 14:41:19 +0000
> From:???? DiBiase, Gregory <dibiase at amazon.com>
> To:???? aheineman at godaddy.com <aheineman at godaddy.com>, Lori Schulman 
> <lschulman at inta.org>, Cole, Mason (POR) <MCole at perkinscoie.com>, Johan 
> Helsingius <julf at Julf.com>, sdemetriou at verisign.com 
> <sdemetriou at verisign.com>, philippe.fouquart at orange.com 
> <philippe.fouquart at orange.com>
> CC:???? Steve Chan <steve.chan at icann.org>, gnso-secs at icann.org 
> <gnso-secs at icann.org>
>
>
>
> Dear Ashley, Julf, Lori, Mason, Philippe, and Samantha,
>
> I am writing to you all in your roles as Chairs of Stakeholder Groups 
> or Constituencies that appoint delegates to ICANN?s Nominating 
> Committee (NomCom).
>
> You may recall that the NomCom2 Review produced 27 recommendations, 
> several of which relate to the composition and terms of the NomCom. In 
> order to effectuate these particular recommendations, the ICANN Board 
> approved Standard Bylaws Amendments in Articles 8, 12, and 27.
>
> The Bylaws amendments made no change to the number and nature of 
> delegates from the GNSO (i.e., 1 each from the RySG, RrSG, ISPCP, IPC, 
> NCSG, and 2 from the BC), though the length of terms were extended to 
> two years (see Section 8.3 of the Bylaws). However, from Article 27, 
> in order to, ?effectuate the introduction of the two-year terms and 
> support the goal of staggering delegate terms??, three of the GNSO 
> delegates shall serve a one-year term. ARTICLE 27 TRANSITION ARTICLE 
> states that the GNSO is responsible for determining which three of the 
> seven delegates shall initially serve one-year terms.
>
> Unfortunately, no guidance was provided on how to identify the three 
> of seven GNSO delegates to serve one-year terms. For reference, the 
> ALAC was also in the position of having to identify a subset of 
> delegates to serve one-year terms. They elected to rely on random 
> selection during a live call.
>
> The GNSO may want to rely on a similarly simple approach. An important 
> point in considering the approach is that the level of representation 
> on the NomCom is not affected by the term-length. However, the SG/Cs 
> with one-year terms will have to replace those delegates after one 
> year rather than two.
>
> *Question: Do you believe there would be any objections from your 
> groups, and potentially delegates that you have already identified, to 
> proceeding with a simple path forward in which we randomly select 
> three of seven GNSO delegates to serve one-year terms?*
>
> If you believe that there may be concerns (e.g., we may want to avoid 
> having the one-year terms concentrated in particular areas), please 
> share them with Council leadership no later than 31 May 2024.
>
> If however there are no concerns, Council leadership can perform the 
> random selection process with staff or if you prefer, on a Zoom call 
> with all of you.
>
> Thanks,
>
> Greg DiBiase, GNSO Chair
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc


From julf at julf.com  Sat Jun  1 14:07:05 2024
From: julf at julf.com (Johan Helsingius)
Date: Sat, 1 Jun 2024 13:07:05 +0200
Subject: [NCSG-PC] Fwd: NomCom changes
In-Reply-To: <f1f28108-04d0-4a7f-8f9b-c5d038d4582c@digitaldiscretion.ca>
References: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
 <aa680b0b-ee62-4297-a704-da8f03cb43ba@julf.com>
 <f1f28108-04d0-4a7f-8f9b-c5d038d4582c@digitaldiscretion.ca>
Message-ID: <a56b2543-cf7b-4601-8ac2-142e22dd499c@julf.com>

 From Greg: Hi All- fixing small typo below.  Feedback is requested by
Council leadership no later than 5 June 2024 (not 31 May).

	Julf

On 01/06/2024 12:30, Stephanie E Perrin via NCSG-PC wrote:
> Well they sure didnt give us long to think about that one....
> 
> Seems ok in our case.
> 
> cheers SP
> 
> On 2024-05-31 1:56 pm, Johan Helsingius via NCSG-PC wrote:
>>
>>
>>
>> -------- Forwarded Message --------
>> Subject:???? NomCom changes
>> Date:???? Fri, 31 May 2024 14:41:19 +0000
>> From:???? DiBiase, Gregory <dibiase at amazon.com>
>> To:???? aheineman at godaddy.com <aheineman at godaddy.com>, Lori Schulman 
>> <lschulman at inta.org>, Cole, Mason (POR) <MCole at perkinscoie.com>, Johan 
>> Helsingius <julf at Julf.com>, sdemetriou at verisign.com 
>> <sdemetriou at verisign.com>, philippe.fouquart at orange.com 
>> <philippe.fouquart at orange.com>
>> CC:???? Steve Chan <steve.chan at icann.org>, gnso-secs at icann.org 
>> <gnso-secs at icann.org>
>>
>>
>>
>> Dear Ashley, Julf, Lori, Mason, Philippe, and Samantha,
>>
>> I am writing to you all in your roles as Chairs of Stakeholder Groups 
>> or Constituencies that appoint delegates to ICANN?s Nominating 
>> Committee (NomCom).
>>
>> You may recall that the NomCom2 Review produced 27 recommendations, 
>> several of which relate to the composition and terms of the NomCom. In 
>> order to effectuate these particular recommendations, the ICANN Board 
>> approved Standard Bylaws Amendments in Articles 8, 12, and 27.
>>
>> The Bylaws amendments made no change to the number and nature of 
>> delegates from the GNSO (i.e., 1 each from the RySG, RrSG, ISPCP, IPC, 
>> NCSG, and 2 from the BC), though the length of terms were extended to 
>> two years (see Section 8.3 of the Bylaws). However, from Article 27, 
>> in order to, ?effectuate the introduction of the two-year terms and 
>> support the goal of staggering delegate terms??, three of the GNSO 
>> delegates shall serve a one-year term. ARTICLE 27 TRANSITION ARTICLE 
>> states that the GNSO is responsible for determining which three of the 
>> seven delegates shall initially serve one-year terms.
>>
>> Unfortunately, no guidance was provided on how to identify the three 
>> of seven GNSO delegates to serve one-year terms. For reference, the 
>> ALAC was also in the position of having to identify a subset of 
>> delegates to serve one-year terms. They elected to rely on random 
>> selection during a live call.
>>
>> The GNSO may want to rely on a similarly simple approach. An important 
>> point in considering the approach is that the level of representation 
>> on the NomCom is not affected by the term-length. However, the SG/Cs 
>> with one-year terms will have to replace those delegates after one 
>> year rather than two.
>>
>> *Question: Do you believe there would be any objections from your 
>> groups, and potentially delegates that you have already identified, to 
>> proceeding with a simple path forward in which we randomly select 
>> three of seven GNSO delegates to serve one-year terms?*
>>
>> If you believe that there may be concerns (e.g., we may want to avoid 
>> having the one-year terms concentrated in particular areas), please 
>> share them with Council leadership no later than 31 May 2024.
>>
>> If however there are no concerns, Council leadership can perform the 
>> random selection process with staff or if you prefer, on a Zoom call 
>> with all of you.
>>
>> Thanks,
>>
>> Greg DiBiase, GNSO Chair
>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc


From jumaropi at yahoo.com  Sat Jun  1 20:26:41 2024
From: jumaropi at yahoo.com (Juan Manuel Rojas)
Date: Sat, 1 Jun 2024 17:26:41 +0000 (UTC)
Subject: [NCSG-PC] Fwd: NomCom changes
In-Reply-To: <a56b2543-cf7b-4601-8ac2-142e22dd499c@julf.com>
References: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
 <aa680b0b-ee62-4297-a704-da8f03cb43ba@julf.com>
 <f1f28108-04d0-4a7f-8f9b-c5d038d4582c@digitaldiscretion.ca>
 <a56b2543-cf7b-4601-8ac2-142e22dd499c@julf.com>
Message-ID: <1524075964.360208.1717262801078@mail.yahoo.com>

 Hi Julf and all,
I think the rotation from two years to one should apply to constituencies that have two representatives on the NomCom, such as the BC. We only have one seat, and it could add too much complexity to our election process to include one more position, despite this position being appointed in our case.

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

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

Cel. +57 301 743 56 00
Instagram: jmanurojas

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




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

    El s?bado, 1 de junio de 2024, 06:07:16 a.?m. GMT-5, Johan Helsingius via NCSG-PC <ncsg-pc at lists.ncsg.is> escribi?:  
 
  From Greg: Hi All- fixing small typo below.? Feedback is requested by
Council leadership no later than 5 June 2024 (not 31 May).

??? Julf

On 01/06/2024 12:30, Stephanie E Perrin via NCSG-PC wrote:
> Well they sure didnt give us long to think about that one....
> 
> Seems ok in our case.
> 
> cheers SP
> 
> On 2024-05-31 1:56 pm, Johan Helsingius via NCSG-PC wrote:
>>
>>
>>
>> -------- Forwarded Message --------
>> Subject:???? NomCom changes
>> Date:???? Fri, 31 May 2024 14:41:19 +0000
>> From:???? DiBiase, Gregory <dibiase at amazon.com>
>> To:???? aheineman at godaddy.com <aheineman at godaddy.com>, Lori Schulman 
>> <lschulman at inta.org>, Cole, Mason (POR) <MCole at perkinscoie.com>, Johan 
>> Helsingius <julf at Julf.com>, sdemetriou at verisign.com 
>> <sdemetriou at verisign.com>, philippe.fouquart at orange.com 
>> <philippe.fouquart at orange.com>
>> CC:???? Steve Chan <steve.chan at icann.org>, gnso-secs at icann.org 
>> <gnso-secs at icann.org>
>>
>>
>>
>> Dear Ashley, Julf, Lori, Mason, Philippe, and Samantha,
>>
>> I am writing to you all in your roles as Chairs of Stakeholder Groups 
>> or Constituencies that appoint delegates to ICANN?s Nominating 
>> Committee (NomCom).
>>
>> You may recall that the NomCom2 Review produced 27 recommendations, 
>> several of which relate to the composition and terms of the NomCom. In 
>> order to effectuate these particular recommendations, the ICANN Board 
>> approved Standard Bylaws Amendments in Articles 8, 12, and 27.
>>
>> The Bylaws amendments made no change to the number and nature of 
>> delegates from the GNSO (i.e., 1 each from the RySG, RrSG, ISPCP, IPC, 
>> NCSG, and 2 from the BC), though the length of terms were extended to 
>> two years (see Section 8.3 of the Bylaws). However, from Article 27, 
>> in order to, ?effectuate the introduction of the two-year terms and 
>> support the goal of staggering delegate terms??, three of the GNSO 
>> delegates shall serve a one-year term. ARTICLE 27 TRANSITION ARTICLE 
>> states that the GNSO is responsible for determining which three of the 
>> seven delegates shall initially serve one-year terms.
>>
>> Unfortunately, no guidance was provided on how to identify the three 
>> of seven GNSO delegates to serve one-year terms. For reference, the 
>> ALAC was also in the position of having to identify a subset of 
>> delegates to serve one-year terms. They elected to rely on random 
>> selection during a live call.
>>
>> The GNSO may want to rely on a similarly simple approach. An important 
>> point in considering the approach is that the level of representation 
>> on the NomCom is not affected by the term-length. However, the SG/Cs 
>> with one-year terms will have to replace those delegates after one 
>> year rather than two.
>>
>> *Question: Do you believe there would be any objections from your 
>> groups, and potentially delegates that you have already identified, to 
>> proceeding with a simple path forward in which we randomly select 
>> three of seven GNSO delegates to serve one-year terms?*
>>
>> If you believe that there may be concerns (e.g., we may want to avoid 
>> having the one-year terms concentrated in particular areas), please 
>> share them with Council leadership no later than 31 May 2024.
>>
>> If however there are no concerns, Council leadership can perform the 
>> random selection process with staff or if you prefer, on a Zoom call 
>> with all of you.
>>
>> Thanks,
>>
>> Greg DiBiase, GNSO Chair
>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
_______________________________________________
NCSG-PC mailing list
NCSG-PC at lists.ncsg.is
https://lists.ncsg.is/mailman/listinfo/ncsg-pc
  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240601/8fade783/attachment.htm>

From mesumbeslin at gmail.com  Sun Jun  2 00:34:10 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Sun, 2 Jun 2024 07:34:10 +1000
Subject: [NCSG-PC] Fwd: NomCom changes
In-Reply-To: <1524075964.360208.1717262801078@mail.yahoo.com>
References: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
 <aa680b0b-ee62-4297-a704-da8f03cb43ba@julf.com>
 <f1f28108-04d0-4a7f-8f9b-c5d038d4582c@digitaldiscretion.ca>
 <a56b2543-cf7b-4601-8ac2-142e22dd499c@julf.com>
 <1524075964.360208.1717262801078@mail.yahoo.com>
Message-ID: <CAM8DdeWj6-J=s5JEWisWi7qm-9rxaSGuHnrnQVeh+trZmDwjBQ@mail.gmail.com>

Hi Juan,

It might just be my brain having a slow start, but I didn't understand the
complexity you described is introduces to NCSG.

@Johan Helsingius <julf at julf.com> I feel like we should include the EC in
this discussion. I believe that they would want to be part of the decision
making?

Warmly,
Tomslin

On Sun, 2 June 2024, 03:26 Juan Manuel Rojas via NCSG-PC, <
ncsg-pc at lists.ncsg.is> wrote:

> Hi Julf and all,
>
> I think the rotation from two years to one should apply to constituencies
> that have two representatives on the NomCom, such as the BC. We only have
> one seat, and it could add too much complexity to our election process to
> include one more position, despite this position being appointed in our
> case.
>
>
> *JUAN MANUEL ROJAS, M.Sc.*
> Director - MINKA DIGITAL Colombia
> NPOC Chair - NCSG/GNSO
> M.Sc. Information Technology
>
> Registered Linux User No.*533108.*
> http://www.jmanurojas.com
>
>
> *Cel. +57 301 743 56 00Instagram: jmanurojas*
>
> -----BEGIN GEEK CODE BLOCK-----
> Version: 3.1
> GIT d- s: a+ C+++ UL P+ L+++ !E !W+++ !N !o K+++ w-- !O M- V PS+ PE-- Y+
> PGP+ t+ 5 X++ R tv+ b+ DI D G e+++(+++)>+++ h+ r++ y+
> ------END GEEK CODE BLOCK------
>
>
>
>
>
>
>
>
> El s?bado, 1 de junio de 2024, 06:07:16 a. m. GMT-5, Johan Helsingius via
> NCSG-PC <ncsg-pc at lists.ncsg.is> escribi?:
>
>
> From Greg: Hi All- fixing small typo below.  Feedback is requested by
> Council leadership no later than 5 June 2024 (not 31 May).
>
>     Julf
>
> On 01/06/2024 12:30, Stephanie E Perrin via NCSG-PC wrote:
> > Well they sure didnt give us long to think about that one....
> >
> > Seems ok in our case.
> >
> > cheers SP
> >
> > On 2024-05-31 1:56 pm, Johan Helsingius via NCSG-PC wrote:
> >>
> >>
> >>
> >> -------- Forwarded Message --------
> >> Subject:     NomCom changes
> >> Date:     Fri, 31 May 2024 14:41:19 +0000
> >> From:     DiBiase, Gregory <dibiase at amazon.com>
> >> To:     aheineman at godaddy.com <aheineman at godaddy.com>, Lori Schulman
> >> <lschulman at inta.org>, Cole, Mason (POR) <MCole at perkinscoie.com>, Johan
> >> Helsingius <julf at Julf.com>, sdemetriou at verisign.com
> >> <sdemetriou at verisign.com>, philippe.fouquart at orange.com
> >> <philippe.fouquart at orange.com>
> >> CC:     Steve Chan <steve.chan at icann.org>, gnso-secs at icann.org
> >> <gnso-secs at icann.org>
> >>
> >>
> >>
> >> Dear Ashley, Julf, Lori, Mason, Philippe, and Samantha,
> >>
> >> I am writing to you all in your roles as Chairs of Stakeholder Groups
> >> or Constituencies that appoint delegates to ICANN?s Nominating
> >> Committee (NomCom).
> >>
> >> You may recall that the NomCom2 Review produced 27 recommendations,
> >> several of which relate to the composition and terms of the NomCom. In
> >> order to effectuate these particular recommendations, the ICANN Board
> >> approved Standard Bylaws Amendments in Articles 8, 12, and 27.
> >>
> >> The Bylaws amendments made no change to the number and nature of
> >> delegates from the GNSO (i.e., 1 each from the RySG, RrSG, ISPCP, IPC,
> >> NCSG, and 2 from the BC), though the length of terms were extended to
> >> two years (see Section 8.3 of the Bylaws). However, from Article 27,
> >> in order to, ?effectuate the introduction of the two-year terms and
> >> support the goal of staggering delegate terms??, three of the GNSO
> >> delegates shall serve a one-year term. ARTICLE 27 TRANSITION ARTICLE
> >> states that the GNSO is responsible for determining which three of the
> >> seven delegates shall initially serve one-year terms.
> >>
> >> Unfortunately, no guidance was provided on how to identify the three
> >> of seven GNSO delegates to serve one-year terms. For reference, the
> >> ALAC was also in the position of having to identify a subset of
> >> delegates to serve one-year terms. They elected to rely on random
> >> selection during a live call.
> >>
> >> The GNSO may want to rely on a similarly simple approach. An important
> >> point in considering the approach is that the level of representation
> >> on the NomCom is not affected by the term-length. However, the SG/Cs
> >> with one-year terms will have to replace those delegates after one
> >> year rather than two.
> >>
> >> *Question: Do you believe there would be any objections from your
> >> groups, and potentially delegates that you have already identified, to
> >> proceeding with a simple path forward in which we randomly select
> >> three of seven GNSO delegates to serve one-year terms?*
> >>
> >> If you believe that there may be concerns (e.g., we may want to avoid
> >> having the one-year terms concentrated in particular areas), please
> >> share them with Council leadership no later than 31 May 2024.
> >>
> >> If however there are no concerns, Council leadership can perform the
> >> random selection process with staff or if you prefer, on a Zoom call
> >> with all of you.
> >>
> >> Thanks,
> >>
> >> Greg DiBiase, GNSO Chair
> >>
> >> _______________________________________________
> >> NCSG-PC mailing list
> >> NCSG-PC at lists.ncsg.is
> >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
> > _______________________________________________
> > NCSG-PC mailing list
> > NCSG-PC at lists.ncsg.is
> > https://lists.ncsg.is/mailman/listinfo/ncsg-pc
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
> _______________________________________________
> 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/20240602/8921aba9/attachment.htm>

From mamattah.raymond at gmail.com  Sun Jun  2 10:27:44 2024
From: mamattah.raymond at gmail.com (Raymond Mamattah)
Date: Sun, 2 Jun 2024 07:27:44 +0000
Subject: [NCSG-PC] Fwd: NomCom changes
In-Reply-To: <CAM8DdeWj6-J=s5JEWisWi7qm-9rxaSGuHnrnQVeh+trZmDwjBQ@mail.gmail.com>
References: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
 <aa680b0b-ee62-4297-a704-da8f03cb43ba@julf.com>
 <f1f28108-04d0-4a7f-8f9b-c5d038d4582c@digitaldiscretion.ca>
 <a56b2543-cf7b-4601-8ac2-142e22dd499c@julf.com>
 <1524075964.360208.1717262801078@mail.yahoo.com>
 <CAM8DdeWj6-J=s5JEWisWi7qm-9rxaSGuHnrnQVeh+trZmDwjBQ@mail.gmail.com>
Message-ID: <CAEGCQGtdQO0Xpom9SNTv+yjvvaQbjfWzp8PMpcoSUSVE37Y2ng@mail.gmail.com>

Hello,

Below are what I know:

1. The one-year tenure starting from the end of the AGM is not a permanent
thing.

2. At the end of the one-year tenure, all constituencies will have a
two-year tenure. The *ICANN Nominating Committee (NomCom) Operating
Procedures
<https://www.icann.org/resources/pages/governance/bylaws-en/#article8> *Section
8.3. section A states:

"The term for each voting delegate shall be a *two-year term*. No
individual may serve as a delegate for more than two terms. In addition, no
individual may serve in consecutive terms, regardless of the entity
selecting them to the Nominating Committee. An individual will only be
eligible to serve a second term as a delegate on the Nominating committee
if a minimum of two years has elapsed between the end of their first term
and the beginning of the term for which they are being selected."

3. I suggest a simple ballot be done to determine those who will serve the
one-year tenure, just as the other constituencies did.

Regards,
Raymond Mamattah
[image: linkedin]
<https://www.linkedin.com/in/raymond-selorm-mamattah/> [image:
facebook] <https://www.facebook.com/selorm.mamattah> [image: twitter]
<https://twitter.com/RMamattah>
Accra, Ghana


On Sat, Jun 1, 2024 at 9:53?PM Tomslin Samme-Nlar <mesumbeslin at gmail.com>
wrote:

> Hi Juan,
>
> It might just be my brain having a slow start, but I didn't understand the
> complexity you described is introduces to NCSG.
>
> @Johan Helsingius <julf at julf.com> I feel like we should include the EC in
> this discussion. I believe that they would want to be part of the decision
> making?
>
> Warmly,
> Tomslin
>
> On Sun, 2 June 2024, 03:26 Juan Manuel Rojas via NCSG-PC, <
> ncsg-pc at lists.ncsg.is> wrote:
>
>> Hi Julf and all,
>>
>> I think the rotation from two years to one should apply to constituencies
>> that have two representatives on the NomCom, such as the BC. We only have
>> one seat, and it could add too much complexity to our election process to
>> include one more position, despite this position being appointed in our
>> case.
>>
>>
>> *JUAN MANUEL ROJAS, M.Sc.*
>> Director - MINKA DIGITAL Colombia
>> NPOC Chair - NCSG/GNSO
>> M.Sc. Information Technology
>>
>> Registered Linux User No.*533108.*
>> http://www.jmanurojas.com
>>
>>
>> *Cel. +57 301 743 56 00Instagram: jmanurojas*
>>
>> -----BEGIN GEEK CODE BLOCK-----
>> Version: 3.1
>> GIT d- s: a+ C+++ UL P+ L+++ !E !W+++ !N !o K+++ w-- !O M- V PS+ PE-- Y+
>> PGP+ t+ 5 X++ R tv+ b+ DI D G e+++(+++)>+++ h+ r++ y+
>> ------END GEEK CODE BLOCK------
>>
>>
>>
>>
>>
>>
>>
>>
>> El s?bado, 1 de junio de 2024, 06:07:16 a. m. GMT-5, Johan Helsingius via
>> NCSG-PC <ncsg-pc at lists.ncsg.is> escribi?:
>>
>>
>> From Greg: Hi All- fixing small typo below.  Feedback is requested by
>> Council leadership no later than 5 June 2024 (not 31 May).
>>
>>     Julf
>>
>> On 01/06/2024 12:30, Stephanie E Perrin via NCSG-PC wrote:
>> > Well they sure didnt give us long to think about that one....
>> >
>> > Seems ok in our case.
>> >
>> > cheers SP
>> >
>> > On 2024-05-31 1:56 pm, Johan Helsingius via NCSG-PC wrote:
>> >>
>> >>
>> >>
>> >> -------- Forwarded Message --------
>> >> Subject:     NomCom changes
>> >> Date:     Fri, 31 May 2024 14:41:19 +0000
>> >> From:     DiBiase, Gregory <dibiase at amazon.com>
>> >> To:     aheineman at godaddy.com <aheineman at godaddy.com>, Lori Schulman
>> >> <lschulman at inta.org>, Cole, Mason (POR) <MCole at perkinscoie.com>,
>> Johan
>> >> Helsingius <julf at Julf.com>, sdemetriou at verisign.com
>> >> <sdemetriou at verisign.com>, philippe.fouquart at orange.com
>> >> <philippe.fouquart at orange.com>
>> >> CC:     Steve Chan <steve.chan at icann.org>, gnso-secs at icann.org
>> >> <gnso-secs at icann.org>
>> >>
>> >>
>> >>
>> >> Dear Ashley, Julf, Lori, Mason, Philippe, and Samantha,
>> >>
>> >> I am writing to you all in your roles as Chairs of Stakeholder Groups
>> >> or Constituencies that appoint delegates to ICANN?s Nominating
>> >> Committee (NomCom).
>> >>
>> >> You may recall that the NomCom2 Review produced 27 recommendations,
>> >> several of which relate to the composition and terms of the NomCom. In
>> >> order to effectuate these particular recommendations, the ICANN Board
>> >> approved Standard Bylaws Amendments in Articles 8, 12, and 27.
>> >>
>> >> The Bylaws amendments made no change to the number and nature of
>> >> delegates from the GNSO (i.e., 1 each from the RySG, RrSG, ISPCP, IPC,
>> >> NCSG, and 2 from the BC), though the length of terms were extended to
>> >> two years (see Section 8.3 of the Bylaws). However, from Article 27,
>> >> in order to, ?effectuate the introduction of the two-year terms and
>> >> support the goal of staggering delegate terms??, three of the GNSO
>> >> delegates shall serve a one-year term. ARTICLE 27 TRANSITION ARTICLE
>> >> states that the GNSO is responsible for determining which three of the
>> >> seven delegates shall initially serve one-year terms.
>> >>
>> >> Unfortunately, no guidance was provided on how to identify the three
>> >> of seven GNSO delegates to serve one-year terms. For reference, the
>> >> ALAC was also in the position of having to identify a subset of
>> >> delegates to serve one-year terms. They elected to rely on random
>> >> selection during a live call.
>> >>
>> >> The GNSO may want to rely on a similarly simple approach. An important
>> >> point in considering the approach is that the level of representation
>> >> on the NomCom is not affected by the term-length. However, the SG/Cs
>> >> with one-year terms will have to replace those delegates after one
>> >> year rather than two.
>> >>
>> >> *Question: Do you believe there would be any objections from your
>> >> groups, and potentially delegates that you have already identified, to
>> >> proceeding with a simple path forward in which we randomly select
>> >> three of seven GNSO delegates to serve one-year terms?*
>> >>
>> >> If you believe that there may be concerns (e.g., we may want to avoid
>> >> having the one-year terms concentrated in particular areas), please
>> >> share them with Council leadership no later than 31 May 2024.
>> >>
>> >> If however there are no concerns, Council leadership can perform the
>> >> random selection process with staff or if you prefer, on a Zoom call
>> >> with all of you.
>> >>
>> >> Thanks,
>> >>
>> >> Greg DiBiase, GNSO Chair
>> >>
>> >> _______________________________________________
>> >> NCSG-PC mailing list
>> >> NCSG-PC at lists.ncsg.is
>> >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
>> > _______________________________________________
>> > NCSG-PC mailing list
>> > NCSG-PC at lists.ncsg.is
>> > https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>> _______________________________________________
>> 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/20240602/6ca279c6/attachment.htm>

From julf at julf.com  Sun Jun  2 10:43:48 2024
From: julf at julf.com (Johan Helsingius)
Date: Sun, 2 Jun 2024 09:43:48 +0200
Subject: [NCSG-PC] Fwd: NomCom changes
In-Reply-To: <CAM8DdeWj6-J=s5JEWisWi7qm-9rxaSGuHnrnQVeh+trZmDwjBQ@mail.gmail.com>
References: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
 <aa680b0b-ee62-4297-a704-da8f03cb43ba@julf.com>
 <f1f28108-04d0-4a7f-8f9b-c5d038d4582c@digitaldiscretion.ca>
 <a56b2543-cf7b-4601-8ac2-142e22dd499c@julf.com>
 <1524075964.360208.1717262801078@mail.yahoo.com>
 <CAM8DdeWj6-J=s5JEWisWi7qm-9rxaSGuHnrnQVeh+trZmDwjBQ@mail.gmail.com>
Message-ID: <4d1903fb-d3e2-4b8e-8919-2c08951244de@julf.com>

On 01/06/2024 23:34, Tomslin Samme-Nlar wrote:
> @Johan Helsingius <mailto:julf at julf.com>?I feel like we should include 
> the EC in this discussion. I believe that they would want to be part of 
> the decision making?

Noted - thanks, Tomslin. Forwarded the message to the EC too.

	Julf



From mesumbeslin at gmail.com  Mon Jun  3 05:57:38 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Mon, 3 Jun 2024 12:57:38 +1000
Subject: [NCSG-PC] Fwd: NomCom changes
In-Reply-To: <4d1903fb-d3e2-4b8e-8919-2c08951244de@julf.com>
References: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
 <aa680b0b-ee62-4297-a704-da8f03cb43ba@julf.com>
 <f1f28108-04d0-4a7f-8f9b-c5d038d4582c@digitaldiscretion.ca>
 <a56b2543-cf7b-4601-8ac2-142e22dd499c@julf.com>
 <1524075964.360208.1717262801078@mail.yahoo.com>
 <CAM8DdeWj6-J=s5JEWisWi7qm-9rxaSGuHnrnQVeh+trZmDwjBQ@mail.gmail.com>
 <4d1903fb-d3e2-4b8e-8919-2c08951244de@julf.com>
Message-ID: <CAM8DdeUSToi2f0ZF3nX1Zp96nAjY07-=YmAVeXe_U_Fm0YKg-A@mail.gmail.com>

I see the issue is very lively in the EC list but unfortunately not helping
with the immediate question at hand which is:

To prevent all delegates term ending at the same time with the new term
limits, what does NCSG think about using a random selection process to
select three out of seven GNSO delegates to serve one-year terms?

Warmly,
Tomslin

On Sun, 2 June 2024, 17:43 Johan Helsingius, <julf at julf.com> wrote:

> On 01/06/2024 23:34, Tomslin Samme-Nlar wrote:
> > @Johan Helsingius <mailto:julf at julf.com> I feel like we should include
> > the EC in this discussion. I believe that they would want to be part of
> > the decision making?
>
> Noted - thanks, Tomslin. Forwarded the message to the EC too.
>
>         Julf
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240603/2d7631bb/attachment.htm>

From mesumbeslin at gmail.com  Mon Jun  3 06:00:33 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Mon, 3 Jun 2024 13:00:33 +1000
Subject: [NCSG-PC] [Call for Volunteers] Appointment of representative
 and alternate to the PPSAI IRT
In-Reply-To: <CAM8DdeWf70W_Bda-FVsM84X-PHyNw21y6AtJd3nB4V0JcLSihg@mail.gmail.com>
References: <CB52871E-374F-48BF-97D7-D184C00AD654@contoso.com>
 <ee28ed26-ea0c-4aa3-ba5f-46e9aa43bcbf@julf.com>
 <CAM8DdeUFVZ18WfoH28uMpys9dO20V=mZuTXqERZ2BYRqDerYEw@mail.gmail.com>
 <CAN1qJvAuWt0PPC7M+0SXRDmd3ksUUaoYpiY2nqsQReZG0pPz8w@mail.gmail.com>
 <130d1bc0-5408-4af3-a37b-f8a58aeeb9a3@dnrc.tech>
 <CAAjCLO20pmx4d2QixY10jcgmjSGYZdoWg-+_KEyu05qVWM9nMw@mail.gmail.com>
 <CAGSP6RQZxTgj=hR-5kHZaypzWQAkQLEBLWY2KE4QEcAHfn-CGQ@mail.gmail.com>
 <CAM8DdeWf70W_Bda-FVsM84X-PHyNw21y6AtJd3nB4V0JcLSihg@mail.gmail.com>
Message-ID: <CAM8DdeWNzdfs4HJCzEvtwC5RV2=zHg9-084xy2q1RMqrA1DS4w@mail.gmail.com>

Hi members,

I haven't heard back on this. So, I am following up to know whether the PC
should proceed with appointing a representative to the IRT or decline to.

Warmly,
Tomslin

On Tue, 28 May 2024, 09:53 Tomslin Samme-Nlar, <mesumbeslin at gmail.com>
wrote:

> Thanks for the comments @farzi, @Kathy, @Ponce and @Pedro.
>
> @Pedro, you ask an important question, "*are we ... appointing volunteers
> while we wait for the GNSO council to act or is it better to refuse to
> nominate someone for now*? ". I wait to hear what our members think.
>
> On the GNSO action side of things, Find my a brief of what has transpired
> in the council since 2019 on this topic below but I'd also like input from @Stephanie
> Perrin <stephanie.perrin at mail.utoronto.ca> who is one of the council
> liaisons to the PPSAI IRT:
>
> - As a result of potential conflicts and/or overlap of work between the
> PPSAI IRT and GDPR-related work in EPDP on Temp Spec, in March 2019,  ICANN
> org asked the GNSO Council, ?whether ICANN org should continue to delay
> public comment and implementation of PPSAI or take additional steps pending
> completion of the EPDP in consultation with the PPSAI Implementation Review
> Team (IRT).
> - Council responded to Org saying, ?*given the divergent views among
> Councilors* and considering the respective roles of ICANN Org in leading
> implementation work of consensus policy recommendations and the PPSAI IRT
> in overseeing the implementation work, the GNSO *Council considers it
> appropriate to defer the decision on this issue to ICANN org and the PPSAI
> IRT*, taking into account the various views of the SOs and ACs.?
> [emphasis added]
> - On 2 March 2021, ICANN org delivered the Wave 1.5 Report
> <https://mm.icann.org/pipermail/council/2021-March/024506.html> to the
> GNSO Council, which included a detailed analysis of the extent to which the
> EPDP Phase 1 recommendations may require modification to the PPSAI and
> Translation & Transliteration policies, which are in the policy
> implementation phase. Following review of the Wave 1.5 Report, the Council
> observed the following in its 1 July 2021 letter [gnso.icann.org]
> <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/field-file-attach/fouquart-to-lentz-01jul21-en.pdf__;!!PtGJab4!72Ceiu66uyoV0OHChjdR9frkPlBYYXnOJZ5zB8r86XzWBmEUoVf8ybKlInPdH4obWmz6r2jOJd6I6Op0U5lFnsYtCg$>
> :
>
>
>
>    - *The decision to pause the implementation of the PPSAI and
>    Translation & Transliteration policy recommendations was a decision that
>    was made by ICANN org, not the GNSO Council. As such, the Council is of the
>    view that a decision to restart the implementation activities is not within
>    the remit of the GNSO Council but for ICANN org* to make.
>    - *Should any policy issues arise during the implementation of these
>    policy recommendations, there are processes and procedures that allow the
>    Council to further consider these*, but the Council is of the view
>    that the respective Implementation Review Teams (IRTs) will be best placed
>    to identify such possible issues.
>    - The Council would also like to point to the letter
>    <https://www.icann.org/en/system/files/correspondence/namazi-to-drazek-et-al-05sep19-en.pdf>
>    that was sent to the Council in September 2019 in which it was noted that
>    ?following the completion of relevant EPDP work, ICANN org will reassess
>    the existing draft PP materials in consultation with the PPSAI IRT and
>    determine how to proceed with implementation of the Privacy and Proxy
>    Services Accreditation Program?. From a Council?s perspective this still
>    seems a relevant and timely next step.
>
> So, as you can see, the council holds the view that if there are issues
> arising in the policy as drafted during implementation, they are confident
> that the issues can be addressed with existing processes and procedures.
>
>
> Warmly,
> Tomslin
>
>
>
> On Tue, 28 May 2024 at 07:06, Pedro de Perdig?o Lana <
> pedrodeperdigaolana at gmail.com> wrote:
>
>> Hi everyone,
>>
>> Regarding the strategy on how to approach this problem, are we
>> nonetheless appointing volunteers while we wait for the GNSO council to act
>> or is it better to refuse to nominate someone for now?
>>
>> Cordially,
>>
>> *Pedro de Perdig?o Lana*
>> Lawyer <https://www.nic.br/>, GEDAI/UFPR <https://www.gedai.com.br/>
>> Researcher
>> PhD Candidate (UFPR), LLM in Business Law (UCoimbra)
>> Board Member @ CC Brasil <https://br.creativecommons.net/>, ISOC BR
>> <https://isoc.org.br/> and IODA <https://ioda.org.br/>
>> This message is restricted to the sender and recipient(s). If received by
>> mistake, please reply informing it.
>>
>>
>> Em seg., 27 de mai. de 2024 ?s 11:35, Poncelet Ileleji <
>> pileleji at jokkolabs.co> escreveu:
>>
>>> +1 kathy +1 Farzi, I can't agree more
>>>
>>> *Poncelet O. Ileleji*
>>>
>>> *Jokkolabs Banjul -  Lead / CEO*
>>> *Sait Matty Road, Bakau, Adjacent to Swedish Consulate*
>>> *KMC, The Gambia*
>>> *P O Box 4496 Bakau,KMC, The Gambia*
>>> *Skype: pons_utd*
>>> *Tel Direct Office: +220 4495115*
>>>
>>> *Tel Mobile/Whatsapp: +220 9912508*
>>>
>>> *LinkedIn: Jokkolabs Banjul*
>>> *Facebook: Jokkolabs Banjul*
>>> *Twitter: @jBanjul*
>>>
>>>
>>>
>>>
>>> On Mon, May 27, 2024 at 1:46?PM Kathy Kleiman <kathy at dnrc.tech> wrote:
>>>
>>>>  +1 to Farzi, and an Implementation Review Team (run by ICANN Staff) is
>>>> hardly the place to state that the law has gone in a completely different
>>>> direction since the original Policy was negotiated.  No one on  the ICANN
>>>> Board or Staff feels empowered to "stop this train" although it is eight
>>>> years old and badly out of date.
>>>>
>>>> *That power rests in the GNSO Council. Can we (NCSG), through our
>>>> Councilors, call for a legal review of the proposed PPSAI for problems (if
>>>> any) with its underlying legal foundation in light of the adoption of GDPR
>>>> and over half the countries of the world now following the European
>>>> "comprehensive right of privacy"? *
>>>>
>>>> Best and asking all of our current Councilors (past and future ones
>>>> too),
>>>>
>>>> Kathy
>>>> On 5/27/2024 9:26 AM, farzaneh badii wrote:
>>>>
>>>> Hi Tomslin,
>>>>
>>>> This is a bit odd. Didn?t we discuss that most of those policy
>>>> recommendations were outdated and could not be implemented? Are they hoping
>>>> that by doing the IRT we can undertake feasibility for the recommendations?
>>>>
>>>> This is why I did suggest considering time limits for implementing
>>>> policies. You can?t come up with a policy and then want to enforce it 8
>>>> years later! Especially in the technology space, that is not possible.
>>>>
>>>> Best regards
>>>>
>>>>
>>>> Farzaneh
>>>>
>>>>
>>>> On Mon, May 27, 2024 at 5:53?AM Tomslin Samme-Nlar <
>>>> mesumbeslin at gmail.com> wrote:
>>>>
>>>>> Dear members,
>>>>>
>>>>> There is a request from Org for SG/Cs to appoint a representative and
>>>>> an alternate to the PPSAI IRT. We (NCSG) had concerns with the IRT going
>>>>> ahead but as you can see, Org is still going ahead with it.
>>>>>
>>>>> NCSG is seeking a representative and an alternate. Please read below
>>>>> for details of the role of the representative and on what the IRT will be
>>>>> doing.
>>>>>
>>>>> Send your EOI to me (mesumbeslin at gmail.com) copying Julf (
>>>>> julf at julf.com) and Andrea (andrea.glandon at icann.org) no later than
>>>>> Friday May 31st 2023 for the policy committee's review.
>>>>>
>>>>> Warmly,
>>>>> Tomslin
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> -------- Forwarded Message --------
>>>>> Subject:        [GNSO-SG-C-Leadership] Appointment of representative
>>>>> and
>>>>> alternate to the PPSAI IRT
>>>>> Date:   Tue, 21 May 2024 19:59:02 +0000
>>>>> From:   Dennis Chang via GNSO-SG-C-Leadership
>>>>> <gnso-sg-c-leadership at icann.org>
>>>>> Reply-To:       Dennis Chang <dennis.chang at icann.org>
>>>>> To:     gnso-sg-c-leadership at icann.org <gnso-sg-c-leadership at icann.org
>>>>> >
>>>>> CC:     Leon Grundmann <leon.grundmann at icann.org>
>>>>>
>>>>>
>>>>>
>>>>> Dear All,
>>>>>
>>>>> Following the publication of the Call for Volunteers
>>>>> <
>>>>> https://www.icann.org/en/announcements/details/icann-seeks-volunteers-for-the-ppsai-implementation-review-team-20-05-2024-en>,
>>>>>
>>>>> the Internet Corporation for Assigned Names and Numbers (ICANN)
>>>>> organization (org) is pleased to invite you to nominate a
>>>>> representative
>>>>> and an alternate to the Proxy & Privacy Services (PPSAI) policy
>>>>> Implementation Review Team (IRT).
>>>>>
>>>>> The implementation process is an ICANN org-driven exercise.  ICANN org
>>>>> plans to employ the ?Open + Representative Model? piloted on the
>>>>> Subsequent Procedures IRT and based on the GNSO?s PDP 3.0 model
>>>>> <
>>>>> https://gnso.icann.org/sites/default/files/file/field-file-attach/pdp-3-2-working-group-models-10feb20-en.pdf.pdf>.
>>>>>
>>>>> The goal is to provide a structure that allows for efficient
>>>>> resolution
>>>>> of issues that may occur.
>>>>>
>>>>> We kindly ask that your group nominate up to one representative and up
>>>>> to one alternate to participate in the IRT. Please note, we are asking
>>>>> each of ICANN?s supporting organizations, advisory committees,
>>>>> stakeholder groups and constituencies to nominate up to one
>>>>> representative and one alternate.
>>>>>
>>>>> Putting forward a representative and alternate is optional; all
>>>>> members
>>>>> of the GNSO Group are welcome to join the IRT as participants. In
>>>>> fact,
>>>>> we urge anyone who is interested in being selected as a representative
>>>>> to join the IRT as a participant first (call for volunteers
>>>>> <
>>>>> https://www.icann.org/en/announcements/details/icann-seeks-volunteers-for-the-ppsai-implementation-review-team-20-05-2024-en>).
>>>>>
>>>>> As you will see below, the roles of participants and representatives
>>>>> are
>>>>> nearly identical, with the representatives? main function being that
>>>>> of
>>>>> an information-bridge to their community groups.
>>>>>
>>>>> ICANN org plans to host the first IRT call during the ICANN80 public
>>>>> meeting in June 2024. We do not require the nominees for the first
>>>>> meeting, but request that you conclude the nomination process and
>>>>> inform
>>>>> us of the nominees as soon as feasible.
>>>>>
>>>>> Why Have Representatives?
>>>>>
>>>>> While participants always speak in their own personal capacity,
>>>>> representatives are expected to speak on behalf of their constituency,
>>>>> stakeholder group, supporting organization, or advisory committee.
>>>>> Therefore, a key part of the representative?s role will be to engage
>>>>> actively and consistently with their colleagues to ensure they can
>>>>> convey their group?s viewpoints to the IRT. Please note, that this
>>>>> will
>>>>> require an efficient process for representatives to inform and receive
>>>>> input from their respective groups. To put this into place will be the
>>>>> responsibility of each representative.
>>>>>
>>>>> In addition, when determining the level of consensus in the
>>>>> circumstance
>>>>> described in Section V.E. of the IRT Principles & Guidelines
>>>>> <
>>>>> https://www.icann.org/en/system/files/files/irt-principles-guidelines-23aug16-en.pdf>,
>>>>>
>>>>> the GNSO Liaison, in the Open + Representative model, shall take into
>>>>> consideration that members who are representatives are expected to
>>>>> express the viewpoint of their respective community groups and
>>>>> participants to express their own views. This does not impact each
>>>>> member?s ability to raise any concern they may have, nor does it
>>>>> absolve
>>>>> ICANN org or the GNSO Council liaison from ?exercis[ing] all
>>>>> reasonable
>>>>> efforts to resolve disagreements? within the IRT.
>>>>>
>>>>> More information can be found on this PPSAI IRT wiki page
>>>>> <https://community.icann.org/x/lQDSEw>.  We are looking forward to
>>>>> getting the IRT underway and, please, do not hesitate to reach out
>>>>> should you have any questions.
>>>>>
>>>>> --
>>>>>
>>>>> Kind Regards,
>>>>>
>>>>> Dennis S. Chang
>>>>>
>>>>> GDD Programs Director
>>>>>
>>>>> Phone: +1 213 293 7889
>>>>>
>>>>> Sykpe: dennisSchang
>>>>>
>>>>> www.icann.org <http://www.icann.org>  One World ? One Internet
>>>>>
>>>>> _______________________________________________
>>>>> NCSG-PC mailing list
>>>>> NCSG-PC at lists.ncsg.is
>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>
>>>> --
>>>> Kathy Kleiman
>>>> Past President, Domain Name Rights Coalition
>>>>
>>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240603/9eed19ee/attachment.htm>

From bruna.mrtns at gmail.com  Mon Jun  3 11:01:28 2024
From: bruna.mrtns at gmail.com (Bruna Martins dos Santos)
Date: Mon, 3 Jun 2024 10:01:28 +0200
Subject: [NCSG-PC] Fwd: NomCom changes
In-Reply-To: <CAM8DdeUSToi2f0ZF3nX1Zp96nAjY07-=YmAVeXe_U_Fm0YKg-A@mail.gmail.com>
References: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
 <aa680b0b-ee62-4297-a704-da8f03cb43ba@julf.com>
 <f1f28108-04d0-4a7f-8f9b-c5d038d4582c@digitaldiscretion.ca>
 <a56b2543-cf7b-4601-8ac2-142e22dd499c@julf.com>
 <1524075964.360208.1717262801078@mail.yahoo.com>
 <CAM8DdeWj6-J=s5JEWisWi7qm-9rxaSGuHnrnQVeh+trZmDwjBQ@mail.gmail.com>
 <4d1903fb-d3e2-4b8e-8919-2c08951244de@julf.com>
 <CAM8DdeUSToi2f0ZF3nX1Zp96nAjY07-=YmAVeXe_U_Fm0YKg-A@mail.gmail.com>
Message-ID: <CADAEEV1_QaaUU+E0qPPnOZszN1XcuaOwHhtLBhNUtsBfmP6F1w@mail.gmail.com>

Im a bit confused as to why they added Julf to the initial thread as the
seat we have at NomCom is NCUC's. But once we're past this point I agree
that this is a very bizarre amendment in the bylaws w/ a rather clear
exclusion of our perspective.

Id say No to the random rotation and think it should be given to the groups
w/ more seats: If BC has two then one of their seats should rotate every
1y. Other than that the random rotation weakens the position of groups like
ours.

Also adding a +1 to the plan Farzaneh highlighted above: 1) write a letter
to the board ; 2) set up meetings with the cph to specifically talk about
this; and  3) talk to ISPCP

best,
B


On Mon, Jun 3, 2024 at 4:57?AM Tomslin Samme-Nlar <mesumbeslin at gmail.com>
wrote:

> I see the issue is very lively in the EC list but unfortunately not
> helping with the immediate question at hand which is:
>
> To prevent all delegates term ending at the same time with the new term
> limits, what does NCSG think about using a random selection process to
> select three out of seven GNSO delegates to serve one-year terms?
>
> Warmly,
> Tomslin
>
> On Sun, 2 June 2024, 17:43 Johan Helsingius, <julf at julf.com> wrote:
>
>> On 01/06/2024 23:34, Tomslin Samme-Nlar wrote:
>> > @Johan Helsingius <mailto:julf at julf.com> I feel like we should include
>> > the EC in this discussion. I believe that they would want to be part of
>> > the decision making?
>>
>> Noted - thanks, Tomslin. Forwarded the message to the EC too.
>>
>>         Julf
>>
>>
>> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>


-- 

*Bruna Martins dos Santos *

Global Campaigns Manager | Digital Action <http://digitalaction.co>

German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von
Humboldt Foundation <https://www.humboldt-foundation.de/>

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

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

From julf at Julf.com  Mon Jun  3 12:44:03 2024
From: julf at Julf.com (Johan Helsingius)
Date: Mon, 3 Jun 2024 11:44:03 +0200
Subject: [NCSG-PC] Fwd: NomCom changes
In-Reply-To: <CADAEEV1_QaaUU+E0qPPnOZszN1XcuaOwHhtLBhNUtsBfmP6F1w@mail.gmail.com>
References: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
 <aa680b0b-ee62-4297-a704-da8f03cb43ba@julf.com>
 <f1f28108-04d0-4a7f-8f9b-c5d038d4582c@digitaldiscretion.ca>
 <a56b2543-cf7b-4601-8ac2-142e22dd499c@julf.com>
 <1524075964.360208.1717262801078@mail.yahoo.com>
 <CAM8DdeWj6-J=s5JEWisWi7qm-9rxaSGuHnrnQVeh+trZmDwjBQ@mail.gmail.com>
 <4d1903fb-d3e2-4b8e-8919-2c08951244de@julf.com>
 <CAM8DdeUSToi2f0ZF3nX1Zp96nAjY07-=YmAVeXe_U_Fm0YKg-A@mail.gmail.com>
 <CADAEEV1_QaaUU+E0qPPnOZszN1XcuaOwHhtLBhNUtsBfmP6F1w@mail.gmail.com>
Message-ID: <d713279c-4226-4607-a87c-55a9b78cad43@Julf.com>

On 03/06/2024 10:01, Bruna Martins dos Santos wrote:
> Id say No to the random rotation and think it should be given to the 
> groups w/ more seats: If BC has two then one of their seats should 
> rotate every 1y. Other than that?the random rotation weakens the 
> position?of groups like ours.

It is not about rotation going forward, but a one-off as they
introduce the new harmonized terms.

	Julf



From compsoftnet at gmail.com  Mon Jun  3 16:39:40 2024
From: compsoftnet at gmail.com (Akinremi Peter Taiwo)
Date: Mon, 3 Jun 2024 09:39:40 -0400
Subject: [NCSG-PC] Fwd: NomCom changes
In-Reply-To: <d713279c-4226-4607-a87c-55a9b78cad43@Julf.com>
References: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
 <aa680b0b-ee62-4297-a704-da8f03cb43ba@julf.com>
 <f1f28108-04d0-4a7f-8f9b-c5d038d4582c@digitaldiscretion.ca>
 <a56b2543-cf7b-4601-8ac2-142e22dd499c@julf.com>
 <1524075964.360208.1717262801078@mail.yahoo.com>
 <CAM8DdeWj6-J=s5JEWisWi7qm-9rxaSGuHnrnQVeh+trZmDwjBQ@mail.gmail.com>
 <4d1903fb-d3e2-4b8e-8919-2c08951244de@julf.com>
 <CAM8DdeUSToi2f0ZF3nX1Zp96nAjY07-=YmAVeXe_U_Fm0YKg-A@mail.gmail.com>
 <CADAEEV1_QaaUU+E0qPPnOZszN1XcuaOwHhtLBhNUtsBfmP6F1w@mail.gmail.com>
 <d713279c-4226-4607-a87c-55a9b78cad43@Julf.com>
Message-ID: <CAGK4d0_iCaNztkaup1KiPOzco4jn_pWZ11mjtx_6EizjYrQiLA@mail.gmail.com>

I strong believe this should not apply to the one slot NCUC has because if
that happens there won't be anyone representing noncomercial on Nomcom.

I will suggest this should apply to SG that has more than on slots. We need
to have a concrete discussion with Greg and other members on the GNSO to
except noncommercial slot from the gaming scenario.

Kind regards
Peter


On Mon, Jun 3, 2024 at 5:44?AM Johan Helsingius via NCSG-PC <
ncsg-pc at lists.ncsg.is> wrote:

> On 03/06/2024 10:01, Bruna Martins dos Santos wrote:
> > Id say No to the random rotation and think it should be given to the
> > groups w/ more seats: If BC has two then one of their seats should
> > rotate every 1y. Other than that the random rotation weakens the
> > position of groups like ours.
>
> It is not about rotation going forward, but a one-off as they
> introduce the new harmonized terms.
>
>         Julf
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>


-- 
Best regards

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

From julf at Julf.com  Mon Jun  3 16:55:44 2024
From: julf at Julf.com (Johan Helsingius)
Date: Mon, 3 Jun 2024 15:55:44 +0200
Subject: [NCSG-PC] Fwd: NomCom changes
In-Reply-To: <CAGK4d0_iCaNztkaup1KiPOzco4jn_pWZ11mjtx_6EizjYrQiLA@mail.gmail.com>
References: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
 <aa680b0b-ee62-4297-a704-da8f03cb43ba@julf.com>
 <f1f28108-04d0-4a7f-8f9b-c5d038d4582c@digitaldiscretion.ca>
 <a56b2543-cf7b-4601-8ac2-142e22dd499c@julf.com>
 <1524075964.360208.1717262801078@mail.yahoo.com>
 <CAM8DdeWj6-J=s5JEWisWi7qm-9rxaSGuHnrnQVeh+trZmDwjBQ@mail.gmail.com>
 <4d1903fb-d3e2-4b8e-8919-2c08951244de@julf.com>
 <CAM8DdeUSToi2f0ZF3nX1Zp96nAjY07-=YmAVeXe_U_Fm0YKg-A@mail.gmail.com>
 <CADAEEV1_QaaUU+E0qPPnOZszN1XcuaOwHhtLBhNUtsBfmP6F1w@mail.gmail.com>
 <d713279c-4226-4607-a87c-55a9b78cad43@Julf.com>
 <CAGK4d0_iCaNztkaup1KiPOzco4jn_pWZ11mjtx_6EizjYrQiLA@mail.gmail.com>
Message-ID: <b382728b-5657-49f7-9a88-71ccea71d1f2@Julf.com>

 From the original message: "However, the SG/Cs with
one-year terms will have to replace those delegates after
one year rather than two."

It doesn't mean there wouldn't be anyone representing us - it
just means we would have to select a new rep one year sooner
than planned.

	Julf

On 03/06/2024 15:39, Akinremi Peter Taiwo wrote:
> I strong believe this should not apply to the one slot NCUC has because 
> if that happens there won't be anyone representing noncomercial?on Nomcom.
> 
> I will suggest this should apply to SG that has more than on slots. We 
> need to have a concrete discussion with Greg and other members on the 
> GNSO to except noncommercial slot from the gaming scenario.
> 
> Kind regards
> Peter
> 
> 
> On Mon, Jun 3, 2024 at 5:44?AM Johan Helsingius via NCSG-PC 
> <ncsg-pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>> wrote:
> 
>     On 03/06/2024 10:01, Bruna Martins dos Santos wrote:
>      > Id say No to the random rotation and think it should be given to the
>      > groups w/ more seats: If BC has two then one of their seats should
>      > rotate every 1y. Other than that?the random rotation weakens the
>      > position?of groups like ours.
> 
>     It is not about rotation going forward, but a one-off as they
>     introduce the new harmonized terms.
> 
>      ? ? ? ? Julf
> 
>     _______________________________________________
>     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>
> 
> 
> 
> -- 
> Best regards
> 
> *Taiwo Peter Akinremi*
> ------ ------ ------- ------ ------ ------- ------ ------ ------- ------ 
> ------ ------- ------ ------
> *Policy Advisory | Data Governance and Privacy Consultant | Information 
> Security & Cybersecurity | Certified Salesforce Administrator*
> *Phone*; +2348117714345, +2347063830177 *Skype*: akinremi.taiwo
> *Email:* compsoftnet at gmail.com <mailto:compsoftnet at gmail.com>, 
> peterexecute at gmail.com <mailto:peterexecute at gmail.com>
> ___________________________________________
> 
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc


From mesumbeslin at gmail.com  Tue Jun  4 04:18:38 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Tue, 4 Jun 2024 11:18:38 +1000
Subject: [NCSG-PC] Fwd: NomCom changes
In-Reply-To: <b382728b-5657-49f7-9a88-71ccea71d1f2@Julf.com>
References: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
 <aa680b0b-ee62-4297-a704-da8f03cb43ba@julf.com>
 <f1f28108-04d0-4a7f-8f9b-c5d038d4582c@digitaldiscretion.ca>
 <a56b2543-cf7b-4601-8ac2-142e22dd499c@julf.com>
 <1524075964.360208.1717262801078@mail.yahoo.com>
 <CAM8DdeWj6-J=s5JEWisWi7qm-9rxaSGuHnrnQVeh+trZmDwjBQ@mail.gmail.com>
 <4d1903fb-d3e2-4b8e-8919-2c08951244de@julf.com>
 <CAM8DdeUSToi2f0ZF3nX1Zp96nAjY07-=YmAVeXe_U_Fm0YKg-A@mail.gmail.com>
 <CADAEEV1_QaaUU+E0qPPnOZszN1XcuaOwHhtLBhNUtsBfmP6F1w@mail.gmail.com>
 <d713279c-4226-4607-a87c-55a9b78cad43@Julf.com>
 <CAGK4d0_iCaNztkaup1KiPOzco4jn_pWZ11mjtx_6EizjYrQiLA@mail.gmail.com>
 <b382728b-5657-49f7-9a88-71ccea71d1f2@Julf.com>
Message-ID: <CAM8DdeUs1ZQ6cxH7upLrjketBZFJ8_MNPGDqXYqy8THMbr0rUg@mail.gmail.com>

Thanks, Julf.

I wanted to add that clarification as well, so that we are all on the same
page on the question in front if us. I know it is a bit confusing.

I like the suggestion that we should ask which GNSO reps have only one term
left, and start from there.

On a side note, it is a bit late now but I think we should have included
our NomCom rep in this discussion.

Warmly,
Tomslin

On Mon, 3 June 2024, 23:55 Johan Helsingius via NCSG-PC, <
ncsg-pc at lists.ncsg.is> wrote:

>  From the original message: "However, the SG/Cs with
> one-year terms will have to replace those delegates after
> one year rather than two."
>
> It doesn't mean there wouldn't be anyone representing us - it
> just means we would have to select a new rep one year sooner
> than planned.
>
>         Julf
>
> On 03/06/2024 15:39, Akinremi Peter Taiwo wrote:
> > I strong believe this should not apply to the one slot NCUC has because
> > if that happens there won't be anyone representing noncomercial on
> Nomcom.
> >
> > I will suggest this should apply to SG that has more than on slots. We
> > need to have a concrete discussion with Greg and other members on the
> > GNSO to except noncommercial slot from the gaming scenario.
> >
> > Kind regards
> > Peter
> >
> >
> > On Mon, Jun 3, 2024 at 5:44?AM Johan Helsingius via NCSG-PC
> > <ncsg-pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>> wrote:
> >
> >     On 03/06/2024 10:01, Bruna Martins dos Santos wrote:
> >      > Id say No to the random rotation and think it should be given to
> the
> >      > groups w/ more seats: If BC has two then one of their seats should
> >      > rotate every 1y. Other than that the random rotation weakens the
> >      > position of groups like ours.
> >
> >     It is not about rotation going forward, but a one-off as they
> >     introduce the new harmonized terms.
> >
> >              Julf
> >
> >     _______________________________________________
> >     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>
> >
> >
> >
> > --
> > Best regards
> >
> > *Taiwo Peter Akinremi*
> > ------ ------ ------- ------ ------ ------- ------ ------ ------- ------
> > ------ ------- ------ ------
> > *Policy Advisory | Data Governance and Privacy Consultant | Information
> > Security & Cybersecurity | Certified Salesforce Administrator*
> > *Phone*; +2348117714345, +2347063830177 *Skype*: akinremi.taiwo
> > *Email:* compsoftnet at gmail.com <mailto:compsoftnet at gmail.com>,
> > peterexecute at gmail.com <mailto:peterexecute at gmail.com>
> > ___________________________________________
> >
> > _______________________________________________
> > NCSG-PC mailing list
> > NCSG-PC at lists.ncsg.is
> > https://lists.ncsg.is/mailman/listinfo/ncsg-pc
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240604/70f7d5a6/attachment.htm>

From julf at Julf.com  Tue Jun  4 07:59:37 2024
From: julf at Julf.com (Johan Helsingius)
Date: Tue, 4 Jun 2024 06:59:37 +0200
Subject: [NCSG-PC] Fwd: NomCom changes
In-Reply-To: <CAM8DdeUs1ZQ6cxH7upLrjketBZFJ8_MNPGDqXYqy8THMbr0rUg@mail.gmail.com>
References: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
 <aa680b0b-ee62-4297-a704-da8f03cb43ba@julf.com>
 <f1f28108-04d0-4a7f-8f9b-c5d038d4582c@digitaldiscretion.ca>
 <a56b2543-cf7b-4601-8ac2-142e22dd499c@julf.com>
 <1524075964.360208.1717262801078@mail.yahoo.com>
 <CAM8DdeWj6-J=s5JEWisWi7qm-9rxaSGuHnrnQVeh+trZmDwjBQ@mail.gmail.com>
 <4d1903fb-d3e2-4b8e-8919-2c08951244de@julf.com>
 <CAM8DdeUSToi2f0ZF3nX1Zp96nAjY07-=YmAVeXe_U_Fm0YKg-A@mail.gmail.com>
 <CADAEEV1_QaaUU+E0qPPnOZszN1XcuaOwHhtLBhNUtsBfmP6F1w@mail.gmail.com>
 <d713279c-4226-4607-a87c-55a9b78cad43@Julf.com>
 <CAGK4d0_iCaNztkaup1KiPOzco4jn_pWZ11mjtx_6EizjYrQiLA@mail.gmail.com>
 <b382728b-5657-49f7-9a88-71ccea71d1f2@Julf.com>
 <CAM8DdeUs1ZQ6cxH7upLrjketBZFJ8_MNPGDqXYqy8THMbr0rUg@mail.gmail.com>
Message-ID: <fca65f24-48b8-422f-a419-ae0928b528d3@Julf.com>

I have gotten some clarification from ICANN staff. Seems the nomcom
review team has produced something completely contradictory - on one
hand they want two-year staggered terms in order to have continuity,
but on the other hand they want to start with a clean slate at the
2024 AGM, so everyone has to be reappointed, some with a 1-year and
some with a 2-year term.

Seems we really should have included our team reps in this discussion.

	Julf




On 04/06/2024 03:18, Tomslin Samme-Nlar wrote:
> Thanks, Julf.
> 
> I wanted to add that clarification as well, so that we are all on the 
> same page on the question in front if us. I know it is a bit confusing.
> 
> I like the suggestion that we should ask which GNSO reps have only one 
> term left, and start from there.
> 
> On a side note, it is a bit late now but I think we should have included 
> our NomCom rep in this discussion.
> 
> Warmly,
> Tomslin
> 
> On Mon, 3 June 2024, 23:55 Johan Helsingius via NCSG-PC, 
> <ncsg-pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>> wrote:
> 
>      ?From the original message: "However, the SG/Cs with
>     one-year terms will have to replace those delegates after
>     one year rather than two."
> 
>     It doesn't mean there wouldn't be anyone representing us - it
>     just means we would have to select a new rep one year sooner
>     than planned.
> 
>      ? ? ? ? Julf
> 
>     On 03/06/2024 15:39, Akinremi Peter Taiwo wrote:
>      > I strong believe this should not apply to the one slot NCUC has
>     because
>      > if that happens there won't be anyone representing
>     noncomercial?on Nomcom.
>      >
>      > I will suggest this should apply to SG that has more than on
>     slots. We
>      > need to have a concrete discussion with Greg and other members on
>     the
>      > GNSO to except noncommercial slot from the gaming scenario.
>      >
>      > Kind regards
>      > Peter
>      >
>      >
>      > On Mon, Jun 3, 2024 at 5:44?AM Johan Helsingius via NCSG-PC
>      > <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>>> wrote:
>      >
>      >? ? ?On 03/06/2024 10:01, Bruna Martins dos Santos wrote:
>      >? ? ? > Id say No to the random rotation and think it should be
>     given to the
>      >? ? ? > groups w/ more seats: If BC has two then one of their
>     seats should
>      >? ? ? > rotate every 1y. Other than that?the random rotation
>     weakens the
>      >? ? ? > position?of groups like ours.
>      >
>      >? ? ?It is not about rotation going forward, but a one-off as they
>      >? ? ?introduce the new harmonized terms.
>      >
>      >? ? ? ? ? ? ? Julf
>      >
>      >? ? ?_______________________________________________
>      >? ? ?NCSG-PC mailing list
>      > NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>     <mailto:NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>>
>      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>      >? ? ?<https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>>
>      >
>      >
>      >
>      > --
>      > Best regards
>      >
>      > *Taiwo Peter Akinremi*
>      > ------ ------ ------- ------ ------ ------- ------ ------ -------
>     ------
>      > ------ ------- ------ ------
>      > *Policy Advisory | Data Governance and Privacy Consultant |
>     Information
>      > Security & Cybersecurity | Certified Salesforce Administrator*
>      > *Phone*; +2348117714345, +2347063830177 *Skype*: akinremi.taiwo
>      > *Email:* compsoftnet at gmail.com <mailto:compsoftnet at gmail.com>
>     <mailto:compsoftnet at gmail.com <mailto:compsoftnet at gmail.com>>,
>      > peterexecute at gmail.com <mailto:peterexecute at gmail.com>
>     <mailto:peterexecute at gmail.com <mailto:peterexecute at gmail.com>>
>      > ___________________________________________
>      >
>      > _______________________________________________
>      > 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 mesumbeslin at gmail.com  Wed Jun  5 15:50:00 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Wed, 5 Jun 2024 22:50:00 +1000
Subject: [NCSG-PC] Fwd: [gnso-chairs] [CORRESPONDENCE] Tripti Sinha to Greg
 DiBiase - Urgent Requests
In-Reply-To: <BC46EC65-1EED-46C7-8564-D3FC88BE9F58@icann.org>
References: <BC46EC65-1EED-46C7-8564-D3FC88BE9F58@icann.org>
Message-ID: <CAM8DdeX5L6d2_M++0OV81=2Q7a-orSO60ZWzSUsT+b8GMexKjw@mail.gmail.com>

Dear members,

Please see attached a letter from the board to the council regarding
registration data urgent requests. The gist is that the Board believes that
the Board adopted Recommendation 18 of Expedited Policy Development Process
(EPDP) Phase 1 adopted which relates to urgent requests for unpublished
registrant data in the context of situations that pose an imminent threat
to life, serious bodily harm, infrastructure, or child exploitation is not
fit for purpose and wants it to be revisited. The reasons are listed in the
letter, please read it.

The Board notes that neither the Bylaws nor existing procedures account for
this situation where the Board concludes that a policy recommendation that
it has previously approved should be revisited prior to implementation. So,
they would like to get ideas from the council on how to approach the
matter. We will appreciate it if you have any comments/suggestions which
councillors can take to the meeting next week.

Warmly,
Tomslin



---------- Forwarded message ---------
From: Wendy Profit via Gnso-chairs <gnso-chairs at icann.org>
Date: Mon, 3 Jun 2024 at 22:34
Subject: [gnso-chairs] [CORRESPONDENCE] Tripti Sinha to Greg DiBiase -
Urgent Requests
To: gnso-chairs at icann.org <gnso-chairs at icann.org>, dibiase at amazon.com <
dibiase at amazon.com>, gnso-secs at icann.org <gnso-secs at icann.org>
Cc: Tripti Sinha <tripti.sinha at board.icann.org>, Correspondence <
Correspondence at icann.org>, Secretary <secretary at icann.org>, Board Ops Team <
board-ops-team at icann.org>


Dear Greg DiBiase,



Please find the attached letter from Tripti Sinha regarding EPDP Phase 1
Recommendation 18 as it relates to urgent requests.



Thank you and best regards,



Wendy Profit

Board Operations Senior Manager

ICANN






_______________________________________________
Gnso-chairs mailing list -- gnso-chairs at icann.org
To unsubscribe send an email to gnso-chairs-leave at icann.org
_______________________________________________
By submitting your personal data, you consent to the processing of your
personal data for purposes of subscribing to this mailing list accordance
with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
the website Terms of Service (https://www.icann.org/privacy/tos). You can
visit the Mailman link above to change your membership status or
configuration, including unsubscribing, setting digest-style delivery or
disabling delivery altogether (e.g., for a vacation), and so on.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240605/908008da/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2024-06-03 Sinha-to-DiBiase-UrgentRequests.pdf
Type: application/pdf
Size: 123492 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240605/908008da/attachment.pdf>

From mesumbeslin at gmail.com  Wed Jun  5 15:50:53 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Wed, 5 Jun 2024 22:50:53 +1000
Subject: [NCSG-PC] Call for meeting topics for our Policy meeting in Kigali
Message-ID: <CAM8DdeXNQ2NXno0=Zs1Ms-srEHon=JKm+msaeEDfasNxHCnR=A@mail.gmail.com>

Hello team,

I am currently putting together the agenda for the policy meeting in
Kigali, so I am checking with you to know whether there are topics that you
would either like us to discuss or a topic you'd like to present to the
group? Some potential ones are:
1. The board's Urgent Request letter to the council
2. Singulars/Plurals

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

From muyiwacaleb at gmail.com  Wed Jun  5 23:23:42 2024
From: muyiwacaleb at gmail.com (Caleb Olumuyiwa Ogundele)
Date: Wed, 5 Jun 2024 15:23:42 -0500
Subject: [NCSG-PC] UPDATE : Continuous Improvement Program Community
 Coordination Group (CIP-CCG)
In-Reply-To: <CAL_ZvK4UA0F2iMFQ-UEkU-ojDEQ26+TQiXZUfq+PEtXiypLVVw@mail.gmail.com>
References: <CAL_ZvK4UA0F2iMFQ-UEkU-ojDEQ26+TQiXZUfq+PEtXiypLVVw@mail.gmail.com>
Message-ID: <CAL_ZvK7vgV2r_-hiuSSrbhedRhaLA5edyY3BTu+ZYhH_q0qdEA@mail.gmail.com>

In anticipation of having staff socialize this working group's core mission
during the NCSG membership session, I wanted to do a follow-up on these
principles while welcoming your feedback.

Regards

Caleb

On Sat, Apr 6, 2024 at 1:02?PM Caleb Olumuyiwa Ogundele <
muyiwacaleb at gmail.com> wrote:

> Hello Everyone,
> This working group update is specifically for NPOC Membership but since we
> usually have or share the same position, I thought is good to share also
> with NCSG Members to ask for their feedback. This is the first update and I
> hope to write the second update in a few days time after the content of
> this email is digested as it promises to be a very long email content.
>
> The representation in this group has myself (Caleb) representing NPOC with
> Wisdom as the NPOC alternate while  Manju is NCSG (through the GNSO
> Council) and Benjamin is NCUC. In case I miss anything, please jump in
> Manju, Wisdom, and Benjamin.
> But first, let me introduce what the working group is all about while we
> seek feedback
>
> *What is the Continuous Improvement Program Community Coordination Group
> (CIP-CCG)?*
> ICANN's commitment to continuous improvement led to the formation of the
> CIP-CCG on December 12, 2023.
> The purpose of the group is to improve the effectiveness of ICANN's
> Organizational Reviews process. This aligns with ongoing efforts to
> strengthen ICANN's multistakeholder model. The CIP-CCG will create a
> framework for continuous improvement within ICANN's Supporting
> Organizations, Advisory Committees, and Nominating Committee.
> While this group was formed to help transform ICANN's Organizational
> Reviews into a Continuous Improvement Program, implementing Recommendation
> 3.6 from the Third Accountability and Transparency Review (ATRT3)
> <https://community.icann.org/pages/viewpage.action?pageId=273454168> was
> the offshoot of this group formation. Developing this Continuous
> Improvement Program is part of a broader effort to enhance the
> effectiveness of ICANN's multistakeholder model, aligning with ICANN's
> Interim President and CEO's Goal 11
> <https://www.icann.org/en/blogs/details/icann-interim-president-and-ceo-shares-goals-for-fiscal-year-2024-27-09-2023-en>
> related to refining the review processes. To read more about this check this
> link
> <https://www.icann.org/en/blogs/details/icann-reviews-program-update-and-interim-president-and-ceo-goal-11-03-10-2023-en>
>
> *The key responsibilities of the CIP-CCG are:*
>
>    1. Establish a shared understanding of what "continuous improvement"
>    means in the context of ATRT3's Recommendation 3.6.
>    2. Evaluate different methodologies for effective Continuous
>    Improvement Programs.
>    3. Agree on the methodology best suited for ICANN's purposes.
>    4. Formulate a Continuous Improvement Program Framework to be used by
>    ICANN's Supporting Organizations, Advisory Committees, and the Nominating
>    Committee.
>
>
> * ICANN Principles of Continuous Improvement to NPOC (But relevant and
> same content for NCUC/NCSG)*
> Historically, ICANN Organizational Reviews have asked whether the
> Supporting Organizations (SOs), Advisory Committees (ACs), and the
> Nominating Committee (NomCom) have a continuing purpose within the ICANN
> community. Rather than articulating this as a single principle, ICANN org
> proposes it as an overarching consideration that is addressed through five
> separate principles that would guide the successful execution of the
> Continuous Improvement Program (CIP).
>
>    1. Principle 1: The SO/AC is fulfilling its purpose.
>    2. Principle 2: The structure of the SO/AC is effective.
>    3. Principle 3: Are the operations of SO/AC are efficient?
>    4. Principle 4: Is the SO/AC is accountable internally to its
>    stakeholders, and externally to the wider ICANN community?
>    5. Principle 5: The ICANN community collaborates to further the
>    mission of ICANN and the effectiveness of the ICANN multistakeholder model.
>
> We have been tasked to ask the community for some feedback. While I hope
> to collate some of your thoughts and take back to the WG.
>
> To make this email brief, I will break this email into several parts for
> us to digest the content while I post other updates in a day or two from
> now.
> *Caleb Ogundele*
> Email: muyiwacaleb at gmail.com
>


-- 
*Caleb Ogundele*
Email: muyiwacaleb at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240605/6b12869f/attachment.htm>

From rafik.dammak at gmail.com  Thu Jun  6 04:49:39 2024
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Thu, 6 Jun 2024 10:49:39 +0900
Subject: [NCSG-PC] Fwd: [gnso-chairs] [CORRESPONDENCE] Tripti Sinha to
 Greg DiBiase - Urgent Requests
In-Reply-To: <CAM8DdeX5L6d2_M++0OV81=2Q7a-orSO60ZWzSUsT+b8GMexKjw@mail.gmail.com>
References: <BC46EC65-1EED-46C7-8564-D3FC88BE9F58@icann.org>
 <CAM8DdeX5L6d2_M++0OV81=2Q7a-orSO60ZWzSUsT+b8GMexKjw@mail.gmail.com>
Message-ID: <CAH5sTh=jKU+KfY-p54tFGGE0sL5gHDU3vvXAnvUHHFe1dWC+Lg@mail.gmail.com>

Hi Tomslin,

This is uncharted territory as the expression says and unfortunately it
might open for more ad-hoc approaches to revisit policy recommendations.
one point is to agree that we shouldn't just focus on fixing a single issue
but have more deep discussion on how to set up proper processes to deal
with such a situation and create safeguards against
reopening recommendations at every possible occasion during the lifecycle.
I would think that supposed steps like ODP or policy impact assessment
reviews could have helped at an earlier stage.  Something to bring later if
we talk about the effectiveness of PDP.

I would suggest first by being strongly against any small group or
council-board negotiation as it happened in other cases.  One idea to
explore or for brainstorming: can we initiate a quite limited scope EPDP
i.e. only working on recommendation 18 be the answer as we can assume that
all deliberations in previous EPDP and in IRT as indication that we don't
need an issue report? that will be a proper setup, following the usual
known process and flow and with proper representation. I can see the
objections now that we need quick response etc, but setting EPDP for one
single question, for one recommendation shouldn't take a long time and we
won't sacrifice due process on the altar of supposed efficiency.

Best,

Rafik

Le mer. 5 juin 2024 ? 21:50, Tomslin Samme-Nlar <mesumbeslin at gmail.com> a
?crit :

> Dear members,
>
> Please see attached a letter from the board to the council regarding
> registration data urgent requests. The gist is that the Board believes that
> the Board adopted Recommendation 18 of Expedited Policy Development Process
> (EPDP) Phase 1 adopted which relates to urgent requests for unpublished
> registrant data in the context of situations that pose an imminent threat
> to life, serious bodily harm, infrastructure, or child exploitation is not
> fit for purpose and wants it to be revisited. The reasons are listed in the
> letter, please read it.
>
> The Board notes that neither the Bylaws nor existing procedures account
> for this situation where the Board concludes that a policy recommendation
> that it has previously approved should be revisited prior to
> implementation. So, they would like to get ideas from the council on how to
> approach the matter. We will appreciate it if you have any
> comments/suggestions which councillors can take to the meeting next week.
>
> Warmly,
> Tomslin
>
>
>
> ---------- Forwarded message ---------
> From: Wendy Profit via Gnso-chairs <gnso-chairs at icann.org>
> Date: Mon, 3 Jun 2024 at 22:34
> Subject: [gnso-chairs] [CORRESPONDENCE] Tripti Sinha to Greg DiBiase -
> Urgent Requests
> To: gnso-chairs at icann.org <gnso-chairs at icann.org>, dibiase at amazon.com <
> dibiase at amazon.com>, gnso-secs at icann.org <gnso-secs at icann.org>
> Cc: Tripti Sinha <tripti.sinha at board.icann.org>, Correspondence <
> Correspondence at icann.org>, Secretary <secretary at icann.org>, Board Ops
> Team <board-ops-team at icann.org>
>
>
> Dear Greg DiBiase,
>
>
>
> Please find the attached letter from Tripti Sinha regarding EPDP Phase 1
> Recommendation 18 as it relates to urgent requests.
>
>
>
> Thank you and best regards,
>
>
>
> Wendy Profit
>
> Board Operations Senior Manager
>
> ICANN
>
>
>
>
>
>
> _______________________________________________
> Gnso-chairs mailing list -- gnso-chairs at icann.org
> To unsubscribe send an email to gnso-chairs-leave at icann.org
> _______________________________________________
> By submitting your personal data, you consent to the processing of your
> personal data for purposes of subscribing to this mailing list accordance
> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). You can
> visit the Mailman link above to change your membership status or
> configuration, including unsubscribing, setting digest-style delivery or
> disabling delivery altogether (e.g., for a vacation), and so on.
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240606/b9b69f89/attachment.htm>

From julf at Julf.com  Thu Jun  6 18:50:33 2024
From: julf at Julf.com (Johan Helsingius)
Date: Thu, 6 Jun 2024 17:50:33 +0200
Subject: [NCSG-PC] FY26 Planning Prioritization Group Nominations
In-Reply-To: <2E51EF31-16F4-441D-A581-E9B151796547@icann.org>
References: <2E51EF31-16F4-441D-A581-E9B151796547@icann.org>
Message-ID: <a92188fb-b578-4624-8d96-0f0660c48bf5@Julf.com>

Are we still OK with Peter and Amine, or should we do a new round
of looking for reps?

	Julf

  *NEW: **A Request for FY26 Planning Prioritization Group Nominations: 
Due 28 June 2024*

The FY26 Annual Operating Plan and Budget Planning Process has launched, 
and we are seeking nominations from the SO/AC Leadership to the 
community led Planning Prioritization Group. *The community-led Planning 
Prioritization Group is scheduled to hold meetings in July 2024. *This 
timing will permit ICANN org to receive input for the development of the 
Draft Operating Plan and Budget, which is planned to open for Public 
Comment in December 2024.

*We ask that the SO/AC Leadership please nominate new members or 
re-confirm the previous member(s) from your group no later than 28 June 
2024.*Previous members by SO/AC are listed here [danh45uab.cc.rs6.net] 
<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001t4d7Wn0JFTI5hiPMyoJvGG0aURb7DweptRKxSvJsuk8uicrV_ywF0SM6U38yVW2y_lZ_v2peHpj7z14dXA0zn0dWJr8ms-ClqsGL2mWPYFmMJsCDYGYRVnXsZIPJhWENP9Wx9q43q0Z0V3f0AVXENvwGws8un_98b7w1BvtARI-6f2Eyr-XyvmctbFid1ZQkVVE7Cn4WEm40Ez12fWBetlSu805QjF9rC4lpgX_Ekr4=&c=YBqeloUnG6gkmed1LO1Ol4lKtkyL8CEtQ9q3LU-TBjGoj1i0yg91oQ==&ch=RO0kRXExHnCYLGxX1azq-x8RtTRaLaOa7eQKfl5WG0rIPpSK9uxriA==__;!!PtGJab4!-XLbExQBPpk743O9KhWNs8kjS_NxBgRysBRevN9rwWD-alyh_z-hteneqBvez70rX69QWziC9LanJVXEuCBcODQRruHj$>. 
Please email the name of the members that you have nominated to 
planning at icann.org <mailto:planning at icann.org> with a copy to the Policy 
Strategic Management team (policy-strat-mgt at icann.org 
<mailto:policy-strat-mgt at icann.org>).

Please nominate 1 member and 1 secondary member from your group as follows:

ASO | ALAC | GNSO/CSG | GNSO/CPH | GNSO/NCSG | ccNSO | GAC | RSSAC | SSAC

For more information on the Planning Prioritization Group please visit 
here [danh45uab.cc.rs6.net] 
<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001t4d7Wn0JFTI5hiPMyoJvGG0aURb7DweptRKxSvJsuk8uicrV_ywF0SM6U38yVW2yDjhYk-dgOTgKVcMK2qNYD5FzofxkNQt5UhfAWEaqnwDmnGHyDESUYp9xW-iFNdK1Viz5J85smQfBSjy_VtuaehwB5-saGF1M3wRhsuw5mROxdIILJLubtsrxv6jXL6DXo7ABadFbKvbqBPOVNvzAyef1ekTshqVEv5BGR0PagfDEx185J_mJ5VHvQDubF3o4&c=YBqeloUnG6gkmed1LO1Ol4lKtkyL8CEtQ9q3LU-TBjGoj1i0yg91oQ==&ch=RO0kRXExHnCYLGxX1azq-x8RtTRaLaOa7eQKfl5WG0rIPpSK9uxriA==__;!!PtGJab4!-XLbExQBPpk743O9KhWNs8kjS_NxBgRysBRevN9rwWD-alyh_z-hteneqBvez70rX69QWziC9LanJVXEuCBcOGIbsAEe$>.




From wisdom.dk at gmail.com  Thu Jun  6 19:00:57 2024
From: wisdom.dk at gmail.com (Wisdom Donkor)
Date: Thu, 6 Jun 2024 16:00:57 +0000
Subject: [NCSG-PC] FY26 Planning Prioritization Group Nominations
In-Reply-To: <a92188fb-b578-4624-8d96-0f0660c48bf5@Julf.com>
References: <2E51EF31-16F4-441D-A581-E9B151796547@icann.org>
 <a92188fb-b578-4624-8d96-0f0660c48bf5@Julf.com>
Message-ID: <CAAU+vPHbvEiRK2SEr0hAnFLtp=ovfGHN2vTZYh56rGaE=TEaXQ@mail.gmail.com>

Am ok

On Thu, 6 Jun 2024, 3:50?pm Johan Helsingius via NCSG-PC, <
ncsg-pc at lists.ncsg.is> wrote:

> Are we still OK with Peter and Amine, or should we do a new round
> of looking for reps?
>
>         Julf
>
>   *NEW: **A Request for FY26 Planning Prioritization Group Nominations:
> Due 28 June 2024*
>
> The FY26 Annual Operating Plan and Budget Planning Process has launched,
> and we are seeking nominations from the SO/AC Leadership to the
> community led Planning Prioritization Group. *The community-led Planning
> Prioritization Group is scheduled to hold meetings in July 2024. *This
> timing will permit ICANN org to receive input for the development of the
> Draft Operating Plan and Budget, which is planned to open for Public
> Comment in December 2024.
>
> *We ask that the SO/AC Leadership please nominate new members or
> re-confirm the previous member(s) from your group no later than 28 June
> 2024.*Previous members by SO/AC are listed here [danh45uab.cc.rs6.net]
> <
> https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001t4d7Wn0JFTI5hiPMyoJvGG0aURb7DweptRKxSvJsuk8uicrV_ywF0SM6U38yVW2y_lZ_v2peHpj7z14dXA0zn0dWJr8ms-ClqsGL2mWPYFmMJsCDYGYRVnXsZIPJhWENP9Wx9q43q0Z0V3f0AVXENvwGws8un_98b7w1BvtARI-6f2Eyr-XyvmctbFid1ZQkVVE7Cn4WEm40Ez12fWBetlSu805QjF9rC4lpgX_Ekr4=&c=YBqeloUnG6gkmed1LO1Ol4lKtkyL8CEtQ9q3LU-TBjGoj1i0yg91oQ==&ch=RO0kRXExHnCYLGxX1azq-x8RtTRaLaOa7eQKfl5WG0rIPpSK9uxriA==__;!!PtGJab4!-XLbExQBPpk743O9KhWNs8kjS_NxBgRysBRevN9rwWD-alyh_z-hteneqBvez70rX69QWziC9LanJVXEuCBcODQRruHj$>.
>
> Please email the name of the members that you have nominated to
> planning at icann.org <mailto:planning at icann.org> with a copy to the Policy
> Strategic Management team (policy-strat-mgt at icann.org
> <mailto:policy-strat-mgt at icann.org>).
>
> Please nominate 1 member and 1 secondary member from your group as follows:
>
> ASO | ALAC | GNSO/CSG | GNSO/CPH | GNSO/NCSG | ccNSO | GAC | RSSAC | SSAC
>
> For more information on the Planning Prioritization Group please visit
> here [danh45uab.cc.rs6.net]
> <
> https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001t4d7Wn0JFTI5hiPMyoJvGG0aURb7DweptRKxSvJsuk8uicrV_ywF0SM6U38yVW2yDjhYk-dgOTgKVcMK2qNYD5FzofxkNQt5UhfAWEaqnwDmnGHyDESUYp9xW-iFNdK1Viz5J85smQfBSjy_VtuaehwB5-saGF1M3wRhsuw5mROxdIILJLubtsrxv6jXL6DXo7ABadFbKvbqBPOVNvzAyef1ekTshqVEv5BGR0PagfDEx185J_mJ5VHvQDubF3o4&c=YBqeloUnG6gkmed1LO1Ol4lKtkyL8CEtQ9q3LU-TBjGoj1i0yg91oQ==&ch=RO0kRXExHnCYLGxX1azq-x8RtTRaLaOa7eQKfl5WG0rIPpSK9uxriA==__;!!PtGJab4!-XLbExQBPpk743O9KhWNs8kjS_NxBgRysBRevN9rwWD-alyh_z-hteneqBvez70rX69QWziC9LanJVXEuCBcOGIbsAEe$
> >.
>
>
> _______________________________________________
> 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/20240606/c9b8c32f/attachment.htm>

From mesumbeslin at gmail.com  Mon Jun 10 09:39:42 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Mon, 10 Jun 2024 08:39:42 +0200
Subject: [NCSG-PC] [Public Comment] Policy Status Report on the Policy &
 Implementation Recommendations
Message-ID: <CAM8DdeXO+GDuEGC-aoaSeH6+nFC-oApCbdjDn4oduYun0Pt5Fg@mail.gmail.com>

 Dear members,

ICANN org is seeking input on the Policy Status Report on the Policy &
Implementation Recommendations adopted by the GNSO Council and ICANN Board
in 2015. The report discusses the contents of the Policy and Implementation
Recommendations and their performance against stated objectives by the GNSO
Council and the ICANN community, based on readily available data, staff
observations, and analysis to date. The report is intended to serve as
input to the GNSO Council?s review of the policy and implementation related
efforts.

Refer to this page for more information:
https://www.icann.org/en/public-comment/proceeding/policy-status-report-gnso-policy-implementation-working-group-recommendations-16-05-2024

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

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

Pedro has kindly volunteered but he is keen for more volunteers to join
him. Let us know if you'd like to join in the drafting please.

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

From julf at julf.com  Tue Jun 11 12:11:00 2024
From: julf at julf.com (Johan Helsingius)
Date: Tue, 11 Jun 2024 11:11:00 +0200
Subject: [NCSG-PC] NCPH session Wednesday, 12 June 10:45-12:15
Message-ID: <ccabb864-1027-4b3b-bc2d-a4d24317df52@julf.com>

Just a reminder that we have the NCPH session on Wednesday.

The agenda is here:

https://docs.google.com/document/d/1_ez9vaJwX6VIliX-xN36Uv0mrbAur4s0imuNym7RT2o/

We should at least have the EC members present, but it would be
good to have PC members there too. In particular, we need the
Team 14 members and people familiar with the IPC Request for
Reconsideration to be in the room.

	Julf


From mesumbeslin at gmail.com  Tue Jun 11 12:30:45 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Tue, 11 Jun 2024 11:30:45 +0200
Subject: [NCSG-PC] Fwd: EOI representative to the PPSAI IRT
In-Reply-To: <CAGKde+1T3DiMxGouRgwsV-rH6t9qZ=Ne60wYyMhe1M36z1WQng@mail.gmail.com>
References: <CAGKde+1T3DiMxGouRgwsV-rH6t9qZ=Ne60wYyMhe1M36z1WQng@mail.gmail.com>
Message-ID: <CAM8DdeWM7ntC0=tyrJQT+8R1-idXk3WM-LN1v2NyBcwUAftvdQ@mail.gmail.com>

FYI

Warmly,
Tomslin



---------- Forwarded message ---------
From: Emmanuel Vitus <emmanuelvitus at gmail.com>
Date: Mon, 3 Jun 2024 at 20:10
Subject: EOI representative to the PPSAI IRT
To: Tomslin Samme-Nlar <mesumbeslin at gmail.com>
Cc: Johan Helsingius <julf at julf.com>, Andrea Glandon <
andrea.glandon at icann.org>


*Statement of Interest
<https://community.icann.org/display/gnsosoi/Emmanuel+Vitus+Agbenonwossi+++SOI>*

Name: Emmanuel Vitus
Affiliation: NCSG/NPOC

Hello Tomslin, Julf, and Andrea,

I am writing to express my interest in joining the Implementation Review
Team (IRT) for the Privacy and Proxy Services Accreditation Issues (PPSAI)
Policy Development Process (PDP). I believe my background and experience
<https://community.icann.org/display/gnsosoi/Emmanuel+Vitus+Agbenonwossi+++SOI>
make me a suitable candidate for this role.

This past year, as NPOC Policy Chair, I concentrated on enhancing our
impact within the ICANN ecosystem, particularly focusing on policy issues
including Internationalized Domain Names (IDNs), where I represent the
NCSG. I have been actively involved in the ICANN community for several
years. With the IDNs EPDP nearing its conclusion, I am eager to serve as
our SG's representative on the PPSAI IRT. This topic is of particular
interest to me. I am committed to actively participating in the IRT
meetings and contributing my expertise to support the successful
implementation of the Privacy/Proxy Policy Recommendations. I have informed
my colleagues and other members from the EC, about my intention to
participate.

Please feel free to reach out with any further questions or concerns.

Kind regards,

Emmanuel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240611/2eb83924/attachment.htm>

From mesumbeslin at gmail.com  Tue Jun 11 12:31:35 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Tue, 11 Jun 2024 11:31:35 +0200
Subject: [NCSG-PC] Fwd: [Call for Volunteers] Appointment of representative
 and alternate to the PPSAI IRT
In-Reply-To: <CAGSP6RTqj_4wU=Chax2Ct2Wu32g1N+7293zAdLJDfSiuhAE_ZQ@mail.gmail.com>
References: <CB52871E-374F-48BF-97D7-D184C00AD654@contoso.com>
 <ee28ed26-ea0c-4aa3-ba5f-46e9aa43bcbf@julf.com>
 <CAM8DdeUFVZ18WfoH28uMpys9dO20V=mZuTXqERZ2BYRqDerYEw@mail.gmail.com>
 <CAN1qJvAuWt0PPC7M+0SXRDmd3ksUUaoYpiY2nqsQReZG0pPz8w@mail.gmail.com>
 <130d1bc0-5408-4af3-a37b-f8a58aeeb9a3@dnrc.tech>
 <CAAjCLO20pmx4d2QixY10jcgmjSGYZdoWg-+_KEyu05qVWM9nMw@mail.gmail.com>
 <CAGSP6RQZxTgj=hR-5kHZaypzWQAkQLEBLWY2KE4QEcAHfn-CGQ@mail.gmail.com>
 <CAM8DdeWf70W_Bda-FVsM84X-PHyNw21y6AtJd3nB4V0JcLSihg@mail.gmail.com>
 <CAM8DdeWNzdfs4HJCzEvtwC5RV2=zHg9-084xy2q1RMqrA1DS4w@mail.gmail.com>
 <CAGSP6RTqj_4wU=Chax2Ct2Wu32g1N+7293zAdLJDfSiuhAE_ZQ@mail.gmail.com>
Message-ID: <CAM8DdeUVcBoBCYUBe11r-mhUg5ehiWJPKhgg__ajjSDUJ4Q+zQ@mail.gmail.com>

FYI

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


---------- Forwarded message ---------
From: Pedro de Perdig?o Lana <pedrodeperdigaolana at gmail.com>
Date: Mon, 3 Jun 2024 at 15:52
Subject: Re: [Call for Volunteers] Appointment of representative and
alternate to the PPSAI IRT
To: Tomslin Samme-Nlar <mesumbeslin at gmail.com>


Hi Tomslin,

If no one else applies for this, I may do it, preferably as an alternate
(since I plan to apply for the Pilot Holistic Review and, in 2025 or 2026,
the UDRP WP, and have little knowledge of the facts that lead to the PPSAI
IRT). I have some background in data protection, academically and
professionally. I am currently working as a lawyer in the "Conformity" (an
area similar to compliance, but a little broader) in NIC.br - I do not
represent this ".br" registry within ICANN, just my personal positions,
aligned with other non-profit organizations that I'm a board member.

As a specific conflict of interest related to this issue (another reason
why I prefer to be an alternate), I can't go directly against my employer's
positions on certain data protection topics - which is relevant, for
example, for WhoIs data disclosure, since there are some differences
between NCSG position on the subject and the one adopted by NIC.br

Here is the link to my SOI:
https://community.icann.org/pages/viewpage.action?pageId=300613648

Cordially,

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


Em seg., 3 de jun. de 2024 ?s 00:00, Tomslin Samme-Nlar <
mesumbeslin at gmail.com> escreveu:

> Hi members,
>
> I haven't heard back on this. So, I am following up to know whether the PC
> should proceed with appointing a representative to the IRT or decline to.
>
> Warmly,
> Tomslin
>
> On Tue, 28 May 2024, 09:53 Tomslin Samme-Nlar, <mesumbeslin at gmail.com>
> wrote:
>
>> Thanks for the comments @farzi, @Kathy, @Ponce and @Pedro.
>>
>> @Pedro, you ask an important question, "*are we ... appointing
>> volunteers while we wait for the GNSO council to act or is it better to
>> refuse to nominate someone for now*? ". I wait to hear what our members
>> think.
>>
>> On the GNSO action side of things, Find my a brief of what has transpired
>> in the council since 2019 on this topic below but I'd also like input from @Stephanie
>> Perrin <stephanie.perrin at mail.utoronto.ca> who is one of the council
>> liaisons to the PPSAI IRT:
>>
>> - As a result of potential conflicts and/or overlap of work between the
>> PPSAI IRT and GDPR-related work in EPDP on Temp Spec, in March 2019,  ICANN
>> org asked the GNSO Council, ?whether ICANN org should continue to delay
>> public comment and implementation of PPSAI or take additional steps pending
>> completion of the EPDP in consultation with the PPSAI Implementation Review
>> Team (IRT).
>> - Council responded to Org saying, ?*given the divergent views among
>> Councilors* and considering the respective roles of ICANN Org in leading
>> implementation work of consensus policy recommendations and the PPSAI IRT
>> in overseeing the implementation work, the GNSO *Council considers it
>> appropriate to defer the decision on this issue to ICANN org and the PPSAI
>> IRT*, taking into account the various views of the SOs and ACs.?
>> [emphasis added]
>> - On 2 March 2021, ICANN org delivered the Wave 1.5 Report
>> <https://mm.icann.org/pipermail/council/2021-March/024506.html> to the
>> GNSO Council, which included a detailed analysis of the extent to which the
>> EPDP Phase 1 recommendations may require modification to the PPSAI and
>> Translation & Transliteration policies, which are in the policy
>> implementation phase. Following review of the Wave 1.5 Report, the Council
>> observed the following in its 1 July 2021 letter [gnso.icann.org]
>> <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/field-file-attach/fouquart-to-lentz-01jul21-en.pdf__;!!PtGJab4!72Ceiu66uyoV0OHChjdR9frkPlBYYXnOJZ5zB8r86XzWBmEUoVf8ybKlInPdH4obWmz6r2jOJd6I6Op0U5lFnsYtCg$>
>> :
>>
>>
>>
>>    - *The decision to pause the implementation of the PPSAI and
>>    Translation & Transliteration policy recommendations was a decision that
>>    was made by ICANN org, not the GNSO Council. As such, the Council is of the
>>    view that a decision to restart the implementation activities is not within
>>    the remit of the GNSO Council but for ICANN org* to make.
>>    - *Should any policy issues arise during the implementation of these
>>    policy recommendations, there are processes and procedures that allow the
>>    Council to further consider these*, but the Council is of the view
>>    that the respective Implementation Review Teams (IRTs) will be best placed
>>    to identify such possible issues.
>>    - The Council would also like to point to the letter
>>    <https://www.icann.org/en/system/files/correspondence/namazi-to-drazek-et-al-05sep19-en.pdf>
>>    that was sent to the Council in September 2019 in which it was noted that
>>    ?following the completion of relevant EPDP work, ICANN org will reassess
>>    the existing draft PP materials in consultation with the PPSAI IRT
>>    and determine how to proceed with implementation of the Privacy and Proxy
>>    Services Accreditation Program?. From a Council?s perspective this still
>>    seems a relevant and timely next step.
>>
>> So, as you can see, the council holds the view that if there are issues
>> arising in the policy as drafted during implementation, they are confident
>> that the issues can be addressed with existing processes and procedures.
>>
>>
>> Warmly,
>> Tomslin
>>
>>
>>
>> On Tue, 28 May 2024 at 07:06, Pedro de Perdig?o Lana <
>> pedrodeperdigaolana at gmail.com> wrote:
>>
>>> Hi everyone,
>>>
>>> Regarding the strategy on how to approach this problem, are we
>>> nonetheless appointing volunteers while we wait for the GNSO council to act
>>> or is it better to refuse to nominate someone for now?
>>>
>>> Cordially,
>>>
>>> *Pedro de Perdig?o Lana*
>>> Lawyer <https://www.nic.br/>, GEDAI/UFPR <https://www.gedai.com.br/>
>>> Researcher
>>> PhD Candidate (UFPR), LLM in Business Law (UCoimbra)
>>> Board Member @ CC Brasil <https://br.creativecommons.net/>, ISOC BR
>>> <https://isoc.org.br/> and IODA <https://ioda.org.br/>
>>> This message is restricted to the sender and recipient(s). If received
>>> by mistake, please reply informing it.
>>>
>>>
>>> Em seg., 27 de mai. de 2024 ?s 11:35, Poncelet Ileleji <
>>> pileleji at jokkolabs.co> escreveu:
>>>
>>>> +1 kathy +1 Farzi, I can't agree more
>>>>
>>>> *Poncelet O. Ileleji*
>>>>
>>>> *Jokkolabs Banjul -  Lead / CEO*
>>>> *Sait Matty Road, Bakau, Adjacent to Swedish Consulate*
>>>> *KMC, The Gambia*
>>>> *P O Box 4496 Bakau,KMC, The Gambia*
>>>> *Skype: pons_utd*
>>>> *Tel Direct Office: +220 4495115*
>>>>
>>>> *Tel Mobile/Whatsapp: +220 9912508*
>>>>
>>>> *LinkedIn: Jokkolabs Banjul*
>>>> *Facebook: Jokkolabs Banjul*
>>>> *Twitter: @jBanjul*
>>>>
>>>>
>>>>
>>>>
>>>> On Mon, May 27, 2024 at 1:46?PM Kathy Kleiman <kathy at dnrc.tech> wrote:
>>>>
>>>>>  +1 to Farzi, and an Implementation Review Team (run by ICANN Staff)
>>>>> is hardly the place to state that the law has gone in a completely
>>>>> different direction since the original Policy was negotiated.  No one on
>>>>> the ICANN Board or Staff feels empowered to "stop this train" although it
>>>>> is eight years old and badly out of date.
>>>>>
>>>>> *That power rests in the GNSO Council. Can we (NCSG), through our
>>>>> Councilors, call for a legal review of the proposed PPSAI for problems (if
>>>>> any) with its underlying legal foundation in light of the adoption of GDPR
>>>>> and over half the countries of the world now following the European
>>>>> "comprehensive right of privacy"? *
>>>>>
>>>>> Best and asking all of our current Councilors (past and future ones
>>>>> too),
>>>>>
>>>>> Kathy
>>>>> On 5/27/2024 9:26 AM, farzaneh badii wrote:
>>>>>
>>>>> Hi Tomslin,
>>>>>
>>>>> This is a bit odd. Didn?t we discuss that most of those policy
>>>>> recommendations were outdated and could not be implemented? Are they hoping
>>>>> that by doing the IRT we can undertake feasibility for the recommendations?
>>>>>
>>>>> This is why I did suggest considering time limits for implementing
>>>>> policies. You can?t come up with a policy and then want to enforce it 8
>>>>> years later! Especially in the technology space, that is not possible.
>>>>>
>>>>> Best regards
>>>>>
>>>>>
>>>>> Farzaneh
>>>>>
>>>>>
>>>>> On Mon, May 27, 2024 at 5:53?AM Tomslin Samme-Nlar <
>>>>> mesumbeslin at gmail.com> wrote:
>>>>>
>>>>>> Dear members,
>>>>>>
>>>>>> There is a request from Org for SG/Cs to appoint a representative and
>>>>>> an alternate to the PPSAI IRT. We (NCSG) had concerns with the IRT going
>>>>>> ahead but as you can see, Org is still going ahead with it.
>>>>>>
>>>>>> NCSG is seeking a representative and an alternate. Please read below
>>>>>> for details of the role of the representative and on what the IRT will be
>>>>>> doing.
>>>>>>
>>>>>> Send your EOI to me (mesumbeslin at gmail.com) copying Julf (
>>>>>> julf at julf.com) and Andrea (andrea.glandon at icann.org) no later than
>>>>>> Friday May 31st 2023 for the policy committee's review.
>>>>>>
>>>>>> Warmly,
>>>>>> Tomslin
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> -------- Forwarded Message --------
>>>>>> Subject:        [GNSO-SG-C-Leadership] Appointment of representative
>>>>>> and
>>>>>> alternate to the PPSAI IRT
>>>>>> Date:   Tue, 21 May 2024 19:59:02 +0000
>>>>>> From:   Dennis Chang via GNSO-SG-C-Leadership
>>>>>> <gnso-sg-c-leadership at icann.org>
>>>>>> Reply-To:       Dennis Chang <dennis.chang at icann.org>
>>>>>> To:     gnso-sg-c-leadership at icann.org <
>>>>>> gnso-sg-c-leadership at icann.org>
>>>>>> CC:     Leon Grundmann <leon.grundmann at icann.org>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Dear All,
>>>>>>
>>>>>> Following the publication of the Call for Volunteers
>>>>>> <
>>>>>> https://www.icann.org/en/announcements/details/icann-seeks-volunteers-for-the-ppsai-implementation-review-team-20-05-2024-en>,
>>>>>>
>>>>>> the Internet Corporation for Assigned Names and Numbers (ICANN)
>>>>>> organization (org) is pleased to invite you to nominate a
>>>>>> representative
>>>>>> and an alternate to the Proxy & Privacy Services (PPSAI) policy
>>>>>> Implementation Review Team (IRT).
>>>>>>
>>>>>> The implementation process is an ICANN org-driven exercise.  ICANN
>>>>>> org
>>>>>> plans to employ the ?Open + Representative Model? piloted on the
>>>>>> Subsequent Procedures IRT and based on the GNSO?s PDP 3.0 model
>>>>>> <
>>>>>> https://gnso.icann.org/sites/default/files/file/field-file-attach/pdp-3-2-working-group-models-10feb20-en.pdf.pdf>.
>>>>>>
>>>>>> The goal is to provide a structure that allows for efficient
>>>>>> resolution
>>>>>> of issues that may occur.
>>>>>>
>>>>>> We kindly ask that your group nominate up to one representative and
>>>>>> up
>>>>>> to one alternate to participate in the IRT. Please note, we are
>>>>>> asking
>>>>>> each of ICANN?s supporting organizations, advisory committees,
>>>>>> stakeholder groups and constituencies to nominate up to one
>>>>>> representative and one alternate.
>>>>>>
>>>>>> Putting forward a representative and alternate is optional; all
>>>>>> members
>>>>>> of the GNSO Group are welcome to join the IRT as participants. In
>>>>>> fact,
>>>>>> we urge anyone who is interested in being selected as a
>>>>>> representative
>>>>>> to join the IRT as a participant first (call for volunteers
>>>>>> <
>>>>>> https://www.icann.org/en/announcements/details/icann-seeks-volunteers-for-the-ppsai-implementation-review-team-20-05-2024-en>).
>>>>>>
>>>>>> As you will see below, the roles of participants and representatives
>>>>>> are
>>>>>> nearly identical, with the representatives? main function being that
>>>>>> of
>>>>>> an information-bridge to their community groups.
>>>>>>
>>>>>> ICANN org plans to host the first IRT call during the ICANN80 public
>>>>>> meeting in June 2024. We do not require the nominees for the first
>>>>>> meeting, but request that you conclude the nomination process and
>>>>>> inform
>>>>>> us of the nominees as soon as feasible.
>>>>>>
>>>>>> Why Have Representatives?
>>>>>>
>>>>>> While participants always speak in their own personal capacity,
>>>>>> representatives are expected to speak on behalf of their
>>>>>> constituency,
>>>>>> stakeholder group, supporting organization, or advisory committee.
>>>>>> Therefore, a key part of the representative?s role will be to engage
>>>>>> actively and consistently with their colleagues to ensure they can
>>>>>> convey their group?s viewpoints to the IRT. Please note, that this
>>>>>> will
>>>>>> require an efficient process for representatives to inform and
>>>>>> receive
>>>>>> input from their respective groups. To put this into place will be
>>>>>> the
>>>>>> responsibility of each representative.
>>>>>>
>>>>>> In addition, when determining the level of consensus in the
>>>>>> circumstance
>>>>>> described in Section V.E. of the IRT Principles & Guidelines
>>>>>> <
>>>>>> https://www.icann.org/en/system/files/files/irt-principles-guidelines-23aug16-en.pdf>,
>>>>>>
>>>>>> the GNSO Liaison, in the Open + Representative model, shall take into
>>>>>> consideration that members who are representatives are expected to
>>>>>> express the viewpoint of their respective community groups and
>>>>>> participants to express their own views. This does not impact each
>>>>>> member?s ability to raise any concern they may have, nor does it
>>>>>> absolve
>>>>>> ICANN org or the GNSO Council liaison from ?exercis[ing] all
>>>>>> reasonable
>>>>>> efforts to resolve disagreements? within the IRT.
>>>>>>
>>>>>> More information can be found on this PPSAI IRT wiki page
>>>>>> <https://community.icann.org/x/lQDSEw>.  We are looking forward to
>>>>>> getting the IRT underway and, please, do not hesitate to reach out
>>>>>> should you have any questions.
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Kind Regards,
>>>>>>
>>>>>> Dennis S. Chang
>>>>>>
>>>>>> GDD Programs Director
>>>>>>
>>>>>> Phone: +1 213 293 7889
>>>>>>
>>>>>> Sykpe: dennisSchang
>>>>>>
>>>>>> www.icann.org <http://www.icann.org>  One World ? One Internet
>>>>>>
>>>>>> _______________________________________________
>>>>>> NCSG-PC mailing list
>>>>>> NCSG-PC at lists.ncsg.is
>>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>>
>>>>> --
>>>>> Kathy Kleiman
>>>>> Past President, Domain Name Rights Coalition
>>>>>
>>>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240611/dab18a35/attachment.htm>

From julf at julf.com  Tue Jun 11 16:50:14 2024
From: julf at julf.com (Johan Helsingius)
Date: Tue, 11 Jun 2024 15:50:14 +0200
Subject: [NCSG-PC] Nomcom comments
Message-ID: <11b37333-fbc4-4c43-8edd-7620581d0061@julf.com>

Here is my suggested response to Greg's question about the NomCom
changes.

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


The question is "Do you believe there would be any objections from your
groups, and potentially delegates that you have already identified, to
proceeding with a simple path forward in which we randomly select three
of seven GNSO delegates to serve one-year terms?"

We do find that the recommendations and internally inconsistent and
should not have been approved. On one hand the recommendations
call for staggered terms in order to provide continuity and to
avoid an "all new faces" situation, but then on the other hand
force all representatives to be new appointees (with reappointing
existing representatives specifically not allowed) at the beginning
of the new term structure.

We also note that the random selection of lengths of initial
terms might be appropriate for an AC like ALAC as they don't
have multiple constituencies with diverging interests and
uneven representation. We don't think it is appropriate
for the GNSO.

In addition to the issue about initial terms, we also want
to once again note another reason the recommendations should
not have been approved. In the draft recommendations there
was almost to the end a recommendation for a NomCom rebalancing.
It is our understanding that that recommendation was removed
at the last moment, based on a vote taken at one single meeting
where none of our constituencies were represented. We don't
feel that is how consensus policy should be decided.

On behalf of the NCSG, NCUC and NPOC,

	Julf Helsingius, NCSG Chair





From bruna.mrtns at gmail.com  Tue Jun 11 17:00:25 2024
From: bruna.mrtns at gmail.com (Bruna Martins dos Santos)
Date: Tue, 11 Jun 2024 16:00:25 +0200
Subject: [NCSG-PC] Nomcom comments
In-Reply-To: <11b37333-fbc4-4c43-8edd-7620581d0061@julf.com>
References: <11b37333-fbc4-4c43-8edd-7620581d0061@julf.com>
Message-ID: <CADAEEV0T6wvXwALGQGeZZcD+BYwaC+bPk3WiZLkYSLLRAbrCdg@mail.gmail.com>

Thanks for this, Julf.

I asked to add comments to the reply but the document is closed for
comments. Id maybe just add in an even clearer way that we are not onboard
with this suggestion especially in light of the fact that despite the fact
we have 2 constituencies within our SG, we only have one slot in the Nomcom
as opposed to other parts of the GNSO having two slots.

Best,
B

On Tue, Jun 11, 2024 at 3:50?PM Johan Helsingius via NCSG-PC <
ncsg-pc at lists.ncsg.is> wrote:

> Here is my suggested response to Greg's question about the NomCom
> changes.
>
> Google doc at:
>
> https://docs.google.com/document/d/1z2EIBHxO68xOklCFqw44Df8f225QCR94eDobzlXZ9CI/edit?usp=sharing
>
>
> The question is "Do you believe there would be any objections from your
> groups, and potentially delegates that you have already identified, to
> proceeding with a simple path forward in which we randomly select three
> of seven GNSO delegates to serve one-year terms?"
>
> We do find that the recommendations and internally inconsistent and
> should not have been approved. On one hand the recommendations
> call for staggered terms in order to provide continuity and to
> avoid an "all new faces" situation, but then on the other hand
> force all representatives to be new appointees (with reappointing
> existing representatives specifically not allowed) at the beginning
> of the new term structure.
>
> We also note that the random selection of lengths of initial
> terms might be appropriate for an AC like ALAC as they don't
> have multiple constituencies with diverging interests and
> uneven representation. We don't think it is appropriate
> for the GNSO.
>
> In addition to the issue about initial terms, we also want
> to once again note another reason the recommendations should
> not have been approved. In the draft recommendations there
> was almost to the end a recommendation for a NomCom rebalancing.
> It is our understanding that that recommendation was removed
> at the last moment, based on a vote taken at one single meeting
> where none of our constituencies were represented. We don't
> feel that is how consensus policy should be decided.
>
> On behalf of the NCSG, NCUC and NPOC,
>
>         Julf Helsingius, NCSG Chair
>
>
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>


-- 

*Bruna Martins dos Santos *

Global Campaigns Manager | Digital Action <http://digitalaction.co>

German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von
Humboldt Foundation <https://www.humboldt-foundation.de/>

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

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

From julf at julf.com  Tue Jun 11 17:43:58 2024
From: julf at julf.com (Johan Helsingius)
Date: Tue, 11 Jun 2024 16:43:58 +0200
Subject: [NCSG-PC] Nomcom comments
In-Reply-To: <CADAEEV0T6wvXwALGQGeZZcD+BYwaC+bPk3WiZLkYSLLRAbrCdg@mail.gmail.com>
References: <11b37333-fbc4-4c43-8edd-7620581d0061@julf.com>
 <CADAEEV0T6wvXwALGQGeZZcD+BYwaC+bPk3WiZLkYSLLRAbrCdg@mail.gmail.com>
Message-ID: <aa9a666e-30ad-492c-ab12-f7d2187d7726@julf.com>

Now anyone can comment. Not sure we need to emphasize the representation
point - we have made a lot of noise about it already, but we want to
have it formally noted.

	Julf


On 11/06/2024 16:00, Bruna Martins dos Santos wrote:
> Thanks for this, Julf.
> 
> I asked to add comments to the reply but the document is closed for 
> comments. Id maybe just add in an even clearer way that we are not 
> onboard with this suggestion?especially in light of the fact?that 
> despite the fact we have 2 constituencies within our SG, we only have 
> one slot in the Nomcom as opposed to other parts of the GNSO having two 
> slots.
> 
> Best,
> B
> 
> On Tue, Jun 11, 2024 at 3:50?PM Johan Helsingius via NCSG-PC 
> <ncsg-pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>> wrote:
> 
>     Here is my suggested response to Greg's question about the NomCom
>     changes.
> 
>     Google doc at:
>     https://docs.google.com/document/d/1z2EIBHxO68xOklCFqw44Df8f225QCR94eDobzlXZ9CI/edit?usp=sharing <https://docs.google.com/document/d/1z2EIBHxO68xOklCFqw44Df8f225QCR94eDobzlXZ9CI/edit?usp=sharing>
> 
> 
>     The question is "Do you believe there would be any objections from your
>     groups, and potentially delegates that you have already identified, to
>     proceeding with a simple path forward in which we randomly select three
>     of seven GNSO delegates to serve one-year terms?"
> 
>     We do find that the recommendations and internally inconsistent and
>     should not have been approved. On one hand the recommendations
>     call for staggered terms in order to provide continuity and to
>     avoid an "all new faces" situation, but then on the other hand
>     force all representatives to be new appointees (with reappointing
>     existing representatives specifically not allowed) at the beginning
>     of the new term structure.
> 
>     We also note that the random selection of lengths of initial
>     terms might be appropriate for an AC like ALAC as they don't
>     have multiple constituencies with diverging interests and
>     uneven representation. We don't think it is appropriate
>     for the GNSO.
> 
>     In addition to the issue about initial terms, we also want
>     to once again note another reason the recommendations should
>     not have been approved. In the draft recommendations there
>     was almost to the end a recommendation for a NomCom rebalancing.
>     It is our understanding that that recommendation was removed
>     at the last moment, based on a vote taken at one single meeting
>     where none of our constituencies were represented. We don't
>     feel that is how consensus policy should be decided.
> 
>     On behalf of the NCSG, NCUC and NPOC,
> 
>      ? ? ? ? Julf Helsingius, NCSG Chair
> 
> 
> 
>     _______________________________________________
>     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>
> 
> 
> 
> -- 
> */Bruna Martins dos Santos
> /*
> 
> Global Campaigns Manager | Digital Action <http://digitalaction.co>
> 
> German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander 
> von Humboldt Foundation <https://www.humboldt-foundation.de/>
> 
> Member | Coaliz?o Direitos na Rede <https://direitosnarede.org.br/>
> Co-Coordinator?| Internet Governance Caucus <https://igcaucus.org/>
> 
> Twitter: @boomartins <https://twitter.com/boomartins>?// Skype: 
> bruna.martinsantos
> Email: bruna.mrtns at gmail.com <mailto:bruna.mrtns at gmail.com>


From bruna.mrtns at gmail.com  Tue Jun 11 17:46:06 2024
From: bruna.mrtns at gmail.com (Bruna Martins dos Santos)
Date: Tue, 11 Jun 2024 16:46:06 +0200
Subject: [NCSG-PC] Nomcom comments
In-Reply-To: <aa9a666e-30ad-492c-ab12-f7d2187d7726@julf.com>
References: <11b37333-fbc4-4c43-8edd-7620581d0061@julf.com>
 <CADAEEV0T6wvXwALGQGeZZcD+BYwaC+bPk3WiZLkYSLLRAbrCdg@mail.gmail.com>
 <aa9a666e-30ad-492c-ab12-f7d2187d7726@julf.com>
Message-ID: <CADAEEV0sSrNux9mkQKdz6r1CzjLi4zR6NhmOU_N+Arpzquk5Lw@mail.gmail.com>

Added it w/ change marks, feel free to take it out if you want but thought
it would be another good argument.

On Tue, Jun 11, 2024 at 4:44?PM Johan Helsingius <julf at julf.com> wrote:

> Now anyone can comment. Not sure we need to emphasize the representation
> point - we have made a lot of noise about it already, but we want to
> have it formally noted.
>
>         Julf
>
>
> On 11/06/2024 16:00, Bruna Martins dos Santos wrote:
> > Thanks for this, Julf.
> >
> > I asked to add comments to the reply but the document is closed for
> > comments. Id maybe just add in an even clearer way that we are not
> > onboard with this suggestion especially in light of the fact that
> > despite the fact we have 2 constituencies within our SG, we only have
> > one slot in the Nomcom as opposed to other parts of the GNSO having two
> > slots.
> >
> > Best,
> > B
> >
> > On Tue, Jun 11, 2024 at 3:50?PM Johan Helsingius via NCSG-PC
> > <ncsg-pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>> wrote:
> >
> >     Here is my suggested response to Greg's question about the NomCom
> >     changes.
> >
> >     Google doc at:
> >
> https://docs.google.com/document/d/1z2EIBHxO68xOklCFqw44Df8f225QCR94eDobzlXZ9CI/edit?usp=sharing
> <
> https://docs.google.com/document/d/1z2EIBHxO68xOklCFqw44Df8f225QCR94eDobzlXZ9CI/edit?usp=sharing
> >
> >
> >
> >     The question is "Do you believe there would be any objections from
> your
> >     groups, and potentially delegates that you have already identified,
> to
> >     proceeding with a simple path forward in which we randomly select
> three
> >     of seven GNSO delegates to serve one-year terms?"
> >
> >     We do find that the recommendations and internally inconsistent and
> >     should not have been approved. On one hand the recommendations
> >     call for staggered terms in order to provide continuity and to
> >     avoid an "all new faces" situation, but then on the other hand
> >     force all representatives to be new appointees (with reappointing
> >     existing representatives specifically not allowed) at the beginning
> >     of the new term structure.
> >
> >     We also note that the random selection of lengths of initial
> >     terms might be appropriate for an AC like ALAC as they don't
> >     have multiple constituencies with diverging interests and
> >     uneven representation. We don't think it is appropriate
> >     for the GNSO.
> >
> >     In addition to the issue about initial terms, we also want
> >     to once again note another reason the recommendations should
> >     not have been approved. In the draft recommendations there
> >     was almost to the end a recommendation for a NomCom rebalancing.
> >     It is our understanding that that recommendation was removed
> >     at the last moment, based on a vote taken at one single meeting
> >     where none of our constituencies were represented. We don't
> >     feel that is how consensus policy should be decided.
> >
> >     On behalf of the NCSG, NCUC and NPOC,
> >
> >              Julf Helsingius, NCSG Chair
> >
> >
> >
> >     _______________________________________________
> >     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>
> >
> >
> >
> > --
> > */Bruna Martins dos Santos
> > /*
> >
> > Global Campaigns Manager | Digital Action <http://digitalaction.co>
> >
> > German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander
> > von Humboldt Foundation <https://www.humboldt-foundation.de/>
> >
> > Member | Coaliz?o Direitos na Rede <https://direitosnarede.org.br/>
> > Co-Coordinator | Internet Governance Caucus <https://igcaucus.org/>
> >
> > Twitter: @boomartins <https://twitter.com/boomartins> // Skype:
> > bruna.martinsantos
> > Email: bruna.mrtns at gmail.com <mailto:bruna.mrtns at gmail.com>
>


-- 

*Bruna Martins dos Santos *

Global Campaigns Manager | Digital Action <http://digitalaction.co>

German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von
Humboldt Foundation <https://www.humboldt-foundation.de/>

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

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

From julf at julf.com  Tue Jun 11 17:48:59 2024
From: julf at julf.com (Johan Helsingius)
Date: Tue, 11 Jun 2024 16:48:59 +0200
Subject: [NCSG-PC] Nomcom comments
In-Reply-To: <CADAEEV0sSrNux9mkQKdz6r1CzjLi4zR6NhmOU_N+Arpzquk5Lw@mail.gmail.com>
References: <11b37333-fbc4-4c43-8edd-7620581d0061@julf.com>
 <CADAEEV0T6wvXwALGQGeZZcD+BYwaC+bPk3WiZLkYSLLRAbrCdg@mail.gmail.com>
 <aa9a666e-30ad-492c-ab12-f7d2187d7726@julf.com>
 <CADAEEV0sSrNux9mkQKdz6r1CzjLi4zR6NhmOU_N+Arpzquk5Lw@mail.gmail.com>
Message-ID: <26309f2d-ca42-4d4d-8215-24ad41aa4c31@julf.com>

The argument is good, but we need to keep the two issues
(terms and representation) separate.

	Julf


On 11/06/2024 16:46, Bruna Martins dos Santos wrote:
> Added it w/ change marks, feel free to take it out if you want but 
> thought it would be another good argument.
> 
> On Tue, Jun 11, 2024 at 4:44?PM Johan Helsingius <julf at julf.com 
> <mailto:julf at julf.com>> wrote:
> 
>     Now anyone can comment. Not sure we need to emphasize the representation
>     point - we have made a lot of noise about it already, but we want to
>     have it formally noted.
> 
>      ? ? ? ? Julf
> 
> 
>     On 11/06/2024 16:00, Bruna Martins dos Santos wrote:
>      > Thanks for this, Julf.
>      >
>      > I asked to add comments to the reply but the document is closed for
>      > comments. Id maybe just add in an even clearer way that we are not
>      > onboard with this suggestion?especially in light of the fact?that
>      > despite the fact we have 2 constituencies within our SG, we only
>     have
>      > one slot in the Nomcom as opposed to other parts of the GNSO
>     having two
>      > slots.
>      >
>      > Best,
>      > B
>      >
>      > On Tue, Jun 11, 2024 at 3:50?PM Johan Helsingius via NCSG-PC
>      > <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>>> wrote:
>      >
>      >? ? ?Here is my suggested response to Greg's question about the NomCom
>      >? ? ?changes.
>      >
>      >? ? ?Google doc at:
>      >
>     https://docs.google.com/document/d/1z2EIBHxO68xOklCFqw44Df8f225QCR94eDobzlXZ9CI/edit?usp=sharing <https://docs.google.com/document/d/1z2EIBHxO68xOklCFqw44Df8f225QCR94eDobzlXZ9CI/edit?usp=sharing> <https://docs.google.com/document/d/1z2EIBHxO68xOklCFqw44Df8f225QCR94eDobzlXZ9CI/edit?usp=sharing <https://docs.google.com/document/d/1z2EIBHxO68xOklCFqw44Df8f225QCR94eDobzlXZ9CI/edit?usp=sharing>>
>      >
>      >
>      >? ? ?The question is "Do you believe there would be any objections
>     from your
>      >? ? ?groups, and potentially delegates that you have already
>     identified, to
>      >? ? ?proceeding with a simple path forward in which we randomly
>     select three
>      >? ? ?of seven GNSO delegates to serve one-year terms?"
>      >
>      >? ? ?We do find that the recommendations and internally
>     inconsistent and
>      >? ? ?should not have been approved. On one hand the recommendations
>      >? ? ?call for staggered terms in order to provide continuity and to
>      >? ? ?avoid an "all new faces" situation, but then on the other hand
>      >? ? ?force all representatives to be new appointees (with reappointing
>      >? ? ?existing representatives specifically not allowed) at the
>     beginning
>      >? ? ?of the new term structure.
>      >
>      >? ? ?We also note that the random selection of lengths of initial
>      >? ? ?terms might be appropriate for an AC like ALAC as they don't
>      >? ? ?have multiple constituencies with diverging interests and
>      >? ? ?uneven representation. We don't think it is appropriate
>      >? ? ?for the GNSO.
>      >
>      >? ? ?In addition to the issue about initial terms, we also want
>      >? ? ?to once again note another reason the recommendations should
>      >? ? ?not have been approved. In the draft recommendations there
>      >? ? ?was almost to the end a recommendation for a NomCom rebalancing.
>      >? ? ?It is our understanding that that recommendation was removed
>      >? ? ?at the last moment, based on a vote taken at one single meeting
>      >? ? ?where none of our constituencies were represented. We don't
>      >? ? ?feel that is how consensus policy should be decided.
>      >
>      >? ? ?On behalf of the NCSG, NCUC and NPOC,
>      >
>      >? ? ? ? ? ? ? Julf Helsingius, NCSG Chair
>      >
>      >
>      >
>      >? ? ?_______________________________________________
>      >? ? ?NCSG-PC mailing list
>      > NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>     <mailto:NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>>
>      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>      >? ? ?<https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>>
>      >
>      >
>      >
>      > --
>      > */Bruna Martins dos Santos
>      > /*
>      >
>      > Global Campaigns Manager | Digital Action
>     <http://digitalaction.co <http://digitalaction.co>>
>      >
>      > German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) |
>     Alexander
>      > von Humboldt Foundation <https://www.humboldt-foundation.de/
>     <https://www.humboldt-foundation.de/>>
>      >
>      > Member | Coaliz?o Direitos na Rede
>     <https://direitosnarede.org.br/ <https://direitosnarede.org.br/>>
>      > Co-Coordinator?| Internet Governance Caucus
>     <https://igcaucus.org/ <https://igcaucus.org/>>
>      >
>      > Twitter: @boomartins <https://twitter.com/boomartins
>     <https://twitter.com/boomartins>>?// Skype:
>      > bruna.martinsantos
>      > Email: bruna.mrtns at gmail.com <mailto:bruna.mrtns at gmail.com>
>     <mailto:bruna.mrtns at gmail.com <mailto:bruna.mrtns at gmail.com>>
> 
> 
> 
> -- 
> */Bruna Martins dos Santos
> /*
> 
> Global Campaigns Manager | Digital Action <http://digitalaction.co>
> 
> German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander 
> von Humboldt Foundation <https://www.humboldt-foundation.de/>
> 
> Member | Coaliz?o Direitos na Rede <https://direitosnarede.org.br/>
> Co-Coordinator?| Internet Governance Caucus <https://igcaucus.org/>
> 
> Twitter: @boomartins <https://twitter.com/boomartins>?// Skype: 
> bruna.martinsantos
> Email: bruna.mrtns at gmail.com <mailto:bruna.mrtns at gmail.com>


From julf at julf.com  Tue Jun 11 17:51:43 2024
From: julf at julf.com (Johan Helsingius)
Date: Tue, 11 Jun 2024 16:51:43 +0200
Subject: [NCSG-PC] Nomcom comments
In-Reply-To: <11b37333-fbc4-4c43-8edd-7620581d0061@julf.com>
References: <11b37333-fbc4-4c43-8edd-7620581d0061@julf.com>
Message-ID: <90bee414-c713-4452-90d0-c6a5ec65a502@julf.com>

Benjamnin and Juan,

Are you OK with the response being a joint NCSG/NCUC/NPOC one?

	Julf


On 11/06/2024 15:50, Johan Helsingius via NCSG-PC wrote:
> Here is my suggested response to Greg's question about the NomCom
> changes.
> 
> Google doc at: 
> https://docs.google.com/document/d/1z2EIBHxO68xOklCFqw44Df8f225QCR94eDobzlXZ9CI/edit?usp=sharing
> 
> 
> The question is "Do you believe there would be any objections from your
> groups, and potentially delegates that you have already identified, to
> proceeding with a simple path forward in which we randomly select three
> of seven GNSO delegates to serve one-year terms?"
> 
> We do find that the recommendations and internally inconsistent and
> should not have been approved. On one hand the recommendations
> call for staggered terms in order to provide continuity and to
> avoid an "all new faces" situation, but then on the other hand
> force all representatives to be new appointees (with reappointing
> existing representatives specifically not allowed) at the beginning
> of the new term structure.
> 
> We also note that the random selection of lengths of initial
> terms might be appropriate for an AC like ALAC as they don't
> have multiple constituencies with diverging interests and
> uneven representation. We don't think it is appropriate
> for the GNSO.
> 
> In addition to the issue about initial terms, we also want
> to once again note another reason the recommendations should
> not have been approved. In the draft recommendations there
> was almost to the end a recommendation for a NomCom rebalancing.
> It is our understanding that that recommendation was removed
> at the last moment, based on a vote taken at one single meeting
> where none of our constituencies were represented. We don't
> feel that is how consensus policy should be decided.
> 
> On behalf of the NCSG, NCUC and NPOC,
> 
>  ????Julf Helsingius, NCSG Chair
> 
> 
> 
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc


From jumaropi at yahoo.com  Tue Jun 11 21:17:36 2024
From: jumaropi at yahoo.com (Juan Manuel Rojas)
Date: Tue, 11 Jun 2024 18:17:36 +0000 (UTC)
Subject: [NCSG-PC] Nomcom comments
In-Reply-To: <90bee414-c713-4452-90d0-c6a5ec65a502@julf.com>
References: <11b37333-fbc4-4c43-8edd-7620581d0061@julf.com>
 <90bee414-c713-4452-90d0-c6a5ec65a502@julf.com>
Message-ID: <1938531715.2553110.1718129856454@mail.yahoo.com>

Hi Julf, 
It's OK for me
?Regards

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

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

Cel. +57 301 743 56 00
Instagram: jmanurojas

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




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

    El martes, 11 de junio de 2024, 04:51:50 p.?m. GMT+2, Johan Helsingius <julf at julf.com> escribi?:  
 
 Benjamnin and Juan,

Are you OK with the response being a joint NCSG/NCUC/NPOC one?

??? Julf


On 11/06/2024 15:50, Johan Helsingius via NCSG-PC wrote:
> Here is my suggested response to Greg's question about the NomCom
> changes.
> 
> Google doc at: 
> https://docs.google.com/document/d/1z2EIBHxO68xOklCFqw44Df8f225QCR94eDobzlXZ9CI/edit?usp=sharing
> 
> 
> The question is "Do you believe there would be any objections from your
> groups, and potentially delegates that you have already identified, to
> proceeding with a simple path forward in which we randomly select three
> of seven GNSO delegates to serve one-year terms?"
> 
> We do find that the recommendations and internally inconsistent and
> should not have been approved. On one hand the recommendations
> call for staggered terms in order to provide continuity and to
> avoid an "all new faces" situation, but then on the other hand
> force all representatives to be new appointees (with reappointing
> existing representatives specifically not allowed) at the beginning
> of the new term structure.
> 
> We also note that the random selection of lengths of initial
> terms might be appropriate for an AC like ALAC as they don't
> have multiple constituencies with diverging interests and
> uneven representation. We don't think it is appropriate
> for the GNSO.
> 
> In addition to the issue about initial terms, we also want
> to once again note another reason the recommendations should
> not have been approved. In the draft recommendations there
> was almost to the end a recommendation for a NomCom rebalancing.
> It is our understanding that that recommendation was removed
> at the last moment, based on a vote taken at one single meeting
> where none of our constituencies were represented. We don't
> feel that is how consensus policy should be decided.
> 
> On behalf of the NCSG, NCUC and NPOC,
> 
>? ????Julf Helsingius, NCSG Chair
> 
> 
> 
> _______________________________________________
> 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/20240611/12553246/attachment.htm>

From mesumbeslin at gmail.com  Wed Jun 12 06:24:02 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Wed, 12 Jun 2024 05:24:02 +0200
Subject: [NCSG-PC] Nomcom comments
In-Reply-To: <90bee414-c713-4452-90d0-c6a5ec65a502@julf.com>
References: <11b37333-fbc4-4c43-8edd-7620581d0061@julf.com>
 <90bee414-c713-4452-90d0-c6a5ec65a502@julf.com>
Message-ID: <CAM8DdeVQtDivW78UnmcoyJfFcXWQ9YUbOjqWfY3Mw4EGZY7dqg@mail.gmail.com>

Thanks, Julf. I am happy with it.

Warmly,
Tomslin



On Tue, 11 Jun 2024 at 16:51, Johan Helsingius via NCSG-PC <
ncsg-pc at lists.ncsg.is> wrote:

> Benjamnin and Juan,
>
> Are you OK with the response being a joint NCSG/NCUC/NPOC one?
>
>         Julf
>
>
> On 11/06/2024 15:50, Johan Helsingius via NCSG-PC wrote:
> > Here is my suggested response to Greg's question about the NomCom
> > changes.
> >
> > Google doc at:
> >
> https://docs.google.com/document/d/1z2EIBHxO68xOklCFqw44Df8f225QCR94eDobzlXZ9CI/edit?usp=sharing
> >
> >
> > The question is "Do you believe there would be any objections from your
> > groups, and potentially delegates that you have already identified, to
> > proceeding with a simple path forward in which we randomly select three
> > of seven GNSO delegates to serve one-year terms?"
> >
> > We do find that the recommendations and internally inconsistent and
> > should not have been approved. On one hand the recommendations
> > call for staggered terms in order to provide continuity and to
> > avoid an "all new faces" situation, but then on the other hand
> > force all representatives to be new appointees (with reappointing
> > existing representatives specifically not allowed) at the beginning
> > of the new term structure.
> >
> > We also note that the random selection of lengths of initial
> > terms might be appropriate for an AC like ALAC as they don't
> > have multiple constituencies with diverging interests and
> > uneven representation. We don't think it is appropriate
> > for the GNSO.
> >
> > In addition to the issue about initial terms, we also want
> > to once again note another reason the recommendations should
> > not have been approved. In the draft recommendations there
> > was almost to the end a recommendation for a NomCom rebalancing.
> > It is our understanding that that recommendation was removed
> > at the last moment, based on a vote taken at one single meeting
> > where none of our constituencies were represented. We don't
> > feel that is how consensus policy should be decided.
> >
> > On behalf of the NCSG, NCUC and NPOC,
> >
> >      Julf Helsingius, NCSG Chair
> >
> >
> >
> > _______________________________________________
> > 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/20240612/c77ba769/attachment.htm>

From benakin at gmail.com  Tue Jun 11 22:03:46 2024
From: benakin at gmail.com (Benjamin Akinmoyeje)
Date: Tue, 11 Jun 2024 21:03:46 +0200
Subject: [NCSG-PC] Nomcom comments
In-Reply-To: <1938531715.2553110.1718129856454@mail.yahoo.com>
References: <11b37333-fbc4-4c43-8edd-7620581d0061@julf.com>
 <90bee414-c713-4452-90d0-c6a5ec65a502@julf.com>
 <1938531715.2553110.1718129856454@mail.yahoo.com>
Message-ID: <CAJR4JuHksJbRRiyttrY9qfCAP1uqKJg3QprHiDjfWj46WjXBqQ@mail.gmail.com>

Dear Julf,
I am onboard with this response.

Thank you,
Benjamin

On Tue, Jun 11, 2024 at 8:19?PM Juan Manuel Rojas <jumaropi at yahoo.com>
wrote:

> Hi Julf,
> It's OK for me
>
>  Regards
>
> *JUAN MANUEL ROJAS, M.Sc.*
> Director - MINKA DIGITAL Colombia
> NPOC Chair - NCSG/GNSO
> M.Sc. Information Technology
>
> Registered Linux User No.*533108.*
> http://www.jmanurojas.com
>
>
> *Cel. +57 301 743 56 00Instagram: jmanurojas*
>
> -----BEGIN GEEK CODE BLOCK-----
> Version: 3.1
> GIT d- s: a+ C+++ UL P+ L+++ !E !W+++ !N !o K+++ w-- !O M- V PS+ PE-- Y+
> PGP+ t+ 5 X++ R tv+ b+ DI D G e+++(+++)>+++ h+ r++ y+
> ------END GEEK CODE BLOCK------
>
>
>
>
>
>
>
>
> El martes, 11 de junio de 2024, 04:51:50 p. m. GMT+2, Johan Helsingius <
> julf at julf.com> escribi?:
>
>
> Benjamnin and Juan,
>
> Are you OK with the response being a joint NCSG/NCUC/NPOC one?
>
>     Julf
>
>
> On 11/06/2024 15:50, Johan Helsingius via NCSG-PC wrote:
> > Here is my suggested response to Greg's question about the NomCom
> > changes.
> >
> > Google doc at:
> >
> https://docs.google.com/document/d/1z2EIBHxO68xOklCFqw44Df8f225QCR94eDobzlXZ9CI/edit?usp=sharing
> >
> >
> > The question is "Do you believe there would be any objections from your
> > groups, and potentially delegates that you have already identified, to
> > proceeding with a simple path forward in which we randomly select three
> > of seven GNSO delegates to serve one-year terms?"
> >
> > We do find that the recommendations and internally inconsistent and
> > should not have been approved. On one hand the recommendations
> > call for staggered terms in order to provide continuity and to
> > avoid an "all new faces" situation, but then on the other hand
> > force all representatives to be new appointees (with reappointing
> > existing representatives specifically not allowed) at the beginning
> > of the new term structure.
> >
> > We also note that the random selection of lengths of initial
> > terms might be appropriate for an AC like ALAC as they don't
> > have multiple constituencies with diverging interests and
> > uneven representation. We don't think it is appropriate
> > for the GNSO.
> >
> > In addition to the issue about initial terms, we also want
> > to once again note another reason the recommendations should
> > not have been approved. In the draft recommendations there
> > was almost to the end a recommendation for a NomCom rebalancing.
> > It is our understanding that that recommendation was removed
> > at the last moment, based on a vote taken at one single meeting
> > where none of our constituencies were represented. We don't
> > feel that is how consensus policy should be decided.
> >
> > On behalf of the NCSG, NCUC and NPOC,
> >
> >      Julf Helsingius, NCSG Chair
>
> >
> >
> >
> > _______________________________________________
> > 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/20240611/ef5b0dbc/attachment.htm>

From julf at Julf.com  Sat Jun 15 14:31:33 2024
From: julf at Julf.com (Johan Helsingius)
Date: Sat, 15 Jun 2024 13:31:33 +0200
Subject: [NCSG-PC] Fwd: ICANN81 Block Schedule, Production Timeline
In-Reply-To: <F5145518-D39A-42C2-910C-9DE778A8AE07@icann.org>
References: <F5145518-D39A-42C2-910C-9DE778A8AE07@icann.org>
Message-ID: <8f18ce87-c963-4510-9b9d-09001f363242@Julf.com>

FYI

	Julf

-------- Forwarded Message --------
Subject: 	[SOAC-Leaders-ICANNMeeting-Planning] ICANN81 Block Schedule, 
Production Timeline
From: 	Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning 
<soac-leaders-icannmeeting-planning at icann.org>
Reply-To: 	Nathalie Peregrine <nathalie.peregrine at icann.org>
To: 	soac-leaders-icannmeeting-planning at icann.org 
<soac-leaders-icannmeeting-planning at icann.org>



Dear all,

Whilst you are all busy planning for ICANN80, staff support thought it 
might be helpful for you to have access to the ICANN81 draft block 
schedule and production timeline ahead of time. ICANN81 will take place 
in Istanbul from the 9 ? 14 November 2024.

As most of you know, planning for an ICANN meeting would traditionally 
start at the end of the previous ICANN meeting for the next one. There 
are many benefits to starting planning earlier, this allows for more 
discussions about topics, new session formats and ought to make outreach 
and engagement efforts easier.

Holding ICANN81 Production Calls prior to ICANN80 may be confusing, but 
having access to a proposed block schedule and production timeline could 
trigger discussions within your own groups but also on this ICANN 
meeting planning mailing list. It may also assist with session agenda 
planning for ICANN80.

Please bear in mind the following:

   * The draft block schedule follows a thought process stemming from
     what worked at previous AGMs and equally other ICANN meetings. It
     can however be modified and tweaked according to your collective input
   * The production timeline shows an estimate of the deadlines by which
     scheduling steps should have taken place. If we can be ahead of the
     production timeline (for instance, the sharing of the block schedule
     and timeline before ICANN80), this will free up more Production Call
     time for discussion.

Please do not hesitate to provide your input here, your questions, your 
ideas for ICANN81.

We look forward to working with you on the AGM!

Kind regards,

The Schedule Team
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ICANN81 Production Timeline.pdf
Type: application/pdf
Size: 75225 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240615/3b3259dc/attachment.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ICANN81- AGM Istanbul DRAFT v.1 15 May 2024 - Sheet1.pdf
Type: application/pdf
Size: 57478 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240615/3b3259dc/attachment-0001.pdf>

From stephanie.perrin at mail.utoronto.ca  Sat Jun 15 14:58:06 2024
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Sat, 15 Jun 2024 11:58:06 +0000
Subject: [NCSG-PC] Fwd: ICANN81 Block Schedule, Production Timeline
In-Reply-To: <8f18ce87-c963-4510-9b9d-09001f363242@Julf.com>
References: <F5145518-D39A-42C2-910C-9DE778A8AE07@icann.org>
 <8f18ce87-c963-4510-9b9d-09001f363242@Julf.com>
Message-ID: <987705AC-E42F-4692-8CC9-AF6122C8C323@mail.utoronto.ca>

We should focus on this at the next pc meeting.  in the meantime, get the request for a day zero meeting for NCPH  submitted.  Manju convinced me that additional travel fir a short ncph  meeting was a pain.  Plus this meeting maximizes the presence of our councillors because of transition
Stephanie

Sent from my iPhone

> On Jun 15, 2024, at 07:32, Johan Helsingius via NCSG-PC <ncsg-pc at lists.ncsg.is> wrote:
> 
> ?FYI
> 
>    Julf
> 
> -------- Forwarded Message --------
> Subject:    [SOAC-Leaders-ICANNMeeting-Planning] ICANN81 Block Schedule, Production Timeline
> From:    Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning <soac-leaders-icannmeeting-planning at icann.org>
> Reply-To:    Nathalie Peregrine <nathalie.peregrine at icann.org>
> To:    soac-leaders-icannmeeting-planning at icann.org <soac-leaders-icannmeeting-planning at icann.org>
> 
> 
> 
> Dear all,
> 
> Whilst you are all busy planning for ICANN80, staff support thought it might be helpful for you to have access to the ICANN81 draft block schedule and production timeline ahead of time. ICANN81 will take place in Istanbul from the 9 ? 14 November 2024.
> 
> As most of you know, planning for an ICANN meeting would traditionally start at the end of the previous ICANN meeting for the next one. There are many benefits to starting planning earlier, this allows for more discussions about topics, new session formats and ought to make outreach and engagement efforts easier.
> 
> Holding ICANN81 Production Calls prior to ICANN80 may be confusing, but having access to a proposed block schedule and production timeline could trigger discussions within your own groups but also on this ICANN meeting planning mailing list. It may also assist with session agenda planning for ICANN80.
> 
> Please bear in mind the following:
> 
>  * The draft block schedule follows a thought process stemming from
>    what worked at previous AGMs and equally other ICANN meetings. It
>    can however be modified and tweaked according to your collective input
>  * The production timeline shows an estimate of the deadlines by which
>    scheduling steps should have taken place. If we can be ahead of the
>    production timeline (for instance, the sharing of the block schedule
>    and timeline before ICANN80), this will free up more Production Call
>    time for discussion.
> 
> Please do not hesitate to provide your input here, your questions, your ideas for ICANN81.
> 
> We look forward to working with you on the AGM!
> 
> Kind regards,
> 
> The Schedule Team
> <ICANN81 Production Timeline.pdf>
> <ICANN81- AGM Istanbul DRAFT v.1 15 May 2024 - Sheet1.pdf>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc

From julf at Julf.com  Tue Jun 18 17:31:41 2024
From: julf at Julf.com (Johan Helsingius)
Date: Tue, 18 Jun 2024 16:31:41 +0200
Subject: [NCSG-PC] Fwd: ICANN81 Block Schedule, Production Timeline
In-Reply-To: <987705AC-E42F-4692-8CC9-AF6122C8C323@mail.utoronto.ca>
References: <F5145518-D39A-42C2-910C-9DE778A8AE07@icann.org>
 <8f18ce87-c963-4510-9b9d-09001f363242@Julf.com>
 <987705AC-E42F-4692-8CC9-AF6122C8C323@mail.utoronto.ca>
Message-ID: <2e116845-c881-41b9-b6f6-9720f335430b@Julf.com>

We are on the case!

	Julf

On 15/06/2024 13:58, Stephanie Perrin wrote:
> We should focus on this at the next pc meeting.  in the meantime, get the request for a day zero meeting for NCPH  submitted.  Manju convinced me that additional travel fir a short ncph  meeting was a pain.  Plus this meeting maximizes the presence of our councillors because of transition
> Stephanie
> 
> Sent from my iPhone
> 
>> On Jun 15, 2024, at 07:32, Johan Helsingius via NCSG-PC <ncsg-pc at lists.ncsg.is> wrote:
>>
>> ?FYI
>>
>>     Julf
>>
>> -------- Forwarded Message --------
>> Subject:    [SOAC-Leaders-ICANNMeeting-Planning] ICANN81 Block Schedule, Production Timeline
>> From:    Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning <soac-leaders-icannmeeting-planning at icann.org>
>> Reply-To:    Nathalie Peregrine <nathalie.peregrine at icann.org>
>> To:    soac-leaders-icannmeeting-planning at icann.org <soac-leaders-icannmeeting-planning at icann.org>
>>
>>
>>
>> Dear all,
>>
>> Whilst you are all busy planning for ICANN80, staff support thought it might be helpful for you to have access to the ICANN81 draft block schedule and production timeline ahead of time. ICANN81 will take place in Istanbul from the 9 ? 14 November 2024.
>>
>> As most of you know, planning for an ICANN meeting would traditionally start at the end of the previous ICANN meeting for the next one. There are many benefits to starting planning earlier, this allows for more discussions about topics, new session formats and ought to make outreach and engagement efforts easier.
>>
>> Holding ICANN81 Production Calls prior to ICANN80 may be confusing, but having access to a proposed block schedule and production timeline could trigger discussions within your own groups but also on this ICANN meeting planning mailing list. It may also assist with session agenda planning for ICANN80.
>>
>> Please bear in mind the following:
>>
>>   * The draft block schedule follows a thought process stemming from
>>     what worked at previous AGMs and equally other ICANN meetings. It
>>     can however be modified and tweaked according to your collective input
>>   * The production timeline shows an estimate of the deadlines by which
>>     scheduling steps should have taken place. If we can be ahead of the
>>     production timeline (for instance, the sharing of the block schedule
>>     and timeline before ICANN80), this will free up more Production Call
>>     time for discussion.
>>
>> Please do not hesitate to provide your input here, your questions, your ideas for ICANN81.
>>
>> We look forward to working with you on the AGM!
>>
>> Kind regards,
>>
>> The Schedule Team
>> <ICANN81 Production Timeline.pdf>
>> <ICANN81- AGM Istanbul DRAFT v.1 15 May 2024 - Sheet1.pdf>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc


From julf at Julf.com  Thu Jun 20 18:02:04 2024
From: julf at Julf.com (Johan Helsingius)
Date: Thu, 20 Jun 2024 17:02:04 +0200
Subject: [NCSG-PC] Fwd: ICANN81 | Istanbul | Supported Travelers Database
 Due | Thursday, 11 July 2024
In-Reply-To: <599CEBD6-AC19-416E-B511-3027A2B35D9C@icann.org>
References: <599CEBD6-AC19-416E-B511-3027A2B35D9C@icann.org>
Message-ID: <d26f4c15-afc5-4661-957a-cb5149d290c7@Julf.com>

Here we go again...

Please let me know if you intend to be in Istanbul in person or not.

	Julf



-------- Forwarded Message --------
Subject: 	ICANN81 | Istanbul | Supported Travelers Database Due | 
Thursday, 11 July 2024
Date: 	Thu, 20 Jun 2024 14:02:02 +0000
From: 	Terri Agnew <terri.agnew at icann.org>
To: 	julf at julf.com <julf at julf.com>, jumaropi at yahoo.com 
<jumaropi at yahoo.com>, benakin at gmail.com <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>, philippe.fouquart at orange.com 
<philippe.fouquart at orange.com>, sdemetriou at verisign.com 
<sdemetriou at verisign.com>, John McElwaine 
<john.mcelwaine at nelsonmullins.com>, Karen Day <Karen.Day at sas.com>
CC: 	Brenda Brewer <brenda.brewer at icann.org>, gnso-secs at icann.org 
<gnso-secs at icann.org>, Zoe Bonython <secretariat at icannregistrars.org>, 
Andrea Glandon <andrea.glandon at icann.org>, Sue Schuler 
<secretariat at rysg.info>



Dear all,

In order to service your travel needs for ICANN81Istanbulin a timely 
fashion, please submit your meeting database tognso-secs at icann.org 
<mailto:gnso-secs at icann.org>by*Thursday, 11 July 2024. *It is important 
all funded travel air booking is completed by due date given in ICANN 
Travel emails.

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

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

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

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

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

*TRAVEL BOOKING PROCESS*

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

	

*WHO*

	

*WHAT*

1

	

Funded Traveler

	

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

2

	

Funded Traveler

	

Approved for Trade Regulations Review

3

	

Funded Traveler

	

Receive Travel Funding Confirmation Email from ICANN Travel Support

4

	

*Funded Traveler*

	

*Book Air Travel for meeting*

	

	

	

	

*Approved dates of Arrival and Departure*

*ARRIVAL DATE*

	

*DEPARTURE DATE*

*Friday, 08 November *

	

*Friday, 15 November*

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

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

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

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

3.Wednesday, 25 September 2024*(45 days before travel)*is the last day 
to submit additions/replacements.

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

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

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

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

Reminder:

   * GNSO supported traveler with a designated hotel accommodation
     funding, a hotel room is automatically secured for you, please *DO
     NOT* book your own hotel as it is un-reimbursable.
   * All personal data provided to ICANN org in for purposes of providing
     travel support for participants related to ICANN events will be
     processed in accordance with the ICANN Privacy Policy [icann.org]
 
<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=A_rkvV7hcBAIOU12pQX6fSkWBC6-P-bPaQDowX2oR_A&s=WwqcPGGS1mvkGHO5BjVc3E9ewPva_WoF-Snq25kq0OM&e=>. 

     Should you have any questions or concerns about this Privacy Policy
     and our privacy practices, you may contact us at privacy at icann.org
     <mailto:privacy at icann.org>.
   * As a reminder, for the AGM meeting only, incoming Councilors get
     funding, as well as the then-incumbent Councilors.
  ?Many thanks for your cooperation!

Thank you.

Kind regards,

Terri

Policy Team Supporting the GNSO



From bruna.mrtns at gmail.com  Thu Jun 20 18:06:14 2024
From: bruna.mrtns at gmail.com (Bruna Martins dos Santos)
Date: Thu, 20 Jun 2024 17:06:14 +0200
Subject: [NCSG-PC] [NCSG-EC] Fwd: ICANN81 | Istanbul | Supported
 Travelers Database Due | Thursday, 11 July 2024
In-Reply-To: <d26f4c15-afc5-4661-957a-cb5149d290c7@Julf.com>
References: <599CEBD6-AC19-416E-B511-3027A2B35D9C@icann.org>
 <d26f4c15-afc5-4661-957a-cb5149d290c7@Julf.com>
Message-ID: <CADAEEV0Ppw-V2FzP+qT+S_nF9btvK7wgQc3BL_rdvgW_wEZBcA@mail.gmail.com>

Am coming !

On Thu, Jun 20, 2024 at 5:02?PM Johan Helsingius via NCSG-EC <
ncsg-ec at lists.ncsg.is> wrote:

> Here we go again...
>
> Please let me know if you intend to be in Istanbul in person or not.
>
>         Julf
>
>
>
> -------- Forwarded Message --------
> Subject:        ICANN81 | Istanbul | Supported Travelers Database Due |
> Thursday, 11 July 2024
> Date:   Thu, 20 Jun 2024 14:02:02 +0000
> From:   Terri Agnew <terri.agnew at icann.org>
> To:     julf at julf.com <julf at julf.com>, jumaropi at yahoo.com
> <jumaropi at yahoo.com>, benakin at gmail.com <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>, philippe.fouquart at orange.com
> <philippe.fouquart at orange.com>, sdemetriou at verisign.com
> <sdemetriou at verisign.com>, John McElwaine
> <john.mcelwaine at nelsonmullins.com>, Karen Day <Karen.Day at sas.com>
> CC:     Brenda Brewer <brenda.brewer at icann.org>, gnso-secs at icann.org
> <gnso-secs at icann.org>, Zoe Bonython <secretariat at icannregistrars.org>,
> Andrea Glandon <andrea.glandon at icann.org>, Sue Schuler
> <secretariat at rysg.info>
>
>
>
> Dear all,
>
> In order to service your travel needs for ICANN81Istanbulin a timely
> fashion, please submit your meeting database tognso-secs at icann.org
> <mailto:gnso-secs at icann.org>by*Thursday, 11 July 2024. *It is important
> all funded travel air booking is completed by due date given in ICANN
> Travel emails.
>
> Please share with all funded travelers, the travel support guidelines
> wiki space: https://community.icann.org/x/lgvxAg
> <https://community.icann.org/x/lgvxAg> and highlight the communications
> responsibilities section:
>
> ICANN Travel Support attempts to reach a supported traveler four times
> before deeming the supported traveler unresponsive:
>
>   1. ICANN Travel Support sends ?welcome email.?
>   2. If there is no response after seven business days, ICANN Travel
>      Support sends a second email, copying ICANN support staff.
>   3. If there is no response five business days after the second email,
>      ICANN Travel Support sends a third email, copying ICANN support
>      staff and the community group chair.
>   4. If there is no response five business days after the third email,
>      ICANN Travel Support sends a fourth email, copying ICANN support
>      staff and the community group chair.
>
> If there is no response three days after the fourth attempt to reach the
> supported traveler, the community group may substitute another traveler.
>
> A timely response would be appreciated in view of visa issues and the
> OFAC review. The deadline for submissions is critical to allow for
> confirmed reservation numbers as required for visa and travel arrangements.
>
> *TRAVEL BOOKING PROCESS*
>
> In order for Funded Travelers to start booking travel, they MUST
> complete Steps 1, 2, and 3.
>
>
>
> *WHO*
>
>
>
> *WHAT*
>
> 1
>
>
>
> Funded Traveler
>
>
>
> Register for meeting using the Funded Traveler Registration Link
> provided by ICANN Travel Support
>
> 2
>
>
>
> Funded Traveler
>
>
>
> Approved for Trade Regulations Review
>
> 3
>
>
>
> Funded Traveler
>
>
>
> Receive Travel Funding Confirmation Email from ICANN Travel Support
>
> 4
>
>
>
> *Funded Traveler*
>
>
>
> *Book Air Travel for meeting*
>
>
>
>
>
>
>
>
>
> *Approved dates of Arrival and Departure*
>
> *ARRIVAL DATE*
>
>
>
> *DEPARTURE DATE*
>
> *Friday, 08 November *
>
>
>
> *Friday, 15 November*
>
> For air, this must be booked using either via our online booking
> platform (Concur) or official travel agency (FCM). ICANN org does not
> allow self-booking.
>
> Please note that when requesting travel support, in the interest of
> fairness and in light of budget restrictions we would like you to take
> the following into consideration:
>
> 1.Respond timely to ICANN Travel regarding your upcoming travel and book
> by deadline given in email.
>
> 2.If you require a visa to enter the country, please make sure to
> acquire your visa immediately.Follow link here
> <https://community.icann.org/x/fSfxAg> for assistance.
>
> 3.Wednesday, 25 September 2024*(45 days before travel)*is the last day
> to submit additions/replacements.
>
> 4.Requests past the deadline will be handled on a case-by-case basis by
> ICANN. All additional travelers added after the 90-day deadline are
> subject to availability, may NOT be placed in the same hotel as their
> funded traveler groups, and may not be able to attend due to visa issues.
>
> 5.If possible, please book direct travel requests. Detours and
> multi-stop trips are unfortunately not guaranteed.
>
> 6.If travelers want to extend their stay this must be done at their own
> expense and should contact the hotel directly once the ICANN hotel
> confirmation has be sent to them.
>
> 7.*Privately Booked Reservations*: ICANN will not refund or take over
> accommodations directly booked by the funded traveler. If a replacement
> has an existing hotel reservation, they will need to cancel their
> reservation and ICANN will not be able to take over their reservation.
>
> Reminder:
>
>    * GNSO supported traveler with a designated hotel accommodation
>      funding, a hotel room is automatically secured for you, please *DO
>      NOT* book your own hotel as it is un-reimbursable.
>    * All personal data provided to ICANN org in for purposes of providing
>      travel support for participants related to ICANN events will be
>      processed in accordance with the ICANN Privacy Policy [icann.org]
>
> <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=A_rkvV7hcBAIOU12pQX6fSkWBC6-P-bPaQDowX2oR_A&s=WwqcPGGS1mvkGHO5BjVc3E9ewPva_WoF-Snq25kq0OM&e=>.
>
>
>      Should you have any questions or concerns about this Privacy Policy
>      and our privacy practices, you may contact us at privacy at icann.org
>      <mailto:privacy at icann.org>.
>    * As a reminder, for the AGM meeting only, incoming Councilors get
>      funding, as well as the then-incumbent Councilors.
>    Many thanks for your cooperation!
>
> Thank you.
>
> Kind regards,
>
> Terri
>
> Policy Team Supporting the GNSO
>
> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>


-- 

*Bruna Martins dos Santos *

Global Campaigns Manager | Digital Action <http://digitalaction.co>

German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von
Humboldt Foundation <https://www.humboldt-foundation.de/>

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

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

From stephanie.perrin at mail.utoronto.ca  Thu Jun 20 19:52:24 2024
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Thu, 20 Jun 2024 16:52:24 +0000
Subject: [NCSG-PC] [NCSG-EC] Fwd: ICANN81 | Istanbul | Supported
 Travelers Database Due | Thursday, 11 July 2024
In-Reply-To: <CADAEEV0Ppw-V2FzP+qT+S_nF9btvK7wgQc3BL_rdvgW_wEZBcA@mail.gmail.com>
References: <599CEBD6-AC19-416E-B511-3027A2B35D9C@icann.org>
 <d26f4c15-afc5-4661-957a-cb5149d290c7@Julf.com>
 <CADAEEV0Ppw-V2FzP+qT+S_nF9btvK7wgQc3BL_rdvgW_wEZBcA@mail.gmail.com>
Message-ID: <1FD565A1-3505-47C8-983E-A6F67CBC24CA@mail.utoronto.ca>

I intend to be there, this will be my last meeting.  Looking forward to seeing you all one last time!
Cheers Stephanie

On Jun 20, 2024, at 11:06?AM, Bruna Martins dos Santos <bruna.mrtns at gmail.com> wrote:

Am coming !

On Thu, Jun 20, 2024 at 5:02?PM Johan Helsingius via NCSG-EC <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>> wrote:
Here we go again...

Please let me know if you intend to be in Istanbul in person or not.

        Julf



-------- Forwarded Message --------
Subject:        ICANN81 | Istanbul | Supported Travelers Database Due |
Thursday, 11 July 2024
Date:   Thu, 20 Jun 2024 14:02:02 +0000
From:   Terri Agnew <terri.agnew at icann.org<mailto:terri.agnew at icann.org>>
To:     julf at julf.com<mailto:julf at julf.com> <julf at julf.com<mailto:julf at julf.com>>, jumaropi at yahoo.com<mailto:jumaropi at yahoo.com>
<jumaropi at yahoo.com<mailto:jumaropi at yahoo.com>>, benakin at gmail.com<mailto:benakin at gmail.com> <benakin at gmail.com<mailto:benakin at gmail.com>>,
chair at rysg.info<mailto:chair at rysg.info> <chair at rysg.info<mailto:chair at rysg.info>>, aheineman at godaddy.com<mailto:aheineman at godaddy.com>
<aheineman at godaddy.com<mailto:aheineman at godaddy.com>>, mcole at perkinscoie.com<mailto:mcole at perkinscoie.com> <mcole at perkinscoie.com<mailto:mcole at perkinscoie.com>>,
lschulman at inta.org<mailto:lschulman at inta.org> <lschulman at inta.org<mailto:lschulman at inta.org>>, philippe.fouquart at orange.com<mailto:philippe.fouquart at orange.com>
<philippe.fouquart at orange.com<mailto:philippe.fouquart at orange.com>>, sdemetriou at verisign.com<mailto:sdemetriou at verisign.com>
<sdemetriou at verisign.com<mailto:sdemetriou at verisign.com>>, John McElwaine
<john.mcelwaine at nelsonmullins.com<mailto:john.mcelwaine at nelsonmullins.com>>, Karen Day <Karen.Day at sas.com<mailto:Karen.Day at sas.com>>
CC:     Brenda Brewer <brenda.brewer at icann.org<mailto:brenda.brewer at icann.org>>, gnso-secs at icann.org<mailto:gnso-secs at icann.org>
<gnso-secs at icann.org<mailto:gnso-secs at icann.org>>, Zoe Bonython <secretariat at icannregistrars.org<mailto:secretariat at icannregistrars.org>>,
Andrea Glandon <andrea.glandon at icann.org<mailto:andrea.glandon at icann.org>>, Sue Schuler
<secretariat at rysg.info<mailto:secretariat at rysg.info>>



Dear all,

In order to service your travel needs for ICANN81Istanbulin a timely
fashion, please submit your meeting database tognso-secs at icann.org<mailto:tognso-secs at icann.org>
<mailto:gnso-secs at icann.org<mailto:gnso-secs at icann.org>>by*Thursday, 11 July 2024. *It is important
all funded travel air booking is completed by due date given in ICANN
Travel emails.

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

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

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

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

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

*TRAVEL BOOKING PROCESS*

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



*WHO*



*WHAT*

1



Funded Traveler



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

2



Funded Traveler



Approved for Trade Regulations Review

3



Funded Traveler



Receive Travel Funding Confirmation Email from ICANN Travel Support

4



*Funded Traveler*



*Book Air Travel for meeting*









*Approved dates of Arrival and Departure*

*ARRIVAL DATE*



*DEPARTURE DATE*

*Friday, 08 November *



*Friday, 15 November*

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

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

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

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

3.Wednesday, 25 September 2024*(45 days before travel)*is the last day
to submit additions/replacements.

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

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

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

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

Reminder:

   * GNSO supported traveler with a designated hotel accommodation
     funding, a hotel room is automatically secured for you, please *DO
     NOT* book your own hotel as it is un-reimbursable.
   * All personal data provided to ICANN org in for purposes of providing
     travel support for participants related to ICANN events will be
     processed in accordance with the ICANN Privacy Policy [icann.org<http://icann.org/>]

<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=A_rkvV7hcBAIOU12pQX6fSkWBC6-P-bPaQDowX2oR_A&s=WwqcPGGS1mvkGHO5BjVc3E9ewPva_WoF-Snq25kq0OM&e=>.

     Should you have any questions or concerns about this Privacy Policy
     and our privacy practices, you may contact us at privacy at icann.org<mailto:privacy at icann.org>
     <mailto:privacy at icann.org<mailto:privacy at icann.org>>.
   * As a reminder, for the AGM meeting only, incoming Councilors get
     funding, as well as the then-incumbent Councilors.
   Many thanks for your cooperation!

Thank you.

Kind regards,

Terri

Policy Team Supporting the GNSO

_______________________________________________
NCSG-EC mailing list
NCSG-EC at lists.ncsg.is<mailto:NCSG-EC at lists.ncsg.is>
https://lists.ncsg.is/mailman/listinfo/ncsg-ec


--
Bruna Martins dos Santos

Global Campaigns Manager | Digital Action<http://digitalaction.co/>

German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von Humboldt Foundation<https://www.humboldt-foundation.de/>
Member | Coaliz?o Direitos na Rede<https://direitosnarede.org.br/>
Co-Coordinator | Internet Governance Caucus <https://igcaucus.org/>

Twitter: @boomartins<https://twitter.com/boomartins> // Skype: bruna.martinsantos
Email: bruna.mrtns at gmail.com<mailto:bruna.mrtns at gmail.com>
_______________________________________________
NCSG-PC mailing list
NCSG-PC at lists.ncsg.is<mailto:NCSG-PC at lists.ncsg.is>
https://lists.ncsg.is/mailman/listinfo/ncsg-pc

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

From wisdom.dk at gmail.com  Thu Jun 20 21:59:14 2024
From: wisdom.dk at gmail.com (Wisdom Donkor)
Date: Thu, 20 Jun 2024 20:59:14 +0200
Subject: [NCSG-PC] Fwd: ICANN81 | Istanbul | Supported Travelers
 Database Due | Thursday, 11 July 2024
In-Reply-To: <d26f4c15-afc5-4661-957a-cb5149d290c7@Julf.com>
References: <599CEBD6-AC19-416E-B511-3027A2B35D9C@icann.org>
 <d26f4c15-afc5-4661-957a-cb5149d290c7@Julf.com>
Message-ID: <CAAU+vPGR+whO5fTJph8GCbB=JGtGnvOwFeXzAhmSTHZrVjG39Q@mail.gmail.com>

I will attend in person.

On Thu, 20 Jun 2024, 5:02?pm Johan Helsingius via NCSG-PC, <
ncsg-pc at lists.ncsg.is> wrote:

> Here we go again...
>
> Please let me know if you intend to be in Istanbul in person or not.
>
>         Julf
>
>
>
> -------- Forwarded Message --------
> Subject:        ICANN81 | Istanbul | Supported Travelers Database Due |
> Thursday, 11 July 2024
> Date:   Thu, 20 Jun 2024 14:02:02 +0000
> From:   Terri Agnew <terri.agnew at icann.org>
> To:     julf at julf.com <julf at julf.com>, jumaropi at yahoo.com
> <jumaropi at yahoo.com>, benakin at gmail.com <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>, philippe.fouquart at orange.com
> <philippe.fouquart at orange.com>, sdemetriou at verisign.com
> <sdemetriou at verisign.com>, John McElwaine
> <john.mcelwaine at nelsonmullins.com>, Karen Day <Karen.Day at sas.com>
> CC:     Brenda Brewer <brenda.brewer at icann.org>, gnso-secs at icann.org
> <gnso-secs at icann.org>, Zoe Bonython <secretariat at icannregistrars.org>,
> Andrea Glandon <andrea.glandon at icann.org>, Sue Schuler
> <secretariat at rysg.info>
>
>
>
> Dear all,
>
> In order to service your travel needs for ICANN81Istanbulin a timely
> fashion, please submit your meeting database tognso-secs at icann.org
> <mailto:gnso-secs at icann.org>by*Thursday, 11 July 2024. *It is important
> all funded travel air booking is completed by due date given in ICANN
> Travel emails.
>
> Please share with all funded travelers, the travel support guidelines
> wiki space: https://community.icann.org/x/lgvxAg
> <https://community.icann.org/x/lgvxAg> and highlight the communications
> responsibilities section:
>
> ICANN Travel Support attempts to reach a supported traveler four times
> before deeming the supported traveler unresponsive:
>
>   1. ICANN Travel Support sends ?welcome email.?
>   2. If there is no response after seven business days, ICANN Travel
>      Support sends a second email, copying ICANN support staff.
>   3. If there is no response five business days after the second email,
>      ICANN Travel Support sends a third email, copying ICANN support
>      staff and the community group chair.
>   4. If there is no response five business days after the third email,
>      ICANN Travel Support sends a fourth email, copying ICANN support
>      staff and the community group chair.
>
> If there is no response three days after the fourth attempt to reach the
> supported traveler, the community group may substitute another traveler.
>
> A timely response would be appreciated in view of visa issues and the
> OFAC review. The deadline for submissions is critical to allow for
> confirmed reservation numbers as required for visa and travel arrangements.
>
> *TRAVEL BOOKING PROCESS*
>
> In order for Funded Travelers to start booking travel, they MUST
> complete Steps 1, 2, and 3.
>
>
>
> *WHO*
>
>
>
> *WHAT*
>
> 1
>
>
>
> Funded Traveler
>
>
>
> Register for meeting using the Funded Traveler Registration Link
> provided by ICANN Travel Support
>
> 2
>
>
>
> Funded Traveler
>
>
>
> Approved for Trade Regulations Review
>
> 3
>
>
>
> Funded Traveler
>
>
>
> Receive Travel Funding Confirmation Email from ICANN Travel Support
>
> 4
>
>
>
> *Funded Traveler*
>
>
>
> *Book Air Travel for meeting*
>
>
>
>
>
>
>
>
>
> *Approved dates of Arrival and Departure*
>
> *ARRIVAL DATE*
>
>
>
> *DEPARTURE DATE*
>
> *Friday, 08 November *
>
>
>
> *Friday, 15 November*
>
> For air, this must be booked using either via our online booking
> platform (Concur) or official travel agency (FCM). ICANN org does not
> allow self-booking.
>
> Please note that when requesting travel support, in the interest of
> fairness and in light of budget restrictions we would like you to take
> the following into consideration:
>
> 1.Respond timely to ICANN Travel regarding your upcoming travel and book
> by deadline given in email.
>
> 2.If you require a visa to enter the country, please make sure to
> acquire your visa immediately.Follow link here
> <https://community.icann.org/x/fSfxAg> for assistance.
>
> 3.Wednesday, 25 September 2024*(45 days before travel)*is the last day
> to submit additions/replacements.
>
> 4.Requests past the deadline will be handled on a case-by-case basis by
> ICANN. All additional travelers added after the 90-day deadline are
> subject to availability, may NOT be placed in the same hotel as their
> funded traveler groups, and may not be able to attend due to visa issues.
>
> 5.If possible, please book direct travel requests. Detours and
> multi-stop trips are unfortunately not guaranteed.
>
> 6.If travelers want to extend their stay this must be done at their own
> expense and should contact the hotel directly once the ICANN hotel
> confirmation has be sent to them.
>
> 7.*Privately Booked Reservations*: ICANN will not refund or take over
> accommodations directly booked by the funded traveler. If a replacement
> has an existing hotel reservation, they will need to cancel their
> reservation and ICANN will not be able to take over their reservation.
>
> Reminder:
>
>    * GNSO supported traveler with a designated hotel accommodation
>      funding, a hotel room is automatically secured for you, please *DO
>      NOT* book your own hotel as it is un-reimbursable.
>    * All personal data provided to ICANN org in for purposes of providing
>      travel support for participants related to ICANN events will be
>      processed in accordance with the ICANN Privacy Policy [icann.org]
>
> <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=A_rkvV7hcBAIOU12pQX6fSkWBC6-P-bPaQDowX2oR_A&s=WwqcPGGS1mvkGHO5BjVc3E9ewPva_WoF-Snq25kq0OM&e=>.
>
>
>      Should you have any questions or concerns about this Privacy Policy
>      and our privacy practices, you may contact us at privacy at icann.org
>      <mailto:privacy at icann.org>.
>    * As a reminder, for the AGM meeting only, incoming Councilors get
>      funding, as well as the then-incumbent Councilors.
>    Many thanks for your cooperation!
>
> Thank you.
>
> Kind regards,
>
> Terri
>
> Policy Team Supporting the GNSO
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240620/05c29e5c/attachment.htm>

From mesumbeslin at gmail.com  Sat Jun 22 03:40:31 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Sat, 22 Jun 2024 10:40:31 +1000
Subject: [NCSG-PC] Volunteers to the Pilot Holistic Review Team
In-Reply-To: <CAM8DdeXPcRSYFgvRfjz5OPf+RU154vP8kCGnOEf3K84utv52Kg@mail.gmail.com>
References: <CAM8DdeXPcRSYFgvRfjz5OPf+RU154vP8kCGnOEf3K84utv52Kg@mail.gmail.com>
Message-ID: <CAM8DdeXWqFtVBTjhXPnq-o-KSc3E1OXv+yLd85C_DDs4LD2krQ@mail.gmail.com>

Hi all,

**(Included all our SSC reps and chairs)

Regarding the candidates for the Pilot Holistic Review, I checked with
staff whether SG/Cs will endorse candidates and the response I got is that
"the applications aren?t associated with a SG/C and they don?t come in with
endorsements so they will be evaluated by the SSC on their merits".

With that in mind, I wanted to bring to our SSC reps attention the
importance to ensure that atleast two(2) of the seven (7) appointees
allowed for GNSO must be from NCSG, since there are a total of 7
constituencies in GNSO.

The list of applicants have been posted here:
https://community.icann.org/display/atrt/Review+Team+Applicants

We have 8 NCSG members (3 NPOC and 5 NCUC) who've applied. They are:
1. Emmanuel Nnaemeka Vitus - NPOC
2. James Gannon - NCUC
3. Pedro Lana - NCUC
4. Poncelet Ileleji - NPOC
5. Caleb Ogundele - NPOC
6. Julf (Johan) Helsingius - NCUC
7. Akinmoyeje Benjamin - NCUC
8. Bekono Pascal - NCUC

We need at least 1 from NCUC and 1 from NPOC. Should we instruct our SSC
reps who our preferred 2 are or should we leave it at the discretion of the
SSC to ensure that atleast one us selected from each of our constituencies?

Warmly,
Tomslin

On Fri, 7 June 2024, 19:25 Tomslin Samme-Nlar, <mesumbeslin at gmail.com>
wrote:

> Hi members,
>
> I want to bring to your attention this call from ICANN for volunteers to
> the Pilot Holistic Review Team that will commence work on 25 September
> 2024. Each SO/AC is entitled to nominate up to 7 applicants, so the
> selection process in our case will be at the GNSO level.
>
> Volunteers may apply by filling out an Application Form here
> https://forms.gle/TzUAz2p6K8TU8utZ9 . ICANN encourages volunteers to
> apply by the closing date, 19 June 2024.
>
> Warmly,
> Tomslin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240622/f86a9de6/attachment.htm>

From julf at Julf.com  Sat Jun 22 12:03:34 2024
From: julf at Julf.com (Johan Helsingius)
Date: Sat, 22 Jun 2024 11:03:34 +0200
Subject: [NCSG-PC] Volunteers to the Pilot Holistic Review Team
In-Reply-To: <CAM8DdeXWqFtVBTjhXPnq-o-KSc3E1OXv+yLd85C_DDs4LD2krQ@mail.gmail.com>
References: <CAM8DdeXPcRSYFgvRfjz5OPf+RU154vP8kCGnOEf3K84utv52Kg@mail.gmail.com>
 <CAM8DdeXWqFtVBTjhXPnq-o-KSc3E1OXv+yLd85C_DDs4LD2krQ@mail.gmail.com>
Message-ID: <8078e9be-4604-4707-bb3a-b64ff2d2f00c@Julf.com>

1. I think we should do both. Indicate our preference, but also add
"but at least make sure we get 2 reps".

2. Seeing we have enough volunteers, I am happy to withdraw.

I am a bit surprised to see myself labelled as "NCUC" - nothing
wrong with that, but NCSG can't have a rep? And who picked
NCUC for me - it could just as well have been NPOC?

	Julf


On 22/06/2024 02:40, Tomslin Samme-Nlar wrote:
> Hi all,
> 
> **(Included all our SSC reps and chairs)
> 
> Regarding the candidates for the Pilot Holistic Review, I checked with 
> staff whether SG/Cs will endorse candidates and the response I got is 
> that "the applications aren?t associated with a SG/C and they don?t come 
> in with endorsements so they will be evaluated by the SSC on their merits".
> 
> With that in mind, I wanted to bring to our SSC reps attention the 
> importance to ensure that atleast two(2) of the seven (7) appointees 
> allowed for GNSO must be from NCSG, since there are a total of 7 
> constituencies in GNSO.
> 
> The list of applicants have been posted here: 
> https://community.icann.org/display/atrt/Review+Team+Applicants 
> <https://community.icann.org/display/atrt/Review+Team+Applicants>
> 
> We have 8 NCSG members (3 NPOC and 5 NCUC) who've applied. They are:
> 1. Emmanuel Nnaemeka Vitus - NPOC
> 2. James Gannon - NCUC
> 3. Pedro Lana - NCUC
> 4.?Poncelet Ileleji - NPOC
> 5. Caleb Ogundele - NPOC
> 6. Julf (Johan) Helsingius - NCUC
> 7.?Akinmoyeje Benjamin - NCUC
> 8. Bekono Pascal - NCUC
> 
> We need at least 1 from NCUC and 1 from NPOC. Should we instruct our SSC 
> reps who our preferred 2 are or should we leave it at the discretion of 
> the SSC to ensure that atleast one us selected from each of our 
> constituencies?
> 
> Warmly,
> Tomslin
> 
> On Fri, 7 June 2024, 19:25 Tomslin Samme-Nlar, <mesumbeslin at gmail.com 
> <mailto:mesumbeslin at gmail.com>> wrote:
> 
>     Hi members,
> 
>     I want to bring to your attention this call from ICANN for
>     volunteers to the Pilot Holistic Review Team that will commence work
>     on 25 September 2024. Each SO/AC is entitled to nominate up to 7
>     applicants, so the selection process in our case will be at the GNSO
>     level.
> 
>     Volunteers may apply by filling out an Application Form here
>     https://forms.gle/TzUAz2p6K8TU8utZ9
>     <https://forms.gle/TzUAz2p6K8TU8utZ9> . ICANN encourages volunteers
>     to apply by the closing date, 19 June 2024.
> 
>     Warmly,
>     Tomslin
> 


From jumaropi at yahoo.com  Sat Jun 22 21:27:35 2024
From: jumaropi at yahoo.com (Juan Manuel Rojas)
Date: Sat, 22 Jun 2024 18:27:35 +0000 (UTC)
Subject: [NCSG-PC] Volunteers to the Pilot Holistic Review Team
In-Reply-To: <8078e9be-4604-4707-bb3a-b64ff2d2f00c@Julf.com>
References: <CAM8DdeXPcRSYFgvRfjz5OPf+RU154vP8kCGnOEf3K84utv52Kg@mail.gmail.com>
 <CAM8DdeXWqFtVBTjhXPnq-o-KSc3E1OXv+yLd85C_DDs4LD2krQ@mail.gmail.com>
 <8078e9be-4604-4707-bb3a-b64ff2d2f00c@Julf.com>
Message-ID: <310805442.4932982.1719080855521@mail.yahoo.com>

Hi Julf,For NPOC, Caleb volunteered. But I'm bit confused with the process. We haven't sent nothing about it yet.?


Yahoo Mail: Search, Organize, Conquer 
 
  On Sat, Jun 22, 2024 at 4:03, Johan Helsingius<julf at Julf.com> wrote:   1. I think we should do both. Indicate our preference, but also add
"but at least make sure we get 2 reps".

2. Seeing we have enough volunteers, I am happy to withdraw.

I am a bit surprised to see myself labelled as "NCUC" - nothing
wrong with that, but NCSG can't have a rep? And who picked
NCUC for me - it could just as well have been NPOC?

??? Julf


On 22/06/2024 02:40, Tomslin Samme-Nlar wrote:
> Hi all,
> 
> **(Included all our SSC reps and chairs)
> 
> Regarding the candidates for the Pilot Holistic Review, I checked with 
> staff whether SG/Cs will endorse candidates and the response I got is 
> that "the applications aren?t associated with a SG/C and they don?t come 
> in with endorsements so they will be evaluated by the SSC on their merits".
> 
> With that in mind, I wanted to bring to our SSC reps attention the 
> importance to ensure that atleast two(2) of the seven (7) appointees 
> allowed for GNSO must be from NCSG, since there are a total of 7 
> constituencies in GNSO.
> 
> The list of applicants have been posted here: 
> https://community.icann.org/display/atrt/Review+Team+Applicants 
> <https://community.icann.org/display/atrt/Review+Team+Applicants>
> 
> We have 8 NCSG members (3 NPOC and 5 NCUC) who've applied. They are:
> 1. Emmanuel Nnaemeka Vitus - NPOC
> 2. James Gannon - NCUC
> 3. Pedro Lana - NCUC
> 4.?Poncelet Ileleji - NPOC
> 5. Caleb Ogundele - NPOC
> 6. Julf (Johan) Helsingius - NCUC
> 7.?Akinmoyeje Benjamin - NCUC
> 8. Bekono Pascal - NCUC
> 
> We need at least 1 from NCUC and 1 from NPOC. Should we instruct our SSC 
> reps who our preferred 2 are or should we leave it at the discretion of 
> the SSC to ensure that atleast one us selected from each of our 
> constituencies?
> 
> Warmly,
> Tomslin
> 
> On Fri, 7 June 2024, 19:25 Tomslin Samme-Nlar, <mesumbeslin at gmail.com 
> <mailto:mesumbeslin at gmail.com>> wrote:
> 
>? ? Hi members,
> 
>? ? I want to bring to your attention this call from ICANN for
>? ? volunteers to the Pilot Holistic Review Team that will commence work
>? ? on 25 September 2024. Each SO/AC is entitled to nominate up to 7
>? ? applicants, so the selection process in our case will be at the GNSO
>? ? level.
> 
>? ? Volunteers may apply by filling out an Application Form here
>? ? https://forms.gle/TzUAz2p6K8TU8utZ9
>? ? <https://forms.gle/TzUAz2p6K8TU8utZ9> . ICANN encourages volunteers
>? ? to apply by the closing date, 19 June 2024.
> 
>? ? Warmly,
>? ? Tomslin
> 
  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240622/fff6ff39/attachment.htm>

From julf at Julf.com  Sat Jun 22 22:04:11 2024
From: julf at Julf.com (Johan Helsingius)
Date: Sat, 22 Jun 2024 21:04:11 +0200
Subject: [NCSG-PC] Volunteers to the Pilot Holistic Review Team
In-Reply-To: <310805442.4932982.1719080855521@mail.yahoo.com>
References: <CAM8DdeXPcRSYFgvRfjz5OPf+RU154vP8kCGnOEf3K84utv52Kg@mail.gmail.com>
 <CAM8DdeXWqFtVBTjhXPnq-o-KSc3E1OXv+yLd85C_DDs4LD2krQ@mail.gmail.com>
 <8078e9be-4604-4707-bb3a-b64ff2d2f00c@Julf.com>
 <310805442.4932982.1719080855521@mail.yahoo.com>
Message-ID: <0b215948-8487-4ec5-b00f-39075713e214@Julf.com>

Candidates apply directly through the ICANN website. We don't get to
see any of it - it all goes through council/SSC.

	Julf


On 22/06/2024 20:27, Juan Manuel Rojas wrote:
> Hi Julf,
> For NPOC, Caleb volunteered. But I'm bit confused with the process. We 
> haven't sent nothing about it yet.
> 
> 
> 
> Yahoo Mail: Search, Organize, Conquer 
> <https://mail.onelink.me/107872968?pid=NativePlacement&c=Global_Acquisition_YMktg_315_EmailSignatureGrowth_YahooMail:Search,Organize,Conquer&af_sub1=Acquisition&af_sub2=Global_YMktg&af_sub3=&af_sub4=100000945&af_sub5=OrganizeConquer__Static_>
> 
>     On Sat, Jun 22, 2024 at 4:03, Johan Helsingius
>     <julf at Julf.com> wrote:
>     1. I think we should do both. Indicate our preference, but also add
>     "but at least make sure we get 2 reps".
> 
>     2. Seeing we have enough volunteers, I am happy to withdraw.
> 
>     I am a bit surprised to see myself labelled as "NCUC" - nothing
>     wrong with that, but NCSG can't have a rep? And who picked
>     NCUC for me - it could just as well have been NPOC?
> 
>      ??? Julf
> 
> 
>     On 22/06/2024 02:40, Tomslin Samme-Nlar wrote:
>      > Hi all,
>      >
>      > **(Included all our SSC reps and chairs)
>      >
>      > Regarding the candidates for the Pilot Holistic Review, I checked
>     with
>      > staff whether SG/Cs will endorse candidates and the response I
>     got is
>      > that "the applications aren?t associated with a SG/C and they
>     don?t come
>      > in with endorsements so they will be evaluated by the SSC on
>     their merits".
>      >
>      > With that in mind, I wanted to bring to our SSC reps attention the
>      > importance to ensure that atleast two(2) of the seven (7) appointees
>      > allowed for GNSO must be from NCSG, since there are a total of 7
>      > constituencies in GNSO.
>      >
>      > The list of applicants have been posted here:
>      > https://community.icann.org/display/atrt/Review+Team+Applicants
>     <https://community.icann.org/display/atrt/Review+Team+Applicants>
>      > <https://community.icann.org/display/atrt/Review+Team+Applicants
>     <https://community.icann.org/display/atrt/Review+Team+Applicants>>
>      >
>      > We have 8 NCSG members (3 NPOC and 5 NCUC) who've applied. They are:
>      > 1. Emmanuel Nnaemeka Vitus - NPOC
>      > 2. James Gannon - NCUC
>      > 3. Pedro Lana - NCUC
>      > 4.?Poncelet Ileleji - NPOC
>      > 5. Caleb Ogundele - NPOC
>      > 6. Julf (Johan) Helsingius - NCUC
>      > 7.?Akinmoyeje Benjamin - NCUC
>      > 8. Bekono Pascal - NCUC
>      >
>      > We need at least 1 from NCUC and 1 from NPOC. Should we instruct
>     our SSC
>      > reps who our preferred 2 are or should we leave it at the
>     discretion of
>      > the SSC to ensure that atleast one us selected from each of our
>      > constituencies?
>      >
>      > Warmly,
>      > Tomslin
>      >
>      > On Fri, 7 June 2024, 19:25 Tomslin Samme-Nlar,
>     <mesumbeslin at gmail.com <mailto:mesumbeslin at gmail.com>
>      > <mailto:mesumbeslin at gmail.com>> wrote:
> 
>      >
>      >? ? Hi members,
>      >
>      >? ? I want to bring to your attention this call from ICANN for
>      >? ? volunteers to the Pilot Holistic Review Team that will
>     commence work
>      >? ? on 25 September 2024. Each SO/AC is entitled to nominate up to 7
>      >? ? applicants, so the selection process in our case will be at
>     the GNSO
>      >? ? level.
>      >
>      >? ? Volunteers may apply by filling out an Application Form here
>      > https://forms.gle/TzUAz2p6K8TU8utZ9
>     <https://forms.gle/TzUAz2p6K8TU8utZ9>
>      >? ? <https://forms.gle/TzUAz2p6K8TU8utZ9
>     <https://forms.gle/TzUAz2p6K8TU8utZ9>> . ICANN encourages volunteers
>      >? ? to apply by the closing date, 19 June 2024.
>      >
>      >? ? Warmly,
>      >? ? Tomslin
>      >
> 


From mesumbeslin at gmail.com  Sun Jun 23 08:57:43 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Sun, 23 Jun 2024 15:57:43 +1000
Subject: [NCSG-PC] Volunteers to the Pilot Holistic Review Team
In-Reply-To: <8078e9be-4604-4707-bb3a-b64ff2d2f00c@Julf.com>
References: <CAM8DdeXPcRSYFgvRfjz5OPf+RU154vP8kCGnOEf3K84utv52Kg@mail.gmail.com>
 <CAM8DdeXWqFtVBTjhXPnq-o-KSc3E1OXv+yLd85C_DDs4LD2krQ@mail.gmail.com>
 <8078e9be-4604-4707-bb3a-b64ff2d2f00c@Julf.com>
Message-ID: <CAM8DdeUV6vyxu80kPBSswU86Yf08r82A7G9eZW6_ULg=CtUYjg@mail.gmail.com>

@Johan Helsingius <julf at julf.com>  I picked NCUC for you ? only for the
sake of our internal choice. The website does not differentiate SG or C.
Forgive me if I got it wrong.



Warmly,
Tomslin

On Sat, 22 June 2024, 19:03 Johan Helsingius, <julf at julf.com> wrote:

> 1. I think we should do both. Indicate our preference, but also add
> "but at least make sure we get 2 reps".
>
> 2. Seeing we have enough volunteers, I am happy to withdraw.
>
> I am a bit surprised to see myself labelled as "NCUC" - nothing
> wrong with that, but NCSG can't have a rep? And who picked
> NCUC for me - it could just as well have been NPOC?
>
>         Julf
>
>
> On 22/06/2024 02:40, Tomslin Samme-Nlar wrote:
> > Hi all,
> >
> > **(Included all our SSC reps and chairs)
> >
> > Regarding the candidates for the Pilot Holistic Review, I checked with
> > staff whether SG/Cs will endorse candidates and the response I got is
> > that "the applications aren?t associated with a SG/C and they don?t come
> > in with endorsements so they will be evaluated by the SSC on their
> merits".
> >
> > With that in mind, I wanted to bring to our SSC reps attention the
> > importance to ensure that atleast two(2) of the seven (7) appointees
> > allowed for GNSO must be from NCSG, since there are a total of 7
> > constituencies in GNSO.
> >
> > The list of applicants have been posted here:
> > https://community.icann.org/display/atrt/Review+Team+Applicants
> > <https://community.icann.org/display/atrt/Review+Team+Applicants>
> >
> > We have 8 NCSG members (3 NPOC and 5 NCUC) who've applied. They are:
> > 1. Emmanuel Nnaemeka Vitus - NPOC
> > 2. James Gannon - NCUC
> > 3. Pedro Lana - NCUC
> > 4. Poncelet Ileleji - NPOC
> > 5. Caleb Ogundele - NPOC
> > 6. Julf (Johan) Helsingius - NCUC
> > 7. Akinmoyeje Benjamin - NCUC
> > 8. Bekono Pascal - NCUC
> >
> > We need at least 1 from NCUC and 1 from NPOC. Should we instruct our SSC
> > reps who our preferred 2 are or should we leave it at the discretion of
> > the SSC to ensure that atleast one us selected from each of our
> > constituencies?
> >
> > Warmly,
> > Tomslin
> >
> > On Fri, 7 June 2024, 19:25 Tomslin Samme-Nlar, <mesumbeslin at gmail.com
> > <mailto:mesumbeslin at gmail.com>> wrote:
> >
> >     Hi members,
> >
> >     I want to bring to your attention this call from ICANN for
> >     volunteers to the Pilot Holistic Review Team that will commence work
> >     on 25 September 2024. Each SO/AC is entitled to nominate up to 7
> >     applicants, so the selection process in our case will be at the GNSO
> >     level.
> >
> >     Volunteers may apply by filling out an Application Form here
> >     https://forms.gle/TzUAz2p6K8TU8utZ9
> >     <https://forms.gle/TzUAz2p6K8TU8utZ9> . ICANN encourages volunteers
> >     to apply by the closing date, 19 June 2024.
> >
> >     Warmly,
> >     Tomslin
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240623/d1a5737c/attachment.htm>

From mesumbeslin at gmail.com  Sun Jun 23 10:04:06 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Sun, 23 Jun 2024 17:04:06 +1000
Subject: [NCSG-PC] [Call for Volunteers] Appointment of representative
 and alternate to the PPSAI IRT
In-Reply-To: <CAM8DdeUFVZ18WfoH28uMpys9dO20V=mZuTXqERZ2BYRqDerYEw@mail.gmail.com>
References: <CB52871E-374F-48BF-97D7-D184C00AD654@contoso.com>
 <ee28ed26-ea0c-4aa3-ba5f-46e9aa43bcbf@julf.com>
 <CAM8DdeUFVZ18WfoH28uMpys9dO20V=mZuTXqERZ2BYRqDerYEw@mail.gmail.com>
Message-ID: <CAM8DdeXb-E-t9qvStEdhFbfC1PAM7rn9P+wsmKWeP_Zq7z26YA@mail.gmail.com>

Dear PC,

We have 4 expressions of interest on this (yaay!) in the order in which
they came.

   1. Emmanuel Vitus - NPOC
   2. Caleb - NPOC
   3. Pedro de Perdig?o Lana - NCUC (If necessary)
   4. Razoana Moslam - NCUC
   5. Reema Mousa - NCUC

I believe we need to appoint 2 members and two alternates. Can you let me
know your preferences?

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


On Mon, 27 May 2024 at 11:52, Tomslin Samme-Nlar <mesumbeslin at gmail.com>
wrote:

> Dear members,
>
> There is a request from Org for SG/Cs to appoint a representative and an
> alternate to the PPSAI IRT. We (NCSG) had concerns with the IRT going ahead
> but as you can see, Org is still going ahead with it.
>
> NCSG is seeking a representative and an alternate. Please read below for
> details of the role of the representative and on what the IRT will be doing.
>
> Send your EOI to me (mesumbeslin at gmail.com) copying Julf (julf at julf.com)
> and Andrea (andrea.glandon at icann.org) no later than Friday May 31st 2023
> for the policy committee's review.
>
> Warmly,
> Tomslin
>
>
>
>
> -------- Forwarded Message --------
> Subject:        [GNSO-SG-C-Leadership] Appointment of representative and
> alternate to the PPSAI IRT
> Date:   Tue, 21 May 2024 19:59:02 +0000
> From:   Dennis Chang via GNSO-SG-C-Leadership
> <gnso-sg-c-leadership at icann.org>
> Reply-To:       Dennis Chang <dennis.chang at icann.org>
> To:     gnso-sg-c-leadership at icann.org <gnso-sg-c-leadership at icann.org>
> CC:     Leon Grundmann <leon.grundmann at icann.org>
>
>
>
> Dear All,
>
> Following the publication of the Call for Volunteers
> <
> https://www.icann.org/en/announcements/details/icann-seeks-volunteers-for-the-ppsai-implementation-review-team-20-05-2024-en>,
>
> the Internet Corporation for Assigned Names and Numbers (ICANN)
> organization (org) is pleased to invite you to nominate a representative
> and an alternate to the Proxy & Privacy Services (PPSAI) policy
> Implementation Review Team (IRT).
>
> The implementation process is an ICANN org-driven exercise.  ICANN org
> plans to employ the ?Open + Representative Model? piloted on the
> Subsequent Procedures IRT and based on the GNSO?s PDP 3.0 model
> <
> https://gnso.icann.org/sites/default/files/file/field-file-attach/pdp-3-2-working-group-models-10feb20-en.pdf.pdf>.
>
> The goal is to provide a structure that allows for efficient resolution
> of issues that may occur.
>
> We kindly ask that your group nominate up to one representative and up
> to one alternate to participate in the IRT. Please note, we are asking
> each of ICANN?s supporting organizations, advisory committees,
> stakeholder groups and constituencies to nominate up to one
> representative and one alternate.
>
> Putting forward a representative and alternate is optional; all members
> of the GNSO Group are welcome to join the IRT as participants. In fact,
> we urge anyone who is interested in being selected as a representative
> to join the IRT as a participant first (call for volunteers
> <
> https://www.icann.org/en/announcements/details/icann-seeks-volunteers-for-the-ppsai-implementation-review-team-20-05-2024-en>).
>
> As you will see below, the roles of participants and representatives are
> nearly identical, with the representatives? main function being that of
> an information-bridge to their community groups.
>
> ICANN org plans to host the first IRT call during the ICANN80 public
> meeting in June 2024. We do not require the nominees for the first
> meeting, but request that you conclude the nomination process and inform
> us of the nominees as soon as feasible.
>
> Why Have Representatives?
>
> While participants always speak in their own personal capacity,
> representatives are expected to speak on behalf of their constituency,
> stakeholder group, supporting organization, or advisory committee.
> Therefore, a key part of the representative?s role will be to engage
> actively and consistently with their colleagues to ensure they can
> convey their group?s viewpoints to the IRT. Please note, that this will
> require an efficient process for representatives to inform and receive
> input from their respective groups. To put this into place will be the
> responsibility of each representative.
>
> In addition, when determining the level of consensus in the circumstance
> described in Section V.E. of the IRT Principles & Guidelines
> <
> https://www.icann.org/en/system/files/files/irt-principles-guidelines-23aug16-en.pdf>,
>
> the GNSO Liaison, in the Open + Representative model, shall take into
> consideration that members who are representatives are expected to
> express the viewpoint of their respective community groups and
> participants to express their own views. This does not impact each
> member?s ability to raise any concern they may have, nor does it absolve
> ICANN org or the GNSO Council liaison from ?exercis[ing] all reasonable
> efforts to resolve disagreements? within the IRT.
>
> More information can be found on this PPSAI IRT wiki page
> <https://community.icann.org/x/lQDSEw>.  We are looking forward to
> getting the IRT underway and, please, do not hesitate to reach out
> should you have any questions.
>
> --
>
> Kind Regards,
>
> Dennis S. Chang
>
> GDD Programs Director
>
> Phone: +1 213 293 7889
>
> Sykpe: dennisSchang
>
> www.icann.org <http://www.icann.org>  One World ? One Internet
>
> _______________________________________________
> 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/20240623/57cdfe90/attachment.htm>

From julf at Julf.com  Sun Jun 23 10:52:37 2024
From: julf at Julf.com (Johan Helsingius)
Date: Sun, 23 Jun 2024 09:52:37 +0200
Subject: [NCSG-PC] Volunteers to the Pilot Holistic Review Team
In-Reply-To: <CAM8DdeUV6vyxu80kPBSswU86Yf08r82A7G9eZW6_ULg=CtUYjg@mail.gmail.com>
References: <CAM8DdeXPcRSYFgvRfjz5OPf+RU154vP8kCGnOEf3K84utv52Kg@mail.gmail.com>
 <CAM8DdeXWqFtVBTjhXPnq-o-KSc3E1OXv+yLd85C_DDs4LD2krQ@mail.gmail.com>
 <8078e9be-4604-4707-bb3a-b64ff2d2f00c@Julf.com>
 <CAM8DdeUV6vyxu80kPBSswU86Yf08r82A7G9eZW6_ULg=CtUYjg@mail.gmail.com>
Message-ID: <c2080848-a180-4102-80c0-d8299f22ca13@Julf.com>

Good to know, Tomslin - doesn't matter, was just curious.

	Julf


On 23/06/2024 07:57, Tomslin Samme-Nlar wrote:
> @Johan Helsingius <mailto:julf at julf.com>I picked NCUC for you ? only 
> for the sake of our internal choice. The website does not differentiate 
> SG or C. Forgive me if I got it?wrong.
> 
> 
> 
> Warmly,
> Tomslin
> 
> On Sat, 22 June 2024, 19:03 Johan Helsingius, <julf at julf.com 
> <mailto:julf at julf.com>> wrote:
> 
>     1. I think we should do both. Indicate our preference, but also add
>     "but at least make sure we get 2 reps".
> 
>     2. Seeing we have enough volunteers, I am happy to withdraw.
> 
>     I am a bit surprised to see myself labelled as "NCUC" - nothing
>     wrong with that, but NCSG can't have a rep? And who picked
>     NCUC for me - it could just as well have been NPOC?
> 
>      ? ? ? ? Julf
> 
> 
>     On 22/06/2024 02:40, Tomslin Samme-Nlar wrote:
>      > Hi all,
>      >
>      > **(Included all our SSC reps and chairs)
>      >
>      > Regarding the candidates for the Pilot Holistic Review, I checked
>     with
>      > staff whether SG/Cs will endorse candidates and the response I
>     got is
>      > that "the applications aren?t associated with a SG/C and they
>     don?t come
>      > in with endorsements so they will be evaluated by the SSC on
>     their merits".
>      >
>      > With that in mind, I wanted to bring to our SSC reps attention the
>      > importance to ensure that atleast two(2) of the seven (7) appointees
>      > allowed for GNSO must be from NCSG, since there are a total of 7
>      > constituencies in GNSO.
>      >
>      > The list of applicants have been posted here:
>      > https://community.icann.org/display/atrt/Review+Team+Applicants
>     <https://community.icann.org/display/atrt/Review+Team+Applicants>
>      > <https://community.icann.org/display/atrt/Review+Team+Applicants
>     <https://community.icann.org/display/atrt/Review+Team+Applicants>>
>      >
>      > We have 8 NCSG members (3 NPOC and 5 NCUC) who've applied. They are:
>      > 1. Emmanuel Nnaemeka Vitus - NPOC
>      > 2. James Gannon - NCUC
>      > 3. Pedro Lana - NCUC
>      > 4.?Poncelet Ileleji - NPOC
>      > 5. Caleb Ogundele - NPOC
>      > 6. Julf (Johan) Helsingius - NCUC
>      > 7.?Akinmoyeje Benjamin - NCUC
>      > 8. Bekono Pascal - NCUC
>      >
>      > We need at least 1 from NCUC and 1 from NPOC. Should we instruct
>     our SSC
>      > reps who our preferred 2 are or should we leave it at the
>     discretion of
>      > the SSC to ensure that atleast one us selected from each of our
>      > constituencies?
>      >
>      > Warmly,
>      > Tomslin
>      >
>      > On Fri, 7 June 2024, 19:25 Tomslin Samme-Nlar,
>     <mesumbeslin at gmail.com <mailto:mesumbeslin at gmail.com>
>      > <mailto:mesumbeslin at gmail.com <mailto:mesumbeslin at gmail.com>>> wrote:
>      >
>      >? ? ?Hi members,
>      >
>      >? ? ?I want to bring to your attention this call from ICANN for
>      >? ? ?volunteers to the Pilot Holistic Review Team that will
>     commence work
>      >? ? ?on 25 September 2024. Each SO/AC is entitled to nominate up to 7
>      >? ? ?applicants, so the selection process in our case will be at
>     the GNSO
>      >? ? ?level.
>      >
>      >? ? ?Volunteers may apply by filling out an Application Form here
>      > https://forms.gle/TzUAz2p6K8TU8utZ9
>     <https://forms.gle/TzUAz2p6K8TU8utZ9>
>      >? ? ?<https://forms.gle/TzUAz2p6K8TU8utZ9
>     <https://forms.gle/TzUAz2p6K8TU8utZ9>> . ICANN encourages volunteers
>      >? ? ?to apply by the closing date, 19 June 2024.
>      >
>      >? ? ?Warmly,
>      >? ? ?Tomslin
>      >
> 


From julf at Julf.com  Sun Jun 23 11:50:26 2024
From: julf at Julf.com (Johan Helsingius)
Date: Sun, 23 Jun 2024 10:50:26 +0200
Subject: [NCSG-PC] Fwd: ICANN81 | Istanbul | Supported Travelers Database
 Due | Thursday, 11 July 2024
In-Reply-To: <599CEBD6-AC19-416E-B511-3027A2B35D9C@icann.org>
References: <599CEBD6-AC19-416E-B511-3027A2B35D9C@icann.org>
Message-ID: <c2ead156-97e6-4489-92d3-665b6902a04b@Julf.com>

Reminder...

Manju, Peter, Tomslin, Farzaneh, Tapani,

Please let me know if you intend to be in Istanbul in person or not.

	Julf



-------- Forwarded Message --------
Subject: 	ICANN81 | Istanbul | Supported Travelers Database Due | 
Thursday, 11 July 2024
Date: 	Thu, 20 Jun 2024 14:02:02 +0000
From: 	Terri Agnew <terri.agnew at icann.org>
To: 	julf at julf.com <julf at julf.com>, jumaropi at yahoo.com 
<jumaropi at yahoo.com>, benakin at gmail.com <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>, philippe.fouquart at orange.com 
<philippe.fouquart at orange.com>, sdemetriou at verisign.com 
<sdemetriou at verisign.com>, John McElwaine 
<john.mcelwaine at nelsonmullins.com>, Karen Day <Karen.Day at sas.com>
CC: 	Brenda Brewer <brenda.brewer at icann.org>, gnso-secs at icann.org 
<gnso-secs at icann.org>, Zoe Bonython <secretariat at icannregistrars.org>, 
Andrea Glandon <andrea.glandon at icann.org>, Sue Schuler 
<secretariat at rysg.info>



Dear all,

In order to service your travel needs for ICANN81Istanbulin a timely 
fashion, please submit your meeting database tognso-secs at icann.org 
<mailto:gnso-secs at icann.org>by*Thursday, 11 July 2024. *It is important 
all funded travel air booking is completed by due date given in ICANN 
Travel emails.

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

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

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

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

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

*TRAVEL BOOKING PROCESS*

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

	

*WHO*

	

*WHAT*

1

	

Funded Traveler

	

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

2

	

Funded Traveler

	

Approved for Trade Regulations Review

3

	

Funded Traveler

	

Receive Travel Funding Confirmation Email from ICANN Travel Support

4

	

*Funded Traveler*

	

*Book Air Travel for meeting*

	

	

	

	

*Approved dates of Arrival and Departure*

*ARRIVAL DATE*

	

*DEPARTURE DATE*

*Friday, 08 November *

	

*Friday, 15 November*

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

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

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

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

3.Wednesday, 25 September 2024*(45 days before travel)*is the last day 
to submit additions/replacements.

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

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

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

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

Reminder:

    * GNSO supported traveler with a designated hotel accommodation
      funding, a hotel room is automatically secured for you, please *DO
      NOT* book your own hotel as it is un-reimbursable.
    * All personal data provided to ICANN org in for purposes of providing
      travel support for participants related to ICANN events will be
      processed in accordance with the ICANN Privacy Policy [icann.org]
 
<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=A_rkvV7hcBAIOU12pQX6fSkWBC6-P-bPaQDowX2oR_A&s=WwqcPGGS1mvkGHO5BjVc3E9ewPva_WoF-Snq25kq0OM&e=>. 

      Should you have any questions or concerns about this Privacy Policy
      and our privacy practices, you may contact us at privacy at icann.org
      <mailto:privacy at icann.org>.
    * As a reminder, for the AGM meeting only, incoming Councilors get
      funding, as well as the then-incumbent Councilors.
   ?Many thanks for your cooperation!

Thank you.

Kind regards,

Terri

Policy Team Supporting the GNSO



From mesumbeslin at gmail.com  Sun Jun 23 12:22:42 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Sun, 23 Jun 2024 19:22:42 +1000
Subject: [NCSG-PC] [NCSG-EC] Fwd: ICANN81 | Istanbul | Supported
 Travelers Database Due | Thursday, 11 July 2024
In-Reply-To: <c2ead156-97e6-4489-92d3-665b6902a04b@Julf.com>
References: <599CEBD6-AC19-416E-B511-3027A2B35D9C@icann.org>
 <c2ead156-97e6-4489-92d3-665b6902a04b@Julf.com>
Message-ID: <CAM8DdeV=vxM+AFEMgWp4x752wfzV76cT_+RcQTTDS4_5HgFyhQ@mail.gmail.com>

I intend to be there

Warmly,
Tomslin

On Sun, 23 June 2024, 18:50 Johan Helsingius via NCSG-EC, <
ncsg-ec at lists.ncsg.is> wrote:

> Reminder...
>
> Manju, Peter, Tomslin, Farzaneh, Tapani,
>
> Please let me know if you intend to be in Istanbul in person or not.
>
>         Julf
>
>
>
> -------- Forwarded Message --------
> Subject:        ICANN81 | Istanbul | Supported Travelers Database Due |
> Thursday, 11 July 2024
> Date:   Thu, 20 Jun 2024 14:02:02 +0000
> From:   Terri Agnew <terri.agnew at icann.org>
> To:     julf at julf.com <julf at julf.com>, jumaropi at yahoo.com
> <jumaropi at yahoo.com>, benakin at gmail.com <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>, philippe.fouquart at orange.com
> <philippe.fouquart at orange.com>, sdemetriou at verisign.com
> <sdemetriou at verisign.com>, John McElwaine
> <john.mcelwaine at nelsonmullins.com>, Karen Day <Karen.Day at sas.com>
> CC:     Brenda Brewer <brenda.brewer at icann.org>, gnso-secs at icann.org
> <gnso-secs at icann.org>, Zoe Bonython <secretariat at icannregistrars.org>,
> Andrea Glandon <andrea.glandon at icann.org>, Sue Schuler
> <secretariat at rysg.info>
>
>
>
> Dear all,
>
> In order to service your travel needs for ICANN81Istanbulin a timely
> fashion, please submit your meeting database tognso-secs at icann.org
> <mailto:gnso-secs at icann.org>by*Thursday, 11 July 2024. *It is important
> all funded travel air booking is completed by due date given in ICANN
> Travel emails.
>
> Please share with all funded travelers, the travel support guidelines
> wiki space: https://community.icann.org/x/lgvxAg
> <https://community.icann.org/x/lgvxAg> and highlight the communications
> responsibilities section:
>
> ICANN Travel Support attempts to reach a supported traveler four times
> before deeming the supported traveler unresponsive:
>
>    1. ICANN Travel Support sends ?welcome email.?
>    2. If there is no response after seven business days, ICANN Travel
>       Support sends a second email, copying ICANN support staff.
>    3. If there is no response five business days after the second email,
>       ICANN Travel Support sends a third email, copying ICANN support
>       staff and the community group chair.
>    4. If there is no response five business days after the third email,
>       ICANN Travel Support sends a fourth email, copying ICANN support
>       staff and the community group chair.
>
> If there is no response three days after the fourth attempt to reach the
> supported traveler, the community group may substitute another traveler.
>
> A timely response would be appreciated in view of visa issues and the
> OFAC review. The deadline for submissions is critical to allow for
> confirmed reservation numbers as required for visa and travel arrangements.
>
> *TRAVEL BOOKING PROCESS*
>
> In order for Funded Travelers to start booking travel, they MUST
> complete Steps 1, 2, and 3.
>
>
>
> *WHO*
>
>
>
> *WHAT*
>
> 1
>
>
>
> Funded Traveler
>
>
>
> Register for meeting using the Funded Traveler Registration Link
> provided by ICANN Travel Support
>
> 2
>
>
>
> Funded Traveler
>
>
>
> Approved for Trade Regulations Review
>
> 3
>
>
>
> Funded Traveler
>
>
>
> Receive Travel Funding Confirmation Email from ICANN Travel Support
>
> 4
>
>
>
> *Funded Traveler*
>
>
>
> *Book Air Travel for meeting*
>
>
>
>
>
>
>
>
>
> *Approved dates of Arrival and Departure*
>
> *ARRIVAL DATE*
>
>
>
> *DEPARTURE DATE*
>
> *Friday, 08 November *
>
>
>
> *Friday, 15 November*
>
> For air, this must be booked using either via our online booking
> platform (Concur) or official travel agency (FCM). ICANN org does not
> allow self-booking.
>
> Please note that when requesting travel support, in the interest of
> fairness and in light of budget restrictions we would like you to take
> the following into consideration:
>
> 1.Respond timely to ICANN Travel regarding your upcoming travel and book
> by deadline given in email.
>
> 2.If you require a visa to enter the country, please make sure to
> acquire your visa immediately.Follow link here
> <https://community.icann.org/x/fSfxAg> for assistance.
>
> 3.Wednesday, 25 September 2024*(45 days before travel)*is the last day
> to submit additions/replacements.
>
> 4.Requests past the deadline will be handled on a case-by-case basis by
> ICANN. All additional travelers added after the 90-day deadline are
> subject to availability, may NOT be placed in the same hotel as their
> funded traveler groups, and may not be able to attend due to visa issues.
>
> 5.If possible, please book direct travel requests. Detours and
> multi-stop trips are unfortunately not guaranteed.
>
> 6.If travelers want to extend their stay this must be done at their own
> expense and should contact the hotel directly once the ICANN hotel
> confirmation has be sent to them.
>
> 7.*Privately Booked Reservations*: ICANN will not refund or take over
> accommodations directly booked by the funded traveler. If a replacement
> has an existing hotel reservation, they will need to cancel their
> reservation and ICANN will not be able to take over their reservation.
>
> Reminder:
>
>     * GNSO supported traveler with a designated hotel accommodation
>       funding, a hotel room is automatically secured for you, please *DO
>       NOT* book your own hotel as it is un-reimbursable.
>     * All personal data provided to ICANN org in for purposes of providing
>       travel support for participants related to ICANN events will be
>       processed in accordance with the ICANN Privacy Policy [icann.org]
>
> <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=A_rkvV7hcBAIOU12pQX6fSkWBC6-P-bPaQDowX2oR_A&s=WwqcPGGS1mvkGHO5BjVc3E9ewPva_WoF-Snq25kq0OM&e=>.
>
>
>       Should you have any questions or concerns about this Privacy Policy
>       and our privacy practices, you may contact us at privacy at icann.org
>       <mailto:privacy at icann.org>.
>     * As a reminder, for the AGM meeting only, incoming Councilors get
>       funding, as well as the then-incumbent Councilors.
>     Many thanks for your cooperation!
>
> Thank you.
>
> Kind regards,
>
> Terri
>
> Policy Team Supporting the GNSO
>
> _______________________________________________
> NCSG-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/20240623/b7dffcd4/attachment.htm>

From stephanie.perrin at mail.utoronto.ca  Sun Jun 23 16:38:22 2024
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Sun, 23 Jun 2024 13:38:22 +0000
Subject: [NCSG-PC] [Call for Volunteers] Appointment of representative
 and alternate to the PPSAI IRT
In-Reply-To: <CAM8DdeXb-E-t9qvStEdhFbfC1PAM7rn9P+wsmKWeP_Zq7z26YA@mail.gmail.com>
References: <CB52871E-374F-48BF-97D7-D184C00AD654@contoso.com>
 <ee28ed26-ea0c-4aa3-ba5f-46e9aa43bcbf@julf.com>
 <CAM8DdeUFVZ18WfoH28uMpys9dO20V=mZuTXqERZ2BYRqDerYEw@mail.gmail.com>
 <CAM8DdeXb-E-t9qvStEdhFbfC1PAM7rn9P+wsmKWeP_Zq7z26YA@mail.gmail.com>
Message-ID: <A5FF3B59-0AE9-4BA6-82AE-488A66D5370C@mail.utoronto.ca>

I think I am already there as I have been on the IRT.  Happy to continue since I feel it is important that someone who has been following this for years be there...knowing where the bodies are buried is helpful.  planning to step away from the RDRs as there is less policy risk there IMHO
Stephanie

Sent from my iPhone

On Jun 23, 2024, at 03:04, Tomslin Samme-Nlar <mesumbeslin at gmail.com> wrote:

?
Dear PC,

We have 4 expressions of interest on this (yaay!) in the order in which they came.

  1.  Emmanuel Vitus - NPOC
  2.  Caleb - NPOC
  3.  Pedro de Perdig?o Lana - NCUC (If necessary)
  4.  Razoana Moslam - NCUC
  5.  Reema Mousa - NCUC

I believe we need to appoint 2 members and two alternates. Can you let me know your preferences?

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


On Mon, 27 May 2024 at 11:52, Tomslin Samme-Nlar <mesumbeslin at gmail.com<mailto:mesumbeslin at gmail.com>> wrote:
Dear members,

There is a request from Org for SG/Cs to appoint a representative and an alternate to the PPSAI IRT. We (NCSG) had concerns with the IRT going ahead but as you can see, Org is still going ahead with it.

NCSG is seeking a representative and an alternate. Please read below for details of the role of the representative and on what the IRT will be doing.

Send your EOI to me (mesumbeslin at gmail.com<mailto:mesumbeslin at gmail.com>) copying Julf (julf at julf.com<mailto:julf at julf.com>) and Andrea (andrea.glandon at icann.org<mailto:andrea.glandon at icann.org>) no later than Friday May 31st 2023 for the policy committee's review.

Warmly,
Tomslin




-------- Forwarded Message --------
Subject:        [GNSO-SG-C-Leadership] Appointment of representative and
alternate to the PPSAI IRT
Date:   Tue, 21 May 2024 19:59:02 +0000
From:   Dennis Chang via GNSO-SG-C-Leadership
<gnso-sg-c-leadership at icann.org<mailto:gnso-sg-c-leadership at icann.org>>
Reply-To:       Dennis Chang <dennis.chang at icann.org<mailto:dennis.chang at icann.org>>
To:     gnso-sg-c-leadership at icann.org<mailto:gnso-sg-c-leadership at icann.org> <gnso-sg-c-leadership at icann.org<mailto:gnso-sg-c-leadership at icann.org>>
CC:     Leon Grundmann <leon.grundmann at icann.org<mailto:leon.grundmann at icann.org>>



Dear All,

Following the publication of the Call for Volunteers
<https://www.icann.org/en/announcements/details/icann-seeks-volunteers-for-the-ppsai-implementation-review-team-20-05-2024-en>,
the Internet Corporation for Assigned Names and Numbers (ICANN)
organization (org) is pleased to invite you to nominate a representative
and an alternate to the Proxy & Privacy Services (PPSAI) policy
Implementation Review Team (IRT).

The implementation process is an ICANN org-driven exercise.  ICANN org
plans to employ the ?Open + Representative Model? piloted on the
Subsequent Procedures IRT and based on the GNSO?s PDP 3.0 model
<https://gnso.icann.org/sites/default/files/file/field-file-attach/pdp-3-2-working-group-models-10feb20-en.pdf.pdf>.
The goal is to provide a structure that allows for efficient resolution
of issues that may occur.

We kindly ask that your group nominate up to one representative and up
to one alternate to participate in the IRT. Please note, we are asking
each of ICANN?s supporting organizations, advisory committees,
stakeholder groups and constituencies to nominate up to one
representative and one alternate.

Putting forward a representative and alternate is optional; all members
of the GNSO Group are welcome to join the IRT as participants. In fact,
we urge anyone who is interested in being selected as a representative
to join the IRT as a participant first (call for volunteers
<https://www.icann.org/en/announcements/details/icann-seeks-volunteers-for-the-ppsai-implementation-review-team-20-05-2024-en>).
As you will see below, the roles of participants and representatives are
nearly identical, with the representatives? main function being that of
an information-bridge to their community groups.

ICANN org plans to host the first IRT call during the ICANN80 public
meeting in June 2024. We do not require the nominees for the first
meeting, but request that you conclude the nomination process and inform
us of the nominees as soon as feasible.

Why Have Representatives?

While participants always speak in their own personal capacity,
representatives are expected to speak on behalf of their constituency,
stakeholder group, supporting organization, or advisory committee.
Therefore, a key part of the representative?s role will be to engage
actively and consistently with their colleagues to ensure they can
convey their group?s viewpoints to the IRT. Please note, that this will
require an efficient process for representatives to inform and receive
input from their respective groups. To put this into place will be the
responsibility of each representative.

In addition, when determining the level of consensus in the circumstance
described in Section V.E. of the IRT Principles & Guidelines
<https://www.icann.org/en/system/files/files/irt-principles-guidelines-23aug16-en.pdf>,
the GNSO Liaison, in the Open + Representative model, shall take into
consideration that members who are representatives are expected to
express the viewpoint of their respective community groups and
participants to express their own views. This does not impact each
member?s ability to raise any concern they may have, nor does it absolve
ICANN org or the GNSO Council liaison from ?exercis[ing] all reasonable
efforts to resolve disagreements? within the IRT.

More information can be found on this PPSAI IRT wiki page
<https://community.icann.org/x/lQDSEw>.  We are looking forward to
getting the IRT underway and, please, do not hesitate to reach out
should you have any questions.

--

Kind Regards,

Dennis S. Chang

GDD Programs Director

Phone: +1 213 293 7889

Sykpe: dennisSchang

www.icann.org<http://www.icann.org> <http://www.icann.org>  One World ? One Internet

_______________________________________________
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
_______________________________________________
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/20240623/75067e0c/attachment.htm>

From mesumbeslin at gmail.com  Mon Jun 24 02:25:49 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Mon, 24 Jun 2024 09:25:49 +1000
Subject: [NCSG-PC] [Call for Volunteers] Appointment of representative
 and alternate to the PPSAI IRT
In-Reply-To: <A5FF3B59-0AE9-4BA6-82AE-488A66D5370C@mail.utoronto.ca>
References: <CB52871E-374F-48BF-97D7-D184C00AD654@contoso.com>
 <ee28ed26-ea0c-4aa3-ba5f-46e9aa43bcbf@julf.com>
 <CAM8DdeUFVZ18WfoH28uMpys9dO20V=mZuTXqERZ2BYRqDerYEw@mail.gmail.com>
 <CAM8DdeXb-E-t9qvStEdhFbfC1PAM7rn9P+wsmKWeP_Zq7z26YA@mail.gmail.com>
 <A5FF3B59-0AE9-4BA6-82AE-488A66D5370C@mail.utoronto.ca>
Message-ID: <CAM8DdeVD+rn-fZpv77OGQFENo0PchbaC+vU6fbwW=27xvk611A@mail.gmail.com>

Thanks @Stephanie Perrin <stephanie.perrin at mail.utoronto.ca>

Looks like we need to select one other member and 2 alternates.

Warmly,
Tomslin

On Sun, 23 June 2024, 23:38 Stephanie Perrin, <
stephanie.perrin at mail.utoronto.ca> wrote:

> I think I am already there as I have been on the IRT.  Happy to continue
> since I feel it is important that someone who has been following this for
> years be there...knowing where the bodies are buried is helpful.  planning
> to step away from the RDRs as there is less policy risk there IMHO
> Stephanie
>
> Sent from my iPhone
>
> On Jun 23, 2024, at 03:04, Tomslin Samme-Nlar <mesumbeslin at gmail.com>
> wrote:
>
> ?
> Dear PC,
>
> We have 4 expressions of interest on this (yaay!) in the order in which
> they came.
>
>    1. Emmanuel Vitus - NPOC
>    2. Caleb - NPOC
>    3. Pedro de Perdig?o Lana - NCUC (If necessary)
>    4. Razoana Moslam - NCUC
>    5. Reema Mousa - NCUC
>
> I believe we need to appoint 2 members and two alternates. Can you let me
> know your preferences?
>
> Warmly,
> Tomslin
> @LinkedIn: https://www.linkedin.com/in/tomslin/
>
>
> On Mon, 27 May 2024 at 11:52, Tomslin Samme-Nlar <mesumbeslin at gmail.com>
> wrote:
>
>> Dear members,
>>
>> There is a request from Org for SG/Cs to appoint a representative and an
>> alternate to the PPSAI IRT. We (NCSG) had concerns with the IRT going ahead
>> but as you can see, Org is still going ahead with it.
>>
>> NCSG is seeking a representative and an alternate. Please read below for
>> details of the role of the representative and on what the IRT will be doing.
>>
>> Send your EOI to me (mesumbeslin at gmail.com) copying Julf (julf at julf.com)
>> and Andrea (andrea.glandon at icann.org) no later than Friday May 31st 2023
>> for the policy committee's review.
>>
>> Warmly,
>> Tomslin
>>
>>
>>
>>
>> -------- Forwarded Message --------
>> Subject:        [GNSO-SG-C-Leadership] Appointment of representative and
>> alternate to the PPSAI IRT
>> Date:   Tue, 21 May 2024 19:59:02 +0000
>> From:   Dennis Chang via GNSO-SG-C-Leadership
>> <gnso-sg-c-leadership at icann.org>
>> Reply-To:       Dennis Chang <dennis.chang at icann.org>
>> To:     gnso-sg-c-leadership at icann.org <gnso-sg-c-leadership at icann.org>
>> CC:     Leon Grundmann <leon.grundmann at icann.org>
>>
>>
>>
>> Dear All,
>>
>> Following the publication of the Call for Volunteers
>> <
>> https://www.icann.org/en/announcements/details/icann-seeks-volunteers-for-the-ppsai-implementation-review-team-20-05-2024-en>,
>>
>> the Internet Corporation for Assigned Names and Numbers (ICANN)
>> organization (org) is pleased to invite you to nominate a representative
>> and an alternate to the Proxy & Privacy Services (PPSAI) policy
>> Implementation Review Team (IRT).
>>
>> The implementation process is an ICANN org-driven exercise.  ICANN org
>> plans to employ the ?Open + Representative Model? piloted on the
>> Subsequent Procedures IRT and based on the GNSO?s PDP 3.0 model
>> <
>> https://gnso.icann.org/sites/default/files/file/field-file-attach/pdp-3-2-working-group-models-10feb20-en.pdf.pdf>.
>>
>> The goal is to provide a structure that allows for efficient resolution
>> of issues that may occur.
>>
>> We kindly ask that your group nominate up to one representative and up
>> to one alternate to participate in the IRT. Please note, we are asking
>> each of ICANN?s supporting organizations, advisory committees,
>> stakeholder groups and constituencies to nominate up to one
>> representative and one alternate.
>>
>> Putting forward a representative and alternate is optional; all members
>> of the GNSO Group are welcome to join the IRT as participants. In fact,
>> we urge anyone who is interested in being selected as a representative
>> to join the IRT as a participant first (call for volunteers
>> <
>> https://www.icann.org/en/announcements/details/icann-seeks-volunteers-for-the-ppsai-implementation-review-team-20-05-2024-en>).
>>
>> As you will see below, the roles of participants and representatives are
>> nearly identical, with the representatives? main function being that of
>> an information-bridge to their community groups.
>>
>> ICANN org plans to host the first IRT call during the ICANN80 public
>> meeting in June 2024. We do not require the nominees for the first
>> meeting, but request that you conclude the nomination process and inform
>> us of the nominees as soon as feasible.
>>
>> Why Have Representatives?
>>
>> While participants always speak in their own personal capacity,
>> representatives are expected to speak on behalf of their constituency,
>> stakeholder group, supporting organization, or advisory committee.
>> Therefore, a key part of the representative?s role will be to engage
>> actively and consistently with their colleagues to ensure they can
>> convey their group?s viewpoints to the IRT. Please note, that this will
>> require an efficient process for representatives to inform and receive
>> input from their respective groups. To put this into place will be the
>> responsibility of each representative.
>>
>> In addition, when determining the level of consensus in the circumstance
>> described in Section V.E. of the IRT Principles & Guidelines
>> <
>> https://www.icann.org/en/system/files/files/irt-principles-guidelines-23aug16-en.pdf>,
>>
>> the GNSO Liaison, in the Open + Representative model, shall take into
>> consideration that members who are representatives are expected to
>> express the viewpoint of their respective community groups and
>> participants to express their own views. This does not impact each
>> member?s ability to raise any concern they may have, nor does it absolve
>> ICANN org or the GNSO Council liaison from ?exercis[ing] all reasonable
>> efforts to resolve disagreements? within the IRT.
>>
>> More information can be found on this PPSAI IRT wiki page
>> <https://community.icann.org/x/lQDSEw>.  We are looking forward to
>> getting the IRT underway and, please, do not hesitate to reach out
>> should you have any questions.
>>
>> --
>>
>> Kind Regards,
>>
>> Dennis S. Chang
>>
>> GDD Programs Director
>>
>> Phone: +1 213 293 7889
>>
>> Sykpe: dennisSchang
>>
>> www.icann.org <http://www.icann.org>  One World ? One Internet
>>
>> _______________________________________________
>> 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/20240624/da6ead2d/attachment.htm>

From stephanie.perrin at mail.utoronto.ca  Mon Jun 24 02:45:13 2024
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Sun, 23 Jun 2024 23:45:13 +0000
Subject: [NCSG-PC] [Call for Volunteers] Appointment of representative
 and alternate to the PPSAI IRT
In-Reply-To: <CAM8DdeVD+rn-fZpv77OGQFENo0PchbaC+vU6fbwW=27xvk611A@mail.gmail.com>
References: <CB52871E-374F-48BF-97D7-D184C00AD654@contoso.com>
 <ee28ed26-ea0c-4aa3-ba5f-46e9aa43bcbf@julf.com>
 <CAM8DdeUFVZ18WfoH28uMpys9dO20V=mZuTXqERZ2BYRqDerYEw@mail.gmail.com>
 <CAM8DdeXb-E-t9qvStEdhFbfC1PAM7rn9P+wsmKWeP_Zq7z26YA@mail.gmail.com>
 <A5FF3B59-0AE9-4BA6-82AE-488A66D5370C@mail.utoronto.ca>
 <CAM8DdeVD+rn-fZpv77OGQFENo0PchbaC+vU6fbwW=27xvk611A@mail.gmail.com>
Message-ID: <51ABD87D-CFF1-4AD9-8941-EB8442F1912F@mail.utoronto.ca>

Thanks, we could use some more folks on the RDRS group.  Farzi is there but we need some alternates.  Things could happen there?.
Cheers Steph

On Jun 23, 2024, at 7:25?PM, Tomslin Samme-Nlar <mesumbeslin at gmail.com> wrote:

Thanks @Stephanie Perrin<mailto:stephanie.perrin at mail.utoronto.ca>

Looks like we need to select one other member and 2 alternates.

Warmly,
Tomslin

On Sun, 23 June 2024, 23:38 Stephanie Perrin, <stephanie.perrin at mail.utoronto.ca<mailto:stephanie.perrin at mail.utoronto.ca>> wrote:
I think I am already there as I have been on the IRT.  Happy to continue since I feel it is important that someone who has been following this for years be there...knowing where the bodies are buried is helpful.  planning to step away from the RDRs as there is less policy risk there IMHO
Stephanie

Sent from my iPhone

On Jun 23, 2024, at 03:04, Tomslin Samme-Nlar <mesumbeslin at gmail.com<mailto:mesumbeslin at gmail.com>> wrote:

?
Dear PC,

We have 4 expressions of interest on this (yaay!) in the order in which they came.

  1.  Emmanuel Vitus - NPOC
  2.  Caleb - NPOC
  3.  Pedro de Perdig?o Lana - NCUC (If necessary)
  4.  Razoana Moslam - NCUC
  5.  Reema Mousa - NCUC

I believe we need to appoint 2 members and two alternates. Can you let me know your preferences?

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


On Mon, 27 May 2024 at 11:52, Tomslin Samme-Nlar <mesumbeslin at gmail.com<mailto:mesumbeslin at gmail.com>> wrote:
Dear members,

There is a request from Org for SG/Cs to appoint a representative and an alternate to the PPSAI IRT. We (NCSG) had concerns with the IRT going ahead but as you can see, Org is still going ahead with it.

NCSG is seeking a representative and an alternate. Please read below for details of the role of the representative and on what the IRT will be doing.

Send your EOI to me (mesumbeslin at gmail.com<mailto:mesumbeslin at gmail.com>) copying Julf (julf at julf.com<mailto:julf at julf.com>) and Andrea (andrea.glandon at icann.org<mailto:andrea.glandon at icann.org>) no later than Friday May 31st 2023 for the policy committee's review.

Warmly,
Tomslin




-------- Forwarded Message --------
Subject:        [GNSO-SG-C-Leadership] Appointment of representative and
alternate to the PPSAI IRT
Date:   Tue, 21 May 2024 19:59:02 +0000
From:   Dennis Chang via GNSO-SG-C-Leadership
<gnso-sg-c-leadership at icann.org<mailto:gnso-sg-c-leadership at icann.org>>
Reply-To:       Dennis Chang <dennis.chang at icann.org<mailto:dennis.chang at icann.org>>
To:     gnso-sg-c-leadership at icann.org<mailto:gnso-sg-c-leadership at icann.org> <gnso-sg-c-leadership at icann.org<mailto:gnso-sg-c-leadership at icann.org>>
CC:     Leon Grundmann <leon.grundmann at icann.org<mailto:leon.grundmann at icann.org>>



Dear All,

Following the publication of the Call for Volunteers
<https://www.icann.org/en/announcements/details/icann-seeks-volunteers-for-the-ppsai-implementation-review-team-20-05-2024-en>,
the Internet Corporation for Assigned Names and Numbers (ICANN)
organization (org) is pleased to invite you to nominate a representative
and an alternate to the Proxy & Privacy Services (PPSAI) policy
Implementation Review Team (IRT).

The implementation process is an ICANN org-driven exercise.  ICANN org
plans to employ the ?Open + Representative Model? piloted on the
Subsequent Procedures IRT and based on the GNSO?s PDP 3.0 model
<https://gnso.icann.org/sites/default/files/file/field-file-attach/pdp-3-2-working-group-models-10feb20-en.pdf.pdf>.
The goal is to provide a structure that allows for efficient resolution
of issues that may occur.

We kindly ask that your group nominate up to one representative and up
to one alternate to participate in the IRT. Please note, we are asking
each of ICANN?s supporting organizations, advisory committees,
stakeholder groups and constituencies to nominate up to one
representative and one alternate.

Putting forward a representative and alternate is optional; all members
of the GNSO Group are welcome to join the IRT as participants. In fact,
we urge anyone who is interested in being selected as a representative
to join the IRT as a participant first (call for volunteers
<https://www.icann.org/en/announcements/details/icann-seeks-volunteers-for-the-ppsai-implementation-review-team-20-05-2024-en>).
As you will see below, the roles of participants and representatives are
nearly identical, with the representatives? main function being that of
an information-bridge to their community groups.

ICANN org plans to host the first IRT call during the ICANN80 public
meeting in June 2024. We do not require the nominees for the first
meeting, but request that you conclude the nomination process and inform
us of the nominees as soon as feasible.

Why Have Representatives?

While participants always speak in their own personal capacity,
representatives are expected to speak on behalf of their constituency,
stakeholder group, supporting organization, or advisory committee.
Therefore, a key part of the representative?s role will be to engage
actively and consistently with their colleagues to ensure they can
convey their group?s viewpoints to the IRT. Please note, that this will
require an efficient process for representatives to inform and receive
input from their respective groups. To put this into place will be the
responsibility of each representative.

In addition, when determining the level of consensus in the circumstance
described in Section V.E. of the IRT Principles & Guidelines
<https://www.icann.org/en/system/files/files/irt-principles-guidelines-23aug16-en.pdf>,
the GNSO Liaison, in the Open + Representative model, shall take into
consideration that members who are representatives are expected to
express the viewpoint of their respective community groups and
participants to express their own views. This does not impact each
member?s ability to raise any concern they may have, nor does it absolve
ICANN org or the GNSO Council liaison from ?exercis[ing] all reasonable
efforts to resolve disagreements? within the IRT.

More information can be found on this PPSAI IRT wiki page
<https://community.icann.org/x/lQDSEw>.  We are looking forward to
getting the IRT underway and, please, do not hesitate to reach out
should you have any questions.

--

Kind Regards,

Dennis S. Chang

GDD Programs Director

Phone: +1 213 293 7889

Sykpe: dennisSchang

www.icann.org<http://www.icann.org/> <http://www.icann.org<http://www.icann.org/>>  One World ? One Internet

_______________________________________________
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
_______________________________________________
NCSG-PC mailing list
NCSG-PC at lists.ncsg.is<mailto:NCSG-PC at lists.ncsg.is>
https://lists.ncsg.is/mailman/listinfo/ncsg-pc

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

From manju at nii.org.tw  Mon Jun 24 06:30:09 2024
From: manju at nii.org.tw (=?UTF-8?B?6Zmz5pu86Iy5IE1hbmp1IENoZW4=?=)
Date: Mon, 24 Jun 2024 11:30:09 +0800
Subject: [NCSG-PC] [NCSG-EC] Fwd: ICANN81 | Istanbul | Supported
 Travelers Database Due | Thursday, 11 July 2024
In-Reply-To: <CAM8DdeV=vxM+AFEMgWp4x752wfzV76cT_+RcQTTDS4_5HgFyhQ@mail.gmail.com>
References: <599CEBD6-AC19-416E-B511-3027A2B35D9C@icann.org>
 <c2ead156-97e6-4489-92d3-665b6902a04b@Julf.com>
 <CAM8DdeV=vxM+AFEMgWp4x752wfzV76cT_+RcQTTDS4_5HgFyhQ@mail.gmail.com>
Message-ID: <CAMeQZi1F+VhEmAhV1MQ81gi=tt3fN3mSxwpg00Od1S5h2Drz_A@mail.gmail.com>

Will be there in person, thank you!

Best,
Manju

On Sun, Jun 23, 2024 at 5:22?PM Tomslin Samme-Nlar <mesumbeslin at gmail.com>
wrote:

> I intend to be there
>
> Warmly,
> Tomslin
>
> On Sun, 23 June 2024, 18:50 Johan Helsingius via NCSG-EC, <
> ncsg-ec at lists.ncsg.is> wrote:
>
>> Reminder...
>>
>> Manju, Peter, Tomslin, Farzaneh, Tapani,
>>
>> Please let me know if you intend to be in Istanbul in person or not.
>>
>>         Julf
>>
>>
>>
>> -------- Forwarded Message --------
>> Subject:        ICANN81 | Istanbul | Supported Travelers Database Due |
>> Thursday, 11 July 2024
>> Date:   Thu, 20 Jun 2024 14:02:02 +0000
>> From:   Terri Agnew <terri.agnew at icann.org>
>> To:     julf at julf.com <julf at julf.com>, jumaropi at yahoo.com
>> <jumaropi at yahoo.com>, benakin at gmail.com <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>, philippe.fouquart at orange.com
>> <philippe.fouquart at orange.com>, sdemetriou at verisign.com
>> <sdemetriou at verisign.com>, John McElwaine
>> <john.mcelwaine at nelsonmullins.com>, Karen Day <Karen.Day at sas.com>
>> CC:     Brenda Brewer <brenda.brewer at icann.org>, gnso-secs at icann.org
>> <gnso-secs at icann.org>, Zoe Bonython <secretariat at icannregistrars.org>,
>> Andrea Glandon <andrea.glandon at icann.org>, Sue Schuler
>> <secretariat at rysg.info>
>>
>>
>>
>> Dear all,
>>
>> In order to service your travel needs for ICANN81Istanbulin a timely
>> fashion, please submit your meeting database tognso-secs at icann.org
>> <mailto:gnso-secs at icann.org>by*Thursday, 11 July 2024. *It is important
>> all funded travel air booking is completed by due date given in ICANN
>> Travel emails.
>>
>> Please share with all funded travelers, the travel support guidelines
>> wiki space: https://community.icann.org/x/lgvxAg
>> <https://community.icann.org/x/lgvxAg> and highlight the communications
>> responsibilities section:
>>
>> ICANN Travel Support attempts to reach a supported traveler four times
>> before deeming the supported traveler unresponsive:
>>
>>    1. ICANN Travel Support sends ?welcome email.?
>>    2. If there is no response after seven business days, ICANN Travel
>>       Support sends a second email, copying ICANN support staff.
>>    3. If there is no response five business days after the second email,
>>       ICANN Travel Support sends a third email, copying ICANN support
>>       staff and the community group chair.
>>    4. If there is no response five business days after the third email,
>>       ICANN Travel Support sends a fourth email, copying ICANN support
>>       staff and the community group chair.
>>
>> If there is no response three days after the fourth attempt to reach the
>> supported traveler, the community group may substitute another traveler.
>>
>> A timely response would be appreciated in view of visa issues and the
>> OFAC review. The deadline for submissions is critical to allow for
>> confirmed reservation numbers as required for visa and travel
>> arrangements.
>>
>> *TRAVEL BOOKING PROCESS*
>>
>> In order for Funded Travelers to start booking travel, they MUST
>> complete Steps 1, 2, and 3.
>>
>>
>>
>> *WHO*
>>
>>
>>
>> *WHAT*
>>
>> 1
>>
>>
>>
>> Funded Traveler
>>
>>
>>
>> Register for meeting using the Funded Traveler Registration Link
>> provided by ICANN Travel Support
>>
>> 2
>>
>>
>>
>> Funded Traveler
>>
>>
>>
>> Approved for Trade Regulations Review
>>
>> 3
>>
>>
>>
>> Funded Traveler
>>
>>
>>
>> Receive Travel Funding Confirmation Email from ICANN Travel Support
>>
>> 4
>>
>>
>>
>> *Funded Traveler*
>>
>>
>>
>> *Book Air Travel for meeting*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *Approved dates of Arrival and Departure*
>>
>> *ARRIVAL DATE*
>>
>>
>>
>> *DEPARTURE DATE*
>>
>> *Friday, 08 November *
>>
>>
>>
>> *Friday, 15 November*
>>
>> For air, this must be booked using either via our online booking
>> platform (Concur) or official travel agency (FCM). ICANN org does not
>> allow self-booking.
>>
>> Please note that when requesting travel support, in the interest of
>> fairness and in light of budget restrictions we would like you to take
>> the following into consideration:
>>
>> 1.Respond timely to ICANN Travel regarding your upcoming travel and book
>> by deadline given in email.
>>
>> 2.If you require a visa to enter the country, please make sure to
>> acquire your visa immediately.Follow link here
>> <https://community.icann.org/x/fSfxAg> for assistance.
>>
>> 3.Wednesday, 25 September 2024*(45 days before travel)*is the last day
>> to submit additions/replacements.
>>
>> 4.Requests past the deadline will be handled on a case-by-case basis by
>> ICANN. All additional travelers added after the 90-day deadline are
>> subject to availability, may NOT be placed in the same hotel as their
>> funded traveler groups, and may not be able to attend due to visa issues.
>>
>> 5.If possible, please book direct travel requests. Detours and
>> multi-stop trips are unfortunately not guaranteed.
>>
>> 6.If travelers want to extend their stay this must be done at their own
>> expense and should contact the hotel directly once the ICANN hotel
>> confirmation has be sent to them.
>>
>> 7.*Privately Booked Reservations*: ICANN will not refund or take over
>> accommodations directly booked by the funded traveler. If a replacement
>> has an existing hotel reservation, they will need to cancel their
>> reservation and ICANN will not be able to take over their reservation.
>>
>> Reminder:
>>
>>     * GNSO supported traveler with a designated hotel accommodation
>>       funding, a hotel room is automatically secured for you, please *DO
>>       NOT* book your own hotel as it is un-reimbursable.
>>     * All personal data provided to ICANN org in for purposes of providing
>>       travel support for participants related to ICANN events will be
>>       processed in accordance with the ICANN Privacy Policy [icann.org]
>>
>> <
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=A_rkvV7hcBAIOU12pQX6fSkWBC6-P-bPaQDowX2oR_A&s=WwqcPGGS1mvkGHO5BjVc3E9ewPva_WoF-Snq25kq0OM&e=>.
>>
>>
>>       Should you have any questions or concerns about this Privacy Policy
>>       and our privacy practices, you may contact us at privacy at icann.org
>>       <mailto:privacy at icann.org>.
>>     * As a reminder, for the AGM meeting only, incoming Councilors get
>>       funding, as well as the then-incumbent Councilors.
>>     Many thanks for your cooperation!
>>
>> Thank you.
>>
>> Kind regards,
>>
>> Terri
>>
>> Policy Team Supporting the GNSO
>>
>> _______________________________________________
>> NCSG-EC mailing list
>> NCSG-EC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240624/48104451/attachment.htm>

From remmyn at gmail.com  Sun Jun 23 00:45:21 2024
From: remmyn at gmail.com (Remmy Nweke)
Date: Sat, 22 Jun 2024 22:45:21 +0100
Subject: [NCSG-PC] Volunteers to the Pilot Holistic Review Team
In-Reply-To: <8078e9be-4604-4707-bb3a-b64ff2d2f00c@Julf.com>
References: <CAM8DdeXPcRSYFgvRfjz5OPf+RU154vP8kCGnOEf3K84utv52Kg@mail.gmail.com>
 <CAM8DdeXWqFtVBTjhXPnq-o-KSc3E1OXv+yLd85C_DDs4LD2krQ@mail.gmail.com>
 <8078e9be-4604-4707-bb3a-b64ff2d2f00c@Julf.com>
Message-ID: <CAMc__oo0MkG-8B3Oa7q3d02puWuNTq4Btnu8EF8zJg=g7oAJ+w@mail.gmail.com>

Thanks for the heads up. Points well noted.
___________________
REMMY NWEKE,  *mNUJ, mNGE, mGOCOP*
Lead Consulting Strategist/Group Executive Editor,
*ITREALMS Media* group [*Multiple-award winning medium*]
(ITREALMS <http://www.itrealms.com.ng/>, DigitalSENSE Business Magazine
<http://www.digitalsenseafrica.com.ng/businessnews>; NaijaAgroNet
<http://www.naijaagronet.com.ng/>)
No. 36 Afariogun Street, Oshodi-Lagos
M: 234-8033592762, 8023122558, T: @ITRealms
<http://www.twitter.com/ITRealms>
@DigitalSENSEng
2023 *Nigeria DigitalSENSE Forum on IG4D*, Thursday June 8
<https://www.itrealms.com.ng/>
2023 *ITREALMS* e-Waste Dialogue, Thursday December 7
<https://www.itrealms.com.ng/>
@Welcome Center Hotels, Int'l Airport Road, Lagos-Nigeria
<http://welcomecentrehotels.com/>
Former Vice President, African Civil Society on Information Society (ACSIS)
______________________________________________________________
*Confidentiality Notice:* The information in this document and attachments
are confidential and may also be privileged information. It is intended
only for the use of the named recipient. Remmy Nweke does not accept legal
responsibility for the contents of this e-mail. If you are not the intended
recipient, please notify me immediately, then delete this document and do
not disclose the contents of this document to any other person, nor make
any copies. Violators may face court persecution.


On Sat, Jun 22, 2024 at 10:03?AM Johan Helsingius <julf at julf.com> wrote:

> 1. I think we should do both. Indicate our preference, but also add
> "but at least make sure we get 2 reps".
>
> 2. Seeing we have enough volunteers, I am happy to withdraw.
>
> I am a bit surprised to see myself labelled as "NCUC" - nothing
> wrong with that, but NCSG can't have a rep? And who picked
> NCUC for me - it could just as well have been NPOC?
>
>         Julf
>
>
> On 22/06/2024 02:40, Tomslin Samme-Nlar wrote:
> > Hi all,
> >
> > **(Included all our SSC reps and chairs)
> >
> > Regarding the candidates for the Pilot Holistic Review, I checked with
> > staff whether SG/Cs will endorse candidates and the response I got is
> > that "the applications aren?t associated with a SG/C and they don?t come
> > in with endorsements so they will be evaluated by the SSC on their
> merits".
> >
> > With that in mind, I wanted to bring to our SSC reps attention the
> > importance to ensure that atleast two(2) of the seven (7) appointees
> > allowed for GNSO must be from NCSG, since there are a total of 7
> > constituencies in GNSO.
> >
> > The list of applicants have been posted here:
> > https://community.icann.org/display/atrt/Review+Team+Applicants
> > <https://community.icann.org/display/atrt/Review+Team+Applicants>
> >
> > We have 8 NCSG members (3 NPOC and 5 NCUC) who've applied. They are:
> > 1. Emmanuel Nnaemeka Vitus - NPOC
> > 2. James Gannon - NCUC
> > 3. Pedro Lana - NCUC
> > 4. Poncelet Ileleji - NPOC
> > 5. Caleb Ogundele - NPOC
> > 6. Julf (Johan) Helsingius - NCUC
> > 7. Akinmoyeje Benjamin - NCUC
> > 8. Bekono Pascal - NCUC
> >
> > We need at least 1 from NCUC and 1 from NPOC. Should we instruct our SSC
> > reps who our preferred 2 are or should we leave it at the discretion of
> > the SSC to ensure that atleast one us selected from each of our
> > constituencies?
> >
> > Warmly,
> > Tomslin
> >
> > On Fri, 7 June 2024, 19:25 Tomslin Samme-Nlar, <mesumbeslin at gmail.com
> > <mailto:mesumbeslin at gmail.com>> wrote:
> >
> >     Hi members,
> >
> >     I want to bring to your attention this call from ICANN for
> >     volunteers to the Pilot Holistic Review Team that will commence work
> >     on 25 September 2024. Each SO/AC is entitled to nominate up to 7
> >     applicants, so the selection process in our case will be at the GNSO
> >     level.
> >
> >     Volunteers may apply by filling out an Application Form here
> >     https://forms.gle/TzUAz2p6K8TU8utZ9
> >     <https://forms.gle/TzUAz2p6K8TU8utZ9> . ICANN encourages volunteers
> >     to apply by the closing date, 19 June 2024.
> >
> >     Warmly,
> >     Tomslin
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240622/39758faf/attachment.htm>

From tapani at tapanitarvainen.fi  Mon Jun 24 13:06:57 2024
From: tapani at tapanitarvainen.fi (Tapani Tarvainen)
Date: Mon, 24 Jun 2024 13:06:57 +0300
Subject: [NCSG-PC] [NCSG-EC] Fwd: ICANN81 | Istanbul | Supported
 Travelers Database Due | Thursday, 11 July 2024
In-Reply-To: <c2ead156-97e6-4489-92d3-665b6902a04b@Julf.com>
References: <599CEBD6-AC19-416E-B511-3027A2B35D9C@icann.org>
 <c2ead156-97e6-4489-92d3-665b6902a04b@Julf.com>
Message-ID: <ZnlFQQp_sC75rzfN@saukko.tarvainen.info>

I'm not coming.

Tapani

On Sun, Jun 23, 2024 at 10:50:26AM +0200, Johan Helsingius via NCSG-EC (ncsg-ec at lists.ncsg.is) wrote:
> 
> Reminder...
> 
> Manju, Peter, Tomslin, Farzaneh, Tapani,
> 
> Please let me know if you intend to be in Istanbul in person or not.
> 
> 	Julf
> 
> 
> 
> -------- Forwarded Message --------
> Subject: 	ICANN81 | Istanbul | Supported Travelers Database Due | Thursday,
> 11 July 2024
> Date: 	Thu, 20 Jun 2024 14:02:02 +0000
> From: 	Terri Agnew <terri.agnew at icann.org>
> To: 	julf at julf.com <julf at julf.com>, jumaropi at yahoo.com <jumaropi at yahoo.com>,
> benakin at gmail.com <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>,
> philippe.fouquart at orange.com <philippe.fouquart at orange.com>,
> sdemetriou at verisign.com <sdemetriou at verisign.com>, John McElwaine
> <john.mcelwaine at nelsonmullins.com>, Karen Day <Karen.Day at sas.com>
> CC: 	Brenda Brewer <brenda.brewer at icann.org>, gnso-secs at icann.org
> <gnso-secs at icann.org>, Zoe Bonython <secretariat at icannregistrars.org>,
> Andrea Glandon <andrea.glandon at icann.org>, Sue Schuler
> <secretariat at rysg.info>
> 
> 
> 
> Dear all,
> 
> In order to service your travel needs for ICANN81Istanbulin a timely
> fashion, please submit your meeting database tognso-secs at icann.org
> <mailto:gnso-secs at icann.org>by*Thursday, 11 July 2024. *It is important all
> funded travel air booking is completed by due date given in ICANN Travel
> emails.
> 
> Please share with all funded travelers, the travel support guidelines wiki
> space: https://community.icann.org/x/lgvxAg
> <https://community.icann.org/x/lgvxAg> and highlight the communications
> responsibilities section:
> 
> ICANN Travel Support attempts to reach a supported traveler four times
> before deeming the supported traveler unresponsive:
> 
>   1. ICANN Travel Support sends ?welcome email.?
>   2. If there is no response after seven business days, ICANN Travel
>      Support sends a second email, copying ICANN support staff.
>   3. If there is no response five business days after the second email,
>      ICANN Travel Support sends a third email, copying ICANN support
>      staff and the community group chair.
>   4. If there is no response five business days after the third email,
>      ICANN Travel Support sends a fourth email, copying ICANN support
>      staff and the community group chair.
> 
> If there is no response three days after the fourth attempt to reach the
> supported traveler, the community group may substitute another traveler.
> 
> A timely response would be appreciated in view of visa issues and the OFAC
> review. The deadline for submissions is critical to allow for confirmed
> reservation numbers as required for visa and travel arrangements.
> 
> *TRAVEL BOOKING PROCESS*
> 
> In order for Funded Travelers to start booking travel, they MUST complete
> Steps 1, 2, and 3.
> 
> 	
> 
> *WHO*
> 
> 	
> 
> *WHAT*
> 
> 1
> 
> 	
> 
> Funded Traveler
> 
> 	
> 
> Register for meeting using the Funded Traveler Registration Link provided by
> ICANN Travel Support
> 
> 2
> 
> 	
> 
> Funded Traveler
> 
> 	
> 
> Approved for Trade Regulations Review
> 
> 3
> 
> 	
> 
> Funded Traveler
> 
> 	
> 
> Receive Travel Funding Confirmation Email from ICANN Travel Support
> 
> 4
> 
> 	
> 
> *Funded Traveler*
> 
> 	
> 
> *Book Air Travel for meeting*
> 
> 	
> 
> 	
> 
> 	
> 
> 	
> 
> *Approved dates of Arrival and Departure*
> 
> *ARRIVAL DATE*
> 
> 	
> 
> *DEPARTURE DATE*
> 
> *Friday, 08 November *
> 
> 	
> 
> *Friday, 15 November*
> 
> For air, this must be booked using either via our online booking platform
> (Concur) or official travel agency (FCM). ICANN org does not allow
> self-booking.
> 
> Please note that when requesting travel support, in the interest of fairness
> and in light of budget restrictions?we would like you to take the following
> into consideration:
> 
> 1.Respond?timely to ICANN Travel regarding your upcoming travel and book by
> deadline given in email.
> 
> 2.If you require a visa to enter the country, please make sure to acquire
> your visa immediately.Follow link here
> <https://community.icann.org/x/fSfxAg> for assistance.
> 
> 3.Wednesday, 25 September 2024*(45 days before travel)*is the last day to
> submit additions/replacements.
> 
> 4.Requests past the deadline will be handled on a case-by-case basis by
> ICANN. All additional travelers added after the 90-day deadline are subject
> to availability, may NOT be placed in the same hotel as their funded
> traveler groups, and may not be able to attend due to visa issues.
> 
> 5.If possible, please book?direct travel requests.?Detours and multi-stop
> trips are unfortunately not guaranteed.
> 
> 6.If travelers want to extend their stay this must be done at their own
> expense and should contact the hotel directly once the ICANN hotel
> confirmation has be sent to them.
> 
> 7.*Privately Booked Reservations*: ICANN will not refund or take over
> accommodations directly booked by the funded traveler. If a replacement has
> an existing hotel reservation, they will need to cancel their reservation
> and ICANN will not be able to take over their reservation.
> 
> Reminder:
> 
>    * GNSO supported traveler with a designated hotel accommodation
>      funding, a hotel room is automatically secured for you, please *DO
>      NOT* book your own hotel as it is un-reimbursable.
>    * All personal data provided to ICANN org in for purposes of providing
>      travel support for participants related to ICANN events will be
>      processed in accordance with the ICANN Privacy Policy [icann.org]
> 
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=A_rkvV7hcBAIOU12pQX6fSkWBC6-P-bPaQDowX2oR_A&s=WwqcPGGS1mvkGHO5BjVc3E9ewPva_WoF-Snq25kq0OM&e=>.
> 
>      Should you have any questions or concerns about this Privacy Policy
>      and our privacy practices, you may contact us at privacy at icann.org
>      <mailto:privacy at icann.org>.
>    * As a reminder, for the AGM meeting only, incoming Councilors get
>      funding, as well as the then-incumbent Councilors.
>   ?Many thanks for your cooperation!
> 
> Thank you.
> 
> Kind regards,
> 
> Terri
> 
> Policy Team Supporting the GNSO
> 
> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec

-- 
Tapani Tarvainen


From julf at Julf.com  Wed Jun 26 11:51:24 2024
From: julf at Julf.com (Johan Helsingius)
Date: Wed, 26 Jun 2024 10:51:24 +0200
Subject: [NCSG-PC] Fwd: [SOAC-Leaders-ICANNMeeting-Planning] Re: ICANN81
 Block Schedule, Production Timeline
In-Reply-To: <BB136AC0-2366-4677-8B66-A9522C57341E@icann.org>
References: <BB136AC0-2366-4677-8B66-A9522C57341E@icann.org>
Message-ID: <017d28e8-25f1-438e-8ee0-e7ae9f5f5da8@Julf.com>

FYI...

	Julf

-------- Forwarded Message --------
Subject: 	[SOAC-Leaders-ICANNMeeting-Planning] Re: ICANN81 Block 
Schedule, Production Timeline
Date: 	Wed, 26 Jun 2024 08:13:12 +0000
From: 	Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning 
<soac-leaders-icannmeeting-planning at icann.org>
Reply-To: 	Nathalie Peregrine <nathalie.peregrine at icann.org>
To: 	soac-leaders-icannmeeting-planning at icann.org 
<soac-leaders-icannmeeting-planning at icann.org>



Dear all,

Ahead of our first ICANN81 Production call scheduled later today at 
17:30 UTC, the Schedule team would like to share an updated version of 
the previously circulated ICANN81 Block Schedule.

Notable changes are:

*Monday*

The Welcome Ceremony has now been extended to 75 mins rather than the 
initially scheduled 60 mins. This is to allow for sufficient time for 
the Tarek Kamal Award. The 30 min break is preserved to allow for room 
re-set for the following session, the Q&A with ICANN org Executives, 
which will now run for 75 mins instead of the previously scheduled 90 mins.

*Thursday*

The schedule will end at 17:30 local time, instead of the previously 
scheduled 16:00 end time in keeping with habitual planning. This will 
also allow for the Board Placeholder session should it be required.

The updated document as well as the previously circulated Production 
Timeline are attached to this email.

Looking forward to discussing this further with you all later today!

Thank you!

Nathalie, on behalf of the Schedule Team.

*From: *Nathalie Peregrine <nathalie.peregrine at icann.org>
*Date: *Wednesday, 22 May 2024 at 22:13
*To: *"soac-leaders-icannmeeting-planning at icann.org" 
<soac-leaders-icannmeeting-planning at icann.org>
*Subject: *ICANN81 Block Schedule, Production Timeline

Dear all,

Whilst you are all busy planning for ICANN80, staff support thought it 
might be helpful for you to have access to the ICANN81 draft block 
schedule and production timeline ahead of time. ICANN81 will take place 
in Istanbul from the 9 ? 14 November 2024.

As most of you know, planning for an ICANN meeting would traditionally 
start at the end of the previous ICANN meeting for the next one. There 
are many benefits to starting planning earlier, this allows for more 
discussions about topics, new session formats and ought to make outreach 
and engagement efforts easier.

Holding ICANN81 Production Calls prior to ICANN80 may be confusing, but 
having access to a proposed block schedule and production timeline could 
trigger discussions within your own groups but also on this ICANN 
meeting planning mailing list. It may also assist with session agenda 
planning for ICANN80.

Please bear in mind the following:

   * The draft block schedule follows a thought process stemming from
     what worked at previous AGMs and equally other ICANN meetings. It
     can however be modified and tweaked according to your collective input
   * The production timeline shows an estimate of the deadlines by which
     scheduling steps should have taken place. If we can be ahead of the
     production timeline (for instance, the sharing of the block schedule
     and timeline before ICANN80), this will free up more Production Call
     time for discussion.

Please do not hesitate to provide your input here, your questions, your 
ideas for ICANN81.

We look forward to working with you on the AGM!

Kind regards,

The Schedule Team
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ICANN81- AGM Istanbul DRAFT v.2 26 June 2024 - Sheet1.pdf
Type: application/pdf
Size: 58470 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240626/25f5eb22/attachment.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ICANN81 Production Timeline.pdf
Type: application/pdf
Size: 75225 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240626/25f5eb22/attachment-0001.pdf>
-------------- next part --------------
_______________________________________________
SOAC-Leaders-ICANNMeeting-Planning mailing list -- soac-leaders-icannmeeting-planning at icann.org
To unsubscribe send an email to soac-leaders-icannmeeting-planning-leave at icann.org

_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

From mesumbeslin at gmail.com  Sun Jun 30 15:28:26 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Sun, 30 Jun 2024 22:28:26 +1000
Subject: [NCSG-PC] [Call for Volunteers] Appointment of representative
 and alternate to the PPSAI IRT
In-Reply-To: <51ABD87D-CFF1-4AD9-8941-EB8442F1912F@mail.utoronto.ca>
References: <CB52871E-374F-48BF-97D7-D184C00AD654@contoso.com>
 <ee28ed26-ea0c-4aa3-ba5f-46e9aa43bcbf@julf.com>
 <CAM8DdeUFVZ18WfoH28uMpys9dO20V=mZuTXqERZ2BYRqDerYEw@mail.gmail.com>
 <CAM8DdeXb-E-t9qvStEdhFbfC1PAM7rn9P+wsmKWeP_Zq7z26YA@mail.gmail.com>
 <A5FF3B59-0AE9-4BA6-82AE-488A66D5370C@mail.utoronto.ca>
 <CAM8DdeVD+rn-fZpv77OGQFENo0PchbaC+vU6fbwW=27xvk611A@mail.gmail.com>
 <51ABD87D-CFF1-4AD9-8941-EB8442F1912F@mail.utoronto.ca>
Message-ID: <CAM8DdeWpwDK1ehCPZTwmobrX_ncD88ZRA-WJ5R8Lo1tpezdQ7w@mail.gmail.com>

Hi PC,

By the way, I never got any suggestions on how to proceed with this
selection. Shall I just select in the order in which the expressions of
interests were submitted?

Warmly,
Tomslin



On Mon, 24 Jun 2024 at 09:45, Stephanie Perrin <
stephanie.perrin at mail.utoronto.ca> wrote:

> Thanks, we could use some more folks on the RDRS group.  Farzi is there
> but we need some alternates.  Things could happen there?.
> Cheers Steph
>
> On Jun 23, 2024, at 7:25?PM, Tomslin Samme-Nlar <mesumbeslin at gmail.com>
> wrote:
>
> Thanks @Stephanie Perrin <stephanie.perrin at mail.utoronto.ca>
>
> Looks like we need to select one other member and 2 alternates.
>
> Warmly,
> Tomslin
>
> On Sun, 23 June 2024, 23:38 Stephanie Perrin, <
> stephanie.perrin at mail.utoronto.ca> wrote:
>
>> I think I am already there as I have been on the IRT.  Happy to continue
>> since I feel it is important that someone who has been following this for
>> years be there...knowing where the bodies are buried is helpful.  planning
>> to step away from the RDRs as there is less policy risk there IMHO
>> Stephanie
>>
>> Sent from my iPhone
>>
>> On Jun 23, 2024, at 03:04, Tomslin Samme-Nlar <mesumbeslin at gmail.com>
>> wrote:
>>
>> ?
>> Dear PC,
>>
>> We have 4 expressions of interest on this (yaay!) in the order in which
>> they came.
>>
>>    1. Emmanuel Vitus - NPOC
>>    2. Caleb - NPOC
>>    3. Pedro de Perdig?o Lana - NCUC (If necessary)
>>    4. Razoana Moslam - NCUC
>>    5. Reema Mousa - NCUC
>>
>> I believe we need to appoint 2 members and two alternates. Can you let me
>> know your preferences?
>>
>> Warmly,
>> Tomslin
>> @LinkedIn: https://www.linkedin.com/in/tomslin/
>>
>>
>> On Mon, 27 May 2024 at 11:52, Tomslin Samme-Nlar <mesumbeslin at gmail.com>
>> wrote:
>>
>>> Dear members,
>>>
>>> There is a request from Org for SG/Cs to appoint a representative and an
>>> alternate to the PPSAI IRT. We (NCSG) had concerns with the IRT going ahead
>>> but as you can see, Org is still going ahead with it.
>>>
>>> NCSG is seeking a representative and an alternate. Please read below for
>>> details of the role of the representative and on what the IRT will be doing.
>>>
>>> Send your EOI to me (mesumbeslin at gmail.com) copying Julf (julf at julf.com)
>>> and Andrea (andrea.glandon at icann.org) no later than Friday May 31st
>>> 2023 for the policy committee's review.
>>>
>>> Warmly,
>>> Tomslin
>>>
>>>
>>>
>>>
>>> -------- Forwarded Message --------
>>> Subject:        [GNSO-SG-C-Leadership] Appointment of representative and
>>> alternate to the PPSAI IRT
>>> Date:   Tue, 21 May 2024 19:59:02 +0000
>>> From:   Dennis Chang via GNSO-SG-C-Leadership
>>> <gnso-sg-c-leadership at icann.org>
>>> Reply-To:       Dennis Chang <dennis.chang at icann.org>
>>> To:     gnso-sg-c-leadership at icann.org <gnso-sg-c-leadership at icann.org>
>>> CC:     Leon Grundmann <leon.grundmann at icann.org>
>>>
>>>
>>>
>>> Dear All,
>>>
>>> Following the publication of the Call for Volunteers
>>> <
>>> https://www.icann.org/en/announcements/details/icann-seeks-volunteers-for-the-ppsai-implementation-review-team-20-05-2024-en>,
>>>
>>> the Internet Corporation for Assigned Names and Numbers (ICANN)
>>> organization (org) is pleased to invite you to nominate a representative
>>> and an alternate to the Proxy & Privacy Services (PPSAI) policy
>>> Implementation Review Team (IRT).
>>>
>>> The implementation process is an ICANN org-driven exercise.  ICANN org
>>> plans to employ the ?Open + Representative Model? piloted on the
>>> Subsequent Procedures IRT and based on the GNSO?s PDP 3.0 model
>>> <
>>> https://gnso.icann.org/sites/default/files/file/field-file-attach/pdp-3-2-working-group-models-10feb20-en.pdf.pdf>.
>>>
>>> The goal is to provide a structure that allows for efficient resolution
>>> of issues that may occur.
>>>
>>> We kindly ask that your group nominate up to one representative and up
>>> to one alternate to participate in the IRT. Please note, we are asking
>>> each of ICANN?s supporting organizations, advisory committees,
>>> stakeholder groups and constituencies to nominate up to one
>>> representative and one alternate.
>>>
>>> Putting forward a representative and alternate is optional; all members
>>> of the GNSO Group are welcome to join the IRT as participants. In fact,
>>> we urge anyone who is interested in being selected as a representative
>>> to join the IRT as a participant first (call for volunteers
>>> <
>>> https://www.icann.org/en/announcements/details/icann-seeks-volunteers-for-the-ppsai-implementation-review-team-20-05-2024-en>).
>>>
>>> As you will see below, the roles of participants and representatives are
>>> nearly identical, with the representatives? main function being that of
>>> an information-bridge to their community groups.
>>>
>>> ICANN org plans to host the first IRT call during the ICANN80 public
>>> meeting in June 2024. We do not require the nominees for the first
>>> meeting, but request that you conclude the nomination process and inform
>>> us of the nominees as soon as feasible.
>>>
>>> Why Have Representatives?
>>>
>>> While participants always speak in their own personal capacity,
>>> representatives are expected to speak on behalf of their constituency,
>>> stakeholder group, supporting organization, or advisory committee.
>>> Therefore, a key part of the representative?s role will be to engage
>>> actively and consistently with their colleagues to ensure they can
>>> convey their group?s viewpoints to the IRT. Please note, that this will
>>> require an efficient process for representatives to inform and receive
>>> input from their respective groups. To put this into place will be the
>>> responsibility of each representative.
>>>
>>> In addition, when determining the level of consensus in the circumstance
>>> described in Section V.E. of the IRT Principles & Guidelines
>>> <
>>> https://www.icann.org/en/system/files/files/irt-principles-guidelines-23aug16-en.pdf>,
>>>
>>> the GNSO Liaison, in the Open + Representative model, shall take into
>>> consideration that members who are representatives are expected to
>>> express the viewpoint of their respective community groups and
>>> participants to express their own views. This does not impact each
>>> member?s ability to raise any concern they may have, nor does it absolve
>>> ICANN org or the GNSO Council liaison from ?exercis[ing] all reasonable
>>> efforts to resolve disagreements? within the IRT.
>>>
>>> More information can be found on this PPSAI IRT wiki page
>>> <https://community.icann.org/x/lQDSEw>.  We are looking forward to
>>> getting the IRT underway and, please, do not hesitate to reach out
>>> should you have any questions.
>>>
>>> --
>>>
>>> Kind Regards,
>>>
>>> Dennis S. Chang
>>>
>>> GDD Programs Director
>>>
>>> Phone: +1 213 293 7889
>>>
>>> Sykpe: dennisSchang
>>>
>>> www.icann.org <http://www.icann.org>  One World ? One Internet
>>>
>>> _______________________________________________
>>> 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/20240630/1d97724a/attachment.htm>