From julf at Julf.com Tue Jul 2 18:17:59 2024 From: julf at Julf.com (Johan Helsingius) Date: Tue, 2 Jul 2024 17:17:59 +0200 Subject: [NCSG-EC] Fwd: [SOAC-Leaders-ICANNMeeting-Planning] Re: [Ext] Re: Re: ICANN81 Block Schedule, Production Timeline In-Reply-To: <8BFF615C-7A89-4AF3-9CAA-1D1F555B8D38@icann.org> References: <8BFF615C-7A89-4AF3-9CAA-1D1F555B8D38@icann.org> Message-ID: <3b52f19b-d26f-43d7-9ab6-9f3be0fc205e@Julf.com> -------- Forwarded Message -------- Subject: [SOAC-Leaders-ICANNMeeting-Planning] Re: [Ext] Re: Re: ICANN81 Block Schedule, Production Timeline Date: Mon, 1 Jul 2024 08:16:48 +0000 From: Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning Reply-To: Nathalie Peregrine To: soac-leaders-icannmeeting-planning at icann.org Dear all, Thank you so much for joining the ICANN81 Kick off call! The input shared, be it feedback for ICANN80 and advice regarding the ICANN81 Block Schedule was extremely helpful! Please find the Zoom chat text and slide deck from the call attached to this email. ?The Zoom recording can be accessed here . Regarding the block schedule, please also find the latest version attached with the following change: * Monday?s Q&A with ICANN Org?s Executive Team removed, and replaced by the Geopolitical Forum initially scheduled on Tuesday. Thank you to Alejandra for her input on the Community Session topic deadline! The previous deadline of the 12^th July 2024 can be extended to the 19^th July 2024. However, it would be interesting to hear from community leaders on the matter before then via the mailing list. Please do bear in mind, that there is no obligation for this Community Session to take place, should there be no clear topic community groups agree upon, the session can be postponed until ICANN82. *Action Items for all:* * Kindly express any objection to the current block schedule as speedily as possible. * Please review the joint Board & SO/AC slots and raise concerns should there be any * Begin conversations about the Community Session topic and the need for such a session to be held at ICANN81 Thank you to all and have a lovely week! Kind regards, Nathalie *From: *Alejandra Reynoso Barral *Date: *Friday, 28 June 2024 at 13:04 *To: *Nathalie Peregrine *Cc: *"soac-leaders-icannmeeting-planning at icann.org" *Subject: *[Ext] Re: [SOAC-Leaders-ICANNMeeting-Planning] Re: ICANN81 Block Schedule, Production Timeline Dear Nathalie and All It was good to see/hear you at?the kickoff call. I understand the eagerness to finalize the block schedule as soon as possible, but the current 12th of July deadline to submit a community session topic is a bit tight. The ccNSO council will meet on the 18th of July and, depending on the outcome of the discussion of this item, we may or may not want to submit something. Can the deadline be extended? Best regards, Alejandra ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. ******************************************* On Wed, Jun 26, 2024 at 10:13?AM Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning > wrote: 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 > *Date: *Wednesday, 22 May 2024 at 22:13 *To: *"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 _______________________________________________ SOAC-Leaders-ICANNMeeting-Planning mailing list -- soac-leaders-icannmeeting-planning at icann.org To unsubscribe send an email to soac-leaders-icannmeeting-planning-leave at icann.org _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy ) and the website Terms of Service (https://www.icann.org/privacy/tos ). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. -------------- next part -------------- A non-text attachment was scrubbed... Name: Chat - ICANN81 Production Planning Call No 1.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 21690 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Feedback - ICANN80 and ICANN81 Planning_Kickoff_26 June 2024[4].pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 7658344 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ICANN81- AGM Istanbul DRAFT v.3 01 July 2024 - Sheet1.pdf Type: application/pdf Size: 57011 bytes Desc: not available URL: From JFQueralt at theiofoundation.org Wed Jul 3 07:45:08 2024 From: JFQueralt at theiofoundation.org (=?UTF-8?Q?Jean_F=2E_Qu=C3=A9ralt?=) Date: Wed, 3 Jul 2024 12:45:08 +0800 Subject: [NCSG-EC] TIOF - NCSG online channels. Message-ID: Hello. I've been checking some info around and so far I have found the following - ICANN Confluence page - Domain (redirects to the above) - ICANNWiki page - X - Facebook Is there other channels I am missing? Best. Jean F. Queralt Founder & CEO - The IO Foundation Book a meeting (30 minutes) -- **DISCLAIMER** *The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Wed Jul 3 12:31:33 2024 From: julf at Julf.com (Johan Helsingius) Date: Wed, 3 Jul 2024 11:31:33 +0200 Subject: [NCSG-EC] TIOF - NCSG online channels. In-Reply-To: References: Message-ID: <67c39698-253e-434d-946b-3bccb91b2bcb@Julf.com> On 03/07/2024 06:45, Jean F. Qu?ralt via NCSG-EC wrote: > Is there other channels I am missing? The mail lists, of course: https://lists.ncsg.is/mailman/listinfo Then there are a couple of ad-hoc unofficial messaging channels. Julf From JFQueralt at theiofoundation.org Wed Jul 3 12:38:06 2024 From: JFQueralt at theiofoundation.org (=?UTF-8?Q?Jean_F=2E_Qu=C3=A9ralt?=) Date: Wed, 3 Jul 2024 17:38:06 +0800 Subject: [NCSG-EC] TIOF - NCSG online channels. In-Reply-To: <67c39698-253e-434d-946b-3bccb91b2bcb@Julf.com> References: <67c39698-253e-434d-946b-3bccb91b2bcb@Julf.com> Message-ID: Great, thanks. On Wed, Jul 3, 2024, 17:31 Johan Helsingius via NCSG-EC < ncsg-ec at lists.ncsg.is> wrote: > On 03/07/2024 06:45, Jean F. Qu?ralt via NCSG-EC wrote: > > Is there other channels I am missing? > > The mail lists, of course: > > https://lists.ncsg.is/mailman/listinfo > > Then there are a couple of ad-hoc unofficial messaging > channels. > > Julf > > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -- **DISCLAIMER** *The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Fri Jul 5 10:35:07 2024 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Fri, 5 Jul 2024 17:35:07 +1000 Subject: [NCSG-EC] Agenda for NCSG Policy Call | 15 July at 11:30 UTC Message-ID: Hi all, Looking for agenda suggestions for our meeting this month. Here are some suggestions: 1. Council Agenda 2. ICANN81 draft schedule blocks 3. NCPH Day zero event update? 4. DNS Africa Study update Warmly, Tomslin -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Sat Jul 6 16:46:47 2024 From: julf at Julf.com (Johan Helsingius) Date: Sat, 6 Jul 2024 15:46:47 +0200 Subject: [NCSG-EC] More ICANN81 travel... Message-ID: <6e1c1d7c-6fef-4faa-b5ee-a9eb6f73abdd@Julf.com> As I get travel to Istanbul as incoming councillor, I don't need my NCSG EC travel slot. Would anyone be against using it for Rafik in case he is able and willing to travel to Istanbul? I think it would be very useful to have him there. Julf From muyiwacaleb at gmail.com Sat Jul 6 17:08:02 2024 From: muyiwacaleb at gmail.com (Caleb Olumuyiwa Ogundele) Date: Sat, 6 Jul 2024 09:08:02 -0500 Subject: [NCSG-EC] More ICANN81 travel... In-Reply-To: <6e1c1d7c-6fef-4faa-b5ee-a9eb6f73abdd@Julf.com> References: <6e1c1d7c-6fef-4faa-b5ee-a9eb6f73abdd@Julf.com> Message-ID: Technically I have no objection except anyone wants to apply the previous rule that was heavily debated by announcing this on the list. On Sat, Jul 6, 2024, 8:46?AM Johan Helsingius via NCSG-EC < ncsg-ec at lists.ncsg.is> wrote: > As I get travel to Istanbul as incoming councillor, I don't need my > NCSG EC travel slot. Would anyone be against using it for Rafik in > case he is able and willing to travel to Istanbul? I think it would > be very useful to have him there. > > Julf > > > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Sat Jul 6 17:34:28 2024 From: julf at Julf.com (Johan Helsingius) Date: Sat, 6 Jul 2024 16:34:28 +0200 Subject: [NCSG-EC] More ICANN81 travel... In-Reply-To: References: <6e1c1d7c-6fef-4faa-b5ee-a9eb6f73abdd@Julf.com> Message-ID: <624a0f3d-25f6-4e01-a69a-0896a9a09940@Julf.com> Technically the NCSG EC gets 3 travel slots. It has been a convention (but not a firm rule) that one goes to the chair, one to the NCSG rep, and one to the NPOC rep. My suggestion is that this time it goes to the incoming rather than outgoing chair - it is not a situation where an EC member would be unable to use their slot. Julf On 06/07/2024 16:08, Caleb Olumuyiwa Ogundele wrote: > Technically I have no objection except anyone wants to apply the > previous rule that was heavily debated by announcing this on the list. > > On Sat, Jul 6, 2024, 8:46?AM Johan Helsingius via NCSG-EC > > wrote: > > As I get travel to Istanbul as incoming councillor, I don't need my > NCSG EC travel slot. Would anyone be against using it for Rafik in > case he is able and willing to travel to Istanbul? I think it would > be very useful to have him there. > > ? ? ? ? Julf > > > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > > From JFQueralt at theiofoundation.org Sat Jul 6 18:16:55 2024 From: JFQueralt at theiofoundation.org (=?UTF-8?Q?Jean_F=2E_Qu=C3=A9ralt?=) Date: Sat, 6 Jul 2024 23:16:55 +0800 Subject: [NCSG-EC] More ICANN81 travel... In-Reply-To: <624a0f3d-25f6-4e01-a69a-0896a9a09940@Julf.com> References: <6e1c1d7c-6fef-4faa-b5ee-a9eb6f73abdd@Julf.com> <624a0f3d-25f6-4e01-a69a-0896a9a09940@Julf.com> Message-ID: While I'm unfamiliar with past habits/conventions/(unwritten) rules, if the slot is available I do see it as a net positive for the incoming chair to be there. It does make a lot of sense to me. Jean On Sat, Jul 6, 2024, 22:34 Johan Helsingius via NCSG-EC < ncsg-ec at lists.ncsg.is> wrote: > Technically the NCSG EC gets 3 travel slots. It has been a convention > (but not a firm rule) that one goes to the chair, one to the NCSG > rep, and one to the NPOC rep. My suggestion is that this time it > goes to the incoming rather than outgoing chair - it is not a > situation where an EC member would be unable to use their slot. > > Julf > > > On 06/07/2024 16:08, Caleb Olumuyiwa Ogundele wrote: > > Technically I have no objection except anyone wants to apply the > > previous rule that was heavily debated by announcing this on the list. > > > > On Sat, Jul 6, 2024, 8:46?AM Johan Helsingius via NCSG-EC > > > wrote: > > > > As I get travel to Istanbul as incoming councillor, I don't need my > > NCSG EC travel slot. Would anyone be against using it for Rafik in > > case he is able and willing to travel to Istanbul? I think it would > > be very useful to have him there. > > > > Julf > > > > > > _______________________________________________ > > NCSG-EC mailing list > > NCSG-EC at lists.ncsg.is > > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > > > > > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -- **DISCLAIMER** *The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From mamattah.raymond at gmail.com Mon Jul 8 17:01:58 2024 From: mamattah.raymond at gmail.com (Raymond Mamattah) Date: Mon, 8 Jul 2024 14:01:58 +0000 Subject: [NCSG-EC] [NCSG-PC] More ICANN81 travel... In-Reply-To: <6e1c1d7c-6fef-4faa-b5ee-a9eb6f73abdd@Julf.com> References: <6e1c1d7c-6fef-4faa-b5ee-a9eb6f73abdd@Julf.com> Message-ID: Hello Johan, et al, I think this is an excellent idea, since you the outgoing chair already has a travel slot, it is good to give that slot to the incoming chair. I support it as well. Regards, Raymond Mamattah [image: linkedin] [image: facebook] [image: twitter] Accra, Ghana On Sat, Jul 6, 2024 at 1:46?PM Johan Helsingius via NCSG-PC < ncsg-pc at lists.ncsg.is> wrote: > As I get travel to Istanbul as incoming councillor, I don't need my > NCSG EC travel slot. Would anyone be against using it for Rafik in > case he is able and willing to travel to Istanbul? I think it would > be very useful to have him there. > > Julf > > > _______________________________________________ > 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: From andrea.glandon at icann.org Mon Jul 8 19:05:38 2024 From: andrea.glandon at icann.org (Andrea Glandon) Date: Mon, 8 Jul 2024 16:05:38 +0000 Subject: [NCSG-EC] [Ext] Re: NCSG EC travel for ICANN81 (Istanbul) In-Reply-To: References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com> <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com> <5b281f29-4915-445f-ba0a-e21550c2b079@Julf.com> <2a534ff6-965a-4708-9504-b14e06af855d@Julf.com> <221dd75a-7fc9-44ec-a554-5f2e6ce674cd@Julf.com> Message-ID: Hello Julf, I am confirming that Pedro will be taking David Morar's spot on the NCSG EC. Pedro will also use the NCSG EC travel slot for ICANN81. I will add Pedro to the NCSG EC email list today. Thanks! Kind Regards, Andrea ?On 6/28/24, 13:35, "NCSG-EC on behalf of Johan Helsingius via NCSG-EC" > on behalf of ncsg-ec at lists.ncsg.is >> wrote: Dear Benjamin, Understood. Thanks! Do you have any guess about when there would be a permanent replacement (by Pedro or someone else)? Julf On 28/06/2024 17:08, Benjamin Akinmoyeje wrote: > Dear Julf, > > He will replace David. > > Kind regards, > Benjamin > > > On Wed, Jun 26, 2024 at 5:44 PM Johan Helsingius > > >>> wrote: > > Hi Benjamin, > > > Please why can't Pedro be an NCSG EC? > > He can. of course, if the NCUC decides so. > > You mentioned you want an NCUC EC, and he can be our NCSG > interim EC, > > that is the path we would like to take. > > Interim as in "until a permanent new EC member is appointed"? Sure. > Will he replace David or Farzaneh? > > Julf > _______________________________________________ NCSG-EC mailing list NCSG-EC at lists.ncsg.is > https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!5JAL2hZ1n5_aceSA8exfKOUaeEO69v4buRnxBxniKCQ_vUJ9AsWXgAcsVtB08gRNsT21ICf55_Sd_d3n49JZD9s3NqRL6w$ > [lists[.]ncsg[.]is] From julf at julf.com Mon Jul 8 22:06:18 2024 From: julf at julf.com (Johan Helsingius) Date: Mon, 8 Jul 2024 21:06:18 +0200 Subject: [NCSG-EC] [Ext] Re: NCSG EC travel for ICANN81 (Istanbul) In-Reply-To: References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com> <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com> <5b281f29-4915-445f-ba0a-e21550c2b079@Julf.com> <2a534ff6-965a-4708-9504-b14e06af855d@Julf.com> <221dd75a-7fc9-44ec-a554-5f2e6ce674cd@Julf.com> Message-ID: <805ddd8f-cfc9-456d-a117-96f22db3d596@julf.com> Thanks Andrea! Julf On 08/07/2024 18:05, Andrea Glandon wrote: > Hello Julf, > > I am confirming that Pedro will be taking David Morar's spot on the NCSG EC. Pedro will also use the NCSG EC travel slot for ICANN81. I will add Pedro to the NCSG EC email list today. > > Thanks! > Kind Regards, > Andrea > > > > > > > > > ?On 6/28/24, 13:35, "NCSG-EC on behalf of Johan Helsingius via NCSG-EC" > on behalf of ncsg-ec at lists.ncsg.is >> wrote: > > > > > Dear Benjamin, > > > > > Understood. Thanks! Do you have any guess about when there would > be a permanent replacement (by Pedro or someone else)? > > > > > Julf > > > > > > > > > On 28/06/2024 17:08, Benjamin Akinmoyeje wrote: >> Dear Julf, >> >> He will replace David. >> >> Kind regards, >> Benjamin >> >> >> On Wed, Jun 26, 2024 at 5:44 PM Johan Helsingius > >> >>> wrote: >> >> Hi Benjamin, >> >>> Please why can't Pedro be an NCSG EC? >> >> He can. of course, if the NCUC decides so. >>> You mentioned you want an NCUC EC, and he can be our NCSG >> interim EC, >>> that is the path we would like to take. >> >> Interim as in "until a permanent new EC member is appointed"? Sure. >> Will he replace David or Farzaneh? >> >> Julf >> > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > > https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!5JAL2hZ1n5_aceSA8exfKOUaeEO69v4buRnxBxniKCQ_vUJ9AsWXgAcsVtB08gRNsT21ICf55_Sd_d3n49JZD9s3NqRL6w$ > [lists[.]ncsg[.]is] > > > > > > > From JFQueralt at theiofoundation.org Tue Jul 9 06:24:51 2024 From: JFQueralt at theiofoundation.org (=?UTF-8?Q?Jean_F=2E_Qu=C3=A9ralt?=) Date: Tue, 9 Jul 2024 11:24:51 +0800 Subject: [NCSG-EC] TIOF - A couple of things (Membership). Message-ID: Hi everyone. @Andrea Glandon has sent me the invite to what I understand is the client side of the CRM to review applications. Few things to note/ask: - My login credentials only work as far as resetting the password goes. Once I set it, login gets rejected so I keep requesting password resets. Not the end of the world, just not ideal. - I'd say that something else is missing in the configuration as my name does not show in the "Not Yet Responded" column and I believe at this stage my name should be in all applications (since I haven't reviewed any yet). - Do we have an evaluation guideline somewhere? I've checked some of the applications and criteria should be unified across all of us. I'd also support sharing a set of common tools to do our evaluations, should there be none at the moment. Thoughts? Best, Jean F. Queralt Founder & CEO - The IO Foundation Book a meeting (30 minutes) -- **DISCLAIMER** *The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From JFQueralt at theiofoundation.org Tue Jul 9 09:00:11 2024 From: JFQueralt at theiofoundation.org (=?UTF-8?Q?Jean_F=2E_Qu=C3=A9ralt?=) Date: Tue, 9 Jul 2024 14:00:11 +0800 Subject: [NCSG-EC] Agenda for NCSG Policy Call | 15 July at 11:30 UTC In-Reply-To: References: Message-ID: Hi Andrea, Are calendar invites sent for NCSG EC calls? I don't have it on my calendar. Thx. Jean F. Queralt Founder & CEO - The IO Foundation Book a meeting (30 minutes) On Fri, 5 Jul 2024 at 15:35, Tomslin Samme-Nlar via NCSG-EC < ncsg-ec at lists.ncsg.is> wrote: > Hi all, > > Looking for agenda suggestions for our meeting this month. Here are some > suggestions: > > 1. Council Agenda > 2. ICANN81 draft schedule blocks > 3. NCPH Day zero event update? > 4. DNS Africa Study update > > Warmly, > Tomslin > > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -- **DISCLAIMER** *The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at julf.com Tue Jul 9 10:13:45 2024 From: julf at julf.com (Johan Helsingius) Date: Tue, 9 Jul 2024 09:13:45 +0200 Subject: [NCSG-EC] Agenda for NCSG Policy Call | 15 July at 11:30 UTC In-Reply-To: References: Message-ID: <90317f73-303c-47ed-843d-e6e2cba61931@julf.com> The EC calls are not a regular thing, just scheduled as needed. Julf On 09/07/2024 08:00, Jean F. Qu?ralt via NCSG-EC wrote: > Hi Andrea, > > Are calendar invites sent for NCSG EC calls? I don't have it on my calendar. > Thx. > > Jean F. Queralt > Founder & CEO - The IO Foundation > Book a meeting (30 minutes) > > > On Fri, 5 Jul 2024 at 15:35, Tomslin Samme-Nlar via NCSG-EC > > wrote: > > Hi all, > > Looking for agenda suggestions for our meeting this month. Here are > some suggestions: > > 1. Council Agenda > 2. ICANN81 draft schedule blocks > 3. NCPH Day zero event update? > 4. DNS Africa Study update > > Warmly, > Tomslin > > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > > > > /*DISCLAIMER*/ > /The content of this message, which may contain personal or sensitive > data, is confidential. If you have received it by mistake, please inform > the sender by replying to the email and then permanently delete the > message, including any attachments. It is forbidden to copy, forward or > in any way reveal the content of this message to anyone. The integrity > and security of this email cannot be guaranteed over the Internet and, > therefore, the sender will not be held liable for any damage caused by > the message./ > > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec From julf at julf.com Tue Jul 9 10:18:10 2024 From: julf at julf.com (Johan Helsingius) Date: Tue, 9 Jul 2024 09:18:10 +0200 Subject: [NCSG-EC] TIOF - A couple of things (Membership). In-Reply-To: References: Message-ID: <0242cbad-99b9-4547-bfa2-439ad6bbf67d@julf.com> Hi Jean, > - My login credentials only work as far as resetting the password goes. > Once I set it, login gets rejected so I keep requesting password resets. > Not the end of the world, just not ideal. Hmm, odd. > - I'd say that something else is missing in the configuration as my name > does not show in the "Not Yet Responded" column and I believe at this > stage my name should be in all applications (since I haven't reviewed > any yet). The name of the EC member probably needs to be changed in the actual web page code, so for now you are simply called Tapani for the purposes of CiviCRM. :) > - Do we have an evaluation guideline somewhere? Just the charter and operating procedures. Julf From JFQueralt at theiofoundation.org Tue Jul 9 11:33:50 2024 From: JFQueralt at theiofoundation.org (=?UTF-8?Q?Jean_F=2E_Qu=C3=A9ralt?=) Date: Tue, 9 Jul 2024 16:33:50 +0800 Subject: [NCSG-EC] TIOF - A couple of things (Membership). In-Reply-To: <0242cbad-99b9-4547-bfa2-439ad6bbf67d@julf.com> References: <0242cbad-99b9-4547-bfa2-439ad6bbf67d@julf.com> Message-ID: Hi Julf. Comments inline below. > - My login credentials only work as far as resetting the password goes. > > Once I set it, login gets rejected so I keep requesting password resets. > > Not the end of the world, just not ideal. > > Hmm, odd. > > Indeed. For now, I can function. We can look into this issue later on. > > - I'd say that something else is missing in the configuration as my name > > does not show in the "Not Yet Responded" column and I believe at this > > stage my name should be in all applications (since I haven't reviewed > > any yet). > > The name of the EC member probably needs to be changed in the actual > web page code, so for now you are simply called Tapani for the purposes > of CiviCRM. :) > > [image: image.png] > > - Do we have an evaluation guideline somewhere? > > Just the charter and operating procedures. > > Noted. If no one objects, I'll draft some checklist. Best, Jean F. Queralt Founder & CEO - The IO Foundation Book a meeting (30 minutes) > Julf > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -- **DISCLAIMER** *The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message.* -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 557984 bytes Desc: not available URL: From JFQueralt at theiofoundation.org Tue Jul 9 11:34:50 2024 From: JFQueralt at theiofoundation.org (=?UTF-8?Q?Jean_F=2E_Qu=C3=A9ralt?=) Date: Tue, 9 Jul 2024 16:34:50 +0800 Subject: [NCSG-EC] Agenda for NCSG Policy Call | 15 July at 11:30 UTC In-Reply-To: <90317f73-303c-47ed-843d-e6e2cba61931@julf.com> References: <90317f73-303c-47ed-843d-e6e2cba61931@julf.com> Message-ID: Noted, thanks. Jean F. Queralt Founder & CEO - The IO Foundation Book a meeting (30 minutes) On Tue, 9 Jul 2024 at 15:13, Johan Helsingius via NCSG-EC < ncsg-ec at lists.ncsg.is> wrote: > The EC calls are not a regular thing, just scheduled as needed. > > Julf > > > On 09/07/2024 08:00, Jean F. Qu?ralt via NCSG-EC wrote: > > Hi Andrea, > > > > Are calendar invites sent for NCSG EC calls? I don't have it on my > calendar. > > Thx. > > > > Jean F. Queralt > > Founder & CEO - The IO Foundation > > Book a meeting (30 minutes) > > > > > > On Fri, 5 Jul 2024 at 15:35, Tomslin Samme-Nlar via NCSG-EC > > > wrote: > > > > Hi all, > > > > Looking for agenda suggestions for our meeting this month. Here are > > some suggestions: > > > > 1. Council Agenda > > 2. ICANN81 draft schedule blocks > > 3. NCPH Day zero event update? > > 4. DNS Africa Study update > > > > Warmly, > > Tomslin > > > > _______________________________________________ > > NCSG-EC mailing list > > NCSG-EC at lists.ncsg.is > > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > > > > > > > > /*DISCLAIMER*/ > > /The content of this message, which may contain personal or sensitive > > data, is confidential. If you have received it by mistake, please inform > > the sender by replying to the email and then permanently delete the > > message, including any attachments. It is forbidden to copy, forward or > > in any way reveal the content of this message to anyone. The integrity > > and security of this email cannot be guaranteed over the Internet and, > > therefore, the sender will not be held liable for any damage caused by > > the message./ > > > > _______________________________________________ > > NCSG-EC mailing list > > NCSG-EC at lists.ncsg.is > > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -- **DISCLAIMER** *The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From ncsg at tapani.tarvainen.info Tue Jul 9 11:49:23 2024 From: ncsg at tapani.tarvainen.info (Tapani Tarvainen) Date: Tue, 9 Jul 2024 11:49:23 +0300 Subject: [NCSG-EC] TIOF - A couple of things (Membership). In-Reply-To: <0242cbad-99b9-4547-bfa2-439ad6bbf67d@julf.com> References: <0242cbad-99b9-4547-bfa2-439ad6bbf67d@julf.com> Message-ID: On Tue, Jul 09, 2024 at 09:18:10AM +0200, Johan Helsingius (julf at julf.com) wrote: > > Hi Jean, > > > - My login credentials only work as far as resetting the password goes. > > Once I set it, login gets rejected so I keep requesting password resets. > > Not the end of the world, just not ideal. > > Hmm, odd. No idea about why that would be. > > - I'd say that something else is missing in the configuration as my name > > does not show in the "Not Yet Responded" column and I believe at this > > stage my name should be in all applications (since I haven't reviewed > > any yet). > > The name of the EC member probably needs to be changed in the actual > web page code, so for now you are simply called Tapani for the purposes > of CiviCRM. :) I'd rather not have anyone else being me so I fixed that. (The name is hardcoded in the webforms - two of them, one for individuals and one for organizations, and three times in each. Duh.) My name still shows up in the "Not Yet Responded" -column. I think that'll change as soon as the page updates (that is, when someone is approved or thatever) - let me know if not. -- Tapani Tarvainen From ncsg at tapani.tarvainen.info Tue Jul 9 12:06:38 2024 From: ncsg at tapani.tarvainen.info (Tapani Tarvainen) Date: Tue, 9 Jul 2024 12:06:38 +0300 Subject: [NCSG-EC] TIOF - A couple of things (Membership). In-Reply-To: References: <0242cbad-99b9-4547-bfa2-439ad6bbf67d@julf.com> Message-ID: On Tue, Jul 09, 2024 at 11:49:26AM +0300, Tapani Tarvainen (ncsg at tapani.tarvainen.info) wrote: > > > - I'd say that something else is missing in the configuration as my name > > > does not show in the "Not Yet Responded" column and I believe at this > > > stage my name should be in all applications (since I haven't reviewed > > > any yet). > > > > The name of the EC member probably needs to be changed in the actual > > web page code, so for now you are simply called Tapani for the purposes > > of CiviCRM. :) > > I'd rather not have anyone else being me so I fixed that. > > (The name is hardcoded in the webforms - two of them, one for > individuals and one for organizations, and three times in each. Duh.) > > My name still shows up in the "Not Yet Responded" -column. I think > that'll change as soon as the page updates (that is, when someone > is approved or thatever) - let me know if not. Not, it turned out. That was hardcoded in two more places. Fixed those, too. Do let me know iof my name still shows up somewhere it shouldn't. -- Tapani Tarvainen From JFQueralt at theiofoundation.org Tue Jul 9 12:09:31 2024 From: JFQueralt at theiofoundation.org (=?UTF-8?Q?Jean_F=2E_Qu=C3=A9ralt?=) Date: Tue, 9 Jul 2024 17:09:31 +0800 Subject: [NCSG-EC] TIOF - A couple of things (Membership). In-Reply-To: References: <0242cbad-99b9-4547-bfa2-439ad6bbf67d@julf.com> Message-ID: Thanks for that, Tapani. Much appreciated! Quick one: can you update "Jean Qouralt" to "Jean F. Queralt" ? Thx Best, Jean F. Queralt Founder & CEO - The IO Foundation Book a meeting (30 minutes) On Tue, 9 Jul 2024 at 17:06, Tapani Tarvainen via NCSG-EC < ncsg-ec at lists.ncsg.is> wrote: > On Tue, Jul 09, 2024 at 11:49:26AM +0300, Tapani Tarvainen ( > ncsg at tapani.tarvainen.info) wrote: > > > > > - I'd say that something else is missing in the configuration as my > name > > > > does not show in the "Not Yet Responded" column and I believe at this > > > > stage my name should be in all applications (since I haven't reviewed > > > > any yet). > > > > > > The name of the EC member probably needs to be changed in the actual > > > web page code, so for now you are simply called Tapani for the purposes > > > of CiviCRM. :) > > > > I'd rather not have anyone else being me so I fixed that. > > > > (The name is hardcoded in the webforms - two of them, one for > > individuals and one for organizations, and three times in each. Duh.) > > > > My name still shows up in the "Not Yet Responded" -column. I think > > that'll change as soon as the page updates (that is, when someone > > is approved or thatever) - let me know if not. > > Not, it turned out. That was hardcoded in two more places. Fixed > those, too. > > Do let me know iof my name still shows up somewhere it shouldn't. > > -- > Tapani Tarvainen > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -- **DISCLAIMER** *The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From pedrodeperdigaolana at gmail.com Tue Jul 9 14:48:32 2024 From: pedrodeperdigaolana at gmail.com (=?UTF-8?Q?Pedro_de_Perdig=C3=A3o_Lana?=) Date: Tue, 9 Jul 2024 08:48:32 -0300 Subject: [NCSG-EC] TIOF - A couple of things (Membership). In-Reply-To: References: <0242cbad-99b9-4547-bfa2-439ad6bbf67d@julf.com> Message-ID: Hi all, @Jean, just as a comment that may help identify the issue more precisely - just created my profile yesterday, and it is working normally, so it may be something related to your login info. Also, by the logic of the exchange above, I believe that I am David Morar on the platform right now. Can I change that somewhere, or I should ask Tapani for some help to change this? ? Cordially, *Pedro de Perdig?o Lana* Lawyer , GEDAI/UFPR Researcher PhD Candidate (UFPR), LLM in Business Law (UCoimbra) Board Member @ NCUC (ICANN) , ISOC BR , CC Brasil and IODA This message is restricted to the sender and recipient(s). If received by mistake, please reply informing it. Em ter., 9 de jul. de 2024 ?s 06:10, Jean F. Qu?ralt via NCSG-EC < ncsg-ec at lists.ncsg.is> escreveu: > Thanks for that, Tapani. Much appreciated! > > Quick one: can you update "Jean Qouralt" to "Jean F. Queralt" ? > Thx > > Best, > Jean F. Queralt > Founder & CEO - The IO Foundation > Book a meeting (30 minutes) > > > On Tue, 9 Jul 2024 at 17:06, Tapani Tarvainen via NCSG-EC < > ncsg-ec at lists.ncsg.is> wrote: > >> On Tue, Jul 09, 2024 at 11:49:26AM +0300, Tapani Tarvainen ( >> ncsg at tapani.tarvainen.info) wrote: >> >> > > > - I'd say that something else is missing in the configuration as my >> name >> > > > does not show in the "Not Yet Responded" column and I believe at >> this >> > > > stage my name should be in all applications (since I haven't >> reviewed >> > > > any yet). >> > > >> > > The name of the EC member probably needs to be changed in the actual >> > > web page code, so for now you are simply called Tapani for the >> purposes >> > > of CiviCRM. :) >> > >> > I'd rather not have anyone else being me so I fixed that. >> > >> > (The name is hardcoded in the webforms - two of them, one for >> > individuals and one for organizations, and three times in each. Duh.) >> > >> > My name still shows up in the "Not Yet Responded" -column. I think >> > that'll change as soon as the page updates (that is, when someone >> > is approved or thatever) - let me know if not. >> >> Not, it turned out. That was hardcoded in two more places. Fixed >> those, too. >> >> Do let me know iof my name still shows up somewhere it shouldn't. >> >> -- >> Tapani Tarvainen >> _______________________________________________ >> NCSG-EC mailing list >> NCSG-EC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >> > > *DISCLAIMER* > *The content of this message, which may contain personal or sensitive > data, is confidential. If you have received it by mistake, please inform > the sender by replying to the email and then permanently delete the > message, including any attachments. It is forbidden to copy, forward or in > any way reveal the content of this message to anyone. The integrity and > security of this email cannot be guaranteed over the Internet and, > therefore, the sender will not be held liable for any damage caused by the > message.* > _______________________________________________ > 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: From JFQueralt at theiofoundation.org Tue Jul 9 16:09:36 2024 From: JFQueralt at theiofoundation.org (=?UTF-8?Q?Jean_F=2E_Qu=C3=A9ralt?=) Date: Tue, 9 Jul 2024 21:09:36 +0800 Subject: [NCSG-EC] TIOF - A couple of things (Membership). In-Reply-To: References: <0242cbad-99b9-4547-bfa2-439ad6bbf67d@julf.com> Message-ID: Reflecting on the steps I took, I did update my email to use uppercase letters (JFQueralt at TheIOFoundation.org instead of the horrifying jfqueralt at theiofoundation.org) and thatau have messed up something. I did revert the change though with no positive result. @Tapani Tarvainen bear with us ????? Jean On Tue, Jul 9, 2024, 19:48 Pedro de Perdig?o Lana < pedrodeperdigaolana at gmail.com> wrote: > Hi all, > > @Jean, just as a comment that may help identify the issue more precisely - > just created my profile yesterday, and it is working normally, so it may be > something related to your login info. > > Also, by the logic of the exchange above, I believe that I am David Morar > on the platform right now. Can I change that somewhere, or I should ask > Tapani for some help to change this? ? > > Cordially, > > *Pedro de Perdig?o Lana* > Lawyer , GEDAI/UFPR > Researcher > PhD Candidate (UFPR), LLM in Business Law (UCoimbra) > Board Member @ NCUC (ICANN) , ISOC BR > , CC Brasil and > IODA > This message is restricted to the sender and recipient(s). If received by > mistake, please reply informing it. > > > Em ter., 9 de jul. de 2024 ?s 06:10, Jean F. Qu?ralt via NCSG-EC < > ncsg-ec at lists.ncsg.is> escreveu: > >> Thanks for that, Tapani. Much appreciated! >> >> Quick one: can you update "Jean Qouralt" to "Jean F. Queralt" ? >> Thx >> >> Best, >> Jean F. Queralt >> Founder & CEO - The IO Foundation >> Book a meeting (30 minutes) >> >> >> On Tue, 9 Jul 2024 at 17:06, Tapani Tarvainen via NCSG-EC < >> ncsg-ec at lists.ncsg.is> wrote: >> >>> On Tue, Jul 09, 2024 at 11:49:26AM +0300, Tapani Tarvainen ( >>> ncsg at tapani.tarvainen.info) wrote: >>> >>> > > > - I'd say that something else is missing in the configuration as >>> my name >>> > > > does not show in the "Not Yet Responded" column and I believe at >>> this >>> > > > stage my name should be in all applications (since I haven't >>> reviewed >>> > > > any yet). >>> > > >>> > > The name of the EC member probably needs to be changed in the actual >>> > > web page code, so for now you are simply called Tapani for the >>> purposes >>> > > of CiviCRM. :) >>> > >>> > I'd rather not have anyone else being me so I fixed that. >>> > >>> > (The name is hardcoded in the webforms - two of them, one for >>> > individuals and one for organizations, and three times in each. Duh.) >>> > >>> > My name still shows up in the "Not Yet Responded" -column. I think >>> > that'll change as soon as the page updates (that is, when someone >>> > is approved or thatever) - let me know if not. >>> >>> Not, it turned out. That was hardcoded in two more places. Fixed >>> those, too. >>> >>> Do let me know iof my name still shows up somewhere it shouldn't. >>> >>> -- >>> Tapani Tarvainen >>> _______________________________________________ >>> NCSG-EC mailing list >>> NCSG-EC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>> >> >> *DISCLAIMER* >> *The content of this message, which may contain personal or sensitive >> data, is confidential. If you have received it by mistake, please inform >> the sender by replying to the email and then permanently delete the >> message, including any attachments. It is forbidden to copy, forward or in >> any way reveal the content of this message to anyone. The integrity and >> security of this email cannot be guaranteed over the Internet and, >> therefore, the sender will not be held liable for any damage caused by the >> message.* >> _______________________________________________ >> NCSG-EC mailing list >> NCSG-EC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >> > -- **DISCLAIMER** *The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From ncsg at tapani.tarvainen.info Wed Jul 10 09:14:53 2024 From: ncsg at tapani.tarvainen.info (Tapani Tarvainen) Date: Wed, 10 Jul 2024 09:14:53 +0300 Subject: [NCSG-EC] TIOF - A couple of things (Membership). In-Reply-To: References: <0242cbad-99b9-4547-bfa2-439ad6bbf67d@julf.com> Message-ID: Hi Pedro, You can't change it yourself, the name is hardcoded in two webforms and two pieces of PHP code and editing those requires administrator privileges in CiviCRM. (Who should have those is not my decision to make, I have them just for historical reasons.) Anyway, I changed David to Pedro and Robin to Farzaneh and added F to Jean's name and fixed a couple of misspellings. Let me know if you spot typos or misspellings or places I've missed. Best, Tapani On Tue, Jul 09, 2024 at 08:48:32AM -0300, Pedro de Perdig?o Lana (pedrodeperdigaolana at gmail.com) wrote: > > Hi all, > > @Jean, just as a comment that may help identify the issue more precisely - > just created my profile yesterday, and it is working normally, so it may be > something related to your login info. > > Also, by the logic of the exchange above, I believe that I am David Morar > on the platform right now. Can I change that somewhere, or I should ask > Tapani for some help to change this? ? > > Cordially, > > *Pedro de Perdig?o Lana* > Lawyer , GEDAI/UFPR > Researcher > PhD Candidate (UFPR), LLM in Business Law (UCoimbra) > Board Member @ NCUC (ICANN) , ISOC BR > , CC Brasil and IODA > > This message is restricted to the sender and recipient(s). If received by > mistake, please reply informing it. > > > Em ter., 9 de jul. de 2024 ?s 06:10, Jean F. Qu?ralt via NCSG-EC < > ncsg-ec at lists.ncsg.is> escreveu: > > > Thanks for that, Tapani. Much appreciated! > > > > Quick one: can you update "Jean Qouralt" to "Jean F. Queralt" ? > > Thx > > > > Best, > > Jean F. Queralt > > Founder & CEO - The IO Foundation > > Book a meeting (30 minutes) > > > > > > On Tue, 9 Jul 2024 at 17:06, Tapani Tarvainen via NCSG-EC < > > ncsg-ec at lists.ncsg.is> wrote: > > > >> On Tue, Jul 09, 2024 at 11:49:26AM +0300, Tapani Tarvainen ( > >> ncsg at tapani.tarvainen.info) wrote: > >> > >> > > > - I'd say that something else is missing in the configuration as my > >> name > >> > > > does not show in the "Not Yet Responded" column and I believe at > >> this > >> > > > stage my name should be in all applications (since I haven't > >> reviewed > >> > > > any yet). > >> > > > >> > > The name of the EC member probably needs to be changed in the actual > >> > > web page code, so for now you are simply called Tapani for the > >> purposes > >> > > of CiviCRM. :) > >> > > >> > I'd rather not have anyone else being me so I fixed that. > >> > > >> > (The name is hardcoded in the webforms - two of them, one for > >> > individuals and one for organizations, and three times in each. Duh.) > >> > > >> > My name still shows up in the "Not Yet Responded" -column. I think > >> > that'll change as soon as the page updates (that is, when someone > >> > is approved or thatever) - let me know if not. > >> > >> Not, it turned out. That was hardcoded in two more places. Fixed > >> those, too. > >> > >> Do let me know iof my name still shows up somewhere it shouldn't. > >> > >> -- > >> Tapani Tarvainen > >> _______________________________________________ > >> NCSG-EC mailing list > >> NCSG-EC at lists.ncsg.is > >> https://lists.ncsg.is/mailman/listinfo/ncsg-ec > >> > > > > *DISCLAIMER* > > *The content of this message, which may contain personal or sensitive > > data, is confidential. If you have received it by mistake, please inform > > the sender by replying to the email and then permanently delete the > > message, including any attachments. It is forbidden to copy, forward or in > > any way reveal the content of this message to anyone. The integrity and > > security of this email cannot be guaranteed over the Internet and, > > therefore, the sender will not be held liable for any damage caused by the > > message.* > > _______________________________________________ > > NCSG-EC mailing list > > NCSG-EC at lists.ncsg.is > > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > > -- Tapani Tarvainen From JFQueralt at theiofoundation.org Wed Jul 10 09:44:07 2024 From: JFQueralt at theiofoundation.org (=?UTF-8?Q?Jean_F=2E_Qu=C3=A9ralt?=) Date: Wed, 10 Jul 2024 14:44:07 +0800 Subject: [NCSG-EC] TIOF - A couple of things (Membership). In-Reply-To: References: <0242cbad-99b9-4547-bfa2-439ad6bbf67d@julf.com> Message-ID: Hi Tapani. Thanks a lot for the update. @Everyone: Please ignore the TEST submissions I have made to check the whole flow. Thx. Best, Jean F. Queralt Founder & CEO - The IO Foundation Book a meeting (30 minutes) On Wed, 10 Jul 2024 at 14:14, Tapani Tarvainen wrote: > Hi Pedro, > > You can't change it yourself, the name is hardcoded in two > webforms and two pieces of PHP code and editing those requires > administrator privileges in CiviCRM. (Who should have those is > not my decision to make, I have them just for historical reasons.) > > Anyway, I changed David to Pedro and Robin to Farzaneh and added F to > Jean's name and fixed a couple of misspellings. > > Let me know if you spot typos or misspellings or places I've missed. > > Best, > > Tapani > > On Tue, Jul 09, 2024 at 08:48:32AM -0300, Pedro de Perdig?o Lana ( > pedrodeperdigaolana at gmail.com) wrote: > > > > Hi all, > > > > @Jean, just as a comment that may help identify the issue more precisely > - > > just created my profile yesterday, and it is working normally, so it may > be > > something related to your login info. > > > > Also, by the logic of the exchange above, I believe that I am David Morar > > on the platform right now. Can I change that somewhere, or I should ask > > Tapani for some help to change this? ? > > > > Cordially, > > > > *Pedro de Perdig?o Lana* > > Lawyer , GEDAI/UFPR > > Researcher > > PhD Candidate (UFPR), LLM in Business Law (UCoimbra) > > Board Member @ NCUC (ICANN) , ISOC BR > > , CC Brasil and > IODA > > > > This message is restricted to the sender and recipient(s). If received by > > mistake, please reply informing it. > > > > > > Em ter., 9 de jul. de 2024 ?s 06:10, Jean F. Qu?ralt via NCSG-EC < > > ncsg-ec at lists.ncsg.is> escreveu: > > > > > Thanks for that, Tapani. Much appreciated! > > > > > > Quick one: can you update "Jean Qouralt" to "Jean F. Queralt" ? > > > Thx > > > > > > Best, > > > Jean F. Queralt > > > Founder & CEO - The IO Foundation > > > Book a meeting (30 minutes) > > > > > > > > > On Tue, 9 Jul 2024 at 17:06, Tapani Tarvainen via NCSG-EC < > > > ncsg-ec at lists.ncsg.is> wrote: > > > > > >> On Tue, Jul 09, 2024 at 11:49:26AM +0300, Tapani Tarvainen ( > > >> ncsg at tapani.tarvainen.info) wrote: > > >> > > >> > > > - I'd say that something else is missing in the configuration > as my > > >> name > > >> > > > does not show in the "Not Yet Responded" column and I believe at > > >> this > > >> > > > stage my name should be in all applications (since I haven't > > >> reviewed > > >> > > > any yet). > > >> > > > > >> > > The name of the EC member probably needs to be changed in the > actual > > >> > > web page code, so for now you are simply called Tapani for the > > >> purposes > > >> > > of CiviCRM. :) > > >> > > > >> > I'd rather not have anyone else being me so I fixed that. > > >> > > > >> > (The name is hardcoded in the webforms - two of them, one for > > >> > individuals and one for organizations, and three times in each. > Duh.) > > >> > > > >> > My name still shows up in the "Not Yet Responded" -column. I think > > >> > that'll change as soon as the page updates (that is, when someone > > >> > is approved or thatever) - let me know if not. > > >> > > >> Not, it turned out. That was hardcoded in two more places. Fixed > > >> those, too. > > >> > > >> Do let me know iof my name still shows up somewhere it shouldn't. > > >> > > >> -- > > >> Tapani Tarvainen > > >> _______________________________________________ > > >> NCSG-EC mailing list > > >> NCSG-EC at lists.ncsg.is > > >> https://lists.ncsg.is/mailman/listinfo/ncsg-ec > > >> > > > > > > *DISCLAIMER* > > > *The content of this message, which may contain personal or sensitive > > > data, is confidential. If you have received it by mistake, please > inform > > > the sender by replying to the email and then permanently delete the > > > message, including any attachments. It is forbidden to copy, forward > or in > > > any way reveal the content of this message to anyone. The integrity and > > > security of this email cannot be guaranteed over the Internet and, > > > therefore, the sender will not be held liable for any damage caused by > the > > > message.* > > > _______________________________________________ > > > NCSG-EC mailing list > > > NCSG-EC at lists.ncsg.is > > > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > > > > > -- > Tapani Tarvainen > -- **DISCLAIMER** *The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Fri Jul 12 13:39:19 2024 From: julf at Julf.com (Johan Helsingius) Date: Fri, 12 Jul 2024 12:39:19 +0200 Subject: [NCSG-EC] Fwd: NomCom changes In-Reply-To: References: Message-ID: <107bb356-604e-436c-b386-02c1332dcd42@Julf.com> -------- Forwarded Message -------- Subject: RE: RE: NomCom changes Date: Wed, 10 Jul 2024 16:25:10 +0000 From: DiBiase, Gregory To: Demetriou, Samantha , aheineman at godaddy.com , lschulman at inta.org , MCole at perkinscoie.com , julf at Julf.com , philippe.fouquart at orange.com CC: steve.chan at icann.org , gnso-secs at icann.org , gnso-chairs at icann.org Hi All, Thank you for your patience while we worked out this process. I?ve received feedback from all of you that the proposed process is acceptable and we will proceed with randomly selecting three of seven GNSO delegates to serve one-year terms. One additional parameter arose in these conversations: there can only be: ?????? - no more than one delegate assigned the 1-yr term from the CPH ?????? - no more than one delegate assigned the 1-yr term from the BC The next step is to run the randomization exercise. Steve, myself, and the GNSO Secretariat will perform the randomization on a recorded Zoom call on Monday. If any of you would like to attend, please let me know and I will send an invite. Please let me know if you have any concerns with this approach. Thanks, Greg *From: *"DiBiase, Gregory" > *Date: *Friday, May 31, 2024 at 12:02 PM *To: *"aheineman at godaddy.com " >, Lori Schulman >, "Cole, Mason (POR)" >, Johan Helsingius >, Samantha Demetriou >, "philippe.fouquart at orange.com " > *Cc: *Steve Chan >, "gnso-secs at icann.org " > *Subject: *[EXTERNAL] RE: NomCom changes *Caution:*This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi All- fixing small typo below.? Feedback is requested by Council leadership no later than 5 June 2024 (not 31 May). *From:* DiBiase, Gregory *Sent:* Friday, May 31, 2024 7:41 AM *To:* aheineman at godaddy.com ; 'Lori Schulman' >; 'Cole, Mason (POR)' >; 'Johan Helsingius' >; 'sdemetriou at verisign.com' >; 'philippe.fouquart at orange.com' > *Cc:* Steve Chan >; gnso-secs at icann.org *Subject:* NomCom changes 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 From julf at Julf.com Fri Jul 12 13:41:03 2024 From: julf at Julf.com (Johan Helsingius) Date: Fri, 12 Jul 2024 12:41:03 +0200 Subject: [NCSG-EC] Fwd: [SOAC-Leaders-ICANNMeeting-Planning] Re: [Ext] Re: Re: ICANN81 Block Schedule, Production Timeline In-Reply-To: <9A8E9154-58C5-4F60-8674-D6DEDB1B8B70@icann.org> References: <9A8E9154-58C5-4F60-8674-D6DEDB1B8B70@icann.org> Message-ID: -------- Forwarded Message -------- Subject: [SOAC-Leaders-ICANNMeeting-Planning] Re: [Ext] Re: Re: ICANN81 Block Schedule, Production Timeline Date: Thu, 11 Jul 2024 14:56:57 +0000 From: Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning Reply-To: Nathalie Peregrine To: soac-leaders-icannmeeting-planning at icann.org Hello all! I hope you are doing well! A friendly reminder to please consider the action items below, and should topics for the ICANN81 Community Session be raised within your groups, to please share on this list for discussion. The deadline for topic submission on the list is 19 July 2024. Thank you all! Kind regards, Nathalie *From: *Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning *Reply to: *Nathalie Peregrine *Date: *Monday, 1 July 2024 at 10:20 *To: *"soac-leaders-icannmeeting-planning at icann.org" *Subject: *[SOAC-Leaders-ICANNMeeting-Planning] Re: [Ext] Re: Re: ICANN81 Block Schedule, Production Timeline Dear all, Thank you so much for joining the ICANN81 Kick off call! The input shared, be it feedback for ICANN80 and advice regarding the ICANN81 Block Schedule was extremely helpful! Please find the Zoom chat text and slide deck from the call attached to this email. ?The Zoom recording can be accessed here . Regarding the block schedule, please also find the latest version attached with the following change: * Monday?s Q&A with ICANN Org?s Executive Team removed, and replaced by the Geopolitical Forum initially scheduled on Tuesday. Thank you to Alejandra for her input on the Community Session topic deadline! The previous deadline of the 12^th July 2024 can be extended to the 19^th July 2024. However, it would be interesting to hear from community leaders on the matter before then via the mailing list. Please do bear in mind, that there is no obligation for this Community Session to take place, should there be no clear topic community groups agree upon, the session can be postponed until ICANN82. *Action Items for all:* * Kindly express any objection to the current block schedule as speedily as possible. * Please review the joint Board & SO/AC slots and raise concerns should there be any * Begin conversations about the Community Session topic and the need for such a session to be held at ICANN81 Thank you to all and have a lovely week! Kind regards, Nathalie *From: *Alejandra Reynoso Barral *Date: *Friday, 28 June 2024 at 13:04 *To: *Nathalie Peregrine *Cc: *"soac-leaders-icannmeeting-planning at icann.org" *Subject: *[Ext] Re: [SOAC-Leaders-ICANNMeeting-Planning] Re: ICANN81 Block Schedule, Production Timeline Dear Nathalie and All It was good to see/hear you at?the kickoff call. I understand the eagerness to finalize the block schedule as soon as possible, but the current 12th of July deadline to submit a community session topic is a bit tight. The ccNSO council will meet on the 18th of July and, depending on the outcome of the discussion of this item, we may or may not want to submit something. Can the deadline be extended? Best regards, Alejandra ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. ******************************************* On Wed, Jun 26, 2024 at 10:13?AM Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning > wrote: 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 > *Date: *Wednesday, 22 May 2024 at 22:13 *To: *"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 _______________________________________________ SOAC-Leaders-ICANNMeeting-Planning mailing list -- soac-leaders-icannmeeting-planning at icann.org To unsubscribe send an email to soac-leaders-icannmeeting-planning-leave at icann.org _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy ) and the website Terms of Service (https://www.icann.org/privacy/tos ). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. -------------- next part -------------- A non-text attachment was scrubbed... Name: Chat - ICANN81 Production Planning Call No 1.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 21690 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Feedback - ICANN80 and ICANN81 Planning_Kickoff_26 June 2024[4].pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 7658344 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ICANN81- AGM Istanbul DRAFT v.3 01 July 2024 - Sheet1.pdf Type: application/pdf Size: 57011 bytes Desc: not available URL: -------------- 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. -------------- 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 andrea.glandon at icann.org Fri Jul 12 16:41:15 2024 From: andrea.glandon at icann.org (Andrea Glandon) Date: Fri, 12 Jul 2024 13:41:15 +0000 Subject: [NCSG-EC] WS2 Implementation Progress Message-ID: <2B83D63F-EAB6-47E8-83BD-C16D48D719C5@icann.org> Hello NCSG EC, Please take a look at the WS2 Community Implementation spreadsheet. Can you please update the implementation status of items that are not marked Completed or Won?t Be Implemented? If still not implemented, can you please provide a timeline for implementation? https://docs.google.com/spreadsheets/d/1xxPZjIjrjLBiKjcgWKbhhxWhbsBdcRudCqRDl4W5UlY/edit?usp=sharing Thank you! Andrea Glandon Policy Operations Sr. Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: acglandon76 -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrea.glandon at icann.org Fri Jul 12 20:45:08 2024 From: andrea.glandon at icann.org (Andrea Glandon) Date: Fri, 12 Jul 2024 17:45:08 +0000 Subject: [NCSG-EC] Ageia Densi (Argentina) Message-ID: Hello NCSG EC, The organization Ageia Densi is already an approved NCSG and NCUC member. They would like to add NPOC to their membership. I have looked at the charter and do not see anything specific regarding this situation. How should this situation be handled? Do they have to go through the regular application process? Thanks! Andrea Glandon Policy Operations Sr. Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: acglandon76 -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Fri Jul 12 23:20:27 2024 From: julf at Julf.com (Johan Helsingius) Date: Fri, 12 Jul 2024 22:20:27 +0200 Subject: [NCSG-EC] Ageia Densi (Argentina) In-Reply-To: References: Message-ID: <2cea847b-caf8-4084-9491-ff70abc6ffaa@Julf.com> If the NPOC reps are OK with it, I think we can just OK them. Julf On 12/07/2024 19:45, Andrea Glandon via NCSG-EC wrote: > Hello NCSG EC, > > The organization Ageia Densi is already an approved NCSG and NCUC > member. They would like to add NPOC to their membership. I have looked > at the charter and do not see anything specific regarding this > situation. How should this situation be handled? Do they have to go > through the regular application process? > > Thanks! > > *Andrea Glandon* > > Policy Operations Sr. Coordinator > > Internet Corporation for Assigned Names and Numbers (ICANN) > > *Skype ID:*acglandon76 > > > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec From JFQueralt at theiofoundation.org Sat Jul 13 08:58:17 2024 From: JFQueralt at theiofoundation.org (=?UTF-8?Q?Jean_F=2E_Qu=C3=A9ralt?=) Date: Sat, 13 Jul 2024 13:58:17 +0800 Subject: [NCSG-EC] Ageia Densi (Argentina) In-Reply-To: References: Message-ID: Hi Andrea. Looking into this now. Just for the sake of extra info, have they indicated any reason for joining NPOC? Best, Jean F. Queralt Founder & CEO - The IO Foundation Book a meeting (30 minutes) On Sat, 13 Jul 2024 at 01:45, Andrea Glandon via NCSG-EC < ncsg-ec at lists.ncsg.is> wrote: > Hello NCSG EC, > > > > The organization Ageia Densi is already an approved NCSG and NCUC member. > They would like to add NPOC to their membership. I have looked at the > charter and do not see anything specific regarding this situation. How > should this situation be handled? Do they have to go through the regular > application process? > > > > Thanks! > > *Andrea Glandon* > > Policy Operations Sr. Coordinator > > Internet Corporation for Assigned Names and Numbers (ICANN) > > *Skype ID:* acglandon76 > > > > > > > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -- **DISCLAIMER** *The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From muyiwacaleb at gmail.com Sat Jul 13 16:39:43 2024 From: muyiwacaleb at gmail.com (Caleb Olumuyiwa Ogundele) Date: Sat, 13 Jul 2024 08:39:43 -0500 Subject: [NCSG-EC] Ageia Densi (Argentina) In-Reply-To: <2cea847b-caf8-4084-9491-ff70abc6ffaa@Julf.com> References: <2cea847b-caf8-4084-9491-ff70abc6ffaa@Julf.com> Message-ID: Hi Andrea, Yes you can go ahead and add them. On Fri, Jul 12, 2024, 3:20?PM Johan Helsingius via NCSG-EC < ncsg-ec at lists.ncsg.is> wrote: > If the NPOC reps are OK with it, I think we can just OK them. > > Julf > > > On 12/07/2024 19:45, Andrea Glandon via NCSG-EC wrote: > > Hello NCSG EC, > > > > The organization Ageia Densi is already an approved NCSG and NCUC > > member. They would like to add NPOC to their membership. I have looked > > at the charter and do not see anything specific regarding this > > situation. How should this situation be handled? Do they have to go > > through the regular application process? > > > > Thanks! > > > > *Andrea Glandon* > > > > Policy Operations Sr. Coordinator > > > > Internet Corporation for Assigned Names and Numbers (ICANN) > > > > *Skype ID:*acglandon76 > > > > > > _______________________________________________ > > NCSG-EC mailing list > > NCSG-EC at lists.ncsg.is > > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -------------- next part -------------- An HTML attachment was scrubbed... URL: From JFQueralt at theiofoundation.org Sat Jul 13 16:42:06 2024 From: JFQueralt at theiofoundation.org (=?UTF-8?Q?Jean_F=2E_Qu=C3=A9ralt?=) Date: Sat, 13 Jul 2024 21:42:06 +0800 Subject: [NCSG-EC] Ageia Densi (Argentina) In-Reply-To: References: <2cea847b-caf8-4084-9491-ff70abc6ffaa@Julf.com> Message-ID: Hi. @Caleb Olumuyiwa Ogundele is that your opinion or the final decision? Jean On Sat, Jul 13, 2024, 21:40 Caleb Olumuyiwa Ogundele via NCSG-EC < ncsg-ec at lists.ncsg.is> wrote: > Hi Andrea, > > Yes you can go ahead and add them. > > On Fri, Jul 12, 2024, 3:20?PM Johan Helsingius via NCSG-EC < > ncsg-ec at lists.ncsg.is> wrote: > >> If the NPOC reps are OK with it, I think we can just OK them. >> >> Julf >> >> >> On 12/07/2024 19:45, Andrea Glandon via NCSG-EC wrote: >> > Hello NCSG EC, >> > >> > The organization Ageia Densi is already an approved NCSG and NCUC >> > member. They would like to add NPOC to their membership. I have looked >> > at the charter and do not see anything specific regarding this >> > situation. How should this situation be handled? Do they have to go >> > through the regular application process? >> > >> > Thanks! >> > >> > *Andrea Glandon* >> > >> > Policy Operations Sr. Coordinator >> > >> > Internet Corporation for Assigned Names and Numbers (ICANN) >> > >> > *Skype ID:*acglandon76 >> > >> > >> > _______________________________________________ >> > NCSG-EC mailing list >> > NCSG-EC at lists.ncsg.is >> > https://lists.ncsg.is/mailman/listinfo/ncsg-ec >> _______________________________________________ >> NCSG-EC mailing list >> NCSG-EC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >> > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -- **DISCLAIMER** *The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From JFQueralt at theiofoundation.org Sat Jul 13 20:20:43 2024 From: JFQueralt at theiofoundation.org (=?UTF-8?Q?Jean_F=2E_Qu=C3=A9ralt?=) Date: Sun, 14 Jul 2024 01:20:43 +0800 Subject: [NCSG-EC] Ageia Densi (Argentina) In-Reply-To: References: Message-ID: Hi all, I have confirmed that there is a procedural impasse that needs to be addressed before we register AGEIA DENSI as a member to NPOC. 1) First of all, it is to be noted that, as @Andrea Glandon has mentioned, I have not found reference/info on this type of procedure. It would appear we are playing it by ear, which is fine to a degree. I'd nonetheless recommend that moving forward we take the opportunity to write this case scenario somewhere. I can work on the language and submit a proposal. 2) The applicant, AGEIA DENSI, is not in a position at this very moment, to comply with one of the requirements to be a member of NPOC. As per NPOC Charter: 2. Membership > c. Requirements > 3.Is a registrant of a domain name. Currently, the organization does not own their previous domain anymore (and it would appear that no other domain either). After reaching out to the org's rep, I am confirmed this is a situation they are actively looking to resolve. Once that's done, I'll be OK with them joining. Meanwhile, I rather apply procedure and put the topic on standby. Also, @Andrea Glandon can you clarify if they have a) Requested information about whether is it possible b) Formally requested to join NPOC Thanks. Regards, Jean F. Queralt Founder & CEO - The IO Foundation Book a meeting (30 minutes) On Sat, 13 Jul 2024 at 01:45, Andrea Glandon via NCSG-EC < ncsg-ec at lists.ncsg.is> wrote: > Hello NCSG EC, > > > > The organization Ageia Densi is already an approved NCSG and NCUC member. > They would like to add NPOC to their membership. I have looked at the > charter and do not see anything specific regarding this situation. How > should this situation be handled? Do they have to go through the regular > application process? > > > > Thanks! > > *Andrea Glandon* > > Policy Operations Sr. Coordinator > > Internet Corporation for Assigned Names and Numbers (ICANN) > > *Skype ID:* acglandon76 > > > > > > > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -- **DISCLAIMER** *The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From JFQueralt at theiofoundation.org Sat Jul 13 22:12:24 2024 From: JFQueralt at theiofoundation.org (=?UTF-8?Q?Jean_F=2E_Qu=C3=A9ralt?=) Date: Sun, 14 Jul 2024 03:12:24 +0800 Subject: [NCSG-EC] Ageia Densi (Argentina) In-Reply-To: References: Message-ID: Hi all, I've been informed that the organization has reacquired their domain ( http://www.ageia.org/) The website is not up although that should not be a consideration for us. For all I am concerned, I give my thumbs up for when/if AGEIA DENSI requests to join NPOC without having to undergo a new membership application. Best, Jean F. Queralt Founder & CEO - The IO Foundation Book a meeting (30 minutes) On Sun, 14 Jul 2024 at 01:20, Jean F. Qu?ralt wrote: > Hi all, > > I have confirmed that there is a procedural impasse that needs to be > addressed before we register AGEIA DENSI as a member to NPOC. > > 1) First of all, it is to be noted that, as @Andrea Glandon > has mentioned, I have not found reference/info > on this type of procedure. It would appear we are playing it by ear, which > is fine to a degree. > I'd nonetheless recommend that moving forward we take the opportunity to > write this case scenario somewhere. I can work on the language and submit a > proposal. > > 2) The applicant, AGEIA DENSI, is not in a position at this very moment, > to comply with one of the requirements to be a member of NPOC. > As per NPOC Charter: > 2. Membership > c. Requirements > 3.Is a registrant of a domain name. > > Currently, the organization does not own their previous domain anymore > (and it would appear that no other domain either). > After reaching out to the org's rep, I am confirmed this is a situation > they are actively looking to resolve. > Once that's done, I'll be OK with them joining. Meanwhile, I rather apply > procedure and put the topic on standby. > > Also, @Andrea Glandon can you clarify if they > have > a) Requested information about whether is it possible > b) Formally requested to join NPOC > Thanks. > > Regards, > Jean F. Queralt > Founder & CEO - The IO Foundation > Book a meeting (30 minutes) > > > On Sat, 13 Jul 2024 at 01:45, Andrea Glandon via NCSG-EC < > ncsg-ec at lists.ncsg.is> wrote: > >> Hello NCSG EC, >> >> >> >> The organization Ageia Densi is already an approved NCSG and NCUC member. >> They would like to add NPOC to their membership. I have looked at the >> charter and do not see anything specific regarding this situation. How >> should this situation be handled? Do they have to go through the regular >> application process? >> >> >> >> Thanks! >> >> *Andrea Glandon* >> >> Policy Operations Sr. Coordinator >> >> Internet Corporation for Assigned Names and Numbers (ICANN) >> >> *Skype ID:* acglandon76 >> >> >> >> >> >> >> _______________________________________________ >> NCSG-EC mailing list >> NCSG-EC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >> > -- **DISCLAIMER** *The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From muyiwacaleb at gmail.com Sun Jul 14 01:39:00 2024 From: muyiwacaleb at gmail.com (Caleb Olumuyiwa Ogundele) Date: Sat, 13 Jul 2024 17:39:00 -0500 Subject: [NCSG-EC] Ageia Densi (Argentina) In-Reply-To: References: Message-ID: Hi Everyone, I did a little more digging. I will be declining my support for AGEIA DENSI. The domain Jean mentioned is parked and until when it is active, we can't seem to find out. Ideally, I would grant this but given as with the usual procedure, more information is requested. Regards On Sat, Jul 13, 2024 at 2:13?PM Jean F. Qu?ralt via NCSG-EC < ncsg-ec at lists.ncsg.is> wrote: > Hi all, > > I've been informed that the organization has reacquired their domain ( > http://www.ageia.org/) > The website is not up although that should not be a consideration for us. > > For all I am concerned, I give my thumbs up for when/if AGEIA DENSI > requests to join NPOC without having to undergo a new membership > application. > > Best, > Jean F. Queralt > Founder & CEO - The IO Foundation > Book a meeting (30 minutes) > > > On Sun, 14 Jul 2024 at 01:20, Jean F. Qu?ralt < > JFQueralt at theiofoundation.org> wrote: > >> Hi all, >> >> I have confirmed that there is a procedural impasse that needs to be >> addressed before we register AGEIA DENSI as a member to NPOC. >> >> 1) First of all, it is to be noted that, as @Andrea Glandon >> has mentioned, I have not found >> reference/info on this type of procedure. It would appear we are playing it >> by ear, which is fine to a degree. >> I'd nonetheless recommend that moving forward we take the opportunity to >> write this case scenario somewhere. I can work on the language and submit a >> proposal. >> >> 2) The applicant, AGEIA DENSI, is not in a position at this very moment, >> to comply with one of the requirements to be a member of NPOC. >> As per NPOC Charter: >> 2. Membership > c. Requirements > 3.Is a registrant of a domain name. >> >> Currently, the organization does not own their previous domain anymore >> (and it would appear that no other domain either). >> After reaching out to the org's rep, I am confirmed this is a situation >> they are actively looking to resolve. >> Once that's done, I'll be OK with them joining. Meanwhile, I rather apply >> procedure and put the topic on standby. >> >> Also, @Andrea Glandon can you clarify if they >> have >> a) Requested information about whether is it possible >> b) Formally requested to join NPOC >> Thanks. >> >> Regards, >> Jean F. Queralt >> Founder & CEO - The IO Foundation >> Book a meeting (30 minutes) >> >> >> On Sat, 13 Jul 2024 at 01:45, Andrea Glandon via NCSG-EC < >> ncsg-ec at lists.ncsg.is> wrote: >> >>> Hello NCSG EC, >>> >>> >>> >>> The organization Ageia Densi is already an approved NCSG and NCUC >>> member. They would like to add NPOC to their membership. I have looked at >>> the charter and do not see anything specific regarding this situation. How >>> should this situation be handled? Do they have to go through the regular >>> application process? >>> >>> >>> >>> Thanks! >>> >>> *Andrea Glandon* >>> >>> Policy Operations Sr. Coordinator >>> >>> Internet Corporation for Assigned Names and Numbers (ICANN) >>> >>> *Skype ID:* acglandon76 >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> NCSG-EC mailing list >>> NCSG-EC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>> >> > *DISCLAIMER* > *The content of this message, which may contain personal or sensitive > data, is confidential. If you have received it by mistake, please inform > the sender by replying to the email and then permanently delete the > message, including any attachments. It is forbidden to copy, forward or in > any way reveal the content of this message to anyone. The integrity and > security of this email cannot be guaranteed over the Internet and, > therefore, the sender will not be held liable for any damage caused by the > message.* > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -- *Caleb Ogundele* Email: muyiwacaleb at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From JFQueralt at theiofoundation.org Sun Jul 14 06:25:48 2024 From: JFQueralt at theiofoundation.org (=?UTF-8?Q?Jean_F=2E_Qu=C3=A9ralt?=) Date: Sun, 14 Jul 2024 11:25:48 +0800 Subject: [NCSG-EC] Ageia Densi (Argentina) In-Reply-To: References: Message-ID: Hi Caleb, Does this mean that membership requires specific proof of ownership to be verified? How do you propose we do that? I haven't seen a mention to this on the existing documentation. Personally, I don't see a problem with having a domain parked (which in this case is because they reacquired it hours ago). As mentioned in my previous message, NPOC's charter requires ownership. It says nothing about usage. There are plenty of reasons why an organization may not be actively using their domain. Sometimes they don't even want to have a website and just want to protect themselves against impersonation. I've met orgs like that. If we are going down the rabbit hole of actively verifying ownership, given the current Lookup/RDRS status, we have a few options that we then need to document properly. Option 1) We give some custom code that needs to be injected into the Public Info so that it can be found through https://lookup.icann.org/en/lookup Option 2) We give some custom code that needs to be injected in a TXT record that we then query Option 3) We give some custom code that needs to be injected in a text file on the root of their https server so we can query it (https://domain/NPOC-Code.txt) There may be other options. These already cost more work for the EC. The situation now is we need to decide what's our procedure or we'll get stuck here. Jean On Sun, Jul 14, 2024, 06:39 Caleb Olumuyiwa Ogundele wrote: > Hi Everyone, > > I did a little more digging. I will be declining my support for AGEIA > DENSI. > The domain Jean mentioned is parked and until when it is active, we can't > seem to find out. Ideally, I would grant this but given as with the usual > procedure, more information is requested. > > Regards > > On Sat, Jul 13, 2024 at 2:13?PM Jean F. Qu?ralt via NCSG-EC < > ncsg-ec at lists.ncsg.is> wrote: > >> Hi all, >> >> I've been informed that the organization has reacquired their domain ( >> http://www.ageia.org/) >> The website is not up although that should not be a consideration for us. >> >> For all I am concerned, I give my thumbs up for when/if AGEIA DENSI >> requests to join NPOC without having to undergo a new membership >> application. >> >> Best, >> Jean F. Queralt >> Founder & CEO - The IO Foundation >> Book a meeting (30 minutes) >> >> >> On Sun, 14 Jul 2024 at 01:20, Jean F. Qu?ralt < >> JFQueralt at theiofoundation.org> wrote: >> >>> Hi all, >>> >>> I have confirmed that there is a procedural impasse that needs to be >>> addressed before we register AGEIA DENSI as a member to NPOC. >>> >>> 1) First of all, it is to be noted that, as @Andrea Glandon >>> has mentioned, I have not found >>> reference/info on this type of procedure. It would appear we are playing it >>> by ear, which is fine to a degree. >>> I'd nonetheless recommend that moving forward we take the opportunity to >>> write this case scenario somewhere. I can work on the language and submit a >>> proposal. >>> >>> 2) The applicant, AGEIA DENSI, is not in a position at this very moment, >>> to comply with one of the requirements to be a member of NPOC. >>> As per NPOC Charter: >>> 2. Membership > c. Requirements > 3.Is a registrant of a domain name. >>> >>> Currently, the organization does not own their previous domain anymore >>> (and it would appear that no other domain either). >>> After reaching out to the org's rep, I am confirmed this is a situation >>> they are actively looking to resolve. >>> Once that's done, I'll be OK with them joining. Meanwhile, I rather >>> apply procedure and put the topic on standby. >>> >>> Also, @Andrea Glandon can you clarify if >>> they have >>> a) Requested information about whether is it possible >>> b) Formally requested to join NPOC >>> Thanks. >>> >>> Regards, >>> Jean F. Queralt >>> Founder & CEO - The IO Foundation >>> Book a meeting (30 minutes) >>> >>> >>> On Sat, 13 Jul 2024 at 01:45, Andrea Glandon via NCSG-EC < >>> ncsg-ec at lists.ncsg.is> wrote: >>> >>>> Hello NCSG EC, >>>> >>>> >>>> >>>> The organization Ageia Densi is already an approved NCSG and NCUC >>>> member. They would like to add NPOC to their membership. I have looked at >>>> the charter and do not see anything specific regarding this situation. How >>>> should this situation be handled? Do they have to go through the regular >>>> application process? >>>> >>>> >>>> >>>> Thanks! >>>> >>>> *Andrea Glandon* >>>> >>>> Policy Operations Sr. Coordinator >>>> >>>> Internet Corporation for Assigned Names and Numbers (ICANN) >>>> >>>> *Skype ID:* acglandon76 >>>> >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> NCSG-EC mailing list >>>> NCSG-EC at lists.ncsg.is >>>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>>> >>> >> *DISCLAIMER* >> *The content of this message, which may contain personal or sensitive >> data, is confidential. If you have received it by mistake, please inform >> the sender by replying to the email and then permanently delete the >> message, including any attachments. It is forbidden to copy, forward or in >> any way reveal the content of this message to anyone. The integrity and >> security of this email cannot be guaranteed over the Internet and, >> therefore, the sender will not be held liable for any damage caused by the >> message.* >> _______________________________________________ >> NCSG-EC mailing list >> NCSG-EC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >> > > > -- > *Caleb Ogundele* > Email: muyiwacaleb at gmail.com > -- **DISCLAIMER** *The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From pedrodeperdigaolana at gmail.com Sun Jul 14 18:19:30 2024 From: pedrodeperdigaolana at gmail.com (=?UTF-8?Q?Pedro_de_Perdig=C3=A3o_Lana?=) Date: Sun, 14 Jul 2024 12:19:30 -0300 Subject: [NCSG-EC] Ageia Densi (Argentina) In-Reply-To: References: Message-ID: Hi Jean, Caleb, Is the Charter marked by upcoming in the wiki already in effect? If not, the previous/current chart seems to have a higher bar: "5.1.1.6 Own at least one domain name *and maintain or have plans to create an organization website*". Another question: within NCSG, Ageia Densi is an international organization (encompassing Ageia Densi Brazil as well) or an Argentinian one? On our website, the Argentinian one seems to be affiliated with NCSG/NCUC, with Franco as its rep, but, digging for more info, Carlos Aguirre seems to be the official rep of the international part. Sorry if I'm not being precise, it is a bit hard to find clear and recent info about it through search tools. Cordially, *Pedro de Perdig?o Lana* Lawyer , GEDAI/UFPR Researcher PhD Candidate (UFPR), LLM in Business Law (UCoimbra) Board Member @ NCUC (ICANN) , ISOC BR , CC Brasil and IODA This message is restricted to the sender and recipient(s). If received by mistake, please reply informing it. Em dom., 14 de jul. de 2024 ?s 00:26, Jean F. Qu?ralt via NCSG-EC < ncsg-ec at lists.ncsg.is> escreveu: > Hi Caleb, > > Does this mean that membership requires specific proof of ownership to be > verified? > > How do you propose we do that? > I haven't seen a mention to this on the existing documentation. > > Personally, I don't see a problem with having a domain parked (which in > this case is because they reacquired it hours ago). > > As mentioned in my previous message, NPOC's charter requires ownership. It > says nothing about usage. > > There are plenty of reasons why an organization may not be actively using > their domain. Sometimes they don't even want to have a website and just > want to protect themselves against impersonation. I've met orgs like that. > > If we are going down the rabbit hole of actively verifying ownership, > given the current Lookup/RDRS status, we have a few options that we then > need to document properly. > > Option 1) > We give some custom code that needs to be injected into the Public Info so > that it can be found through > https://lookup.icann.org/en/lookup > > Option 2) > We give some custom code that needs to be injected in a TXT record that we > then query > > Option 3) > We give some custom code that needs to be injected in a text file on the > root of their https server so we can query it ( > https://domain/NPOC-Code.txt) > > There may be other options. These already cost more work for the EC. > > The situation now is we need to decide what's our procedure or we'll get > stuck here. > > Jean > > > On Sun, Jul 14, 2024, 06:39 Caleb Olumuyiwa Ogundele < > muyiwacaleb at gmail.com> wrote: > >> Hi Everyone, >> >> I did a little more digging. I will be declining my support for AGEIA >> DENSI. >> The domain Jean mentioned is parked and until when it is active, we can't >> seem to find out. Ideally, I would grant this but given as with the usual >> procedure, more information is requested. >> >> Regards >> >> On Sat, Jul 13, 2024 at 2:13?PM Jean F. Qu?ralt via NCSG-EC < >> ncsg-ec at lists.ncsg.is> wrote: >> >>> Hi all, >>> >>> I've been informed that the organization has reacquired their domain ( >>> http://www.ageia.org/) >>> The website is not up although that should not be a consideration for us. >>> >>> For all I am concerned, I give my thumbs up for when/if AGEIA DENSI >>> requests to join NPOC without having to undergo a new membership >>> application. >>> >>> Best, >>> Jean F. Queralt >>> Founder & CEO - The IO Foundation >>> Book a meeting (30 minutes) >>> >>> >>> On Sun, 14 Jul 2024 at 01:20, Jean F. Qu?ralt < >>> JFQueralt at theiofoundation.org> wrote: >>> >>>> Hi all, >>>> >>>> I have confirmed that there is a procedural impasse that needs to be >>>> addressed before we register AGEIA DENSI as a member to NPOC. >>>> >>>> 1) First of all, it is to be noted that, as @Andrea Glandon >>>> has mentioned, I have not found >>>> reference/info on this type of procedure. It would appear we are playing it >>>> by ear, which is fine to a degree. >>>> I'd nonetheless recommend that moving forward we take the opportunity >>>> to write this case scenario somewhere. I can work on the language and >>>> submit a proposal. >>>> >>>> 2) The applicant, AGEIA DENSI, is not in a position at this very >>>> moment, to comply with one of the requirements to be a member of NPOC. >>>> As per NPOC Charter: >>>> 2. Membership > c. Requirements > 3.Is a registrant of a domain name. >>>> >>>> Currently, the organization does not own their previous domain anymore >>>> (and it would appear that no other domain either). >>>> After reaching out to the org's rep, I am confirmed this is a situation >>>> they are actively looking to resolve. >>>> Once that's done, I'll be OK with them joining. Meanwhile, I rather >>>> apply procedure and put the topic on standby. >>>> >>>> Also, @Andrea Glandon can you clarify if >>>> they have >>>> a) Requested information about whether is it possible >>>> b) Formally requested to join NPOC >>>> Thanks. >>>> >>>> Regards, >>>> Jean F. Queralt >>>> Founder & CEO - The IO Foundation >>>> Book a meeting (30 minutes) >>>> >>>> >>>> On Sat, 13 Jul 2024 at 01:45, Andrea Glandon via NCSG-EC < >>>> ncsg-ec at lists.ncsg.is> wrote: >>>> >>>>> Hello NCSG EC, >>>>> >>>>> >>>>> >>>>> The organization Ageia Densi is already an approved NCSG and NCUC >>>>> member. They would like to add NPOC to their membership. I have looked at >>>>> the charter and do not see anything specific regarding this situation. How >>>>> should this situation be handled? Do they have to go through the regular >>>>> application process? >>>>> >>>>> >>>>> >>>>> Thanks! >>>>> >>>>> *Andrea Glandon* >>>>> >>>>> Policy Operations Sr. Coordinator >>>>> >>>>> Internet Corporation for Assigned Names and Numbers (ICANN) >>>>> >>>>> *Skype ID:* acglandon76 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> NCSG-EC mailing list >>>>> NCSG-EC at lists.ncsg.is >>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>>>> >>>> >>> *DISCLAIMER* >>> *The content of this message, which may contain personal or sensitive >>> data, is confidential. If you have received it by mistake, please inform >>> the sender by replying to the email and then permanently delete the >>> message, including any attachments. It is forbidden to copy, forward or in >>> any way reveal the content of this message to anyone. The integrity and >>> security of this email cannot be guaranteed over the Internet and, >>> therefore, the sender will not be held liable for any damage caused by the >>> message.* >>> _______________________________________________ >>> NCSG-EC mailing list >>> NCSG-EC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>> >> >> >> -- >> *Caleb Ogundele* >> Email: muyiwacaleb at gmail.com >> > > *DISCLAIMER* > *The content of this message, which may contain personal or sensitive > data, is confidential. If you have received it by mistake, please inform > the sender by replying to the email and then permanently delete the > message, including any attachments. It is forbidden to copy, forward or in > any way reveal the content of this message to anyone. The integrity and > security of this email cannot be guaranteed over the Internet and, > therefore, the sender will not be held liable for any damage caused by the > message.* > _______________________________________________ > 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: From JFQueralt at theiofoundation.org Sun Jul 14 18:29:39 2024 From: JFQueralt at theiofoundation.org (=?UTF-8?Q?Jean_F=2E_Qu=C3=A9ralt?=) Date: Sun, 14 Jul 2024 23:29:39 +0800 Subject: [NCSG-EC] Ageia Densi (Argentina) In-Reply-To: References: Message-ID: Hi Pedro. > Is the Charter marked by upcoming > in the wiki > already in effect? If not, the previous/current chart > seems to have a > higher bar: "5.1.1.6 Own at least one domain name *and maintain or have > plans to create an organization website*". > It is my understanding that the current applicable charter is the one I referenced as the new positions in the last election were those described in it. I admit I'm fuzzy about that as the transition never was fully clear to me. Probably Andrea and Daniel can shed light on this. On the other hand, "plans to create an organization website" is definitely a qualitative concept that can't be measured and open to interpretation at an operational level. I'm more comfortable with just the ownership (of which we need to establish a procedure for verification as I mentioned) so I hope that's not applicable anymore because it would be pretty much an admin nightmare. > Another question: within NCSG, Ageia Densi is an international > organization (encompassing Ageia Densi Brazil as well) or an Argentinian > one? On our website, the Argentinian one seems to be affiliated with > NCSG/NCUC, with Franco as its rep, but, digging for more info, Carlos > Aguirre seems to be the official rep of the international part. Sorry if > I'm not being precise, it is a bit hard to find clear and recent info about > it through search tools. > All I was able to find was their FB page and ALAC profile. There I saw Juan Manuel Rojas was a Rep. Is your doubt about their structure and actual jurisdiction of registration? Regards, Jean > Cordially, > > *Pedro de Perdig?o Lana* > Lawyer , GEDAI/UFPR > Researcher > PhD Candidate (UFPR), LLM in Business Law (UCoimbra) > Board Member @ NCUC (ICANN) , ISOC BR > , CC Brasil and > IODA > This message is restricted to the sender and recipient(s). If received by > mistake, please reply informing it. > > > Em dom., 14 de jul. de 2024 ?s 00:26, Jean F. Qu?ralt via NCSG-EC < > ncsg-ec at lists.ncsg.is> escreveu: > >> Hi Caleb, >> >> Does this mean that membership requires specific proof of ownership to be >> verified? >> >> How do you propose we do that? >> I haven't seen a mention to this on the existing documentation. >> >> Personally, I don't see a problem with having a domain parked (which in >> this case is because they reacquired it hours ago). >> >> As mentioned in my previous message, NPOC's charter requires ownership. >> It says nothing about usage. >> >> There are plenty of reasons why an organization may not be actively using >> their domain. Sometimes they don't even want to have a website and just >> want to protect themselves against impersonation. I've met orgs like that. >> >> If we are going down the rabbit hole of actively verifying ownership, >> given the current Lookup/RDRS status, we have a few options that we then >> need to document properly. >> >> Option 1) >> We give some custom code that needs to be injected into the Public Info >> so that it can be found through >> https://lookup.icann.org/en/lookup >> >> Option 2) >> We give some custom code that needs to be injected in a TXT record that >> we then query >> >> Option 3) >> We give some custom code that needs to be injected in a text file on the >> root of their https server so we can query it ( >> https://domain/NPOC-Code.txt) >> >> There may be other options. These already cost more work for the EC. >> >> The situation now is we need to decide what's our procedure or we'll get >> stuck here. >> >> Jean >> >> >> On Sun, Jul 14, 2024, 06:39 Caleb Olumuyiwa Ogundele < >> muyiwacaleb at gmail.com> wrote: >> >>> Hi Everyone, >>> >>> I did a little more digging. I will be declining my support for AGEIA >>> DENSI. >>> The domain Jean mentioned is parked and until when it is active, we >>> can't seem to find out. Ideally, I would grant this but given as with the >>> usual procedure, more information is requested. >>> >>> Regards >>> >>> On Sat, Jul 13, 2024 at 2:13?PM Jean F. Qu?ralt via NCSG-EC < >>> ncsg-ec at lists.ncsg.is> wrote: >>> >>>> Hi all, >>>> >>>> I've been informed that the organization has reacquired their domain ( >>>> http://www.ageia.org/) >>>> The website is not up although that should not be a consideration for >>>> us. >>>> >>>> For all I am concerned, I give my thumbs up for when/if AGEIA DENSI >>>> requests to join NPOC without having to undergo a new membership >>>> application. >>>> >>>> Best, >>>> Jean F. Queralt >>>> Founder & CEO - The IO Foundation >>>> Book a meeting (30 minutes) >>>> >>>> >>>> On Sun, 14 Jul 2024 at 01:20, Jean F. Qu?ralt < >>>> JFQueralt at theiofoundation.org> wrote: >>>> >>>>> Hi all, >>>>> >>>>> I have confirmed that there is a procedural impasse that needs to be >>>>> addressed before we register AGEIA DENSI as a member to NPOC. >>>>> >>>>> 1) First of all, it is to be noted that, as @Andrea Glandon >>>>> has mentioned, I have not found >>>>> reference/info on this type of procedure. It would appear we are playing it >>>>> by ear, which is fine to a degree. >>>>> I'd nonetheless recommend that moving forward we take the opportunity >>>>> to write this case scenario somewhere. I can work on the language and >>>>> submit a proposal. >>>>> >>>>> 2) The applicant, AGEIA DENSI, is not in a position at this very >>>>> moment, to comply with one of the requirements to be a member of NPOC. >>>>> As per NPOC Charter: >>>>> 2. Membership > c. Requirements > 3.Is a registrant of a domain name. >>>>> >>>>> Currently, the organization does not own their previous domain anymore >>>>> (and it would appear that no other domain either). >>>>> After reaching out to the org's rep, I am confirmed this is a >>>>> situation they are actively looking to resolve. >>>>> Once that's done, I'll be OK with them joining. Meanwhile, I rather >>>>> apply procedure and put the topic on standby. >>>>> >>>>> Also, @Andrea Glandon can you clarify if >>>>> they have >>>>> a) Requested information about whether is it possible >>>>> b) Formally requested to join NPOC >>>>> Thanks. >>>>> >>>>> Regards, >>>>> Jean F. Queralt >>>>> Founder & CEO - The IO Foundation >>>>> Book a meeting (30 minutes) >>>>> >>>>> >>>>> On Sat, 13 Jul 2024 at 01:45, Andrea Glandon via NCSG-EC < >>>>> ncsg-ec at lists.ncsg.is> wrote: >>>>> >>>>>> Hello NCSG EC, >>>>>> >>>>>> >>>>>> >>>>>> The organization Ageia Densi is already an approved NCSG and NCUC >>>>>> member. They would like to add NPOC to their membership. I have looked at >>>>>> the charter and do not see anything specific regarding this situation. How >>>>>> should this situation be handled? Do they have to go through the regular >>>>>> application process? >>>>>> >>>>>> >>>>>> >>>>>> Thanks! >>>>>> >>>>>> *Andrea Glandon* >>>>>> >>>>>> Policy Operations Sr. Coordinator >>>>>> >>>>>> Internet Corporation for Assigned Names and Numbers (ICANN) >>>>>> >>>>>> *Skype ID:* acglandon76 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> NCSG-EC mailing list >>>>>> NCSG-EC at lists.ncsg.is >>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>>>>> >>>>> >>>> *DISCLAIMER* >>>> *The content of this message, which may contain personal or sensitive >>>> data, is confidential. If you have received it by mistake, please inform >>>> the sender by replying to the email and then permanently delete the >>>> message, including any attachments. It is forbidden to copy, forward or in >>>> any way reveal the content of this message to anyone. The integrity and >>>> security of this email cannot be guaranteed over the Internet and, >>>> therefore, the sender will not be held liable for any damage caused by the >>>> message.* >>>> _______________________________________________ >>>> NCSG-EC mailing list >>>> NCSG-EC at lists.ncsg.is >>>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>>> >>> >>> >>> -- >>> *Caleb Ogundele* >>> Email: muyiwacaleb at gmail.com >>> >> >> *DISCLAIMER* >> *The content of this message, which may contain personal or sensitive >> data, is confidential. If you have received it by mistake, please inform >> the sender by replying to the email and then permanently delete the >> message, including any attachments. It is forbidden to copy, forward or in >> any way reveal the content of this message to anyone. The integrity and >> security of this email cannot be guaranteed over the Internet and, >> therefore, the sender will not be held liable for any damage caused by the >> message.* >> _______________________________________________ >> NCSG-EC mailing list >> NCSG-EC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >> > -- **DISCLAIMER** *The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From pedrodeperdigaolana at gmail.com Sun Jul 14 18:49:38 2024 From: pedrodeperdigaolana at gmail.com (=?UTF-8?Q?Pedro_de_Perdig=C3=A3o_Lana?=) Date: Sun, 14 Jul 2024 12:49:38 -0300 Subject: [NCSG-EC] Ageia Densi (Argentina) In-Reply-To: References: Message-ID: Thanks for your answers, Jean! My doubt was actually if it was the same organization (that is already part of NCUC/NCSG) asking to be a part of NPOC. I'm saying this because in LACRALO there are two different ALS, Ageia Densi Argentina and Ageia Densi Brazil, while you can find other manifestations that seem to refer to Ageia Densi as an international org with Argentia as its headquarters. In his LinkedIn, Juan appears to be the president of "Ageia Densi Colombia", which is a third organization (and that I couldn't find before in the ALAC ALS search because it is listed as MINKA Colombia - https://atlarge.icann.org/alses/lacralo, which was the name I remember him being affiliated to a few months ago). I think we need to better understand if there is a difference with the person who requested the affiliation. Cordially, *Pedro de Perdig?o Lana* Advogado - OAB/PR 90.600 , Pesquisador (GEDAI/UFPR ) Doutorando em Direito (UFPR), Mestre em Direito Empresarial (UCoimbra), Membro da Coordena??o - NCUC (ICANN) , ISOC BR , IODA e CC Brasil . Essa mensagem ? restrita ao remetente e destinat?rio(s). Se recebida por engano, favor responder informando o erro. Em dom., 14 de jul. de 2024 ?s 12:29, Jean F. Qu?ralt < JFQueralt at theiofoundation.org> escreveu: > Hi Pedro. > > > >> Is the Charter marked by upcoming >> in the wiki >> already in effect? If not, the previous/current chart >> seems to have a >> higher bar: "5.1.1.6 Own at least one domain name *and maintain or have >> plans to create an organization website*". >> > > > It is my understanding that the current applicable charter is the one I > referenced as the new positions in the last election were those described > in it. > > I admit I'm fuzzy about that as the transition never was fully clear to > me. > Probably Andrea and Daniel can shed light on this. > > On the other hand, "plans to create an organization website" is definitely > a qualitative concept that can't be measured and open to interpretation at > an operational level. > I'm more comfortable with just the ownership (of which we need to > establish a procedure for verification as I mentioned) so I hope that's not > applicable anymore because it would be pretty much an admin nightmare. > > > >> Another question: within NCSG, Ageia Densi is an international >> organization (encompassing Ageia Densi Brazil as well) or an Argentinian >> one? On our website, the Argentinian one seems to be affiliated with >> NCSG/NCUC, with Franco as its rep, but, digging for more info, Carlos >> Aguirre seems to be the official rep of the international part. Sorry if >> I'm not being precise, it is a bit hard to find clear and recent info about >> it through search tools. >> > > All I was able to find was their FB page and ALAC profile. There I saw > Juan Manuel Rojas was a Rep. > > Is your doubt about their structure and actual jurisdiction of > registration? > > Regards, > Jean > > >> Cordially, >> >> *Pedro de Perdig?o Lana* >> Lawyer , GEDAI/UFPR >> Researcher >> PhD Candidate (UFPR), LLM in Business Law (UCoimbra) >> Board Member @ NCUC (ICANN) , ISOC BR >> , CC Brasil and >> IODA >> This message is restricted to the sender and recipient(s). If received by >> mistake, please reply informing it. >> >> >> Em dom., 14 de jul. de 2024 ?s 00:26, Jean F. Qu?ralt via NCSG-EC < >> ncsg-ec at lists.ncsg.is> escreveu: >> >>> Hi Caleb, >>> >>> Does this mean that membership requires specific proof of ownership to >>> be verified? >>> >>> How do you propose we do that? >>> I haven't seen a mention to this on the existing documentation. >>> >>> Personally, I don't see a problem with having a domain parked (which in >>> this case is because they reacquired it hours ago). >>> >>> As mentioned in my previous message, NPOC's charter requires ownership. >>> It says nothing about usage. >>> >>> There are plenty of reasons why an organization may not be actively >>> using their domain. Sometimes they don't even want to have a website and >>> just want to protect themselves against impersonation. I've met orgs like >>> that. >>> >>> If we are going down the rabbit hole of actively verifying ownership, >>> given the current Lookup/RDRS status, we have a few options that we then >>> need to document properly. >>> >>> Option 1) >>> We give some custom code that needs to be injected into the Public Info >>> so that it can be found through >>> https://lookup.icann.org/en/lookup >>> >>> Option 2) >>> We give some custom code that needs to be injected in a TXT record that >>> we then query >>> >>> Option 3) >>> We give some custom code that needs to be injected in a text file on the >>> root of their https server so we can query it ( >>> https://domain/NPOC-Code.txt) >>> >>> There may be other options. These already cost more work for the EC. >>> >>> The situation now is we need to decide what's our procedure or we'll get >>> stuck here. >>> >>> Jean >>> >>> >>> On Sun, Jul 14, 2024, 06:39 Caleb Olumuyiwa Ogundele < >>> muyiwacaleb at gmail.com> wrote: >>> >>>> Hi Everyone, >>>> >>>> I did a little more digging. I will be declining my support for AGEIA >>>> DENSI. >>>> The domain Jean mentioned is parked and until when it is active, we >>>> can't seem to find out. Ideally, I would grant this but given as with the >>>> usual procedure, more information is requested. >>>> >>>> Regards >>>> >>>> On Sat, Jul 13, 2024 at 2:13?PM Jean F. Qu?ralt via NCSG-EC < >>>> ncsg-ec at lists.ncsg.is> wrote: >>>> >>>>> Hi all, >>>>> >>>>> I've been informed that the organization has reacquired their domain ( >>>>> http://www.ageia.org/) >>>>> The website is not up although that should not be a consideration for >>>>> us. >>>>> >>>>> For all I am concerned, I give my thumbs up for when/if AGEIA DENSI >>>>> requests to join NPOC without having to undergo a new membership >>>>> application. >>>>> >>>>> Best, >>>>> Jean F. Queralt >>>>> Founder & CEO - The IO Foundation >>>>> Book a meeting (30 minutes) >>>>> >>>>> >>>>> On Sun, 14 Jul 2024 at 01:20, Jean F. Qu?ralt < >>>>> JFQueralt at theiofoundation.org> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> I have confirmed that there is a procedural impasse that needs to be >>>>>> addressed before we register AGEIA DENSI as a member to NPOC. >>>>>> >>>>>> 1) First of all, it is to be noted that, as @Andrea Glandon >>>>>> has mentioned, I have not found >>>>>> reference/info on this type of procedure. It would appear we are playing it >>>>>> by ear, which is fine to a degree. >>>>>> I'd nonetheless recommend that moving forward we take the opportunity >>>>>> to write this case scenario somewhere. I can work on the language and >>>>>> submit a proposal. >>>>>> >>>>>> 2) The applicant, AGEIA DENSI, is not in a position at this very >>>>>> moment, to comply with one of the requirements to be a member of NPOC. >>>>>> As per NPOC Charter: >>>>>> 2. Membership > c. Requirements > 3.Is a registrant of a domain name. >>>>>> >>>>>> Currently, the organization does not own their previous domain >>>>>> anymore (and it would appear that no other domain either). >>>>>> After reaching out to the org's rep, I am confirmed this is a >>>>>> situation they are actively looking to resolve. >>>>>> Once that's done, I'll be OK with them joining. Meanwhile, I rather >>>>>> apply procedure and put the topic on standby. >>>>>> >>>>>> Also, @Andrea Glandon can you clarify if >>>>>> they have >>>>>> a) Requested information about whether is it possible >>>>>> b) Formally requested to join NPOC >>>>>> Thanks. >>>>>> >>>>>> Regards, >>>>>> Jean F. Queralt >>>>>> Founder & CEO - The IO Foundation >>>>>> Book a meeting (30 minutes) >>>>>> >>>>>> >>>>>> On Sat, 13 Jul 2024 at 01:45, Andrea Glandon via NCSG-EC < >>>>>> ncsg-ec at lists.ncsg.is> wrote: >>>>>> >>>>>>> Hello NCSG EC, >>>>>>> >>>>>>> >>>>>>> >>>>>>> The organization Ageia Densi is already an approved NCSG and NCUC >>>>>>> member. They would like to add NPOC to their membership. I have looked at >>>>>>> the charter and do not see anything specific regarding this situation. How >>>>>>> should this situation be handled? Do they have to go through the regular >>>>>>> application process? >>>>>>> >>>>>>> >>>>>>> >>>>>>> Thanks! >>>>>>> >>>>>>> *Andrea Glandon* >>>>>>> >>>>>>> Policy Operations Sr. Coordinator >>>>>>> >>>>>>> Internet Corporation for Assigned Names and Numbers (ICANN) >>>>>>> >>>>>>> *Skype ID:* acglandon76 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> NCSG-EC mailing list >>>>>>> NCSG-EC at lists.ncsg.is >>>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>>>>>> >>>>>> >>>>> *DISCLAIMER* >>>>> *The content of this message, which may contain personal or sensitive >>>>> data, is confidential. If you have received it by mistake, please inform >>>>> the sender by replying to the email and then permanently delete the >>>>> message, including any attachments. It is forbidden to copy, forward or in >>>>> any way reveal the content of this message to anyone. The integrity and >>>>> security of this email cannot be guaranteed over the Internet and, >>>>> therefore, the sender will not be held liable for any damage caused by the >>>>> message.* >>>>> _______________________________________________ >>>>> NCSG-EC mailing list >>>>> NCSG-EC at lists.ncsg.is >>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>>>> >>>> >>>> >>>> -- >>>> *Caleb Ogundele* >>>> Email: muyiwacaleb at gmail.com >>>> >>> >>> *DISCLAIMER* >>> *The content of this message, which may contain personal or sensitive >>> data, is confidential. If you have received it by mistake, please inform >>> the sender by replying to the email and then permanently delete the >>> message, including any attachments. It is forbidden to copy, forward or in >>> any way reveal the content of this message to anyone. The integrity and >>> security of this email cannot be guaranteed over the Internet and, >>> therefore, the sender will not be held liable for any damage caused by the >>> message.* >>> _______________________________________________ >>> NCSG-EC mailing list >>> NCSG-EC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>> >> > *DISCLAIMER* > *The content of this message, which may contain personal or sensitive > data, is confidential. If you have received it by mistake, please inform > the sender by replying to the email and then permanently delete the > message, including any attachments. It is forbidden to copy, forward or in > any way reveal the content of this message to anyone. The integrity and > security of this email cannot be guaranteed over the Internet and, > therefore, the sender will not be held liable for any damage caused by the > message.* > -------------- next part -------------- An HTML attachment was scrubbed... URL: From JFQueralt at theiofoundation.org Sun Jul 14 18:59:13 2024 From: JFQueralt at theiofoundation.org (=?UTF-8?Q?Jean_F=2E_Qu=C3=A9ralt?=) Date: Sun, 14 Jul 2024 23:59:13 +0800 Subject: [NCSG-EC] Ageia Densi (Argentina) In-Reply-To: References: Message-ID: Yes, that makes a lot of sense. I don't have access to the CRM. @Andrea Glandon could you give is some extra information on the source of the inquiry/request? Thx. Regards, Jean On Sun, Jul 14, 2024, 23:49 Pedro de Perdig?o Lana < pedrodeperdigaolana at gmail.com> wrote: > Thanks for your answers, Jean! > > My doubt was actually if it was the same organization (that is already > part of NCUC/NCSG) asking to be a part of NPOC. > > I'm saying this because in LACRALO there are two different ALS, Ageia > Densi Argentina and Ageia Densi Brazil, while you can find other > manifestations that seem to refer to Ageia Densi as an international org > with Argentia as its headquarters. In his LinkedIn, Juan appears to be the > president of "Ageia Densi Colombia", which is a third organization (and > that I couldn't find before in the ALAC ALS search because it is listed as > MINKA Colombia - https://atlarge.icann.org/alses/lacralo, which was the > name I remember him being affiliated to a few months ago). I think we need > to better understand if there is a difference with the person who requested > the affiliation. > > Cordially, > > *Pedro de Perdig?o Lana* > Advogado - OAB/PR 90.600 , Pesquisador (GEDAI/UFPR > ) > Doutorando em Direito (UFPR), Mestre em Direito Empresarial (UCoimbra), > Membro da Coordena??o - NCUC (ICANN) , ISOC BR > , IODA e CC Brasil > . > Essa mensagem ? restrita ao remetente e destinat?rio(s). Se recebida por > engano, favor responder informando o erro. > > > Em dom., 14 de jul. de 2024 ?s 12:29, Jean F. Qu?ralt < > JFQueralt at theiofoundation.org> escreveu: > >> Hi Pedro. >> >> >> >>> Is the Charter marked by upcoming >>> in the >>> wiki already in effect? If not, the previous/current chart >>> seems to have a >>> higher bar: "5.1.1.6 Own at least one domain name *and maintain or have >>> plans to create an organization website*". >>> >> >> >> It is my understanding that the current applicable charter is the one I >> referenced as the new positions in the last election were those described >> in it. >> >> I admit I'm fuzzy about that as the transition never was fully clear to >> me. >> Probably Andrea and Daniel can shed light on this. >> >> On the other hand, "plans to create an organization website" is >> definitely a qualitative concept that can't be measured and open to >> interpretation at an operational level. >> I'm more comfortable with just the ownership (of which we need to >> establish a procedure for verification as I mentioned) so I hope that's not >> applicable anymore because it would be pretty much an admin nightmare. >> >> >> >>> Another question: within NCSG, Ageia Densi is an international >>> organization (encompassing Ageia Densi Brazil as well) or an Argentinian >>> one? On our website, the Argentinian one seems to be affiliated with >>> NCSG/NCUC, with Franco as its rep, but, digging for more info, Carlos >>> Aguirre seems to be the official rep of the international part. Sorry if >>> I'm not being precise, it is a bit hard to find clear and recent info about >>> it through search tools. >>> >> >> All I was able to find was their FB page and ALAC profile. There I saw >> Juan Manuel Rojas was a Rep. >> >> Is your doubt about their structure and actual jurisdiction of >> registration? >> >> Regards, >> Jean >> >> >>> Cordially, >>> >>> *Pedro de Perdig?o Lana* >>> Lawyer , GEDAI/UFPR >>> Researcher >>> PhD Candidate (UFPR), LLM in Business Law (UCoimbra) >>> Board Member @ NCUC (ICANN) , ISOC BR >>> , CC Brasil and >>> IODA >>> This message is restricted to the sender and recipient(s). If received >>> by mistake, please reply informing it. >>> >>> >>> Em dom., 14 de jul. de 2024 ?s 00:26, Jean F. Qu?ralt via NCSG-EC < >>> ncsg-ec at lists.ncsg.is> escreveu: >>> >>>> Hi Caleb, >>>> >>>> Does this mean that membership requires specific proof of ownership to >>>> be verified? >>>> >>>> How do you propose we do that? >>>> I haven't seen a mention to this on the existing documentation. >>>> >>>> Personally, I don't see a problem with having a domain parked (which in >>>> this case is because they reacquired it hours ago). >>>> >>>> As mentioned in my previous message, NPOC's charter requires ownership. >>>> It says nothing about usage. >>>> >>>> There are plenty of reasons why an organization may not be actively >>>> using their domain. Sometimes they don't even want to have a website and >>>> just want to protect themselves against impersonation. I've met orgs like >>>> that. >>>> >>>> If we are going down the rabbit hole of actively verifying ownership, >>>> given the current Lookup/RDRS status, we have a few options that we then >>>> need to document properly. >>>> >>>> Option 1) >>>> We give some custom code that needs to be injected into the Public Info >>>> so that it can be found through >>>> https://lookup.icann.org/en/lookup >>>> >>>> Option 2) >>>> We give some custom code that needs to be injected in a TXT record that >>>> we then query >>>> >>>> Option 3) >>>> We give some custom code that needs to be injected in a text file on >>>> the root of their https server so we can query it ( >>>> https://domain/NPOC-Code.txt) >>>> >>>> There may be other options. These already cost more work for the EC. >>>> >>>> The situation now is we need to decide what's our procedure or we'll >>>> get stuck here. >>>> >>>> Jean >>>> >>>> >>>> On Sun, Jul 14, 2024, 06:39 Caleb Olumuyiwa Ogundele < >>>> muyiwacaleb at gmail.com> wrote: >>>> >>>>> Hi Everyone, >>>>> >>>>> I did a little more digging. I will be declining my support for AGEIA >>>>> DENSI. >>>>> The domain Jean mentioned is parked and until when it is active, we >>>>> can't seem to find out. Ideally, I would grant this but given as with the >>>>> usual procedure, more information is requested. >>>>> >>>>> Regards >>>>> >>>>> On Sat, Jul 13, 2024 at 2:13?PM Jean F. Qu?ralt via NCSG-EC < >>>>> ncsg-ec at lists.ncsg.is> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> I've been informed that the organization has reacquired their domain ( >>>>>> http://www.ageia.org/) >>>>>> The website is not up although that should not be a consideration for >>>>>> us. >>>>>> >>>>>> For all I am concerned, I give my thumbs up for when/if AGEIA DENSI >>>>>> requests to join NPOC without having to undergo a new membership >>>>>> application. >>>>>> >>>>>> Best, >>>>>> Jean F. Queralt >>>>>> Founder & CEO - The IO Foundation >>>>>> Book a meeting (30 minutes) >>>>>> >>>>>> >>>>>> On Sun, 14 Jul 2024 at 01:20, Jean F. Qu?ralt < >>>>>> JFQueralt at theiofoundation.org> wrote: >>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> I have confirmed that there is a procedural impasse that needs to be >>>>>>> addressed before we register AGEIA DENSI as a member to NPOC. >>>>>>> >>>>>>> 1) First of all, it is to be noted that, as @Andrea Glandon >>>>>>> has mentioned, I have not found >>>>>>> reference/info on this type of procedure. It would appear we are playing it >>>>>>> by ear, which is fine to a degree. >>>>>>> I'd nonetheless recommend that moving forward we take the >>>>>>> opportunity to write this case scenario somewhere. I can work on the >>>>>>> language and submit a proposal. >>>>>>> >>>>>>> 2) The applicant, AGEIA DENSI, is not in a position at this very >>>>>>> moment, to comply with one of the requirements to be a member of NPOC. >>>>>>> As per NPOC Charter: >>>>>>> 2. Membership > c. Requirements > 3.Is a registrant of a domain name. >>>>>>> >>>>>>> Currently, the organization does not own their previous domain >>>>>>> anymore (and it would appear that no other domain either). >>>>>>> After reaching out to the org's rep, I am confirmed this is a >>>>>>> situation they are actively looking to resolve. >>>>>>> Once that's done, I'll be OK with them joining. Meanwhile, I rather >>>>>>> apply procedure and put the topic on standby. >>>>>>> >>>>>>> Also, @Andrea Glandon can you clarify if >>>>>>> they have >>>>>>> a) Requested information about whether is it possible >>>>>>> b) Formally requested to join NPOC >>>>>>> Thanks. >>>>>>> >>>>>>> Regards, >>>>>>> Jean F. Queralt >>>>>>> Founder & CEO - The IO Foundation >>>>>>> Book a meeting (30 minutes) >>>>>>> >>>>>>> >>>>>>> On Sat, 13 Jul 2024 at 01:45, Andrea Glandon via NCSG-EC < >>>>>>> ncsg-ec at lists.ncsg.is> wrote: >>>>>>> >>>>>>>> Hello NCSG EC, >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> The organization Ageia Densi is already an approved NCSG and NCUC >>>>>>>> member. They would like to add NPOC to their membership. I have looked at >>>>>>>> the charter and do not see anything specific regarding this situation. How >>>>>>>> should this situation be handled? Do they have to go through the regular >>>>>>>> application process? >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Thanks! >>>>>>>> >>>>>>>> *Andrea Glandon* >>>>>>>> >>>>>>>> Policy Operations Sr. Coordinator >>>>>>>> >>>>>>>> Internet Corporation for Assigned Names and Numbers (ICANN) >>>>>>>> >>>>>>>> *Skype ID:* acglandon76 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> NCSG-EC mailing list >>>>>>>> NCSG-EC at lists.ncsg.is >>>>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>>>>>>> >>>>>>> >>>>>> *DISCLAIMER* >>>>>> *The content of this message, which may contain personal or sensitive >>>>>> data, is confidential. If you have received it by mistake, please inform >>>>>> the sender by replying to the email and then permanently delete the >>>>>> message, including any attachments. It is forbidden to copy, forward or in >>>>>> any way reveal the content of this message to anyone. The integrity and >>>>>> security of this email cannot be guaranteed over the Internet and, >>>>>> therefore, the sender will not be held liable for any damage caused by the >>>>>> message.* >>>>>> _______________________________________________ >>>>>> NCSG-EC mailing list >>>>>> NCSG-EC at lists.ncsg.is >>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Caleb Ogundele* >>>>> Email: muyiwacaleb at gmail.com >>>>> >>>> >>>> *DISCLAIMER* >>>> *The content of this message, which may contain personal or sensitive >>>> data, is confidential. If you have received it by mistake, please inform >>>> the sender by replying to the email and then permanently delete the >>>> message, including any attachments. It is forbidden to copy, forward or in >>>> any way reveal the content of this message to anyone. The integrity and >>>> security of this email cannot be guaranteed over the Internet and, >>>> therefore, the sender will not be held liable for any damage caused by the >>>> message.* >>>> _______________________________________________ >>>> NCSG-EC mailing list >>>> NCSG-EC at lists.ncsg.is >>>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>>> >>> >> *DISCLAIMER* >> *The content of this message, which may contain personal or sensitive >> data, is confidential. If you have received it by mistake, please inform >> the sender by replying to the email and then permanently delete the >> message, including any attachments. It is forbidden to copy, forward or in >> any way reveal the content of this message to anyone. The integrity and >> security of this email cannot be guaranteed over the Internet and, >> therefore, the sender will not be held liable for any damage caused by the >> message.* >> > -- **DISCLAIMER** *The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrea.glandon at icann.org Mon Jul 15 14:51:37 2024 From: andrea.glandon at icann.org (Andrea Glandon) Date: Mon, 15 Jul 2024 11:51:37 +0000 Subject: [NCSG-EC] [Ext] Re: Ageia Densi (Argentina) In-Reply-To: References: Message-ID: Hello all, This request came to me from Juan Manuel. Someone reached out to him. I do not have any further information. I told Juan I would find out what the procedure is to add them. Kind Regards, Andrea From: "Jean F. Qu?ralt" Date: Sunday, July 14, 2024 at 10:59 To: Pedro de Perdig?o Lana , Andrea Glandon Cc: Caleb Olumuyiwa Ogundele , NCSG EC Subject: [Ext] Re: [NCSG-EC] Ageia Densi (Argentina) Yes, that makes a lot of sense. I don't have access to the CRM. @Andrea Glandon could you give is some extra information on the source of the inquiry/request? Thx. Regards, Jean On Sun, Jul 14, 2024, 23:49 Pedro de Perdig?o Lana > wrote: Thanks for your answers, Jean! My doubt was actually if it was the same organization (that is already part of NCUC/NCSG) asking to be a part of NPOC. I'm saying this because in LACRALO there are two different ALS, Ageia Densi Argentina and Ageia Densi Brazil, while you can find other manifestations that seem to refer to Ageia Densi as an international org with Argentia as its headquarters. In his LinkedIn, Juan appears to be the president of "Ageia Densi Colombia", which is a third organization (and that I couldn't find before in the ALAC ALS search because it is listed as MINKA Colombia - https://atlarge.icann.org/alses/lacralo [atlarge.icann.org], which was the name I remember him being affiliated to a few months ago). I think we need to better understand if there is a difference with the person who requested the affiliation. Cordially, Pedro de Perdig?o Lana Advogado - OAB/PR 90.600 [nic.br], Pesquisador (GEDAI/UFPR [gedai.com.br]) Doutorando em Direito (UFPR), Mestre em Direito Empresarial (UCoimbra), Membro da Coordena??o - NCUC (ICANN) [ncuc.org], ISOC BR [isoc.org.br], IODA [ioda.org.br] e CC Brasil [br.creativecommons.net]. Essa mensagem ? restrita ao remetente e destinat?rio(s). Se recebida por engano, favor responder informando o erro. Em dom., 14 de jul. de 2024 ?s 12:29, Jean F. Qu?ralt > escreveu: Hi Pedro. Is the Charter marked by upcoming in the wiki already in effect? If not, the previous/current chart seems to have a higher bar: "5.1.1.6 Own at least one domain name and maintain or have plans to create an organization website". It is my understanding that the current applicable charter is the one I referenced as the new positions in the last election were those described in it. I admit I'm fuzzy about that as the transition never was fully clear to me. Probably Andrea and Daniel can shed light on this. On the other hand, "plans to create an organization website" is definitely a qualitative concept that can't be measured and open to interpretation at an operational level. I'm more comfortable with just the ownership (of which we need to establish a procedure for verification as I mentioned) so I hope that's not applicable anymore because it would be pretty much an admin nightmare. Another question: within NCSG, Ageia Densi is an international organization (encompassing Ageia Densi Brazil as well) or an Argentinian one? On our website, the Argentinian one seems to be affiliated with NCSG/NCUC, with Franco as its rep, but, digging for more info, Carlos Aguirre seems to be the official rep of the international part. Sorry if I'm not being precise, it is a bit hard to find clear and recent info about it through search tools. All I was able to find was their FB page and ALAC profile. There I saw Juan Manuel Rojas was a Rep. Is your doubt about their structure and actual jurisdiction of registration? Regards, Jean Cordially, Pedro de Perdig?o Lana Lawyer [nic.br], GEDAI/UFPR [gedai.com.br] Researcher PhD Candidate (UFPR), LLM in Business Law (UCoimbra) Board Member @ NCUC (ICANN) [ncuc.org], ISOC BR [isoc.org.br], CC Brasil [br.creativecommons.net] and IODA [ioda.org.br] This message is restricted to the sender and recipient(s). If received by mistake, please reply informing it. Em dom., 14 de jul. de 2024 ?s 00:26, Jean F. Qu?ralt via NCSG-EC > escreveu: Hi Caleb, Does this mean that membership requires specific proof of ownership to be verified? How do you propose we do that? I haven't seen a mention to this on the existing documentation. Personally, I don't see a problem with having a domain parked (which in this case is because they reacquired it hours ago). As mentioned in my previous message, NPOC's charter requires ownership. It says nothing about usage. There are plenty of reasons why an organization may not be actively using their domain. Sometimes they don't even want to have a website and just want to protect themselves against impersonation. I've met orgs like that. If we are going down the rabbit hole of actively verifying ownership, given the current Lookup/RDRS status, we have a few options that we then need to document properly. Option 1) We give some custom code that needs to be injected into the Public Info so that it can be found through https://lookup.icann.org/en/lookup [lookup.icann.org] Option 2) We give some custom code that needs to be injected in a TXT record that we then query Option 3) We give some custom code that needs to be injected in a text file on the root of their https server so we can query it (https://domain/NPOC-Code.txt [domain]) There may be other options. These already cost more work for the EC. The situation now is we need to decide what's our procedure or we'll get stuck here. Jean On Sun, Jul 14, 2024, 06:39 Caleb Olumuyiwa Ogundele > wrote: Hi Everyone, I did a little more digging. I will be declining my support for AGEIA DENSI. The domain Jean mentioned is parked and until when it is active, we can't seem to find out. Ideally, I would grant this but given as with the usual procedure, more information is requested. Regards On Sat, Jul 13, 2024 at 2:13?PM Jean F. Qu?ralt via NCSG-EC > wrote: Hi all, I've been informed that the organization has reacquired their domain (http://www.ageia.org/ [ageia.org]) The website is not up although that should not be a consideration for us. For all I am concerned, I give my thumbs up for when/if AGEIA DENSI requests to join NPOC without having to undergo a new membership application. Best, Jean F. Queralt Founder & CEO - The IO Foundation [theiofoundation.org] Book a meeting [tiof.click] (30 minutes) On Sun, 14 Jul 2024 at 01:20, Jean F. Qu?ralt > wrote: Hi all, I have confirmed that there is a procedural impasse that needs to be addressed before we register AGEIA DENSI as a member to NPOC. 1) First of all, it is to be noted that, as @Andrea Glandon has mentioned, I have not found reference/info on this type of procedure. It would appear we are playing it by ear, which is fine to a degree. I'd nonetheless recommend that moving forward we take the opportunity to write this case scenario somewhere. I can work on the language and submit a proposal. 2) The applicant, AGEIA DENSI, is not in a position at this very moment, to comply with one of the requirements to be a member of NPOC. As per NPOC Charter: 2. Membership > c. Requirements > 3.Is a registrant of a domain name. Currently, the organization does not own their previous domain anymore (and it would appear that no other domain either). After reaching out to the org's rep, I am confirmed this is a situation they are actively looking to resolve. Once that's done, I'll be OK with them joining. Meanwhile, I rather apply procedure and put the topic on standby. Also, @Andrea Glandon can you clarify if they have a) Requested information about whether is it possible b) Formally requested to join NPOC Thanks. Regards, Jean F. Queralt Founder & CEO - The IO Foundation [theiofoundation.org] Book a meeting [tiof.click] (30 minutes) On Sat, 13 Jul 2024 at 01:45, Andrea Glandon via NCSG-EC > wrote: Hello NCSG EC, The organization Ageia Densi is already an approved NCSG and NCUC member. They would like to add NPOC to their membership. I have looked at the charter and do not see anything specific regarding this situation. How should this situation be handled? Do they have to go through the regular application process? Thanks! Andrea Glandon Policy Operations Sr. Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: acglandon76 _______________________________________________ NCSG-EC mailing list NCSG-EC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-ec [lists.ncsg.is] DISCLAIMER The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message. _______________________________________________ NCSG-EC mailing list NCSG-EC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-ec [lists.ncsg.is] -- Caleb Ogundele Email: muyiwacaleb at gmail.com DISCLAIMER The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message. _______________________________________________ NCSG-EC mailing list NCSG-EC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-ec [lists.ncsg.is] DISCLAIMER The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message. DISCLAIMER The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message. -------------- next part -------------- An HTML attachment was scrubbed... URL: From JFQueralt at theiofoundation.org Mon Jul 15 18:57:19 2024 From: JFQueralt at theiofoundation.org (=?UTF-8?Q?Jean_F=2E_Qu=C3=A9ralt?=) Date: Mon, 15 Jul 2024 23:57:19 +0800 Subject: [NCSG-EC] [Ext] Re: Ageia Densi (Argentina) In-Reply-To: References: Message-ID: Hi. Thx for the info @Andrea Glandon ! Can anyone confirm which ANGEIA DENSI is the one currently registered? I don't have access to the CRM and I can't confirm it is the same organization that is registered in NCUC. (I should assume it is yet a verification is due.) My position is that even if a number of organizations are from the same network and share name by existing in different jurisdictions should request membership separately. Again, nothing specific in this scenario that I can find. Regards, Jean F. Queralt Founder & CEO - The IO Foundation Book a meeting (30 minutes) On Mon, 15 Jul 2024 at 19:51, Andrea Glandon wrote: > Hello all, > > > > This request came to me from Juan Manuel. Someone reached out to him. I do > not have any further information. I told Juan I would find out what the > procedure is to add them. > > > > Kind Regards, > > Andrea > > > > > > *From: *"Jean F. Qu?ralt" > *Date: *Sunday, July 14, 2024 at 10:59 > *To: *Pedro de Perdig?o Lana , Andrea > Glandon > *Cc: *Caleb Olumuyiwa Ogundele , NCSG EC < > ncsg-ec at lists.ncsg.is> > *Subject: *[Ext] Re: [NCSG-EC] Ageia Densi (Argentina) > > > > Yes, that makes a lot of sense. > > > > I don't have access to the CRM. > > @Andrea Glandon could you give is some extra > information on the source of the inquiry/request? > > Thx. > > > > Regards, > > Jean > > > > On Sun, Jul 14, 2024, 23:49 Pedro de Perdig?o Lana < > pedrodeperdigaolana at gmail.com> wrote: > > Thanks for your answers, Jean! > > > > My doubt was actually if it was the same organization (that is already > part of NCUC/NCSG) asking to be a part of NPOC. > > > > I'm saying this because in LACRALO there are two different ALS, Ageia > Densi Argentina and Ageia Densi Brazil, while you can find other > manifestations that seem to refer to Ageia Densi as an international org > with Argentia as its headquarters. In his LinkedIn, Juan appears to be the > president of "Ageia Densi Colombia", which is a third organization (and > that I couldn't find before in the ALAC ALS search because it is listed as > MINKA Colombia - https://atlarge.icann.org/alses/lacralo > [atlarge.icann.org] > , > which was the name I remember him being affiliated to a few months ago). I > think we need to better understand if there is a difference with the person > who requested the affiliation. > > > > Cordially, > > > > *Pedro de Perdig?o Lana* > > Advogado - OAB/PR 90.600 [nic.br] > , > Pesquisador (GEDAI/UFPR [gedai.com.br] > > ) > > Doutorando em Direito (UFPR), Mestre em Direito Empresarial (UCoimbra), > > Membro da Coordena??o - NCUC (ICANN) [ncuc.org] > , > ISOC BR [isoc.org.br] > , > IODA [ioda.org.br] > > e CC Brasil [br.creativecommons.net] > > . > > Essa mensagem ? restrita ao remetente e destinat?rio(s). Se recebida por > engano, favor responder informando o erro. > > > > > > Em dom., 14 de jul. de 2024 ?s 12:29, Jean F. Qu?ralt < > JFQueralt at theiofoundation.org> escreveu: > > Hi Pedro. > > > > > > > > Is the Charter marked by upcoming > in the wiki > already in effect? If not, the previous/current chart > seems to have a > higher bar: "5.1.1.6 Own at least one domain name *and maintain or have > plans to create an organization website*". > > > > > > It is my understanding that the current applicable charter is the one I > referenced as the new positions in the last election were those described > in it. > > > > I admit I'm fuzzy about that as the transition never was fully clear to > me. > > Probably Andrea and Daniel can shed light on this. > > > > On the other hand, "plans to create an organization website" is definitely > a qualitative concept that can't be measured and open to interpretation at > an operational level. > > I'm more comfortable with just the ownership (of which we need to > establish a procedure for verification as I mentioned) so I hope that's not > applicable anymore because it would be pretty much an admin nightmare. > > > > > > > > Another question: within NCSG, Ageia Densi is an international > organization (encompassing Ageia Densi Brazil as well) or an Argentinian > one? On our website, the Argentinian one seems to be affiliated with > NCSG/NCUC, with Franco as its rep, but, digging for more info, Carlos > Aguirre seems to be the official rep of the international part. Sorry if > I'm not being precise, it is a bit hard to find clear and recent info about > it through search tools. > > > > All I was able to find was their FB page and ALAC profile. There I saw > Juan Manuel Rojas was a Rep. > > > > Is your doubt about their structure and actual jurisdiction of > registration? > > > > Regards, > > Jean > > > > > > Cordially, > > > *Pedro de Perdig?o Lana* > > Lawyer [nic.br] > , > GEDAI/UFPR [gedai.com.br] > > Researcher > > PhD Candidate (UFPR), LLM in Business Law (UCoimbra) > > Board Member @ NCUC (ICANN) [ncuc.org] > , > ISOC BR [isoc.org.br] > > , CC Brasil [br.creativecommons.net] > > and IODA [ioda.org.br] > > > This message is restricted to the sender and recipient(s). If received by > mistake, please reply informing it. > > > > > > Em dom., 14 de jul. de 2024 ?s 00:26, Jean F. Qu?ralt via NCSG-EC < > ncsg-ec at lists.ncsg.is> escreveu: > > Hi Caleb, > > > > Does this mean that membership requires specific proof of ownership to be > verified? > > > > How do you propose we do that? > > I haven't seen a mention to this on the existing documentation. > > > > Personally, I don't see a problem with having a domain parked (which in > this case is because they reacquired it hours ago). > > > > As mentioned in my previous message, NPOC's charter requires ownership. It > says nothing about usage. > > > > There are plenty of reasons why an organization may not be actively using > their domain. Sometimes they don't even want to have a website and just > want to protect themselves against impersonation. I've met orgs like that. > > > > If we are going down the rabbit hole of actively verifying ownership, > given the current Lookup/RDRS status, we have a few options that we then > need to document properly. > > > > Option 1) > > We give some custom code that needs to be injected into the Public Info so > that it can be found through > > https://lookup.icann.org/en/lookup [lookup.icann.org] > > > > > Option 2) > > We give some custom code that needs to be injected in a TXT record that we > then query > > > > Option 3) > > We give some custom code that needs to be injected in a text file on the > root of their https server so we can query it (https://domain/NPOC-Code.txt > [domain] > > ) > > > > There may be other options. These already cost more work for the EC. > > > > The situation now is we need to decide what's our procedure or we'll get > stuck here. > > > > Jean > > > > > > On Sun, Jul 14, 2024, 06:39 Caleb Olumuyiwa Ogundele < > muyiwacaleb at gmail.com> wrote: > > Hi Everyone, > > > > I did a little more digging. I will be declining my support for AGEIA > DENSI. > > The domain Jean mentioned is parked and until when it is active, we can't > seem to find out. Ideally, I would grant this but given as with the usual > procedure, more information is requested. > > > > Regards > > > > On Sat, Jul 13, 2024 at 2:13?PM Jean F. Qu?ralt via NCSG-EC < > ncsg-ec at lists.ncsg.is> wrote: > > Hi all, > > > > I've been informed that the organization has reacquired their domain (http://www.ageia.org/ > [ageia.org] > > ) > > The website is not up although that should not be a consideration for us. > > > > For all I am concerned, I give my thumbs up for when/if AGEIA DENSI > requests to join NPOC without having to undergo a new membership > application. > > > > Best, > > Jean F. Queralt > > Founder & CEO - The IO Foundation [theiofoundation.org] > > > Book a meeting [tiof.click] > > (30 minutes) > > > > > > On Sun, 14 Jul 2024 at 01:20, Jean F. Qu?ralt < > JFQueralt at theiofoundation.org> wrote: > > Hi all, > > > > I have confirmed that there is a procedural impasse that needs to be > addressed before we register AGEIA DENSI as a member to NPOC. > > > > 1) First of all, it is to be noted that, as @Andrea Glandon > has mentioned, I have not found reference/info > on this type of procedure. It would appear we are playing it by ear, which > is fine to a degree. > > I'd nonetheless recommend that moving forward we take the opportunity to > write this case scenario somewhere. I can work on the language and submit a > proposal. > > > > 2) The applicant, AGEIA DENSI, is not in a position at this very moment, > to comply with one of the requirements to be a member of NPOC. > > As per NPOC Charter: > > 2. Membership > c. Requirements > 3.Is a registrant of a domain name. > > > > Currently, the organization does not own their previous domain anymore > (and it would appear that no other domain either). > > After reaching out to the org's rep, I am confirmed this is a situation > they are actively looking to resolve. > > Once that's done, I'll be OK with them joining. Meanwhile, I rather apply > procedure and put the topic on standby. > > > > Also, @Andrea Glandon can you clarify if they > have > > a) Requested information about whether is it possible > > b) Formally requested to join NPOC > > Thanks. > > > > Regards, > > Jean F. Queralt > > Founder & CEO - The IO Foundation [theiofoundation.org] > > > Book a meeting [tiof.click] > > (30 minutes) > > > > > > On Sat, 13 Jul 2024 at 01:45, Andrea Glandon via NCSG-EC < > ncsg-ec at lists.ncsg.is> wrote: > > Hello NCSG EC, > > > > The organization Ageia Densi is already an approved NCSG and NCUC member. > They would like to add NPOC to their membership. I have looked at the > charter and do not see anything specific regarding this situation. How > should this situation be handled? Do they have to go through the regular > application process? > > > > Thanks! > > *Andrea Glandon* > > Policy Operations Sr. Coordinator > > Internet Corporation for Assigned Names and Numbers (ICANN) > > *Skype ID:* acglandon76 > > > > > > > > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec [lists.ncsg.is] > > > > > *DISCLAIMER* > > *The content of this message, which may contain personal or sensitive > data, is confidential. If you have received it by mistake, please inform > the sender by replying to the email and then permanently delete the > message, including any attachments. It is forbidden to copy, forward or in > any way reveal the content of this message to anyone. The integrity and > security of this email cannot be guaranteed over the Internet and, > therefore, the sender will not be held liable for any damage caused by the > message.* > > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec [lists.ncsg.is] > > > > > > -- > > *Caleb Ogundele* > > Email: muyiwacaleb at gmail.com > > > > *DISCLAIMER* > > *The content of this message, which may contain personal or sensitive > data, is confidential. If you have received it by mistake, please inform > the sender by replying to the email and then permanently delete the > message, including any attachments. It is forbidden to copy, forward or in > any way reveal the content of this message to anyone. The integrity and > security of this email cannot be guaranteed over the Internet and, > therefore, the sender will not be held liable for any damage caused by the > message.* > > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec [lists.ncsg.is] > > > > > *DISCLAIMER* > > *The content of this message, which may contain personal or sensitive > data, is confidential. If you have received it by mistake, please inform > the sender by replying to the email and then permanently delete the > message, including any attachments. It is forbidden to copy, forward or in > any way reveal the content of this message to anyone. The integrity and > security of this email cannot be guaranteed over the Internet and, > therefore, the sender will not be held liable for any damage caused by the > message.* > > > > *DISCLAIMER* > > *The content of this message, which may contain personal or sensitive > data, is confidential. If you have received it by mistake, please inform > the sender by replying to the email and then permanently delete the > message, including any attachments. It is forbidden to copy, forward or in > any way reveal the content of this message to anyone. The integrity and > security of this email cannot be guaranteed over the Internet and, > therefore, the sender will not be held liable for any damage caused by the > message.* > -- **DISCLAIMER** *The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrea.glandon at icann.org Mon Jul 15 19:02:11 2024 From: andrea.glandon at icann.org (Andrea Glandon) Date: Mon, 15 Jul 2024 16:02:11 +0000 Subject: [NCSG-EC] [Ext] Re: Ageia Densi (Argentina) In-Reply-To: References: Message-ID: In Civi, the group is listed as Ageia Densi (Argentina). Juan told me someone reached out to him whose group is already a member of NCSG and NCUC. Thanks! Kind Regards, Andrea From: "Jean F. Qu?ralt" Date: Monday, July 15, 2024 at 10:58 To: Andrea Glandon Cc: Pedro de Perdig?o Lana , Caleb Olumuyiwa Ogundele , NCSG EC Subject: Re: [Ext] Re: [NCSG-EC] Ageia Densi (Argentina) Hi. Thx for the info @Andrea Glandon! Can anyone confirm which ANGEIA DENSI is the one currently registered? I don't have access to the CRM and I can't confirm it is the same organization that is registered in NCUC. (I should assume it is yet a verification is due.) My position is that even if a number of organizations are from the same network and share name by existing in different jurisdictions should request membership separately. Again, nothing specific in this scenario that I can find. Regards, Jean F. Queralt Founder & CEO - The IO Foundation [theiofoundation.org] Book a meeting [tiof.click] (30 minutes) On Mon, 15 Jul 2024 at 19:51, Andrea Glandon > wrote: Hello all, This request came to me from Juan Manuel. Someone reached out to him. I do not have any further information. I told Juan I would find out what the procedure is to add them. Kind Regards, Andrea From: "Jean F. Qu?ralt" > Date: Sunday, July 14, 2024 at 10:59 To: Pedro de Perdig?o Lana >, Andrea Glandon > Cc: Caleb Olumuyiwa Ogundele >, NCSG EC > Subject: [Ext] Re: [NCSG-EC] Ageia Densi (Argentina) Yes, that makes a lot of sense. I don't have access to the CRM. @Andrea Glandon could you give is some extra information on the source of the inquiry/request? Thx. Regards, Jean On Sun, Jul 14, 2024, 23:49 Pedro de Perdig?o Lana > wrote: Thanks for your answers, Jean! My doubt was actually if it was the same organization (that is already part of NCUC/NCSG) asking to be a part of NPOC. I'm saying this because in LACRALO there are two different ALS, Ageia Densi Argentina and Ageia Densi Brazil, while you can find other manifestations that seem to refer to Ageia Densi as an international org with Argentia as its headquarters. In his LinkedIn, Juan appears to be the president of "Ageia Densi Colombia", which is a third organization (and that I couldn't find before in the ALAC ALS search because it is listed as MINKA Colombia - https://atlarge.icann.org/alses/lacralo [atlarge.icann.org], which was the name I remember him being affiliated to a few months ago). I think we need to better understand if there is a difference with the person who requested the affiliation. Cordially, Pedro de Perdig?o Lana Advogado - OAB/PR 90.600 [nic.br], Pesquisador (GEDAI/UFPR [gedai.com.br]) Doutorando em Direito (UFPR), Mestre em Direito Empresarial (UCoimbra), Membro da Coordena??o - NCUC (ICANN) [ncuc.org], ISOC BR [isoc.org.br], IODA [ioda.org.br] e CC Brasil [br.creativecommons.net]. Essa mensagem ? restrita ao remetente e destinat?rio(s). Se recebida por engano, favor responder informando o erro. Em dom., 14 de jul. de 2024 ?s 12:29, Jean F. Qu?ralt > escreveu: Hi Pedro. Is the Charter marked by upcoming in the wiki already in effect? If not, the previous/current chart seems to have a higher bar: "5.1.1.6 Own at least one domain name and maintain or have plans to create an organization website". It is my understanding that the current applicable charter is the one I referenced as the new positions in the last election were those described in it. I admit I'm fuzzy about that as the transition never was fully clear to me. Probably Andrea and Daniel can shed light on this. On the other hand, "plans to create an organization website" is definitely a qualitative concept that can't be measured and open to interpretation at an operational level. I'm more comfortable with just the ownership (of which we need to establish a procedure for verification as I mentioned) so I hope that's not applicable anymore because it would be pretty much an admin nightmare. Another question: within NCSG, Ageia Densi is an international organization (encompassing Ageia Densi Brazil as well) or an Argentinian one? On our website, the Argentinian one seems to be affiliated with NCSG/NCUC, with Franco as its rep, but, digging for more info, Carlos Aguirre seems to be the official rep of the international part. Sorry if I'm not being precise, it is a bit hard to find clear and recent info about it through search tools. All I was able to find was their FB page and ALAC profile. There I saw Juan Manuel Rojas was a Rep. Is your doubt about their structure and actual jurisdiction of registration? Regards, Jean Cordially, Pedro de Perdig?o Lana Lawyer [nic.br], GEDAI/UFPR [gedai.com.br] Researcher PhD Candidate (UFPR), LLM in Business Law (UCoimbra) Board Member @ NCUC (ICANN) [ncuc.org], ISOC BR [isoc.org.br], CC Brasil [br.creativecommons.net] and IODA [ioda.org.br] This message is restricted to the sender and recipient(s). If received by mistake, please reply informing it. Em dom., 14 de jul. de 2024 ?s 00:26, Jean F. Qu?ralt via NCSG-EC > escreveu: Hi Caleb, Does this mean that membership requires specific proof of ownership to be verified? How do you propose we do that? I haven't seen a mention to this on the existing documentation. Personally, I don't see a problem with having a domain parked (which in this case is because they reacquired it hours ago). As mentioned in my previous message, NPOC's charter requires ownership. It says nothing about usage. There are plenty of reasons why an organization may not be actively using their domain. Sometimes they don't even want to have a website and just want to protect themselves against impersonation. I've met orgs like that. If we are going down the rabbit hole of actively verifying ownership, given the current Lookup/RDRS status, we have a few options that we then need to document properly. Option 1) We give some custom code that needs to be injected into the Public Info so that it can be found through https://lookup.icann.org/en/lookup [lookup.icann.org] Option 2) We give some custom code that needs to be injected in a TXT record that we then query Option 3) We give some custom code that needs to be injected in a text file on the root of their https server so we can query it (https://domain/NPOC-Code.txt [domain]) There may be other options. These already cost more work for the EC. The situation now is we need to decide what's our procedure or we'll get stuck here. Jean On Sun, Jul 14, 2024, 06:39 Caleb Olumuyiwa Ogundele > wrote: Hi Everyone, I did a little more digging. I will be declining my support for AGEIA DENSI. The domain Jean mentioned is parked and until when it is active, we can't seem to find out. Ideally, I would grant this but given as with the usual procedure, more information is requested. Regards On Sat, Jul 13, 2024 at 2:13?PM Jean F. Qu?ralt via NCSG-EC > wrote: Hi all, I've been informed that the organization has reacquired their domain (http://www.ageia.org/ [ageia.org]) The website is not up although that should not be a consideration for us. For all I am concerned, I give my thumbs up for when/if AGEIA DENSI requests to join NPOC without having to undergo a new membership application. Best, Jean F. Queralt Founder & CEO - The IO Foundation [theiofoundation.org] Book a meeting [tiof.click] (30 minutes) On Sun, 14 Jul 2024 at 01:20, Jean F. Qu?ralt > wrote: Hi all, I have confirmed that there is a procedural impasse that needs to be addressed before we register AGEIA DENSI as a member to NPOC. 1) First of all, it is to be noted that, as @Andrea Glandon has mentioned, I have not found reference/info on this type of procedure. It would appear we are playing it by ear, which is fine to a degree. I'd nonetheless recommend that moving forward we take the opportunity to write this case scenario somewhere. I can work on the language and submit a proposal. 2) The applicant, AGEIA DENSI, is not in a position at this very moment, to comply with one of the requirements to be a member of NPOC. As per NPOC Charter: 2. Membership > c. Requirements > 3.Is a registrant of a domain name. Currently, the organization does not own their previous domain anymore (and it would appear that no other domain either). After reaching out to the org's rep, I am confirmed this is a situation they are actively looking to resolve. Once that's done, I'll be OK with them joining. Meanwhile, I rather apply procedure and put the topic on standby. Also, @Andrea Glandon can you clarify if they have a) Requested information about whether is it possible b) Formally requested to join NPOC Thanks. Regards, Jean F. Queralt Founder & CEO - The IO Foundation [theiofoundation.org] Book a meeting [tiof.click] (30 minutes) On Sat, 13 Jul 2024 at 01:45, Andrea Glandon via NCSG-EC > wrote: Hello NCSG EC, The organization Ageia Densi is already an approved NCSG and NCUC member. They would like to add NPOC to their membership. I have looked at the charter and do not see anything specific regarding this situation. How should this situation be handled? Do they have to go through the regular application process? Thanks! Andrea Glandon Policy Operations Sr. Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: acglandon76 _______________________________________________ NCSG-EC mailing list NCSG-EC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-ec [lists.ncsg.is] DISCLAIMER The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message. _______________________________________________ NCSG-EC mailing list NCSG-EC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-ec [lists.ncsg.is] -- Caleb Ogundele Email: muyiwacaleb at gmail.com DISCLAIMER The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message. _______________________________________________ NCSG-EC mailing list NCSG-EC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-ec [lists.ncsg.is] DISCLAIMER The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message. DISCLAIMER The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message. DISCLAIMER The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message. -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Tue Jul 16 10:01:33 2024 From: julf at Julf.com (Johan Helsingius) Date: Tue, 16 Jul 2024 09:01:33 +0200 Subject: [NCSG-EC] Fwd: [Ext] RE: RE: NomCom changes In-Reply-To: <1B62C7DF-3637-4571-BDEA-45A774F459AE@icann.org> References: <1B62C7DF-3637-4571-BDEA-45A774F459AE@icann.org> Message-ID: <6d49113b-c0f3-4c8d-8ba0-bd79f6946cc4@Julf.com> -------- Forwarded Message -------- Subject: Re: [Ext] RE: RE: NomCom changes Date: Mon, 15 Jul 2024 20:15:54 +0000 From: Steve Chan To: DiBiase, Gregory , Demetriou, Samantha , aheineman at godaddy.com , lschulman at inta.org , MCole at perkinscoie.com , julf at Julf.com , philippe.fouquart at orange.com CC: GNSO-Secs , gnso-chairs at icann.org Hi All, We (Greg, Tomslin, Mason as well as Devan and me from staff) just completed the randomization process. If you?re curious to see how the selection process was conducted, you can review the _very_ brief call (a grand total of 6 minutes!) here: https://icann.zoom.us/rec/play/BJtII0xE98UCeVrzOvAPTkX1RLnvsoqvbiQGXx5luCztNEFTbsUH5q7FDHXn93zNdlFfLi3QrSwcozZw.FcicxlWXnIiUrE8-?autoplay=true&startTime=1721073677000 The three groups that will have the 1-year terms are: * Internet Service Providers and Connectivity Providers * Non-Commercial Users Constituency * Business Constituency We will provide our ICANN org colleagues with the results. If you have any questions or concerns, please let us know. Best, Steve *From: *"DiBiase, Gregory" *Date: *Wednesday, July 10, 2024 at 9:26 AM *To: *"Demetriou, Samantha" , "aheineman at godaddy.com" , "lschulman at inta.org" , "MCole at perkinscoie.com" , "julf at Julf.com" , "philippe.fouquart at orange.com" *Cc: *Steve Chan , GNSO-Secs , "gnso-chairs at icann.org" *Subject: *[Ext] RE: RE: NomCom changes Hi All, Thank you for your patience while we worked out this process. I?ve received feedback from all of you that the proposed process is acceptable and we will proceed with randomly selecting three of seven GNSO delegates to serve one-year terms. One additional parameter arose in these conversations: there can only be: ?????? - no more than one delegate assigned the 1-yr term from the CPH ?????? - no more than one delegate assigned the 1-yr term from the BC The next step is to run the randomization exercise. Steve, myself, and the GNSO Secretariat will perform the randomization on a recorded Zoom call on Monday. If any of you would like to attend, please let me know and I will send an invite. Please let me know if you have any concerns with this approach. Thanks, Greg *From: *"DiBiase, Gregory" > *Date: *Friday, May 31, 2024 at 12:02 PM *To: *"aheineman at godaddy.com " >, Lori Schulman >, "Cole, Mason (POR)" >, Johan Helsingius >, Samantha Demetriou >, "philippe.fouquart at orange.com " > *Cc: *Steve Chan >, "gnso-secs at icann.org " > *Subject: *[EXTERNAL] RE: NomCom changes *Caution:*This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi All- fixing small typo below.? Feedback is requested by Council leadership no later than 5 June 2024 (not 31 May). *From:* DiBiase, Gregory *Sent:* Friday, May 31, 2024 7:41 AM *To:* aheineman at godaddy.com ; 'Lori Schulman' >; 'Cole, Mason (POR)' >; 'Johan Helsingius' >; 'sdemetriou at verisign.com' >; 'philippe.fouquart at orange.com' > *Cc:* Steve Chan >; gnso-secs at icann.org *Subject:* NomCom changes 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 From julf at Julf.com Tue Jul 16 11:29:01 2024 From: julf at Julf.com (Johan Helsingius) Date: Tue, 16 Jul 2024 10:29:01 +0200 Subject: [NCSG-EC] Fwd: GNSO Chair/Vice Chair Selections In-Reply-To: References: Message-ID: I assume we too are OK with Greg and Tomslin continuing? Julf -------- Forwarded Message -------- Subject: GNSO Chair/Vice Chair Selections Date: Mon, 15 Jul 2024 23:34:14 +0000 From: Lori Schulman To: csg-excomm at ICANN.org , julf at julf.com , Johan Helsingius , Rafik Dammak CC: Tomslin Samme-Nlar , DiBiase, Gregory Dear Julf, The CSG ExCom met to discuss our approach to the upcoming Chair and Vice Chair elections.? ?As both Greg DiBiase and Tomslin Samme-Nlar are doing an excellent job, we are pleased to support both for re-election should they chose to stand again.? We agree that the consistency in leadership will be helpful to the functioning of the GNSO during this time of transition at ICANN.? It also has the added benefit of allowing NCPH to keep our work focused on the outcomes of the Team 14 discussions. Please contact me if you have any questions about our position or wish further discussion. With kind regards, __ Lori Schulman Senior Director, Internet Policy *International Trademark Association* LSchulman at inta.org inta.org ***|***Locations ***|***Social Media From JFQueralt at theiofoundation.org Tue Jul 16 11:31:38 2024 From: JFQueralt at theiofoundation.org (=?UTF-8?Q?Jean_F=2E_Qu=C3=A9ralt?=) Date: Tue, 16 Jul 2024 16:31:38 +0800 Subject: [NCSG-EC] Fwd: GNSO Chair/Vice Chair Selections In-Reply-To: References: Message-ID: I am too new to have an opinion one way or another. I believe the reasonable position for me at this stage is to abstain. Best, Jean F. Queralt Founder & CEO - The IO Foundation Book a meeting (30 minutes) On Tue, 16 Jul 2024 at 16:29, Johan Helsingius via NCSG-EC < ncsg-ec at lists.ncsg.is> wrote: > I assume we too are OK with Greg and Tomslin continuing? > > Julf > > > > -------- Forwarded Message -------- > Subject: GNSO Chair/Vice Chair Selections > Date: Mon, 15 Jul 2024 23:34:14 +0000 > From: Lori Schulman > To: csg-excomm at ICANN.org , julf at julf.com > , Johan Helsingius , Rafik > Dammak > CC: Tomslin Samme-Nlar , DiBiase, Gregory > > > > > Dear Julf, > > The CSG ExCom met to discuss our approach to the upcoming Chair and Vice > Chair elections. As both Greg DiBiase and Tomslin Samme-Nlar are doing > an excellent job, we are pleased to support both for re-election should > they chose to stand again. We agree that the consistency in leadership > will be helpful to the functioning of the GNSO during this time of > transition at ICANN. It also has the added benefit of allowing NCPH to > keep our work focused on the outcomes of the Team 14 discussions. > > Please contact me if you have any questions about our position or wish > further discussion. > > With kind regards, > > __ > > > > Lori Schulman > > Senior Director, Internet Policy > > *International Trademark Association* > > LSchulman at inta.org > > inta.org ***|***Locations > ***|***Social Media > > > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -- **DISCLAIMER** *The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Tue Jul 16 12:34:10 2024 From: julf at Julf.com (Johan Helsingius) Date: Tue, 16 Jul 2024 11:34:10 +0200 Subject: [NCSG-EC] Fwd: GNSO Chair/Vice Chair Selections In-Reply-To: References: Message-ID: Reasonable position - but it is really a PC call anyway. Julf On 16/07/2024 10:31, Jean F. Qu?ralt wrote: > > I am too new to have an opinion one way or another. I believe the > reasonable position for me at this stage is to abstain. > > Best, > Jean F. Queralt > Founder & CEO - The IO Foundation > Book a meeting (30 minutes) > > > On Tue, 16 Jul 2024 at 16:29, Johan Helsingius via NCSG-EC > > wrote: > > I assume we too are OK with Greg and Tomslin continuing? > > ? ? ? ? Julf > > > > -------- Forwarded Message -------- > Subject:? ? ? ? GNSO Chair/Vice Chair Selections > Date:? ?Mon, 15 Jul 2024 23:34:14 +0000 > From:? ?Lori Schulman > > To:? ? ?csg-excomm at ICANN.org >, julf at julf.com > , Johan Helsingius >, Rafik > Dammak > > CC:? ? ?Tomslin Samme-Nlar >, DiBiase, Gregory > > > > > > Dear Julf, > > The CSG ExCom met to discuss our approach to the upcoming Chair and > Vice > Chair elections.? ?As both Greg DiBiase and Tomslin Samme-Nlar are > doing > an excellent job, we are pleased to support both for re-election should > they chose to stand again.? We agree that the consistency in leadership > will be helpful to the functioning of the GNSO during this time of > transition at ICANN.? It also has the added benefit of allowing NCPH to > keep our work focused on the outcomes of the Team 14 discussions. > > Please contact me if you have any questions about our position or wish > further discussion. > > With kind regards, > > __ > > > > > Lori Schulman > > Senior Director, Internet Policy > > *International Trademark Association* > > LSchulman at inta.org > ?subject=Hello> > > inta.org >***|***Locations > >***|***Social Media > > > > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > > > > /*DISCLAIMER*/ > /The content of this message, which may contain personal or sensitive > data, is confidential. If you have received it by mistake, please inform > the sender by replying to the email and then permanently delete the > message, including any attachments. It is forbidden to copy, forward or > in any way reveal the content of this message to anyone. The integrity > and security of this email cannot be guaranteed over the Internet and, > therefore, the sender will not be held liable for any damage caused by > the message./ From wisdom.dk at gmail.com Tue Jul 16 13:30:00 2024 From: wisdom.dk at gmail.com (Wisdom Donkor) Date: Tue, 16 Jul 2024 12:30:00 +0200 Subject: [NCSG-EC] [NCSG-PC] Fwd: GNSO Chair/Vice Chair Selections In-Reply-To: References: Message-ID: I am very ok On Tue, 16 Jul 2024, 10:29?am Johan Helsingius via NCSG-PC, < ncsg-pc at lists.ncsg.is> wrote: > I assume we too are OK with Greg and Tomslin continuing? > > Julf > > > > -------- Forwarded Message -------- > Subject: GNSO Chair/Vice Chair Selections > Date: Mon, 15 Jul 2024 23:34:14 +0000 > From: Lori Schulman > To: csg-excomm at ICANN.org , julf at julf.com > , Johan Helsingius , Rafik > Dammak > CC: Tomslin Samme-Nlar , DiBiase, Gregory > > > > > Dear Julf, > > The CSG ExCom met to discuss our approach to the upcoming Chair and Vice > Chair elections. As both Greg DiBiase and Tomslin Samme-Nlar are doing > an excellent job, we are pleased to support both for re-election should > they chose to stand again. We agree that the consistency in leadership > will be helpful to the functioning of the GNSO during this time of > transition at ICANN. It also has the added benefit of allowing NCPH to > keep our work focused on the outcomes of the Team 14 discussions. > > Please contact me if you have any questions about our position or wish > further discussion. > > With kind regards, > > __ > > > > Lori Schulman > > Senior Director, Internet Policy > > *International Trademark Association* > > LSchulman at inta.org > > inta.org ***|***Locations > ***|***Social Media > > > _______________________________________________ > 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: From stephanie.perrin at mail.utoronto.ca Tue Jul 16 15:31:00 2024 From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin) Date: Tue, 16 Jul 2024 12:31:00 +0000 Subject: [NCSG-EC] [NCSG-PC] Fwd: GNSO Chair/Vice Chair Selections In-Reply-To: References: Message-ID: Seems good to me Stephanie Sent from my iPhone > On Jul 16, 2024, at 05:34, Johan Helsingius via NCSG-PC wrote: > > ?Reasonable position - but it is really a PC call anyway. > > Julf > > >> On 16/07/2024 10:31, Jean F. Qu?ralt wrote: >> I am too new to have an opinion one way or another. I believe the reasonable position for me at this stage is to abstain. >> Best, >> Jean F. Queralt >> Founder & CEO - The IO Foundation >> Book a meeting (30 minutes) >> On Tue, 16 Jul 2024 at 16:29, Johan Helsingius via NCSG-EC > wrote: >> I assume we too are OK with Greg and Tomslin continuing? >> Julf >> -------- Forwarded Message -------- >> Subject: GNSO Chair/Vice Chair Selections >> Date: Mon, 15 Jul 2024 23:34:14 +0000 >> From: Lori Schulman > >> To: csg-excomm at ICANN.org > >, julf at julf.com >> , Johan Helsingius > >, Rafik >> Dammak > >> CC: Tomslin Samme-Nlar > >, DiBiase, Gregory >> > >> Dear Julf, >> The CSG ExCom met to discuss our approach to the upcoming Chair and >> Vice >> Chair elections. As both Greg DiBiase and Tomslin Samme-Nlar are >> doing >> an excellent job, we are pleased to support both for re-election should >> they chose to stand again. We agree that the consistency in leadership >> will be helpful to the functioning of the GNSO during this time of >> transition at ICANN. It also has the added benefit of allowing NCPH to >> keep our work focused on the outcomes of the Team 14 discussions. >> Please contact me if you have any questions about our position or wish >> further discussion. >> With kind regards, >> __ > >> Lori Schulman >> Senior Director, Internet Policy >> *International Trademark Association* >> LSchulman at inta.org >> ?subject=Hello> >> inta.org > >***|***Locations >> > >***|***Social Media >> > > >> _______________________________________________ >> NCSG-EC mailing list >> NCSG-EC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >> >> /*DISCLAIMER*/ >> /The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message./ > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc From pedrodeperdigaolana at gmail.com Wed Jul 17 05:46:20 2024 From: pedrodeperdigaolana at gmail.com (=?UTF-8?Q?Pedro_de_Perdig=C3=A3o_Lana?=) Date: Tue, 16 Jul 2024 23:46:20 -0300 Subject: [NCSG-EC] Fwd: [SOAC-Leaders-ICANNMeeting-Planning] Re: [Ext] Re: Re: ICANN81 Block Schedule, Production Timeline In-Reply-To: References: <9A8E9154-58C5-4F60-8674-D6DEDB1B8B70@icann.org> Message-ID: Hi Julf, EC, PC, Is there any topic of particular importance to NCSG work right now, maybe related to the Next Round, that would be interesting to propose to the community session? One thing that wouldn't be a repetition of previous sessions and which is recurrently appearing in NCSG comments would be how accessible the New gTLD Program is (i.e. readability of materials), considering the Program's declared objective of diversifying the market. I can't see right now, however, how this could be transformed into a topic interesting enough to become a community session. Cordially, *Pedro de Perdig?o Lana* Lawyer , GEDAI/UFPR Researcher PhD Candidate (UFPR), LLM in Business Law (UCoimbra) Board Member @ NCUC (ICANN) , ISOC BR , CC Brasil and IODA This message is restricted to the sender and recipient(s). If received by mistake, please reply informing it. Em sex., 12 de jul. de 2024 ?s 07:41, Johan Helsingius via NCSG-EC < ncsg-ec at lists.ncsg.is> escreveu: > > > > -------- Forwarded Message -------- > Subject: [SOAC-Leaders-ICANNMeeting-Planning] Re: [Ext] Re: Re: > ICANN81 > Block Schedule, Production Timeline > Date: Thu, 11 Jul 2024 14:56:57 +0000 > From: Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning > > Reply-To: Nathalie Peregrine > To: soac-leaders-icannmeeting-planning at icann.org > > > > > Hello all! > > I hope you are doing well! > > A friendly reminder to please consider the action items below, and > should topics for the ICANN81 Community Session be raised within your > groups, to please share on this list for discussion. The deadline for > topic submission on the list is 19 July 2024. > > Thank you all! > > Kind regards, > > Nathalie > > *From: *Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning > > *Reply to: *Nathalie Peregrine > *Date: *Monday, 1 July 2024 at 10:20 > *To: *"soac-leaders-icannmeeting-planning at icann.org" > > *Subject: *[SOAC-Leaders-ICANNMeeting-Planning] Re: [Ext] Re: Re: > ICANN81 Block Schedule, Production Timeline > > Dear all, > > Thank you so much for joining the ICANN81 Kick off call! The input > shared, be it feedback for ICANN80 and advice regarding the ICANN81 > Block Schedule was extremely helpful! > > Please find the Zoom chat text and slide deck from the call attached to > this email. The Zoom recording can be accessed here > < > https://urldefense.com/v3/__https:/icann.zoom.us/rec/share/8HiDU7bcC13tsDFgOgtPSh2YTj7xqe9kDfacMoEjpeQKh-fh7ophCuEmFyX6JeVE.BlDlBj8WRpmjCG9V__;!!PtGJab4!6MPup5812nXaAULfm-kZwfPE-BCPuPpQdMkq9ISKsQwhCeKhXSr953lge41PsKnaFgNkCLtx6h1PjbbVNzsnwCfSP4g$>. > > > > Regarding the block schedule, please also find the latest version > attached with the following change: > > * Monday?s Q&A with ICANN Org?s Executive Team removed, and replaced > by the Geopolitical Forum initially scheduled on Tuesday. > > Thank you to Alejandra for her input on the Community Session topic > deadline! The previous deadline of the 12^th July 2024 can be extended > to the 19^th July 2024. However, it would be interesting to hear from > community leaders on the matter before then via the mailing list. Please > do bear in mind, that there is no obligation for this Community Session > to take place, should there be no clear topic community groups agree > upon, the session can be postponed until ICANN82. > > *Action Items for all:* > > * Kindly express any objection to the current block schedule as > speedily as possible. > * Please review the joint Board & SO/AC slots and raise concerns > should there be any > * Begin conversations about the Community Session topic and the need > for such a session to be held at ICANN81 > > Thank you to all and have a lovely week! > > Kind regards, > > Nathalie > > *From: *Alejandra Reynoso Barral > *Date: *Friday, 28 June 2024 at 13:04 > *To: *Nathalie Peregrine > *Cc: *"soac-leaders-icannmeeting-planning at icann.org" > > *Subject: *[Ext] Re: [SOAC-Leaders-ICANNMeeting-Planning] Re: ICANN81 > Block Schedule, Production Timeline > > Dear Nathalie and All > > It was good to see/hear you at the kickoff call. > > I understand the eagerness to finalize the block schedule as soon as > possible, but the current 12th of July deadline to submit a community > session topic is a bit tight. > > The ccNSO council will meet on the 18th of July and, depending on the > outcome of the discussion of this item, we may or may not want to submit > something. > > Can the deadline be extended? > > Best regards, > > Alejandra > > > ******************************************* > Work like you don't need the money. > Love like you've never been hurt. > Dance like nobody's watching. > Sing like nobody's listening. > And live like it's Heaven on Earth. > ******************************************* > > On Wed, Jun 26, 2024 at 10:13?AM Nathalie Peregrine via > SOAC-Leaders-ICANNMeeting-Planning > > wrote: > > 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 > > *Date: *Wednesday, 22 May 2024 at 22:13 > *To: *"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 > > _______________________________________________ > SOAC-Leaders-ICANNMeeting-Planning mailing list -- > soac-leaders-icannmeeting-planning at icann.org > > To unsubscribe send an email to > soac-leaders-icannmeeting-planning-leave at icann.org > > > _______________________________________________ > By submitting your personal data, you consent to the processing of > your personal data for purposes of subscribing to this mailing list > accordance with the ICANN Privacy Policy > (https://www.icann.org/privacy/policy > ) and the website Terms of > Service (https://www.icann.org/privacy/tos > ). You can visit the Mailman link > above to change your membership status or configuration, including > unsubscribing, setting digest-style delivery or disabling delivery > altogether (e.g., for a vacation), and so on. > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pedrodeperdigaolana at gmail.com Wed Jul 17 05:58:44 2024 From: pedrodeperdigaolana at gmail.com (=?UTF-8?Q?Pedro_de_Perdig=C3=A3o_Lana?=) Date: Tue, 16 Jul 2024 23:58:44 -0300 Subject: [NCSG-EC] WS2 Implementation Progress In-Reply-To: <2B83D63F-EAB6-47E8-83BD-C16D48D719C5@icann.org> References: <2B83D63F-EAB6-47E8-83BD-C16D48D719C5@icann.org> Message-ID: Hi everyone, Just for some background/context, when was the last update to this sheet made? Who was there, from the current EC, that could point out to us what was discussed then about the assessment of current procedures and future plans? Cordially, *Pedro de Perdig?o Lana* Lawyer , GEDAI/UFPR Researcher PhD Candidate (UFPR), LLM in Business Law (UCoimbra) Board Member @ NCUC (ICANN) , ISOC BR , CC Brasil and IODA This message is restricted to the sender and recipient(s). If received by mistake, please reply informing it. Em sex., 12 de jul. de 2024 ?s 10:41, Andrea Glandon via NCSG-EC < ncsg-ec at lists.ncsg.is> escreveu: > Hello NCSG EC, > > > > Please take a look at the WS2 Community Implementation spreadsheet. Can > you please update the implementation status of items that are not marked > Completed or Won?t Be Implemented? If still not implemented, can you please > provide a timeline for implementation? > > > > > https://docs.google.com/spreadsheets/d/1xxPZjIjrjLBiKjcgWKbhhxWhbsBdcRudCqRDl4W5UlY/edit?usp=sharing > > > > Thank you! > > *Andrea Glandon* > > Policy Operations Sr. Coordinator > > Internet Corporation for Assigned Names and Numbers (ICANN) > > *Skype ID:* acglandon76 > > > > > > > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -------------- next part -------------- An HTML attachment was scrubbed... URL: From farzaneh.badii at gmail.com Wed Jul 17 06:51:29 2024 From: farzaneh.badii at gmail.com (farzaneh badii) Date: Tue, 16 Jul 2024 23:51:29 -0400 Subject: [NCSG-EC] WS2 Implementation Progress In-Reply-To: References: <2B83D63F-EAB6-47E8-83BD-C16D48D719C5@icann.org> Message-ID: Ah I remember this from my early 30s. I was co-chairing the so/ac accountability as a part of ws2 on accountability. Later on as the NCSG chair we responded to the questionnaire with others. (2018) the recommendations are not binding in anyway but I think they are good practice and we should consider them. Unlike other groups we have many of them in place such as ?term limits?? Farzaneh On Tue, Jul 16, 2024 at 10:58?PM Pedro de Perdig?o Lana via NCSG-EC < ncsg-ec at lists.ncsg.is> wrote: > Hi everyone, > > Just for some background/context, when was the last update to this sheet > made? Who was there, from the current EC, that could point out to us what > was discussed then about the assessment of current procedures and future > plans? > > Cordially, > > *Pedro de Perdig?o Lana* > Lawyer , GEDAI/UFPR > Researcher > PhD Candidate (UFPR), LLM in Business Law (UCoimbra) > Board Member @ NCUC (ICANN) , ISOC BR > , CC Brasil and > IODA > This message is restricted to the sender and recipient(s). If received by > mistake, please reply informing it. > > > Em sex., 12 de jul. de 2024 ?s 10:41, Andrea Glandon via NCSG-EC < > ncsg-ec at lists.ncsg.is> escreveu: > >> Hello NCSG EC, >> >> >> >> Please take a look at the WS2 Community Implementation spreadsheet. Can >> you please update the implementation status of items that are not marked >> Completed or Won?t Be Implemented? If still not implemented, can you please >> provide a timeline for implementation? >> >> >> >> >> https://docs.google.com/spreadsheets/d/1xxPZjIjrjLBiKjcgWKbhhxWhbsBdcRudCqRDl4W5UlY/edit?usp=sharing >> >> >> >> Thank you! >> >> *Andrea Glandon* >> >> Policy Operations Sr. Coordinator >> >> Internet Corporation for Assigned Names and Numbers (ICANN) >> >> *Skype ID:* acglandon76 >> >> >> >> >> >> >> _______________________________________________ >> NCSG-EC mailing list >> NCSG-EC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >> > _______________________________________________ > 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: From julf at Julf.com Wed Jul 24 18:16:13 2024 From: julf at Julf.com (Johan Helsingius) Date: Wed, 24 Jul 2024 17:16:13 +0200 Subject: [NCSG-EC] Fwd: Initiating the Community Dialogue on "How We Meet": Initial Ideas & Meeting Request In-Reply-To: References: Message-ID: Interesting comments from ISPC. Julf -------- Forwarded Message -------- Subject: [GNSO-SG-C-Leadership] Re: [soac-chairs] Initiating the Community Dialogue on "How We Meet": Initial Ideas & Meeting Request Date: Wed, 24 Jul 2024 15:09:51 +0000 From: philippe.fouquart--- via GNSO-SG-C-Leadership Reply-To: philippe.fouquart at orange.com To: DiBiase, Gregory CC: gnso-chairs at icann.org , Novoa, Osvaldo via ISPCP-Leadership , gnso-sg-c-leadership at icann.org Hi Greg, Thanks for this opportunity of providing comments on the proposed approach to the Community Dialogue. You will find attached the ISPCP Constituency?s initial ideas. Happy to discuss. Regards, Philippe, on behalf of the ISPs and Connectivity Providers Constituency *From:* DiBiase, Gregory via council *Sent:* Monday, July 22, 2024 4:44 PM *To:* GNSO Council List ; gnso-sg-c-leadership at icann.org *Cc:* gnso-chairs at icann.org *Subject:* [council] Re: [soac-chairs] Initiating the Community Dialogue on "How We Meet": Initial Ideas & Meeting Request *CAUTION*: This email originated outside the company. Do not click on any links or open attachments unless you are expecting them from the sender. *ATTENTION*: Cet e-mail provient de l'ext?rieur de l'entreprise. Ne cliquez pas sur les liens ou n'ouvrez pas les pi?ces jointes ? moins de connaitre l'exp?diteur. Hi All- resending this email as a reminder.? Council Leadership is requesting feedback by 24 July. Thanks, Greg *From:*DiBiase, Gregory *Sent:* Tuesday, July 9, 2024 11:02 AM *To:* GNSO Council List >; 'gnso-sg-c-leadership at icann.org' > *Cc:* gnso-chairs at icann.org *Subject:* FW: [EXTERNAL] [soac-chairs] Initiating the Community Dialogue on "How We Meet": Initial Ideas & Meeting Request Dear Councilors and SG/C Leadership, We are forwarding the below message re: ?How We Meet? from ICANN staff. Please solicit input from your respective groups on the ideas articulated in the attached Community Discussion Paper. For the purposes of gathering feedback, GNSO Leadership is happy to collect and collate inputs from the SG/Cs in order to share it with the other SO/AC Chairs. Looking at ICANN?s proposed timeline below, please send any feedback to gnso-chairs at icann.org by 24 July. Let us know if you have concerns with this approach. Thanks, Greg on behalf of GNSO Leadership *From:*Mary Wong via soac-chairs > *Sent:* Sunday, July 7, 2024 11:58 PM *To:* soac-chairs at icann.org *Cc:* team-leaders at icann.org *Subject:* [EXTERNAL] [soac-chairs] Initiating the Community Dialogue on "How We Meet": Initial Ideas & Meeting Request *CAUTION*: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Dear SOAC leaders, An action item from your informal meeting with Sally in Kigali was for the Policy team to facilitate a dialogue with you about ?How We Meet?, viz., how our in-person and hybrid meetings can be optimized to ensure that resources (including financial, staff and community time) continue to be allocated appropriately to ensure the community can do its work effectively and efficiently, while staying within budgetary constraints. As a starting point for this dialogue, we have drafted the attached discussion paper with some initial ideas for your community?s consideration and to invite your suggestions for further discussion. To capitalize on the momentum of recent conversations and to facilitate a constructive and substantive dialogue, we?d like to suggest the following cadence of meetings, structured around a few foundational questions: * Late/end-July: first call with SOAC Chairs and Vice-Chairs to share feedback on agreed strategic questions * Mid/late August (following collation of ideas and input): second call to discuss and agree on concrete ideas for implementation or further exploration * End-August/early September (if agreed is needed): third call to review agreed way forward, including any next steps for additional (longer term) ideas to be discussed further The sort of strategic, foundational questions we were thinking might be helpful for focusing the dialogue include: o If you or your group could change one thing about how we meet that will facilitate efficiency in how we deliver ICANN?s mission while remaining sustainable into the future, what would that be? o What other key changes do we need to make to continue to ensure we can meet these goals? Thank you for your support and willingness to collaborate with us in seeking to improve and optimize how we meet. Assuming you are comfortable with the proposed approach, I?ll make sure to come back to you with some suggested dates for the calls. Please let me know if your group have any questions or would like any additional information that can assist with your internal discussions about this topic. Thank you! Cheers Mary ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- A non-text attachment was scrubbed... Name: How we meet - ISPCP comments v1.0.pdf Type: application/pdf Size: 177231 bytes Desc: not available URL: From JFQueralt at theiofoundation.org Wed Jul 24 21:30:17 2024 From: JFQueralt at theiofoundation.org (=?UTF-8?Q?Jean_F=2E_Qu=C3=A9ralt?=) Date: Thu, 25 Jul 2024 02:30:17 +0800 Subject: [NCSG-EC] Fwd: Initiating the Community Dialogue on "How We Meet": Initial Ideas & Meeting Request In-Reply-To: References: Message-ID: Should anyone want to follow up on some of their recommendations/comments, would NCSG respond directly or add them to its own comment document? Best, Jean F. Queralt Founder & CEO - The IO Foundation Book a meeting (30 minutes) On Wed, 24 Jul 2024 at 23:16, Johan Helsingius via NCSG-EC < ncsg-ec at lists.ncsg.is> wrote: > Interesting comments from ISPC. > > Julf > > > > -------- Forwarded Message -------- > Subject: [GNSO-SG-C-Leadership] Re: [soac-chairs] Initiating the > Community Dialogue on "How We Meet": Initial Ideas & Meeting Request > Date: Wed, 24 Jul 2024 15:09:51 +0000 > From: philippe.fouquart--- via GNSO-SG-C-Leadership > > Reply-To: philippe.fouquart at orange.com > To: DiBiase, Gregory > CC: gnso-chairs at icann.org , Novoa, Osvaldo via > ISPCP-Leadership , > gnso-sg-c-leadership at icann.org > > > > Hi Greg, > > Thanks for this opportunity of providing comments on the proposed > approach to the Community Dialogue. > > You will find attached the ISPCP Constituency?s initial ideas. > > Happy to discuss. > > Regards, > > Philippe, on behalf of the ISPs and Connectivity Providers Constituency > > *From:* DiBiase, Gregory via council > *Sent:* Monday, July 22, 2024 4:44 PM > *To:* GNSO Council List ; > gnso-sg-c-leadership at icann.org > *Cc:* gnso-chairs at icann.org > *Subject:* [council] Re: [soac-chairs] Initiating the Community Dialogue > on "How We Meet": Initial Ideas & Meeting Request > > *CAUTION*: This email originated outside the company. Do not click on > any links or open attachments unless you are expecting them from the > sender. > > *ATTENTION*: Cet e-mail provient de l'ext?rieur de l'entreprise. Ne > cliquez pas sur les liens ou n'ouvrez pas les pi?ces jointes ? moins de > connaitre l'exp?diteur. > > Hi All- resending this email as a reminder. Council Leadership is > requesting feedback by 24 July. > > Thanks, > > Greg > > *From:*DiBiase, Gregory > *Sent:* Tuesday, July 9, 2024 11:02 AM > *To:* GNSO Council List >; 'gnso-sg-c-leadership at icann.org' > > > *Cc:* gnso-chairs at icann.org > *Subject:* FW: [EXTERNAL] [soac-chairs] Initiating the Community > Dialogue on "How We Meet": Initial Ideas & Meeting Request > > Dear Councilors and SG/C Leadership, > > We are forwarding the below message re: ?How We Meet? from ICANN staff. > Please solicit input from your respective groups on the ideas > articulated in the attached Community Discussion Paper. For the purposes > of gathering feedback, GNSO Leadership is happy to collect and collate > inputs from the SG/Cs in order to share it with the other SO/AC Chairs. > Looking at ICANN?s proposed timeline below, please send any feedback to > gnso-chairs at icann.org by 24 July. Let us > know if you have concerns with this approach. > > Thanks, > > Greg on behalf of GNSO Leadership > > *From:*Mary Wong via soac-chairs > > *Sent:* Sunday, July 7, 2024 11:58 PM > *To:* soac-chairs at icann.org > *Cc:* team-leaders at icann.org > *Subject:* [EXTERNAL] [soac-chairs] Initiating the Community Dialogue on > "How We Meet": Initial Ideas & Meeting Request > > *CAUTION*: This email originated from outside of the organization. Do > not click links or open attachments unless you can confirm the sender > and know the content is safe. > > Dear SOAC leaders, > > An action item from your informal meeting with Sally in Kigali was for > the Policy team to facilitate a dialogue with you about ?How We Meet?, > viz., how our in-person and hybrid meetings can be optimized to ensure > that resources (including financial, staff and community time) continue > to be allocated appropriately to ensure the community can do its work > effectively and efficiently, while staying within budgetary constraints. > As a starting point for this dialogue, we have drafted the attached > discussion paper with some initial ideas for your community?s > consideration and to invite your suggestions for further discussion. > > To capitalize on the momentum of recent conversations and to facilitate > a constructive and substantive dialogue, we?d like to suggest the > following cadence of meetings, structured around a few foundational > questions: > > * Late/end-July: first call with SOAC Chairs and Vice-Chairs to share > feedback on agreed strategic questions > * Mid/late August (following collation of ideas and input): second > call to discuss and agree on concrete ideas for implementation or > further exploration > * End-August/early September (if agreed is needed): third call to > review agreed way forward, including any next steps for additional > (longer term) ideas to be discussed further > The sort of strategic, foundational questions we were thinking might be > helpful for focusing the dialogue include: > > o If you or your group could change one thing about how we meet > that will facilitate efficiency in how we deliver ICANN?s > mission while remaining sustainable into the future, what would > that be? > o What other key changes do we need to make to continue to ensure > we can meet these goals? > > Thank you for your support and willingness to collaborate with us in > seeking to improve and optimize how we meet. Assuming you are > comfortable with the proposed approach, I?ll make sure to come back to > you with some suggested dates for the calls. Please let me know if your > group have any questions or would like any additional information that > can assist with your internal discussions about this topic. Thank you! > > Cheers > > Mary > > > ____________________________________________________________________________________________________________ > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez > recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme > ou falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and > delete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have > been modified, changed or falsified. > Thank you. > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -- **DISCLAIMER** *The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Thu Jul 25 01:47:57 2024 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Thu, 25 Jul 2024 08:47:57 +1000 Subject: [NCSG-EC] Fwd: Initiating the Community Dialogue on "How We Meet": Initial Ideas & Meeting Request In-Reply-To: References: Message-ID: Hi Jean, NCSG should be able to respond to follow-up comments. Warmly, Tomslin On Thu, 25 Jul 2024 at 04:30, Jean F. Qu?ralt via NCSG-EC < ncsg-ec at lists.ncsg.is> wrote: > Should anyone want to follow up on some of their recommendations/comments, > would NCSG respond directly or add them to its own comment document? > > Best, > Jean F. Queralt > Founder & CEO - The IO Foundation > Book a meeting (30 minutes) > > > On Wed, 24 Jul 2024 at 23:16, Johan Helsingius via NCSG-EC < > ncsg-ec at lists.ncsg.is> wrote: > >> Interesting comments from ISPC. >> >> Julf >> >> >> >> -------- Forwarded Message -------- >> Subject: [GNSO-SG-C-Leadership] Re: [soac-chairs] Initiating the >> Community Dialogue on "How We Meet": Initial Ideas & Meeting Request >> Date: Wed, 24 Jul 2024 15:09:51 +0000 >> From: philippe.fouquart--- via GNSO-SG-C-Leadership >> >> Reply-To: philippe.fouquart at orange.com >> To: DiBiase, Gregory >> CC: gnso-chairs at icann.org , Novoa, Osvaldo >> via >> ISPCP-Leadership , >> gnso-sg-c-leadership at icann.org >> >> >> >> Hi Greg, >> >> Thanks for this opportunity of providing comments on the proposed >> approach to the Community Dialogue. >> >> You will find attached the ISPCP Constituency?s initial ideas. >> >> Happy to discuss. >> >> Regards, >> >> Philippe, on behalf of the ISPs and Connectivity Providers Constituency >> >> *From:* DiBiase, Gregory via council >> *Sent:* Monday, July 22, 2024 4:44 PM >> *To:* GNSO Council List ; >> gnso-sg-c-leadership at icann.org >> *Cc:* gnso-chairs at icann.org >> *Subject:* [council] Re: [soac-chairs] Initiating the Community Dialogue >> on "How We Meet": Initial Ideas & Meeting Request >> >> *CAUTION*: This email originated outside the company. Do not click on >> any links or open attachments unless you are expecting them from the >> sender. >> >> *ATTENTION*: Cet e-mail provient de l'ext?rieur de l'entreprise. Ne >> cliquez pas sur les liens ou n'ouvrez pas les pi?ces jointes ? moins de >> connaitre l'exp?diteur. >> >> Hi All- resending this email as a reminder. Council Leadership is >> requesting feedback by 24 July. >> >> Thanks, >> >> Greg >> >> *From:*DiBiase, Gregory >> *Sent:* Tuesday, July 9, 2024 11:02 AM >> *To:* GNSO Council List > >; 'gnso-sg-c-leadership at icann.org' >> > >> *Cc:* gnso-chairs at icann.org >> *Subject:* FW: [EXTERNAL] [soac-chairs] Initiating the Community >> Dialogue on "How We Meet": Initial Ideas & Meeting Request >> >> Dear Councilors and SG/C Leadership, >> >> We are forwarding the below message re: ?How We Meet? from ICANN staff. >> Please solicit input from your respective groups on the ideas >> articulated in the attached Community Discussion Paper. For the purposes >> of gathering feedback, GNSO Leadership is happy to collect and collate >> inputs from the SG/Cs in order to share it with the other SO/AC Chairs. >> Looking at ICANN?s proposed timeline below, please send any feedback to >> gnso-chairs at icann.org by 24 July. Let us >> know if you have concerns with this approach. >> >> Thanks, >> >> Greg on behalf of GNSO Leadership >> >> *From:*Mary Wong via soac-chairs > > >> *Sent:* Sunday, July 7, 2024 11:58 PM >> *To:* soac-chairs at icann.org >> *Cc:* team-leaders at icann.org >> *Subject:* [EXTERNAL] [soac-chairs] Initiating the Community Dialogue on >> "How We Meet": Initial Ideas & Meeting Request >> >> *CAUTION*: This email originated from outside of the organization. Do >> not click links or open attachments unless you can confirm the sender >> and know the content is safe. >> >> Dear SOAC leaders, >> >> An action item from your informal meeting with Sally in Kigali was for >> the Policy team to facilitate a dialogue with you about ?How We Meet?, >> viz., how our in-person and hybrid meetings can be optimized to ensure >> that resources (including financial, staff and community time) continue >> to be allocated appropriately to ensure the community can do its work >> effectively and efficiently, while staying within budgetary constraints. >> As a starting point for this dialogue, we have drafted the attached >> discussion paper with some initial ideas for your community?s >> consideration and to invite your suggestions for further discussion. >> >> To capitalize on the momentum of recent conversations and to facilitate >> a constructive and substantive dialogue, we?d like to suggest the >> following cadence of meetings, structured around a few foundational >> questions: >> >> * Late/end-July: first call with SOAC Chairs and Vice-Chairs to share >> feedback on agreed strategic questions >> * Mid/late August (following collation of ideas and input): second >> call to discuss and agree on concrete ideas for implementation or >> further exploration >> * End-August/early September (if agreed is needed): third call to >> review agreed way forward, including any next steps for additional >> (longer term) ideas to be discussed further >> The sort of strategic, foundational questions we were thinking might be >> helpful for focusing the dialogue include: >> >> o If you or your group could change one thing about how we meet >> that will facilitate efficiency in how we deliver ICANN?s >> mission while remaining sustainable into the future, what would >> that be? >> o What other key changes do we need to make to continue to ensure >> we can meet these goals? >> >> Thank you for your support and willingness to collaborate with us in >> seeking to improve and optimize how we meet. Assuming you are >> comfortable with the proposed approach, I?ll make sure to come back to >> you with some suggested dates for the calls. Please let me know if your >> group have any questions or would like any additional information that >> can assist with your internal discussions about this topic. Thank you! >> >> Cheers >> >> Mary >> >> >> ____________________________________________________________________________________________________________ >> Ce message et ses pieces jointes peuvent contenir des informations >> confidentielles ou privilegiees et ne doivent donc >> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez >> recu ce message par erreur, veuillez le signaler >> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages >> electroniques etant susceptibles d'alteration, >> Orange decline toute responsabilite si ce message a ete altere, deforme >> ou falsifie. Merci. >> >> This message and its attachments may contain confidential or privileged >> information that may be protected by law; >> they should not be distributed, used or copied without authorisation. >> If you have received this email in error, please notify the sender and >> delete this message and its attachments. >> As emails may be altered, Orange is not liable for messages that have >> been modified, changed or falsified. >> Thank you. >> _______________________________________________ >> NCSG-EC mailing list >> NCSG-EC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >> > > *DISCLAIMER* > *The content of this message, which may contain personal or sensitive > data, is confidential. If you have received it by mistake, please inform > the sender by replying to the email and then permanently delete the > message, including any attachments. It is forbidden to copy, forward or in > any way reveal the content of this message to anyone. The integrity and > security of this email cannot be guaranteed over the Internet and, > therefore, the sender will not be held liable for any damage caused by the > message.* > _______________________________________________ > 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: From mesumbeslin at gmail.com Thu Jul 25 01:51:52 2024 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Thu, 25 Jul 2024 08:51:52 +1000 Subject: [NCSG-EC] [NCSG-PC] [gnso-chairs] Initiating the Community Dialogue on "How We Meet": Initial Ideas & Meeting Request In-Reply-To: References: <762F544A-1954-4255-B920-FD02149E4C22@icann.org> <9a1df164-3e18-4950-8fcd-fc9d8e8e9dea@Julf.com> Message-ID: Thanks for the input, Bruna. Taking your inputs into consideration, I have modified our response to the following below. Can everyone let me know if it is good to go as preliminary thoughts? I have to send them before midnight UTC 24 July. NCSG Comments: We think that reviewing the ICANN Meeting Strategy after ten years (considering how many important things happened in this period) is a good idea, even if we end up concluding that we should maintain the status quo. While NCSG supports the general idea of reviewing the cost of how we meet or work, if the recommendation out of the review is to reduce sessions and/or travel, we think session/travel reduction should not be done in a blanket way across the board, since all community groups do not have access to equal level of funding outside ICANN. However, our members think the timing of the changes is poor, considering the upcoming new gTLD round and WSIS concerns. The last time we went into a round of new gTLDs, it was a London meeting where 6,000 people. It was apparently the biggest meeting ICANN had ever, ever hosted because there was massive interest, concern, and questions about the new gTLD program. If ICANN cut?s back now, we will lose the very thing that we are trying to do, which is to get many more people involved in and interested in new gTLDs. Newcomers through the applicant support program, through the outreach and marketing are going to come in and they will have a million questions about ICANN. So ICANN needs those education and outreach sessions and we need them sometimes face to face so people can actually ask the dumb question in the hallway. In addition, NCSG members would like to know what is going on financially with ICANN? On Thu, 25 Jul 2024 at 01:50, Bruna Martins dos Santos < bruna.mrtns at gmail.com> wrote: > Besides that, the entire discussion about *creating criteria and metrics > for what "substantial participation" *is indeed important but by > enforcing such things we might miss on relevant opportunities of bringing > in new and shiny stars within our groups and will restrict even further the > spaces for commending members on their dedicated participation and so on. > Instead of just blankly supporting things such as the open concept of > "Substantial participation" we owe it to our groups a proper reflection > that - as opposed to other groups - its very hard for the NCSG-related > volunteers to have ICANN as their primary occupation or as a position > funded by other means besides ICANN Org sponsorship for GNSO SGs and Cs. > Unfortunately our stakeholder group is the weaker link of this equation due > to good old issues such as resources limitation, lack of fully funded NGOs > able to work on ICANN and its PDPs, as well as volunteer burnout due to the > concentration of knowledge and lack of resources for improving capacity > building efforts internally. > > These are my two cents. kind regards, > B > > On Wed, Jul 24, 2024 at 5:44?PM Bruna Martins dos Santos < > bruna.mrtns at gmail.com> wrote: > >> Hello, >> >> Apologies for stepping in late in this discussion but I would perhaps >> rephrase the following sentence: *our members thought ICANN should >> genuinely explore reducing sessions at each meeting and a qualitative >> evaluation of the benefits of face-to-face meetings in general so that we >> fully understand what we are potentially going to lose. *Maybe we can >> frame it as a last resource kinda of exercise since our groups were already >> affected a couple of years ago with recommendations from staff to take less >> meetings during the F2F and prioritizing online interaction. The reason why >> im bringing this story into the conversation is that im concerned that we >> come to a point where community funding will only be faciliated to groups >> w/ a x number of meetings or if we get our space in meetings shortened even >> further. In the last 3-4 years we have had already faced limitations in >> what sorts of rooms and facilities can be offered to us and it would be >> important to think about that before sending the msg @Tomslin Samme-Nlar >> crafted. * best, * >> *B * >> >> On Wed, Jul 24, 2024 at 4:58?PM Johan Helsingius via NCSG-PC < >> ncsg-pc at lists.ncsg.is> wrote: >> >>> Excellent! Thanks, Tomslin!! >>> >>> Julf >>> >>> >>> On 24/07/2024 15:54, Tomslin Samme-Nlar wrote: >>> > Hi PC, >>> > >>> > This is the response I have put together based on the conversation we >>> > had last week and comments of the document. I wil be sending this to >>> Greg: >>> > >>> > Foundational questions: >>> > >>> > >>> > 1. >>> > >>> > If you or your group could change one thing about how we meet that >>> > will facilitate efficiency in how we deliver ICANN?s mission while >>> > remaining sustainable into the future, what would that be? - >>> > >>> > *NCSG Response:* One thing we could try to develop a bit more and >>> think >>> > thoroughly is to focus resources on groups/individuals within ICANN >>> that >>> > actually contribute substantially. I'm aware that creating criteria >>> and >>> > metrics for what "substantial participation" may mean, but the idea >>> here >>> > would be pushing the community towards a proper stimuli environment, >>> > rewarding work effectively done and discouraging people from resting >>> > passively on past laurels (and this should apply not only to >>> > individuals, but to community bodies as a whole.) >>> > >>> > >>> > >>> > Other NCSG Comments: >>> > >>> > >>> > We think that reviewing the ICANN Meeting Strategy >>> > (https://meetings.icann.org/en/future-meeting-strategy >>> > ) after ten >>> years >>> > (considering how many important things happened in this period) is a >>> > good idea, even if we end up concluding that we should maintain the >>> > status quo. >>> > >>> > >>> > In addition, our members thought ICANN should genuinely explore >>> reducing >>> > sessions at each meeting and a qualitative evaluation of the benefits >>> of >>> > face-to-face meetings in general so that we fully understand what we >>> are >>> > potentially going to lose. >>> > >>> > >>> > At the same time, we think session/travel reduction should not be done >>> > in a blanket way across the board, since all community groups do not >>> > have access to equal level of funding outside ICANN. However, our >>> > members think the timing of the changes is poor, considering the >>> > upcoming new gTLD round and WSIS concerns. The last time we went into >>> a >>> > round of new gTLDs, it was a London meeting where 6,000 people. It was >>> > apparently the biggest meeting ICANN had ever, ever hosted >>> > because there was massive interest, concern, and questions >>> about >>> > the new gTLD program. If ICANN cut?s back now, we will lose the >>> very >>> > thing that we are trying to do, which is to get many more people >>> > involved in and interested in new gTLDs. Newcomers through the >>> > applicant support program, through the outreach and marketing >>> are >>> > going to come in and they will have a million questions about ICANN. >>> > So ICANN needs those education and outreach sessions and we need >>> them >>> > sometimes face to face so people can actually ask the dumb question in >>> > the hallway. >>> > >>> > >>> > In addition, NCSG members would like to know what is going on >>> > financially with ICANN. >>> > >>> > >>> > >>> > >>> > >>> > On Thu, 11 Jul 2024 at 08:59, Tomslin Samme-Nlar < >>> mesumbeslin at gmail.com >>> > > wrote: >>> > >>> > Hi team, >>> > >>> > In our SOAC leadership meeting with Sally in Kigali, she mentioned >>> 2 >>> > areas where the community needs to have a dialogue on; (1) "How We >>> > Meet" and (2) "How We Work". Below and attached is a discussion >>> > paper from ICANN's Policy & Advice Development staff team to >>> > facilitate the discussion on dialogue #1 "How We Meet. >>> > >>> > Things will move fast since we have to send our feedback (if any) >>> to >>> > gnso-chairs at icann.org by 24 July >>> > 2024. As a result, I have added this topic as an agenda item to our >>> > monthly policy meeting which is on Monday 15 July at 11:30 UTC (See >>> > Andrea's email/reminder for joining details and full agenda). Come >>> > with some ideas please. I have also created this Google Doc >>> > < >>> https://docs.google.com/document/d/1rQ3_P-xlb48qcy4iY4prOis4Y4O1O2a_geBfrYMuQ4Y/edit?usp=sharing> >>> to solicit feedback from everyone, even if you can't make the meeting. >>> > >>> > In the paper, you will notice a number of suggestions such as: >>> > >>> > 1. Evaluate the full cycle of in-person and hybrid community >>> > meetings, including standalone SOAC Leadership and Strategic >>> > Planning meetings, targeted group meetings (such as the >>> > Contracted Parties Summit, the At Large Summit, and the >>> > High-Level Governmental Meeting) and similar, cost-intensive, >>> > travel-dependent Meetings >>> > 2. Review the planning by ICANN Org and the community for all >>> > in-person/hybrid meetings (including ICANN Public Meetings) by >>> > adopting an annualized, regular approach of planning for a full >>> > meeting cycle (either by a calendar year or a fiscal year) >>> > 3. Review of the current allocation of Funded Travelers to each >>> > ICANN Public Meeting >>> > 4. Reduce the number of sessions at ICANN Public Meetings, which >>> > could result in a reduction in the cost of travel (i.e., >>> > accommodation) and venue-related costs (e.g., room and >>> equipment >>> > rentals, contractors) >>> > 5. Reduce or eliminate informational and training sessions at >>> ICANN >>> > Public Meetings >>> > 6. Reduce or eliminate ICANN-hosted or ICANN-sponsored social and >>> > outreach events at, or associated with, an ICANN Public Meeting >>> > 7. Move at least one (1) upcoming ICANN Public Meeting to a >>> Virtual >>> > Meeting >>> > 8. Review the current state of ICANN Public Meetings, with a view >>> > toward updating the ten-year-old ICANN Meetings Strategy >>> (dating >>> > from 2014) to match current and expected future needs and >>> budget >>> > constraints >>> > >>> > Talk to you all on Monday. >>> > >>> > Warmly, >>> > Tomslin >>> > >>> > >>> > >>> > >>> > *From:* Mary Wong via soac-chairs >> > > >>> > *Sent:* Sunday, July 7, 2024 11:58 PM >>> > *To:* soac-chairs at icann.org >>> > *Cc:* team-leaders at icann.org >>> > *Subject:* [EXTERNAL] [soac-chairs] Initiating the Community >>> > Dialogue on "How We Meet": Initial Ideas & Meeting Request____ >>> > >>> > __ __ >>> > >>> > *CAUTION*: This email originated from outside of the organization. >>> > Do not click links or open attachments unless you can confirm the >>> > sender and know the content is safe.____ >>> > >>> > __ __ >>> > >>> > Dear SOAC leaders,____ >>> > >>> > __ __ >>> > >>> > An action item from your informal meeting with Sally in Kigali was >>> > for the Policy team to facilitate a dialogue with you about ?How We >>> > Meet?, viz., how our in-person and hybrid meetings can be optimized >>> > to ensure that resources (including financial, staff and community >>> > time) continue to be allocated appropriately to ensure the >>> community >>> > can do its work effectively and efficiently, while staying within >>> > budgetary constraints. As a starting point for this dialogue, we >>> > have drafted the attached discussion paper with some initial ideas >>> > for your community?s consideration and to invite your suggestions >>> > for further discussion. ____ >>> > >>> > __ __ >>> > >>> > To capitalize on the momentum of recent conversations and to >>> > facilitate a constructive and substantive dialogue, we?d like to >>> > suggest the following cadence of meetings, structured around a few >>> > foundational questions: ____ >>> > >>> > * Late/end-July: first call with SOAC Chairs and Vice-Chairs to >>> > share feedback on agreed strategic questions ____ >>> > * Mid/late August (following collation of ideas and input): >>> second >>> > call to discuss and agree on concrete ideas for implementation >>> > or further exploration____ >>> > * End-August/early September (if agreed is needed): third call to >>> > review agreed way forward, including any next steps for >>> > additional (longer term) ideas to be discussed further ____ >>> > >>> > __ __ >>> > >>> > The sort of strategic, foundational questions we were thinking >>> might >>> > be helpful for focusing the dialogue include:____ >>> > >>> > o If you or your group could change one thing about how we >>> > meet that will facilitate efficiency in how we deliver >>> > ICANN?s mission while remaining sustainable into the >>> future, >>> > what would that be? ____ >>> > o What other key changes do we need to make to continue to >>> > ensure we can meet these goals?____ >>> > >>> > __ __ >>> > >>> > Thank you for your support and willingness to collaborate with us >>> in >>> > seeking to improve and optimize how we meet. Assuming you are >>> > comfortable with the proposed approach, I?ll make sure to come back >>> > to you with some suggested dates for the calls. Please let me know >>> > if your group have any questions or would like any additional >>> > information that can assist with your internal discussions about >>> > this topic. Thank you!____ >>> > >>> > __ __ >>> > >>> > Cheers____ >>> > >>> > Mary ____ >>> > >>> > __ __ >>> > >>> > __ __ >>> > >>> > __ __ >>> > >>> > _______________________________________________ >>> > 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 >>> _______________________________________________ >>> 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 >> >> German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander >> von Humboldt Foundation >> >> Member | Coaliz?o Direitos na Rede >> Co-Coordinator | Internet Governance Caucus >> >> Twitter: @boomartins // Skype: >> bruna.martinsantos >> Email: bruna.mrtns at gmail.com >> > > > -- > > *Bruna Martins dos Santos * > > Global Campaigns Manager | Digital Action > > German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von > Humboldt Foundation > > Member | Coaliz?o Direitos na Rede > Co-Coordinator | Internet Governance Caucus > > Twitter: @boomartins // Skype: > bruna.martinsantos > Email: bruna.mrtns at gmail.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pedrodeperdigaolana at gmail.com Thu Jul 25 05:14:16 2024 From: pedrodeperdigaolana at gmail.com (=?UTF-8?Q?Pedro_de_Perdig=C3=A3o_Lana?=) Date: Wed, 24 Jul 2024 23:14:16 -0300 Subject: [NCSG-EC] [NCSG-PC] [gnso-chairs] Initiating the Community Dialogue on "How We Meet": Initial Ideas & Meeting Request In-Reply-To: References: <762F544A-1954-4255-B920-FD02149E4C22@icann.org> <9a1df164-3e18-4950-8fcd-fc9d8e8e9dea@Julf.com> Message-ID: Hi Tomslin, Arriving a bit late for this last comment, but just to mention that this final version is fantastic and highlights the most important concerns of noncommercial. Truly well written. Thanks! Cordially, *Pedro de Perdig?o Lana* Advogado - OAB/PR 90.600 , Pesquisador (GEDAI/UFPR ) Doutorando em Direito (UFPR), Mestre em Direito Empresarial (UCoimbra), Membro da Coordena??o - NCUC (ICANN) , ISOC BR , IODA e CC Brasil . Essa mensagem ? restrita ao remetente e destinat?rio(s). Se recebida por engano, favor responder informando o erro. Em qua., 24 de jul. de 2024 ?s 19:52, Tomslin Samme-Nlar via NCSG-EC < ncsg-ec at lists.ncsg.is> escreveu: > Thanks for the input, Bruna. > > Taking your inputs into consideration, I have modified our response to the > following below. Can everyone let me know if it is good to go as > preliminary thoughts? I have to send them before midnight UTC 24 July. > > NCSG Comments: > > We think that reviewing the ICANN Meeting Strategy after ten years > (considering how many important things happened in this period) is a good > idea, even if we end up concluding that we should maintain the status quo. > > While NCSG supports the general idea of reviewing the cost of how we meet > or work, if the recommendation out of the review is to reduce sessions > and/or travel, we think session/travel reduction should not be done in a > blanket way across the board, since all community groups do not have access > to equal level of funding outside ICANN. However, our members think the > timing of the changes is poor, considering the upcoming new gTLD round and > WSIS concerns. The last time we went into a round of new gTLDs, it was a > London meeting where 6,000 people. It was apparently the biggest meeting > ICANN had ever, ever hosted because there was massive interest, > concern, and questions about the new gTLD program. If ICANN cut?s > back now, we will lose the very thing that we are trying to do, which is to > get many more people involved in and interested in new gTLDs. Newcomers > through the applicant support program, through the outreach and > marketing are going to come in and they will have a million questions > about ICANN. So ICANN needs those education and outreach sessions and > we need them sometimes face to face so people can actually ask the dumb > question in the hallway. > > In addition, NCSG members would like to know what is going on financially > with ICANN? > > > On Thu, 25 Jul 2024 at 01:50, Bruna Martins dos Santos < > bruna.mrtns at gmail.com> wrote: > >> Besides that, the entire discussion about *creating criteria and metrics >> for what "substantial participation" *is indeed important but by >> enforcing such things we might miss on relevant opportunities of bringing >> in new and shiny stars within our groups and will restrict even further the >> spaces for commending members on their dedicated participation and so on. >> Instead of just blankly supporting things such as the open concept of >> "Substantial participation" we owe it to our groups a proper reflection >> that - as opposed to other groups - its very hard for the NCSG-related >> volunteers to have ICANN as their primary occupation or as a position >> funded by other means besides ICANN Org sponsorship for GNSO SGs and Cs. >> Unfortunately our stakeholder group is the weaker link of this equation due >> to good old issues such as resources limitation, lack of fully funded NGOs >> able to work on ICANN and its PDPs, as well as volunteer burnout due to the >> concentration of knowledge and lack of resources for improving capacity >> building efforts internally. >> >> These are my two cents. kind regards, >> B >> >> On Wed, Jul 24, 2024 at 5:44?PM Bruna Martins dos Santos < >> bruna.mrtns at gmail.com> wrote: >> >>> Hello, >>> >>> Apologies for stepping in late in this discussion but I would perhaps >>> rephrase the following sentence: *our members thought ICANN should >>> genuinely explore reducing sessions at each meeting and a qualitative >>> evaluation of the benefits of face-to-face meetings in general so that we >>> fully understand what we are potentially going to lose. *Maybe we can >>> frame it as a last resource kinda of exercise since our groups were already >>> affected a couple of years ago with recommendations from staff to take less >>> meetings during the F2F and prioritizing online interaction. The reason why >>> im bringing this story into the conversation is that im concerned that we >>> come to a point where community funding will only be faciliated to groups >>> w/ a x number of meetings or if we get our space in meetings shortened even >>> further. In the last 3-4 years we have had already faced limitations in >>> what sorts of rooms and facilities can be offered to us and it would be >>> important to think about that before sending the msg @Tomslin Samme-Nlar >>> crafted. * best, * >>> *B * >>> >>> On Wed, Jul 24, 2024 at 4:58?PM Johan Helsingius via NCSG-PC < >>> ncsg-pc at lists.ncsg.is> wrote: >>> >>>> Excellent! Thanks, Tomslin!! >>>> >>>> Julf >>>> >>>> >>>> On 24/07/2024 15:54, Tomslin Samme-Nlar wrote: >>>> > Hi PC, >>>> > >>>> > This is the response I have put together based on the conversation we >>>> > had last week and comments of the document. I wil be sending this to >>>> Greg: >>>> > >>>> > Foundational questions: >>>> > >>>> > >>>> > 1. >>>> > >>>> > If you or your group could change one thing about how we meet that >>>> > will facilitate efficiency in how we deliver ICANN?s mission while >>>> > remaining sustainable into the future, what would that be? - >>>> > >>>> > *NCSG Response:* One thing we could try to develop a bit more and >>>> think >>>> > thoroughly is to focus resources on groups/individuals within ICANN >>>> that >>>> > actually contribute substantially. I'm aware that creating criteria >>>> and >>>> > metrics for what "substantial participation" may mean, but the idea >>>> here >>>> > would be pushing the community towards a proper stimuli environment, >>>> > rewarding work effectively done and discouraging people from resting >>>> > passively on past laurels (and this should apply not only to >>>> > individuals, but to community bodies as a whole.) >>>> > >>>> > >>>> > >>>> > Other NCSG Comments: >>>> > >>>> > >>>> > We think that reviewing the ICANN Meeting Strategy >>>> > (https://meetings.icann.org/en/future-meeting-strategy >>>> > ) after ten >>>> years >>>> > (considering how many important things happened in this period) is a >>>> > good idea, even if we end up concluding that we should maintain the >>>> > status quo. >>>> > >>>> > >>>> > In addition, our members thought ICANN should genuinely explore >>>> reducing >>>> > sessions at each meeting and a qualitative evaluation of the benefits >>>> of >>>> > face-to-face meetings in general so that we fully understand what we >>>> are >>>> > potentially going to lose. >>>> > >>>> > >>>> > At the same time, we think session/travel reduction should not be >>>> done >>>> > in a blanket way across the board, since all community groups do not >>>> > have access to equal level of funding outside ICANN. However, our >>>> > members think the timing of the changes is poor, considering the >>>> > upcoming new gTLD round and WSIS concerns. The last time we went into >>>> a >>>> > round of new gTLDs, it was a London meeting where 6,000 people. It >>>> was >>>> > apparently the biggest meeting ICANN had ever, ever hosted >>>> > because there was massive interest, concern, and questions >>>> about >>>> > the new gTLD program. If ICANN cut?s back now, we will lose the >>>> very >>>> > thing that we are trying to do, which is to get many more people >>>> > involved in and interested in new gTLDs. Newcomers through the >>>> > applicant support program, through the outreach and marketing >>>> are >>>> > going to come in and they will have a million questions about >>>> ICANN. >>>> > So ICANN needs those education and outreach sessions and we need >>>> them >>>> > sometimes face to face so people can actually ask the dumb question >>>> in >>>> > the hallway. >>>> > >>>> > >>>> > In addition, NCSG members would like to know what is going on >>>> > financially with ICANN. >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > On Thu, 11 Jul 2024 at 08:59, Tomslin Samme-Nlar < >>>> mesumbeslin at gmail.com >>>> > > wrote: >>>> > >>>> > Hi team, >>>> > >>>> > In our SOAC leadership meeting with Sally in Kigali, she >>>> mentioned 2 >>>> > areas where the community needs to have a dialogue on; (1) "How We >>>> > Meet" and (2) "How We Work". Below and attached is a discussion >>>> > paper from ICANN's Policy & Advice Development staff team to >>>> > facilitate the discussion on dialogue #1 "How We Meet. >>>> > >>>> > Things will move fast since we have to send our feedback (if any) >>>> to >>>> > gnso-chairs at icann.org by 24 July >>>> > 2024. As a result, I have added this topic as an agenda item to >>>> our >>>> > monthly policy meeting which is on Monday 15 July at 11:30 UTC >>>> (See >>>> > Andrea's email/reminder for joining details and full agenda). Come >>>> > with some ideas please. I have also created this Google Doc >>>> > < >>>> https://docs.google.com/document/d/1rQ3_P-xlb48qcy4iY4prOis4Y4O1O2a_geBfrYMuQ4Y/edit?usp=sharing> >>>> to solicit feedback from everyone, even if you can't make the meeting. >>>> > >>>> > In the paper, you will notice a number of suggestions such as: >>>> > >>>> > 1. Evaluate the full cycle of in-person and hybrid community >>>> > meetings, including standalone SOAC Leadership and Strategic >>>> > Planning meetings, targeted group meetings (such as the >>>> > Contracted Parties Summit, the At Large Summit, and the >>>> > High-Level Governmental Meeting) and similar, cost-intensive, >>>> > travel-dependent Meetings >>>> > 2. Review the planning by ICANN Org and the community for all >>>> > in-person/hybrid meetings (including ICANN Public Meetings) by >>>> > adopting an annualized, regular approach of planning for a >>>> full >>>> > meeting cycle (either by a calendar year or a fiscal year) >>>> > 3. Review of the current allocation of Funded Travelers to each >>>> > ICANN Public Meeting >>>> > 4. Reduce the number of sessions at ICANN Public Meetings, which >>>> > could result in a reduction in the cost of travel (i.e., >>>> > accommodation) and venue-related costs (e.g., room and >>>> equipment >>>> > rentals, contractors) >>>> > 5. Reduce or eliminate informational and training sessions at >>>> ICANN >>>> > Public Meetings >>>> > 6. Reduce or eliminate ICANN-hosted or ICANN-sponsored social and >>>> > outreach events at, or associated with, an ICANN Public >>>> Meeting >>>> > 7. Move at least one (1) upcoming ICANN Public Meeting to a >>>> Virtual >>>> > Meeting >>>> > 8. Review the current state of ICANN Public Meetings, with a view >>>> > toward updating the ten-year-old ICANN Meetings Strategy >>>> (dating >>>> > from 2014) to match current and expected future needs and >>>> budget >>>> > constraints >>>> > >>>> > Talk to you all on Monday. >>>> > >>>> > Warmly, >>>> > Tomslin >>>> > >>>> > >>>> > >>>> > >>>> > *From:* Mary Wong via soac-chairs >>> > > >>>> > *Sent:* Sunday, July 7, 2024 11:58 PM >>>> > *To:* soac-chairs at icann.org >>>> > *Cc:* team-leaders at icann.org >>>> > *Subject:* [EXTERNAL] [soac-chairs] Initiating the Community >>>> > Dialogue on "How We Meet": Initial Ideas & Meeting Request____ >>>> > >>>> > __ __ >>>> > >>>> > *CAUTION*: This email originated from outside of the organization. >>>> > Do not click links or open attachments unless you can confirm the >>>> > sender and know the content is safe.____ >>>> > >>>> > __ __ >>>> > >>>> > Dear SOAC leaders,____ >>>> > >>>> > __ __ >>>> > >>>> > An action item from your informal meeting with Sally in Kigali was >>>> > for the Policy team to facilitate a dialogue with you about ?How >>>> We >>>> > Meet?, viz., how our in-person and hybrid meetings can be >>>> optimized >>>> > to ensure that resources (including financial, staff and community >>>> > time) continue to be allocated appropriately to ensure the >>>> community >>>> > can do its work effectively and efficiently, while staying within >>>> > budgetary constraints. As a starting point for this dialogue, we >>>> > have drafted the attached discussion paper with some initial ideas >>>> > for your community?s consideration and to invite your suggestions >>>> > for further discussion. ____ >>>> > >>>> > __ __ >>>> > >>>> > To capitalize on the momentum of recent conversations and to >>>> > facilitate a constructive and substantive dialogue, we?d like to >>>> > suggest the following cadence of meetings, structured around a few >>>> > foundational questions: ____ >>>> > >>>> > * Late/end-July: first call with SOAC Chairs and Vice-Chairs to >>>> > share feedback on agreed strategic questions ____ >>>> > * Mid/late August (following collation of ideas and input): >>>> second >>>> > call to discuss and agree on concrete ideas for implementation >>>> > or further exploration____ >>>> > * End-August/early September (if agreed is needed): third call >>>> to >>>> > review agreed way forward, including any next steps for >>>> > additional (longer term) ideas to be discussed further ____ >>>> > >>>> > __ __ >>>> > >>>> > The sort of strategic, foundational questions we were thinking >>>> might >>>> > be helpful for focusing the dialogue include:____ >>>> > >>>> > o If you or your group could change one thing about how we >>>> > meet that will facilitate efficiency in how we deliver >>>> > ICANN?s mission while remaining sustainable into the >>>> future, >>>> > what would that be? ____ >>>> > o What other key changes do we need to make to continue to >>>> > ensure we can meet these goals?____ >>>> > >>>> > __ __ >>>> > >>>> > Thank you for your support and willingness to collaborate with us >>>> in >>>> > seeking to improve and optimize how we meet. Assuming you are >>>> > comfortable with the proposed approach, I?ll make sure to come >>>> back >>>> > to you with some suggested dates for the calls. Please let me know >>>> > if your group have any questions or would like any additional >>>> > information that can assist with your internal discussions about >>>> > this topic. Thank you!____ >>>> > >>>> > __ __ >>>> > >>>> > Cheers____ >>>> > >>>> > Mary ____ >>>> > >>>> > __ __ >>>> > >>>> > __ __ >>>> > >>>> > __ __ >>>> > >>>> > _______________________________________________ >>>> > 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 >>>> _______________________________________________ >>>> 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 >>> >>> German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander >>> von Humboldt Foundation >>> >>> Member | Coaliz?o Direitos na Rede >>> Co-Coordinator | Internet Governance Caucus >>> >>> Twitter: @boomartins // Skype: >>> bruna.martinsantos >>> Email: bruna.mrtns at gmail.com >>> >> >> >> -- >> >> *Bruna Martins dos Santos * >> >> Global Campaigns Manager | Digital Action >> >> German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander >> von Humboldt Foundation >> >> Member | Coaliz?o Direitos na Rede >> Co-Coordinator | Internet Governance Caucus >> >> Twitter: @boomartins // Skype: >> bruna.martinsantos >> Email: bruna.mrtns at gmail.com >> > _______________________________________________ > 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: From pedrodeperdigaolana at gmail.com Thu Jul 25 05:28:24 2024 From: pedrodeperdigaolana at gmail.com (=?UTF-8?Q?Pedro_de_Perdig=C3=A3o_Lana?=) Date: Wed, 24 Jul 2024 23:28:24 -0300 Subject: [NCSG-EC] Fwd: Initiating the Community Dialogue on "How We Meet": Initial Ideas & Meeting Request In-Reply-To: References: Message-ID: Very interesting and well structured, Julf. I have mixed feelings about the capacity building part, but maybe it would indeed be fruitful to test focusing on continuous and increasingly in-depth learning processes for newcomers who consistently keep engaged (instead of centering resources on attracting larger numbers of an initial contact with ICANN through the opportunity of international travels). Cordially, *Pedro de Perdig?o Lana* Advogado - OAB/PR 90.600 , Pesquisador (GEDAI/UFPR ) Doutorando em Direito (UFPR), Mestre em Direito Empresarial (UCoimbra), Membro da Coordena??o - NCUC (ICANN) , ISOC BR , IODA e CC Brasil . Essa mensagem ? restrita ao remetente e destinat?rio(s). Se recebida por engano, favor responder informando o erro. Em qua., 24 de jul. de 2024 ?s 19:48, Tomslin Samme-Nlar via NCSG-EC < ncsg-ec at lists.ncsg.is> escreveu: > Hi Jean, > > NCSG should be able to respond to follow-up comments. > > Warmly, > Tomslin > > > > On Thu, 25 Jul 2024 at 04:30, Jean F. Qu?ralt via NCSG-EC < > ncsg-ec at lists.ncsg.is> wrote: > >> Should anyone want to follow up on some of their >> recommendations/comments, would NCSG respond directly or add them to its >> own comment document? >> >> Best, >> Jean F. Queralt >> Founder & CEO - The IO Foundation >> Book a meeting (30 minutes) >> >> >> On Wed, 24 Jul 2024 at 23:16, Johan Helsingius via NCSG-EC < >> ncsg-ec at lists.ncsg.is> wrote: >> >>> Interesting comments from ISPC. >>> >>> Julf >>> >>> >>> >>> -------- Forwarded Message -------- >>> Subject: [GNSO-SG-C-Leadership] Re: [soac-chairs] Initiating the >>> Community Dialogue on "How We Meet": Initial Ideas & Meeting Request >>> Date: Wed, 24 Jul 2024 15:09:51 +0000 >>> From: philippe.fouquart--- via GNSO-SG-C-Leadership >>> >>> Reply-To: philippe.fouquart at orange.com >>> To: DiBiase, Gregory >>> CC: gnso-chairs at icann.org , Novoa, Osvaldo >>> via >>> ISPCP-Leadership , >>> gnso-sg-c-leadership at icann.org >>> >>> >>> >>> Hi Greg, >>> >>> Thanks for this opportunity of providing comments on the proposed >>> approach to the Community Dialogue. >>> >>> You will find attached the ISPCP Constituency?s initial ideas. >>> >>> Happy to discuss. >>> >>> Regards, >>> >>> Philippe, on behalf of the ISPs and Connectivity Providers Constituency >>> >>> *From:* DiBiase, Gregory via council >>> *Sent:* Monday, July 22, 2024 4:44 PM >>> *To:* GNSO Council List ; >>> gnso-sg-c-leadership at icann.org >>> *Cc:* gnso-chairs at icann.org >>> *Subject:* [council] Re: [soac-chairs] Initiating the Community Dialogue >>> on "How We Meet": Initial Ideas & Meeting Request >>> >>> *CAUTION*: This email originated outside the company. Do not click on >>> any links or open attachments unless you are expecting them from the >>> sender. >>> >>> *ATTENTION*: Cet e-mail provient de l'ext?rieur de l'entreprise. Ne >>> cliquez pas sur les liens ou n'ouvrez pas les pi?ces jointes ? moins de >>> connaitre l'exp?diteur. >>> >>> Hi All- resending this email as a reminder. Council Leadership is >>> requesting feedback by 24 July. >>> >>> Thanks, >>> >>> Greg >>> >>> *From:*DiBiase, Gregory >>> *Sent:* Tuesday, July 9, 2024 11:02 AM >>> *To:* GNSO Council List >> >; 'gnso-sg-c-leadership at icann.org' >>> > >>> *Cc:* gnso-chairs at icann.org >>> *Subject:* FW: [EXTERNAL] [soac-chairs] Initiating the Community >>> Dialogue on "How We Meet": Initial Ideas & Meeting Request >>> >>> Dear Councilors and SG/C Leadership, >>> >>> We are forwarding the below message re: ?How We Meet? from ICANN staff. >>> Please solicit input from your respective groups on the ideas >>> articulated in the attached Community Discussion Paper. For the purposes >>> of gathering feedback, GNSO Leadership is happy to collect and collate >>> inputs from the SG/Cs in order to share it with the other SO/AC Chairs. >>> Looking at ICANN?s proposed timeline below, please send any feedback to >>> gnso-chairs at icann.org by 24 July. Let us >>> know if you have concerns with this approach. >>> >>> Thanks, >>> >>> Greg on behalf of GNSO Leadership >>> >>> *From:*Mary Wong via soac-chairs >> > >>> *Sent:* Sunday, July 7, 2024 11:58 PM >>> *To:* soac-chairs at icann.org >>> *Cc:* team-leaders at icann.org >>> *Subject:* [EXTERNAL] [soac-chairs] Initiating the Community Dialogue on >>> "How We Meet": Initial Ideas & Meeting Request >>> >>> *CAUTION*: This email originated from outside of the organization. Do >>> not click links or open attachments unless you can confirm the sender >>> and know the content is safe. >>> >>> Dear SOAC leaders, >>> >>> An action item from your informal meeting with Sally in Kigali was for >>> the Policy team to facilitate a dialogue with you about ?How We Meet?, >>> viz., how our in-person and hybrid meetings can be optimized to ensure >>> that resources (including financial, staff and community time) continue >>> to be allocated appropriately to ensure the community can do its work >>> effectively and efficiently, while staying within budgetary constraints. >>> As a starting point for this dialogue, we have drafted the attached >>> discussion paper with some initial ideas for your community?s >>> consideration and to invite your suggestions for further discussion. >>> >>> To capitalize on the momentum of recent conversations and to facilitate >>> a constructive and substantive dialogue, we?d like to suggest the >>> following cadence of meetings, structured around a few foundational >>> questions: >>> >>> * Late/end-July: first call with SOAC Chairs and Vice-Chairs to share >>> feedback on agreed strategic questions >>> * Mid/late August (following collation of ideas and input): second >>> call to discuss and agree on concrete ideas for implementation or >>> further exploration >>> * End-August/early September (if agreed is needed): third call to >>> review agreed way forward, including any next steps for additional >>> (longer term) ideas to be discussed further >>> The sort of strategic, foundational questions we were thinking might be >>> helpful for focusing the dialogue include: >>> >>> o If you or your group could change one thing about how we meet >>> that will facilitate efficiency in how we deliver ICANN?s >>> mission while remaining sustainable into the future, what would >>> that be? >>> o What other key changes do we need to make to continue to ensure >>> we can meet these goals? >>> >>> Thank you for your support and willingness to collaborate with us in >>> seeking to improve and optimize how we meet. Assuming you are >>> comfortable with the proposed approach, I?ll make sure to come back to >>> you with some suggested dates for the calls. Please let me know if your >>> group have any questions or would like any additional information that >>> can assist with your internal discussions about this topic. Thank you! >>> >>> Cheers >>> >>> Mary >>> >>> >>> ____________________________________________________________________________________________________________ >>> Ce message et ses pieces jointes peuvent contenir des informations >>> confidentielles ou privilegiees et ne doivent donc >>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez >>> recu ce message par erreur, veuillez le signaler >>> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages >>> electroniques etant susceptibles d'alteration, >>> Orange decline toute responsabilite si ce message a ete altere, deforme >>> ou falsifie. Merci. >>> >>> This message and its attachments may contain confidential or privileged >>> information that may be protected by law; >>> they should not be distributed, used or copied without authorisation. >>> If you have received this email in error, please notify the sender and >>> delete this message and its attachments. >>> As emails may be altered, Orange is not liable for messages that have >>> been modified, changed or falsified. >>> Thank you. >>> _______________________________________________ >>> NCSG-EC mailing list >>> NCSG-EC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>> >> >> *DISCLAIMER* >> *The content of this message, which may contain personal or sensitive >> data, is confidential. If you have received it by mistake, please inform >> the sender by replying to the email and then permanently delete the >> message, including any attachments. It is forbidden to copy, forward or in >> any way reveal the content of this message to anyone. The integrity and >> security of this email cannot be guaranteed over the Internet and, >> therefore, the sender will not be held liable for any damage caused by the >> message.* >> _______________________________________________ >> NCSG-EC mailing list >> NCSG-EC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >> > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Fri Jul 26 09:30:32 2024 From: julf at Julf.com (Johan Helsingius) Date: Fri, 26 Jul 2024 08:30:32 +0200 Subject: [NCSG-EC] Fwd: [GNSO-SG-C-Leadership] Re: [gnso-chairs] Re: [soac-chairs] Initiating the Community Dialogue on "How We Meet": Initial Ideas & Meeting Request In-Reply-To: <92A25906-B26B-499C-90B1-840FB2D06997@verisign.com> References: <92A25906-B26B-499C-90B1-840FB2D06997@verisign.com> Message-ID: FYI - good point from RySG. Julf -------- Forwarded Message -------- Subject: [GNSO-SG-C-Leadership] Re: [gnso-chairs] Re: [soac-chairs] Initiating the Community Dialogue on "How We Meet": Initial Ideas & Meeting Request Date: Thu, 25 Jul 2024 21:20:31 +0000 From: Demetriou, Samantha via GNSO-SG-C-Leadership Reply-To: Demetriou, Samantha To: terri.agnew at icann.org , aheineman at godaddy.com , philippe.fouquart at orange.com , dibiase at amazon.com CC: gnso-chairs at icann.org , ispcp-leadership at icann.org , gnso-sg-c-leadership at icann.org Hi all, Thank you for the extra time on this. The RySG offers the following feedback on the ?How We Meet? paper and proposed community dialogue: The RySG appreciates the opportunity to comment on this important issue. Continued community reflection on how to make ICANN?s processes more efficient and effective is always valuable.?However, the RySG believes that holding these discussions and possibly ?agreeing? to changes through ICANN Org consultations with the SO/AC leadership is not the right approach. These matters are fundamental to the operation of ICANN and the multi-stakeholder community. The last review of ?how we meet? was the 2014 cross-community working group process that led to the current Meeting Strategy and the RySG believes that any changes to that strategy need to be agreed thorough a similar cross-community process and not through a brief set of questions put to the SO/AC Leaders with a request that they consult their communities. The RySG stands ready to participate in such a working group. The RySG looks forward to identifying and discussing relevant issues for any Working Group Charter, such as future budgetary considerations, remote participation, climate impacts, current cadence and structure with the Community and the Board. The RySG encourages ICANN to provide concrete data around existing meeting structures and associated costs in advance of discussions with the Community to facilitate substantive, targeted discussions. The RySG appreciates ICANN bringing this important topic to the forefront and looks forward to discussion with the broader ICANN Community. Thanks, Sam -- Samantha Demetriou RySG Chair *From: *Terri Agnew via GNSO-SG-C-Leadership *Reply-To: *Terri Agnew *Date: *Wednesday, July 24, 2024 at 6:15?PM *To: *"aheineman at godaddy.com" , "philippe.fouquart at orange.com" , "DiBiase, Gregory" *Cc: *"gnso-chairs at icann.org" , "Novoa, Osvaldo via ISPCP-Leadership" , "gnso-sg-c-leadership at icann.org" *Subject: *[EXTERNAL] [GNSO-SG-C-Leadership] Re: [gnso-chairs] Re: [soac-chairs] Initiating the Community Dialogue on "How We Meet": Initial Ideas & Meeting Request *Caution:*This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi Ashley, We can offer the extension until Monday, 29 July 2024. Thanks for checking in! Terri *From: *aheineman--- via Gnso-chairs *Reply-To: *"aheineman at godaddy.com" *Date: *Wednesday, July 24, 2024 at 12:13 PM *To: *"philippe.fouquart at orange.com" , "DiBiase, Gregory" *Cc: *"gnso-chairs at icann.org" , "Novoa, Osvaldo via ISPCP-Leadership" , "gnso-sg-c-leadership at icann.org" *Subject: *[gnso-chairs] Re: [soac-chairs] Initiating the Community Dialogue on "How We Meet": Initial Ideas & Meeting Request Apologies, but would it be possible to get an extension?? The RrSG is in process of drafting an initial response, but needs until next week if that is possible. *From:* philippe.fouquart--- via GNSO-SG-C-Leadership *Sent:* Wednesday, July 24, 2024 11:10 AM *To:* DiBiase, Gregory *Cc:* gnso-chairs at icann.org; Novoa, Osvaldo via ISPCP-Leadership ; gnso-sg-c-leadership at icann.org *Subject:* [GNSO-SG-C-Leadership] Re: [soac-chairs] Initiating the Community Dialogue on "How We Meet": Initial Ideas & Meeting Request Caution:This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad at . Hi Greg, Thanks for this opportunity of providing comments on the proposed approach to the Community Dialogue. You will find attached the ISPCP Constituency?s initial ideas. Happy to discuss. Regards, Philippe, on behalf of the ISPs and Connectivity Providers Constituency *From:*DiBiase, Gregory via council > *Sent:* Monday, July 22, 2024 4:44 PM *To:* GNSO Council List >; gnso-sg-c-leadership at icann.org *Cc:* gnso-chairs at icann.org *Subject:* [council] Re: [soac-chairs] Initiating the Community Dialogue on "How We Meet": Initial Ideas & Meeting Request *CAUTION*: This email originated outside the company. Do not click on any links or open attachments unless you are expecting them from the sender. *ATTENTION*: Cet e-mail provient de l'ext?rieur de l'entreprise. Ne cliquez pas sur les liens ou n'ouvrez pas les pi?ces jointes ? moins de connaitre l'exp?diteur. Hi All- resending this email as a reminder.? Council Leadership is requesting feedback by 24 July. Thanks, Greg *From:* DiBiase, Gregory *Sent:* Tuesday, July 9, 2024 11:02 AM *To:* GNSO Council List >; 'gnso-sg-c-leadership at icann.org' > *Cc:* gnso-chairs at icann.org *Subject:* FW: [EXTERNAL] [soac-chairs] Initiating the Community Dialogue on "How We Meet": Initial Ideas & Meeting Request Dear Councilors and SG/C Leadership, We are forwarding the below message re: ?How We Meet? from ICANN staff. Please solicit input from your respective groups on the ideas articulated in the attached Community Discussion Paper. For the purposes of gathering feedback, GNSO Leadership is happy to collect and collate inputs from the SG/Cs in order to share it with the other SO/AC Chairs. Looking at ICANN?s proposed timeline below, please send any feedback to gnso-chairs at icann.org by 24 July. Let us know if you have concerns with this approach. Thanks, Greg on behalf of GNSO Leadership *From:* Mary Wong via soac-chairs > *Sent:* Sunday, July 7, 2024 11:58 PM *To:* soac-chairs at icann.org *Cc:* team-leaders at icann.org *Subject:* [EXTERNAL] [soac-chairs] Initiating the Community Dialogue on "How We Meet": Initial Ideas & Meeting Request *CAUTION*: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Dear SOAC leaders, An action item from your informal meeting with Sally in Kigali was for the Policy team to facilitate a dialogue with you about ?How We Meet?, viz., how our in-person and hybrid meetings can be optimized to ensure that resources (including financial, staff and community time) continue to be allocated appropriately to ensure the community can do its work effectively and efficiently, while staying within budgetary constraints. As a starting point for this dialogue, we have drafted the attached discussion paper with some initial ideas for your community?s consideration and to invite your suggestions for further discussion. To capitalize on the momentum of recent conversations and to facilitate a constructive and substantive dialogue, we?d like to suggest the following cadence of meetings, structured around a few foundational questions: * Late/end-July: first call with SOAC Chairs and Vice-Chairs to share feedback on agreed strategic questions * Mid/late August (following collation of ideas and input): second call to discuss and agree on concrete ideas for implementation or further exploration * End-August/early September (if agreed is needed): third call to review agreed way forward, including any next steps for additional (longer term) ideas to be discussed further The sort of strategic, foundational questions we were thinking might be helpful for focusing the dialogue include: o If you or your group could change one thing about how we meet that will facilitate efficiency in how we deliver ICANN?s mission while remaining sustainable into the future, what would that be? o What other key changes do we need to make to continue to ensure we can meet these goals? Thank you for your support and willingness to collaborate with us in seeking to improve and optimize how we meet. Assuming you are comfortable with the proposed approach, I?ll make sure to come back to you with some suggested dates for the calls. Please let me know if your group have any questions or would like any additional information that can assist with your internal discussions about this topic. Thank you! Cheers Mary ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- _______________________________________________ GNSO-SG-C-Leadership mailing list -- gnso-sg-c-leadership at icann.org To unsubscribe send an email to gnso-sg-c-leadership-leave at icann.org _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. From julf at Julf.com Fri Jul 26 17:14:51 2024 From: julf at Julf.com (Johan Helsingius) Date: Fri, 26 Jul 2024 16:14:51 +0200 Subject: [NCSG-EC] Fwd: [SOAC-Leaders-ICANNMeeting-Planning] Re: [Ext] Re: Re: ICANN81 Block Schedule, Production Timeline In-Reply-To: References: Message-ID: -------- Forwarded Message -------- Subject: [SOAC-Leaders-ICANNMeeting-Planning] Re: [Ext] Re: Re: ICANN81 Block Schedule, Production Timeline Date: Fri, 26 Jul 2024 15:41:35 +0200 From: Alejandra Reynoso Barral via SOAC-Leaders-ICANNMeeting-Planning Reply-To: Alejandra Reynoso Barral To: Nathalie Peregrine CC: soac-leaders-icannmeeting-planning at icann.org , ccNSO Secretariat Dear All The ccNSO Council suggests a plenary session during the ICANN 81 meeting to be held in Istanbul in November 2024, on the topic of the WSIS+20 Review and what ICANN (the community and the organisation) can do to help advertise and preserve ICANN?s multi-stakeholder model, and the broader multi-stakeholder internet governance approach, during the Review. ICANN is working with the community to reflect on lessons learned in the GDC process during 2023-2024, and developing a strategy for the role ICANN and its community can play during the WSIS+20 review in 2024 and 2025. By the time ICANN81 rolls around, this strategy should be well developed, and it will be time to further mobilise the ICANN community around the role it can play in this important work. The main outcomes of such a session should be that: * The ICANN community is well informed about the strategic approach to the WSIS+20 Review, and what role individual organisations and communities can play * The ICANN community is mobilised to play the roles they can play as part of the Review A secondary outcome would be the sharing of greater insight about where the WSIS+20 review is at, though this can be covered in the Geopolitical session. Best regards, Alejandra ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. ******************************************* On Fri, Jul 19, 2024 at 6:03?PM Nathalie Peregrine > wrote: Dear Alejandra and all,____ __ __ Thank you for the update! Given the email issues today, and the fact I believe several groups might also need additional time, we can postpone this to Tuesday 30th July. ____ __ __ Please take note this extension concerns the Community Session topic *only*. Having received no objection on the Block Schedule, it is considered finalized, bar the Community Session slot which will be confirmed on Tuesday 30^th July. This will be the final deadline to avoid impacting the SO/AC internal scheduling process further. ____ __ __ I hope this works well for all!____ __ __ Kind regards,____ __ __ Nathalie____ __ __ *From: *Alejandra Reynoso Barral > *Date: *Friday, 19 July 2024 at 17:45 *To: *Nathalie Peregrine > *Cc: *"soac-leaders-icannmeeting-planning at icann.org " > *Subject: *Re: [SOAC-Leaders-ICANNMeeting-Planning] Re: [Ext] Re: Re: ICANN81 Block Schedule, Production Timeline____ __ __ Dear Nathalie and all ____ __ __ Yesterday the ccNSO Council had its July meeting and we want to put forward a plenary topic but need a bit more time to prepare the proposal.____ Can we send it early next week?____ __ __ Best regards,____ Alejandra____ ____ ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. *******************************************____ __ __ __ __ On Thu, Jul 11, 2024 at 4:57?PM Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning > wrote:____ Hello all!____ ____ I hope you are doing well!____ ____ A friendly reminder to please consider the action items below, and should topics for the ICANN81 Community Session be raised within your groups, to please share on this list for discussion. The deadline for topic submission on the list is 19 July 2024.____ ____ Thank you all!____ ____ Kind regards,____ ____ Nathalie____ ____ *From: *Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning > *Reply to: *Nathalie Peregrine > *Date: *Monday, 1 July 2024 at 10:20 *To: *"soac-leaders-icannmeeting-planning at icann.org " > *Subject: *[SOAC-Leaders-ICANNMeeting-Planning] Re: [Ext] Re: Re: ICANN81 Block Schedule, Production Timeline____ ____ Dear all,____ ____ Thank you so much for joining the ICANN81 Kick off call! The input shared, be it feedback for ICANN80 and advice regarding the ICANN81 Block Schedule was extremely helpful!____ ____ Please find the Zoom chat text and slide deck from the call attached to this email.? The Zoom recording can be accessed here . ____ ____ Regarding the block schedule, please also find the latest version attached with the following change:____ * Monday?s Q&A with ICANN Org?s Executive Team removed, and replaced by the Geopolitical Forum initially scheduled on Tuesday.____ ____ Thank you to Alejandra for her input on the Community Session topic deadline! The previous deadline of the 12^th July 2024 can be extended to the 19^th July 2024. However, it would be interesting to hear from community leaders on the matter before then via the mailing list. Please do bear in mind, that there is no obligation for this Community Session to take place, should there be no clear topic community groups agree upon, the session can be postponed until ICANN82. ____ ____ *Action Items for all:*____ * Kindly express any objection to the current block schedule as speedily as possible.____ * Please review the joint Board & SO/AC slots and raise concerns should there be any____ * Begin conversations about the Community Session topic and the need for such a session to be held at ICANN81____ ____ Thank you to all and have a lovely week!____ ____ Kind regards,____ ____ Nathalie____ ____ ____ ____ *From: *Alejandra Reynoso Barral > *Date: *Friday, 28 June 2024 at 13:04 *To: *Nathalie Peregrine > *Cc: *"soac-leaders-icannmeeting-planning at icann.org " > *Subject: *[Ext] Re: [SOAC-Leaders-ICANNMeeting-Planning] Re: ICANN81 Block Schedule, Production Timeline____ ____ Dear Nathalie and All ____ ____ It was good to see/hear you at?the kickoff call.____ ____ I understand the eagerness to finalize the block schedule as soon as possible, but the current 12th of July deadline to submit a community session topic is a bit tight. ____ The ccNSO council will meet on the 18th of July and, depending on the outcome of the discussion of this item, we may or may not want to submit something.____ Can the deadline be extended?____ ____ Best regards,____ Alejandra____ ____ ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. *******************************************____ ____ ____ On Wed, Jun 26, 2024 at 10:13?AM Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning > wrote:____ 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 > *Date: *Wednesday, 22 May 2024 at 22:13 *To: *"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____ ____ ____ _______________________________________________ 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.____ _______________________________________________ SOAC-Leaders-ICANNMeeting-Planning mailing list -- soac-leaders-icannmeeting-planning at icann.org To unsubscribe send an email to soac-leaders-icannmeeting-planning-leave at icann.org _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy ) and the website Terms of Service (https://www.icann.org/privacy/tos ). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.____ -------------- next part -------------- _______________________________________________ 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 julf at Julf.com Sat Jul 27 16:19:39 2024 From: julf at Julf.com (Johan Helsingius) Date: Sat, 27 Jul 2024 15:19:39 +0200 Subject: [NCSG-EC] [NCSG-PC] Fwd: Initiating the Community Dialogue on "How We Meet": Initial Ideas & Meeting Request In-Reply-To: References: Message-ID: <2d22aba0-0c6e-497e-aa3b-debc12a91c35@Julf.com> I agree we should focus on attracting new blood that actually contributes to policy work rather than outreach effort that attracts larger number of newcomers who then disappear after a while. Julf On 25/07/2024 04:28, Pedro de Perdig?o Lana wrote: > Very interesting and well structured, Julf. I have mixed feelings about > the capacity building part, but maybe it would indeed be fruitful to > test focusing on continuous and increasingly in-depth learning processes > for newcomers who consistently keep engaged (instead of centering > resources on attracting larger numbers of an initial contact with ICANN > through the opportunity of international travels). > > Cordially, > > *Pedro de Perdig?o Lana* > Advogado - OAB/PR 90.600 , Pesquisador (GEDAI/UFPR > ) > Doutorando em Direito (UFPR), Mestre em Direito Empresarial (UCoimbra), > Membro da Coordena??o - NCUC (ICANN) , ISOC BR > , IODA e CC Brasil > . > Essa mensagem ? restrita ao remetente e destinat?rio(s). Se recebida por > engano, favor responder informando o erro. > From julf at Julf.com Wed Jul 31 15:24:33 2024 From: julf at Julf.com (Johan Helsingius) Date: Wed, 31 Jul 2024 14:24:33 +0200 Subject: [NCSG-EC] Fwd: [SOAC-Leaders-ICANNMeeting-Planning] Re: [Ext] proposal for ICANN81 Community Sessionncs In-Reply-To: References: Message-ID: <3f5a9726-2f98-4e81-ab2f-ab0f3c7d4fa1@Julf.com> -------- Forwarded Message -------- Subject: [SOAC-Leaders-ICANNMeeting-Planning] Re: [Ext] proposal for ICANN81 Community Session Date: Tue, 30 Jul 2024 06:33:07 +0000 From: Susan Payne via SOAC-Leaders-ICANNMeeting-Planning Reply-To: Susan Payne To: Nathalie Peregrine , soac-leaders-icannmeeting-planning at icann.org Hi all The IPC would like to put forward a topic for a potential Community Session at ICANN 81, for consideration by the group: Working Title: Reviewing ICANN?s Accountability Mechanisms Aim:? To hold a general discussion across the community about the ICANN Accountability Mechanisms, particularly the Request for Reconsideration (RFR) and Independent Review Process (IRP) in order to elicit views on whether: * these mechanisms are fit for purpose * there are unintended outcomes resulting from the manner in which these mechanisms are set out in the Bylaws.? For example: o do the standing and grounds requirements for either mechanism serve to exclude legitimate access by those that the community intended to have access, such as SO, AC, SG and Cs o Are these mechanisms available to any classes of complainant who were not intended by the community to have access to them o Is the EC IRP process sufficiently clear and unambiguous. * there are concerns sufficient to warrant review and potential revision of the relevant Bylaws provisions and, if so, whether there is a sufficient support from the community to convene a CCWG to work on this. Brief Background: On a number of occasions recently, including in meetings with the GNSO Council, ICANN Board Members have expressed the view that the IRP, as presently drafted, could be used by classes of potential claimant who were never intended to have access to this mechanism, such as an unsuccessful respondent to an ICANN RFP or tender process. ?Board Members have expressed the desire for a community discussion on this. At the same time, the GNSO?s Intellectual Property Constituency recently brought a RFR against a proposal by the Board that would have had the effect of changing a Fundamental Bylaws without following the Bylaws-mandated process for doing so.? The IPC?s RFR was summarily dismissed as failing to demonstrate that the IPC was harmed by such a Board action. The intent of this session would not be to publicly debate the IPC?s ongoing disagreement with ICANN over the RFR, which is currently in the Co-Operative Engagement Process.? Rather, we believe that both examples demonstrate that there are concerns, both on ICANN Org?s side and on the Community side, with these important accountability mechanisms which were revised as a result of the cross community work on Accountability in the context of the IANA Transition.? We believe this is an appropriate time for a discussion on whether the mechanisms meet the community?s expectations, or whether they would benefit from a more formal review and revision. Susan Payne (on behalf of IPC) Susan Payne Head of Legal Policy Image 28 Little Russell Street, London?WC1A 2HN,?UK *T*+44 (0) 20 7421 8250 *Ext*?255 *comlaude.com * /Follow us on//LinkedIn //and//YouTube / *Image* ***Image* ***Image* ***Image* Image Get Outlook for iOS ------------------------------------------------------------------------ *From:* Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning *Sent:* Thursday, July 11, 2024 3:59 PM *To:* soac-leaders-icannmeeting-planning at icann.org *Subject:* [SOAC-Leaders-ICANNMeeting-Planning] Re: [Ext] Re: Re: ICANN81 Block Schedule, Production Timeline Hello all! I hope you are doing well! A friendly reminder to please consider the action items below, and should topics for the ICANN81 Community Session be raised within your groups, to please share on this list for discussion. The deadline for topic submission on the list is 19 July 2024. Thank you all! Kind regards, Nathalie *From: *Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning *Reply to: *Nathalie Peregrine *Date: *Monday, 1 July 2024 at 10:20 *To: *"soac-leaders-icannmeeting-planning at icann.org" *Subject: *[SOAC-Leaders-ICANNMeeting-Planning] Re: [Ext] Re: Re: ICANN81 Block Schedule, Production Timeline Dear all, Thank you so much for joining the ICANN81 Kick off call! The input shared, be it feedback for ICANN80 and advice regarding the ICANN81 Block Schedule was extremely helpful! Please find the Zoom chat text and slide deck from the call attached to this email. ?The Zoom recording can be accessed here . Regarding the block schedule, please also find the latest version attached with the following change: * Monday?s Q&A with ICANN Org?s Executive Team removed, and replaced by the Geopolitical Forum initially scheduled on Tuesday. Thank you to Alejandra for her input on the Community Session topic deadline! The previous deadline of the 12^th July 2024 can be extended to the 19^th July 2024. However, it would be interesting to hear from community leaders on the matter before then via the mailing list. Please do bear in mind, that there is no obligation for this Community Session to take place, should there be no clear topic community groups agree upon, the session can be postponed until ICANN82. *Action Items for all:* * Kindly express any objection to the current block schedule as speedily as possible. * Please review the joint Board & SO/AC slots and raise concerns should there be any * Begin conversations about the Community Session topic and the need for such a session to be held at ICANN81 Thank you to all and have a lovely week! Kind regards, Nathalie *From: *Alejandra Reynoso Barral *Date: *Friday, 28 June 2024 at 13:04 *To: *Nathalie Peregrine *Cc: *"soac-leaders-icannmeeting-planning at icann.org" *Subject: *[Ext] Re: [SOAC-Leaders-ICANNMeeting-Planning] Re: ICANN81 Block Schedule, Production Timeline Dear Nathalie and All It was good to see/hear you at?the kickoff call. I understand the eagerness to finalize the block schedule as soon as possible, but the current 12th of July deadline to submit a community session topic is a bit tight. The ccNSO council will meet on the 18th of July and, depending on the outcome of the discussion of this item, we may or may not want to submit something. Can the deadline be extended? Best regards, Alejandra ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. ******************************************* On Wed, Jun 26, 2024 at 10:13?AM Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning > wrote: 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 > *Date: *Wednesday, 22 May 2024 at 22:13 *To: *"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 _______________________________________________ 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. ------------------------------------------------------------------------ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the ?Com Laude Group?) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com -------------- 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 julf at Julf.com Wed Jul 31 15:26:46 2024 From: julf at Julf.com (Johan Helsingius) Date: Wed, 31 Jul 2024 14:26:46 +0200 Subject: [NCSG-EC] Fwd: [SOAC-Leaders-ICANNMeeting-Planning] ALAC proposal for ICANN81 Community Session topic In-Reply-To: References: Message-ID: <96af0d6b-f3e6-4e3f-b2e6-f920298043ea@Julf.com> -------- Forwarded Message -------- Subject: [SOAC-Leaders-ICANNMeeting-Planning] ALAC proposal for ICANN81 Community Session topic Date: Tue, 30 Jul 2024 19:12:41 +0800 From: Justine Chew via SOAC-Leaders-ICANNMeeting-Planning Reply-To: Justine Chew To: Nathalie Peregrine , soac-leaders-icannmeeting-planning at icann.org Hello Nathalie, Dear all, The ALAC/At-Large would like to propose for consideration by the group, the following potential ICANN81 Community Session topic: _Working Title_: Shifting Paradigms: Multistakeholderism, Geopolitics, International Law, and New Internet Infrastructures. _Objective/Aims_: To explore the intersections of geopolitics, international law, and emerging internet infrastructures. Key topics include the reshaping of the multistakeholder model, implications for new internet infrastructures, and data governance. The discussion will reference the 2024 United States International Cyberspace & Digital Policy Strategy, EU's GDPR, the AI Act, and NIS2.?This session is crucial for end users, regulators, policymakers, technologists, legal experts, academics, and other stakeholders in the Internet governance community. It emphasizes the link between infrastructure governance and data management from the end user perspective, highlighting the importance of user-centric approaches in shaping the future of internet infrastructures. _Proposed Speakers_: ?- Vint Cerf, Internet Pioneer ?- Leon Sanchez, ICANN Board Member ?- Jorge Cancio, Deputy Head of the International Relations Team at the Federal Office of Communications (OFCOM); GAC Switzerland ?- Pari Esfandiari, ALAC/EURALO, Global TechnoPolitics Forum ?- Susan Chalmers, Internet Policy Specialist, US Department of Commerce, NTIA ?- Berna Ak?al? G?r, Lecturer, CCLS Queen Mary University of London, Associate Research Fellow at UNU-CRIS Digital Cluster ?- John Crain, ICANN SVP & Chief Technology Officer _Moderator:_ Joanna Kulesza, ALAC Liaison to the GAC _Scoping Questions_: 1. ?How should the multistakeholder model evolve to accommodate new internet infrastructures and the shift towards them in governance? 2. ?What are the primary governance challenges posed by the development of new internet infrastructures and governance models? 3. ?How do existing regulatory frameworks like GDPR, the AI Act, and NIS2 address the challenges and opportunities presented by new internet infrastructures and respective governance models? _Expected Outcomes_: - A comprehensive understanding of the challenges and opportunities presented by new internet infrastructures and the regulatory shift towards them - MSM implications. - Insight into how existing regulatory frameworks, including the MSM, can adapt to these emerging technologies. - Enhanced dialogue among stakeholders on the future of multistakeholder Internet governance. On behalf of the ALAC/At-Large, Justine Chew * * On Sat, 20 Jul 2024 at 00:03, Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning > wrote: Dear Alejandra and all,____ __ __ Thank you for the update! Given the email issues today, and the fact I believe several groups might also need additional time, we can postpone this to Tuesday 30th July. ____ __ __ Please take note this extension concerns the Community Session topic *only*. Having received no objection on the Block Schedule, it is considered finalized, bar the Community Session slot which will be confirmed on Tuesday 30^th July. This will be the final deadline to avoid impacting the SO/AC internal scheduling process further. ____ __ __ I hope this works well for all!____ __ __ Kind regards,____ __ __ Nathalie____ -------------- 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 julf at Julf.com Wed Jul 31 15:28:23 2024 From: julf at Julf.com (Johan Helsingius) Date: Wed, 31 Jul 2024 14:28:23 +0200 Subject: [NCSG-EC] Fwd: [SOAC-Leaders-ICANNMeeting-Planning] Updated: INPUT NEEDED ICANN81 Community Session Topic by Wednesday 07 August 2024 In-Reply-To: <599D1663-3954-40F4-A3F1-8308B4240167@icann.org> References: <599D1663-3954-40F4-A3F1-8308B4240167@icann.org> Message-ID: <1c39a5a9-5589-4fcd-bdb2-3777ddba1890@Julf.com> -------- Forwarded Message -------- Subject: [SOAC-Leaders-ICANNMeeting-Planning] Updated: INPUT NEEDED ICANN81 Community Session Topic by Wednesday 07 August 2024 Date: Tue, 30 Jul 2024 14:51:07 +0000 From: Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning Reply-To: Nathalie Peregrine To: soac-leaders-icannmeeting-planning at icann.org **With additional RrSG topic added, and extended deadline 7^th August 20:00 UTC, thank you to Alejandra and Justine for the suggestion!** Dear all, The deadline for topic suggestions regarding the ICANN81 Community Session has now passed. You may have seen three proposals circulated on this mailing list. I have posted them below in order of submission. In order to finalize the choice of topic, we would like to invite ICANN community leaders ?to submit their choices via the mailing list by responding to these two questions: 1. Which topic is your group most interested in? /(Please bear in mind that ?none? is also an acceptable response)/ 2. Would this topic engage your group to the point of taking part in the organization of the session? Kindly respond by _Wednesday 7 August 2024 2000 UTC._ __ Thank you all! ** 1. *ccNSO Proposal* The ccNSO Council suggests a plenary session during the ICANN 81 meeting to be held in Istanbul in November 2024, on the topic of the WSIS+20 Review and what ICANN (the community and the organisation) can do to help advertise and preserve ICANN?s multi-stakeholder model, and the broader multi-stakeholder internet governance approach, during the Review. ICANN is working with the community to reflect on lessons learned in the GDC process during 2023-2024, and developing a strategy for the role ICANN and its community can play during the WSIS+20 review in 2024 and 2025. By the time ICANN81 rolls around, this strategy should be well developed, and it will be time to further mobilise the ICANN community around the role it can play in this important work. The main outcomes of such a session should be that: * The ICANN community is well informed about the strategic approach to the WSIS+20 Review, and what role individual organisations and communities can play * The ICANN community is mobilised to play the roles they can play as part of the Review A secondary outcome would be the sharing of greater insight about where the WSIS+20 review is at, though this can be covered in the Geopolitical session. 2. *IPC Proposal* _Working Title:_Reviewing ICANN?s Accountability Mechanisms _Aim:_? To hold a general discussion across the community about the ICANN Accountability Mechanisms, particularly the Request for Reconsideration (RFR) and Independent Review Process (IRP) in order to elicit views on whether: * these mechanisms are fit for purpose * there are unintended outcomes resulting from the manner in which these mechanisms are set out in the Bylaws.? For example: o do the standing and grounds requirements for either mechanism serve to exclude legitimate access by those that the community intended to have access, such as SO, AC, SG and Cs o Are these mechanisms available to any classes of complainant who were not intended by the community to have access to them o Is the EC IRP process sufficiently clear and unambiguous. * there are concerns sufficient to warrant review and potential revision of the relevant Bylaws provisions and, if so, whether there is a sufficient support from the community to convene a CCWG to work on this. _Brief Background:_ On a number of occasions recently, including in meetings with the GNSO Council, ICANN Board Members have expressed the view that the IRP, as presently drafted, could be used by classes of potential claimant who were never intended to have access to this mechanism, such as an unsuccessful respondent to an ICANN RFP or tender process. ?Board Members have expressed the desire for a community discussion on this. At the same time, the GNSO?s Intellectual Property Constituency recently brought a RFR against a proposal by the Board that would have had the effect of changing a Fundamental Bylaws without following the Bylaws-mandated process for doing so.? The IPC?s RFR was summarily dismissed as failing to demonstrate that the IPC was harmed by such a Board action. The intent of this session would not be to publicly debate the IPC?s ongoing disagreement with ICANN over the RFR, which is currently in the Co-Operative Engagement Process.? Rather, we believe that both examples demonstrate that there are concerns, both on ICANN Org?s side and on the Community side, with these important accountability mechanisms which were revised as a result of the cross community work on Accountability in the context of the IANA Transition.? We believe this is an appropriate time for a discussion on whether the mechanisms meet the community?s expectations, or whether they would benefit from a more formal review and revision. ** *3) At-Large/ ALAC Proposal* _Working Title_: Shifting Paradigms: Multistakeholderism, Geopolitics, International Law, and New Internet Infrastructures. _Objective/Aims_: To explore the intersections of geopolitics, international law, and emerging internet infrastructures. Key topics include the reshaping of the multistakeholder model, implications for new internet infrastructures, and data governance. The discussion will reference the 2024 United States International Cyberspace & Digital Policy Strategy, EU's GDPR, the AI Act, and NIS2.?This session is crucial for end users, regulators, policymakers, technologists, legal experts, academics, and other stakeholders in the Internet governance community. It emphasizes the link between infrastructure governance and data management from the end user perspective, highlighting the importance of user-centric approaches in shaping the future of internet infrastructures. _Proposed Speakers_: ?- Vint Cerf, Internet Pioneer ?- Leon Sanchez, ICANN Board Member ?- Jorge Cancio, Deputy Head of the International Relations Team at the Federal Office of Communications (OFCOM); GAC Switzerland ?- Pari Esfandiari, ALAC/EURALO, Global TechnoPolitics Forum ?- Susan Chalmers, Internet Policy Specialist, US Department of Commerce, NTIA ?- Berna Ak?al? G?r, Lecturer, CCLS Queen Mary University of London, Associate Research Fellow at UNU-CRIS Digital Cluster ?- John Crain, ICANN SVP & Chief Technology Officer _Moderator:_?Joanna Kulesza, ALAC Liaison to the GAC _Scoping Questions_: 1. ?How should the multistakeholder model evolve to accommodate new internet infrastructures and the shift towards them in governance? 2. ?What are the primary governance challenges posed by the development of new internet infrastructures and governance models? 3. ?How do existing regulatory frameworks like GDPR, the AI Act, and NIS2 address the challenges and opportunities presented by new internet infrastructures and respective governance models? _Expected Outcomes_: - A comprehensive understanding of the challenges and opportunities presented by new internet infrastructures and the regulatory shift towards them - MSM implications. - Insight into how existing regulatory frameworks, including the MSM, can adapt to these emerging technologies. - Enhanced dialogue among stakeholders on the future of multistakeholder Internet governance. 4. *RrSG Proposal* ** RrSG Proposal for ICANN81 Plenary Session: The Registrant?s Journey Follow along with our hero Sophia Exemplar as she begins her Registrant Journey and encounters ICANN policies in the registration and use of her new domain name to create a fan website for the 1960s TV show /Thunderbirds/. Along the way, she?ll encounter choices for registration data submission and publication, phishing emails and deceptive notices, and renewal reminders. She?ll consider moving to a new registrar, or even giving the domain name away to a friend, and more. Will Sophia?s journey be a success? We?ll poll the meeting attendees to help her decide what to do at each important step in the process. /This session takes attendees through important aspects of the domain name lifecycle, covering registration data collection requirements, choices around data masking or publication, contacts sent to the domain owner, and processes including registrar transfer and change of ownership data. Attendees will gain a greater understanding of the industry landscape and domain owner experience. / **