From rafik.dammak at gmail.com Thu May 1 00:49:26 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Thu, 1 May 2025 06:49:26 +0900 Subject: [NCSG-PC] NCSG rep to Planning Prioritization Group Message-ID: hi all, Amin as secondary member in the community planning prioritization group informed me that the group is confirming the membership for FY27: Dear Planning Prioritization Group (PPG) members, > > We would like to thank you again for being a member of the Community > Planning Prioritization Group. > > During the development of the Draft FY2630 Operating Plan and FY26 Budget, > there were no new community recommendation activities to prioritize. Drafts > of these plans were published for Public Comment in December 2024. Please > see the publication of the Draft FY26*?*30 Operating Plan and Draft FY26 > Budget here > > . > > > *Action to Confirm Members:*As there were not any activities to > prioritize for FY26, we are proposing that each PPG member continue to > serve the group for FY27. > Please confirm this approach with your SO/AC leadership. If there are any > changes to the primary and secondary members, please email the Planning > team by 6 May 2025. > If there are no objections or requests for changes by 6 May 2025, we will > convene the FY27 Planning Prioritization process with the current members. > The process will involve meetings starting in late May 2025. > > For more information and the current members please see the Planning > Prioritization Framework V4 > and > Community webpage here > > . > > > Thank you, > ICANN org Planning" Currently Peter and Amin are representing NCSG there . so the action here is to confirm them or if we need to replace any. Amin expressed interest to continue as a secondary or primary member. The deadline to respond to the group is the 6th May. Best, Rafik -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Thu May 1 14:16:26 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Thu, 1 May 2025 20:16:26 +0900 Subject: [NCSG-PC] Kickoff discussion about GNSO council chair and vice-chair In-Reply-To: References: Message-ID: Thanks Farzaneh. Yes it is clear that CSG cannot have both chair and vice chair positions. Rafik On Thu, May 1, 2025, 00:00 farzaneh badii wrote: > Hi Rafik > > We will interview them but I think we should be clear that we can't have > both nominations to the council to come from CSG. If we agree on one of > their candidates, the other has to come from NSCG. from our side, I heard > from Peter that he would like to also be nominated for the vice chair > position. But at the moment I haven't heard anyone volunteering for the > Chair. > > Best regards, > > Farzaneh > > > On Wed, Apr 30, 2025 at 8:13?AM Rafik Dammak > wrote: > >> Hi all, >> >> Mason from CSG reached out to initiate discussion about GNSO council >> chair election and vice chair appointment. CSG might propose a candidate >> for GNSO chair and for they would propose Lawrence for vice chair position. >> We need to confirm if we have or not a candidate from our side. For their >> candidate which would need nomination from NCPH they will have to be >> interviewed by us and vetted. >> I will also check in CPH side about their plan too. >> I will discuss with Mason, feel free to share your thoughts about the >> direction to take. >> >> Best, >> >> Rafik >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From farzaneh.badii at gmail.com Thu May 1 17:15:18 2025 From: farzaneh.badii at gmail.com (farzaneh badii) Date: Thu, 1 May 2025 10:15:18 -0400 Subject: [NCSG-PC] law enforcement authentication and RDRS Message-ID: Hi all, I am one of your reps on RDRS, the triage system for disclosure of domain name private, sensitive data requests. Law enforcement is asking if they can submit domain names to ICANN so that if registrars receive requests from RDRS that information can be accompanied by it as well. I think this is a better approach than what we have now that anybody can say I am law enforcement. But we have to be careful and have accountability mechanisms in place later on. Here is what Gabe from FBI requested: During the RDRS meeting, Gabe noted that he?s working with the Public Safety Working Group on both short-term and long-term approaches to support ICANN community efforts around law enforcement authentication. As part of the short-term solution, they are exploring a mechanism that involves compiling a list of domain names tied to known law enforcement agencies. The idea is that these domain names could be shared with ICANN technical staff to integrate into the RDRS. If someone submits a disclosure request via RDRS and the request comes from an email address associated with a verified law enforcement domain, that information could serve as an additional data point. This data point could then be shared with registrars to help inform their disclosure decisions, particularly in the context of rights balancing. Gabe emphasized that this would involve minimal technical work and is still exploratory. He?s asking the committee if there are any objections to him passing these verified law enforcement domains to the RDRS staff, with the goal of continuing this short-term work. He acknowledged this might not need to be formally documented in the RDRS report, but raised it in case there were concerns or feedback from the group. Farzaneh -------------- next part -------------- An HTML attachment was scrubbed... URL: From farzaneh.badii at gmail.com Thu May 1 17:27:34 2025 From: farzaneh.badii at gmail.com (farzaneh badii) Date: Thu, 1 May 2025 10:27:34 -0400 Subject: [NCSG-PC] Fwd: [council] Next steps for the Whois Accuracy Implementation Advisory Group In-Reply-To: References: Message-ID: Tomslin, Didn't we agree to defer indefinitely? It would be good to review it and try to bring privacy to every domain name registrant regardless of where they are but I don't think that is a battle we can win considering we don't have the resources and can't do that through this group and we can work on implementation of DPS which applies to all registrars and registries. Farzaneh On Tue, Apr 29, 2025 at 9:06?PM Tomslin Samme-Nlar wrote: > FYI team. > > I am keen to hear any thoughts on the questions posed below on the steps > for the Whois Accuracy Implementation Advisory Group. > > @Stephanie E Perrin looking to you for > some guidance as well being our WHOIS expert then. > > Remain blessed, > Tomslin > > > ---------- Forwarded message --------- > From: DiBiase, Gregory via council > Date: Tue, 22 Apr 2025 at 02:28 > Subject: [council] Next steps for the Whois Accuracy Implementation > Advisory Group > To: Council at icann.org > > > Dear Councilors, > > > > During our April meeting > , > we discussed potential next steps for the Whois Accuracy Implementation > Advisory Group. Background and potential options are below (the meeting > recording > > includes additional). Please discuss with your SGs and provide feedback by *Friday, > 2 May.* > > > > *What is this procedure?* > > > > ICANN?s Procedure For Handling Registration Data Directory Services > Conflicts with Privacy Law > > is a procedure that allows Contracted Parties to demonstrate when they are > prevented by local laws from fully complying with the provisions of ICANN > contracts regarding personal data in RDDS. After receiving a recommendation > from the 2003 Whois Task Force, the GNSO launched a PDP on this topic in > 2005, and ICANN org implemented a procedure in 2006. The procedure was > updated in 2017 to include an alternative trigger. > > > > *Why is the Council considering this now? * > > > > Following the addition of the new alternative trigger to the procedure in > 2017, the GNSO Council was set to review the procedure by launching a PDP. > However, because the EPDP on the Temporary Specification was engaged in > parallel work, the GNSO Council decided to pause the call for volunteers > until the EPDP Team delivered its report. Following the publication of the > Final Report, ICANN org and Contracted Parties agreed to prioritize their > work on the Data Processing Specification prior to revisiting the Conflicts > Procedure. > > > > ICANN org published the Data Processing Specification > > (DPS) in January 2025. Now that the DPS is complete, the Council is > considering if/how it should proceed on reviewing the Conflicts Procedure. > > > > *Questions to consider?* > > > > As discussed during the Council meeting and brought up councilors, some of > the factors to consider in determining how to proceed include: > > > > - Do Contracted Parties (the parties who would use the procedure) > believe this is an urgent need as no Contracted Parties have used the > procedure in years? > - Does the new Registration Data Policy, which becomes effective in > August, obviate the need for a modification to the procedure? > - Does the Council believe this should be a priority, which would > require other work to be de-prioritized? > > > > *Potential Options* > > > > 1. *Defer/Leave procedure as is* > - If Councilors (particularly Contracted Parties) do not believe > this procedure needs an urgent modification, further work could be: > 1. *Deferred indefinitely* until the Community communicates a > need to review (in other words, leave the procedure alone until the > Community informs Council it needs to be reviewed.) > 2. *Deferred for a finite amount of time* (1 year, 2 years, > etc.) to revisit if updates may be needed > 2. *Proceed with original plan - ICANN org to draft modification in > consultation with CPs* > - If Councilors (particularly Contracted Parties) believe this work > is urgent and important, the Council *could request ICANN org to > draft a modification* to the procedure in consultation with > Contracted Parties before sharing with the Council. (As noted above, due to > resource constraints, the Council would need to determine what work can be > de-prioritized in order to prioritize this work.) > 3. *Terminate/Retire procedure* > - During the meeting, some councilors noted it may be worth > terminating/retiring this procedure due to flaws. It is important to note > that the termination/retirement of the procedure *would require > further policy work* as this procedure is the product of GNSO > policy recommendations. If the Council does not want to extend resources on > this procedure at this time, it may be worth exploring Option 1. > > > > *Deadline for Feedback?* > > > > Please socialize with your respective SG/Cs and let the Council know how > you think it should proceed by *Friday, 2 May.* > > > > Thanks, > > Greg > > > _______________________________________________ > council mailing list -- council at icann.org > To unsubscribe send an email to council-leave at icann.org > > _______________________________________________ > By submitting your personal data, you consent to the processing of your > personal data for purposes of subscribing to this mailing list accordance > with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and > the website Terms of Service (https://www.icann.org/privacy/tos). You can > visit the Mailman link above to change your membership status or > configuration, including unsubscribing, setting digest-style delivery or > disabling delivery altogether (e.g., for a vacation), and so on. > _______________________________________________ > 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 julf at Julf.com Thu May 1 17:36:43 2025 From: julf at Julf.com (Johan Helsingius) Date: Thu, 1 May 2025 16:36:43 +0200 Subject: [NCSG-PC] law enforcement authentication and RDRS In-Reply-To: References: Message-ID: <2bb19b44-e96b-4efe-8c4a-9c8d1463e0c3@Julf.com> I think it is an OK idea as long as it is really only "an additional data point". Julf On 01/05/2025 16:15, farzaneh badii wrote: > Hi all, > > I am one of your reps on RDRS, the triage system for disclosure of > domain name private, sensitive data requests. Law enforcement is asking > if they can submit domain names to ICANN so that if registrars receive > requests from RDRS that information can be accompanied by it as well. I > think this is a better approach than what we have now that anybody can > say I am law enforcement. But we have to be careful and have > accountability mechanisms?in place later on. Here is what Gabe from FBI > requested: > > During the RDRS meeting, Gabe noted that he?s working with the Public > Safety Working Group on both short-term and long-term approaches to > support ICANN community efforts around law enforcement authentication. > As part of the short-term solution, they are exploring a mechanism that > involves compiling a list of domain names tied to known law enforcement > agencies. The idea is that these domain names could be shared with ICANN > technical staff to integrate into the RDRS. > > If someone submits a disclosure request via RDRS and the request comes > from an email address associated with a verified law enforcement domain, > that information could serve as an additional data point. This data > point could then be shared with registrars to help inform their > disclosure decisions, particularly in the context of rights balancing. > > Gabe emphasized that this would involve minimal technical work and is > still exploratory. He?s asking the committee if there are any objections > to him passing these verified law enforcement domains to the RDRS staff, > with the goal of continuing this short-term work. He acknowledged this > might not need to be formally documented in the RDRS report, but raised > it in case there were concerns or feedback from the group. > > > Farzaneh > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc From Kathy at KathyKleiman.com Thu May 1 22:18:34 2025 From: Kathy at KathyKleiman.com (Kathy Kleiman) Date: Thu, 1 May 2025 15:18:34 -0400 Subject: [NCSG-PC] law enforcement authentication and RDRS In-Reply-To: <2bb19b44-e96b-4efe-8c4a-9c8d1463e0c3@Julf.com> References: <2bb19b44-e96b-4efe-8c4a-9c8d1463e0c3@Julf.com> Message-ID: <3ab70cf2-698f-4aca-b8b8-98d473c3ce07@KathyKleiman.com> Agreed Julf, and tx Farzi.? But do we have to educate ICANN or the registrars on spoofing - and how easily something appears to be coming from one email and it's coming from another? Best, Kathy On 5/1/2025 10:36 AM, Johan Helsingius via NCSG-PC wrote: > I think it is an OK idea as long as it is really only "an additional > ?data point". > > ????Julf > > On 01/05/2025 16:15, farzaneh badii wrote: >> Hi all, >> >> I am one of your reps on RDRS, the triage system for disclosure of >> domain name private, sensitive data requests. Law enforcement is >> asking if they can submit domain names to ICANN so that if registrars >> receive requests from RDRS that information can be accompanied by it >> as well. I think this is a better approach than what we have now that >> anybody can say I am law enforcement. But we have to be careful and >> have accountability mechanisms?in place later on. Here is what Gabe >> from FBI requested: >> >> During the RDRS meeting, Gabe noted that he?s working with the Public >> Safety Working Group on both short-term and long-term approaches to >> support ICANN community efforts around law enforcement >> authentication. As part of the short-term solution, they are >> exploring a mechanism that involves compiling a list of domain names >> tied to known law enforcement agencies. The idea is that these domain >> names could be shared with ICANN technical staff to integrate into >> the RDRS. >> >> If someone submits a disclosure request via RDRS and the request >> comes from an email address associated with a verified law >> enforcement domain, that information could serve as an additional >> data point. This data point could then be shared with registrars to >> help inform their disclosure decisions, particularly in the context >> of rights balancing. >> >> Gabe emphasized that this would involve minimal technical work and is >> still exploratory. He?s asking the committee if there are any >> objections to him passing these verified law enforcement domains to >> the RDRS staff, with the goal of continuing this short-term work. He >> acknowledged this might not need to be formally documented in the >> RDRS report, but raised it in case there were concerns or feedback >> from the group. >> >> >> Farzaneh >> >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc From mesumbeslin at gmail.com Fri May 2 00:52:06 2025 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Fri, 2 May 2025 07:52:06 +1000 Subject: [NCSG-PC] Fwd: [council] Next steps for the Whois Accuracy Implementation Advisory Group In-Reply-To: References: Message-ID: Thanks Farzi and @nyamamutondo at gmail.com for your responses. Farzi, yes we did discuss that but it didn't appear that we had concluded on it. I will pass this position to council mailing list if this is agreeable to us all. Remain blessed, Tomslin On Fri, 2 May 2025, 00:28 farzaneh badii, wrote: > Tomslin, > > Didn't we agree to defer indefinitely? It would be good to review it and > try to bring privacy to every domain name registrant regardless of where > they are but I don't think that is a battle we can win considering we don't > have the resources and can't do that through this group and we can work on > implementation of DPS which applies to all registrars and registries. > > > > > > Farzaneh > > > On Tue, Apr 29, 2025 at 9:06?PM Tomslin Samme-Nlar > wrote: > >> FYI team. >> >> I am keen to hear any thoughts on the questions posed below on the steps >> for the Whois Accuracy Implementation Advisory Group. >> >> @Stephanie E Perrin looking to you for >> some guidance as well being our WHOIS expert then. >> >> Remain blessed, >> Tomslin >> >> >> ---------- Forwarded message --------- >> From: DiBiase, Gregory via council >> Date: Tue, 22 Apr 2025 at 02:28 >> Subject: [council] Next steps for the Whois Accuracy Implementation >> Advisory Group >> To: Council at icann.org >> >> >> Dear Councilors, >> >> >> >> During our April meeting >> , >> we discussed potential next steps for the Whois Accuracy Implementation >> Advisory Group. Background and potential options are below (the meeting >> recording >> >> includes additional). Please discuss with your SGs and provide feedback by *Friday, >> 2 May.* >> >> >> >> *What is this procedure?* >> >> >> >> ICANN?s Procedure For Handling Registration Data Directory Services >> Conflicts with Privacy Law >> >> is a procedure that allows Contracted Parties to demonstrate when they are >> prevented by local laws from fully complying with the provisions of ICANN >> contracts regarding personal data in RDDS. After receiving a recommendation >> from the 2003 Whois Task Force, the GNSO launched a PDP on this topic in >> 2005, and ICANN org implemented a procedure in 2006. The procedure was >> updated in 2017 to include an alternative trigger. >> >> >> >> *Why is the Council considering this now? * >> >> >> >> Following the addition of the new alternative trigger to the procedure in >> 2017, the GNSO Council was set to review the procedure by launching a PDP. >> However, because the EPDP on the Temporary Specification was engaged in >> parallel work, the GNSO Council decided to pause the call for volunteers >> until the EPDP Team delivered its report. Following the publication of the >> Final Report, ICANN org and Contracted Parties agreed to prioritize their >> work on the Data Processing Specification prior to revisiting the Conflicts >> Procedure. >> >> >> >> ICANN org published the Data Processing Specification >> >> (DPS) in January 2025. Now that the DPS is complete, the Council is >> considering if/how it should proceed on reviewing the Conflicts Procedure. >> >> >> >> *Questions to consider?* >> >> >> >> As discussed during the Council meeting and brought up councilors, some >> of the factors to consider in determining how to proceed include: >> >> >> >> - Do Contracted Parties (the parties who would use the procedure) >> believe this is an urgent need as no Contracted Parties have used the >> procedure in years? >> - Does the new Registration Data Policy, which becomes effective in >> August, obviate the need for a modification to the procedure? >> - Does the Council believe this should be a priority, which would >> require other work to be de-prioritized? >> >> >> >> *Potential Options* >> >> >> >> 1. *Defer/Leave procedure as is* >> - If Councilors (particularly Contracted Parties) do not believe >> this procedure needs an urgent modification, further work could be: >> 1. *Deferred indefinitely* until the Community communicates a >> need to review (in other words, leave the procedure alone until the >> Community informs Council it needs to be reviewed.) >> 2. *Deferred for a finite amount of time* (1 year, 2 years, >> etc.) to revisit if updates may be needed >> 2. *Proceed with original plan - ICANN org to draft modification >> in consultation with CPs* >> - If Councilors (particularly Contracted Parties) believe this >> work is urgent and important, the Council *could request ICANN org >> to draft a modification* to the procedure in consultation with >> Contracted Parties before sharing with the Council. (As noted above, due to >> resource constraints, the Council would need to determine what work can be >> de-prioritized in order to prioritize this work.) >> 3. *Terminate/Retire procedure* >> - During the meeting, some councilors noted it may be worth >> terminating/retiring this procedure due to flaws. It is important to note >> that the termination/retirement of the procedure *would require >> further policy work* as this procedure is the product of GNSO >> policy recommendations. If the Council does not want to extend resources on >> this procedure at this time, it may be worth exploring Option 1. >> >> >> >> *Deadline for Feedback?* >> >> >> >> Please socialize with your respective SG/Cs and let the Council know how >> you think it should proceed by *Friday, 2 May.* >> >> >> >> Thanks, >> >> Greg >> >> >> _______________________________________________ >> council mailing list -- council at icann.org >> To unsubscribe send an email to council-leave at icann.org >> >> _______________________________________________ >> By submitting your personal data, you consent to the processing of your >> personal data for purposes of subscribing to this mailing list accordance >> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and >> the website Terms of Service (https://www.icann.org/privacy/tos). You >> can visit the Mailman link above to change your membership status or >> configuration, including unsubscribing, setting digest-style delivery or >> disabling delivery altogether (e.g., for a vacation), and so on. >> _______________________________________________ >> 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 ncsg at tapani.tarvainen.info Fri May 2 10:38:12 2025 From: ncsg at tapani.tarvainen.info (Tapani Tarvainen) Date: Fri, 2 May 2025 10:38:12 +0300 Subject: [NCSG-PC] [GNSO-SG-C-Leadership] Request for Early Input | GNSO Latin Script Diacritics Policy Development Process Working Group In-Reply-To: References: <85BF13AC-B56A-4C81-9F1B-BADC6DDB65D3@icann.org> Message-ID: Hi Rafik, I don't think a late early input would be all that useful at this time. Better save the effort to public comment, when the request comes. The WG's call yesterday reviewed early inputs that had come in time, there were only two and one of them (ispcp) was simply "No specific/additional input other than those suggested by ISPCP members during LD PDP". The one fro RrSG was more substantial, one I disagree with there is "Measures should be considered which would ensure that matching domains are only offered to the same owner, e.g. best.quebec and best.qu?bec cannot be owned by two different parties, in order to reduce potential for confusion." While that makes sense for cases like .qu?bec where the strings clearly refer to the same thing, it's not different in cases where the strings are of different origin. E.g., jon.sj?berg and jon.sj?berg could well be different sites without much confusion (lots of similar cases exist as 2nd and 3rd level domains right now). Tapani On Wed, Apr 30, 2025 at 09:06:12PM +0900, Rafik Dammak (rafik.dammak at gmail.com) wrote: > > Hi all, > > The deadline for submitting input passed few days ago but I am wondering if > we should send something anyway based on what Tapani shared. @Tapani > Tarvainen the WG is able to accommodate a > late submission if any? > > Best, > > Rafik > > > On Wed, Apr 9, 2025, 23:52 Tapani Tarvainen > wrote: > > > Hi all, > > > > Following up here, as I posted on the discuss list the LD PDP WG met > > again today and discussed another to me arbitrary-looking limitation > > of the charter, namely whether the PDP scope includes cases where > > someone applies for diacritic versions of a string only and not the > > base ASCII version. > > > > It was pretty much agreed that there's no technical or other apparent > > reason to exclude them except that the language of the charter > > explicitly talks about base ASCII version being present. It was > > suggested this may have been an oversight on the part of the council, > > someone said that it had not even occurred to them that there might be > > several different diacritic versions of the same character but since > > it's been agreed that the WG will consider such, it makes no sense to > > exclude applications for diacritic versions only. > > > > It was suggested but not decided that the WG might go back to > > the council to ask for clarification or extension of the charter > > to include such cases that could naturally be dealt with at > > the same time. > > > > When the council considers the project plan of the WG (tomorrow > > unless I'm mistaken) some of our councillors might want to alert > > the council about the issue. > > > > In any case I'm planning to write up all such cases that the PDP > > charter excludes for no good reason other than that they did not occur > > to the council at the time the PDP was created. I will then suggest we > > put them in our response to the early input request. > > > > Cheers, > > > > Tapani > > > > On Mon, Apr 07, 2025 at 04:32:39PM +0300, Tapani Tarvainen ( > > ncsg at tapani.tarvainen.info) wrote: > > > > > > Thank you Rafik. > > > > > > I took the liberty of adding myself back to the PC list (it's been > > > customary for former Chairs to be there, but I removed myself from > > > there some years ago). > > > > > > Anyway, following up today's PC call, the Latin Diacritics WG > > > project plan is here: > > > > > > > > https://gnso.icann.org/sites/default/files/policy/2025/presentation/project-plan-latin-script-diacritics-26mar25-en.pdf > > > > > > Timeline can be found there even if not in the most readable form. > > > > > > I'll add a quote from the slides presented in WG meeting: > > > > > > "When the Next Round similarity process finds ASCII/diacritic gTLDs to > > > be similar, this WG will provide rules for diacritics." > > > > > > So the intent is to affect the Next Round. > > > > > > (Slide 9 in WG meeting two, the whole slide deck can be found under > > > backround documents here: > > > > > https://icann-community.atlassian.net/wiki/spaces/gnsolsdpdp/pages/176029697/2025-04-02+Latin+Script+Diacritics+-+Meeting+02 > > ) > > > > > > And as I said I find it odd that the rules will be defined for, e.g., > > > German/Swedish/Finnish/Estonian/Icelandic ? (o with two dots) but not > > > for Norwegian/Danish/Faroese ? (o with stroke). > > > > > > I can imagine a Dane called Sj?berg being annoyed if a Swede gets > > > .sj?berg and an Icelander gets .sj?berg while .sj?berg is being > > > denied because of a technicality. > > > > > > There are other similar cases. I would have preferred including all > > > confusingly similar-looking non-ASCII additions to the Latin script > > > rather than using the technical Unicode definition that users should > > > really not be expected to care of know about. > > > > > > Tapani > > > > > > On Thu, Apr 03, 2025 at 10:02:01AM +0900, Rafik Dammak ( > > rafik.dammak at gmail.com) wrote: > > > > > > > > hi all, > > > > > > > > a reminder about this request for input. added Tapani in cc as he is an > > > > active participant of this WG. > > > > > > > > Best, > > > > > > > > Rafik > > > > > > > > > > > > Le ven. 21 mars 2025 ? 09:48, Rafik Dammak a > > > > ?crit : > > > > > > > > > hi all, > > > > > > > > > > we got this request for input as part of the newly established WG on > > latin > > > > > scripts diacritics. > > > > > > > > > > Best, > > > > > > > > > > Rafik > > > > > > > > > > ---------- Forwarded message --------- > > > > > > > > > > Dear SG/C Leaders, > > > > > > > > > > > > > > > > > > > > We are writing to you on behalf of the GNSO Latin Script Diacritics > > (LD) > > > > > Policy Development Process (PDP) Working Group (WG). This WG is > > tasked with > > > > > providing the GNSO Council policy recommendations on: The limited > > > > > circumstances in which a base ASCII gTLD and the Latin script > > diacritic > > > > > version of the gTLD can be simultaneously delegated. The WG held its > > first > > > > > meeting > > > > > < > > https://icann82.sched.com/event/1vpYP/gnso-latin-script-diacritics-pdp-working-group > > > > > > > > on 08 March, 2025. > > > > > > > > > > > > > > > > > > > > In accordance with GNSO?s PDP requirements, we are seeking early > > written > > > > > input on the topic from each Supporting Organization, Advisory > > Committee, > > > > > and GNSO?s Stakeholder Group / Constituency. Each group has been > > invited to > > > > > participate in the PDP. Kindly note that the written input is > > completely > > > > > voluntary. > > > > > > > > > > > > > > > > > > > > In order to ensure that the WG receives your input in a timely > > manner and > > > > > that your input is incorporated into a summary document for the WG?s > > > > > consideration, we are requesting a response *no later than 24 April > > 2025* > > > > > *.* Input received after this date may be introduced into the > > discussion > > > > > separately by your representatives, by ICANN support staff, or by me > > as the > > > > > relevant topic is discussed. > > > > > > > > > > > > > > > > > > > > The WG?s scope of work is defined through a series of questions > > presented > > > > > in the WG?s Charter. The list of questions and key issues to consider > > > > > soliciting community input are attached for your convenience. To the > > extent > > > > > possible, you are requested to write your responses to the individual > > > > > questions in the attached document and return via email to the GNSO > > > > > Secretariat *gnso-secs at icann.org *. It is not > > > > > necessary to answer every question, and you are also welcome to > > provide any > > > > > other input and/or background information that you deem helpful to > > the > > > > > deliberations. > > > > > > > > > > > > > > > > > > > > As with all GNSO PDPs, there will be additional opportunities for > > > > > community input as the work progresses. > > > > > > > > > > > > > > > > > > > > Thank you very much and we look forward to receiving your input. > > > > > > > > > > > > > > > > > > > > On behalf of the LD PDP WG, > > > > > > > > > > Michael Bauland (LD PDP WG Chair) > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Tapani Tarvainen > > > _______________________________________________ > > > NCSG-PC mailing list > > > NCSG-PC at lists.ncsg.is > > > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > > > > -- > > Tapani Tarvainen > > _______________________________________________ > > NCSG-PC mailing list > > NCSG-PC at lists.ncsg.is > > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > > -- Tapani Tarvainen From rafik.dammak at gmail.com Fri May 2 14:42:27 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Fri, 2 May 2025 20:42:27 +0900 Subject: [NCSG-PC] Topics for joint meeting with ALAC In-Reply-To: <78415269-be5a-4e57-981e-82b7cb75abc1@KathyKleiman.com> References: <78415269-be5a-4e57-981e-82b7cb75abc1@KathyKleiman.com> Message-ID: Thanks Kathy for suggestions. looking forward to hearing from PC members if there are other topics. Rafik Le jeu. 1 mai 2025 ? 04:31, Kathy Kleiman a ?crit : > Independent reviews, Applicant Support, and similar issues that received > a lot of interest at our meeting in Seattle. > > On 4/30/2025 8:09 AM, Rafik Dammak wrote: > > Hi all, > > > > ALAC reached out asking about topics we want to discuss with them. > > Please share your suggestion and/or if you want to volunteer to lead > > the topic. > > > > Best, > > > > Rafik > > > > _______________________________________________ > > NCSG-PC mailing list > > NCSG-PC at lists.ncsg.is > > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From farzaneh.badii at gmail.com Fri May 2 14:58:42 2025 From: farzaneh.badii at gmail.com (farzaneh badii) Date: Fri, 2 May 2025 07:58:42 -0400 Subject: [NCSG-PC] Topics for joint meeting with ALAC In-Reply-To: References: <78415269-be5a-4e57-981e-82b7cb75abc1@KathyKleiman.com> Message-ID: Hi Rafik Michaela and I might have a very rough draft of the guidelines for DNS Abuse and HRIA. But I don?t know if we have a draft to share by then thats why I didn?t suggest it. Maybe have a general NCSG and Alac policy positions? Farzaneh On Fri, May 2, 2025 at 7:42?AM Rafik Dammak wrote: > Thanks Kathy for suggestions. looking forward to hearing from PC members > if there are other topics. > > Rafik > > Le jeu. 1 mai 2025 ? 04:31, Kathy Kleiman a > ?crit : > >> Independent reviews, Applicant Support, and similar issues that received >> a lot of interest at our meeting in Seattle. >> >> On 4/30/2025 8:09 AM, Rafik Dammak wrote: >> > Hi all, >> > >> > ALAC reached out asking about topics we want to discuss with them. >> > Please share your suggestion and/or if you want to volunteer to lead >> > the topic. >> > >> > Best, >> > >> > Rafik >> > >> > _______________________________________________ >> > NCSG-PC mailing list >> > NCSG-PC at lists.ncsg.is >> > https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From farzaneh.badii at gmail.com Sat May 3 18:53:42 2025 From: farzaneh.badii at gmail.com (farzaneh badii) Date: Sat, 3 May 2025 11:53:42 -0400 Subject: [NCSG-PC] Human Rights checklist, Transfer Policy Review In-Reply-To: References: Message-ID: Hi everyone, We will submit this impact assessment to the Council Leadership and perhaps can discuss it with the council during the next council meeting. Best regards, Farzaneh On Mon, Apr 21, 2025 at 4:21?AM farzaneh badii wrote: > Hi all, > > As we reported here, we asked the GNSO council to approve undertaking a > Human Rights checklist on Transfer Review Policy recommendations. I > volunteered to do the first iterative version. Please find the document > here: > https://docs.google.com/document/d/1aQetWyuO0S_0FD0-cFlAFz4cm0km5bywoC7JYtcq7FU/edit?usp=sharing > > Please comment and discuss the method here and then we can agree on > sending it to the council in consultation with Roger (the chair of TPR) > > Best regards > > Farzaneh > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Mon May 5 07:45:23 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Mon, 5 May 2025 13:45:23 +0900 Subject: [NCSG-PC] Topics for joint meeting with ALAC In-Reply-To: References: <78415269-be5a-4e57-981e-82b7cb75abc1@KathyKleiman.com> Message-ID: Thanks Farzaneh. Do you mean discussing with them about specific positions?if we have a list we can proposa that as agenda with reviews and applicant support. Rafik On Fri, May 2, 2025, 20:58 farzaneh badii wrote: > Hi > > > Michaela and I might have a very rough draft of the guidelines for DNS > Abuse and HRIA. But I don?t know if we have a draft to share by then thats > why I didn?t suggest it. Maybe have a general NCSG and Alac policy > positions? > > Farzaneh > > > On Fri, May 2, 2025 at 7:42?AM Rafik Dammak > wrote: > >> Thanks Kathy for suggestions. looking forward to hearing from PC members >> if there are other topics. >> >> Rafik >> >> Le jeu. 1 mai 2025 ? 04:31, Kathy Kleiman a >> ?crit : >> >>> Independent reviews, Applicant Support, and similar issues that received >>> a lot of interest at our meeting in Seattle. >>> >>> On 4/30/2025 8:09 AM, Rafik Dammak wrote: >>> > Hi all, >>> > >>> > ALAC reached out asking about topics we want to discuss with them. >>> > Please share your suggestion and/or if you want to volunteer to lead >>> > the topic. >>> > >>> > Best, >>> > >>> > Rafik >>> > >>> > _______________________________________________ >>> > NCSG-PC mailing list >>> > NCSG-PC at lists.ncsg.is >>> > https://lists.ncsg.is/mailman/listinfo/ncsg-pc >>> _______________________________________________ >>> NCSG-PC mailing list >>> NCSG-PC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >>> >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Wed May 7 10:34:12 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Wed, 7 May 2025 16:34:12 +0900 Subject: [NCSG-PC] NCSG rep to Planning Prioritization Group In-Reply-To: References: Message-ID: Hi all, Any comments on this? Are we ok with keeping the representatives in the prioritization group? Rafik Le jeu. 1 mai 2025 ? 06:49, Rafik Dammak a ?crit : > hi all, > > Amin as secondary member in the community planning prioritization group > informed me that the group is confirming the membership for FY27: > > Dear Planning Prioritization Group (PPG) members, >> >> We would like to thank you again for being a member of the Community >> Planning Prioritization Group. >> >> During the development of the Draft FY2630 Operating Plan and FY26 >> Budget, there were no new community recommendation activities to >> prioritize. Drafts of these plans were published for Public Comment in >> December 2024. Please see the publication of the Draft FY26*?*30 >> Operating Plan and Draft FY26 Budget here >> >> . >> >> >> *Action to Confirm Members:*As there were not any activities to >> prioritize for FY26, we are proposing that each PPG member continue to >> serve the group for FY27. >> Please confirm this approach with your SO/AC leadership. If there are any >> changes to the primary and secondary members, please email the Planning >> team by 6 May 2025. >> If there are no objections or requests for changes by 6 May 2025, we will >> convene the FY27 Planning Prioritization process with the current members. >> The process will involve meetings starting in late May 2025. >> >> For more information and the current members please see the Planning >> Prioritization Framework V4 >> and >> Community webpage here >> >> . >> >> >> Thank you, >> ICANN org Planning" > > > Currently Peter and Amin are representing NCSG there . so the action here > is to confirm them or if we need to replace any. Amin expressed interest to > continue as a secondary or primary member. > > The deadline to respond to the group is the 6th May. > > Best, > > Rafik > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From compsoftnet at gmail.com Wed May 7 15:22:09 2025 From: compsoftnet at gmail.com (Akinremi Peter Taiwo) Date: Wed, 7 May 2025 08:22:09 -0400 Subject: [NCSG-PC] NCSG rep to Planning Prioritization Group In-Reply-To: References: Message-ID: Hi Rafik and PC, Just to let you know that I am the rep for the NCSG on PPG. For FY26, there were no new community recommendations activities to prioritize, hence the group did not meet. Only a few exchanges on the email list on status. The PPG is planning to start the review for the FY27 activities as regards the prioritization of all board-approved org implementation work such as PDP, specific review recommendation, CCWG recommendations etc Kind regards Peter On Wed, May 7, 2025 at 8:00?AM Rafik Dammak wrote: > Hi all, > > Any comments on this? Are we ok with keeping the representatives in the > prioritization group? > > Rafik > > Le jeu. 1 mai 2025 ? 06:49, Rafik Dammak a > ?crit : > >> hi all, >> >> Amin as secondary member in the community planning prioritization group >> informed me that the group is confirming the membership for FY27: >> >> Dear Planning Prioritization Group (PPG) members, >>> >>> We would like to thank you again for being a member of the Community >>> Planning Prioritization Group. >>> >>> During the development of the Draft FY2630 Operating Plan and FY26 >>> Budget, there were no new community recommendation activities to >>> prioritize. Drafts of these plans were published for Public Comment in >>> December 2024. Please see the publication of the Draft FY26*?*30 >>> Operating Plan and Draft FY26 Budget here >>> >>> . >>> >>> >>> *Action to Confirm Members:*As there were not any activities to >>> prioritize for FY26, we are proposing that each PPG member continue to >>> serve the group for FY27. >>> Please confirm this approach with your SO/AC leadership. If there are >>> any changes to the primary and secondary members, please email the Planning >>> team by 6 May 2025. >>> If there are no objections or requests for changes by 6 May 2025, we >>> will convene the FY27 Planning Prioritization process with the current >>> members. The process will involve meetings starting in late May 2025. >>> >>> For more information and the current members please see the Planning >>> Prioritization Framework V4 >>> and >>> Community webpage here >>> >>> . >>> >>> >>> Thank you, >>> ICANN org Planning" >> >> >> Currently Peter and Amin are representing NCSG there . so the action here >> is to confirm them or if we need to replace any. Amin expressed interest to >> continue as a secondary or primary member. >> >> The deadline to respond to the group is the 6th May. >> >> Best, >> >> Rafik >> >> >> _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -- Best regards *Taiwo Peter Akinremi* ------ ------ ------- ------ ------ ------- ------ ------ ------- ------ ------ ------- ------ ------ *Policy Advisory | Data Governance and Privacy Consultant | Information Security & Cybersecurity | Certified Salesforce Administrator* *Phone*; +2348117714345, +2347063830177 *Skype*: akinremi.taiwo *Email:* compsoftnet at gmail.com, peterexecute at gmail.com ___________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Thu May 8 00:50:21 2025 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Thu, 8 May 2025 07:50:21 +1000 Subject: [NCSG-PC] Fwd: [council] Discussion Paper on Mechanism to Address EPDP-IDNs Phase 1 Recommendation 3.17 In-Reply-To: <1BB44931-E97E-41F6-A5E6-5BAB99434A0F@icann.org> References: <1BB44931-E97E-41F6-A5E6-5BAB99434A0F@icann.org> Message-ID: Remain blessed, Tomslin ---------- Forwarded message --------- From: Steve Chan via council Date: Sat, 3 May 2025, 03:59 Subject: [council] Discussion Paper on Mechanism to Address EPDP-IDNs Phase 1 Recommendation 3.17 To: council at gnso.icann.org Dear Councilors, Pursuant to the Council?s April meeting, staff was tasked with providing a briefing document that helps evaluate several options on how to address the issues in implementing EPDP-IDNs Phase 1 Recommendation 3.17. Please find the proposed paper attached, which can be discussed during the Council?s May meeting (and on list of course). Best, Steve *Steven Chan* VP, Policy Development Support & GNSO Relations Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 Email: steve.chan at icann.org Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar _______________________________________________ council mailing list -- council at icann.org To unsubscribe send an email to council-leave at icann.org _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Discussion Paper About the Han script Single Character IDN EPDP Recommendation 3.17.pdf Type: application/pdf Size: 219530 bytes Desc: not available URL: From mesumbeslin at gmail.com Thu May 8 13:04:31 2025 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Thu, 8 May 2025 20:04:31 +1000 Subject: [NCSG-PC] Fwd: [council] Proposed Agenda | GNSO Council Meeting | Thursday, 15 May 2025 In-Reply-To: References: Message-ID: FYI Remain blessed, Tomslin ---------- Forwarded message --------- From: Devan Reed via council Date: Sat, 3 May 2025, 05:08 Subject: [council] Proposed Agenda | GNSO Council Meeting | Thursday, 15 May 2025 To: council at gnso.icann.org , liaison6c at icann.org < liaison6c at icann.org> Cc: GNSO-Secs Dear all, Please find below the agenda for the GNSO Council Meeting on 15 May 2025 at 05:00 UTC. This will be posted on the agenda wiki page shortly. Thank you. Kind regards, Devan Policy Team Supporting the GNSO *GNSO Council Agenda 15 May 2025* Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://icann-community.atlassian.net/wiki/x/0KefBg This agenda was established according to the GNSO Operating Procedures v3.5, updated on 15 March 2023. For convenience: - An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. - An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. GNSO Council meeting on Thursday, 15 May 2025 at 05:00 UTC: https://tinyurl.com/knke3w 22:00 Los Angeles(Wednesday); 01:00 Washington DC; 06:00 London; 07:00 Paris; 08:00 Moscow; 15:00 Melbourne *GNSO Council Meeting Remote Participation: https://icann.zoom.us/j/91048235847?pwd=bmEHjk0uYT3sR2DIoE0c0yw4HKbM6O.1 * Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ *Item 1: Administrative Matters (5 minutes)* 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes of the GNSO Council Meeting on 12 March 2025 were posted on 01 April 2025 Minutes of the GNSO Council Meeting on 10 April 2025 were posted on 24 April 2025 *Item 2: Opening Remarks / Review of Projects & Action List (5 minutes)* 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List and Action Item List. *Item 3: Consent Agenda (5 minutes)* - Aspirational Statement *Item 4: COUNCIL VOTE - Deferral of the Next Steps of Phase Two of the Review of All Rights Protection Mechanisms (RPMs) in All New gTLDs Policy Development Process (PDP)* *for an Additional Six Months (20 minutes)* The Review of All Rights Protection Mechanisms (RPMs) in All New gTLDs Policy Development Process (PDP) was chartered to be conducted in two phases: Phase One focused on a review of all the RPMs that were developed for the 2012 New gTLD Program, and Phase Two will focus on issues identified in respect of the Uniform Dispute Resolution Policy (UDRP). Following the ICANN Board?s approval of the Phase 1 recommendations in January 2022, the GNSO Council discussed delaying Phase Two of the RPMs PDP until the completion of key milestones for the Implementation Review Team, once launched. The Phase One IRT was launched in December 2022 with a projected end date of December 2024. During its meeting on 16 February 2023 , the GNSO Council agreed to defer next steps on the RPMs PDP Phase Two for 18 months. In October 2024, GNSO support staff advised the GNSO Council leadership of staff estimates that the implementation of RPMs Phase One would be delayed until the third quarter of 2025. In light of this, the Council voted to defer the next steps on Phase Two for an additional six months. Following the direction of the Councilors who reviewed the progress to date, the Council is voting to defer the consideration of next steps for Phase 2 for an additional six months. 4.1 - Introduction of Topic (Susan Payne, GNSO Councilor) 4.2 - Council Vote (voting threshold: simple majority) 4.3 - Next Steps *Item 5: COUNCIL DISCUSSION - Han Script Character gTLDs (Recommendation 3.17) (20 minutes) * The New gTLD Subsequent Procedures (SubPro) PDP provided Recommendation 25.4 (approved by the ICANN Board) to allow single character gTLDs for ideographic scripts in the next round, *provided that they do not introduce confusion risks that rise above commonplace similarities.* The IDNs EPDP Phase 1 Final Report put forth important additional detail and limitations on 25.4, prescribing that the single character gTLDs *be limited to the Han script* and that *applications must not be accepted until relevant guidelines are developed and put in place by the Chinese, Japanese, and Korean (CJK) Generation Panels (GPs). *Alternatively, the IDN EPDP concluded that if the CJK GPs determine that additional guidelines beyond the RZ-LGR are not needed, then the single character applications should proceed. The matter was put out for public comment by the CJK Generation Panels. Although the CJK GPs stated that the work done in the Root Zone Label Generation Rules (RZ-LGRs ) sufficiently addresses the concerns around the risk of confusion for single character Han script gTLDs, the majority of the public comments on the CJK GPs? statements opposed moving forward. Some commenters from the Chinese community expressed concerns about the lack of alignment with China?s linguistic laws and regulations, the complexities of Chinese character ideographs, and end-user confusion due to multiple meanings of many single characters. One such comment received from a co-Chair of the CGP argues that the CGP should not be and was not involved in "risk of confusion" policy considerations related to single Han characters as TLDs. Many of the comments call for further community work prior to proceeding. Similar concerns were received through the public comment on the relevant draft AGB sections. This public comment was discussed with the Sub Pro IRT IDN Sub-Track which referred the matter to the main SubPro IRT. The main SubPro IRT was asked by ICANN staff whether Recommendation 25.4 should be modified as not implementable or whether the issue should be reviewed with Council for possible further work. It was agreed that the Liaisons should raise this with Council for direction on next steps. A background document prepared by Lars Hoffmann was shared with the Council on December 9. The Council Liaisons to the IRT suggesting referring the issue to a GNSO Guidance Process (GGP) to determine the guidance necessary to allow Han single characters to proceed, with an acknowledgement that the GGP could well determine that Recommendation 25.4 and IDN EPDP recommendation 3.17 as approved may not be implementable. Due to time constraints, and the fact that both the SubPro and IDNs recommendations were conditional, the Liaisons believe that the recommended GGP process should not hold up the next round. During Council deliberations, some Councilors suggested an Expert Working Group (EWG), as an alternative to the GGP. Staff provided an update to the Council during its April meeting where an additional mechanism was identified - the External Expert Advice (EEA) process as captured in Article 13 of the ICANN Bylaws. Following the Council?s April meeting, GNSO support staff provided an analysis of the potential options to address this issue, the GGP,the EWG, and the EEA. Here, the Council will discuss the next steps for Han Script Character gTLDs. 5.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 5.2 - Council Discussion 5.3 - Next Steps *Item 6: COUNCIL DISCUSSION - Council Alignment on the Future of Reviews (30 minutes)* ICANN created Specific Reviews in 2009 as a way to measure how it was meeting its commitments in four specific areas: Accountability and Transparency; Security, Stability, and Resiliency of the Domain Name System; Registration Directory Service; and Competition, Consumer Trust, and Consumer Choice. These reviews were incorporated into ICANN's Bylaws in 2016. Specific Reviews are led by community review teams and operate according to Section 4.6 of the ICANN Bylaws and the Operating Standards for Specific Reviews. Upon completion of a review, the Board assesses the results and considers recommendations accordingly. With exception of the Competition, Consumer Trust and Consumer Choice review that is conducted ?After a New gTLD Round has been in operation for one year?, Specific Reviews are conducted ?no less frequently than every five years?, measured from the date the previous review effort was convened. The Accountability and Transparency Review Team 3 (ATRT3) recommended the establishment of a new Specific Review, the Holistic Review, to examine the continuous improvement, effectiveness, and accountability of the ICANN community structures as well as the collaboration among them. A Pilot Holistic Review Team was convened to develop the guidelines and methodologies for the future Holistic Review, recommended by the ATRT3. Following an introduction of the topic, the Council will discuss the potential options going forward, including: - Status Quo: Continue on the current path, kick off ATRT4 and bifurcate out the Pilot Holistic Review (structural review) and the Continuing Improvement process. - Change Option 1: Repurpose ATRT4 to have it undertake the structural review, and as a result wind down the Pilot Holistic Review (with the Continuing Improvement process independent and functioning). - Change Option 2: Suspend all reviews and kick off a Review of Reviews to determine what reviews are necessary at this time (including a structural review). Here, the Council will consider these options and determine which, if any, is most supported by councilors. 6.1 - Introduction of Topic (Paul McGrady, GNSO Councilor) 6.2 - Council Discussion 6.3 - Next Steps *Item 7: COUNCIL UPDATE: Subsequent Procedures Implementation Review Team on Recommendation 36.4 (20 minutes)* On 16 March 2023, the ICANN Board adopted , et al., Recommendation 36.4 of the Subsequent Procedures PDP. Recommendation 36.4 provides: ICANN must add a contractual provision stating that the registry operator will not engage in fraudulent or deceptive practices. In the event that ICANN receives an order from a court that a registry has engaged in fraudulent or deceptive practices, ICANN may issue a notice of breach for such practices and allow the registry to cure such breach in accordance with the Registry Agreement. Further, in the event that there is a credible allegation by any third party of fraudulent or deceptive practices, other than as set forth in above, ICANN may, at its discretion, either commence dispute resolution actions under the Registry Agreement (Currently Article 5 of the Registry Agreement), or appoint a panel under the PICDRP. For the purposes of a credible claim of fraudulent or deceptive practices the reporter (as defined by the PICDRP) must only specifically state the grounds of the alleged non-compliance, but not that it personally has been harmed as a result of the registry operator?s act or omission. Here, the Council liaisons to the SubPro Implementation Review Team would like to discuss concerns regarding the proposed implementation of Recommendation 36.4. 7.1 - Introduction of Topic (Anne Aikman-Scalese and Susan Payne, Council Liaisons to SubPro IRT) 7.2 - Council Discussion 7.3 - Next Steps *Item 8: Any Other Business (15 minutes)* 8.1 - ICANN83 Planning 8.2 - ccNSO and GAC Liaison updates 8.3 - Whois Implementation Advisory Group update 8.4 - Registration Data Request Service (RDRS) Standing Committee Report - open question of public comment 8.5 - Chair update _______________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/sites/default/files/file/field-file-attach/op-procedures-15mar23-en.pdf *References for Coordinated Universal Time of 21:00 UTC* Local time between March and November in the NORTHERN hemisphere See https://www.timeanddate.com/time/change/ for Dates for Daylight Saving Time and Clock Changes ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 22:00 (Wednesday) San Jos?, Costa Rica (CST) UTC-6 23:00 (Wednesday) New York/Washington DC, USA (EDT) UTC-4 01:00 Buenos Aires, Argentina (ART) UTC-3 02:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 06:00 Paris, France (CEST) UTC+2 07:00 Moscow, Russia (MSK) UTC+3 08:00 Singapore (SGT) UTC+8 13:00 Melbourne, Australia (AEST) UTC+10 15:00 ---------------------------------------------------------------------- For other places see http://www.timeanddate.com and https://tinyurl.com/knke3w _______________________________________________ council mailing list -- council at icann.org To unsubscribe send an email to council-leave at icann.org _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Thu May 8 15:40:38 2025 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Thu, 8 May 2025 22:40:38 +1000 Subject: [NCSG-PC] Fwd: [council] Request for Input: Public Comment on RDRS Standing Committee Report In-Reply-To: <72cec8e2fcbb40988d81b3d6c67c6f3c@amazon.com> References: <72cec8e2fcbb40988d81b3d6c67c6f3c@amazon.com> Message-ID: FYI Remain blessed, Tomslin ---------- Forwarded message --------- From: DiBiase, Gregory via council Date: Tue, 22 Apr 2025 at 02:45 Subject: [council] Request for Input: Public Comment on RDRS Standing Committee Report To: Council at icann.org Dear Councilors, Following the recent update on the work of the Standing Committee (SC) on the Registration Data Request Service (RDRS), a procedural question was brought before Council: whether there should be a public comment on the RDRS SC Report. *Background:* The SC is nearing completion of its final findings report, which is structured around its assignment from the GNSO Council, which includes information on the usage trends, system enhancements, lessons learned (particularly in light of SSAD recommendations), and suggestions to Council as it approaches its dialogue with the ICANN Board. As described in its Charter , the SC should consult with the GNSO Council on whether this report, which is intended as a factual account of their work, not a policy document, should be published for public comment prior to the submission of the report to the Council? When considering this question, please note that all GNSO SGs are represented in the Standing Committee. In addition, the RDRS Sc benefits from active participation by representatives from GAC, SSAC and ALAC, and it has already received community input during ICANN public sessions. While the Council always retains the option to initiate its public comment period prior to engaging with the ICANN Board, the SC would appreciate clarity whether it should initiate a public comment at this stage - prior to submitting their report to Council. Please consult with your stakeholder groups and be prepared to provide feedback at the upcoming Council meeting in May. Your input will help inform how the Standing Committee proceeds as it finalizes its work. Thanks, Greg _______________________________________________ council mailing list -- council at icann.org To unsubscribe send an email to council-leave at icann.org _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. -------------- next part -------------- An HTML attachment was scrubbed... URL: From farzaneh.badii at gmail.com Thu May 8 15:49:20 2025 From: farzaneh.badii at gmail.com (farzaneh badii) Date: Thu, 8 May 2025 08:49:20 -0400 Subject: [NCSG-PC] Fwd: [council] Request for Input: Public Comment on RDRS Standing Committee Report In-Reply-To: References: <72cec8e2fcbb40988d81b3d6c67c6f3c@amazon.com> Message-ID: Thanks Tomslin I raised this with the PC. I suggest we agree to public comment but ask the announcement to be very precise about rdrs what it does and it doesn?t do. Farzaneh On Thu, May 8, 2025 at 8:40?AM Tomslin Samme-Nlar wrote: > FYI > > Remain blessed, > Tomslin > > > ---------- Forwarded message --------- > From: DiBiase, Gregory via council > Date: Tue, 22 Apr 2025 at 02:45 > Subject: [council] Request for Input: Public Comment on RDRS Standing > Committee Report > To: Council at icann.org > > > Dear Councilors, > > > > Following the recent update > on > the work of the Standing Committee (SC) on the Registration Data Request > Service (RDRS), a procedural question was brought before Council: whether > there should be a public comment on the RDRS SC Report. > > > > *Background:* > > > > The SC is nearing completion of its final findings report, which is > structured around its assignment > > from the GNSO Council, which includes information on the usage trends, > system enhancements, lessons learned (particularly in light of SSAD > recommendations), and suggestions to Council as it approaches its dialogue > with the ICANN Board. > > > > As described in its Charter > , > the SC should consult with the GNSO Council on whether this report, which > is intended as a factual account of their work, not a policy document, > should be published for public comment prior to the submission of the > report to the Council? > > > > When considering this question, please note that all GNSO SGs are > represented > in > the Standing Committee. In addition, the RDRS Sc benefits from active > participation by representatives from GAC, SSAC and ALAC, and it has > already received community input during ICANN public sessions. > > > > While the Council always retains the option to initiate its public comment > period prior to engaging with the ICANN Board, the SC would appreciate > clarity whether it should initiate a public comment at this stage - prior > to submitting their report to Council. > > > > Please consult with your stakeholder groups and be prepared to provide > feedback at the upcoming Council meeting in May. Your input will help > inform how the Standing Committee proceeds as it finalizes its work. > > > > > > Thanks, > > Greg > > > _______________________________________________ > council mailing list -- council at icann.org > To unsubscribe send an email to council-leave at icann.org > > _______________________________________________ > By submitting your personal data, you consent to the processing of your > personal data for purposes of subscribing to this mailing list accordance > with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and > the website Terms of Service (https://www.icann.org/privacy/tos). You can > visit the Mailman link above to change your membership status or > configuration, including unsubscribing, setting digest-style delivery or > disabling delivery altogether (e.g., for a vacation), and so on. > _______________________________________________ > 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 compsoftnet at gmail.com Thu May 8 16:28:13 2025 From: compsoftnet at gmail.com (Akinremi Peter Taiwo) Date: Thu, 8 May 2025 09:28:13 -0400 Subject: [NCSG-PC] Council: Vice Chair Position Message-ID: Dear Rafik, and PC, In light of the current council leadership outlook, I would like to put myself forward for the vice chair position. If other colleagues agree to this, I believe it is good for NCSG to continue to serve in this role. -- Best regards *Taiwo Peter Akinremi* ------ ------ ------- ------ ------ ------- ------ ------ ------- ------ ------ ------- ------ ------ *Policy Advisory | Data Governance and Privacy Consultant | Information Security & Cybersecurity | Certified Salesforce Administrator* *Phone*; +2348117714345, +2347063830177 *Skype*: akinremi.taiwo *Email:* compsoftnet at gmail.com, peterexecute at gmail.com ___________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From compsoftnet at gmail.com Thu May 8 16:32:30 2025 From: compsoftnet at gmail.com (Akinremi Peter Taiwo) Date: Thu, 8 May 2025 09:32:30 -0400 Subject: [NCSG-PC] Fwd: [council] Request for Input: Public Comment on RDRS Standing Committee Report In-Reply-To: References: <72cec8e2fcbb40988d81b3d6c67c6f3c@amazon.com> Message-ID: Thanks Tomslin and Farzaneh. It would be good to get a community feel on the RDRS SC report before it comes to the council. Kind regards On Thu, May 8, 2025 at 8:49?AM farzaneh badii wrote: > Thanks Tomslin > > I raised this with the PC. I suggest we agree to public comment but ask > the announcement to be very precise about rdrs what it does and it doesn?t > do. > > Farzaneh > > > On Thu, May 8, 2025 at 8:40?AM Tomslin Samme-Nlar > wrote: > >> FYI >> >> Remain blessed, >> Tomslin >> >> >> ---------- Forwarded message --------- >> From: DiBiase, Gregory via council >> Date: Tue, 22 Apr 2025 at 02:45 >> Subject: [council] Request for Input: Public Comment on RDRS Standing >> Committee Report >> To: Council at icann.org >> >> >> Dear Councilors, >> >> >> >> Following the recent update >> on >> the work of the Standing Committee (SC) on the Registration Data Request >> Service (RDRS), a procedural question was brought before Council: whether >> there should be a public comment on the RDRS SC Report. >> >> >> >> *Background:* >> >> >> >> The SC is nearing completion of its final findings report, which is >> structured around its assignment >> >> from the GNSO Council, which includes information on the usage trends, >> system enhancements, lessons learned (particularly in light of SSAD >> recommendations), and suggestions to Council as it approaches its dialogue >> with the ICANN Board. >> >> >> >> As described in its Charter >> , >> the SC should consult with the GNSO Council on whether this report, which >> is intended as a factual account of their work, not a policy document, >> should be published for public comment prior to the submission of the >> report to the Council? >> >> >> >> When considering this question, please note that all GNSO SGs are >> represented >> in >> the Standing Committee. In addition, the RDRS Sc benefits from active >> participation by representatives from GAC, SSAC and ALAC, and it has >> already received community input during ICANN public sessions. >> >> >> >> While the Council always retains the option to initiate its public >> comment period prior to engaging with the ICANN Board, the SC would >> appreciate clarity whether it should initiate a public comment at this >> stage - prior to submitting their report to Council. >> >> >> >> Please consult with your stakeholder groups and be prepared to provide >> feedback at the upcoming Council meeting in May. Your input will help >> inform how the Standing Committee proceeds as it finalizes its work. >> >> >> >> >> >> Thanks, >> >> Greg >> >> >> _______________________________________________ >> council mailing list -- council at icann.org >> To unsubscribe send an email to council-leave at icann.org >> >> _______________________________________________ >> By submitting your personal data, you consent to the processing of your >> personal data for purposes of subscribing to this mailing list accordance >> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and >> the website Terms of Service (https://www.icann.org/privacy/tos). You >> can visit the Mailman link above to change your membership status or >> configuration, including unsubscribing, setting digest-style delivery or >> disabling delivery altogether (e.g., for a vacation), and so on. >> _______________________________________________ >> 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 > -- Best regards *Taiwo Peter Akinremi* ------ ------ ------- ------ ------ ------- ------ ------ ------- ------ ------ ------- ------ ------ *Policy Advisory | Data Governance and Privacy Consultant | Information Security & Cybersecurity | Certified Salesforce Administrator* *Phone*; +2348117714345, +2347063830177 *Skype*: akinremi.taiwo *Email:* compsoftnet at gmail.com, peterexecute at gmail.com ___________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Fri May 9 11:50:01 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Fri, 9 May 2025 17:50:01 +0900 Subject: [NCSG-PC] Council: Vice Chair Position In-Reply-To: References: Message-ID: Thanks Peter. If there is no objection, I will share that with CSG in due time. Rafik Le jeu. 8 mai 2025 ? 22:28, Akinremi Peter Taiwo a ?crit : > Dear Rafik, and PC, > > In light of the current council leadership outlook, I would like to put > myself forward for the vice chair position. If other colleagues agree to > this, I believe it is good for NCSG to continue to serve in this role. > > -- > Best regards > > *Taiwo Peter Akinremi* > ------ ------ ------- ------ ------ ------- ------ ------ ------- ------ > ------ ------- ------ ------ > *Policy Advisory | Data Governance and Privacy Consultant | Information > Security & Cybersecurity | Certified Salesforce Administrator* > *Phone*; +2348117714345, +2347063830177 *Skype*: akinremi.taiwo > *Email:* compsoftnet at gmail.com, peterexecute at gmail.com > ___________________________________________ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Fri May 9 11:51:02 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Fri, 9 May 2025 17:51:02 +0900 Subject: [NCSG-PC] NCSG rep to Planning Prioritization Group In-Reply-To: References: Message-ID: Hi Peter, as we didn't object, I think you and Amin will continue in the group Rafik Le mer. 7 mai 2025 ? 21:22, Akinremi Peter Taiwo a ?crit : > Hi Rafik and PC, > > Just to let you know that I am the rep for the NCSG on PPG. > > For FY26, there were no new community recommendations activities to > prioritize, hence the group did not meet. Only a few exchanges on the email > list on status. > > The PPG is planning to start the review for the FY27 activities as regards > the prioritization of all board-approved org implementation work such as > PDP, specific review recommendation, CCWG recommendations etc > > Kind regards > Peter > > > On Wed, May 7, 2025 at 8:00?AM Rafik Dammak > wrote: > >> Hi all, >> >> Any comments on this? Are we ok with keeping the representatives in the >> prioritization group? >> >> Rafik >> >> Le jeu. 1 mai 2025 ? 06:49, Rafik Dammak a >> ?crit : >> >>> hi all, >>> >>> Amin as secondary member in the community planning prioritization group >>> informed me that the group is confirming the membership for FY27: >>> >>> Dear Planning Prioritization Group (PPG) members, >>>> >>>> We would like to thank you again for being a member of the Community >>>> Planning Prioritization Group. >>>> >>>> During the development of the Draft FY2630 Operating Plan and FY26 >>>> Budget, there were no new community recommendation activities to >>>> prioritize. Drafts of these plans were published for Public Comment in >>>> December 2024. Please see the publication of the Draft FY26*?*30 >>>> Operating Plan and Draft FY26 Budget here >>>> >>>> . >>>> >>>> >>>> *Action to Confirm Members:*As there were not any activities to >>>> prioritize for FY26, we are proposing that each PPG member continue to >>>> serve the group for FY27. >>>> Please confirm this approach with your SO/AC leadership. If there are >>>> any changes to the primary and secondary members, please email the Planning >>>> team by 6 May 2025. >>>> If there are no objections or requests for changes by 6 May 2025, we >>>> will convene the FY27 Planning Prioritization process with the current >>>> members. The process will involve meetings starting in late May 2025. >>>> >>>> For more information and the current members please see the Planning >>>> Prioritization Framework V4 >>>> and >>>> Community webpage here >>>> >>>> . >>>> >>>> >>>> Thank you, >>>> ICANN org Planning" >>> >>> >>> Currently Peter and Amin are representing NCSG there . so the action >>> here is to confirm them or if we need to replace any. Amin expressed >>> interest to continue as a secondary or primary member. >>> >>> The deadline to respond to the group is the 6th May. >>> >>> Best, >>> >>> Rafik >>> >>> >>> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> > > > -- > Best regards > > *Taiwo Peter Akinremi* > ------ ------ ------- ------ ------ ------- ------ ------ ------- ------ > ------ ------- ------ ------ > *Policy Advisory | Data Governance and Privacy Consultant | Information > Security & Cybersecurity | Certified Salesforce Administrator* > *Phone*; +2348117714345, +2347063830177 *Skype*: akinremi.taiwo > *Email:* compsoftnet at gmail.com, peterexecute at gmail.com > ___________________________________________ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From compsoftnet at gmail.com Fri May 9 16:42:49 2025 From: compsoftnet at gmail.com (Akinremi Peter Taiwo) Date: Fri, 9 May 2025 09:42:49 -0400 Subject: [NCSG-PC] Council: Vice Chair Position In-Reply-To: References: Message-ID: Thank you Rafik Kind regards On Fri, May 9, 2025 at 4:50?AM Rafik Dammak wrote: > > Thanks Peter. > If there is no objection, I will share that with CSG in due time. > > Rafik > > > Le jeu. 8 mai 2025 ? 22:28, Akinremi Peter Taiwo > a ?crit : > >> Dear Rafik, and PC, >> >> In light of the current council leadership outlook, I would like to put >> myself forward for the vice chair position. If other colleagues agree to >> this, I believe it is good for NCSG to continue to serve in this role. >> >> -- >> Best regards >> >> *Taiwo Peter Akinremi* >> ------ ------ ------- ------ ------ ------- ------ ------ ------- ------ >> ------ ------- ------ ------ >> *Policy Advisory | Data Governance and Privacy Consultant | Information >> Security & Cybersecurity | Certified Salesforce Administrator* >> *Phone*; +2348117714345, +2347063830177 *Skype*: akinremi.taiwo >> *Email:* compsoftnet at gmail.com, peterexecute at gmail.com >> ___________________________________________ >> > -- Best regards *Taiwo Peter Akinremi* ------ ------ ------- ------ ------ ------- ------ ------ ------- ------ ------ ------- ------ ------ *Policy Advisory | Data Governance and Privacy Consultant | Information Security & Cybersecurity | Certified Salesforce Administrator* *Phone*; +2348117714345, +2347063830177 *Skype*: akinremi.taiwo *Email:* compsoftnet at gmail.com, peterexecute at gmail.com ___________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruna.mrtns at gmail.com Fri May 9 17:13:54 2025 From: bruna.mrtns at gmail.com (Bruna Martins dos Santos) Date: Fri, 9 May 2025 16:13:54 +0200 Subject: [NCSG-PC] Council: Vice Chair Position In-Reply-To: References: Message-ID: Thanks Rafik and Peter for Volunteering! It?s a +1 from me !! Bruna Santos Akinremi Peter Taiwo schrieb am Fr. 9. Mai 2025 um 15:43: > Thank you Rafik > > Kind regards > > On Fri, May 9, 2025 at 4:50?AM Rafik Dammak > wrote: > >> >> Thanks Peter. >> If there is no objection, I will share that with CSG in due time. >> >> Rafik >> >> >> Le jeu. 8 mai 2025 ? 22:28, Akinremi Peter Taiwo >> a ?crit : >> >>> Dear Rafik, and PC, >>> >>> In light of the current council leadership outlook, I would like to put >>> myself forward for the vice chair position. If other colleagues agree to >>> this, I believe it is good for NCSG to continue to serve in this role. >>> >>> -- >>> Best regards >>> >>> *Taiwo Peter Akinremi* >>> ------ ------ ------- ------ ------ ------- ------ ------ ------- ------ >>> ------ ------- ------ ------ >>> *Policy Advisory | Data Governance and Privacy Consultant | Information >>> Security & Cybersecurity | Certified Salesforce Administrator* >>> *Phone*; +2348117714345, +2347063830177 *Skype*: akinremi.taiwo >>> *Email:* compsoftnet at gmail.com, peterexecute at gmail.com >>> ___________________________________________ >>> >> > > -- > Best regards > > *Taiwo Peter Akinremi* > ------ ------ ------- ------ ------ ------- ------ ------ ------- ------ > ------ ------- ------ ------ > *Policy Advisory | Data Governance and Privacy Consultant | Information > Security & Cybersecurity | Certified Salesforce Administrator* > *Phone*; +2348117714345, +2347063830177 *Skype*: akinremi.taiwo > *Email:* compsoftnet at gmail.com, peterexecute at gmail.com > ___________________________________________ > _______________________________________________ > 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 rafik.dammak at gmail.com Fri May 9 17:22:50 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Fri, 9 May 2025 23:22:50 +0900 Subject: [NCSG-PC] NCPH meeting in Prague Message-ID: Hi all, I started discussion with the CSG lead about the agenda for the NCPH meeting in Prague. As initial topics, we have the board seat 14 and GNSO council chair and vice-chair elections. But we need additional topics. Let me know if you have any suggestions. Best, Rafik Virus-free.www.avg.com <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrea.glandon at icann.org Fri May 9 19:16:39 2025 From: andrea.glandon at icann.org (Andrea Glandon) Date: Fri, 9 May 2025 16:16:39 +0000 Subject: [NCSG-PC] [Ext] [NCSG-EC] Topics for joint meeting with ALAC In-Reply-To: References: Message-ID: <404951C3-4FDC-4BE8-AAF3-F12735F4CA96@icann.org> Hello all! Kind reminder to work on topics for the joint session with ALAC. At-Large staff is working on confirming the agenda. Thanks! Kind Regards, Andrea From: NCSG-EC on behalf of Rafik Dammak via NCSG-EC Reply-To: Rafik Dammak Date: Wednesday, April 30, 2025 at 07:09 To: ncsg-pc , NCSG EC Subject: [Ext] [NCSG-EC] Topics for joint meeting with ALAC Hi all, ALAC reached out asking about topics we want to discuss with them. Please share your suggestion and/or if you want to volunteer to lead the topic. Best, Rafik -------------- next part -------------- An HTML attachment was scrubbed... URL: From wisdom.dk at gmail.com Fri May 9 20:01:23 2025 From: wisdom.dk at gmail.com (Wisdom Donkor) Date: Fri, 9 May 2025 17:01:23 +0000 Subject: [NCSG-PC] Council: Vice Chair Position In-Reply-To: References: Message-ID: Plus 1 from me also. *Wisdom Donkor* (CASP+, CISM, CEH Certified,) President & CEO Africa Open Data and Internet Research Foundation (AODIRF) | Africa Geospatial Data and Internet Conference (AGDIC) P.O. Box CT 2439, Cantonments, Accra | www.aodirf.org / www. agdic.info Tel: +233 20 812 8851 Skype: wisdom_dk | Facebook: kwasi wisdom | Twitter: @wisdom_dk _______________________________________________________________________________________________________________________ ICANN GNSO Council Member | ICANN transfer policy review working group Member | Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) | UN IGF MAG Member | IGF Support Fund Association Executive Committee Member, World Bank Independent Consultant | AU AFIGF Member | Ghana OGP Advisory Committee member | GSS SDGs Advisory Committee Member ____________________________________________________________________________________________ Specialization: E-government Network Infrastructure and E-application, Internet Governance, Open Data policies platforms & Community Development, Cyber Security, Geospatial Technologies, Open Source Technologies, Domain Name Systems, Human Resource Planning and Development, Software Engineering, Event Planning & Management, On Fri, May 9, 2025 at 2:14?PM Bruna Martins dos Santos < bruna.mrtns at gmail.com> wrote: > Thanks Rafik and Peter for Volunteering! It?s a +1 from me !! > > Bruna Santos > > > Akinremi Peter Taiwo schrieb am Fr. 9. Mai 2025 > um 15:43: > >> Thank you Rafik >> >> Kind regards >> >> On Fri, May 9, 2025 at 4:50?AM Rafik Dammak >> wrote: >> >>> >>> Thanks Peter. >>> If there is no objection, I will share that with CSG in due time. >>> >>> Rafik >>> >>> >>> Le jeu. 8 mai 2025 ? 22:28, Akinremi Peter Taiwo >>> a ?crit : >>> >>>> Dear Rafik, and PC, >>>> >>>> In light of the current council leadership outlook, I would like to put >>>> myself forward for the vice chair position. If other colleagues agree to >>>> this, I believe it is good for NCSG to continue to serve in this role. >>>> >>>> -- >>>> Best regards >>>> >>>> *Taiwo Peter Akinremi* >>>> ------ ------ ------- ------ ------ ------- ------ ------ ------- ------ >>>> ------ ------- ------ ------ >>>> *Policy Advisory | Data Governance and Privacy Consultant | Information >>>> Security & Cybersecurity | Certified Salesforce Administrator* >>>> *Phone*; +2348117714345, +2347063830177 *Skype*: akinremi.taiwo >>>> *Email:* compsoftnet at gmail.com, peterexecute at gmail.com >>>> ___________________________________________ >>>> >>> >> >> -- >> Best regards >> >> *Taiwo Peter Akinremi* >> ------ ------ ------- ------ ------ ------- ------ ------ ------- ------ >> ------ ------- ------ ------ >> *Policy Advisory | Data Governance and Privacy Consultant | Information >> Security & Cybersecurity | Certified Salesforce Administrator* >> *Phone*; +2348117714345, +2347063830177 *Skype*: akinremi.taiwo >> *Email:* compsoftnet at gmail.com, peterexecute at gmail.com >> ___________________________________________ >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From emmanuelvitus at gmail.com Fri May 9 20:02:44 2025 From: emmanuelvitus at gmail.com (Emmanuel Vitus) Date: Fri, 9 May 2025 17:02:44 +0000 Subject: [NCSG-PC] Council: Vice Chair Position In-Reply-To: References: Message-ID: Peter has my support. Thanks. Le ven. 9 mai 2025 ? 17:02, Wisdom Donkor a ?crit : > Plus 1 from me also. > > *Wisdom Donkor* (CASP+, CISM, CEH Certified,) > President & CEO > Africa Open Data and Internet Research Foundation (AODIRF) | Africa > Geospatial Data and Internet Conference (AGDIC) > P.O. Box CT 2439, Cantonments, Accra | www.aodirf.org / www. > agdic.info > Tel: +233 20 812 8851 > Skype: wisdom_dk | Facebook: kwasi wisdom | Twitter: @wisdom_dk > > _______________________________________________________________________________________________________________________ > ICANN GNSO Council Member | ICANN transfer policy review working group > Member | Council Committee for Overseeing and Implementing Continuous > Improvement (CCOICI) | UN IGF MAG Member | IGF Support Fund Association > Executive Committee Member, World Bank Independent Consultant | AU AFIGF > Member | Ghana OGP Advisory Committee member | GSS SDGs Advisory Committee > Member > > ____________________________________________________________________________________________ > Specialization: > E-government Network Infrastructure and E-application, Internet > Governance, Open Data policies platforms & Community Development, Cyber > Security, Geospatial Technologies, Open Source Technologies, Domain Name > Systems, Human Resource Planning and Development, Software Engineering, > Event Planning & Management, > > > On Fri, May 9, 2025 at 2:14?PM Bruna Martins dos Santos < > bruna.mrtns at gmail.com> wrote: > >> Thanks Rafik and Peter for Volunteering! It?s a +1 from me !! >> >> Bruna Santos >> >> >> Akinremi Peter Taiwo schrieb am Fr. 9. Mai 2025 >> um 15:43: >> >>> Thank you Rafik >>> >>> Kind regards >>> >>> On Fri, May 9, 2025 at 4:50?AM Rafik Dammak >>> wrote: >>> >>>> >>>> Thanks Peter. >>>> If there is no objection, I will share that with CSG in due time. >>>> >>>> Rafik >>>> >>>> >>>> Le jeu. 8 mai 2025 ? 22:28, Akinremi Peter Taiwo >>>> a ?crit : >>>> >>>>> Dear Rafik, and PC, >>>>> >>>>> In light of the current council leadership outlook, I would like to >>>>> put myself forward for the vice chair position. If other colleagues agree >>>>> to this, I believe it is good for NCSG to continue to serve in this role. >>>>> >>>>> -- >>>>> Best regards >>>>> >>>>> *Taiwo Peter Akinremi* >>>>> ------ ------ ------- ------ ------ ------- ------ ------ ------- ------ >>>>> ------ ------- ------ ------ >>>>> *Policy Advisory | Data Governance and Privacy Consultant | >>>>> Information Security & Cybersecurity | Certified Salesforce Administrator* >>>>> *Phone*; +2348117714345, +2347063830177 *Skype*: akinremi.taiwo >>>>> *Email:* compsoftnet at gmail.com, peterexecute at gmail.com >>>>> ___________________________________________ >>>>> >>>> >>> >>> -- >>> Best regards >>> >>> *Taiwo Peter Akinremi* >>> ------ ------ ------- ------ ------ ------- ------ ------ ------- ------ >>> ------ ------- ------ ------ >>> *Policy Advisory | Data Governance and Privacy Consultant | Information >>> Security & Cybersecurity | Certified Salesforce Administrator* >>> *Phone*; +2348117714345, +2347063830177 *Skype*: akinremi.taiwo >>> *Email:* compsoftnet at gmail.com, peterexecute at gmail.com >>> ___________________________________________ >>> _______________________________________________ >>> NCSG-PC mailing list >>> NCSG-PC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >>> >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Sat May 10 02:51:24 2025 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Sat, 10 May 2025 09:51:24 +1000 Subject: [NCSG-PC] Council: Vice Chair Position In-Reply-To: References: Message-ID: No objection from me. Remain blessed, Tomslin On Fri, 9 May 2025, 18:50 Rafik Dammak, wrote: > > Thanks Peter. > If there is no objection, I will share that with CSG in due time. > > Rafik > > > Le jeu. 8 mai 2025 ? 22:28, Akinremi Peter Taiwo > a ?crit : > >> Dear Rafik, and PC, >> >> In light of the current council leadership outlook, I would like to put >> myself forward for the vice chair position. If other colleagues agree to >> this, I believe it is good for NCSG to continue to serve in this role. >> >> -- >> Best regards >> >> *Taiwo Peter Akinremi* >> ------ ------ ------- ------ ------ ------- ------ ------ ------- ------ >> ------ ------- ------ ------ >> *Policy Advisory | Data Governance and Privacy Consultant | Information >> Security & Cybersecurity | Certified Salesforce Administrator* >> *Phone*; +2348117714345, +2347063830177 *Skype*: akinremi.taiwo >> *Email:* compsoftnet at gmail.com, peterexecute at gmail.com >> ___________________________________________ >> > _______________________________________________ > 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 rafik.dammak at gmail.com Sat May 10 07:13:58 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Sat, 10 May 2025 13:13:58 +0900 Subject: [NCSG-PC] Kickoff discussion about GNSO council chair and vice-chair In-Reply-To: References: Message-ID: Hi all, CSG has for now 2 candidates for GNSO chair nomination: Susan Payne and Damon Ashcraft. I think our first action would be to interview them after the Prague meeting (and when we get the new councillors elected). We should refer to what we agreed as a process previously. The deadline for nomination is the 29th September. Best, Rafik Le mer. 30 avr. 2025 ? 21:13, Rafik Dammak a ?crit : > Hi all, > > Mason from CSG reached out to initiate discussion about GNSO council chair > election and vice chair appointment. CSG might propose a candidate for GNSO > chair and for they would propose Lawrence for vice chair position. > We need to confirm if we have or not a candidate from our side. For their > candidate which would need nomination from NCPH they will have to be > interviewed by us and vetted. > I will also check in CPH side about their plan too. > I will discuss with Mason, feel free to share your thoughts about the > direction to take. > > Best, > > Rafik > Virus-free.www.avg.com <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Sun May 11 19:37:42 2025 From: julf at Julf.com (Johan Helsingius) Date: Sun, 11 May 2025 18:37:42 +0200 Subject: [NCSG-PC] Meeting Invitation | NCSG Policy Call | Monday, 12 May 2025 at 11:30 UTC In-Reply-To: <73DB82B9-8910-4282-83E3-0506E5F34329@icann.org> References: <73DB82B9-8910-4282-83E3-0506E5F34329@icann.org> Message-ID: <030f9523-80dd-437a-9d10-c0ec33f31690@Julf.com> Please accept my apologies, as I will be on a flight to RIPE90. Julf On 22/04/2025 20:19, Andrea Glandon wrote: > Dear all, > > *The next NCSG Policy Committee call will be held on Monday, 12 May 2025 > at 11:30 UTC.*Check your time zone here worldclock/fixedtime.html? > msg=NCSG+Policy+Committee&iso=20250512T1130&p1=1440&ah=1&am=30>. > > Join details are attached and noted below for your convenience. > > Join Zoom Meeting: *https://icann.zoom.us/j/98878189584? > pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09 [icann.zoom.us]* urldefense.com/v3/__https:/icann.zoom.us/j/98878189584? > pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09__;!!PtGJab4! > 89jS1o75blcYjx01179eBM7Q0Er-lA5anQXpQIKL7VjWzU6Yy- > h2o6sS4YvHIbDhtF0xH2toJXUpOFNQkhQTqGy3yi_7OQBd$> > > Meeting ID: 988 7818 9584 > > Passcode: i!y7.qx+11 > > One tap mobile > > +16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose) > > +12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma) > > PHONE ONLY DETAILS: > > Find your local number: https://icann.zoom.us/u/ayKmeftWg > [icann.zoom.us] ayKmeftWg__;!!PtGJab4!89jS1o75blcYjx01179eBM7Q0Er-lA5anQXpQIKL7VjWzU6Yy- > h2o6sS4YvHIbDhtF0xH2toJXUpOFNQkhQTqGy3yig2JxoC$> > > Meeting ID: 988 7818 9584 > > Phone only Passcode: 7740925615 > > Best, > > Andrea & Dan > From kathy at dnrc.tech Mon May 12 19:23:44 2025 From: kathy at dnrc.tech (Kathy Kleiman) Date: Mon, 12 May 2025 12:23:44 -0400 Subject: [NCSG-PC] Fwd: Fwd: [council] Council Agenda Item 7: Implementation of SubPro Rec 36.4 - Deep concerns In-Reply-To: References: Message-ID: <8edcc1ec-0f28-47c7-a9c3-31e9e58e276d@dnrc.tech> Hi Tomslin and all of our Counselors, Tx to Tomslin for sharing. As discussed in the PC meeting earlier, the two SubPro liaisons in this case are both members of the IPC (although Anne is also a Nomcom appointee to Council). They are good, but they have very clear views, as does the IPC. *Here's some more background: *For the IPC, fraud is one of a series of content issues they think registries and registrars should handle: For example: => [ICANN Registry Agreement ] Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting Registered Name Holders from *distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law, *and providing (consistent with applicable law and any related procedures) consequences for such activities including suspension of the domain name." [I added the bold] Certainly the SubPro WG majority wanted New gTLD registries /to do all of this enforcement actively -- and yet_trademark and copyright infringement and alleged fraudulent and deceptive or counterfeiting issues are *content and contrary to ICANN Bylaws - we don't regulate content in ICANN *(as the June 8th, 2024, ICANN Board Resolution in Kigali confirmed)._/ But some leading members of the SubPro Implementation Review Team don't like this June 8th resolution (and don't remember we told that the SubPro WG recommendations on this topic were contrary to ICANN Bylaws).? >From they perspective:? if the SubPro WG recommended it, they want it done just that way. But ICANN cannot look at fraudulent content on a webpage - because fraudulent content is content (for example, I post that my washing detergent is better than yours - my Tide and better than your Arm& Hammer.? In the US, comparative advertising is legal; in Germany, it is not.? Regardless, Arm & Hammer wants to take down my website down saying that my claims (as Tide) are fraudulent... and wants the Registr/y to enforce it, but ICANN cannot regulate content. This is a legal issue outside of ICANN. / Appropriately (IMHO), ICANN Org (recently in the SubPro IRT) countered and offered the IRT an alternative that I consider reasonable:? ICANN Org wrote and said that "fraud" within ICANN's mission is how a Registry manages its registry business. For example (and these are my examples): if a Registry says that it is putting new domain names into the root, and instead resells them via another registry (charging twice), that would be fraudulent. /But if someone says that a Registry is engaged in fraud of this sort -- how does ICANN know? /ICANN Org now says that the person/company/group should go to court for a finding of fraud against the Registry - and then bring it to ICANN.? Or go to a government consumer protection agency - and bring their finding to ICANN. /Then ICANN will know what is illegal and fraudulent from an expert tribunal (within the scope of the Bylaws) and will act.? That seems fair and right to me. / But if anyone (an IP attorney, etc) can bring a PICDRP action against any registry at any time in the PICDRP, then we will find the definitions of fraud expanding to content - right way -- because so many see DNS abuse as one continuum (although NCSG does not) and including -- *trademark of copyright infringement, fraudulent or deceptive practices, counterfeiting, etc. * * * As our only actived participant in the SubPro IRT at this time (and I've attended the last 30 meetings), I share: I agree with what ICANN Org recommended and disagree with the Liaisons of the Implementation Review Team. Best and tx, Kathy -------- Forwarded Message -------- Subject: Fwd: [council] Council Agenda Item 7: Implementation of SubPro Rec 36.4 Date: Mon, 12 May 2025 23:18:59 +1000 From: Tomslin Samme-Nlar Reply-To: Tomslin Samme-Nlar To: NCSG-DISCUSS at LISTSERV.SYR.EDU Hi NCSG, We have an item on the GNSO council agenda relating to SubPro Recommendation 36.4 implementation. Please read below for the details of the concerns from the council liaisons to the IRT. Remain blessed, Tomslin ---------- Forwarded message --------- From: *Susan Payne via council* Date: Fri, 9 May 2025 at 02:59 Subject: [council] Council Agenda Item 7: Implementation of SubPro Rec 36.4 To: council at icann.org Cc: Tomslin Samme-Nlar via council Dear Council colleagues, ?This relates to agenda item 7 at our Council meeting of 15 May 2025. As the Co-Liaisons to the SubPro IRT, we need to raise a disagreement between staff and the IRT community group over the proposed implementation language in the Next Round Base Registry Agreement of one of the Board-adopted recommendations (SubPro Recommendation 36.4). ICANN's proposed language to implement Recommendation 36.4 is as follows: 4.3(f) ICANN may, upon notice to Registry Operator, terminate this Agreement if ?(i) ICANN receives a complaint, or ICANN otherwise becomes aware, that Registry Operator is engaging in fraudulent or deceptive business practices in provision of Registry Services under this Agreement for the TLD; and (ii) such fraudulent or deceptive business practices have resulted in an adverse action or decision and a failure to remediate finding against the Registry Operator by a relevant governmental consumer protection authority or authorities with jurisdiction over the matter, or Registry Operator is the subject of a determination that ICANN reasonably deems as the substantive equivalent of any of the foregoing; provided that, if ICANN receives a complaint related to the foregoing, all available relevant documentation from such adverse action or decision and a failure to remediate finding must be included as part of the complaint. Rec 36.4 had full consensus in the SubPro PDP WG, and was adopted by the ICANN Board.? It provides as follows? (in bold and divided into bullets by us for ease of reading).? Our text in red explains why the IRT concluded that the above draft does NOT comply with the Board-adopted Recommendation: *?****ICANN must add a contractual provision [to the Next Round Registry Agreement] stating that the registry operator will not engage in fraudulent or deceptive practices*. It is not disputed that such fraudulent or deceptive practices should be in the provision of Registry Services. The added contractual obligation is a key part of Rec 36.4, because the PICDRP Panel in the .Feedback case found that there was such conduct in the operation of the Registry, but that there was no contractual provision whereby the Registry Operator committed not to engage in such conduct.? Consequently the Panel considered itself unable to apply a sanction against the Registry Operator.? In spite of the ramifications of the .Feedback decision,which Rec 36.4 sought to remedy, ICANN proposes NOT to include such a provision in the RA. *?****In the event that ICANN receives an order from a court that a registry has engaged in fraudulent or deceptive practices, ICANN may issue a notice of breach for such practices and allow the registry to cure such breach in accordance with the Registry Agreement*. ICANN proposes to comply but provides in its draft language that the court or other governmental consumer protection authority order must include a finding that the fraudulent or deceptive practice has not been remediated by the Registry Operator.? As drafted (and this may simply be a drafting error) this is highly unlikely since no further order would normally follow in the event the Registry Operator remediates the problem.? Of course the Registry Operator could prove up remediation to ICANN but a court "finding" of a lack of remediation should not be required here. Rec 36.4 envisages ICANN making the determination of lack of remediation, after having given the RO the opportunity to cure the breach. *?****Further, in the event that there is a credible allegation by any third party of fraudulent or deceptive practices, other than as set forth in above, ICANN may, at its discretion, either:* *o****commence dispute resolution actions under the Registry Agreement (Currently Article 5 of the Registry Agreement), or * *o****appoint a panel under the PICDRP*. ICANN proposes NOT to utilise either of these alternative dispute resolution processes, where there is a credible allegation but no court order.? Instead, ICANN proposes to treat such a situation as equivalent to there being a Court Order, and going straight to termination without allowing the registry Operator to defend themselves via a DRP. Sub Pro had full consensus on the alternatives to be pursued in the absence of a court order.? The Recommendation provides for ICANN, in its discretion, to pursue enforcement either via (a) dispute resolution under Article 5 or (b) appointment of a PICDRP panel (the latter being possible only if the contractual provision not to engage, set out in bullet 1, is dealt with in the RA as a PIC/RVC). *?****For the purposes of a credible claim of fraudulent or deceptive practices the reporter (as defined by the PICDRP) must only specifically state the grounds of the alleged non-compliance, but not that it personally has been harmed as a result of the registry operator?s act or omission.*? ICANN proposes NOT to include this language. ?By way of additional detail, we have (attached): ?an explanation from Karla Hakansson of how staff propose to implement Rec 36.4 and why ?a detailed note from Jeff Neuman, one of the SubPro Co-chairs, summarising what Rec 36.4 says, the rationale for this recommendation, and how the staff proposed implementation differs from what was recommended.? Cheryl Langdon-Or, the other Co-chair, supports this note. Karla?s attached note states that Rec 36.4 requires ?ICANN (or ICANN with the assistance of a PICDRP panel) to make the substantive determinations as to whether a registry operator in fact engaged in fraudulent or deceptive practices?, and that this is outside of ICANN?s scope.? The IRT disagrees with that interpretation.? If there is a credible allegation (rather than an actual court finding) ICANN may proceed via its choice of dispute resolution process.? In other words, ICANN merely needs to believe there is sufficient evidence to bring the case, which is in its discretion, it is the DR panel that makes the substantive determination. We believe it is the full consensus of the SubPro IRT that staff?s proposed implementation does not meet Rec 36.4, in a number of ways (as set out in more detail above and in the Co-chairs note).? IRT members have expressed this concern on multiple calls since last November, and (to the best of our recollection) no IRT members have expressed an opposing view.? One member of the IRT has suggested that this issue needs to be addressed at the Board level. *What action might Council take? *We do not believe this is a situation where the PDP recommendation is unclear, and therefore this isn?t a case where clarification or guidance would assist.? Staff are aware of the meaning and intent of the recommendation, but do not intend to implement it as written.? As per Karla's attached note, ICANN believes it has followed the "intent" of the Recommendation.? The IRT disagrees. ? We believe that Council should provide input to ICANN Staff in charge of the IRT confirming Council's position that Rec 36.4 is clear, is designed to address an actual omission that has bearing on the Security and Stability of the Internet, and should be implemented as written.? Accordingly,? the current proposed implementation is unacceptable. We also believe it would be helpful for this communication to be copied to the Board, perhaps with a request to discuss this in Prague. *Susan and Anne* Joint Council Liaisons to SubPro IRT ------------------------------------------------------------------------ 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 _______________________________________________ council mailing list -- council at icann.org To unsubscribe send an email to council-leave at icann.org _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Rec 36.4_ 4.3(f) Fraudulent & Deceptive Practices - ICANN's position.pdf Type: application/pdf Size: 136290 bytes Desc: not available URL: -------------- next part -------------- An embedded message was scrubbed... From: Jeff Neuman via SubPro-IRT Subject: [SubPro-IRT] Re: [Ext] Base RA redline Date: Wed, 30 Apr 2025 19:38:35 +0000 Size: 60382 URL: From mesumbeslin at gmail.com Wed May 14 12:23:08 2025 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Wed, 14 May 2025 19:23:08 +1000 Subject: [NCSG-PC] Fwd: Fwd: [council] Council Agenda Item 7: Implementation of SubPro Rec 36.4 - Deep concerns In-Reply-To: <8edcc1ec-0f28-47c7-a9c3-31e9e58e276d@dnrc.tech> References: <8edcc1ec-0f28-47c7-a9c3-31e9e58e276d@dnrc.tech> Message-ID: Hi Kathy, all, Thanks for that input, very helpful. I didn't mention this during our PC meeting, but I believe the scope of the discussion in the council will be around the procedural and interpretation aspects of the issue, since this is about an already board-adopted recommendation. I agree with the point you make but i think the question will end up being: is ICANN implementing the recommendation as written? (Atleast from a council perspective). If not, which process can be used to retract board adoption of the recommendation. As an IRT member, do you know of anything we could use to strengthen your argument from a procedural perspective? Remain blessed, Tomslin On Tue, 13 May 2025, 02:26 Kathy Kleiman, wrote: > Hi Tomslin and all of our Counselors, > > Tx to Tomslin for sharing. As discussed in the PC meeting earlier, the two > SubPro liaisons in this case are both members of the IPC (although Anne is > also a Nomcom appointee to Council). They are good, but they have very > clear views, as does the IPC. > > *Here's some more background: *For the IPC, fraud is one of a series of > content issues they think registries and registrars should handle: For > example: > > => [ICANN Registry Agreement ] Registry Operator will include a provision > in its Registry-Registrar Agreement that requires Registrars to include in > their Registration Agreements a provision prohibiting Registered Name > Holders from > > *distributing malware, abusively operating botnets, phishing, piracy, > trademark or copyright infringement, fraudulent or deceptive practices, > counterfeiting or otherwise engaging in activity contrary to applicable > law, *and providing (consistent with applicable law and any related > procedures) consequences for such activities including suspension of the > domain name." [I added the bold] > > Certainly the SubPro WG majority wanted New gTLD registries *to do all of > this enforcement actively -- and yet trademark and copyright infringement > and alleged fraudulent and deceptive or counterfeiting issues are content > and contrary to ICANN Bylaws - we don't regulate content in ICANN (as the > June 8th, 2024, ICANN Board Resolution in Kigali confirmed).* > > But some leading members of the SubPro Implementation Review Team don't > like this June 8th resolution (and don't remember we told that the SubPro > WG recommendations on this topic were contrary to ICANN Bylaws). From they > perspective: if the SubPro WG recommended it, they want it done just that > way. > > But ICANN cannot look at fraudulent content on a webpage - because > fraudulent content is content (for example, I post that my washing > detergent is better than yours - my Tide and better than your Arm& Hammer. > In the US, comparative advertising is legal; in Germany, it is not. > Regardless, Arm & Hammer wants to take down my website down saying that my > claims (as Tide) are fraudulent... and wants the Registr > *y to enforce it, but ICANN cannot regulate content. This is a legal issue > outside of ICANN. * > > Appropriately (IMHO), ICANN Org (recently in the SubPro IRT) countered and > offered the IRT an alternative that I consider reasonable: ICANN Org wrote > and said that "fraud" within ICANN's mission is how a Registry manages its > registry business. For example (and these are my examples): if a Registry > says that it is putting new domain names into the root, and instead resells > them via another registry (charging twice), that would be fraudulent. > > *But if someone says that a Registry is engaged in fraud of this sort -- > how does ICANN know? *ICANN Org now says that the person/company/group > should go to court for a finding of fraud against the Registry - and then > bring it to ICANN. Or go to a government consumer protection agency - and > bring their finding to ICANN. > *Then ICANN will know what is illegal and fraudulent from an expert > tribunal (within the scope of the Bylaws) and will act. That seems fair > and right to me. * > But if anyone (an IP attorney, etc) can bring a PICDRP action against any > registry at any time in the PICDRP, then we will find the definitions of > fraud expanding to content - right way -- because so many see DNS abuse as > one continuum (although NCSG does not) and including -- > *trademark of copyright infringement, fraudulent or deceptive practices, > counterfeiting, etc. * > > As our only actived participant in the SubPro IRT at this time (and I've > attended the last 30 meetings), I share: > > I agree with what ICANN Org recommended and disagree with the Liaisons of > the Implementation Review Team. > > Best and tx, Kathy > -------- Forwarded Message -------- > Subject: Fwd: [council] Council Agenda Item 7: Implementation of SubPro > Rec 36.4 > Date: Mon, 12 May 2025 23:18:59 +1000 > From: Tomslin Samme-Nlar > Reply-To: Tomslin Samme-Nlar > > To: NCSG-DISCUSS at LISTSERV.SYR.EDU > > Hi NCSG, > > We have an item on the GNSO council agenda relating to SubPro > Recommendation 36.4 implementation. Please read below for the details of > the concerns from the council liaisons to the IRT. > > Remain blessed, > Tomslin > > > ---------- Forwarded message --------- > From: Susan Payne via council > Date: Fri, 9 May 2025 at 02:59 > Subject: [council] Council Agenda Item 7: Implementation of SubPro Rec 36.4 > To: council at icann.org > Cc: Tomslin Samme-Nlar via council > > > Dear Council colleagues, > > This relates to agenda item 7 at our Council meeting of 15 May 2025. > > As the Co-Liaisons to the SubPro IRT, we need to raise a disagreement > between staff and the IRT community group over the proposed implementation > language in the Next Round Base Registry Agreement of one of the > Board-adopted recommendations (SubPro Recommendation 36.4). ICANN's > proposed language to implement Recommendation 36.4 is as follows: > > 4.3(f) ICANN may, upon notice to Registry Operator, terminate this > Agreement if > > (i) ICANN receives a complaint, or ICANN otherwise becomes aware, that > Registry Operator is engaging in fraudulent or deceptive business practices > in provision of Registry Services under this Agreement for the TLD; and > > (ii) such fraudulent or deceptive business practices have resulted in an > adverse action or decision and a failure to remediate finding against the > Registry Operator by a relevant governmental consumer protection authority > or authorities with jurisdiction over the matter, or Registry Operator is > the subject of a determination that ICANN reasonably deems as the > substantive equivalent of any of the foregoing; provided that, if ICANN > receives a complaint related to the foregoing, all available relevant > documentation from such adverse action or decision and a failure to > remediate finding must be included as part of the complaint. > > Rec 36.4 had full consensus in the SubPro PDP WG, and was adopted by the > ICANN Board. It provides as follows (in bold and divided into bullets by > us for ease of reading). Our text in red explains why the IRT concluded > that the above draft does NOT comply with the Board-adopted Recommendation: > > *?* *ICANN must add a contractual provision [to the Next Round > Registry Agreement] stating that the registry operator will not engage in > fraudulent or deceptive practices*. It is not disputed that such > fraudulent or deceptive practices should be in the provision of Registry > Services. The added contractual obligation is a key part of Rec 36.4, > because the PICDRP Panel in the .Feedback case found that there was such > conduct in the operation of the Registry, but that there was no contractual > provision whereby the Registry Operator committed not to engage in such > conduct. Consequently the Panel considered itself unable to apply a > sanction against the Registry Operator. In spite of the ramifications of > the .Feedback decision, which Rec 36.4 sought to remedy, ICANN proposes > NOT to include such a provision in the RA. > > *?* *In the event that ICANN receives an order from a court that a > registry has engaged in fraudulent or deceptive practices, ICANN may issue > a notice of breach for such practices and allow the registry to cure such > breach in accordance with the Registry Agreement*. ICANN proposes to > comply but provides in its draft language that the court or other > governmental consumer protection authority order must include a finding > that the fraudulent or deceptive practice has not been remediated by the > Registry Operator. As drafted (and this may simply be a drafting error) > this is highly unlikely since no further order would normally follow in the > event the Registry Operator remediates the problem. Of course the Registry > Operator could prove up remediation to ICANN but a court "finding" of a > lack of remediation should not be required here. Rec 36.4 envisages ICANN > making the determination of lack of remediation, after having given the RO > the opportunity to cure the breach. > > *?* *Further, in the event that there is a credible allegation by > any third party of fraudulent or deceptive practices, other than as set > forth in above, ICANN may, at its discretion, either:* > > *o* *commence dispute resolution actions under the Registry Agreement > (Currently Article 5 of the Registry Agreement), or * > > *o* *appoint a panel under the PICDRP*. ICANN proposes NOT to utilise > either of these alternative dispute resolution processes, where there is a > credible allegation but no court order. Instead, ICANN proposes to treat > such a situation as equivalent to there being a Court Order, and going > straight to termination without allowing the registry Operator to defend > themselves via a DRP. Sub Pro had full consensus on the alternatives to be > pursued in the absence of a court order. The Recommendation provides for > ICANN, in its discretion, to pursue enforcement either via (a) dispute > resolution under Article 5 or (b) appointment of a PICDRP panel (the > latter being possible only if the contractual provision not to engage, set > out in bullet 1, is dealt with in the RA as a PIC/RVC). > > *?* *For the purposes of a credible claim of fraudulent or > deceptive practices the reporter (as defined by the PICDRP) must only > specifically state the grounds of the alleged non-compliance, but not that > it personally has been harmed as a result of the registry operator?s act or > omission.* ICANN proposes NOT to include this language. > > By way of additional detail, we have (attached): > > ? an explanation from Karla Hakansson of how staff propose to > implement Rec 36.4 and why > > ? a detailed note from Jeff Neuman, one of the SubPro Co-chairs, > summarising what Rec 36.4 says, the rationale for this recommendation, and > how the staff proposed implementation differs from what was recommended. > Cheryl Langdon-Or, the other Co-chair, supports this note. > > Karla?s attached note states that Rec 36.4 requires ?ICANN (or ICANN with > the assistance of a PICDRP panel) to make the substantive determinations as > to whether a registry operator in fact engaged in fraudulent or deceptive > practices?, and that this is outside of ICANN?s scope. The IRT disagrees > with that interpretation. If there is a credible allegation (rather than > an actual court finding) ICANN may proceed via its choice of dispute > resolution process. In other words, ICANN merely needs to believe there is > sufficient evidence to bring the case, which is in its discretion, it is > the DR panel that makes the substantive determination. > > We believe it is the full consensus of the SubPro IRT that staff?s > proposed implementation does not meet Rec 36.4, in a number of ways (as set > out in more detail above and in the Co-chairs note). IRT members have > expressed this concern on multiple calls since last November, and (to the > best of our recollection) no IRT members have expressed an opposing view. > One member of the IRT has suggested that this issue needs to be addressed > at the Board level. > > *What action might Council take? *We do not believe this is a situation > where the PDP recommendation is unclear, and therefore this isn?t a case > where clarification or guidance would assist. Staff are aware of the > meaning and intent of the recommendation, but do not intend to implement it > as written. As per Karla's attached note, ICANN believes it has followed > the "intent" of the Recommendation. The IRT disagrees. We believe that > Council should provide input to ICANN Staff in charge of the IRT confirming > Council's position that Rec 36.4 is clear, is designed to address an actual > omission that has bearing on the Security and Stability of the Internet, > and should be implemented as written. Accordingly, the current proposed > implementation is unacceptable. We also believe it would be helpful for > this communication to be copied to the Board, perhaps with a request to > discuss this in Prague. > > > > *Susan and Anne* > > Joint Council Liaisons to SubPro IRT > > > ------------------------------ > 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 > > _______________________________________________ > council mailing list -- council at icann.org > To unsubscribe send an email to council-leave at icann.org > > _______________________________________________ > By submitting your personal data, you consent to the processing of your > personal data for purposes of subscribing to this mailing list accordance > with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and > the website Terms of Service (https://www.icann.org/privacy/tos). You can > visit the Mailman link above to change your membership status or > configuration, including unsubscribing, setting digest-style delivery or > disabling delivery altogether (e.g., for a vacation), and so on. > > > > ---------- Forwarded message ---------- > From: Jeff Neuman via SubPro-IRT > To: Karla Hakansson , Anne ICANN < > anneicanngnso at gmail.com>, Jared Erwin via SubPro-IRT > > Cc: > Bcc: > Date: Wed, 30 Apr 2025 19:38:35 +0000 > Subject: [SubPro-IRT] Re: [Ext] Base RA redline > > Dear Anne and Susan, > > > > I know you have this covered, but if I could offer my own view as one of > the former co-chairs of SubPro. I have not spoken with Cheryl about this > as the other co-chair, but I would hope she would support this. I would > support forwarding this on to the Council to assist in its review. > > > > During the discussions within the Subsequent Procedures PDP, the topic of > ?fraudulent and deceptive practices? was discussed on numerous occasions, > especially earlier on during the work track phases (prior to the > preliminary report). The driving force behind those discussions was a > decision issued in the very first PICDRP dispute in 2017 regarding the > .feedback registry. > > > The .feedback PICDRP report (found here > ) > was read by the working group and discussed at length. More specifically, > the Panel found that the .feedback registry was engaged in fraudulent > and/or deceptive practices, but neither Specification 11 nor the registry > agreement itself contained a commitment, representation or covenant, that > the registry would not engage in fraudulent or deceptive practices. See > Exhibit A to the PICDRP report. > > > > The Working Group believed that this was an unjust result and that the > next registry agreement must fix this issue so that consumers are not > harmed in the future when a registry commits a fraudulent or deceptive > action. Therefore it unanimously agreed to recommendation 36.4 which > states: > > > > *Recommendation 36.4 *?CANN must add a contractual provision stating that > the registry operator will not engage in fraudulent or deceptive practices. > In the event that ICANN receives an order from a court that a registry has > engaged in fraudulent or deceptive practices, ICANN may issue a notice of > breach for such practices and allow the registry to cure such breach in > accordance with the Registry Agreement. Further, in the event that there is > a credible allegation by any third party of fraudulent or deceptive > practices, other than as set forth in above, ICANN may, at its discretion, > either commence dispute resolution actions under the Registry Agreement > (Currently Article 5 of the Registry Agreement), or appoint a panel under > the PICDRP. For the purposes of a credible claim of fraudulent or deceptive > practices the reporter (as defined by the PICDRP) must only specifically > state the grounds of the alleged non-compliance, but not that it personally > has been harmed as a result of the registry operator?s act or omission.? > > > > It is also worth noting that neither ICANN staff nor the ICANN Board > raised any issues about this recommendation in their comments to the > Initial Report or to the Proposed Final Draft Report, both of which > contained this recommendation. In addition, the ICANN Board of Directors > adopted this recommendation without any modification. > > > > ICANN now states that they believe they have accurately captured the > intent of the Recommendation 36.4. This could not be further from the > truth. > > > > - First, ICANN is refusing to put a commitment in the Registry > Agreement whereby the registry agrees to not engage in fraudulent or > deceptive practices. Rather, it proposes to hide that commitment in a > termination provision. > - Second, the recommendation is clear that the promise to not engage > in fraud be included in the PICDRP, which means obviously that it must be a > Public Interest Commitment made by the registry. Otherwise it could not be > included in the PICDRP. ICANN has refused to create such a PIC. > - Third, in its proposed language in the termination section, ICANN > states that it will only do so if such fraud is found by a court, a > consumer protection authority, or what it deems to be a suitable > arbitration. ICANN has refused to have it be subject to the PICDRP (where > a third party?.not ICANN?would decide if there was fraud). > - Fourth, ICANN argues that we should not put ICANN in a position to > determine fraud. We actually agree with this which is why SubPro > recommended it be in a PICDRP, so that ICANN could choose to have a third > party make that determination. ICANN has refused. > > > > What does this mean? It means that if the .feedback situation came up > again, we would likely have the same unjust result. A registry would be > found to have engaged in fraud by an independent panel, but ICANN and the > panel would be powerless to find the registry in breach of its Registry > Agreement. Like in .feedback, consumers were harmed, and ICANN stood by > powerless to address. Under ICANN?s proposed language it would still be as > powerless. > > > > It is also worth noting that the reason SubPro chose to go with the > language it went with in the recommendation was because that language > actually appears in another section of the Registry Agreement. More > specifically, ICANN has imposed an obligation for registries to require > registrars to have a registrant agreement that prohibits ? fraudulent and > deceptive practice. The irony here is that ICANN is saying that > registries/registrars should police for this, but ICANN org should not. > Apparently, when it concerns ICANN having to do some enforcement, it will > not claiming they are not law enforcement and do not have the ability to do > that type of enforcement. But apparently ICANN believes that registries > and registrars do have that ability. > > > > To reiterate the SubPro Recommendation: > > 1. ICANN must include a provision in the Registry Agreement stating > that the registry operator will not engage in fraudulent or deceptive > practices. ? ICANN has not done this. > 2. If ICANN receives a Court Order that the registry has engaged in > fraud, it may issue a notice of breach ? ICANN has done this. > 3. Further, in the event that there is a credible allegation by any > third party of fraudulent or deceptive practices, other than as set forth > in above, ICANN may, at its discretion, either commence dispute resolution > actions under the Registry Agreement (Currently Article 5 of the Registry > Agreement), or appoint a panel under the PICDRP. ICANN has NOT done > this. > > > > Nothing requires ICANN to police for fraud. Rather, if there is a > credible claim, ICANN can send it to a PICDRP for the third party to make > the determination OR it can choose to Arbitrate the issue directly under > Article 5 of the Registry Agreement. > > > > Sincerely, > > Jeff > > > > > > *From:* Karla Hakansson via SubPro-IRT > *Sent:* Wednesday, April 30, 2025 1:12 PM > *To:* Anne ICANN ; Jared Erwin via SubPro-IRT < > subpro-irt at icann.org> > *Cc:* subpro-irt at icann.org > *Subject:* [SubPro-IRT] Re: [Ext] Base RA redline > > > > Hi Anne, > > > > You can find the NxR Base RA redline in the working documents under Topic > 36: Base RA on the SubPro IRT wiki: > file:///Users/karla.hakansson/Downloads/REDLINE%20-%20Next%20Round%20Base%20RA%20Preliminary%20Working%20Draft_1%20November%202024%20(7).pdf > > > > Still TBD on the date when we post the RA for public comment. We are > shooting for the end of May. The public comment period will be the standard > 40 days. > > > > Best, > > Karla > > > > *From: *Anne ICANN > *Date: *Tuesday, April 29, 2025 at 15:52 > *To: *Karla Hakansson , Jared Erwin via > SubPro-IRT > *Subject: *[Ext] Base RA redline > > > > Hi Karla, > > Do we currently have a link to the entire Base RA redline as previously > requested? > > > > Will the Base RA language be going out for public comment at the same time > as the draft AGB in its entirety? How long with the public comment period > be? > > > > Thank you, > > Anne > > > > Anne Aikman-Scalese > > GNSO Councilor > > NomCom Non-Voting 2022-2026 > > anneicanngnso at gmail.com > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 13020 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 13020 bytes Desc: not available URL: From rafik.dammak at gmail.com Thu May 15 17:00:19 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Thu, 15 May 2025 23:00:19 +0900 Subject: [NCSG-PC] ALAC plenary in Prague meeting Message-ID: Hi all, At-large invited me to speak on their plenary on Prague "What?s Next on DNS Abuse: Progressing Mitigation Efforts within ICANN" . However, it will be in same time with a NCSG session and I don't believe I am the right person to speak there. They accepted that I propose another representative from NCSG. I am thinking to suggest Farzaneh as she is following this topic closely and spoke on our behalf. I need to respond asap as they will start their planning soon. Best, Rafik -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Thu May 15 17:02:15 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Thu, 15 May 2025 23:02:15 +0900 Subject: [NCSG-PC] [Ext] [NCSG-EC] Topics for joint meeting with ALAC In-Reply-To: <404951C3-4FDC-4BE8-AAF3-F12735F4CA96@icann.org> References: <404951C3-4FDC-4BE8-AAF3-F12735F4CA96@icann.org> Message-ID: Hi all, We need to respond to alac. Till now we got the topics of reviews, applicant support, HRIA and DNS abuse. Best, Rafik On Sat, May 10, 2025, 01:16 Andrea Glandon wrote: > Hello all! > > > > Kind reminder to work on topics for the joint session with ALAC. At-Large > staff is working on confirming the agenda. > > > > Thanks! > > Kind Regards, > > Andrea > > > > > > *From: *NCSG-EC on behalf of Rafik Dammak > via NCSG-EC > *Reply-To: *Rafik Dammak > *Date: *Wednesday, April 30, 2025 at 07:09 > *To: *ncsg-pc , NCSG EC > *Subject: *[Ext] [NCSG-EC] Topics for joint meeting with ALAC > > > > Hi all, > > > > ALAC reached out asking about topics we want to discuss with them. Please > share your suggestion and/or if you want to volunteer to lead the topic. > > > > Best, > > > > Rafik > Rafik Dammak @rafik "fight for the users" -------------- next part -------------- An HTML attachment was scrubbed... URL: From michaela.shapiro at article19.org Thu May 15 17:10:10 2025 From: michaela.shapiro at article19.org (Michaela Nakayama Shapiro) Date: Thu, 15 May 2025 14:10:10 +0000 Subject: [NCSG-PC] ALAC plenary in Prague meeting In-Reply-To: References: <03d95705-f733-4d96-bfa3-6ea2374cd25b.05b495a4-acd5-4405-a5fb-09b87eaaeafb.058b5f33-afa6-4ee6-b7bd-503b730ceba9@emailsignatures365.codetwo.com> Message-ID: INTERNAL INTERNAL Hi Rafik, I second having Farzaneh speak, should she be available at that time! I would also be happy to speak on the topic, but note that Farzaneh certainly has more institutional knowledge and expertise. Would you be able to share the time/date for the plenary? Sara Ali also spoke on the topic of DNS abuse in the session we hosted at ICANN82. If she is interested/available, I think she would be another great option for the session. Best, Michaela Michaela Nakayama Shapiro (she/her/hers) Programme Officer - Censorship [Logo.png] Defending freedom of expression and information www.article19.org Subscribe to our Newsletter [cid:newsletter_02744340-c607-4374-8a37-11b8b216096d.png] Follow us [Bluesky1x.png] [cid:facebook_2853baa0-f060-42e6-b448-6a8788c1b5dd.png] [cid:youtube_ffe95af1-d962-4acd-ab59-4eb4ea07466e.png] [cid:linkedin_199dc89c-14aa-41cd-b2a7-37b8ae8d667d.png] [cid:instagram_05fbcc72-6df2-442b-8c34-146d0e9d8c41.png] [cid:x_d21e0607-da5a-44a7-80c7-e2d86bc18a92.png] [women-journalists-banner.jpeg] From: NCSG-PC on behalf of Rafik Dammak Date: Thursday, 15 May 2025 at 15:00 To: ncsg-pc Subject: [NCSG-PC] ALAC plenary in Prague meeting Hi all, At-large invited me to speak on their plenary on Prague "What?s Next on DNS Abuse: Progressing Mitigation Efforts within ICANN" . However, it will be in same time with a NCSG session and I don't believe I am the right person to speak there. They accepted that I propose another representative from NCSG. I am thinking to suggest Farzaneh as she is following this topic closely and spoke on our behalf. I need to respond asap as they will start their planning soon. Best, Rafik -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo_1c766458-35ee-431a-9a22-e00b47cd2091.png Type: image/png Size: 6889 bytes Desc: logo_1c766458-35ee-431a-9a22-e00b47cd2091.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: newsletter_02744340-c607-4374-8a37-11b8b216096d.png Type: image/png Size: 379 bytes Desc: newsletter_02744340-c607-4374-8a37-11b8b216096d.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bluesky1x_864ef831-9476-4116-88b8-2a3410741630.png Type: image/png Size: 788 bytes Desc: bluesky1x_864ef831-9476-4116-88b8-2a3410741630.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: facebook_2853baa0-f060-42e6-b448-6a8788c1b5dd.png Type: image/png Size: 670 bytes Desc: facebook_2853baa0-f060-42e6-b448-6a8788c1b5dd.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: youtube_ffe95af1-d962-4acd-ab59-4eb4ea07466e.png Type: image/png Size: 678 bytes Desc: youtube_ffe95af1-d962-4acd-ab59-4eb4ea07466e.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: linkedin_199dc89c-14aa-41cd-b2a7-37b8ae8d667d.png Type: image/png Size: 720 bytes Desc: linkedin_199dc89c-14aa-41cd-b2a7-37b8ae8d667d.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: instagram_05fbcc72-6df2-442b-8c34-146d0e9d8c41.png Type: image/png Size: 840 bytes Desc: instagram_05fbcc72-6df2-442b-8c34-146d0e9d8c41.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: x_d21e0607-da5a-44a7-80c7-e2d86bc18a92.png Type: image/png Size: 895 bytes Desc: x_d21e0607-da5a-44a7-80c7-e2d86bc18a92.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: women-journalists-banner_b1cece5c-a86d-452f-b9f8-9e72943680f6.jpeg Type: image/jpeg Size: 15471 bytes Desc: women-journalists-banner_b1cece5c-a86d-452f-b9f8-9e72943680f6.jpeg URL: From Kathy at KathyKleiman.com Thu May 15 17:16:41 2025 From: Kathy at KathyKleiman.com (Kathy Kleiman) Date: Thu, 15 May 2025 10:16:41 -0400 Subject: [NCSG-PC] [Ext] [NCSG-EC] Topics for joint meeting with ALAC In-Reply-To: References: <404951C3-4FDC-4BE8-AAF3-F12735F4CA96@icann.org> Message-ID: <1cebc4f0-440e-46d5-9a64-04954055ea59@KathyKleiman.com> That sounds like a good list, Rafik.? Perhaps they'll have some other items to add? Best, Kathy On 5/15/2025 10:02 AM, Rafik Dammak wrote: > Hi all, > > We need to respond to alac. Till now we got the topics of reviews, > applicant support, HRIA and DNS abuse. > > Best, > > Rafik > > > On Sat, May 10, 2025, 01:16 Andrea Glandon > wrote: > > Hello all! > > Kind reminder to work on topics for the joint session with ALAC. > At-Large staff is working on confirming the agenda. > > Thanks! > > Kind Regards, > > Andrea > > *From: *NCSG-EC on behalf of Rafik > Dammak via NCSG-EC > *Reply-To: *Rafik Dammak > *Date: *Wednesday, April 30, 2025 at 07:09 > *To: *ncsg-pc , NCSG EC > *Subject: *[Ext] [NCSG-EC] Topics for joint meeting with ALAC > > Hi all, > > ALAC reached out asking about topics we want to discuss with them. > Please share your suggestion and/or if you want to volunteer to > lead the topic. > > Best, > > Rafik > > Rafik Dammak > @rafik > "fight for the users" > > _______________________________________________ > 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 manju4icann at gmail.com Fri May 16 08:02:28 2025 From: manju4icann at gmail.com (Manju) Date: Fri, 16 May 2025 13:02:28 +0800 Subject: [NCSG-PC] [Ext] [NCSG-EC] Topics for joint meeting with ALAC In-Reply-To: <1cebc4f0-440e-46d5-9a64-04954055ea59@KathyKleiman.com> References: <404951C3-4FDC-4BE8-AAF3-F12735F4CA96@icann.org> <1cebc4f0-440e-46d5-9a64-04954055ea59@KathyKleiman.com> Message-ID: Hi Rafik, Maybe we can add SOI too since the updated Board document will be published for public comments soon. Thanks! Best, Manju On Thu, May 15, 2025 at 10:16?PM Kathy Kleiman wrote: > That sounds like a good list, Rafik. Perhaps they'll have some other > items to add? > > Best, Kathy > On 5/15/2025 10:02 AM, Rafik Dammak wrote: > > Hi all, > > We need to respond to alac. Till now we got the topics of reviews, > applicant support, HRIA and DNS abuse. > > Best, > > Rafik > > > On Sat, May 10, 2025, 01:16 Andrea Glandon > wrote: > >> Hello all! >> >> >> >> Kind reminder to work on topics for the joint session with ALAC. At-Large >> staff is working on confirming the agenda. >> >> >> >> Thanks! >> >> Kind Regards, >> >> Andrea >> >> >> >> >> >> *From: *NCSG-EC on behalf of Rafik >> Dammak via NCSG-EC >> *Reply-To: *Rafik Dammak >> *Date: *Wednesday, April 30, 2025 at 07:09 >> *To: *ncsg-pc , NCSG EC >> *Subject: *[Ext] [NCSG-EC] Topics for joint meeting with ALAC >> >> >> >> Hi all, >> >> >> >> ALAC reached out asking about topics we want to discuss with them. Please >> share your suggestion and/or if you want to volunteer to lead the topic. >> >> >> >> Best, >> >> >> >> Rafik >> > Rafik Dammak > @rafik > "fight for the users" > > _______________________________________________ > NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Fri May 16 10:28:15 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Fri, 16 May 2025 16:28:15 +0900 Subject: [NCSG-PC] ALAC plenary in Prague meeting In-Reply-To: References: <03d95705-f733-4d96-bfa3-6ea2374cd25b.05b495a4-acd5-4405-a5fb-09b87eaaeafb.058b5f33-afa6-4ee6-b7bd-503b730ceba9@emailsignatures365.codetwo.com> Message-ID: Hi Michaela, Thanks for the comment. The plenary will be on *Thursday, 12 June 2025 from 10:45-12:15 CEST (8:45-10:15 UTC).* Best Rafik Le jeu. 15 mai 2025 ? 23:10, Michaela Nakayama Shapiro < michaela.shapiro at article19.org> a ?crit : > INTERNAL > > INTERNAL > > Hi Rafik, > > > > I second having Farzaneh speak, should she be available at that time! I > would also be happy to speak on the topic, but note that Farzaneh certainly > has more institutional knowledge and expertise. Would you be able to share > the time/date for the plenary? > > > > Sara Ali also spoke on the topic of DNS abuse in the session we hosted at > ICANN82. If she is interested/available, I think she would be another great > option for the session. > > > > Best, > > > > Michaela > > > *Michaela Nakayama Shapiro *(she/her/hers) > Programme Officer - Censorship > [image: Logo.png] Defending freedom of > expression > and information > *www.article19.org* Subscribe to our > Newsletter > > Follow us > [image: Bluesky1x.png] > > > > > > [image: women-journalists-banner.jpeg] > > > *From: *NCSG-PC on behalf of Rafik Dammak > > *Date: *Thursday, 15 May 2025 at 15:00 > *To: *ncsg-pc > *Subject: *[NCSG-PC] ALAC plenary in Prague meeting > > Hi all, > > > > At-large invited me to speak on their plenary on Prague "What?s Next on > DNS Abuse: Progressing Mitigation Efforts within ICANN" . However, it will > be in same time with a NCSG session and I don't believe I am the right > person to speak there. They accepted that I propose another representative > from NCSG. I am thinking to suggest Farzaneh as she is following this topic > closely and spoke on our behalf. > > I need to respond asap as they will start their planning soon. > > > > Best, > > > > Rafik > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo_1c766458-35ee-431a-9a22-e00b47cd2091.png Type: image/png Size: 6889 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: newsletter_02744340-c607-4374-8a37-11b8b216096d.png Type: image/png Size: 379 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bluesky1x_864ef831-9476-4116-88b8-2a3410741630.png Type: image/png Size: 788 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: facebook_2853baa0-f060-42e6-b448-6a8788c1b5dd.png Type: image/png Size: 670 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: youtube_ffe95af1-d962-4acd-ab59-4eb4ea07466e.png Type: image/png Size: 678 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: linkedin_199dc89c-14aa-41cd-b2a7-37b8ae8d667d.png Type: image/png Size: 720 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: instagram_05fbcc72-6df2-442b-8c34-146d0e9d8c41.png Type: image/png Size: 840 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: x_d21e0607-da5a-44a7-80c7-e2d86bc18a92.png Type: image/png Size: 895 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: women-journalists-banner_b1cece5c-a86d-452f-b9f8-9e72943680f6.jpeg Type: image/jpeg Size: 15471 bytes Desc: not available URL: From rafik.dammak at gmail.com Fri May 16 12:18:54 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Fri, 16 May 2025 18:18:54 +0900 Subject: [NCSG-PC] Topics/agenda for NCPH session in prague Message-ID: Hi all, I am discussing with CSG leadership about topics for discussion for our session in Prague and the proposed those in the attached slides. I think those topics are OK while I am not sure how much we will be interested by ICP2 one. I will check about the item of issues of common ground. Initially I proposed the topic of seat 14 and GNSO election. But I would like to get any proposal from our side or to hear if there is any concern. Best, Rafik -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: NCPH Agenda ICANN83.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 36363 bytes Desc: not available URL: From rafik.dammak at gmail.com Fri May 16 12:48:01 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Fri, 16 May 2025 18:48:01 +0900 Subject: [NCSG-PC] [Ext] [NCSG-EC] Topics for joint meeting with ALAC In-Reply-To: References: <404951C3-4FDC-4BE8-AAF3-F12735F4CA96@icann.org> <1cebc4f0-440e-46d5-9a64-04954055ea59@KathyKleiman.com> Message-ID: Hi Manju, Thanks for the suggestion, I will add that. I think we got a decent list and we can work on the lead discussant for each. I will share this with alac. Best, Rafik On Fri, May 16, 2025, 14:02 Manju wrote: > Hi Rafik, > > Maybe we can add SOI too since the updated Board document will be > published for public comments soon. > > Thanks! > > Best, > Manju > > On Thu, May 15, 2025 at 10:16?PM Kathy Kleiman > wrote: > >> That sounds like a good list, Rafik. Perhaps they'll have some other >> items to add? >> >> Best, Kathy >> On 5/15/2025 10:02 AM, Rafik Dammak wrote: >> >> Hi all, >> >> We need to respond to alac. Till now we got the topics of reviews, >> applicant support, HRIA and DNS abuse. >> >> Best, >> >> Rafik >> >> >> On Sat, May 10, 2025, 01:16 Andrea Glandon >> wrote: >> >>> Hello all! >>> >>> >>> >>> Kind reminder to work on topics for the joint session with ALAC. >>> At-Large staff is working on confirming the agenda. >>> >>> >>> >>> Thanks! >>> >>> Kind Regards, >>> >>> Andrea >>> >>> >>> >>> >>> >>> *From: *NCSG-EC on behalf of Rafik >>> Dammak via NCSG-EC >>> *Reply-To: *Rafik Dammak >>> *Date: *Wednesday, April 30, 2025 at 07:09 >>> *To: *ncsg-pc , NCSG EC >>> *Subject: *[Ext] [NCSG-EC] Topics for joint meeting with ALAC >>> >>> >>> >>> Hi all, >>> >>> >>> >>> ALAC reached out asking about topics we want to discuss with them. >>> Please share your suggestion and/or if you want to volunteer to lead the >>> topic. >>> >>> >>> >>> Best, >>> >>> >>> >>> Rafik >>> >> Rafik Dammak >> @rafik >> "fight for the users" >> >> _______________________________________________ >> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc >> >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Sat May 17 01:55:26 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Sat, 17 May 2025 07:55:26 +0900 Subject: [NCSG-PC] Fwd: ICANN83 session participation request: RrSG DNS Abuse: Example Review and Panel Discussion In-Reply-To: References: Message-ID: Hi all, RrSG is asking if we can designate a representative from NCSG to be in their session "DNS Abuse: Example Review and Panel Discussion" on Wednesday, 11 June, from 10:45 am to 12:15 pm local time. As Farzaneh will be a speaker in ALAC plenary on DNS abuse, I think Michaela can join this session as NCSG rep. Any concern? Best, Rafik ---------- Forwarded message --------- Hello Rafik, The RrSG is planning our ICANN83 session ?DNS Abuse: Example Review and Panel Discussion?, where we will invite panelists from across the ICANN Community as well as session attendees to review examples of DNS Abuse reports and tell us what they think the best outcome would be. The goal of the session is to better understand varying perspectives on how DNS Abuse is addressed and consider what further work is necessary to further improve the security, stability, and resilience of the DNS. This session will take place in Prague on Wednesday, 11 June, from 10:45 am to 12:15 pm local time. We invite you to designate someone from the NCSG to join the panel and to provide example DNS Abuse reports to use in the session; we need to confirm panelists and receive the examples by 4 June at the latest. If you prefer to do one but not the other (e.g. provide examples but not join the panel) we still appreciate your input; if you prefer not to participate at all, please let us know as soon as possible. We would ask you to provide two or three example DNS Abuse reports to be used in the session and encourage you to choose real-life reports instead of ?synthetic? or made up examples. Please remove any Personal Data before sharing. You may redact the domain as well; if you choose to do so, please let us know. Please provide the example exactly as you would report it to a registrar. While we will include all the provided examples in the session slides, we do not anticipate that we will be able to discuss all the examples provided by every group as the session will prioritize the discussion. Note that example scenarios will not be provided to panelists in advance of the session, in order to capture real-time and dynamic reactions to these situations. The audience will also be encouraged, via Zoom poll, to provide their own assessments. We look forward to hearing back from you and please don?t hesitate to reach out if you have any questions about this request. Thank you, Sarah Wyld RrSG Communications & Outreach Subgroup Lead in coordination with Luc Seufer & Reg Levy Co-Chairs RrSG DNS Abuse Subgroup -------------- next part -------------- An HTML attachment was scrubbed... URL: From farzaneh.badii at gmail.com Sat May 17 03:01:11 2025 From: farzaneh.badii at gmail.com (farzaneh badii) Date: Fri, 16 May 2025 20:01:11 -0400 Subject: [NCSG-PC] Please comment /GAC Communique HRIA In-Reply-To: References: <30097ff8-4b9e-4015-a966-d06ed978e123@KathyKleiman.com> Message-ID: Hi all I made the changes, Rafik you can send the letter to NCSG again when you get a chance, and we can send it off to GAC next week. Here are the people we should send it to: Nico: GAC Chair GAC Human Rights Group Perhaps Manal? https://docs.google.com/document/d/1ApT0BcojnWQ4otJYFotan2M0pxsxbJQSdbkhIdXX4E8/edit?tab=t.0 Farzaneh On Thu, Apr 24, 2025 at 3:16?PM Kathy Kleiman wrote: > Feel free to say reviewed and endorsed by NCSG & Farzi (if all agree)! > On 4/24/2025 12:45 PM, Tomslin Samme-Nlar wrote: > > Yes, Let's send it with the suggested addition about who did the HRIA > analysis that Kathy mentioned. > > Remain blessed, > Tomslin > > > On Thu, 17 Apr 2025 at 09:01, Kathy Kleiman > wrote: > >> Tx Farzi, the analysis is sharp, clear, and expert! * Question: Should >> there be more information in a header as to who did this HRIA analysis and >> their background?* >> >> This doc is a great new addition to ICANN's review of the GAC communique! >> >> Best, Kathy >> On 4/16/2025 3:34 PM, farzaneh badii wrote: >> >> Hi all >> >> This is what we wrote on GAC communique and human rights. Can the PC look >> over this and decide on whether Rafik should send it to GAC's chair? >> >> >> https://docs.google.com/document/d/1ApT0BcojnWQ4otJYFotan2M0pxsxbJQSdbkhIdXX4E8/edit?tab=t.0 >> >> Best regards, >> >> Farzaneh >> >> _______________________________________________ >> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc >> >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Sat May 17 03:29:17 2025 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Sat, 17 May 2025 10:29:17 +1000 Subject: [NCSG-PC] Public Comment proceeding now open for the How We Meet project In-Reply-To: References: <9FCC8463-B870-4F0E-8814-8D8C87C3C440@icann.org> Message-ID: Hi NCSG, The draft being put together by Yao and team can be found here [ https://docs.google.com/document/d/1BJqZx8AuwQNJONaBLiONDdyoJNC51GfInKjAMaZUDy0/edit?usp=drivesdk] for your review. Please keep in mind that the comment period closes on 19th of May. Remain blessed, Tomslin On Fri, 11 Apr 2025, 05:16 Tomslin Samme-Nlar, wrote: > Thank you for sharing, Rafik. > > Hi all, > if you'd like to volunteer for the drafting of the comment, please let me > know. > I have created a Google doc > > which is populated with the comment template to ease the drafting. > > Warmly, > Tomslin > > > On Thu, 10 Apr 2025 at 12:13, Rafik Dammak wrote: > >> hi all, >> >> A new public comment proceeding is open now , this time about the topic >> of How We Meet which was also covered in session in the last ICANN meeting >> in Seattle. We shared input previously regarding a draft proposal. >> @Tomslin Samme-Nlar will follow-up with regard >> to volunteers for drafting NCSG comments. >> >> Best, >> >> Rafik >> >> ---------- Forwarded message --------- >> >> Dear community leaders, >> >> We are pleased to inform you that the Public Comment proceeding for the >> How We Meet project has opened, and will close on *Monday 19 May* after >> the requisite 40-day comment period: >> https://www.icann.org/en/public-comment/proceeding/how-we-meet-reviewing-the-implementation-of-the-icann-public-meetings-strategy-09-04-2025. >> We?d like to take this opportunity to thank you all for the collaborative >> and collegial discussions, including the initial conversations last year at >> ICANN80 that saw us hold an informal community consultation, paving the way >> for the more targeted project that is currently underway. We hope that you >> will also encourage your respective communities to submit input during this >> Public Comment proceeding, which in some cases can augment or confirm prior >> feedback they provided previously. >> >> >> >> As you concurrently plan your groups? sessions for ICANN83 and the rest >> of the year, we thought it might be useful to share the intended project >> timeline with you: >> >> - Wednesday 9 April: Public Comment proceeding opens >> - Monday 19 May: Public Comment proceeding closes (40 days) >> - Wednesday 21 May: Staff to share initial analysis of Public >> Comments with the How We Meet Community Discussion Group >> - Thursday 22 May: Community Discussion Group meeting to review and >> discuss the initial analysis >> - ICANN83: Working Session for the Community Discussion Group to >> continue discussions (open to the community to attend) >> - End-June (planned): Report updated >> >> >> >> Thank you! >> >> >> >> Cheers >> >> Mary (on behalf of the staff supporting the How We Meet project) >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Sat May 17 03:43:18 2025 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Sat, 17 May 2025 10:43:18 +1000 Subject: [NCSG-PC] [NCSG-EC] Topics/agenda for NCPH session in prague In-Reply-To: References: Message-ID: Looks enough. Remain blessed, Tomslin On Fri, 16 May 2025, 19:19 Rafik Dammak via NCSG-EC, wrote: > Hi all, > > I am discussing with CSG leadership about topics for discussion for our > session in Prague and the proposed those in the attached slides. > > I think those topics are OK while I am not sure how much we will be > interested by ICP2 one. I will check about the item of issues of common > ground. Initially I proposed the topic of seat 14 and GNSO election. But I > would like to get any proposal from our side or to hear if there is any > concern. > > Best, > > Rafik > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -------------- next part -------------- An HTML attachment was scrubbed... URL: From farzaneh.badii at gmail.com Sat May 17 04:07:03 2025 From: farzaneh.badii at gmail.com (farzaneh badii) Date: Fri, 16 May 2025 21:07:03 -0400 Subject: [NCSG-PC] [NCSG-EC] Topics/agenda for NCPH session in prague In-Reply-To: References: Message-ID: So am I right that most of the topics are led by them? And what does RDRS decision transparency mean? Is it too soon for this rejuvenated meeting to talk about tricky issues like dns abuse and accuracy? Farzaneh On Fri, May 16, 2025 at 8:43?PM Tomslin Samme-Nlar via NCSG-EC < ncsg-ec at lists.ncsg.is> wrote: > Looks enough. > > Remain blessed, > Tomslin > > On Fri, 16 May 2025, 19:19 Rafik Dammak via NCSG-EC, < > ncsg-ec at lists.ncsg.is> wrote: > >> Hi all, >> >> I am discussing with CSG leadership about topics for discussion for our >> session in Prague and the proposed those in the attached slides. >> >> I think those topics are OK while I am not sure how much we will be >> interested by ICP2 one. I will check about the item of issues of common >> ground. Initially I proposed the topic of seat 14 and GNSO election. But I >> would like to get any proposal from our side or to hear if there is any >> concern. >> >> Best, >> >> Rafik >> _______________________________________________ >> NCSG-EC mailing list >> NCSG-EC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >> > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Sat May 17 04:21:22 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Sat, 17 May 2025 10:21:22 +0900 Subject: [NCSG-PC] [NCSG-EC] Topics/agenda for NCPH session in prague In-Reply-To: References: Message-ID: Hi Farzaneh, Yes other than board seat and GNSO election, the other topics were proposed by CSG leaders and I didn't discuss yet with them. For leading topics, we can assign a lead from our side. I will ask about the RDRS topic. I think we can talk about any topic and we can clarify what we want as outcome knowing the difference on opinions between NCSG and CSG. Best, Rafik On Sat, May 17, 2025, 10:07 farzaneh badii wrote: > So am I right that most of the topics are led by them? And what does RDRS > decision transparency mean? > > Is it too soon for this rejuvenated meeting to talk about tricky issues > like dns abuse and accuracy? > > Farzaneh > > > On Fri, May 16, 2025 at 8:43?PM Tomslin Samme-Nlar via NCSG-EC < > ncsg-ec at lists.ncsg.is> wrote: > >> Looks enough. >> >> Remain blessed, >> Tomslin >> >> On Fri, 16 May 2025, 19:19 Rafik Dammak via NCSG-EC, < >> ncsg-ec at lists.ncsg.is> wrote: >> >>> Hi all, >>> >>> I am discussing with CSG leadership about topics for discussion for our >>> session in Prague and the proposed those in the attached slides. >>> >>> I think those topics are OK while I am not sure how much we will be >>> interested by ICP2 one. I will check about the item of issues of common >>> ground. Initially I proposed the topic of seat 14 and GNSO election. But I >>> would like to get any proposal from our side or to hear if there is any >>> concern. >>> >>> Best, >>> >>> Rafik >>> _______________________________________________ >>> NCSG-EC mailing list >>> NCSG-EC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>> >> _______________________________________________ >> NCSG-EC mailing list >> NCSG-EC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From manju4icann at gmail.com Sat May 17 12:23:13 2025 From: manju4icann at gmail.com (Manju) Date: Sat, 17 May 2025 17:23:13 +0800 Subject: [NCSG-PC] Please comment /GAC Communique HRIA In-Reply-To: References: <30097ff8-4b9e-4015-a966-d06ed978e123@KathyKleiman.com> Message-ID: Hi, Excellent assessment! Hopefully GAC will appreciate it as we do. Best, Manju On Sat, May 17, 2025 at 08:02 farzaneh badii wrote: > Hi all > > I made the changes, Rafik you can send the letter to NCSG again when you > get a chance, and we can send it off to GAC next week. Here are the people > we should send it to: > > Nico: GAC Chair > GAC Human Rights Group > Perhaps Manal? > > https://docs.google.com/document/d/1ApT0BcojnWQ4otJYFotan2M0pxsxbJQSdbkhIdXX4E8/edit?tab=t.0 > > > Farzaneh > > > On Thu, Apr 24, 2025 at 3:16?PM Kathy Kleiman > wrote: > >> Feel free to say reviewed and endorsed by NCSG & Farzi (if all agree)! >> On 4/24/2025 12:45 PM, Tomslin Samme-Nlar wrote: >> >> Yes, Let's send it with the suggested addition about who did the HRIA >> analysis that Kathy mentioned. >> >> Remain blessed, >> Tomslin >> >> >> On Thu, 17 Apr 2025 at 09:01, Kathy Kleiman >> wrote: >> >>> Tx Farzi, the analysis is sharp, clear, and expert! * Question: Should >>> there be more information in a header as to who did this HRIA analysis and >>> their background?* >>> >>> This doc is a great new addition to ICANN's review of the GAC communique! >>> >>> Best, Kathy >>> On 4/16/2025 3:34 PM, farzaneh badii wrote: >>> >>> Hi all >>> >>> This is what we wrote on GAC communique and human rights. Can the PC >>> look over this and decide on whether Rafik should send it to GAC's chair? >>> >>> >>> https://docs.google.com/document/d/1ApT0BcojnWQ4otJYFotan2M0pxsxbJQSdbkhIdXX4E8/edit?tab=t.0 >>> >>> Best regards, >>> >>> Farzaneh >>> >>> _______________________________________________ >>> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc >>> >>> _______________________________________________ >>> NCSG-PC mailing list >>> NCSG-PC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >>> >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Sat May 17 12:28:12 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Sat, 17 May 2025 18:28:12 +0900 Subject: [NCSG-PC] Please comment /GAC Communique HRIA In-Reply-To: References: <30097ff8-4b9e-4015-a966-d06ed978e123@KathyKleiman.com> Message-ID: Thanks Farzaneh, let me do that. Rafik On Sat, May 17, 2025, 09:02 farzaneh badii wrote: > Hi all > > I made the changes, Rafik you can send the letter to NCSG again when you > get a chance, and we can send it off to GAC next week. Here are the people > we should send it to: > > Nico: GAC Chair > GAC Human Rights Group > Perhaps Manal? > > https://docs.google.com/document/d/1ApT0BcojnWQ4otJYFotan2M0pxsxbJQSdbkhIdXX4E8/edit?tab=t.0 > > > Farzaneh > > > On Thu, Apr 24, 2025 at 3:16?PM Kathy Kleiman > wrote: > >> Feel free to say reviewed and endorsed by NCSG & Farzi (if all agree)! >> On 4/24/2025 12:45 PM, Tomslin Samme-Nlar wrote: >> >> Yes, Let's send it with the suggested addition about who did the HRIA >> analysis that Kathy mentioned. >> >> Remain blessed, >> Tomslin >> >> >> On Thu, 17 Apr 2025 at 09:01, Kathy Kleiman >> wrote: >> >>> Tx Farzi, the analysis is sharp, clear, and expert! * Question: Should >>> there be more information in a header as to who did this HRIA analysis and >>> their background?* >>> >>> This doc is a great new addition to ICANN's review of the GAC communique! >>> >>> Best, Kathy >>> On 4/16/2025 3:34 PM, farzaneh badii wrote: >>> >>> Hi all >>> >>> This is what we wrote on GAC communique and human rights. Can the PC >>> look over this and decide on whether Rafik should send it to GAC's chair? >>> >>> >>> https://docs.google.com/document/d/1ApT0BcojnWQ4otJYFotan2M0pxsxbJQSdbkhIdXX4E8/edit?tab=t.0 >>> >>> Best regards, >>> >>> Farzaneh >>> >>> _______________________________________________ >>> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc >>> >>> _______________________________________________ >>> NCSG-PC mailing list >>> NCSG-PC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >>> >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > Rafik Dammak @rafik "fight for the users" -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Sat May 17 12:55:43 2025 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Sat, 17 May 2025 19:55:43 +1000 Subject: [NCSG-PC] Please comment /GAC Communique HRIA In-Reply-To: References: <30097ff8-4b9e-4015-a966-d06ed978e123@KathyKleiman.com> Message-ID: ? Tomslin reacted via Gmail On Sat, 17 May 2025, 10:01 farzaneh badii, wrote: > Hi all > > I made the changes, Rafik you can send the letter to NCSG again when you > get a chance, and we can send it off to GAC next week. Here are the people > we should send it to: > > Nico: GAC Chair > GAC Human Rights Group > Perhaps Manal? > > https://docs.google.com/document/d/1ApT0BcojnWQ4otJYFotan2M0pxsxbJQSdbkhIdXX4E8/edit?tab=t.0 > > > Farzaneh > > > On Thu, Apr 24, 2025 at 3:16?PM Kathy Kleiman > wrote: > >> Feel free to say reviewed and endorsed by NCSG & Farzi (if all agree)! >> On 4/24/2025 12:45 PM, Tomslin Samme-Nlar wrote: >> >> Yes, Let's send it with the suggested addition about who did the HRIA >> analysis that Kathy mentioned. >> >> Remain blessed, >> Tomslin >> >> >> On Thu, 17 Apr 2025 at 09:01, Kathy Kleiman >> wrote: >> >>> Tx Farzi, the analysis is sharp, clear, and expert! * Question: Should >>> there be more information in a header as to who did this HRIA analysis and >>> their background?* >>> >>> This doc is a great new addition to ICANN's review of the GAC communique! >>> >>> Best, Kathy >>> On 4/16/2025 3:34 PM, farzaneh badii wrote: >>> >>> Hi all >>> >>> This is what we wrote on GAC communique and human rights. Can the PC >>> look over this and decide on whether Rafik should send it to GAC's chair? >>> >>> >>> https://docs.google.com/document/d/1ApT0BcojnWQ4otJYFotan2M0pxsxbJQSdbkhIdXX4E8/edit?tab=t.0 >>> >>> Best regards, >>> >>> Farzaneh >>> >>> _______________________________________________ >>> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc >>> >>> _______________________________________________ >>> NCSG-PC mailing list >>> NCSG-PC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >>> >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> > -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/vnd.google.email-reaction+json Size: 37 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Sun May 18 10:01:01 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Sun, 18 May 2025 16:01:01 +0900 Subject: [NCSG-PC] Public Comment proceeding now open for the How We Meet project In-Reply-To: References: <9FCC8463-B870-4F0E-8814-8D8C87C3C440@icann.org> Message-ID: Hi Tomslin, I left some comments and I believe one needs resolution. Rafik Le sam. 17 mai 2025 ? 09:29, Tomslin Samme-Nlar a ?crit : > Hi NCSG, > > The draft being put together by Yao and team can be found here [ > https://docs.google.com/document/d/1BJqZx8AuwQNJONaBLiONDdyoJNC51GfInKjAMaZUDy0/edit?usp=drivesdk] > for your review. > Please keep in mind that the comment period closes on 19th of May. > > Remain blessed, > Tomslin > > On Fri, 11 Apr 2025, 05:16 Tomslin Samme-Nlar, > wrote: > >> Thank you for sharing, Rafik. >> >> Hi all, >> if you'd like to volunteer for the drafting of the comment, please let me >> know. >> I have created a Google doc >> >> which is populated with the comment template to ease the drafting. >> >> Warmly, >> Tomslin >> >> >> On Thu, 10 Apr 2025 at 12:13, Rafik Dammak >> wrote: >> >>> hi all, >>> >>> A new public comment proceeding is open now , this time about the topic >>> of How We Meet which was also covered in session in the last ICANN meeting >>> in Seattle. We shared input previously regarding a draft proposal. >>> @Tomslin Samme-Nlar will follow-up with regard >>> to volunteers for drafting NCSG comments. >>> >>> Best, >>> >>> Rafik >>> >>> ---------- Forwarded message --------- >>> >>> Dear community leaders, >>> >>> We are pleased to inform you that the Public Comment proceeding for the >>> How We Meet project has opened, and will close on *Monday 19 May* after >>> the requisite 40-day comment period: >>> https://www.icann.org/en/public-comment/proceeding/how-we-meet-reviewing-the-implementation-of-the-icann-public-meetings-strategy-09-04-2025. >>> We?d like to take this opportunity to thank you all for the collaborative >>> and collegial discussions, including the initial conversations last year at >>> ICANN80 that saw us hold an informal community consultation, paving the way >>> for the more targeted project that is currently underway. We hope that you >>> will also encourage your respective communities to submit input during this >>> Public Comment proceeding, which in some cases can augment or confirm prior >>> feedback they provided previously. >>> >>> >>> >>> As you concurrently plan your groups? sessions for ICANN83 and the rest >>> of the year, we thought it might be useful to share the intended project >>> timeline with you: >>> >>> - Wednesday 9 April: Public Comment proceeding opens >>> - Monday 19 May: Public Comment proceeding closes (40 days) >>> - Wednesday 21 May: Staff to share initial analysis of Public >>> Comments with the How We Meet Community Discussion Group >>> - Thursday 22 May: Community Discussion Group meeting to review and >>> discuss the initial analysis >>> - ICANN83: Working Session for the Community Discussion Group to >>> continue discussions (open to the community to attend) >>> - End-June (planned): Report updated >>> >>> >>> >>> Thank you! >>> >>> >>> >>> Cheers >>> >>> Mary (on behalf of the staff supporting the How We Meet project) >>> >>> Virus-free.www.avg.com <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> -------------- next part -------------- An HTML attachment was scrubbed... URL: From michaela.shapiro at article19.org Mon May 19 14:02:17 2025 From: michaela.shapiro at article19.org (Michaela Nakayama Shapiro) Date: Mon, 19 May 2025 11:02:17 +0000 Subject: [NCSG-PC] Fwd: ICANN83 session participation request: RrSG DNS Abuse: Example Review and Panel Discussion In-Reply-To: References: <03d95705-f733-4d96-bfa3-6ea2374cd25b.05b495a4-acd5-4405-a5fb-09b87eaaeafb.f7bab3ae-4833-4bcf-8d58-1f8fd79a98fe@emailsignatures365.codetwo.com> Message-ID: INTERNAL INTERNAL Hi Rafik, Thank you for thinking of me. I would be happy to participate in the session. In terms of examples of abuse reports, I?m not entirely clear on what they are looking for, but I have compiled a couple of examples below that I?m aware of that have had a negative impact on freedom of expression, which would provide a human rights angle to the discussion. ARTICLE 19 is following the topic of DNS abuse to advocate for the preservation of ICANN?s narrow definition of DNS abuse, and to broaden the ICANN?s community awareness of how domain blocking as part of DNS abuse ?mitigation? can be used as a tool to limit freedom of expression. It is with this lens in mind that I selected the examples below, but I would be happy to amend if this is not what they are looking for. I?m also happy to be put in touch with the session organizers directly if that would be helpful. @farzaneh badii, @Sara Ali, others, if there examples you would like to contribute, please feel free to share! Best, Michaela -- 1. In March 2025, a number of independent media websites were blocked from using the domain ?.ni?. Among those affected were Confidencial, La Prensa, 100% Noticias, and Onda Local. The measure was carried out by the government-run National Engineering University (UNI), the institution that administers all the domains under .ni, via NIC.NI, the organization charged with the administration and functioning of the geographic top-level domain corresponding to Nicaragua. This measure represents an additional attack on independent journalism in Nicaragua, where the dictatorship has closed or confiscated 61 Nicaraguan media outlets. Report of this incident can be found here. 2. The Venezuelan organization, Ve Sin Filtros, published a report documenting digital censorship during Venezuela?s electoral period (spanning July 2024 ? January 2025). During this period, the organization documented the blocking of domains that hosted content on human rights issues, social networking, political criticism, new media, and censorship circumvention tools (among other areas). The report outlines the impact on the media sector and provides insights into the broader digital environment in Venezuela. Michaela Nakayama Shapiro (she/her/hers) Programme Officer - Censorship [Logo.png] Defending freedom of expression and information www.article19.org Subscribe to our Newsletter [cid:newsletter_02744340-c607-4374-8a37-11b8b216096d.png] Follow us [Bluesky1x.png] [cid:facebook_2853baa0-f060-42e6-b448-6a8788c1b5dd.png] [cid:youtube_ffe95af1-d962-4acd-ab59-4eb4ea07466e.png] [cid:linkedin_199dc89c-14aa-41cd-b2a7-37b8ae8d667d.png] [cid:instagram_05fbcc72-6df2-442b-8c34-146d0e9d8c41.png] [cid:x_d21e0607-da5a-44a7-80c7-e2d86bc18a92.png] [women-journalists-banner.jpeg] From: NCSG-PC on behalf of Rafik Dammak Date: Friday, 16 May 2025 at 23:56 To: ncsg-pc Subject: [NCSG-PC] Fwd: ICANN83 session participation request: RrSG DNS Abuse: Example Review and Panel Discussion Hi all, RrSG is asking if we can designate a representative from NCSG to be in their session "DNS Abuse: Example Review and Panel Discussion" on Wednesday, 11 June, from 10:45 am to 12:15 pm local time. As Farzaneh will be a speaker in ALAC plenary on DNS abuse, I think Michaela can join this session as NCSG rep. Any concern? Best, Rafik ---------- Forwarded message --------- Hello Rafik, The RrSG is planning our ICANN83 session ?DNS Abuse: Example Review and Panel Discussion?, where we will invite panelists from across the ICANN Community as well as session attendees to review examples of DNS Abuse reports and tell us what they think the best outcome would be. The goal of the session is to better understand varying perspectives on how DNS Abuse is addressed and consider what further work is necessary to further improve the security, stability, and resilience of the DNS. This session will take place in Prague on Wednesday, 11 June, from 10:45 am to 12:15 pm local time. We invite you to designate someone from the NCSG to join the panel and to provide example DNS Abuse reports to use in the session; we need to confirm panelists and receive the examples by 4 June at the latest. If you prefer to do one but not the other (e.g. provide examples but not join the panel) we still appreciate your input; if you prefer not to participate at all, please let us know as soon as possible. We would ask you to provide two or three example DNS Abuse reports to be used in the session and encourage you to choose real-life reports instead of ?synthetic? or made up examples. Please remove any Personal Data before sharing. You may redact the domain as well; if you choose to do so, please let us know. Please provide the example exactly as you would report it to a registrar. While we will include all the provided examples in the session slides, we do not anticipate that we will be able to discuss all the examples provided by every group as the session will prioritize the discussion. Note that example scenarios will not be provided to panelists in advance of the session, in order to capture real-time and dynamic reactions to these situations. The audience will also be encouraged, via Zoom poll, to provide their own assessments. We look forward to hearing back from you and please don?t hesitate to reach out if you have any questions about this request. Thank you, Sarah Wyld RrSG Communications & Outreach Subgroup Lead in coordination with Luc Seufer & Reg Levy Co-Chairs RrSG DNS Abuse Subgroup -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo_1c766458-35ee-431a-9a22-e00b47cd2091.png Type: image/png Size: 6889 bytes Desc: logo_1c766458-35ee-431a-9a22-e00b47cd2091.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: newsletter_02744340-c607-4374-8a37-11b8b216096d.png Type: image/png Size: 379 bytes Desc: newsletter_02744340-c607-4374-8a37-11b8b216096d.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bluesky1x_864ef831-9476-4116-88b8-2a3410741630.png Type: image/png Size: 788 bytes Desc: bluesky1x_864ef831-9476-4116-88b8-2a3410741630.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: facebook_2853baa0-f060-42e6-b448-6a8788c1b5dd.png Type: image/png Size: 670 bytes Desc: facebook_2853baa0-f060-42e6-b448-6a8788c1b5dd.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: youtube_ffe95af1-d962-4acd-ab59-4eb4ea07466e.png Type: image/png Size: 678 bytes Desc: youtube_ffe95af1-d962-4acd-ab59-4eb4ea07466e.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: linkedin_199dc89c-14aa-41cd-b2a7-37b8ae8d667d.png Type: image/png Size: 720 bytes Desc: linkedin_199dc89c-14aa-41cd-b2a7-37b8ae8d667d.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: instagram_05fbcc72-6df2-442b-8c34-146d0e9d8c41.png Type: image/png Size: 840 bytes Desc: instagram_05fbcc72-6df2-442b-8c34-146d0e9d8c41.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: x_d21e0607-da5a-44a7-80c7-e2d86bc18a92.png Type: image/png Size: 895 bytes Desc: x_d21e0607-da5a-44a7-80c7-e2d86bc18a92.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: women-journalists-banner_b1cece5c-a86d-452f-b9f8-9e72943680f6.jpeg Type: image/jpeg Size: 15471 bytes Desc: women-journalists-banner_b1cece5c-a86d-452f-b9f8-9e72943680f6.jpeg URL: From rafik.dammak at gmail.com Mon May 19 15:54:39 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Mon, 19 May 2025 21:54:39 +0900 Subject: [NCSG-PC] Fwd: ICANN83 session participation request: RrSG DNS Abuse: Example Review and Panel Discussion In-Reply-To: References: <03d95705-f733-4d96-bfa3-6ea2374cd25b.05b495a4-acd5-4405-a5fb-09b87eaaeafb.f7bab3ae-4833-4bcf-8d58-1f8fd79a98fe@emailsignatures365.codetwo.com> Message-ID: Hi Michaela, I will send your name and I believe Sarah will be in touch with you to prepare for the session. certainly, if Farzaneh, Sara and you can work to prepare the examples, that would be great. Best, Rafik Le lun. 19 mai 2025 ? 20:02, Michaela Nakayama Shapiro < michaela.shapiro at article19.org> a ?crit : > INTERNAL > > INTERNAL > > Hi Rafik, > > > > Thank you for thinking of me. I would be happy to participate in the > session. > > > > In terms of examples of abuse reports, I?m not entirely clear on what they > are looking for, but I have compiled a couple of examples below that I?m > aware of that have had a negative impact on freedom of expression, which > would provide a human rights angle to the discussion. ARTICLE 19 is > following the topic of DNS abuse to advocate for the preservation of > ICANN?s narrow definition of DNS abuse, and to broaden the ICANN?s > community awareness of how domain blocking as part of DNS abuse > ?mitigation? can be used as a tool to limit freedom of expression. It is > with this lens in mind that I selected the examples below, but I would be > happy to amend if this is not what they are looking for. > > > > I?m also happy to be put in touch with the session organizers directly if > that would be helpful. @farzaneh badii , @Sara > Ali , others, if there examples you would like > to contribute, please feel free to share! > > > > Best, > > > > Michaela > > > > -- > > > > 1. In March 2025, a number of independent media websites were blocked > from using the domain ?.ni?. Among those affected were *Confidencial, > La Prensa, 100% Noticias, and Onda Local*. The measure was carried out > by the government-run National Engineering University (UNI), the > institution that administers all the domains under .ni, via NIC.NI, > the organization charged with the administration and functioning of the > geographic top-level domain corresponding to Nicaragua. This measure > represents an additional attack on independent journalism in Nicaragua, > where the dictatorship has closed or confiscated 61 Nicaraguan media > outlets. Report of this incident can be found here > > . > 2. The Venezuelan organization, Ve Sin Filtros, published a report > > documenting digital censorship during Venezuela?s electoral period > (spanning July 2024 ? January 2025). During this period, the organization > documented the blocking of domains that hosted content on human rights > issues, social networking, political criticism, new media, and censorship > circumvention tools (among other areas). The report outlines the impact on > the media sector and provides insights into the broader digital environment > in Venezuela. > > > *Michaela Nakayama Shapiro *(she/her/hers) > Programme Officer - Censorship > [image: Logo.png] Defending freedom of > expression > and information > *www.article19.org* Subscribe to our > Newsletter > > Follow us > [image: Bluesky1x.png] > > > > > > [image: women-journalists-banner.jpeg] > > > *From: *NCSG-PC on behalf of Rafik Dammak > > *Date: *Friday, 16 May 2025 at 23:56 > *To: *ncsg-pc > *Subject: *[NCSG-PC] Fwd: ICANN83 session participation request: RrSG DNS > Abuse: Example Review and Panel Discussion > > Hi all, > > > > RrSG is asking if we can designate a representative from NCSG to be in > their session "DNS Abuse: Example Review and Panel Discussion" on > Wednesday, 11 June, from 10:45 am to 12:15 pm local time. > > > > As Farzaneh will be a speaker in ALAC plenary on DNS abuse, I think > Michaela can join this session as NCSG rep. Any concern? > > > > Best, > > > > Rafik > > ---------- Forwarded message --------- > > Hello Rafik, > > > > The RrSG is planning our ICANN83 session ?DNS Abuse: Example Review and > Panel Discussion?, where we will invite panelists from across the ICANN > Community as well as session attendees to review examples of DNS Abuse > reports and tell us what they think the best outcome would be. > > > > The goal of the session is to better understand varying perspectives on > how DNS Abuse is addressed and consider what further work is necessary to > further improve the security, stability, and resilience of the DNS. > > > > This session will take place in Prague on *Wednesday, 11 June, from 10:45 > am to 12:15 pm *local time. > > > > *We invite you to designate someone from the NCSG to join the panel and to > provide example DNS Abuse reports to use in the session; we need to confirm > panelists and receive the examples by 4 June at the latest.* > > > > If you prefer to do one but not the other (e.g. provide examples but not > join the panel) we still appreciate your input; if you prefer not to > participate at all, please let us know as soon as possible. > > > > We would ask you to provide two or three example DNS Abuse reports to be > used in the session and encourage you to choose real-life reports instead > of ?synthetic? or made up examples. Please remove any Personal Data before > sharing. You may redact the domain as well; if you choose to do so, please > let us know. Please provide the example exactly as you would report it to a > registrar. > > > > While we will include all the provided examples in the session slides, we > do not anticipate that we will be able to discuss all the examples provided > by every group as the session will prioritize the discussion. Note that > example scenarios will * not* be provided to panelists in advance of the > session, in order to capture real-time and dynamic reactions to these > situations. The audience will also be encouraged, via Zoom poll, to provide > their own assessments. > > > > We look forward to hearing back from you and please don?t hesitate to > reach out if you have any questions about this request. > > > > Thank you, > > > > Sarah Wyld > > RrSG Communications & Outreach Subgroup Lead > > > > in coordination with > > Luc Seufer & Reg Levy > > Co-Chairs RrSG DNS Abuse Subgroup > Virus-free.www.avg.com <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo_1c766458-35ee-431a-9a22-e00b47cd2091.png Type: image/png Size: 6889 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: newsletter_02744340-c607-4374-8a37-11b8b216096d.png Type: image/png Size: 379 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bluesky1x_864ef831-9476-4116-88b8-2a3410741630.png Type: image/png Size: 788 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: facebook_2853baa0-f060-42e6-b448-6a8788c1b5dd.png Type: image/png Size: 670 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: youtube_ffe95af1-d962-4acd-ab59-4eb4ea07466e.png Type: image/png Size: 678 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: linkedin_199dc89c-14aa-41cd-b2a7-37b8ae8d667d.png Type: image/png Size: 720 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: instagram_05fbcc72-6df2-442b-8c34-146d0e9d8c41.png Type: image/png Size: 840 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: x_d21e0607-da5a-44a7-80c7-e2d86bc18a92.png Type: image/png Size: 895 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: women-journalists-banner_b1cece5c-a86d-452f-b9f8-9e72943680f6.jpeg Type: image/jpeg Size: 15471 bytes Desc: not available URL: From rafik.dammak at gmail.com Tue May 20 17:24:12 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Tue, 20 May 2025 23:24:12 +0900 Subject: [NCSG-PC] Board Seat 14 Recommendations In-Reply-To: <9F59BD5E-7CC4-44EA-BD13-05265E0DAC57@icann.org> References: <9F59BD5E-7CC4-44EA-BD13-05265E0DAC57@icann.org> Message-ID: hi all, We received the final version of recommendations for board 14 coming from the small group. It will be one of the topics for discussion in our meeting with CSG in Prague. We , the members of the small group from NCSG, are in the PC list already so you can ask clarifying questions and comments. I will share it later in the NCSG list. Best, Rafik ---------- Forwarded message --------- Hello Mason & Rafik, Please find attached the recommendations from NCPH Team 14 regarding the Board Seat 14. Please note the selection committee noted in recommendation 2 will not be the selection committee which is noted in recommendation 3. Thank you. *Andrea Glandon* Policy Operations Sr. Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Virus-free.www.avg.com <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Team 14 Board Seat 14 Recommendations .pdf Type: application/pdf Size: 78297 bytes Desc: not available URL: From rafik.dammak at gmail.com Wed May 21 12:51:48 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Wed, 21 May 2025 18:51:48 +0900 Subject: [NCSG-PC] [NCSG-EC] Topics/agenda for NCPH session in prague In-Reply-To: References: Message-ID: Hi all, I had call with CSG lead and there was some update about the agenda, following it: - Regarding the RDRS issue, they are removing it from the agenda - Regarding ICP, Philippe will handle the briefing ? no preparation necessary. The objective is to see if there?s common ground following his intervention. Is there any other comment ? Any additional topics we want to add? Best, Rafik Le sam. 17 mai 2025 ? 10:21, Rafik Dammak a ?crit : > Hi Farzaneh, > > Yes other than board seat and GNSO election, the other topics were > proposed by CSG leaders and I didn't discuss yet with them. For leading > topics, we can assign a lead from our side. I will ask about the RDRS topic. > > I think we can talk about any topic and we can clarify what we want as > outcome knowing the difference on opinions between NCSG and CSG. > > Best, > > Rafik > > On Sat, May 17, 2025, 10:07 farzaneh badii > wrote: > >> So am I right that most of the topics are led by them? And what does RDRS >> decision transparency mean? >> >> Is it too soon for this rejuvenated meeting to talk about tricky issues >> like dns abuse and accuracy? >> >> Farzaneh >> >> >> On Fri, May 16, 2025 at 8:43?PM Tomslin Samme-Nlar via NCSG-EC < >> ncsg-ec at lists.ncsg.is> wrote: >> >>> Looks enough. >>> >>> Remain blessed, >>> Tomslin >>> >>> On Fri, 16 May 2025, 19:19 Rafik Dammak via NCSG-EC, < >>> ncsg-ec at lists.ncsg.is> wrote: >>> >>>> Hi all, >>>> >>>> I am discussing with CSG leadership about topics for discussion for our >>>> session in Prague and the proposed those in the attached slides. >>>> >>>> I think those topics are OK while I am not sure how much we will be >>>> interested by ICP2 one. I will check about the item of issues of common >>>> ground. Initially I proposed the topic of seat 14 and GNSO election. But I >>>> would like to get any proposal from our side or to hear if there is any >>>> concern. >>>> >>>> Best, >>>> >>>> Rafik >>>> _______________________________________________ >>>> NCSG-EC mailing list >>>> NCSG-EC at lists.ncsg.is >>>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>>> >>> _______________________________________________ >>> NCSG-EC mailing list >>> NCSG-EC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>> >> Virus-free.www.avg.com <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Wed May 21 12:57:15 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Wed, 21 May 2025 18:57:15 +0900 Subject: [NCSG-PC] [Ext] [NCSG-EC] Topics for joint meeting with ALAC In-Reply-To: References: <404951C3-4FDC-4BE8-AAF3-F12735F4CA96@icann.org> <1cebc4f0-440e-46d5-9a64-04954055ea59@KathyKleiman.com> Message-ID: hi all, This is the agenda for the NCSG-ALAC meeting: *Agenda:* 1. Welcome and session overview - Jonathan Zuck, ALAC Chair and Rafik Dammak, NCSG Chair (5 min) 2. ICANN Reviews (20 mins) 3. ICANN Community Participant Code of Conduct Concerning SOIs (15 mins) 4. New gTLD Program Next Round Applicant Support (20 mins) 5. Human Rights Impact Assessment (HRIA) on DNS Abuse (10 mins) 6. Next Steps and Closing Remarks - Jonathan Zuck, ALAC Chair and Rafik Dammak, NCSG Chair (5 mins) we need to identify a lead/speaker for each topic, I am guessing that would be: - ICANN reviews: ? - CoC: Manju - Applicant support: Kathy/Pedro - HRIA: Farzaneh/Michaela Best, Rafik Le ven. 16 mai 2025 ? 18:48, Rafik Dammak a ?crit : > Hi Manju, > > Thanks for the suggestion, I will add that. I think we got a decent list > and we can work on the lead discussant for each. > I will share this with alac. > > Best, > > Rafik > > On Fri, May 16, 2025, 14:02 Manju wrote: > >> Hi Rafik, >> >> Maybe we can add SOI too since the updated Board document will be >> published for public comments soon. >> >> Thanks! >> >> Best, >> Manju >> >> On Thu, May 15, 2025 at 10:16?PM Kathy Kleiman >> wrote: >> >>> That sounds like a good list, Rafik. Perhaps they'll have some other >>> items to add? >>> >>> Best, Kathy >>> On 5/15/2025 10:02 AM, Rafik Dammak wrote: >>> >>> Hi all, >>> >>> We need to respond to alac. Till now we got the topics of reviews, >>> applicant support, HRIA and DNS abuse. >>> >>> Best, >>> >>> Rafik >>> >>> >>> On Sat, May 10, 2025, 01:16 Andrea Glandon >>> wrote: >>> >>>> Hello all! >>>> >>>> >>>> >>>> Kind reminder to work on topics for the joint session with ALAC. >>>> At-Large staff is working on confirming the agenda. >>>> >>>> >>>> >>>> Thanks! >>>> >>>> Kind Regards, >>>> >>>> Andrea >>>> >>>> >>>> >>>> >>>> >>>> *From: *NCSG-EC on behalf of Rafik >>>> Dammak via NCSG-EC >>>> *Reply-To: *Rafik Dammak >>>> *Date: *Wednesday, April 30, 2025 at 07:09 >>>> *To: *ncsg-pc , NCSG EC >>>> *Subject: *[Ext] [NCSG-EC] Topics for joint meeting with ALAC >>>> >>>> >>>> >>>> Hi all, >>>> >>>> >>>> >>>> ALAC reached out asking about topics we want to discuss with them. >>>> Please share your suggestion and/or if you want to volunteer to lead the >>>> topic. >>>> >>>> >>>> >>>> Best, >>>> >>>> >>>> >>>> Rafik >>>> >>> Rafik Dammak >>> @rafik >>> "fight for the users" >>> >>> _______________________________________________ >>> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://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 >>> >> Virus-free.www.avg.com <#m_-4728882106042814163_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Wed May 21 15:23:21 2025 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Wed, 21 May 2025 22:23:21 +1000 Subject: [NCSG-PC] ALAC plenary in Prague meeting In-Reply-To: References: Message-ID: Hi Rafik, Farzi is leading our effort in the council small team as well. So, happy fo her to represent us. Remain blessed, Tomslin On Fri, 16 May 2025 at 00:00, Rafik Dammak wrote: > Hi all, > > At-large invited me to speak on their plenary on Prague "What?s Next on > DNS Abuse: Progressing Mitigation Efforts within ICANN" . However, it will > be in same time with a NCSG session and I don't believe I am the right > person to speak there. They accepted that I propose another representative > from NCSG. I am thinking to suggest Farzaneh as she is following this topic > closely and spoke on our behalf. > I need to respond asap as they will start their planning soon. > > Best, > > Rafik > > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Wed May 21 15:28:05 2025 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Wed, 21 May 2025 22:28:05 +1000 Subject: [NCSG-PC] ICANN83 PC Meetings Proposed Agenda Message-ID: Hi all, Here is what I have so far as a proposed agenda for both our meetings. I assume we'd like to prep for the bilaterals like we did in Seattle? Workshop 2 still has room for a topic or two. You can suggest topics on the Google doc here ICANN83 NCSG Policy Meeting - Workshop 1 of 2 1. Welcome (5 mins) 2. Review of GNSO Council agenda for meeting scheduled on Wednesday, 11 June - Tomslin (45 mins) 3. Public Comments - Tomslin (10 mins) 4. AOB (15 mins) ICANN83 NCSG Policy Meeting - Workshop 2 of 2 1. Welcome (5 mins) 2. Applicant Guide Book Presentation - ICANN Staff (20 mins) 3. Joint Meetings Planning (45mins) 4. AOB?? (30mins) Remain blessed, Tomslin -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Wed May 21 15:41:50 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Wed, 21 May 2025 21:41:50 +0900 Subject: [NCSG-PC] ICANN83 PC Meetings Proposed Agenda In-Reply-To: References: Message-ID: Hi Tomslin, Few comments: - for AGB we can allocate 30min - the second PC session will be after the council informal meeting I believe so it is an opportunity to prepare for council public meeting based on that - which bilaterals GNSO council is having?or you mean for NCSG joint sessions? Best, Rafik On Wed, May 21, 2025, 21:28 Tomslin Samme-Nlar wrote: > Hi all, > > Here is what I have so far as a proposed agenda for both our meetings. I > assume we'd like to prep for the bilaterals like we did in Seattle? > Workshop 2 still has room for a topic or two. You can suggest topics on > the Google doc here > > > ICANN83 NCSG Policy Meeting - Workshop 1 of 2 > > > 1. > > Welcome (5 mins) > 2. > > Review of GNSO Council agenda > for meeting > scheduled on Wednesday, 11 June - Tomslin (45 mins) > 3. > > Public Comments - Tomslin > (10 mins) > 4. > > AOB (15 mins) > > > > ICANN83 NCSG Policy Meeting - Workshop 2 of 2 > > > 1. > > Welcome (5 mins) > 2. > > Applicant Guide Book Presentation - ICANN Staff (20 mins) > 3. > > Joint Meetings Planning (45mins) > 4. > > AOB?? (30mins) > > > > Remain blessed, > Tomslin > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kathy at KathyKleiman.com Wed May 21 19:04:21 2025 From: Kathy at KathyKleiman.com (Kathy Kleiman) Date: Wed, 21 May 2025 12:04:21 -0400 Subject: [NCSG-PC] Proposing a new addition Message-ID: <68ab927a-448d-41fa-88f5-8639d4d1d6b8@KathyKleiman.com> Dear NCSG PC, I would like to propose the addition of Pedro de Perdig?o Lana to this list. Pedro, as many of you know, is the wizard behind many of our recent comments. He is tireless in his work bringing new and old members together, holding organizing calls, doing the follow-up emails, editing, and finalizing comments for submission. /I would say that this work has been invaluable in the last year, and before. / That is not to take away from Farzi, Michaela, and everyone else, all amazing! We are a good team. But in many of the Applicant Guidebook and related comments, and in our tireless (and little known work) on the Rights Protection Mechanisms Implementation Review Team, Pedro and I wrote endless emails and together reviewed many drafts of educational materials (for the RPM IRT), edited new versions of the Trademark Claims Notice (also RPM IRT), and worked with a larger group of NCSG members to review and offer edits to many sections of the Applicant Guidebook (comments to SubPro IRT).? Together, we hope we made key ICANN texts easier and more understandable to registrants and newcomers. Recognizing everyone's incredible efforts, on the matters above, it is Pedro who finalized many of our comments and, after approval by the PC, then worked with Tomslin to submit. /To make his communication easier with this Policy Committee, and recognize his ongoing work as a leader, teacher and writer of policy comments in our community, I recommend that Pedro de Perdig?o Lana be added to our PC list./ /Best regards,/ /Kathy/ / / -------------- next part -------------- An HTML attachment was scrubbed... URL: From wisdom.dk at gmail.com Wed May 21 19:32:21 2025 From: wisdom.dk at gmail.com (Wisdom Donkor) Date: Wed, 21 May 2025 16:32:21 +0000 Subject: [NCSG-PC] Proposing a new addition In-Reply-To: <68ab927a-448d-41fa-88f5-8639d4d1d6b8@KathyKleiman.com> References: <68ab927a-448d-41fa-88f5-8639d4d1d6b8@KathyKleiman.com> Message-ID: I support the addition of Pedro. *Wisdom Donkor* (CASP+, CISM, CEH Certified,) President & CEO Africa Open Data and Internet Research Foundation (AODIRF) | Africa Geospatial Data and Internet Conference (AGDIC) P.O. Box CT 2439, Cantonments, Accra | www.aodirf.org / www. agdic.info Tel: +233 20 812 8851 Skype: wisdom_dk | Facebook: kwasi wisdom | Twitter: @wisdom_dk _______________________________________________________________________________________________________________________ ICANN GNSO Council Member | ICANN transfer policy review working group Member | Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) | UN IGF MAG Member | IGF Support Fund Association Executive Committee Member, World Bank Independent Consultant | AU AFIGF Member | Ghana OGP Advisory Committee member | GSS SDGs Advisory Committee Member ____________________________________________________________________________________________ Specialization: E-government Network Infrastructure and E-application, Internet Governance, Open Data policies platforms & Community Development, Cyber Security, Geospatial Technologies, Open Source Technologies, Domain Name Systems, Human Resource Planning and Development, Software Engineering, Event Planning & Management, On Wed, 21 May 2025, 4:04?pm Kathy Kleiman, wrote: > Dear NCSG PC, > > I would like to propose the addition of Pedro de Perdig?o Lana to this > list. > > Pedro, as many of you know, is the wizard behind many of our recent > comments. He is tireless in his work bringing new and old members together, > holding organizing calls, doing the follow-up emails, editing, and > finalizing comments for submission. > *I would say that this work has been invaluable in the last year, and > before. * > > That is not to take away from Farzi, Michaela, and everyone else, all > amazing! We are a good team. > > But in many of the Applicant Guidebook and related comments, and in our > tireless (and little known work) on the Rights Protection Mechanisms > Implementation Review Team, Pedro and I wrote endless emails and together > reviewed many drafts of educational materials (for the RPM IRT), edited new > versions of the Trademark Claims Notice (also RPM IRT), and worked with a > larger group of NCSG members to review and offer edits to many sections of > the Applicant Guidebook (comments to SubPro IRT). Together, we hope we > made key ICANN texts easier and more understandable to registrants and > newcomers. > > Recognizing everyone's incredible efforts, on the matters above, it is > Pedro who finalized many of our comments and, after approval by the PC, > then worked with Tomslin to submit. *To make his communication easier > with this Policy Committee, and recognize his ongoing work as a leader, > teacher and writer of policy comments in our community, I recommend that > Pedro de Perdig?o Lana be added to our PC list.* > > *Best regards,* > > *Kathy* > > > _______________________________________________ > 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 michaela.shapiro at article19.org Wed May 21 22:58:33 2025 From: michaela.shapiro at article19.org (Michaela Nakayama Shapiro) Date: Wed, 21 May 2025 19:58:33 +0000 Subject: [NCSG-PC] Proposing a new addition In-Reply-To: References: <68ab927a-448d-41fa-88f5-8639d4d1d6b8@KathyKleiman.com> <03d95705-f733-4d96-bfa3-6ea2374cd25b.05b495a4-acd5-4405-a5fb-09b87eaaeafb.df1e68e1-cfaa-4949-85fe-f817375ac9a6@emailsignatures365.codetwo.com> Message-ID: INTERNAL INTERNAL I couldn?t agree more with Kathy! Pedro has been invaluable in leading and coordinating several policy inputs on behalf of the NCSG. It would be great to have him here as part of the list. Best, Michaela Michaela Nakayama Shapiro (she/her/hers) Programme Officer - Censorship [Logo.png] Defending freedom of expression and information www.article19.org Subscribe to our Newsletter [cid:newsletter_02744340-c607-4374-8a37-11b8b216096d.png] Follow us [Bluesky1x.png] [cid:facebook_2853baa0-f060-42e6-b448-6a8788c1b5dd.png] [cid:youtube_ffe95af1-d962-4acd-ab59-4eb4ea07466e.png] [cid:linkedin_199dc89c-14aa-41cd-b2a7-37b8ae8d667d.png] [cid:instagram_05fbcc72-6df2-442b-8c34-146d0e9d8c41.png] [cid:x_d21e0607-da5a-44a7-80c7-e2d86bc18a92.png] [women-journalists-banner.jpeg] ________________________________ From: NCSG-PC on behalf of Wisdom Donkor Sent: Wednesday, May 21, 2025 5:32:21 PM To: Kathy Kleiman Cc: ncsg-pc Subject: Re: [NCSG-PC] Proposing a new addition I support the addition of Pedro. Wisdom Donkor (CASP+, CISM, CEH Certified,) President & CEO Africa Open Data and Internet Research Foundation (AODIRF) | Africa Geospatial Data and Internet Conference (AGDIC) P.O. Box CT 2439, Cantonments, Accra | www.aodirf.org / www.agdic.info Tel: +233 20 812 8851 Skype: wisdom_dk | Facebook: kwasi wisdom | Twitter: @wisdom_dk _______________________________________________________________________________________________________________________ ICANN GNSO Council Member | ICANN transfer policy review working group Member | Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) | UN IGF MAG Member | IGF Support Fund Association Executive Committee Member, World Bank Independent Consultant | AU AFIGF Member | Ghana OGP Advisory Committee member | GSS SDGs Advisory Committee Member ____________________________________________________________________________________________ Specialization: E-government Network Infrastructure and E-application, Internet Governance, Open Data policies platforms & Community Development, Cyber Security, Geospatial Technologies, Open Source Technologies, Domain Name Systems, Human Resource Planning and Development, Software Engineering, Event Planning & Management, On Wed, 21 May 2025, 4:04?pm Kathy Kleiman, > wrote: Dear NCSG PC, I would like to propose the addition of Pedro de Perdig?o Lana to this list. Pedro, as many of you know, is the wizard behind many of our recent comments. He is tireless in his work bringing new and old members together, holding organizing calls, doing the follow-up emails, editing, and finalizing comments for submission. I would say that this work has been invaluable in the last year, and before. That is not to take away from Farzi, Michaela, and everyone else, all amazing! We are a good team. But in many of the Applicant Guidebook and related comments, and in our tireless (and little known work) on the Rights Protection Mechanisms Implementation Review Team, Pedro and I wrote endless emails and together reviewed many drafts of educational materials (for the RPM IRT), edited new versions of the Trademark Claims Notice (also RPM IRT), and worked with a larger group of NCSG members to review and offer edits to many sections of the Applicant Guidebook (comments to SubPro IRT). Together, we hope we made key ICANN texts easier and more understandable to registrants and newcomers. Recognizing everyone's incredible efforts, on the matters above, it is Pedro who finalized many of our comments and, after approval by the PC, then worked with Tomslin to submit. To make his communication easier with this Policy Committee, and recognize his ongoing work as a leader, teacher and writer of policy comments in our community, I recommend that Pedro de Perdig?o Lana be added to our PC list. Best regards, Kathy _______________________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo_1c766458-35ee-431a-9a22-e00b47cd2091.png Type: image/png Size: 6889 bytes Desc: logo_1c766458-35ee-431a-9a22-e00b47cd2091.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: newsletter_02744340-c607-4374-8a37-11b8b216096d.png Type: image/png Size: 379 bytes Desc: newsletter_02744340-c607-4374-8a37-11b8b216096d.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bluesky1x_864ef831-9476-4116-88b8-2a3410741630.png Type: image/png Size: 788 bytes Desc: bluesky1x_864ef831-9476-4116-88b8-2a3410741630.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: facebook_2853baa0-f060-42e6-b448-6a8788c1b5dd.png Type: image/png Size: 670 bytes Desc: facebook_2853baa0-f060-42e6-b448-6a8788c1b5dd.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: youtube_ffe95af1-d962-4acd-ab59-4eb4ea07466e.png Type: image/png Size: 678 bytes Desc: youtube_ffe95af1-d962-4acd-ab59-4eb4ea07466e.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: linkedin_199dc89c-14aa-41cd-b2a7-37b8ae8d667d.png Type: image/png Size: 720 bytes Desc: linkedin_199dc89c-14aa-41cd-b2a7-37b8ae8d667d.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: instagram_05fbcc72-6df2-442b-8c34-146d0e9d8c41.png Type: image/png Size: 840 bytes Desc: instagram_05fbcc72-6df2-442b-8c34-146d0e9d8c41.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: x_d21e0607-da5a-44a7-80c7-e2d86bc18a92.png Type: image/png Size: 895 bytes Desc: x_d21e0607-da5a-44a7-80c7-e2d86bc18a92.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: women-journalists-banner_b1cece5c-a86d-452f-b9f8-9e72943680f6.jpeg Type: image/jpeg Size: 15471 bytes Desc: women-journalists-banner_b1cece5c-a86d-452f-b9f8-9e72943680f6.jpeg URL: From mesumbeslin at gmail.com Thu May 22 00:50:14 2025 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Thu, 22 May 2025 07:50:14 +1000 Subject: [NCSG-PC] Proposing a new addition In-Reply-To: <68ab927a-448d-41fa-88f5-8639d4d1d6b8@KathyKleiman.com> References: <68ab927a-448d-41fa-88f5-8639d4d1d6b8@KathyKleiman.com> Message-ID: Hi Kathy, Thanks for the proposal. I note that such an addition is anticipated in the NCSG charter, as section *2.5.1. NCSG-PC Composition* of our charter states that "*The membership of the NCSG-PC may invite others to participate as observers*." As a result, I invite PC members to please comment/state their position on the request. Remain blessed, Tomslin On Thu, 22 May 2025, 02:04 Kathy Kleiman, wrote: > Dear NCSG PC, > > I would like to propose the addition of Pedro de Perdig?o Lana to this > list. > > Pedro, as many of you know, is the wizard behind many of our recent > comments. He is tireless in his work bringing new and old members together, > holding organizing calls, doing the follow-up emails, editing, and > finalizing comments for submission. > *I would say that this work has been invaluable in the last year, and > before. * > > That is not to take away from Farzi, Michaela, and everyone else, all > amazing! We are a good team. > > But in many of the Applicant Guidebook and related comments, and in our > tireless (and little known work) on the Rights Protection Mechanisms > Implementation Review Team, Pedro and I wrote endless emails and together > reviewed many drafts of educational materials (for the RPM IRT), edited new > versions of the Trademark Claims Notice (also RPM IRT), and worked with a > larger group of NCSG members to review and offer edits to many sections of > the Applicant Guidebook (comments to SubPro IRT). Together, we hope we > made key ICANN texts easier and more understandable to registrants and > newcomers. > > Recognizing everyone's incredible efforts, on the matters above, it is > Pedro who finalized many of our comments and, after approval by the PC, > then worked with Tomslin to submit. *To make his communication easier > with this Policy Committee, and recognize his ongoing work as a leader, > teacher and writer of policy comments in our community, I recommend that > Pedro de Perdig?o Lana be added to our PC list.* > > *Best regards,* > > *Kathy* > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Thu May 22 01:43:20 2025 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Thu, 22 May 2025 08:43:20 +1000 Subject: [NCSG-PC] ICANN83 PC Meetings Proposed Agenda In-Reply-To: References: Message-ID: Hi Rafik, Thanks for the comments. I will move the agenda around based on that. I was referring to the NCSG joint sessions like we used the first PC session in Seattle to prepare for them. Remain blessed, Tomslin On Wed, 21 May 2025 at 22:42, Rafik Dammak wrote: > Hi Tomslin, > > Few comments: > - for AGB we can allocate 30min > - the second PC session will be after the council informal meeting I > believe so it is an opportunity to prepare for council public meeting based > on that > - which bilaterals GNSO council is having?or you mean for NCSG joint > sessions? > > Best, > > Rafik > > > > On Wed, May 21, 2025, 21:28 Tomslin Samme-Nlar > wrote: > >> Hi all, >> >> Here is what I have so far as a proposed agenda for both our meetings. I >> assume we'd like to prep for the bilaterals like we did in Seattle? >> Workshop 2 still has room for a topic or two. You can suggest topics on >> the Google doc here >> >> >> ICANN83 NCSG Policy Meeting - Workshop 1 of 2 >> >> >> 1. >> >> Welcome (5 mins) >> 2. >> >> Review of GNSO Council agenda >> for meeting >> scheduled on Wednesday, 11 June - Tomslin (45 mins) >> 3. >> >> Public Comments - Tomslin >> (10 mins) >> 4. >> >> AOB (15 mins) >> >> >> >> ICANN83 NCSG Policy Meeting - Workshop 2 of 2 >> >> >> 1. >> >> Welcome (5 mins) >> 2. >> >> Applicant Guide Book Presentation - ICANN Staff (20 mins) >> 3. >> >> Joint Meetings Planning (45mins) >> 4. >> >> AOB?? (30mins) >> >> >> >> Remain blessed, >> Tomslin >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From manju4icann at gmail.com Thu May 22 03:34:46 2025 From: manju4icann at gmail.com (Manju) Date: Thu, 22 May 2025 08:34:46 +0800 Subject: [NCSG-PC] Proposing a new addition In-Reply-To: References: <68ab927a-448d-41fa-88f5-8639d4d1d6b8@KathyKleiman.com> Message-ID: Support to add Pedro to the list. Best, Manju On Thu, May 22, 2025 at 05:50 Tomslin Samme-Nlar wrote: > Hi Kathy, > > Thanks for the proposal. I note that such an addition is anticipated in > the NCSG charter, as section *2.5.1. NCSG-PC Composition* of our charter > states that > > "*The membership of the NCSG-PC may invite others to participate as > observers*." > > As a result, I invite PC members to please comment/state their position on > the request. > > Remain blessed, > Tomslin > > On Thu, 22 May 2025, 02:04 Kathy Kleiman, wrote: > >> Dear NCSG PC, >> >> I would like to propose the addition of Pedro de Perdig?o Lana to this >> list. >> >> Pedro, as many of you know, is the wizard behind many of our recent >> comments. He is tireless in his work bringing new and old members together, >> holding organizing calls, doing the follow-up emails, editing, and >> finalizing comments for submission. >> *I would say that this work has been invaluable in the last year, and >> before. * >> >> That is not to take away from Farzi, Michaela, and everyone else, all >> amazing! We are a good team. >> >> But in many of the Applicant Guidebook and related comments, and in our >> tireless (and little known work) on the Rights Protection Mechanisms >> Implementation Review Team, Pedro and I wrote endless emails and together >> reviewed many drafts of educational materials (for the RPM IRT), edited new >> versions of the Trademark Claims Notice (also RPM IRT), and worked with a >> larger group of NCSG members to review and offer edits to many sections of >> the Applicant Guidebook (comments to SubPro IRT). Together, we hope we >> made key ICANN texts easier and more understandable to registrants and >> newcomers. >> >> Recognizing everyone's incredible efforts, on the matters above, it is >> Pedro who finalized many of our comments and, after approval by the PC, >> then worked with Tomslin to submit. *To make his communication easier >> with this Policy Committee, and recognize his ongoing work as a leader, >> teacher and writer of policy comments in our community, I recommend that >> Pedro de Perdig?o Lana be added to our PC list.* >> >> *Best regards,* >> >> *Kathy* >> >> >> _______________________________________________ > 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 julf at Julf.com Thu May 22 09:24:00 2025 From: julf at Julf.com (Johan Helsingius) Date: Thu, 22 May 2025 08:24:00 +0200 Subject: [NCSG-PC] Proposing a new addition In-Reply-To: <68ab927a-448d-41fa-88f5-8639d4d1d6b8@KathyKleiman.com> References: <68ab927a-448d-41fa-88f5-8639d4d1d6b8@KathyKleiman.com> Message-ID: <4c8bed19-9bc6-4175-b365-90ff4dc51796@Julf.com> I strongly support adding Pedro to the list. Julf On 21/05/2025 18:04, Kathy Kleiman wrote: > Dear NCSG PC, > > I would like to propose the addition of Pedro de Perdig?o Lana to this > list. > > Pedro, as many of you know, is the wizard behind many of our recent > comments. He is tireless in his work bringing new and old members > together, holding organizing calls, doing the follow-up emails, editing, > and finalizing comments for submission. /I would say that this work has > been invaluable in the last year, and before. > / > > That is not to take away from Farzi, Michaela, and everyone else, all > amazing! We are a good team. > > But in many of the Applicant Guidebook and related comments, and in our > tireless (and little known work) on the Rights Protection Mechanisms > Implementation Review Team, Pedro and I wrote endless emails and > together reviewed many drafts of educational materials (for the RPM > IRT), edited new versions of the Trademark Claims Notice (also RPM IRT), > and worked with a larger group of NCSG members to review and offer edits > to many sections of the Applicant Guidebook (comments to SubPro IRT). > Together, we hope we made key ICANN texts easier and more understandable > to registrants and newcomers. > > Recognizing everyone's incredible efforts, on the matters above, it is > Pedro who finalized many of our comments and, after approval by the PC, > then worked with Tomslin to submit. /To make his communication easier > with this Policy Committee, and recognize his ongoing work as a leader, > teacher and writer of policy comments in our community, I recommend that > Pedro de Perdig?o Lana be added to our PC list./ > > /Best regards,/ > > /Kathy/ > > / > / > > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc From rafik.dammak at gmail.com Thu May 22 16:36:32 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Thu, 22 May 2025 22:36:32 +0900 Subject: [NCSG-PC] Joint session with SSAC Message-ID: Hi all, We will meet some of SSAC members in Prague meeting and we need to agree on 2 or 3 topics of interest to discuss with them . I assume DNS abuse and RDRS for example? Best, Rafik -------------- next part -------------- An HTML attachment was scrubbed... URL: From wisdom.dk at gmail.com Thu May 22 17:23:53 2025 From: wisdom.dk at gmail.com (Wisdom Donkor) Date: Thu, 22 May 2025 14:23:53 +0000 Subject: [NCSG-PC] Joint session with SSAC In-Reply-To: References: Message-ID: RDRS will be of interest. *Wisdom Donkor* (CASP+, CISM, CEH Certified,) President & CEO Africa Open Data and Internet Research Foundation (AODIRF) | Africa Geospatial Data and Internet Conference (AGDIC) P.O. Box CT 2439, Cantonments, Accra | www.aodirf.org / www. agdic.info Tel: +233 20 812 8851 Skype: wisdom_dk | Facebook: kwasi wisdom | Twitter: @wisdom_dk _______________________________________________________________________________________________________________________ ICANN GNSO Council Member | ICANN transfer policy review working group Member | Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) | UN IGF MAG Member | IGF Support Fund Association Executive Committee Member, World Bank Independent Consultant | AU AFIGF Member | Ghana OGP Advisory Committee member | GSS SDGs Advisory Committee Member ____________________________________________________________________________________________ Specialization: E-government Network Infrastructure and E-application, Internet Governance, Open Data policies platforms & Community Development, Cyber Security, Geospatial Technologies, Open Source Technologies, Domain Name Systems, Human Resource Planning and Development, Software Engineering, Event Planning & Management, On Thu, May 22, 2025 at 1:36?PM Rafik Dammak wrote: > Hi all, > > We will meet some of SSAC members in Prague meeting and we need to agree > on 2 or 3 topics of interest to discuss with them . I assume DNS abuse and > RDRS for example? > > Best, > > Rafik > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From manju4icann at gmail.com Thu May 22 17:25:46 2025 From: manju4icann at gmail.com (Manju) Date: Thu, 22 May 2025 22:25:46 +0800 Subject: [NCSG-PC] [Ext] [NCSG-EC] Topics for joint meeting with ALAC In-Reply-To: References: <404951C3-4FDC-4BE8-AAF3-F12735F4CA96@icann.org> <1cebc4f0-440e-46d5-9a64-04954055ea59@KathyKleiman.com> Message-ID: Hi Rafik, I can do ICANN reviews too if no other volunteers. Thanks! Manju On Wed, May 21, 2025 at 17:57 Rafik Dammak wrote: > hi all, > > This is the agenda for the NCSG-ALAC meeting: > > *Agenda:* > > 1. Welcome and session overview - Jonathan Zuck, ALAC Chair and Rafik > Dammak, NCSG Chair (5 min) > > 2. ICANN Reviews (20 mins) > > 3. ICANN Community Participant Code of Conduct Concerning SOIs (15 > mins) > > 4. New gTLD Program Next Round Applicant Support (20 mins) > > 5. Human Rights Impact Assessment (HRIA) on DNS Abuse (10 mins) > > 6. Next Steps and Closing Remarks - Jonathan Zuck, ALAC Chair and > Rafik Dammak, NCSG Chair (5 mins) > > > we need to identify a lead/speaker for each topic, I am guessing that > would be: > > - ICANN reviews: ? > - CoC: Manju > - Applicant support: Kathy/Pedro > - HRIA: Farzaneh/Michaela > > Best, > > Rafik > > Le ven. 16 mai 2025 ? 18:48, Rafik Dammak a > ?crit : > >> Hi Manju, >> >> Thanks for the suggestion, I will add that. I think we got a decent list >> and we can work on the lead discussant for each. >> I will share this with alac. >> >> Best, >> >> Rafik >> >> On Fri, May 16, 2025, 14:02 Manju wrote: >> >>> Hi Rafik, >>> >>> Maybe we can add SOI too since the updated Board document will be >>> published for public comments soon. >>> >>> Thanks! >>> >>> Best, >>> Manju >>> >>> On Thu, May 15, 2025 at 10:16?PM Kathy Kleiman >>> wrote: >>> >>>> That sounds like a good list, Rafik. Perhaps they'll have some other >>>> items to add? >>>> >>>> Best, Kathy >>>> On 5/15/2025 10:02 AM, Rafik Dammak wrote: >>>> >>>> Hi all, >>>> >>>> We need to respond to alac. Till now we got the topics of reviews, >>>> applicant support, HRIA and DNS abuse. >>>> >>>> Best, >>>> >>>> Rafik >>>> >>>> >>>> On Sat, May 10, 2025, 01:16 Andrea Glandon >>>> wrote: >>>> >>>>> Hello all! >>>>> >>>>> >>>>> >>>>> Kind reminder to work on topics for the joint session with ALAC. >>>>> At-Large staff is working on confirming the agenda. >>>>> >>>>> >>>>> >>>>> Thanks! >>>>> >>>>> Kind Regards, >>>>> >>>>> Andrea >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> *From: *NCSG-EC on behalf of Rafik >>>>> Dammak via NCSG-EC >>>>> *Reply-To: *Rafik Dammak >>>>> *Date: *Wednesday, April 30, 2025 at 07:09 >>>>> *To: *ncsg-pc , NCSG EC >>>>> *Subject: *[Ext] [NCSG-EC] Topics for joint meeting with ALAC >>>>> >>>>> >>>>> >>>>> Hi all, >>>>> >>>>> >>>>> >>>>> ALAC reached out asking about topics we want to discuss with them. >>>>> Please share your suggestion and/or if you want to volunteer to lead the >>>>> topic. >>>>> >>>>> >>>>> >>>>> Best, >>>>> >>>>> >>>>> >>>>> Rafik >>>>> >>>> Rafik Dammak >>>> @rafik >>>> "fight for the users" >>>> >>>> _______________________________________________ >>>> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://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 >>>> >>> > > > Virus-free.www.avg.com > > <#m_-3451919061806292308_m_-4728882106042814163_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Fri May 23 01:16:13 2025 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Fri, 23 May 2025 08:16:13 +1000 Subject: [NCSG-PC] ICANN83 PC Meetings Proposed Agenda In-Reply-To: References: Message-ID: Hi all, Updated the agenda. This is how it looks now: ICANN83 NCSG Policy Meeting - Workshop 1 of 2 1. Welcome (5 mins) 2. Applicant Guide Book Presentation - ICANN Staff (30 mins) 3. NCSG Joint Meetings Planning (30 mins) 4. AOB (10 mins) ICANN83 NCSG Policy Meeting - Workshop 2 of 2 1. Welcome (5 mins) 2. Review of GNSO Council agenda for meeting scheduled on Wednesday, 11 June - Tomslin (45 mins) 3. Public Comments Update and Discussion - Tomslin (20 mins) 1. In Progress 2. Upcoming 3. Prioritization 4. AOB (15mins) Remain blessed, Tomslin On Thu, 22 May 2025 at 08:43, Tomslin Samme-Nlar wrote: > Hi Rafik, > > Thanks for the comments. I will move the agenda around based on that. > I was referring to the NCSG joint sessions like we used the first PC > session in Seattle to prepare for them. > > Remain blessed, > Tomslin > > > On Wed, 21 May 2025 at 22:42, Rafik Dammak wrote: > >> Hi Tomslin, >> >> Few comments: >> - for AGB we can allocate 30min >> - the second PC session will be after the council informal meeting I >> believe so it is an opportunity to prepare for council public meeting based >> on that >> - which bilaterals GNSO council is having?or you mean for NCSG joint >> sessions? >> >> Best, >> >> Rafik >> >> >> >> On Wed, May 21, 2025, 21:28 Tomslin Samme-Nlar >> wrote: >> >>> Hi all, >>> >>> Here is what I have so far as a proposed agenda for both our meetings. I >>> assume we'd like to prep for the bilaterals like we did in Seattle? >>> Workshop 2 still has room for a topic or two. You can suggest topics on >>> the Google doc here >>> >>> >>> ICANN83 NCSG Policy Meeting - Workshop 1 of 2 >>> >>> >>> 1. >>> >>> Welcome (5 mins) >>> 2. >>> >>> Review of GNSO Council agenda >>> for meeting >>> scheduled on Wednesday, 11 June - Tomslin (45 mins) >>> 3. >>> >>> Public Comments - Tomslin >>> (10 mins) >>> 4. >>> >>> AOB (15 mins) >>> >>> >>> >>> ICANN83 NCSG Policy Meeting - Workshop 2 of 2 >>> >>> >>> 1. >>> >>> Welcome (5 mins) >>> 2. >>> >>> Applicant Guide Book Presentation - ICANN Staff (20 mins) >>> 3. >>> >>> Joint Meetings Planning (45mins) >>> 4. >>> >>> AOB?? (30mins) >>> >>> >>> >>> Remain blessed, >>> Tomslin >>> _______________________________________________ >>> NCSG-PC mailing list >>> NCSG-PC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Fri May 23 05:24:12 2025 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Fri, 23 May 2025 12:24:12 +1000 Subject: [NCSG-PC] [Public Comment] PSR on Expired Domain Deletion and Expired Registration Recovery Policies Message-ID: Hi NCSG, We've discussed this a number of times in our PC meetings this year. The Policy Status Report (PSR) that council requested from staff on Expedited [Expired] Domain Deletion Policy (EDDP) and Expedited [Expired] Registration Recovery Policy (ERRP) has now been published for comments. Some of our members were keen to see this report. I have created a Google doc for drafting our comment. Let me know if you are interested in joining the drafting team. Remain blessed, Tomslin -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Fri May 23 08:33:13 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Fri, 23 May 2025 14:33:13 +0900 Subject: [NCSG-PC] [Ext] [NCSG-EC] Topics for joint meeting with ALAC In-Reply-To: References: <404951C3-4FDC-4BE8-AAF3-F12735F4CA96@icann.org> <1cebc4f0-440e-46d5-9a64-04954055ea59@KathyKleiman.com> Message-ID: Thanks Manju for volunteering. Rafik Le jeu. 22 mai 2025 ? 23:25, Manju a ?crit : > Hi Rafik, > > I can do ICANN reviews too if no other volunteers. > > Thanks! > > Manju > > On Wed, May 21, 2025 at 17:57 Rafik Dammak wrote: > >> hi all, >> >> This is the agenda for the NCSG-ALAC meeting: >> >> *Agenda:* >> >> 1. Welcome and session overview - Jonathan Zuck, ALAC Chair and >> Rafik Dammak, NCSG Chair (5 min) >> >> 2. ICANN Reviews (20 mins) >> >> 3. ICANN Community Participant Code of Conduct Concerning SOIs (15 >> mins) >> >> 4. New gTLD Program Next Round Applicant Support (20 mins) >> >> 5. Human Rights Impact Assessment (HRIA) on DNS Abuse (10 mins) >> >> 6. Next Steps and Closing Remarks - Jonathan Zuck, ALAC Chair and >> Rafik Dammak, NCSG Chair (5 mins) >> >> >> we need to identify a lead/speaker for each topic, I am guessing that >> would be: >> >> - ICANN reviews: ? >> - CoC: Manju >> - Applicant support: Kathy/Pedro >> - HRIA: Farzaneh/Michaela >> >> Best, >> >> Rafik >> >> Le ven. 16 mai 2025 ? 18:48, Rafik Dammak a >> ?crit : >> >>> Hi Manju, >>> >>> Thanks for the suggestion, I will add that. I think we got a decent list >>> and we can work on the lead discussant for each. >>> I will share this with alac. >>> >>> Best, >>> >>> Rafik >>> >>> On Fri, May 16, 2025, 14:02 Manju wrote: >>> >>>> Hi Rafik, >>>> >>>> Maybe we can add SOI too since the updated Board document will be >>>> published for public comments soon. >>>> >>>> Thanks! >>>> >>>> Best, >>>> Manju >>>> >>>> On Thu, May 15, 2025 at 10:16?PM Kathy Kleiman >>>> wrote: >>>> >>>>> That sounds like a good list, Rafik. Perhaps they'll have some other >>>>> items to add? >>>>> >>>>> Best, Kathy >>>>> On 5/15/2025 10:02 AM, Rafik Dammak wrote: >>>>> >>>>> Hi all, >>>>> >>>>> We need to respond to alac. Till now we got the topics of reviews, >>>>> applicant support, HRIA and DNS abuse. >>>>> >>>>> Best, >>>>> >>>>> Rafik >>>>> >>>>> >>>>> On Sat, May 10, 2025, 01:16 Andrea Glandon >>>>> wrote: >>>>> >>>>>> Hello all! >>>>>> >>>>>> >>>>>> >>>>>> Kind reminder to work on topics for the joint session with ALAC. >>>>>> At-Large staff is working on confirming the agenda. >>>>>> >>>>>> >>>>>> >>>>>> Thanks! >>>>>> >>>>>> Kind Regards, >>>>>> >>>>>> Andrea >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> *From: *NCSG-EC on behalf of Rafik >>>>>> Dammak via NCSG-EC >>>>>> *Reply-To: *Rafik Dammak >>>>>> *Date: *Wednesday, April 30, 2025 at 07:09 >>>>>> *To: *ncsg-pc , NCSG EC >>>>> > >>>>>> *Subject: *[Ext] [NCSG-EC] Topics for joint meeting with ALAC >>>>>> >>>>>> >>>>>> >>>>>> Hi all, >>>>>> >>>>>> >>>>>> >>>>>> ALAC reached out asking about topics we want to discuss with them. >>>>>> Please share your suggestion and/or if you want to volunteer to lead the >>>>>> topic. >>>>>> >>>>>> >>>>>> >>>>>> Best, >>>>>> >>>>>> >>>>>> >>>>>> Rafik >>>>>> >>>>> Rafik Dammak >>>>> @rafik >>>>> "fight for the users" >>>>> >>>>> _______________________________________________ >>>>> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://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 >>>>> >>>> >> >> >> Virus-free.www.avg.com >> >> <#m_-689906431296290174_m_-3451919061806292308_m_-4728882106042814163_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Sat May 24 03:40:11 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Sat, 24 May 2025 09:40:11 +0900 Subject: [NCSG-PC] Joint session with SSAC In-Reply-To: References: Message-ID: Hi all, Those are the topics proposed by SSAC: 1. Intro to the SSAC - our 6 priorities and 5 keystone topics 2. Intro to Safer Cyber 3. Intro to NCAP and the next round of gTLDs Please suggest topics. Best, Rafik On Thu, May 22, 2025, 22:36 Rafik Dammak wrote: > Hi all, > > We will meet some of SSAC members in Prague meeting and we need to agree > on 2 or 3 topics of interest to discuss with them . I assume DNS abuse and > RDRS for example? > > Best, > > Rafik > -------------- next part -------------- An HTML attachment was scrubbed... URL: From farzaneh.badii at gmail.com Sat May 24 04:55:35 2025 From: farzaneh.badii at gmail.com (farzaneh badii) Date: Fri, 23 May 2025 21:55:35 -0400 Subject: [NCSG-PC] Joint session with SSAC In-Reply-To: References: Message-ID: Hi Rafik I think we should talk to them about accuracy, disclosure of private data to third parties, and DNS abuse. Discussing NCSG perspective. Farzaneh On Fri, May 23, 2025 at 8:40?PM Rafik Dammak wrote: > Hi all, > > Those are the topics proposed by SSAC: > > 1. Intro to the SSAC - our 6 priorities and 5 keystone topics > 2. Intro to Safer Cyber > 3. Intro to NCAP and the next round of gTLDs > > Please suggest topics. > > Best, > > Rafik > > On Thu, May 22, 2025, 22:36 Rafik Dammak wrote: > >> Hi all, >> >> We will meet some of SSAC members in Prague meeting and we need to agree >> on 2 or 3 topics of interest to discuss with them . I assume DNS abuse and >> RDRS for example? >> >> Best, >> >> Rafik >> > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From michaela.shapiro at article19.org Sat May 24 13:10:17 2025 From: michaela.shapiro at article19.org (Michaela Nakayama Shapiro) Date: Sat, 24 May 2025 10:10:17 +0000 Subject: [NCSG-PC] Joint session with SSAC In-Reply-To: References: <03d95705-f733-4d96-bfa3-6ea2374cd25b.05b495a4-acd5-4405-a5fb-09b87eaaeafb.c1fae48d-e6b7-496f-a270-ce2669eef54a@emailsignatures365.codetwo.com> Message-ID: INTERNAL INTERNAL Hi Rafik, +1 to Farzaneh?s suggestions! Best, Michaela Michaela Nakayama Shapiro (she/her/hers) Programme Officer - Censorship [Logo.png] Defending freedom of expression and information www.article19.org Subscribe to our Newsletter [cid:newsletter_02744340-c607-4374-8a37-11b8b216096d.png] Follow us [Bluesky1x.png] [cid:facebook_2853baa0-f060-42e6-b448-6a8788c1b5dd.png] [cid:youtube_ffe95af1-d962-4acd-ab59-4eb4ea07466e.png] [cid:linkedin_199dc89c-14aa-41cd-b2a7-37b8ae8d667d.png] [cid:instagram_05fbcc72-6df2-442b-8c34-146d0e9d8c41.png] [cid:x_d21e0607-da5a-44a7-80c7-e2d86bc18a92.png] [women-journalists-banner.jpeg] From: NCSG-PC on behalf of farzaneh badii Date: Saturday, 24 May 2025 at 02:55 To: Rafik Dammak Cc: ncsg-pc Subject: Re: [NCSG-PC] Joint session with SSAC Hi Rafik I think we should talk to them about accuracy, disclosure of private data to third parties, and DNS abuse. Discussing NCSG perspective. Farzaneh On Fri, May 23, 2025 at 8:40?PM Rafik Dammak > wrote: Hi all, Those are the topics proposed by SSAC: 1. Intro to the SSAC - our 6 priorities and 5 keystone topics 2. Intro to Safer Cyber 3. Intro to NCAP and the next round of gTLDs Please suggest topics. Best, Rafik On Thu, May 22, 2025, 22:36 Rafik Dammak > wrote: Hi all, We will meet some of SSAC members in Prague meeting and we need to agree on 2 or 3 topics of interest to discuss with them . I assume DNS abuse and RDRS for example? Best, Rafik _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo_1c766458-35ee-431a-9a22-e00b47cd2091.png Type: image/png Size: 6889 bytes Desc: logo_1c766458-35ee-431a-9a22-e00b47cd2091.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: newsletter_02744340-c607-4374-8a37-11b8b216096d.png Type: image/png Size: 379 bytes Desc: newsletter_02744340-c607-4374-8a37-11b8b216096d.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bluesky1x_864ef831-9476-4116-88b8-2a3410741630.png Type: image/png Size: 788 bytes Desc: bluesky1x_864ef831-9476-4116-88b8-2a3410741630.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: facebook_2853baa0-f060-42e6-b448-6a8788c1b5dd.png Type: image/png Size: 670 bytes Desc: facebook_2853baa0-f060-42e6-b448-6a8788c1b5dd.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: youtube_ffe95af1-d962-4acd-ab59-4eb4ea07466e.png Type: image/png Size: 678 bytes Desc: youtube_ffe95af1-d962-4acd-ab59-4eb4ea07466e.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: linkedin_199dc89c-14aa-41cd-b2a7-37b8ae8d667d.png Type: image/png Size: 720 bytes Desc: linkedin_199dc89c-14aa-41cd-b2a7-37b8ae8d667d.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: instagram_05fbcc72-6df2-442b-8c34-146d0e9d8c41.png Type: image/png Size: 840 bytes Desc: instagram_05fbcc72-6df2-442b-8c34-146d0e9d8c41.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: x_d21e0607-da5a-44a7-80c7-e2d86bc18a92.png Type: image/png Size: 895 bytes Desc: x_d21e0607-da5a-44a7-80c7-e2d86bc18a92.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: women-journalists-banner_b1cece5c-a86d-452f-b9f8-9e72943680f6.jpeg Type: image/jpeg Size: 15471 bytes Desc: women-journalists-banner_b1cece5c-a86d-452f-b9f8-9e72943680f6.jpeg URL: From farzaneh.badii at gmail.com Sat May 24 18:08:08 2025 From: farzaneh.badii at gmail.com (farzaneh badii) Date: Sat, 24 May 2025 11:08:08 -0400 Subject: [NCSG-PC] Joint session with SSAC In-Reply-To: References: <03d95705-f733-4d96-bfa3-6ea2374cd25b.05b495a4-acd5-4405-a5fb-09b87eaaeafb.c1fae48d-e6b7-496f-a270-ce2669eef54a@emailsignatures365.codetwo.com> Message-ID: Hi Rafik I see that SSAC has published their report on DNS blocking: https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committee-ssac-reports/sac127-dns-blocking-revisited-16-05-2025-en.pdf I have published a report on DNS resolvers which delves into this topic: https://digitalmedusa.org/wp-content/uploads/2025/04/DNS-Resolvers-2025-Final.pdf If the group wants we can talk about DNS blocking as well. Best regards, Farzaneh On Sat, May 24, 2025 at 6:10?AM Michaela Nakayama Shapiro < michaela.shapiro at article19.org> wrote: > INTERNAL > > INTERNAL > > Hi Rafik, > > > > +1 to Farzaneh?s suggestions! > > > > Best, > > > > Michaela > > > *Michaela Nakayama Shapiro *(she/her/hers) > Programme Officer - Censorship > [image: Logo.png] Defending freedom of > expression > and information > *www.article19.org* Subscribe to our > Newsletter > > Follow us > [image: Bluesky1x.png] > > > > > > [image: women-journalists-banner.jpeg] > > > *From: *NCSG-PC on behalf of farzaneh > badii > *Date: *Saturday, 24 May 2025 at 02:55 > *To: *Rafik Dammak > *Cc: *ncsg-pc > *Subject: *Re: [NCSG-PC] Joint session with SSAC > > Hi Rafik > > > > I think we should talk to them about accuracy, disclosure of private data > to third parties, and DNS abuse. Discussing NCSG perspective. > > Farzaneh > > > > > > On Fri, May 23, 2025 at 8:40?PM Rafik Dammak > wrote: > > Hi all, > > > > Those are the topics proposed by SSAC: > > > > 1. Intro to the SSAC - our 6 priorities and 5 keystone topics > > 2. Intro to Safer Cyber > > 3. Intro to NCAP and the next round of gTLDs > > > > Please suggest topics. > > > Best, > > > > Rafik > > > > On Thu, May 22, 2025, 22:36 Rafik Dammak wrote: > > Hi all, > > > > We will meet some of SSAC members in Prague meeting and we need to agree > on 2 or 3 topics of interest to discuss with them . I assume DNS abuse and > RDRS for example? > > > > Best, > > > > Rafik > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo_1c766458-35ee-431a-9a22-e00b47cd2091.png Type: image/png Size: 6889 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: newsletter_02744340-c607-4374-8a37-11b8b216096d.png Type: image/png Size: 379 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bluesky1x_864ef831-9476-4116-88b8-2a3410741630.png Type: image/png Size: 788 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: facebook_2853baa0-f060-42e6-b448-6a8788c1b5dd.png Type: image/png Size: 670 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: youtube_ffe95af1-d962-4acd-ab59-4eb4ea07466e.png Type: image/png Size: 678 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: linkedin_199dc89c-14aa-41cd-b2a7-37b8ae8d667d.png Type: image/png Size: 720 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: instagram_05fbcc72-6df2-442b-8c34-146d0e9d8c41.png Type: image/png Size: 840 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: x_d21e0607-da5a-44a7-80c7-e2d86bc18a92.png Type: image/png Size: 895 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: women-journalists-banner_b1cece5c-a86d-452f-b9f8-9e72943680f6.jpeg Type: image/jpeg Size: 15471 bytes Desc: not available URL: From jumaropi at yahoo.com Sun May 25 03:08:23 2025 From: jumaropi at yahoo.com (Juan Manuel Rojas) Date: Sun, 25 May 2025 00:08:23 +0000 (UTC) Subject: [NCSG-PC] Joint session with SSAC In-Reply-To: References: <03d95705-f733-4d96-bfa3-6ea2374cd25b.05b495a4-acd5-4405-a5fb-09b87eaaeafb.c1fae48d-e6b7-496f-a270-ce2669eef54a@emailsignatures365.codetwo.com> Message-ID: <595538903.607302.1748131703722@mail.yahoo.com> Hi everyone,?I think it is a good suggestion for address with SSAC we would have those both perspectives.? Yahoo Mail: Search, Organize, Conquer On Sat, May 24, 2025 at 10:08, farzaneh badii wrote: _______________________________________________ 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 rafik.dammak at gmail.com Sun May 25 06:05:17 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Sun, 25 May 2025 12:05:17 +0900 Subject: [NCSG-PC] [NCSG-EC] Topics/agenda for NCPH session in prague In-Reply-To: References: Message-ID: Hi all, As hearing no objection or comment, I assume we agree with the proposed agenda. I will respond to CSG lead. Best, Rafik On Wed, May 21, 2025, 18:51 Rafik Dammak wrote: > Hi all, > > I had call with CSG lead and there was some update about the agenda, > following it: > > - Regarding the RDRS issue, they are removing it from the agenda > - Regarding ICP, Philippe will handle the briefing ? no preparation > necessary. The objective is to see if there?s common ground following his > intervention. > > Is there any other comment ? Any additional topics we want to add? > > Best, > > Rafik > Le sam. 17 mai 2025 ? 10:21, Rafik Dammak a > ?crit : > >> Hi Farzaneh, >> >> Yes other than board seat and GNSO election, the other topics were >> proposed by CSG leaders and I didn't discuss yet with them. For leading >> topics, we can assign a lead from our side. I will ask about the RDRS topic. >> >> I think we can talk about any topic and we can clarify what we want as >> outcome knowing the difference on opinions between NCSG and CSG. >> >> Best, >> >> Rafik >> >> On Sat, May 17, 2025, 10:07 farzaneh badii >> wrote: >> >>> So am I right that most of the topics are led by them? And what does >>> RDRS decision transparency mean? >>> >>> Is it too soon for this rejuvenated meeting to talk about tricky issues >>> like dns abuse and accuracy? >>> >>> Farzaneh >>> >>> >>> On Fri, May 16, 2025 at 8:43?PM Tomslin Samme-Nlar via NCSG-EC < >>> ncsg-ec at lists.ncsg.is> wrote: >>> >>>> Looks enough. >>>> >>>> Remain blessed, >>>> Tomslin >>>> >>>> On Fri, 16 May 2025, 19:19 Rafik Dammak via NCSG-EC, < >>>> ncsg-ec at lists.ncsg.is> wrote: >>>> >>>>> Hi all, >>>>> >>>>> I am discussing with CSG leadership about topics for discussion for >>>>> our session in Prague and the proposed those in the attached slides. >>>>> >>>>> I think those topics are OK while I am not sure how much we will be >>>>> interested by ICP2 one. I will check about the item of issues of common >>>>> ground. Initially I proposed the topic of seat 14 and GNSO election. But I >>>>> would like to get any proposal from our side or to hear if there is any >>>>> concern. >>>>> >>>>> Best, >>>>> >>>>> Rafik >>>>> _______________________________________________ >>>>> NCSG-EC mailing list >>>>> NCSG-EC at lists.ncsg.is >>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>>>> >>>> _______________________________________________ >>>> NCSG-EC mailing list >>>> NCSG-EC at lists.ncsg.is >>>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec >>>> >>> > > > Virus-free.www.avg.com > > <#m_-8700921990263097949_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Sun May 25 06:22:04 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Sun, 25 May 2025 12:22:04 +0900 Subject: [NCSG-PC] Joint session with SSAC In-Reply-To: <595538903.607302.1748131703722@mail.yahoo.com> References: <03d95705-f733-4d96-bfa3-6ea2374cd25b.05b495a4-acd5-4405-a5fb-09b87eaaeafb.c1fae48d-e6b7-496f-a270-ce2669eef54a@emailsignatures365.codetwo.com> <595538903.607302.1748131703722@mail.yahoo.com> Message-ID: Thanks all, we will go with: accuracy, disclosure of private data to third parties, DNS abuse, DNS blocking. Best regards, Rafik On Sun, May 25, 2025, 09:08 Juan Manuel Rojas via NCSG-PC < ncsg-pc at lists.ncsg.is> wrote: > Hi everyone, > I think it is a good suggestion for address with SSAC we would have those > both perspectives. > > Yahoo Mail: Search, Organize, Conquer > > > On Sat, May 24, 2025 at 10:08, farzaneh badii > wrote: > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Sun May 25 08:06:09 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Sun, 25 May 2025 14:06:09 +0900 Subject: [NCSG-PC] Agenda for NCSG sessions Message-ID: Hi all, In addition to Policy sessions and joint sessions, we have 2 other sessions. Here their draft agenda: *NCSG/C Membership Work Session* It will be a joint session between NCSG/NPOC/NCUC. In next ICANN meetings, we will have a coordinated full NC day to avoid duplication and overlap. 1- Introduction (5 min) 2- NCSG part (20 min) - planning for the week - sessions prep 3- NPOC part (30 min) -introduction -crop talking about Youth IGF experience 4- NCUC part (30 min) TBC 5- AOB (5 min) *NCSG Wrap-Up Work Session* It is an experiment to have a session at the end to wrap-up since usually the last NCSG session is on Tuesday. We will see if we should keep or drop it. 1- introduction (5 min) 2- Meeting with ICANN finance team (25 min) TBC - adopted FY26 Operating Plan and Budget 3- Review of the week (35 min) - recap of NCSG sessions and policy discussions - retrospective of joint sessions 4- Next steps & follow-up (20 min) - actions items and plan 5- AOB (5 min) Please share your comments and input. Best, Rafik -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrea.glandon at icann.org Tue May 27 20:19:39 2025 From: andrea.glandon at icann.org (Andrea Glandon) Date: Tue, 27 May 2025 17:19:39 +0000 Subject: [NCSG-PC] [Ext] Agenda for NCSG sessions In-Reply-To: References: Message-ID: These have been updated on the wiki. Kind Regards, Andrea From: NCSG-PC on behalf of Rafik Dammak Date: Sunday, May 25, 2025 at 00:06 To: ncsg-pc , NCSG EC Subject: [Ext] [NCSG-PC] Agenda for NCSG sessions Hi all, In addition to Policy sessions and joint sessions, we have 2 other sessions. Here their draft agenda: NCSG/C Membership Work Session It will be a joint session between NCSG/NPOC/NCUC. In next ICANN meetings, we will have a coordinated full NC day to avoid duplication and overlap. 1- Introduction (5 min) 2- NCSG part (20 min) - planning for the week - sessions prep 3- NPOC part (30 min) -introduction -crop talking about Youth IGF experience 4- NCUC part (30 min) TBC 5- AOB (5 min) NCSG Wrap-Up Work Session It is an experiment to have a session at the end to wrap-up since usually the last NCSG session is on Tuesday. We will see if we should keep or drop it. 1- introduction (5 min) 2- Meeting with ICANN finance team (25 min) TBC - adopted FY26 Operating Plan and Budget 3- Review of the week (35 min) - recap of NCSG sessions and policy discussions - retrospective of joint sessions 4- Next steps & follow-up (20 min) - actions items and plan 5- AOB (5 min) Please share your comments and input. Best, Rafik -------------- next part -------------- An HTML attachment was scrubbed... URL: From PolicyCalendar at icann.org Wed May 28 23:42:15 2025 From: PolicyCalendar at icann.org (ICANN Policy Calendar) Date: Wed, 28 May 2025 20:42:15 +0000 Subject: [NCSG-PC] NCSG Policy Call | 07 July at 11:30 UTC Message-ID: <67164464d7ac49e09125e66a80f3a149@icann.org> Please join the NCSG Monthly Policy call on Monday, 07 July at 11:30 UTC. Join Zoom Meeting: https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09 Meeting ID: 988 7818 9584 Passcode: i!y7.qx+11 One tap mobile +16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose) +12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma) PHONE ONLY DETAILS: Find your local number: https://icann.zoom.us/u/ayKmeftWg Meeting ID: 988 7818 9584 Phone only Passcode: 7740925615 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2031 bytes Desc: not available URL: From PolicyCalendar at icann.org Wed May 28 23:43:29 2025 From: PolicyCalendar at icann.org (ICANN Policy Calendar) Date: Wed, 28 May 2025 20:43:29 +0000 Subject: [NCSG-PC] NCSG Policy Call | 11 August at 11:30 UTC Message-ID: Please join the NCSG Monthly Policy call on Monday, 11 August at 11:30 UTC. Join Zoom Meeting: https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09 Meeting ID: 988 7818 9584 Passcode: i!y7.qx+11 One tap mobile +16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose) +12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma) PHONE ONLY DETAILS: Find your local number: https://icann.zoom.us/u/ayKmeftWg Meeting ID: 988 7818 9584 Phone only Passcode: 7740925615 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2035 bytes Desc: not available URL: From daniel.gluck at icann.org Thu May 29 19:50:20 2025 From: daniel.gluck at icann.org (Daniel Gluck) Date: Thu, 29 May 2025 16:50:20 +0000 Subject: [NCSG-PC] Upcoming Major Public Comment Proceedings Message-ID: Hey All, Keep an eye out tomorrow for a public comment opening for the complete AGB (Runs through mid-July) and for mid-week next week for the Next Round Base RA to have a proceeding launched. Not sure on the timing, but assuming that will also run until mid-July. The AGB is close to 400 pages and both proceedings will use guided submission forms. Nothing in the AGB should be a surprise and they are likely looking to see if their responses / actions reflect the issues raised in prior proceedings. I will have more information when they are publicly available. Thanks, Dan Gluck -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Fri May 30 02:29:39 2025 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Fri, 30 May 2025 09:29:39 +1000 Subject: [NCSG-PC] Upcoming Major Public Comment Proceedings In-Reply-To: References: Message-ID: Thanks so much, Dan. We will keep an eye out for it. Remain blessed, Tomslin On Fri, 30 May 2025, 02:50 Daniel Gluck, wrote: > Hey All, > > Keep an eye out tomorrow for a public comment opening for the complete AGB > (Runs through mid-July) and for mid-week next week for the Next Round Base > RA to have a proceeding launched. Not sure on the timing, but assuming that > will also run until mid-July. > > > > The AGB is close to 400 pages and both proceedings will use guided > submission forms. > > Nothing in the AGB should be a surprise and they are likely looking to see > if their responses / actions reflect the issues raised in prior > proceedings. > > > > I will have more information when they are publicly available. > > > > Thanks, > > Dan Gluck > _______________________________________________ > 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 rafik.dammak at gmail.com Fri May 30 15:22:57 2025 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Fri, 30 May 2025 21:22:57 +0900 Subject: [NCSG-PC] Funded Travellers for ICANN84 Message-ID: Dear Councilors and incoming councilors, As usual we need to confirm if you will be able to attend ICANN84 in Muscat. Please respond asap so we can send the list to GNSO Secretariat. Best, Rafik -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Fri May 30 15:38:40 2025 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Fri, 30 May 2025 22:38:40 +1000 Subject: [NCSG-PC] Funded Travellers for ICANN84 In-Reply-To: References: Message-ID: Wow. Even before we make it to Prague ?. Yes, count me in. Remain blessed, Tomslin On Fri, 30 May 2025, 22:23 Rafik Dammak, wrote: > Dear Councilors and incoming councilors, > > As usual we need to confirm if you will be able to attend ICANN84 in > Muscat. > Please respond asap so we can send the list to GNSO Secretariat. > > Best, > > Rafik > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Fri May 30 15:39:46 2025 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Fri, 30 May 2025 22:39:46 +1000 Subject: [NCSG-PC] Fwd: [council] Proposed Agenda | GNSO Council Meeting | Wednesday, 11 June 2025 In-Reply-To: <6A3BC76C-59E8-4F98-9154-5B91DDC6311C@icann.org> References: <6A3BC76C-59E8-4F98-9154-5B91DDC6311C@icann.org> Message-ID: FYI below ---------- Forwarded message --------- From: Terri Agnew via council Date: Fri, 30 May 2025, 10:59 Subject: [council] Proposed Agenda | GNSO Council Meeting | Wednesday, 11 June 2025 To: council at gnso.icann.org , liaison6c at icann.org < liaison6c at icann.org> Cc: GNSO-Secs Dear all, Please find below the agenda for the GNSO Council Meeting on 11 June 2025 at 11:45 UTC (13:45 CEST) This will be posted on the agenda wiki page shortly. Thank you. Kind regards, Terri Policy Team Supporting the GNSO *GNSO Council Agenda 11 June 2025* Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://icann-community.atlassian.net/wiki/x/2KefBg This agenda was established according to the GNSO Operating Procedures v3.5, updated on 15 March 2023. For convenience: - An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. - An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. GNSO Council meeting on Wednesday, 11 June 2025 at 11:45 UTC: https://tinyurl.com/2zjh8rfh 04:45 Los Angeles; 07:45 Washington DC; 12:45 London; 13:45 Paris; 14:45 Moscow; 21:45 Melbourne *GNSO Council Meeting Remote Participation [Published 24 hours prior to meeting]: **https://icann83.sched.com/event/246XL/gnso-council-meeting* Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ *Item 1: Administrative Matters (5 minutes)* 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes of the GNSO Council Meeting on 10 April 2025 were posted on 24 April 2025. Minutes of the GNSO Council Meeting on 15 May 2025 will be posted on 02 June 2025. *Item 2: Opening Remarks / Review of Projects & Action List (5 minutes)* 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List and Action Item List. *Item 3: Consent Agenda (5 minutes)* - Deferral of Whois Implementation Advisory Group work *Item 4: COUNCIL DISCUSSION - Prioritization of Upcoming Work (35 minutes)* During the GNSO Council?s second Working Session at ICANN82 , the Council discussed its immediate and longer term pipeline of work, including work that the Council has previously committed to, e.g. Latin Diacritics, RPMs Phase 2, and potential areas of work in the future, e.g. DNS Abuse, RDDS, New gTLDs, Expiration Policies, and the Transfer Policy (new dispute mechanism). Here, the Council will begin a detailed discussion of the prioritization of its upcoming work, understanding that all of this work cannot proceed concurrently. 4.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 4.2 - Council Discussion 4.3 - Next Steps *Item 5: COUNCIL UPDATE - Update from Board Readiness Small Team (15 minutes) * During the 2023 GNSO Council Strategic Planning Session (SPS), the GNSO Council agreed that it should seek to limit the likelihood of the Council approving PDP recommendations that the ICANN Board is ultimately unable to adopt. To that end, the Council discussed the desire to ensure it submits ?board-ready policy recommendations? to the Board, to the extent possible. Generally speaking, a policy recommendation is considered board ready when the recommendation is likely to achieve board adoption, i.e., the recommendation has been approved by a GNSO Supermajority Vote and will most likely be considered by the Board to be in the best interests of ICANN Community and ICANN org. In August 2024, a Council Small Team began meeting to further discuss the topic of board readiness. Specifically, the Small Team was tasked by GNSO Council to: - Develop a survey/questionnaire related to the Board?s rejection/non-adoption of policy recommendations, which may be administered to relevant PDP Chairs, PDP WG members, ICANN org Support Staff, and Board members. (Examples: EPDP Temp Spec Phase 1 and 2; Subsequent Procedures) - Administer the survey/questionnaire and conduct interviews with relevant PDP Chairs, PDP WG members, ICANN org Support Staff, and Board members. - Synthesize the findings from the survey/questionnaire and interviews into a set of findings and develop a set of recommendations intended to inform Council work on improving Board readiness. Over the past few months, the Small Team has been conducting interviews with community members, Board members, and staff members. Here, the Council will hear an update on the Small Team?s progress. 5.1 - Introduction of Topic (Kurt Pritz, Small Team Lead) 5.2 - Council Discussion 5.3 - Next Steps *Item 6: COUNCIL UPDATE - Progress Update from Council Accuracy Small Team (15 minutes)* During the Council?s March 2025 meeting , the Council agreed to form a dedicated small team on accuracy, which would be tasked with: - Reviewing the written input received on the Council?s threshold questions; and - Providing a detailed summary of the input received, taking into consideration the potential other sources that can inform the discussion - i.e. (but not limited to) INFERMAL study, EU NIS2 cooperation group, recommendation CC.1, and provide a recommendation to the Council on how to best make progress on the topic of registration data accuracy, e.g., relaunch scoping team with updated assignment, request Issues Report, request additional study (including the recommended form and aim of the study), etc. The Small Team, led by Paul McGrady, began meeting on 15 May 2025. Here, the Council will hear an update on the small team?s progress. 6.1 - Introduction of Topic (Paul McGrady, Small Team Lead) 6.2 - Council Discussion 6.3 - Next Steps *Item 7: COUNCIL UPDATE: Status Update from DNS Abuse Small Team (15 minutes)* During the Council?s March 2025 meeting , the Council agreed to form a dedicated small team on DNS Abuse, which would be tasked with: - evaluating DNS Abuse mitigation efforts across ICANN (e.g., by the CPH, other community groups, and potentially industry firms focusing on DNS whether briefings from such abuse groups would aid the small team. Similar to the first iteration of the DNS Abuse small team, conduct outreach to the broader ICANN community, seeking their input on items specifically suitable for policy development). - reviewing the recommendations that were proposed by the DNS Abuse Small Team in 2022 - assessing the impact of the Contract amendments on DNS abuse mitigation efforts. - How have the amendments helped ICANN Compliance enforce DNS Abuse mitigation? Have they empowered ICANN Compliance to undertake proactive (as opposed to reactive ) enforcement measures? - Can the requirements outlined in the amendments be further clarified to enable more effective DNS Abuse mitigation by registrars and registries? - Can such clarifications be addressed via additional efforts such as focused ICANN policy development, or via other methods such as incremental improvements on industry best practices? What other actions should be taken in order to bring transparency and accountability to the mitigation measures (standardizing ?evidenced and actionable? complaints and response rates for example)? Or even, a practice of reviewing portfolios of malicious registrations rather than one by one, for example. - Assess the human rights impact of the DNS abuse mitigation measures - Discussing with relevant stakeholders and providing a summary on the insights from the INFERMAL study and how these insights can help inform next steps on DNS Abuse. The Small Team, led by Jennifer Chung, began meeting on 15 May 2025. Here, the Council will hear an update on the small team?s progress. 7.1 - Introduction of Topic (Jennifer Chung, Small Team Lead) 7.2 - Council Discussion 7.3 - Next Steps *Item 8: Any Other Business (25 minutes)* 8.1 - Update on Reviews - Letter from ICANN Board Chair, Tripti Sinha 8.2 - Open Mic _______________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/sites/default/files/file/field-file-attach/op-procedures-15mar23-en.pdf *References for Coordinated Universal Time of 11:45 UTC* Local time between March and November in the NORTHERN hemisphere See https://www.timeanddate.com/time/change/ for Dates for Daylight Saving Time and Clock Changes ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 04:45 San Jos?, Costa Rica (CST) UTC-6 05:45 New York/Washington DC, USA (EDT) UTC-4 07:45 Buenos Aires, Argentina (ART) UTC-3 08:45 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 12:45 Paris, France (CEST) UTC+2 13:45 Moscow, Russia (MSK) UTC+3 14:45 Singapore (SGT) UTC+8 19:45 Melbourne, Australia (AEST) UTC+10 21:45 ---------------------------------------------------------------------- For other places see http://www.timeanddate.com and https://tinyurl.com/2zjh8rfh _______________________________________________ council mailing list -- council at icann.org To unsubscribe send an email to council-leave at icann.org _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Fri May 30 18:00:48 2025 From: julf at Julf.com (Johan Helsingius) Date: Fri, 30 May 2025 17:00:48 +0200 Subject: [NCSG-PC] Funded Travellers for ICANN84 In-Reply-To: References: Message-ID: <3a3ed312-056c-4196-a11e-b16aa2d1a25e@Julf.com> I plan to attend. Julf On 30/05/2025 14:22, Rafik Dammak wrote: > Dear Councilors and incoming councilors, > > As usual we need to confirm if you will be able to attend ICANN84 in Muscat. > Please respond asap so we can send the list to GNSO Secretariat. > > Best, > > Rafik > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc From farzaneh.badii at gmail.com Fri May 30 18:02:13 2025 From: farzaneh.badii at gmail.com (farzaneh badii) Date: Fri, 30 May 2025 11:02:13 -0400 Subject: [NCSG-PC] Funded Travellers for ICANN84 In-Reply-To: <3a3ed312-056c-4196-a11e-b16aa2d1a25e@Julf.com> References: <3a3ed312-056c-4196-a11e-b16aa2d1a25e@Julf.com> Message-ID: Yeah Farzaneh On Fri, May 30, 2025 at 11:01?AM Johan Helsingius via NCSG-PC < ncsg-pc at lists.ncsg.is> wrote: > I plan to attend. > > Julf > > > > On 30/05/2025 14:22, Rafik Dammak wrote: > > Dear Councilors and incoming councilors, > > > > As usual we need to confirm if you will be able to attend ICANN84 in > Muscat. > > Please respond asap so we can send the list to GNSO Secretariat. > > > > Best, > > > > Rafik > > > > _______________________________________________ > > NCSG-PC mailing list > > NCSG-PC at lists.ncsg.is > > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From benakin at gmail.com Fri May 30 19:28:20 2025 From: benakin at gmail.com (Benjamin Akinmoyeje) Date: Fri, 30 May 2025 18:28:20 +0200 Subject: [NCSG-PC] Funded Travellers for ICANN84 In-Reply-To: References: Message-ID: Dear Chair, Thank you for the notification. I will be available to attend ICANN84 in Muscat. Kind regards, Benjamin On Fri, May 30, 2025 at 2:38?PM Tomslin Samme-Nlar wrote: > Wow. Even before we make it to Prague ?. Yes, count me in. > > Remain blessed, > Tomslin > > On Fri, 30 May 2025, 22:23 Rafik Dammak, wrote: > >> Dear Councilors and incoming councilors, >> >> As usual we need to confirm if you will be able to attend ICANN84 in >> Muscat. >> Please respond asap so we can send the list to GNSO Secretariat. >> >> Best, >> >> Rafik >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pedrodeperdigaolana at gmail.com Fri May 30 22:06:36 2025 From: pedrodeperdigaolana at gmail.com (=?UTF-8?Q?Pedro_de_Perdig=C3=A3o_Lana?=) Date: Fri, 30 May 2025 16:06:36 -0300 Subject: [NCSG-PC] [NCSG-EC] [Ext] Agenda for NCSG sessions In-Reply-To: References: Message-ID: Hi Rafik, Nothing to add, and the open-ended agenda items are helpful for flexibility :) Cordially, *Pedro de Perdig?o Lana* Lawyer , GEDAI/UFPR Researcher PhD Candidate (UFPR), LLM in Business Law (UCoimbra) Coordination/Board/EC @ ISOC Brazil , NCUC & NCSG (ICANN) and CC Brazil . This message is restricted to the sender and recipient(s). If received by mistake, please reply informing it. Em ter., 27 de mai. de 2025 ?s 14:19, Andrea Glandon via NCSG-EC < ncsg-ec at lists.ncsg.is> escreveu: > These have been updated on the wiki. > > > > Kind Regards, > > Andrea > > > > > > *From: *NCSG-PC on behalf of Rafik Dammak > > *Date: *Sunday, May 25, 2025 at 00:06 > *To: *ncsg-pc , NCSG EC > *Subject: *[Ext] [NCSG-PC] Agenda for NCSG sessions > > > > Hi all, > > > > In addition to Policy sessions and joint sessions, we have 2 other > sessions. Here their draft agenda: > > > > *NCSG/C Membership Work Session* > > It will be a joint session between NCSG/NPOC/NCUC. In next ICANN meetings, > we will have a coordinated full NC day to avoid duplication and overlap. > > > > 1- Introduction (5 min) > > 2- NCSG part (20 min) > > - planning for the week > > - sessions prep > > 3- NPOC part (30 min) > > -introduction > > -crop talking about Youth IGF experience > > 4- NCUC part (30 min) > > TBC > > 5- AOB (5 min) > > > > *NCSG Wrap-Up Work Session* > > It is an experiment to have a session at the end to wrap-up since usually > the last NCSG session is on Tuesday. We will see if we should keep or drop > it. > > > > 1- introduction (5 min) > > 2- Meeting with ICANN finance team (25 min) TBC > > - adopted FY26 Operating Plan and Budget > > 3- Review of the week (35 min) > > - recap of NCSG sessions and policy discussions > > - retrospective of joint sessions > > 4- Next steps & follow-up (20 min) > > - actions items and plan > > 5- AOB (5 min) > > > > Please share your comments and input. > > > > Best, > > > > Rafik > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -------------- next part -------------- An HTML attachment was scrubbed... URL: From manju4icann at gmail.com Sat May 31 05:51:13 2025 From: manju4icann at gmail.com (Manju) Date: Sat, 31 May 2025 10:51:13 +0800 Subject: [NCSG-PC] Funded Travellers for ICANN84 In-Reply-To: References: Message-ID: Hi, Planning to attend, too. Thanks! Manju On Sat, May 31, 2025 at 00:29 Benjamin Akinmoyeje wrote: > Dear Chair, > Thank you for the notification. I will be available to attend ICANN84 in > Muscat. > > Kind regards, > Benjamin > > On Fri, May 30, 2025 at 2:38?PM Tomslin Samme-Nlar > wrote: > >> Wow. Even before we make it to Prague ?. Yes, count me in. >> >> Remain blessed, >> Tomslin >> >> On Fri, 30 May 2025, 22:23 Rafik Dammak, wrote: >> >>> Dear Councilors and incoming councilors, >>> >>> As usual we need to confirm if you will be able to attend ICANN84 in >>> Muscat. >>> Please respond asap so we can send the list to GNSO Secretariat. >>> >>> Best, >>> >>> Rafik >>> _______________________________________________ >>> NCSG-PC mailing list >>> NCSG-PC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >>> >> _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: