From mesumbeslin at gmail.com  Wed May  1 02:05:58 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Wed, 1 May 2024 09:05:58 +1000
Subject: [NCSG-PC] Fwd: [council] Topic 24 Supplemental Recommendations
In-Reply-To: <bc2ff6fb-73ed-4680-a3d4-d79f3d210c2c@KathyKleiman.com>
References: <5ec7137177ed4abeafc8303bc7b8f8c3@amazon.com>
 <CAM8DdeUB+Arkjaa3LOM1xoEVLsViOeHwm-3fxnADAOBX0qw-qQ@mail.gmail.com>
 <CAMeQZi04_xCbGEDd4pSFN1OQGqRY2JJqTaqhaAdssdU9oyAfUA@mail.gmail.com>
 <CAM8DdeVAqjFFgmqDEqMYMeZGfHg+4ppm=fV6FXphEv+Y-BKFCA@mail.gmail.com>
 <bc2ff6fb-73ed-4680-a3d4-d79f3d210c2c@KathyKleiman.com>
Message-ID: <CAM8DdeXjXa3FfQ8LpjJu8jofw3xZx7L==-BVP2RKjd8YjyqGcA@mail.gmail.com>

Hi Kathy,

Thanks for the comments. I believe the same small team plus is expected to
continue this work since they are the ones who've put for a supplemental
recommendation on topic 24 which the board does not like. So, procedural
standpoint, I expect that once the council non-objects this proposal,
communication will be sent out to all existing members and their SG/C/AC
leadership to inform them of the way forward.

And yes, GAC and ALAC will therefore continue to participate as they
currently do.

Warmly,
Tomslin



On Tue, 30 Apr 2024 at 23:12, Kathy Kleiman <Kathy at kathykleiman.com> wrote:

> p.s. I would ask that the Council inform all former members of the Subpro
> Small Team PLUS group of what is happening... everyone who has been part of
> this process in the past should know about the next steps. Tx, Kathy
> On 4/30/2024 5:37 AM, Tomslin Samme-Nlar wrote:
>
> Great, thank you.
>
> Warmly,
> Tomslin
>
> On Tue, 30 Apr 2024, 12:02 ??? Manju Chen, <manju at nii.org.tw> wrote:
>
>> Yes as long as it doesn?t involve diacritics.
>>
>>
>> On Tue, Apr 30, 2024 at 04:33 Tomslin Samme-Nlar <mesumbeslin at gmail.com>
>> wrote:
>>
>>> Are we okay with this?
>>>
>>> Warmly,
>>> Tomslin
>>>
>>>
>>>
>>> ---------- Forwarded message ---------
>>> From: DiBiase, Gregory via council <council at icann.org>
>>> Date: Tue, 30 Apr 2024 at 05:29
>>> Subject: [council] Topic 24 Supplemental Recommendations
>>> To: council at gnso.icann.org <council at gnso.icann.org>
>>>
>>>
>>> Dear Councilors,
>>>
>>>
>>>
>>> At our April meeting we adopted all supplemental recommendations except
>>> for those related to Topic 24: String Similarity Evaluation. Due to time
>>> constraints, we did not decide how to proceed with further evaluation of
>>> Topic 24.
>>>
>>>
>>>
>>> In the interest of sustaining momentum, Leadership is proposing the we
>>> add the new work re: Topic 24 to the small team assignment form (see
>>> attached), then allow the small team to consider a strawman proposal
>>> developed by Staff.  After evaluation of the proposal, the small team will
>>> return to Council with its conclusions on whether this proposal is viable,
>>> and if so, provide draft language for the Council to consider.
>>>
>>>
>>>
>>> We do not believe amendment to the assignment form requires a vote, and
>>> the Small Team can start their work as soon as the strawman proposal is
>>> delivered by Staff. If any Councilors disagree, please respond on list and
>>> we can discuss at our May meeting.
>>>
>>>
>>>
>>> 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 listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240501/44aaf0c3/attachment.htm>

From emmanuelvitus at gmail.com  Wed May  1 16:09:41 2024
From: emmanuelvitus at gmail.com (Emmanuel Vitus)
Date: Wed, 1 May 2024 13:09:41 +0000
Subject: [NCSG-PC] NCSG Public comment on Phase 2 Initial Report of the EPDP
 on IDNs
Message-ID: <CAGKde+2e3W5j4hta40HVVWjwiq2sKrcsiChRTrtPKEnEvdY55w@mail.gmail.com>

Dear Comrades,
As the NCSG representative in the IDNs EPDP discussions, I am seeking your
feedback on the GNSO EPDP Phase 2 Initial Report on Internationalized
Domain Names, specifically concerning second-level variant management for
NCSG public comment.

 I found most of the report straightforward. However, I've identified three
specific areas that appear to require further review and consideration.

*Implementation Guidance 15: *This guideline proposes a standard approach
allowing registries or registrars to enhance services such as RDDS. These
services could offer comprehensive data about a domain and its variants,
possibly through advanced methods like bulk services. I suggest these
enhancements should remain optional and be tightly regulated to ensure
privacy and security.

*F1 Charter Question on TMCH:* The current "exact match" rules under the
Trademark Clearinghouse (TMCH) are too restrictive and could hinder
organizations whose names vary due to linguistic or branding changes. I
propose extending this rule to include "substantial matches," allowing
better protection for the intellectual properties of entities/orgs across
various regions and languages.

*Document Readability: *Although the report is well-structured, its
technical and legal jargon could be a barrier for non-commercial
stakeholders unfamiliar with domain name systems or trademark law. The
readability analysis shows a Flesch-Kincaid Grade Level of 12.96 and a
Gunning Fog Index of 16.37, indicating a high complexity level.

These are my primary concerns, though there may be other issues I'm not
aware of or you may disagree with my points. Please review the attached
document
<https://docs.google.com/document/d/1oeuAYEt-HHIaaD39rX-xRq5uRey2OPZ88z6VBXTPi7g/edit?usp=sharing>
containing my detailed comments and let me know your thoughts.

Feel free to reach out directly if you have any questions or need further
clarification. Colleagues  Akinremi Peter Taiwo,  Grace Githaiga, and Maju
are also monitoring this report and can assist with any inquiries. Great if
we can have all comments or questions by May 8, 2024.

Thank you for your attention and input.

Best regards,

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

From julf at Julf.com  Thu May  2 18:11:27 2024
From: julf at Julf.com (Johan Helsingius)
Date: Thu, 2 May 2024 17:11:27 +0200
Subject: [NCSG-PC] Fwd: [GNSO-SG-C-Leadership] Pilot Holistic Review - Call
 for Volunteers and Preliminary Steps
In-Reply-To: <17897DFF-0AAC-41D7-AF25-AF02A7355F8A@icann.org>
References: <17897DFF-0AAC-41D7-AF25-AF02A7355F8A@icann.org>
Message-ID: <41def6fa-df0e-4b32-bc06-dc554de554af@Julf.com>




-------- Forwarded Message --------
Subject: 	[GNSO-SG-C-Leadership] Pilot Holistic Review - Call for 
Volunteers and Preliminary Steps
Date: 	Thu, 2 May 2024 12:59:13 +0000
From: 	Larisa Gurnick via GNSO-SG-C-Leadership 
<gnso-sg-c-leadership at icann.org>
Reply-To: 	Larisa Gurnick <larisa.gurnick at icann.org>
To: 	soac-leadership at icann.org <soac-leadership at icann.org>
CC: 	gnso-sg-c-leadership at icann.org <gnso-sg-c-leadership at icann.org>, 
Team-leaders at icann.org <Team-leaders at icann.org>, Theresa Swinehart 
<theresa.swinehart at icann.org>



Dear SO/AC Chairs,

In response to the action taken by the Board to initiate the Pilot 
Holistic Review on 29 April 
<https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-special-meeting-of-the-icann-board-29-04-2024-en#section1.a>, 
we would like to bring to your attention the upcoming Call for 
Volunteers for the Pilot Holistic Review (PHR) Team, scheduled for 23 
May ?? 19 June 2024. The Call for Volunteers launches the application 
phase, followed by the nomination and selection phase.

Through its action, the Board requested ?that the Supporting 
Organizations and Advisory Committees shall assemble a Pilot Holistic 
Review Team following the process stipulated at Article 4.6, Section (a) 
of the ICANN Bylaws and follow the Operating Standards for Specific 
Reviews...?

As Chairs of your respective SOs and ACs, you play an important role in 
the review team nomination and selection process. ICANN Bylaws 
<https://www.icann.org/resources/pages/governance/bylaws-en/#article4> 
stipulate that ?The chairs of the Supporting Organizations and Advisory 
Committees participating in the applicable review shall select a group 
of up to 21 review team members from among the prospective members 
nominated by the Supporting Organizations and Advisory Committees, 
balanced for diversity and skill.? Further details on the nomination 
process will be shared via Policy support staff.

We developed the timeline below to commence the PHR Team?s work in 
September 2024, considering the upcoming ICANN meeting and the August 
holiday impacting some of you. Please let us know if you have any 
concerns with the timeline or identified skills and expertise outlined 
below**by*17 MAY 2024*.

Please share this upcoming opportunity amongst your community and 
encourage qualified candidates to apply when the Call for Volunteers is 
announced, and the application period opens. For more information about 
the Pilot Holistic Review, including its Board approved Terms of 
Reference, visit the pilot?s wiki page here 
<https://community.icann.org/x/Cgx1Cw>.

Thank you for your support of this important work. Please feel free to 
contact me directly or my team at reviews at icann.org 
<mailto:reviews at icann.org>if you have any questions.

/Larisa Gurnick/

/VP, Reviews Support & Accountability/

/Global Domains and Strategy/

*Steps and Timeline*

We developed an estimated timeline for the nomination and selection of 
volunteers to serve on the Pilot Holistic Review. This timeline is 
designed to provide sufficient time for each SO/AC to follow its 
internal nomination process and for the Chairs of all the participating 
SO/ACs to complete the selection process to start the review process in 
September 2024. Please find the steps, estimated dates and durations below:

*Steps*

	

*Start Date*

	

*End Date*

	

*Duration*

*Call for Volunteers - *window for applications to be submitted**

	

*23 May 2024*

	

*19 June*

	

*4 weeks*

SO/AC?s review list of applicants and determine their respective nominations

	

20 June

	

2 August

	

6 weeks

*ICANN org posts a list of all SO/AC nominated applicants on the PHR 
wiki and produces a skill and diversity analysis of nominated candidates*

	

*5 August*

	

*9 August*

	

*5 days*

SO/AC Chairs select Review Team members and identify review leadership 
from list of nominated applicants

	

12 August

	

6 September

	

4 weeks

SO/AC Chairs inform ICANN of selected Review Team members.

	

9 September

	

9 September

	

*Review Team members are announced publicly*

	

*13 September*

	

*13 September 2024*

	

*Skills and Expertise *

For this important review, ICANN is seeking volunteers that represent 
different parts of the ICANN community and are geographically and 
experientially diverse. These volunteers will participate in the 
development of methodologies and guidelines for future Holistic Reviews. 
The following skills and expertise needed were identified based on the 
community-supported and Board-approved Terms of Reference 
<https://community.icann.org/display/PHR/PHR+Home?preview=/329220199/330072289/PHR%20ToR_29%20April%202024.docx.pdf>:

   * Performance assessment and audits of organizational effectiveness
     and governance

   * Development of methodologies and guidelines for process improvement
     and measurement
   * Data analysis informing fact-based findings and recommendations
   * Familiarity with ICANN Reviews, and ICANN structures
   * Knowledge of recognized frameworks for organizational excellence
   * Principles of accountability applicable to organizations broadly
     similar to ICANN

In addition to the above skills and expertise, all selected review team 
members are expected to actively participate for the duration of the 
review, anticipated to start in September 2024 and last for up to 14 months.



From mesumbeslin at gmail.com  Sat May  4 11:12:24 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Sat, 4 May 2024 18:12:24 +1000
Subject: [NCSG-PC] Fwd: [council] Proposed Agenda | GNSO Council Meeting |
 Thursday, 16 May 2024
In-Reply-To: <C596EAE2-C889-4EC5-8ECD-9D18AF631573@icann.org>
References: <C596EAE2-C889-4EC5-8ECD-9D18AF631573@icann.org>
Message-ID: <CAM8DdeXSqSDBbQEGDOKYcwptD38DhzJDBt87dcmWgA2WY5KPXQ@mail.gmail.com>

FYI members.

Warmly,
Tomslin

---------- Forwarded message ---------
From: Terri Agnew via council <council at icann.org>
Date: Fri, 3 May 2024, 06:45
Subject: [council] Proposed Agenda | GNSO Council Meeting | Thursday, 16
May 2024
To: council at gnso.icann.org <council at gnso.icann.org>,
liaison6c at gnso.icann.org <liaison6c at gnso.icann.org>
Cc: gnso-secs at icann.org <gnso-secs at icann.org>


Dear all,



Please find below the final proposed agenda for the GNSO Council Meeting
taking place on Thursday, 16 May 2024 at 05:00 UTC for 2 hours This has
been posted on the agenda wiki page <https://community.icann.org/x/BYDyEg>.



Thank you.



Kind regards,



Terri

Policy Team Supporting the GNSO

*GNSO Council Agenda 16 May 2024*

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



This agenda was established according to the GNSO Operating Procedures
<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-procedures-15mar23-en.pdf>
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, 16 May 2024 at 05:00 UTC:
https://tinyurl.com/4dthynkr



22:00 Los Angeles (Wednesday); 01:00 Washington DC; 22:00 London; 06:00
Paris; 08:00 Moscow; 15:00 Melbourne



*GNSO Council Meeting Remote Participation:*
*https://icann.zoom.us/j/92283565389?pwd=QnlHK1JSbzdiSFFZSjRjamxMTkNGdz09*
<https://icann.zoom.us/j/92283565389?pwd=QnlHK1JSbzdiSFFZSjRjamxMTkNGdz09>

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

___________________________________

*Item 1: Administrative Matters (5 minutes)*

1.1 - Roll Call

1.2 - Updates to Statements of Interest

1.3 - Review / Amend Agenda

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

Minutes
<https://gnso.icann.org/sites/default/files/policy/2024/minutes/minutes-gnso-council-06mar24-en.pdf>
of the GNSO Council Meeting on 06 March 2024 were posted on 23 March 2024.

Minutes of the GNSO Council Meeting on 18 April 2024 will be posted on 03
May 2024.



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

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



*Item 3: Consent Agenda (5 minutes)*

   - GNSO Liaison to the Governmental Advisory Committee
   - Council Response to Board Letter on CCWG Auction Proceeds
   Recommendation 7

*Item 4: COUNCIL VOTE - Deferral of Policy Status Report Request -
Expiration Policies (15 minutes)*

The GNSO Council previously considered when to request a Policy Status
Report (?PSR?) for the purpose of conducting a review of the two Expiration
Policies, the Expired Domain Name Deletion Policy (?EDDP?) and the Expired
Registration Recovery Policy (?ERRP?). In November 2020, given concerns
about its capacity and no known issues with the policies, the Council
agreed to delay the request for the Policy Status Report (PSR) for a period
of 24 months. After 24 months had passed, the Council reconsidered whether
it was an appropriate time to request a PSR.

To that end, in July 2022, the Council agreed that it would be helpful to
consult with both registrars and ICANN org to help determine if there are
any known issues or concerns with either of the two Expiration Policies
which could warrant requesting a PSR.

In making its decision whether to request to a PSR at this time, the
Council consulted:



   1. Registrars, who were asked to flag substantial issues with the
   policies that would warrant a near-term request for PSR and did not note
   any issues
   2. ICANN Compliance, who provided a write-up
   <https://mm.icann.org/pipermail/council/2022-November/026164.html>, noting
   confusion with key terms in the policy and persistent registrant confusion
   with the auto-renew grace period and aftermarket activities, et al.
   3. ICANN org Registrant Program, which provided a catalog of the
   available educational resources on domain name expiration and renewal
   (Brian Gutterman?s update at Council)

In reviewing these materials, the Council determined that the EDDP and ERRP
seem to have been implemented as intended and imminent policy work is not
needed at this time. Accordingly, the GNSO Council will reconsider a PSR on
the Expiration Policies in two years time, or earlier, if a need is
determined and it is requested.

Here, the Council will vote to consider a PSR on the Expiration Policies in
two years.

4.1 - Presentation of Motion (Greg DiBiase, GNSO Chair)

4.2 - Council Discussion

4.3 - Council vote (voting threshold: simple majority)



*Item 5: COUNCIL VOTE - Request for Preliminary Issue Report for Diacritics
in Latin Script (15 minutes)*

The GNSO Council was made aware of a potential issue whereby future
applied-for strings in the Latin script containing diacritics may be
confusingly similar to ASCII strings, are non-variants, and the same entity
wishes to operate both strings.

For background, an applied-for IDN gTLD string in the Latin script
containing diacritics, which is NOT an allocatable variant label of the
base ASCII string (existing or applied-for) according to RZ-LGR, are
sometimes seen as equivalents. In some instances, however, the base ASCII
string is seen as a workaround and not necessarily ?correct?. The base
ASCII string and the Latin diacritic string may be determined to be
confusingly similar (i.e., in which case, the strings would be placed in a
contention set or if an existing gTLD is involved, the applied-for label
would not pass the String Similarity Review).

During the GNSO Council Meeting at ICANN78 in Hamburg on 25 October 2023
<https://gnso.icann.org/sites/default/files/policy/2023/minutes/minutes-gnso-council-part1-25oct23-en.pdf>,
the GNSO Council received a detailed briefing on this issue and agreed to
request a study from ICANN org to help inform the GNSO Council on the issue
of diacritics in Latin Script. Prior to the request being made to ICANN
org, the org volunteered to investigate what mechanism or mechanisms might
be appropriate to address this issue.

Following the discussion during its April 2024 meeting
<https://icann.zoom.us/rec/play/NSXhHFF5NVqRpg6rURgSTvIcv2SWS6N92WoiEZ6p_7LBY3RlMEwHGIkz4Hqo8fMtfu92lnxs8mY5qIVQ.cdpok-x9FFk8JDaf?canPlayFromShare=true&from=share_recording_detail&startTime=1713474063000&componentName=rec-play&originRequestUrl=https%3A%2F%2Ficann.zoom.us%2Frec%2Fshare%2FpNzOb50IRhU01eMSlNtJOH_3vppmsiidy6-4Qk5yyjkURfb769C2_CaaR7_j6G_o.BcYhF_QcQLFI16O4%3FstartTime%3D1713474063000>,
the Council discussed requesting a Preliminary Issue Report on diacritics
in the Latin Script. On [date], the request for an Issue Report was
circulated to the Council mailing list.



Here, the Council will vote to request ICANN org to deliver a Preliminary
Issue Report on diacritics in the Latin Script.

5.1 - Introduction of Motion (Greg DiBiase, GNSO Chair)

5.2 - Council Discussion

5.3 - Council Vote (Voting threshold: simple majority)



*Item 6: COUNCIL DISCUSSION - GNSO Council Committee for Overseeing and
Implementing Continuous Improvement (?CCOICI?) Pilot Survey Results (20
minutes)*

Over the course of several months in 2021, the GNSO Council discussed how
it could best approach the GNSO?s work that is focused on structural,
procedural, and process improvements, and specifically not policy
development. Notably, this work affects the GNSO community more broadly,
and not just the GNSO Council. Given concerns about workload and the
efficacy of the approach to this portfolio of work, the GNSO Council
resolved <https://gnso.icann.org/en/council/resolutions/2020-current#202106>
on 16 June 2021 to initiate the Council Committee for Overseeing and
Implementing Continuous Improvement (?CCOICI?) Framework as a pilot and to
reevaluate the Framework after the conclusion of its tasks. The pilot
handled the following assigned tasks: 1) GNSO Working Group Self-Assessment
Requirements; 2) GNSO Statement of Interest (SOI) Requirements; and 3)
Assessment of Accountability Work Stream 2 Requirements.

To conclude the pilot, the CCOICI administered a survey
<https://community.icann.org/display/CCFOICI/c.+CCOICI+Pilot+Survey?preview=/302350647/302350648/SurveyMonkey_CCOICI_Questions%20in%20PDF%20format_31-Jan-2024.pdf>
to all relevant ICANN Community Stakeholder Groups and Constituencies
during 1 February-5 March 2024. In administering this survey, the CCOICI
assessed the views of each SG/C to evaluate if the Council and GNSO
community see value in continuing the use of the CCOICI Framework and if
needed, determine how it could be improved. If the survey results noted a
significant issue, this should be the trigger to initiate appropriate
measures to deal with such issues.



Here, the Council will receive an overview of the results of the survey and
discuss the next steps for the CCOICI.

6.1 - Introduction of Topic (Manju Chen, Chair of CCOICI)

6.2 - Council Discussion

6.3 - Next Steps



*Item 7: COUNCIL DISCUSSION - Intellectual Property Constituency Request
for Reconsideration (15 minutes) *

On 22 November 2023, the Intellectual Property Constituency (IPC)
filed a Request
for Reconsideration
<https://www.icann.org/en/system/files/files/reconsideration-23-2-ipc-request-redacted-22nov23-en.pdf>
of the ICANN Board Resolutions 2023.10.26.11 and 2023.10.26.122
<https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-26-10-2023-en#section2.d>,
regarding (i) the actions and inactions that led to (a) the ICANN Board?s
public comment of 6 December 2018 on the Initial Report
<https://www.icann.org/en/system/files/files/new-gtld-auction-proceeds-initial-08oct18-en.pdf>
of
the Cross-Community Working Group on New gTLD Auction Proceeds (CCWG-AP),
(b) the organization of the public comment phase
<https://www.icann.org/en/public-comment/proceeding/proposed-final-report-of-the-new-gtld-auction-proceeds-cross-community-working-group-23-12-2019>
on
the Proposed Final Report
<https://www.icann.org/en/system/files/files/proposed-new-gtld-auction-proceeds-final-23dec19-en.pdf>
of
the New gTLD Auction Proceeds Cross Community Working Group, (c) the ICANN
Board Resolutions 2022.06.12.13 to 2022.06.12.16 , and (ii) the actions and
inactions involving the implementation of the ICANN Grant Giving Program.



Here, the Council will hear an update on the Request for Consideration and
discuss potential next steps for the Council, if any.

7.1 - Introduction of Topic (Damon Ashcraft, GNSO Councilor for IPC)

7.2 - Council Discussion

7.3 - Next Steps



*Item 8: COUNCIL DISCUSSION - Review of Action Decision Radar (20 minutes)*

During the GNSO Council?s most recent strategic planning session, the
Council discussed the topic of how to be an effective manager of the GNSO?s
Policy Development Process (PDP). In recognition of the importance of
regularly reviewing the Council?s portfolio of work, the Council agreed to
the following action item, ?During a session at ICANN79, Council to prepare
for a careful review of the work captured in the Program Management Tool
(PMT) that will conclude or initiate prior to the next AGM, or continue
beyond the next AGM[.]?

The Council conducted this inaugural review of the Projects List
during its Working
Session at ICANN79
<https://community.icann.org/display/gnsocouncilmeetings/GNSO+Council+Working+Session+1+of+3+-+ICANN79>
on Sunday, 3 March 2024. The review also intended to include an overview of
the Action Decision Radar
<https://community.icann.org/display/gnsocouncilmeetings/Action+Decision+Radar>
(?ADR?); however, due to time constraints, the Council agreed to review the
ADR at an upcoming Council meeting.

The ADR is a tool designed to assist the Council by highlighting imminent
decisions or actions that need to be taken by the GNSO Council. The ADR
contains a series of range markers, e.g., 0-1 month, 1-3 months, etc., to
alert the Council to the timing of the upcoming action or decision.



Here, the Council will review the contents of the ADR and discuss next
steps.

8.1 - Introduction of Topic (Tomslin Samme-NIar, GNSO Vice-Chair)

8.2 - Council Discussion

8.3 - Next Steps



*Item 9: GNSO Council Aspirational Statement (10 minutes)*

During its most recent strategic planning session, the GNSO Council
discussed the desire to have a common understanding of how outputs from the
bottom-up multistakeholder model should be voted on at the Council level.



Specifically, the Council agreed to the following action items coming out
of the SPS:

Proposed Action Item 4.1: Council to develop an aspirational (non-binding)
statement to reflect that Councilors should not seek to undo bottom-up
consensus-driven outcomes of GNSO WGs.



Proposed Action Item 4.2: Once action item 4.1 is complete, Councilors to
leverage the aspirational statement to build awareness within their
respective SG/Cs.



Here, the Council will discuss the most recent iteration of the aspirational
statement
<https://docs.google.com/document/d/1QioeB3MAWb9J38tvz5wSjRULPpbeeNoZvLZH6qLfVyw/edit?usp=sharing>,
which seeks to incorporate the previous feedback from Councilors and
discuss next steps.

9.1 - Introduction of Topic (Greg DiBiase, GNSO Chair)

9.2 - Council Discussion

9.3 - Next Steps



*Item 10: Any Other Business (15 minutes)*



10.1 - Update on ICANN80 planning and GNSO Draft schedule
<https://gnso.icann.org/sites/default/files/policy/2024/draft/gnso-draft-schedule-icann80-02may24-en.pdf>



10.2 - ccNSO & GAC Liaison updates (every three months)



10.3 - SPS Action Item Updates: Recommendation Reports and GNSO Liaisons to
WGs



10.4 - Call for Volunteers
<https://lists.icann.org/hyperkitty/list/council at icann.org/thread/FSVAED2EIDHDSCHPWGZEUAABAUDWKU3K/>-
Privacy and Proxy Services Accreditation Implementation Review Team (PPSAI)



 _______________________________

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 05: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/4dthynkr




_______________________________________________
council mailing list -- council at icann.org
To unsubscribe send an email to council-leave at icann.org

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

From mesumbeslin at gmail.com  Sat May  4 11:13:23 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Sat, 4 May 2024 18:13:23 +1000
Subject: [NCSG-PC] [NCSG-EC] Fwd: [GNSO-SG-C-Leadership] Pilot Holistic
 Review - Call for Volunteers and Preliminary Steps
In-Reply-To: <41def6fa-df0e-4b32-bc06-dc554de554af@Julf.com>
References: <17897DFF-0AAC-41D7-AF25-AF02A7355F8A@icann.org>
 <41def6fa-df0e-4b32-bc06-dc554de554af@Julf.com>
Message-ID: <CAM8DdeWU-cCP097YMb+z_MFAJqM5ugQkWmtWvxLoEZ=wvSdaJw@mail.gmail.com>

Thanks for sharing, Julf.

Considering that the letter talks of SO/AC selection, is it your
understanding therefore that it will be GNSO putting the call out?

Warmly,
Tomslin

On Fri, 3 May 2024, 01:11 Johan Helsingius via NCSG-EC, <
ncsg-ec at lists.ncsg.is> wrote:

>
>
>
> -------- Forwarded Message --------
> Subject:        [GNSO-SG-C-Leadership] Pilot Holistic Review - Call for
> Volunteers and Preliminary Steps
> Date:   Thu, 2 May 2024 12:59:13 +0000
> From:   Larisa Gurnick via GNSO-SG-C-Leadership
> <gnso-sg-c-leadership at icann.org>
> Reply-To:       Larisa Gurnick <larisa.gurnick at icann.org>
> To:     soac-leadership at icann.org <soac-leadership at icann.org>
> CC:     gnso-sg-c-leadership at icann.org <gnso-sg-c-leadership at icann.org>,
> Team-leaders at icann.org <Team-leaders at icann.org>, Theresa Swinehart
> <theresa.swinehart at icann.org>
>
>
>
> Dear SO/AC Chairs,
>
> In response to the action taken by the Board to initiate the Pilot
> Holistic Review on 29 April
> <
> https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-special-meeting-of-the-icann-board-29-04-2024-en#section1.a>,
>
> we would like to bring to your attention the upcoming Call for
> Volunteers for the Pilot Holistic Review (PHR) Team, scheduled for 23
> May  ? 19 June 2024. The Call for Volunteers launches the application
> phase, followed by the nomination and selection phase.
>
> Through its action, the Board requested ?that the Supporting
> Organizations and Advisory Committees shall assemble a Pilot Holistic
> Review Team following the process stipulated at Article 4.6, Section (a)
> of the ICANN Bylaws and follow the Operating Standards for Specific
> Reviews...?
>
> As Chairs of your respective SOs and ACs, you play an important role in
> the review team nomination and selection process. ICANN Bylaws
> <https://www.icann.org/resources/pages/governance/bylaws-en/#article4>
> stipulate that ?The chairs of the Supporting Organizations and Advisory
> Committees participating in the applicable review shall select a group
> of up to 21 review team members from among the prospective members
> nominated by the Supporting Organizations and Advisory Committees,
> balanced for diversity and skill.? Further details on the nomination
> process will be shared via Policy support staff.
>
> We developed the timeline below to commence the PHR Team?s work in
> September 2024, considering the upcoming ICANN meeting and the August
> holiday impacting some of you. Please let us know if you have any
> concerns with the timeline or identified skills and expertise outlined
> below**by*17 MAY 2024*.
>
> Please share this upcoming opportunity amongst your community and
> encourage qualified candidates to apply when the Call for Volunteers is
> announced, and the application period opens. For more information about
> the Pilot Holistic Review, including its Board approved Terms of
> Reference, visit the pilot?s wiki page here
> <https://community.icann.org/x/Cgx1Cw>.
>
> Thank you for your support of this important work. Please feel free to
> contact me directly or my team at reviews at icann.org
> <mailto:reviews at icann.org>if you have any questions.
>
> /Larisa Gurnick/
>
> /VP, Reviews Support & Accountability/
>
> /Global Domains and Strategy/
>
> *Steps and Timeline*
>
> We developed an estimated timeline for the nomination and selection of
> volunteers to serve on the Pilot Holistic Review. This timeline is
> designed to provide sufficient time for each SO/AC to follow its
> internal nomination process and for the Chairs of all the participating
> SO/ACs to complete the selection process to start the review process in
> September 2024. Please find the steps, estimated dates and durations below:
>
> *Steps*
>
>
>
> *Start Date*
>
>
>
> *End Date*
>
>
>
> *Duration*
>
> *Call for Volunteers - *window for applications to be submitted**
>
>
>
> *23 May 2024*
>
>
>
> *19 June*
>
>
>
> *4 weeks*
>
> SO/AC?s review list of applicants and determine their respective
> nominations
>
>
>
> 20 June
>
>
>
> 2 August
>
>
>
> 6 weeks
>
> *ICANN org posts a list of all SO/AC nominated applicants on the PHR
> wiki and produces a skill and diversity analysis of nominated candidates*
>
>
>
> *5 August*
>
>
>
> *9 August*
>
>
>
> *5 days*
>
> SO/AC Chairs select Review Team members and identify review leadership
> from list of nominated applicants
>
>
>
> 12 August
>
>
>
> 6 September
>
>
>
> 4 weeks
>
> SO/AC Chairs inform ICANN of selected Review Team members.
>
>
>
> 9 September
>
>
>
> 9 September
>
>
>
> *Review Team members are announced publicly*
>
>
>
> *13 September*
>
>
>
> *13 September 2024*
>
>
>
> *Skills and Expertise *
>
> For this important review, ICANN is seeking volunteers that represent
> different parts of the ICANN community and are geographically and
> experientially diverse. These volunteers will participate in the
> development of methodologies and guidelines for future Holistic Reviews.
> The following skills and expertise needed were identified based on the
> community-supported and Board-approved Terms of Reference
> <
> https://community.icann.org/display/PHR/PHR+Home?preview=/329220199/330072289/PHR%20ToR_29%20April%202024.docx.pdf
> >:
>
>    * Performance assessment and audits of organizational effectiveness
>      and governance
>
>    * Development of methodologies and guidelines for process improvement
>      and measurement
>    * Data analysis informing fact-based findings and recommendations
>    * Familiarity with ICANN Reviews, and ICANN structures
>    * Knowledge of recognized frameworks for organizational excellence
>    * Principles of accountability applicable to organizations broadly
>      similar to ICANN
>
> In addition to the above skills and expertise, all selected review team
> members are expected to actively participate for the duration of the
> review, anticipated to start in September 2024 and last for up to 14
> months.
>
> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240504/f7e991ad/attachment.htm>

From julf at Julf.com  Sat May  4 17:30:29 2024
From: julf at Julf.com (Johan Helsingius)
Date: Sat, 4 May 2024 16:30:29 +0200
Subject: [NCSG-PC] [NCSG-EC] Fwd: [GNSO-SG-C-Leadership] Pilot Holistic
 Review - Call for Volunteers and Preliminary Steps
In-Reply-To: <CAM8DdeWU-cCP097YMb+z_MFAJqM5ugQkWmtWvxLoEZ=wvSdaJw@mail.gmail.com>
References: <17897DFF-0AAC-41D7-AF25-AF02A7355F8A@icann.org>
 <41def6fa-df0e-4b32-bc06-dc554de554af@Julf.com>
 <CAM8DdeWU-cCP097YMb+z_MFAJqM5ugQkWmtWvxLoEZ=wvSdaJw@mail.gmail.com>
Message-ID: <6cd6b1bd-2ddd-463b-9c76-3bd31de336f5@Julf.com>

Not sure if it will be GNSO, or if there will be a general call.

	Julf


On 04/05/2024 10:13, Tomslin Samme-Nlar wrote:
> Thanks for sharing, Julf.
> 
> Considering that the letter talks of SO/AC selection, is it your 
> understanding therefore that it will be GNSO putting the call out?
> 
> Warmly,
> Tomslin
> 
> On Fri, 3 May 2024, 01:11 Johan Helsingius via NCSG-EC, 
> <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>> wrote:
> 
> 
> 
> 
>     -------- Forwarded Message --------
>     Subject:? ? ? ? [GNSO-SG-C-Leadership] Pilot Holistic Review - Call for
>     Volunteers and Preliminary Steps
>     Date:? ?Thu, 2 May 2024 12:59:13 +0000
>     From:? ?Larisa Gurnick via GNSO-SG-C-Leadership
>     <gnso-sg-c-leadership at icann.org <mailto:gnso-sg-c-leadership at icann.org>>
>     Reply-To:? ? ? ?Larisa Gurnick <larisa.gurnick at icann.org
>     <mailto:larisa.gurnick at icann.org>>
>     To: soac-leadership at icann.org <mailto:soac-leadership at icann.org>
>     <soac-leadership at icann.org <mailto:soac-leadership at icann.org>>
>     CC: gnso-sg-c-leadership at icann.org
>     <mailto:gnso-sg-c-leadership at icann.org>
>     <gnso-sg-c-leadership at icann.org
>     <mailto:gnso-sg-c-leadership at icann.org>>,
>     Team-leaders at icann.org <mailto:Team-leaders at icann.org>
>     <Team-leaders at icann.org <mailto:Team-leaders at icann.org>>, Theresa
>     Swinehart
>     <theresa.swinehart at icann.org <mailto:theresa.swinehart at icann.org>>
> 
> 
> 
>     Dear SO/AC Chairs,
> 
>     In response to the action taken by the Board to initiate the Pilot
>     Holistic Review on 29 April
>     <https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-special-meeting-of-the-icann-board-29-04-2024-en#section1.a <https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-special-meeting-of-the-icann-board-29-04-2024-en#section1.a>>,
>     we would like to bring to your attention the upcoming Call for
>     Volunteers for the Pilot Holistic Review (PHR) Team, scheduled for 23
>     May ?? 19 June 2024. The Call for Volunteers launches the application
>     phase, followed by the nomination and selection phase.
> 
>     Through its action, the Board requested ?that the Supporting
>     Organizations and Advisory Committees shall assemble a Pilot Holistic
>     Review Team following the process stipulated at Article 4.6, Section
>     (a)
>     of the ICANN Bylaws and follow the Operating Standards for Specific
>     Reviews...?
> 
>     As Chairs of your respective SOs and ACs, you play an important role in
>     the review team nomination and selection process. ICANN Bylaws
>     <https://www.icann.org/resources/pages/governance/bylaws-en/#article4 <https://www.icann.org/resources/pages/governance/bylaws-en/#article4>>
>     stipulate that ?The chairs of the Supporting Organizations and Advisory
>     Committees participating in the applicable review shall select a group
>     of up to 21 review team members from among the prospective members
>     nominated by the Supporting Organizations and Advisory Committees,
>     balanced for diversity and skill.? Further details on the nomination
>     process will be shared via Policy support staff.
> 
>     We developed the timeline below to commence the PHR Team?s work in
>     September 2024, considering the upcoming ICANN meeting and the August
>     holiday impacting some of you. Please let us know if you have any
>     concerns with the timeline or identified skills and expertise outlined
>     below**by*17 MAY 2024*.
> 
>     Please share this upcoming opportunity amongst your community and
>     encourage qualified candidates to apply when the Call for Volunteers is
>     announced, and the application period opens. For more information about
>     the Pilot Holistic Review, including its Board approved Terms of
>     Reference, visit the pilot?s wiki page here
>     <https://community.icann.org/x/Cgx1Cw
>     <https://community.icann.org/x/Cgx1Cw>>.
> 
>     Thank you for your support of this important work. Please feel free to
>     contact me directly or my team at reviews at icann.org
>     <mailto:reviews at icann.org>
>     <mailto:reviews at icann.org <mailto:reviews at icann.org>>if you have any
>     questions.
> 
>     /Larisa Gurnick/
> 
>     /VP, Reviews Support & Accountability/
> 
>     /Global Domains and Strategy/
> 
>     *Steps and Timeline*
> 
>     We developed an estimated timeline for the nomination and selection of
>     volunteers to serve on the Pilot Holistic Review. This timeline is
>     designed to provide sufficient time for each SO/AC to follow its
>     internal nomination process and for the Chairs of all the participating
>     SO/ACs to complete the selection process to start the review process in
>     September 2024. Please find the steps, estimated dates and durations
>     below:
> 
>     *Steps*
> 
> 
> 
>     *Start Date*
> 
> 
> 
>     *End Date*
> 
> 
> 
>     *Duration*
> 
>     *Call for Volunteers - *window for applications to be submitted**
> 
> 
> 
>     *23 May 2024*
> 
> 
> 
>     *19 June*
> 
> 
> 
>     *4 weeks*
> 
>     SO/AC?s review list of applicants and determine their respective
>     nominations
> 
> 
> 
>     20 June
> 
> 
> 
>     2 August
> 
> 
> 
>     6 weeks
> 
>     *ICANN org posts a list of all SO/AC nominated applicants on the PHR
>     wiki and produces a skill and diversity analysis of nominated
>     candidates*
> 
> 
> 
>     *5 August*
> 
> 
> 
>     *9 August*
> 
> 
> 
>     *5 days*
> 
>     SO/AC Chairs select Review Team members and identify review leadership
>     from list of nominated applicants
> 
> 
> 
>     12 August
> 
> 
> 
>     6 September
> 
> 
> 
>     4 weeks
> 
>     SO/AC Chairs inform ICANN of selected Review Team members.
> 
> 
> 
>     9 September
> 
> 
> 
>     9 September
> 
> 
> 
>     *Review Team members are announced publicly*
> 
> 
> 
>     *13 September*
> 
> 
> 
>     *13 September 2024*
> 
> 
> 
>     *Skills and Expertise *
> 
>     For this important review, ICANN is seeking volunteers that represent
>     different parts of the ICANN community and are geographically and
>     experientially diverse. These volunteers will participate in the
>     development of methodologies and guidelines for future Holistic
>     Reviews.
>     The following skills and expertise needed were identified based on the
>     community-supported and Board-approved Terms of Reference
>     <https://community.icann.org/display/PHR/PHR+Home?preview=/329220199/330072289/PHR%20ToR_29%20April%202024.docx.pdf <https://community.icann.org/display/PHR/PHR+Home?preview=/329220199/330072289/PHR%20ToR_29%20April%202024.docx.pdf>>:
> 
>      ? ?* Performance assessment and audits of organizational effectiveness
>      ? ? ?and governance
> 
>      ? ?* Development of methodologies and guidelines for process
>     improvement
>      ? ? ?and measurement
>      ? ?* Data analysis informing fact-based findings and recommendations
>      ? ?* Familiarity with ICANN Reviews, and ICANN structures
>      ? ?* Knowledge of recognized frameworks for organizational excellence
>      ? ?* Principles of accountability applicable to organizations broadly
>      ? ? ?similar to ICANN
> 
>     In addition to the above skills and expertise, all selected review team
>     members are expected to actively participate for the duration of the
>     review, anticipated to start in September 2024 and last for up to 14
>     months.
> 
>     _______________________________________________
>     NCSG-EC mailing list
>     NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
>     https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
> 


From mesumbeslin at gmail.com  Sun May  5 23:38:34 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Mon, 6 May 2024 06:38:34 +1000
Subject: [NCSG-PC] FW: ICANN org PPSAI Org Implementation Leads PPSAI IRT
In-Reply-To: <b0ccaddc242f492da47e41ac1a751d39@amazon.com>
References: <b8998ddcfa57476c8fa3413f612e4f03@amazon.com>
 <b0ccaddc242f492da47e41ac1a751d39@amazon.com>
Message-ID: <CAM8DdeUANEGqec5PyBEzbEJWt8w7LcU6L-kY3hc7kRN4EBmMZQ@mail.gmail.com>

Hi folks,

During our April NCSG policy meeting, we discussed ICANN's plans to
resurrect the Privacy and Proxy Services Accreditation Issues (PPSAI)
Implementation Review Team (IRT) which was put on hold in 2019 due to
overlapping issues with ongoing work in the GNSO?s Expedited Policy
Development Process (EPDP) on the Temporary Specification, in light of the
work to address the European Union General Data Protection Regulation
(GDPR).

Here is a draft Call for Volunteers to restart work on the PPSAI
recommendations and ?threshold questions? ICANN plans to ask the
reconstituted IRT before proceeding with formal implementation, which ICANN
is seeking comments on by May 8th. My apologies for the short notice.

Let the list here know please if you identify any areas to comment and what
the comments are ASAP for potential discussion here before the deadline and
we can submit it.

Warmly,
Tomslin



---------- Forwarded message ---------
From: DiBiase, Gregory via council <council at icann.org>
Date: Fri, 3 May 2024 at 04:53
Subject: [council] FW: ICANN org PPSAI Org Implementation Leads & GNSO
Council Liaisons to the PPSAI IRT | Thursday 04 April 2024
To: council at gnso.icann.org <council at gnso.icann.org>


Dear Councilors,



Attached is ICANN?s draft Call for Volunteers to restart work on the PPSAI
recommendations.  Below are the ?threshold questions? ICANN plans to ask
the reconstituted IRT before proceeding with formal implementation.  Please
note that ICANN is requesting feedback from any interested stakeholder
groups by 8 May (see below).  Leadership will add this topic as an AOB in
our May meeting to capture any comments or concerns Councilors may have.





*Threshold Questions*

   1. Are there any policy questions or items IRT already wants to bring to
   Council for guidance?


   1. Submit Recommendation Number or Final Report text



   2. Implementation Model:  Accreditation Program or Alternative
   Implementation


   1. Can an implementation model without a formal accreditation program
   remain consistent with the policy recommendations?


   3. Disclosure Frameworks (Intellectual Property and Law Enforcement)


   1. Are there specific areas to revisit under new law/policy (org to
   share assessment, IRT to review)?
   2. Can these frameworks be aligned with existing work on RDRS,
   Registration Data Policy, and other existing procedures. and remain
   consistent with the policy recommendations?





*From:* Karen Lentz <karen.lentz at icann.org>
*Sent:* Wednesday, May 1, 2024 4:10 PM
*To:* DiBiase, Gregory <dibiase at amazon.com>; 'Stephanie Perrin' <
stephanie.perrin at mail.utoronto.ca>; Paul McGrady <paul at elstermcgrady.com>
*Cc:* gnso-secs at icann.org; Terri Agnew <terri.agnew at icann.org>; Dennis
Chang <dennis.chang at icann.org>; Caitlin Tubergen <caitlin.tubergen at icann.org>;
Feodora Hamza <feodora.hamza at icann.org>
*Subject:* RE: [EXTERNAL] [Ext] RE: Meeting Summary | ICANN org PPSAI Org
Implementation Leads & GNSO Council Liaisons to the PPSAI IRT | Thursday 04
April 2024



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



Hello all,



Further to the below, attached is the draft Call for Volunteers for the
PPSAI recommendations.  Please feel free to share with the Council and/or
any interested stakeholder groups as you find appropriate.  Please direct
any feedback or questions to dennis.chang at icann.org ? and would be most
helpful by Wednesday, *8 May.  *If more time is needed let us know -- we
are aiming to have the IRT convened in time to have the first meeting in
Kigali.



Best regards,

Karen



GNSO Master Calendar
<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_group-2Dactivities_calendar&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=-L6chFfv0OperrXHHpTF722WnH3FZIutn4cS16IvpOg&e=>

_______________________________________________
council mailing list -- council at icann.org
To unsubscribe send an email to council-leave at icann.org

_______________________________________________
By submitting your personal data, you consent to the processing of your
personal data for purposes of subscribing to this mailing list accordance
with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
the website Terms of Service (https://www.icann.org/privacy/tos). You can
visit the Mailman link above to change your membership status or
configuration, including unsubscribing, setting digest-style delivery or
disabling delivery altogether (e.g., for a vacation), and so on.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240506/8ac3baa1/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DRAFT-Call-for-Volunteers-PPSAI-1may24.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 14039 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240506/8ac3baa1/attachment.docx>

From emmanuelvitus at gmail.com  Tue May  7 18:03:37 2024
From: emmanuelvitus at gmail.com (Emmanuel Vitus)
Date: Tue, 7 May 2024 15:03:37 +0000
Subject: [NCSG-PC] NCSG Public comment on Phase 2 Initial Report of the
 EPDP on IDNs
In-Reply-To: <CAGSP6RQfv411kGPev+iSacLHk50nN2K1fabvkUiHS=qCAPXYRw@mail.gmail.com>
References: <CAGKde+2e3W5j4hta40HVVWjwiq2sKrcsiChRTrtPKEnEvdY55w@mail.gmail.com>
 <CAGSP6RQfv411kGPev+iSacLHk50nN2K1fabvkUiHS=qCAPXYRw@mail.gmail.com>
Message-ID: <CAGKde+3YPxL5d3xjhYijYX4=6riqLOmpUcb4Yq0rUj8Y5oFvOQ@mail.gmail.com>

Hello Pedro,
Thank you for your detailed insights. I appreciate your perspective on the
potential expansion of TMCH's tools and the implications it could have for
different stakeholders.
I've attached a few materials specifically addressing the "F1 Charter
Question on TMCH" that should help clarify some of the issues you've
raised. My hope is that these documents will enlighten your opinion on the
question and enrich your contribution to the comment.
I remain available for further discussion and am keen to hear more of your
thoughts, as well as those from other experts in the list and our lawyers
in the house, to shed further light on these complex issues.
Cordialement,
Emmanuel

Le dim. 5 mai 2024 ? 23:21, Pedro de Perdig?o Lana <
pedrodeperdigaolana at gmail.com> a ?crit :

> Dear Emmanuel,
>
> Thank you very much for sharing the document. It's clear and helpful in
> explaining the issues you identified.
>
> However, if you can, I'd like some more info regarding the "F1 Charter
> Question on TMCH." Expanding the scope of TMCH's tools, which seems to
> favor intellectual property rightsholders (IMHO), may raise a few concerns,
> especially if our comment in favor of expanding this protection would not
> align us with the positions traditionally advanced by the IPC and opposed
> by the NCSG. While the current wording might negatively impact some
> non-profits and non-commercial entities, it appears to me that private
> companies with significant IP investments would likely benefit most from
> such an expansion - and IP rights have been instrumentalized, at times,
> against good-faith registrants due to the interpretation margins around IP
> infringement, which can pose a risk to online freedom of expression. Making
> this interpretation margin larger is something that usually worries me.
>
> But I would like to hear your opinion on this, because I may just be
> inadequately extending a piece of the logic around DNS x IP to a different
> context where it does not fit well.
> Cordially,
>
> *Pedro de Perdig?o Lana*
> Lawyer <https://www.nic.br/>, GEDAI/UFPR <https://www.gedai.com.br/>
> Researcher
> PhD Candidate (UFPR), LLM in Business Law (UCoimbra)
> Board Member @ CC Brasil <https://br.creativecommons.net/>, ISOC BR
> <https://isoc.org.br/> and IODA <https://ioda.org.br/>
> This message is restricted to the sender and recipient(s). If received by
> mistake, please reply informing it.
>
>
> Em qua., 1 de mai. de 2024 ?s 10:13, Emmanuel Vitus <
> emmanuelvitus at gmail.com> escreveu:
>
>> Dear Comrades,
>> As the NCSG representative in the IDNs EPDP discussions, I am seeking
>> your feedback on the GNSO EPDP Phase 2 Initial Report on Internationalized
>> Domain Names, specifically concerning second-level variant management for
>> NCSG public comment.
>>
>>  I found most of the report straightforward. However, I've identified
>> three specific areas that appear to require further review and
>> consideration.
>>
>> *Implementation Guidance 15: *This guideline proposes a standard
>> approach allowing registries or registrars to enhance services such as
>> RDDS. These services could offer comprehensive data about a domain and its
>> variants, possibly through advanced methods like bulk services. I suggest
>> these enhancements should remain optional and be tightly regulated to
>> ensure privacy and security.
>>
>> *F1 Charter Question on TMCH:* The current "exact match" rules under the
>> Trademark Clearinghouse (TMCH) are too restrictive and could hinder
>> organizations whose names vary due to linguistic or branding changes. I
>> propose extending this rule to include "substantial matches," allowing
>> better protection for the intellectual properties of entities/orgs across
>> various regions and languages.
>>
>> *Document Readability: *Although the report is well-structured, its
>> technical and legal jargon could be a barrier for non-commercial
>> stakeholders unfamiliar with domain name systems or trademark law. The
>> readability analysis shows a Flesch-Kincaid Grade Level of 12.96 and a
>> Gunning Fog Index of 16.37, indicating a high complexity level.
>>
>> These are my primary concerns, though there may be other issues I'm not
>> aware of or you may disagree with my points. Please review the attached
>> document
>> <https://docs.google.com/document/d/1oeuAYEt-HHIaaD39rX-xRq5uRey2OPZ88z6VBXTPi7g/edit?usp=sharing>
>> containing my detailed comments and let me know your thoughts.
>>
>> Feel free to reach out directly if you have any questions or need further
>> clarification. Colleagues  Akinremi Peter Taiwo,  Grace Githaiga, and Maju
>> are also monitoring this report and can assist with any inquiries. Great if
>> we can have all comments or questions by May 8, 2024.
>>
>> Thank you for your attention and input.
>>
>> Best regards,
>>
>> Emmanuel
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240507/86131e7c/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: EPDP IDNs F1 Charter Question.pdf
Type: application/pdf
Size: 902472 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240507/86131e7c/attachment.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Final Draft Report-TMCH & IDN Variant Research Report .pdf
Type: application/pdf
Size: 1312392 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240507/86131e7c/attachment-0001.pdf>

From mesumbeslin at gmail.com  Mon May 13 12:26:59 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Mon, 13 May 2024 19:26:59 +1000
Subject: [NCSG-PC] REMINDER-Meeting Invitation | NCSG Policy Call |
 Monday, 13 May 2024 at 11:30 UTC
In-Reply-To: <45B89469-A3DE-4992-A46D-E2E962B82BA6@icann.org>
References: <45B89469-A3DE-4992-A46D-E2E962B82BA6@icann.org>
Message-ID: <CAM8DdeU19t7DQ2wBnb9Xb1MGGKHajtLm6wN4COw8Yqg1teVYSA@mail.gmail.com>

Hi PC members,

I thought i should let you know that I am unfortunately not feeling well
today. I have requested that a councillor chair the meeting in my absence.

Here is the agenda that I had:

https://docs.google.com/document/d/10dWjCcu_J2cBc9ofx46gMe6v7pENAjmOKhV99CjTLzI/edit?usp=sharing

Warmly,
Tomslin

On Thu, 9 May 2024, 23:23 Andrea Glandon, <andrea.glandon at icann.org> wrote:

> Dear all,
>
>
>
> *The next NCSG Policy Committee call will be held on Monday, 13 May 2024
> at 11:30 UTC.* Check your time zone here [timeanddate.com]
> <https://urldefense.com/v3/__https:/www.timeanddate.com/worldclock/fixedtime.html?msg=NCSG*PC&iso=20240513T1130&p1=1440&ah=1&am=30__;Kw!!PtGJab4!-qnnYzad_0FCPWqEoQY3Jj5DBvtGSTx9M0iQyrRNaryYt46RDOmppVwxuIJeKDaQp4c1tj9HTXCwKONemofsgJRx3evFzYY0--8$>
> .
>
>
>
> *Agenda: **https://docs.google.com/document/d/1vMhE9f1ns8lyH1YyOtDO1i3ITcLddR3_fu2Q-sYR-Bs/edit?usp=sharing
> [docs.google.com]*
> <https://urldefense.com/v3/__https:/docs.google.com/document/d/1vMhE9f1ns8lyH1YyOtDO1i3ITcLddR3_fu2Q-sYR-Bs/edit?usp=sharing__;!!PtGJab4!9DrHtJU4nTDeN3zUR4JaYopDTyRH6NC5c-Qv1KyxvWE9pLg8IkNanBA4rGBJ3eSlRrQv1zGKXOWGEPn1XcbIz72g3Qb1xiHcut8$>
>
>
>
> Join details are attached and noted below for your convenience.
>
>
>
> Join Zoom Meeting: *https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09
> [icann.zoom.us]*
> <https://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]
> <https://urldefense.com/v3/__https:/icann.zoom.us/u/ayKmeftWg__;!!PtGJab4!89jS1o75blcYjx01179eBM7Q0Er-lA5anQXpQIKL7VjWzU6Yy-h2o6sS4YvHIbDhtF0xH2toJXUpOFNQkhQTqGy3yig2JxoC$>
>
> Meeting ID: 988 7818 9584
>
> Phone only Passcode: 7740925615
>
>
>
> Best,
>
> Andrea & Dan
>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240513/6b4d7f0d/attachment.htm>

From Kathy at KathyKleiman.com  Mon May 13 16:51:39 2024
From: Kathy at KathyKleiman.com (Kathy Kleiman)
Date: Mon, 13 May 2024 09:51:39 -0400
Subject: [NCSG-PC] Position on Singulars and Plurals/ Council SubPro Small
 Team Plus reconvenes today!
Message-ID: <119a282f-a9cc-421a-82f8-f90b843bd273@KathyKleiman.com>

All,

Great meeting today!? The Council SubPro Small Team Plus group is 
reconvening to look at singulars and plurals. I see the Board's point 
(that .mice and .mouse, for example, are very different words and can 
easily be registered by very different applicants).

I see the Registry's concern that .ant and .ants are very similar and 
might create confusion.

However, I note that .com and .co co-exist and have done so now for well 
over a decade (with .co not only continuing to exist, but actually 
marketing to compete with .com domain names/be an alternate if you can't 
get the .com you want).

/Tomslin/Julf/All, do you want to elevate me to being a "subject matter 
expert" as the SubPro Small Team Plus (with subject matter experts) 
reconvenes? /Namra and Reema joined us for the Applicant Support issues 
and did a great job... and now head to law school graduation and first jobs.

Best, Kathy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240513/5efeca17/attachment.htm>

From manju at nii.org.tw  Tue May 14 04:25:13 2024
From: manju at nii.org.tw (=?UTF-8?B?6Zmz5pu86Iy5IE1hbmp1IENoZW4=?=)
Date: Tue, 14 May 2024 09:25:13 +0800
Subject: [NCSG-PC] Position on Singulars and Plurals/ Council SubPro
 Small Team Plus reconvenes today!
In-Reply-To: <119a282f-a9cc-421a-82f8-f90b843bd273@KathyKleiman.com>
References: <119a282f-a9cc-421a-82f8-f90b843bd273@KathyKleiman.com>
Message-ID: <CAMeQZi21=obFsPTb2QqSVCT7ENP32_SPwKXoe0a+LKxf7c=23Q@mail.gmail.com>

we'd be lucky to have Kathy as our subject matter expert on the small team
plus!

Best,
Manju



On Mon, May 13, 2024 at 9:51?PM Kathy Kleiman <Kathy at kathykleiman.com>
wrote:

> All,
>
> Great meeting today!  The Council SubPro Small Team Plus group is
> reconvening to look at singulars and plurals. I see the Board's point (that
> .mice and .mouse, for example, are very different words and can easily be
> registered by very different applicants).
>
> I see the Registry's concern that .ant and .ants are very similar and
> might create confusion.
>
> However, I note that .com and .co co-exist and have done so now for well
> over a decade (with .co not only continuing to exist, but actually
> marketing to compete with .com domain names/be an alternate if you can't
> get the .com you want).
>
> *Tomslin/Julf/All, do you want to elevate me to being a "subject matter
> expert" as the SubPro Small Team Plus (with subject matter experts)
> reconvenes?  *Namra and Reema joined us for the Applicant Support issues
> and did a great job... and now head to law school graduation and first jobs.
>
> Best, 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: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240514/09e98e81/attachment.htm>

From wisdom.dk at gmail.com  Tue May 14 09:05:00 2024
From: wisdom.dk at gmail.com (Wisdom Donkor)
Date: Tue, 14 May 2024 06:05:00 +0000
Subject: [NCSG-PC] Position on Singulars and Plurals/ Council SubPro
 Small Team Plus reconvenes today!
In-Reply-To: <CAMeQZi21=obFsPTb2QqSVCT7ENP32_SPwKXoe0a+LKxf7c=23Q@mail.gmail.com>
References: <119a282f-a9cc-421a-82f8-f90b843bd273@KathyKleiman.com>
 <CAMeQZi21=obFsPTb2QqSVCT7ENP32_SPwKXoe0a+LKxf7c=23Q@mail.gmail.com>
Message-ID: <CAAU+vPE6aJr1p3c72cc6L4Lx4G9DJ8xuH+vgJW6WC8fZQ5E+cA@mail.gmail.com>

In agreement with you Manju.

On Tue, 14 May 2024, 1:25?am ??? Manju Chen, <manju at nii.org.tw> wrote:

> we'd be lucky to have Kathy as our subject matter expert on the small team
> plus!
>
> Best,
> Manju
>
>
>
> On Mon, May 13, 2024 at 9:51?PM Kathy Kleiman <Kathy at kathykleiman.com>
> wrote:
>
>> All,
>>
>> Great meeting today!  The Council SubPro Small Team Plus group is
>> reconvening to look at singulars and plurals. I see the Board's point (that
>> .mice and .mouse, for example, are very different words and can easily be
>> registered by very different applicants).
>>
>> I see the Registry's concern that .ant and .ants are very similar and
>> might create confusion.
>>
>> However, I note that .com and .co co-exist and have done so now for well
>> over a decade (with .co not only continuing to exist, but actually
>> marketing to compete with .com domain names/be an alternate if you can't
>> get the .com you want).
>>
>> *Tomslin/Julf/All, do you want to elevate me to being a "subject matter
>> expert" as the SubPro Small Team Plus (with subject matter experts)
>> reconvenes?  *Namra and Reema joined us for the Applicant Support issues
>> and did a great job... and now head to law school graduation and first jobs.
>>
>> Best, Kathy
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240514/5c087134/attachment.htm>

From mesumbeslin at gmail.com  Tue May 14 10:33:46 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Tue, 14 May 2024 17:33:46 +1000
Subject: [NCSG-PC] Position on Singulars and Plurals/ Council SubPro
 Small Team Plus reconvenes today!
In-Reply-To: <119a282f-a9cc-421a-82f8-f90b843bd273@KathyKleiman.com>
References: <119a282f-a9cc-421a-82f8-f90b843bd273@KathyKleiman.com>
Message-ID: <CAM8DdeVUcnj8Oc2NdVApsEVNaGQ7bNQaksgocP4dqZXP0d3djw@mail.gmail.com>

Would absolutely love to. If PC agrees, as I see Manju and Wissom already
in agreement,  I will inform the small teams Plus leadership.

Warmly,
Tomslin

On Mon, 13 May 2024, 23:51 Kathy Kleiman, <Kathy at kathykleiman.com> wrote:

> All,
>
> Great meeting today!  The Council SubPro Small Team Plus group is
> reconvening to look at singulars and plurals. I see the Board's point (that
> .mice and .mouse, for example, are very different words and can easily be
> registered by very different applicants).
>
> I see the Registry's concern that .ant and .ants are very similar and
> might create confusion.
>
> However, I note that .com and .co co-exist and have done so now for well
> over a decade (with .co not only continuing to exist, but actually
> marketing to compete with .com domain names/be an alternate if you can't
> get the .com you want).
>
> *Tomslin/Julf/All, do you want to elevate me to being a "subject matter
> expert" as the SubPro Small Team Plus (with subject matter experts)
> reconvenes?  *Namra and Reema joined us for the Applicant Support issues
> and did a great job... and now head to law school graduation and first jobs.
>
> Best, 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: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240514/480afb0c/attachment.htm>

From julf at Julf.com  Tue May 14 12:40:11 2024
From: julf at Julf.com (Johan Helsingius)
Date: Tue, 14 May 2024 11:40:11 +0200
Subject: [NCSG-PC] Position on Singulars and Plurals/ Council SubPro
 Small Team Plus reconvenes today!
In-Reply-To: <CAM8DdeVUcnj8Oc2NdVApsEVNaGQ7bNQaksgocP4dqZXP0d3djw@mail.gmail.com>
References: <119a282f-a9cc-421a-82f8-f90b843bd273@KathyKleiman.com>
 <CAM8DdeVUcnj8Oc2NdVApsEVNaGQ7bNQaksgocP4dqZXP0d3djw@mail.gmail.com>
Message-ID: <f3ccbe16-225f-41c9-8f8c-c7767dd9a8c7@Julf.com>

Full support from me too!

	Julf


On 14/05/2024 09:33, Tomslin Samme-Nlar wrote:
> Would absolutely love to. If PC agrees, as I see Manju and Wissom 
> already in agreement,? I will inform the small teams Plus leadership.
> 
> Warmly,
> Tomslin
> 
> On Mon, 13 May 2024, 23:51 Kathy Kleiman, <Kathy at kathykleiman.com 
> <mailto:Kathy at kathykleiman.com>> wrote:
> 
>     __
> 
>     All,
> 
>     Great meeting today!? The Council SubPro Small Team Plus group is
>     reconvening to look at singulars and plurals. I see the Board's
>     point (that .mice and .mouse, for example, are very different words
>     and can easily be registered by very different applicants).
> 
>     I see the Registry's concern that .ant and .ants are very similar
>     and might create confusion.
> 
>     However, I note that .com and .co co-exist and have done so now for
>     well over a decade (with .co not only continuing to exist, but
>     actually marketing to compete with .com domain names/be an alternate
>     if you can't get the .com you want).
> 
>     /Tomslin/Julf/All, do you want to elevate me to being a "subject
>     matter expert" as the SubPro Small Team Plus (with subject matter
>     experts) reconvenes? /Namra and Reema joined us for the Applicant
>     Support issues and did a great job... and now head to law school
>     graduation and first jobs.
> 
>     Best, Kathy
> 
>     _______________________________________________
>     NCSG-PC mailing list
>     NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>     https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
> 
> 
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc


From compsoftnet at gmail.com  Tue May 14 13:52:48 2024
From: compsoftnet at gmail.com (Akinremi Peter Taiwo)
Date: Tue, 14 May 2024 06:52:48 -0400
Subject: [NCSG-PC] Position on Singulars and Plurals/ Council SubPro
 Small Team Plus reconvenes today!
In-Reply-To: <119a282f-a9cc-421a-82f8-f90b843bd273@KathyKleiman.com>
References: <119a282f-a9cc-421a-82f8-f90b843bd273@KathyKleiman.com>
Message-ID: <CAGK4d09vdaXyD1MMC1M_76RkN_oBmvueWxsxgTvsi8x9_wo2rw@mail.gmail.com>

Thanks Kathy.

Let's proceed accordingly.

Kind regards

On Mon, 13 May 2024, 9:51 am Kathy Kleiman, <Kathy at kathykleiman.com> wrote:

> All,
>
> Great meeting today!  The Council SubPro Small Team Plus group is
> reconvening to look at singulars and plurals. I see the Board's point (that
> .mice and .mouse, for example, are very different words and can easily be
> registered by very different applicants).
>
> I see the Registry's concern that .ant and .ants are very similar and
> might create confusion.
>
> However, I note that .com and .co co-exist and have done so now for well
> over a decade (with .co not only continuing to exist, but actually
> marketing to compete with .com domain names/be an alternate if you can't
> get the .com you want).
>
> *Tomslin/Julf/All, do you want to elevate me to being a "subject matter
> expert" as the SubPro Small Team Plus (with subject matter experts)
> reconvenes?  *Namra and Reema joined us for the Applicant Support issues
> and did a great job... and now head to law school graduation and first jobs.
>
> Best, 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: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240514/b5409109/attachment.htm>

From emmanuelvitus at gmail.com  Tue May 14 13:56:40 2024
From: emmanuelvitus at gmail.com (Emmanuel Vitus)
Date: Tue, 14 May 2024 10:56:40 +0000
Subject: [NCSG-PC] Position on Singulars and Plurals/ Council SubPro
 Small Team Plus reconvenes today!
In-Reply-To: <CAGK4d09vdaXyD1MMC1M_76RkN_oBmvueWxsxgTvsi8x9_wo2rw@mail.gmail.com>
References: <119a282f-a9cc-421a-82f8-f90b843bd273@KathyKleiman.com>
 <CAGK4d09vdaXyD1MMC1M_76RkN_oBmvueWxsxgTvsi8x9_wo2rw@mail.gmail.com>
Message-ID: <CAGKde+1+Xh5Hdqabu+7FY7tSg56vd14sktLOpF=P_orBLo4WQw@mail.gmail.com>

My full support! We are lucky to have Kathy!

Sent from iPhone. Excuse brevity and typos.


On Tue 14 May 2024 at 10:53, Akinremi Peter Taiwo <compsoftnet at gmail.com>
wrote:

> Thanks Kathy.
>
> Let's proceed accordingly.
>
> Kind regards
>
> On Mon, 13 May 2024, 9:51 am Kathy Kleiman, <Kathy at kathykleiman.com>
> wrote:
>
>> All,
>>
>> Great meeting today!  The Council SubPro Small Team Plus group is
>> reconvening to look at singulars and plurals. I see the Board's point (that
>> .mice and .mouse, for example, are very different words and can easily be
>> registered by very different applicants).
>>
>> I see the Registry's concern that .ant and .ants are very similar and
>> might create confusion.
>>
>> However, I note that .com and .co co-exist and have done so now for well
>> over a decade (with .co not only continuing to exist, but actually
>> marketing to compete with .com domain names/be an alternate if you can't
>> get the .com you want).
>>
>> *Tomslin/Julf/All, do you want to elevate me to being a "subject matter
>> expert" as the SubPro Small Team Plus (with subject matter experts)
>> reconvenes?  *Namra and Reema joined us for the Applicant Support issues
>> and did a great job... and now head to law school graduation and first jobs.
>>
>> Best, Kathy
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240514/ec4f4eaa/attachment.htm>

From wisdom.dk at gmail.com  Tue May 14 13:59:52 2024
From: wisdom.dk at gmail.com (Wisdom Donkor)
Date: Tue, 14 May 2024 10:59:52 +0000
Subject: [NCSG-PC] Position on Singulars and Plurals/ Council SubPro
 Small Team Plus reconvenes today!
In-Reply-To: <CAGK4d09vdaXyD1MMC1M_76RkN_oBmvueWxsxgTvsi8x9_wo2rw@mail.gmail.com>
References: <119a282f-a9cc-421a-82f8-f90b843bd273@KathyKleiman.com>
 <CAGK4d09vdaXyD1MMC1M_76RkN_oBmvueWxsxgTvsi8x9_wo2rw@mail.gmail.com>
Message-ID: <CAAU+vPHiptq23raUvON69Oi83eq=90UyR0iRs5BF9fwhCH--mw@mail.gmail.com>

Yes for me, let's proceed.

On Tue, 14 May 2024, 10:53?am Akinremi Peter Taiwo, <compsoftnet at gmail.com>
wrote:

> Thanks Kathy.
>
> Let's proceed accordingly.
>
> Kind regards
>
> On Mon, 13 May 2024, 9:51 am Kathy Kleiman, <Kathy at kathykleiman.com>
> wrote:
>
>> All,
>>
>> Great meeting today!  The Council SubPro Small Team Plus group is
>> reconvening to look at singulars and plurals. I see the Board's point (that
>> .mice and .mouse, for example, are very different words and can easily be
>> registered by very different applicants).
>>
>> I see the Registry's concern that .ant and .ants are very similar and
>> might create confusion.
>>
>> However, I note that .com and .co co-exist and have done so now for well
>> over a decade (with .co not only continuing to exist, but actually
>> marketing to compete with .com domain names/be an alternate if you can't
>> get the .com you want).
>>
>> *Tomslin/Julf/All, do you want to elevate me to being a "subject matter
>> expert" as the SubPro Small Team Plus (with subject matter experts)
>> reconvenes?  *Namra and Reema joined us for the Applicant Support issues
>> and did a great job... and now head to law school graduation and first jobs.
>>
>> Best, Kathy
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240514/70bff419/attachment.htm>

From Kathy at KathyKleiman.com  Tue May 14 15:46:29 2024
From: Kathy at KathyKleiman.com (Kathy Kleiman)
Date: Tue, 14 May 2024 08:46:29 -0400
Subject: [NCSG-PC] Position on Singulars and Plurals/ Council SubPro
 Small Team Plus reconvenes today!
In-Reply-To: <CAM8DdeVUcnj8Oc2NdVApsEVNaGQ7bNQaksgocP4dqZXP0d3djw@mail.gmail.com>
References: <119a282f-a9cc-421a-82f8-f90b843bd273@KathyKleiman.com>
 <CAM8DdeVUcnj8Oc2NdVApsEVNaGQ7bNQaksgocP4dqZXP0d3djw@mail.gmail.com>
Message-ID: <7ab70baa-54ec-40be-be91-c80a298d7f20@KathyKleiman.com>

Many thanks to everyone for your kind messages!?? I will soon be 
elevated from the status of Observer to Participant :-).

If you have any thoughts on plurals and singulars, please let me know. I 
am not as concerned about this issue as other issues. I see .CO and .COM 
coexisting and they are only one letter apart. I can certainly see .FOX 
and .FOXES? coexisting if .FOX is the .BRAND of Fox Media and .FOXES as 
a open gTLD marketing itself to "cool people" and dating organizations. 
I welcome your thoughts!

Best regards,

Kathy

On 5/14/2024 3:33 AM, Tomslin Samme-Nlar wrote:
> Would absolutely love to. If PC agrees, as I see Manju and Wissom 
> already in agreement,? I will inform the small teams Plus leadership.
>
> Warmly,
> Tomslin
>
> On Mon, 13 May 2024, 23:51 Kathy Kleiman, <Kathy at kathykleiman.com> wrote:
>
>     All,
>
>     Great meeting today!? The Council SubPro Small Team Plus group is
>     reconvening to look at singulars and plurals. I see the Board's
>     point (that .mice and .mouse, for example, are very different
>     words and can easily be registered by very different applicants).
>
>     I see the Registry's concern that .ant and .ants are very similar
>     and might create confusion.
>
>     However, I note that .com and .co co-exist and have done so now
>     for well over a decade (with .co not only continuing to exist, but
>     actually marketing to compete with .com domain names/be an
>     alternate if you can't get the .com you want).
>
>     /Tomslin/Julf/All, do you want to elevate me to being a "subject
>     matter expert" as the SubPro Small Team Plus (with subject matter
>     experts) reconvenes? /Namra and Reema joined us for the Applicant
>     Support issues and did a great job... and now head to law school
>     graduation and first jobs.
>
>     Best, 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: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240514/94f6d31c/attachment.htm>

From Kathy at KathyKleiman.com  Tue May 21 01:33:44 2024
From: Kathy at KathyKleiman.com (Kathy Kleiman)
Date: Mon, 20 May 2024 18:33:44 -0400
Subject: [NCSG-PC] Comment on IDN EPDP Report - DUE TOMORROW (5/21)
Message-ID: <6a78f859-d721-4b00-bd0a-0d868527c7aa@KathyKleiman.com>

Dear Tomslin and Members of the Policy Committee,

I would like to submit for review the comment written by Emmanuel Vitus 
for /Phase 2 Initial Report of the EPDP on Internationalized Domain Names./

In writing this comment, Emmanuel sought input widely, meeting with 
Pedro and me to discuss the Trademark Clearinghouse and 
trademark/noncommercial speech issues, and holding a discussion with 
Daniel Gluck and me about the intent of some oddly-worded provisions 
regarding the WHOIS/RDS and RDDS.? You will see he has asked for a 
clarification of these draft report paragraphs, and reshared our deep 
concern for privacy.

IDNs and their variants are hard material!? Tx to Emmanuel for guiding 
us through!

*Tomslin, these comments are due tomorrow by, 5/21 by 23:59pm UTC. *In 
light of Emmanuel's input from NCSG, and redrafting and editing to 
incorporate this input, I would ask that the Policy Committee approve 
these comments for timely submission.

Best and tx,

Kathy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240520/10678f99/attachment.htm>

From mesumbeslin at gmail.com  Tue May 21 03:28:55 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Tue, 21 May 2024 10:28:55 +1000
Subject: [NCSG-PC] Comment on IDN EPDP Report - DUE TOMORROW (5/21)
In-Reply-To: <6a78f859-d721-4b00-bd0a-0d868527c7aa@KathyKleiman.com>
References: <6a78f859-d721-4b00-bd0a-0d868527c7aa@KathyKleiman.com>
Message-ID: <CAM8DdeXCd2_dbtSv=6KL88J9wkmqhGOavF2EPWvDr=amobZn5w@mail.gmail.com>

Hi kathy,

Thanks for bringing this up to the top of my inbox. Inlight of the flood of
activities for council leadership and ICAN80 prep, I lost track of the
deadline, though I kept telling myself to check when this is due :-(

You are right, Emmanual sent the comment to members and PC a while ago and
there has not been any objection that I am aware of, so I'll assume
approved.

Warmly,
Tomslin



On Tue, 21 May 2024 at 08:33, Kathy Kleiman <Kathy at kathykleiman.com> wrote:

> Dear Tomslin and Members of the Policy Committee,
>
> I would like to submit for review the comment written by Emmanuel Vitus
> for *Phase 2 Initial Report of the EPDP on Internationalized Domain
> Names.*
>
> In writing this comment, Emmanuel sought input widely, meeting with Pedro
> and me to discuss the Trademark Clearinghouse and trademark/noncommercial
> speech issues, and holding a discussion with Daniel Gluck and me about the
> intent of some oddly-worded provisions regarding the WHOIS/RDS and RDDS.
> You will see he has asked for a clarification of these draft report
> paragraphs, and reshared our deep concern for privacy.
>
> IDNs and their variants are hard material!  Tx to Emmanuel for guiding us
> through!
>
> *Tomslin, these comments are due tomorrow by, 5/21 by 23:59pm UTC. *In
> light of Emmanuel's input from NCSG, and redrafting and editing to
> incorporate this input, I would ask that the Policy Committee approve these
> comments for timely submission.
>
> Best and tx,
>
> Kathy
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240521/6df9a241/attachment.htm>

From mesumbeslin at gmail.com  Tue May 21 04:01:08 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Tue, 21 May 2024 11:01:08 +1000
Subject: [NCSG-PC] Fwd: SPIRT Attendance record
In-Reply-To: <CANsVcEx4Ensb535oXoNXxsgdX-87R==QGRCNp6cFmgur6nrj-Q@mail.gmail.com>
References: <6f71db0799f04d20bc8ce68efbf57e8f@icann.org>
 <CAA5i5mckY9_5-nwSkkjGGgN7djhjuLvMiS5jtRjv52EWoR2dcw@mail.gmail.com>
 <CANsVcEx4Ensb535oXoNXxsgdX-87R==QGRCNp6cFmgur6nrj-Q@mail.gmail.com>
Message-ID: <CAM8DdeXR99qwObCpwgqtw1oL+M_SDCvSP6+MdxPARXsmRqntAw@mail.gmail.com>

Dear Farell and Bolutife,

Please read the below concern from the SPIRT leadership regarding
attendance.

Despite the general concern, I note that Bolu's attendance is above average
but it appears when you can't make it, no apologies are given. Can I
encourage you to please send apologies in advance to staff and leadership
when you genuinely can't make the meeting?

@Farell Folly <farellfolly at gmail.com>  Could you please let us know whether
your circumstances have changed and if the time and day of the meetings no
longer work for you so that we can assess together whether it makes sense
for someone else to attend the meetings in your place or not?

Warmly,
Tomslin


---------- Forwarded message ---------
From: Anne ICANN via council <council at icann.org>
Date: Tue, 21 May 2024 at 08:33
Subject: [council] Fwd: Attendance record
To: Terri Agnew via cou. <council at gnso.icann.org>, <gnso-spirt-dt at icann.org>


Dear Councilors,

I am providing an update on the SPIRT Charter Drafting Team work in my role
as Council Liaison.  With help from Steve and Saewon, we are making
progress but there are concerns regarding attendance.  Could you please
follow up with your respective stakeholder groups and constituencies to
encourage attendance and participation in this drafting process?  We need
broad participation in order to present the best possible output for
Council to review in July.

As mentioned in chat in our last Council meeting in relation to the Action
Decision Radar, there are some possible variations to the Sub Pro Final
Report Annex E Implementation Guidance being discussed by this team so it's
especially important for everyone who signed up to in fact participate.

Beyond those members represented on the Council per se, many thanks to Alan
Greenberg of the ALAC for acting as Vice Chair and bringing the issue of
poor attendance by some to our attention.   Thanks as well to Nigel Hickson
for his input into the Charter document and his participation in the
meetings on behalf of the GAC.  Special thanks to Nitin Walia for his able
chairing of the meetings!

Anne

Anne Aikman-Scalese
GNSO Councilor
NomCom Non-Voting 2022-2024
anneicanngnso at gmail.com


---------- Forwarded message ---------
From: Alan Greenberg <greenberg.alan at gmail.com>
Date: Mon, May 20, 2024 at 2:34?PM
Subject: Re: Attendance record
To: ICANN Policy Calendar <PolicyCalendar at icann.org>
Cc: nitin at data.in <nitin at data.in>, anneicanngnso at gmail.com <
anneicanngnso at gmail.com>, Steve Chan <steve.chan at icann.org>, Julie Hedlund <
julie.hedlund at icann.org>, Saewon Lee <saewon.lee at icann.org>, Julie Bisland <
julie.bisland at icann.org>, Devan Reed <devan.reed at icann.org>, Terri Agnew <
terri.agnew at icann.org>



_______________________________________________
council mailing list -- council at icann.org
To unsubscribe send an email to council-leave at icann.org

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

From mesumbeslin at gmail.com  Tue May 21 04:31:24 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Tue, 21 May 2024 11:31:24 +1000
Subject: [NCSG-PC] NCSG Public comment on Phase 2 Initial Report of the
 EPDP on IDNs
In-Reply-To: <CAGKde+3YPxL5d3xjhYijYX4=6riqLOmpUcb4Yq0rUj8Y5oFvOQ@mail.gmail.com>
References: <CAGKde+2e3W5j4hta40HVVWjwiq2sKrcsiChRTrtPKEnEvdY55w@mail.gmail.com>
 <CAGSP6RQfv411kGPev+iSacLHk50nN2K1fabvkUiHS=qCAPXYRw@mail.gmail.com>
 <CAGKde+3YPxL5d3xjhYijYX4=6riqLOmpUcb4Yq0rUj8Y5oFvOQ@mail.gmail.com>
Message-ID: <CAM8DdeVvA5v6XKbcxXdp86xtDTb4dCRuJ-JvTmCmti-yBm3qXg@mail.gmail.com>

Hi all,

Comment submitted and page updated here
https://community.icann.org/display/gnsononcomstake/Public+Comments+-+2024

Warmly,
Tomslin



On Wed, 8 May 2024 at 01:04, Emmanuel Vitus <emmanuelvitus at gmail.com> wrote:

> Hello Pedro,
> Thank you for your detailed insights. I appreciate your perspective on the
> potential expansion of TMCH's tools and the implications it could have for
> different stakeholders.
> I've attached a few materials specifically addressing the "F1 Charter
> Question on TMCH" that should help clarify some of the issues you've
> raised. My hope is that these documents will enlighten your opinion on the
> question and enrich your contribution to the comment.
> I remain available for further discussion and am keen to hear more of your
> thoughts, as well as those from other experts in the list and our lawyers
> in the house, to shed further light on these complex issues.
> Cordialement,
> Emmanuel
>
> Le dim. 5 mai 2024 ? 23:21, Pedro de Perdig?o Lana <
> pedrodeperdigaolana at gmail.com> a ?crit :
>
>> Dear Emmanuel,
>>
>> Thank you very much for sharing the document. It's clear and helpful in
>> explaining the issues you identified.
>>
>> However, if you can, I'd like some more info regarding the "F1 Charter
>> Question on TMCH." Expanding the scope of TMCH's tools, which seems to
>> favor intellectual property rightsholders (IMHO), may raise a few concerns,
>> especially if our comment in favor of expanding this protection would not
>> align us with the positions traditionally advanced by the IPC and opposed
>> by the NCSG. While the current wording might negatively impact some
>> non-profits and non-commercial entities, it appears to me that private
>> companies with significant IP investments would likely benefit most from
>> such an expansion - and IP rights have been instrumentalized, at times,
>> against good-faith registrants due to the interpretation margins around IP
>> infringement, which can pose a risk to online freedom of expression. Making
>> this interpretation margin larger is something that usually worries me.
>>
>> But I would like to hear your opinion on this, because I may just be
>> inadequately extending a piece of the logic around DNS x IP to a different
>> context where it does not fit well.
>> Cordially,
>>
>> *Pedro de Perdig?o Lana*
>> Lawyer <https://www.nic.br/>, GEDAI/UFPR <https://www.gedai.com.br/>
>> Researcher
>> PhD Candidate (UFPR), LLM in Business Law (UCoimbra)
>> Board Member @ CC Brasil <https://br.creativecommons.net/>, ISOC BR
>> <https://isoc.org.br/> and IODA <https://ioda.org.br/>
>> This message is restricted to the sender and recipient(s). If received by
>> mistake, please reply informing it.
>>
>>
>> Em qua., 1 de mai. de 2024 ?s 10:13, Emmanuel Vitus <
>> emmanuelvitus at gmail.com> escreveu:
>>
>>> Dear Comrades,
>>> As the NCSG representative in the IDNs EPDP discussions, I am seeking
>>> your feedback on the GNSO EPDP Phase 2 Initial Report on Internationalized
>>> Domain Names, specifically concerning second-level variant management for
>>> NCSG public comment.
>>>
>>>  I found most of the report straightforward. However, I've identified
>>> three specific areas that appear to require further review and
>>> consideration.
>>>
>>> *Implementation Guidance 15: *This guideline proposes a standard
>>> approach allowing registries or registrars to enhance services such as
>>> RDDS. These services could offer comprehensive data about a domain and its
>>> variants, possibly through advanced methods like bulk services. I suggest
>>> these enhancements should remain optional and be tightly regulated to
>>> ensure privacy and security.
>>>
>>> *F1 Charter Question on TMCH:* The current "exact match" rules under
>>> the Trademark Clearinghouse (TMCH) are too restrictive and could hinder
>>> organizations whose names vary due to linguistic or branding changes. I
>>> propose extending this rule to include "substantial matches," allowing
>>> better protection for the intellectual properties of entities/orgs across
>>> various regions and languages.
>>>
>>> *Document Readability: *Although the report is well-structured, its
>>> technical and legal jargon could be a barrier for non-commercial
>>> stakeholders unfamiliar with domain name systems or trademark law. The
>>> readability analysis shows a Flesch-Kincaid Grade Level of 12.96 and a
>>> Gunning Fog Index of 16.37, indicating a high complexity level.
>>>
>>> These are my primary concerns, though there may be other issues I'm not
>>> aware of or you may disagree with my points. Please review the attached
>>> document
>>> <https://docs.google.com/document/d/1oeuAYEt-HHIaaD39rX-xRq5uRey2OPZ88z6VBXTPi7g/edit?usp=sharing>
>>> containing my detailed comments and let me know your thoughts.
>>>
>>> Feel free to reach out directly if you have any questions or need
>>> further clarification. Colleagues  Akinremi Peter Taiwo,  Grace Githaiga,
>>> and Maju are also monitoring this report and can assist with any
>>> inquiries. Great if we can have all comments or questions by May 8, 2024.
>>>
>>> Thank you for your attention and input.
>>>
>>> Best regards,
>>>
>>> Emmanuel
>>>
>> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240521/adaee004/attachment.htm>

From adisabolutifeo at gmail.com  Tue May 21 08:44:02 2024
From: adisabolutifeo at gmail.com (Bolutife Adisa)
Date: Tue, 21 May 2024 07:44:02 +0200
Subject: [NCSG-PC] SPIRT Attendance record
In-Reply-To: <CAM8DdeXR99qwObCpwgqtw1oL+M_SDCvSP6+MdxPARXsmRqntAw@mail.gmail.com>
References: <CAM8DdeXR99qwObCpwgqtw1oL+M_SDCvSP6+MdxPARXsmRqntAw@mail.gmail.com>
Message-ID: <71820FD1-5948-4FDB-B1A4-EA3583F94902@gmail.com>

An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240521/94c44d30/attachment.htm>

From julf at julf.com  Tue May 21 23:08:32 2024
From: julf at julf.com (Johan Helsingius)
Date: Tue, 21 May 2024 22:08:32 +0200
Subject: [NCSG-PC] Fwd: [GNSO-SG-C-Leadership] Appointment of representative
 and alternate to the PPSAI IRT
In-Reply-To: <CB52871E-374F-48BF-97D7-D184C00AD654@contoso.com>
References: <CB52871E-374F-48BF-97D7-D184C00AD654@contoso.com>
Message-ID: <ee28ed26-ea0c-4aa3-ba5f-46e9aa43bcbf@julf.com>




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



Dear All,

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

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

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

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

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

Why Have Representatives?

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

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

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

-- 

Kind Regards,

Dennis S. Chang

GDD Programs Director

Phone: +1 213 293 7889

Sykpe: dennisSchang

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



From PolicyCalendar at icann.org  Wed May 22 00:02:45 2024
From: PolicyCalendar at icann.org (ICANN Policy Calendar)
Date: Tue, 21 May 2024 21:02:45 +0000
Subject: [NCSG-PC] NCSG Policy Call | 15 July at 11:30 UTC
Message-ID: <639b3eb15166435ea4d91f285e6d6457@icann.org>

Please join the NCSG Monthly Policy call on Monday, 15 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&#43;11

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

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

From PolicyCalendar at icann.org  Wed May 22 00:06:04 2024
From: PolicyCalendar at icann.org (ICANN Policy Calendar)
Date: Tue, 21 May 2024 21:06:04 +0000
Subject: [NCSG-PC] NCSG Policy Call | 05 August at 11:30 UTC
Message-ID: <4681abcfbe0d4429825597a54d2a281e@icann.org>

Please join the NCSG Monthly Policy call on Monday, 05 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&#43;11

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

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

From PolicyCalendar at icann.org  Wed May 22 00:07:24 2024
From: PolicyCalendar at icann.org (ICANN Policy Calendar)
Date: Tue, 21 May 2024 21:07:24 +0000
Subject: [NCSG-PC] NCSG Policy Call | 16 September at 11:30 UTC
Message-ID: <5bea96d4650a461e9508a8b9d1707422@icann.org>

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

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

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

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

From PolicyCalendar at icann.org  Wed May 22 00:08:52 2024
From: PolicyCalendar at icann.org (ICANN Policy Calendar)
Date: Tue, 21 May 2024 21:08:52 +0000
Subject: [NCSG-PC] NCSG Policy Call | 14 October at 11:30 UTC
Message-ID: <66758eff6df34baab51140794c107a57@icann.org>

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

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

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

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

From Kathy at KathyKleiman.com  Wed May 22 17:59:58 2024
From: Kathy at KathyKleiman.com (Kathy Kleiman)
Date: Wed, 22 May 2024 10:59:58 -0400
Subject: [NCSG-PC] Singulars/Plurals in New gTLDs and future rounds
Message-ID: <c2a3ea36-4b3d-4aa9-98c2-e51d7384a279@KathyKleiman.com>

To NCSG Policy Committee,

I have been asked to circulate the Singular/Plurals ideas of the SubPro 
Small Team Plus created by Council to reconcile recommendations of the 
SubPro Working Group rejected by the ICANN Board, 
*/https://docs.google.com/document/d/19AckdQ_GkPaqCkwcfWdnu8eSKK4YliRjYuP2iVBh4Vs/edit?usp=sharing 
/*

The problem is singular and plural gTLDs. In the First Round of New 
gTLDs, in 2012, singulars and plurals went forward. The idea was that 
one registry might use .SPRING for domain names about seasons and 
another might use .SPRINGS for metal coils. A wide use of words has 
always been NCSG?s position: that there are many meanings for words and 
we should allow them to flourish in domain names and gTLDs.

This is what the SubPro Working Group recommended, but the ICANN Board 
expressed concerns and said no. The Board worries that they will be 
forced to inquire too deeply into the ?content? of a future gTLD ? how 
it will be used ? rather than analyzing what the gTLD looks like only. 
As you know, ICANN cannot regulate ?content? under its new Bylaws.

The SubPro Small Team Plus returned to the Board and offered to put into 
the same contention set future plural such as .example and .examples ? 
these are likely ?confusingly similar? to Internet users and only one 
should be delegated. And singular/plurals must be in/the same language 
/(not across languages).

*/Please look at the Board?s current proposal, from the perspective of 
the languages we speak, and the similarities and differences of 
singulars and plurals, 
https://docs.google.com/document/d/19AckdQ_GkPaqCkwcfWdnu8eSKK4YliRjYuP2iVBh4Vs/edit?usp=sharing 
We will be debating this
"compromise proposal" (that comes from ICANN Org) on Tuesday at the next 
Small Team Plus meeting.
/*

Unfortunately, Jeff Neuman just added? language to remove future 
trademarked gTLDs (.BRANDS) from these rules completely. I am concerned 
as that would elevate commercial gTLD uses over noncommercial gTLD uses. 
I can envision a Liberty Gas Station (a chain in the US) that wants 
.LIBERTY and a noncommercial group that wants .LIBERTIES to promote 
rights in their countries and communities, and a few similar ones.? The 
noncommercial .LIBERTIES is blocked and the commercial .LIBERTY gas 
station goes forward. I know of no legal precedent for such a rule.

Please let me know your thoughts ? soon ?as the SubTeam meets again on 
Tuesday.

Best regards and tx,

Kathy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240522/9647c9fa/attachment.htm>

From emmanuelvitus at gmail.com  Wed May 22 21:03:35 2024
From: emmanuelvitus at gmail.com (Emmanuel Vitus)
Date: Wed, 22 May 2024 18:03:35 +0000
Subject: [NCSG-PC] Singulars/Plurals in New gTLDs and future rounds
In-Reply-To: <c2a3ea36-4b3d-4aa9-98c2-e51d7384a279@KathyKleiman.com>
References: <c2a3ea36-4b3d-4aa9-98c2-e51d7384a279@KathyKleiman.com>
Message-ID: <CAGKde+1cGeH3L6BpB4Rx8A2ZfX9LwQfAG9gRKFDFz1wzO6jhiw@mail.gmail.com>

Hi Kathy,
Thanks for sharing this.
I still don?t get why the Board worries that allowing singular and plural
forms of gTLDs will make them delve too much into ?content.? Were there any
practical examples of arguments given to support this concern?
I completely agree that delegations must be in the same language to avoid
confusion. For example, in Spanish, ?casa? (house) and ?casas? (houses)
shouldn?t both be delegated as gTLDs since they are simply singular and
plural forms of the same word. However, I agree that if they are just
homonyms, they should be allowed to be delegated. For instance, in English,
?bank? (financial institution) and ?bank? (side of a river) are homonyms
and could be delegated as they represent different meanings, but on a
first come first serve basis. Similarly, in French, ?cour? (court) and
?cours? (lessons) are homonyms and should be treated as separate entities.

I?m strongly against the proposal to exclude future trademarked gTLDs from
these rules. As you mentioned, there?s no legal precedent for such a rule,
and it clearly doesn?t favor non-commercial stakeholders. For instance, if
a commercial french entity applied for .SOLIDARITE (solidarity) as a brand,
a non-commercial organization wanting to use .SOLIDARITES (solidarities) to
promote unity and support in communities would be unfairly blocked.
Similarly, .LIBERTE (freedom) for a brand could block .LIBERTES (freedoms)
for a human rights organization. These examples show how such exclusions
could severely disadvantage non-commercial interests.

We should oppose this. Non-commercial entities often don?t have the
resources for trademarks or the priority given to them (as we discussed in
the recent Trademark Clearinghouse conversation regarding the IDNs EPDP
report). The internet should be for everyone. My 2cent.
Thanks.
Emmanuel Vitus

Le mer. 22 mai 2024 ? 15:00, Kathy Kleiman <Kathy at kathykleiman.com> a
?crit :

> To NCSG Policy Committee,
>
> I have been asked to circulate the Singular/Plurals ideas of the SubPro
> Small Team Plus created by Council to reconcile recommendations of the
> SubPro Working Group rejected by the ICANN Board, *https://docs.google.com/document/d/19AckdQ_GkPaqCkwcfWdnu8eSKK4YliRjYuP2iVBh4Vs/edit?usp=sharing
> <https://docs.google.com/document/d/19AckdQ_GkPaqCkwcfWdnu8eSKK4YliRjYuP2iVBh4Vs/edit?usp=sharing>
> *
>
> The problem is singular and plural gTLDs. In the First Round of New gTLDs,
> in 2012, singulars and plurals went forward. The idea was that one registry
> might use .SPRING for domain names about seasons and another might use
> .SPRINGS for metal coils. A wide use of words has always been NCSG?s
> position: that there are many meanings for words and we should allow them
> to flourish in domain names and gTLDs.
>
> This is what the SubPro Working Group recommended, but the ICANN Board
> expressed concerns and said no. The Board worries that they will be forced
> to inquire too deeply into the ?content? of a future gTLD ? how it will be
> used ? rather than analyzing what the gTLD looks like only. As you know,
> ICANN cannot regulate ?content? under its new Bylaws.
>
> The SubPro Small Team Plus returned to the Board and offered to put into
> the same contention set future plural such as .example and .examples ?
> these are likely ?confusingly similar? to Internet users and only one
> should be delegated. And singular/plurals must be in* the same language *(not
> across languages).
>
>
>
> *Please look at the Board?s current proposal, from the perspective of the
> languages we speak, and the similarities and differences of singulars and
> plurals,
> https://docs.google.com/document/d/19AckdQ_GkPaqCkwcfWdnu8eSKK4YliRjYuP2iVBh4Vs/edit?usp=sharing
> <https://docs.google.com/document/d/19AckdQ_GkPaqCkwcfWdnu8eSKK4YliRjYuP2iVBh4Vs/edit?usp=sharing>
> We will be debating this  "compromise proposal" (that comes from ICANN Org)
> on Tuesday at the next Small Team Plus meeting. *
>
> Unfortunately, Jeff Neuman just added  language to remove future
> trademarked gTLDs (.BRANDS) from these rules completely. I am concerned as
> that would elevate commercial gTLD uses over noncommercial gTLD uses. I can
> envision a Liberty Gas Station (a chain in the US) that wants .LIBERTY and
> a noncommercial group that wants .LIBERTIES to promote rights in their
> countries and communities, and a few similar ones.  The noncommercial
> .LIBERTIES is blocked and the commercial .LIBERTY gas station goes forward.
> I know of no legal precedent for such a rule.
>
> Please let me know your thoughts ? soon ?as the SubTeam meets again on
> Tuesday.
>
> Best regards and tx,
>
> 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: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240522/3bb46c1c/attachment.htm>

From Kathy at KathyKleiman.com  Wed May 22 22:43:31 2024
From: Kathy at KathyKleiman.com (Kathy Kleiman)
Date: Wed, 22 May 2024 15:43:31 -0400
Subject: [NCSG-PC] Singulars/Plurals in New gTLDs and future rounds
In-Reply-To: <CAGKde+1cGeH3L6BpB4Rx8A2ZfX9LwQfAG9gRKFDFz1wzO6jhiw@mail.gmail.com>
References: <c2a3ea36-4b3d-4aa9-98c2-e51d7384a279@KathyKleiman.com>
 <CAGKde+1cGeH3L6BpB4Rx8A2ZfX9LwQfAG9gRKFDFz1wzO6jhiw@mail.gmail.com>
Message-ID: <67f99a62-23db-4d5d-a138-3b00de078041@KathyKleiman.com>

Hi Emmanuel,

Tx you! Your response is very valuable. I am incorporating some of your 
examples into my writing to the Small Team now.

Yes, just like our recent TM Clearinghouse discussion!? And I am 
bringing in an IDN variant argument - thanks to our recent work together.

Best, Kathy

On 5/22/2024 2:03 PM, Emmanuel Vitus wrote:
>
> Hi Kathy,
> Thanks for sharing this.
> I still don?t get why the Board worries that allowing singular and 
> plural forms of gTLDs will make them delve too much into ?content.? 
> Were there any practical examples of arguments given to support this 
> concern?
> I completely agree that delegations must be in the same language to 
> avoid confusion. For example, in Spanish, ?casa? (house) and ?casas? 
> (houses) shouldn?t both be delegated as gTLDs since they are simply 
> singular and plural forms of the same word. However, I agree that if 
> they are just homonyms, they should be allowed to be delegated. For 
> instance, in English, ?bank? (financial institution) and ?bank? (side 
> of a river) are homonyms and could be delegated as they represent 
> different meanings, but on a first?come first serve basis. Similarly, 
> in French, ?cour? (court) and ?cours? (lessons) are homonyms and 
> should be treated as separate entities.
>
> I?m strongly against the proposal to exclude future trademarked gTLDs 
> from these rules. As you mentioned, there?s no legal precedent for 
> such a rule, and it clearly doesn?t favor non-commercial stakeholders. 
> For instance, if a commercial french entity applied for .SOLIDARITE 
> (solidarity) as a brand, a non-commercial organization wanting to use 
> .SOLIDARITES(solidarities) to promote unity and support in communities 
> would be unfairly blocked. Similarly, .LIBERTE (freedom) for a brand 
> could block .LIBERTES(freedoms) for a human rights organization. These 
> examples show how such exclusions could severely disadvantage 
> non-commercial interests.
>
> We should oppose this. Non-commercial entities often don?t have the 
> resources for trademarks or the priority given to them(as we discussed 
> in the recent Trademark Clearinghouse conversation regarding the IDNs 
> EPDP report). The internet should be for everyone.My 2cent.
> Thanks.
>
> Emmanuel Vitus
>
> Le?mer. 22 mai 2024 ??15:00, Kathy Kleiman <Kathy at kathykleiman.com> a 
> ?crit?:
>
>     To NCSG Policy Committee,
>
>     I have been asked to circulate the Singular/Plurals ideas of the
>     SubPro Small Team Plus created by Council to reconcile
>     recommendations of the SubPro Working Group rejected by the ICANN
>     Board,
>     */https://docs.google.com/document/d/19AckdQ_GkPaqCkwcfWdnu8eSKK4YliRjYuP2iVBh4Vs/edit?usp=sharing
>     /*
>
>     The problem is singular and plural gTLDs. In the First Round of
>     New gTLDs, in 2012, singulars and plurals went forward. The idea
>     was that one registry might use .SPRING for domain names about
>     seasons and another might use .SPRINGS for metal coils. A wide use
>     of words has always been NCSG?s position: that there are many
>     meanings for words and we should allow them to flourish in domain
>     names and gTLDs.
>
>     This is what the SubPro Working Group recommended, but the ICANN
>     Board expressed concerns and said no. The Board worries that they
>     will be forced to inquire too deeply into the ?content? of a
>     future gTLD ? how it will be used ? rather than analyzing what the
>     gTLD looks like only. As you know, ICANN cannot regulate ?content?
>     under its new Bylaws.
>
>     The SubPro Small Team Plus returned to the Board and offered to
>     put into the same contention set future plural such as .example
>     and .examples ? these are likely ?confusingly similar? to Internet
>     users and only one should be delegated. And singular/plurals must
>     be in/the same language /(not across languages).
>
>     */Please look at the Board?s current proposal, from the
>     perspective of the languages we speak, and the similarities and
>     differences of singulars and plurals,
>     https://docs.google.com/document/d/19AckdQ_GkPaqCkwcfWdnu8eSKK4YliRjYuP2iVBh4Vs/edit?usp=sharing
>     We will be debating this
>     "compromise proposal" (that comes from ICANN Org) on Tuesday at
>     the next Small Team Plus meeting.
>     /*
>
>     Unfortunately, Jeff Neuman just added? language to remove future
>     trademarked gTLDs (.BRANDS) from these rules completely. I am
>     concerned as that would elevate commercial gTLD uses over
>     noncommercial gTLD uses. I can envision a Liberty Gas Station (a
>     chain in the US) that wants .LIBERTY and a noncommercial group
>     that wants .LIBERTIES to promote rights in their countries and
>     communities, and a few similar ones.? The noncommercial .LIBERTIES
>     is blocked and the commercial .LIBERTY gas station goes forward. I
>     know of no legal precedent for such a rule.
>
>     Please let me know your thoughts ? soon ?as the SubTeam meets
>     again on Tuesday.
>
>     Best regards and tx,
>
>     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: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240522/c12303e3/attachment.htm>

From farell at benin2point0.org  Wed May 22 23:08:37 2024
From: farell at benin2point0.org (farell at benin2point0.org)
Date: Wed, 22 May 2024 22:08:37 +0200
Subject: [NCSG-PC] Fwd: SPIRT Attendance record
In-Reply-To: <CAM8DdeXR99qwObCpwgqtw1oL+M_SDCvSP6+MdxPARXsmRqntAw@mail.gmail.com>
References: <6f71db0799f04d20bc8ce68efbf57e8f@icann.org>
 <CAA5i5mckY9_5-nwSkkjGGgN7djhjuLvMiS5jtRjv52EWoR2dcw@mail.gmail.com>
 <CANsVcEx4Ensb535oXoNXxsgdX-87R==QGRCNp6cFmgur6nrj-Q@mail.gmail.com>
 <CAM8DdeXR99qwObCpwgqtw1oL+M_SDCvSP6+MdxPARXsmRqntAw@mail.gmail.com>
Message-ID: <1716408517661.7.5962@webmail-backend-production-8555699db7-47xnv>

Hi Tomslin and all,

I am sorry for this behaviour and my sinceres apologies to the team.


As you could have already noticed, Monday is not a good time for me for meetings, and it is also the reason why I don't attend NCSG Policy calls.

Meetings of the SPIRT have been put on Mondays after I joined, then it became very difficult for me to attend. And I also missed sending apologies, because I usually expect to join last minutes but it rarely worked. I am involved in IDN WG with more than 85% of attendance in 3 years and having leadership meetings until 1 am my local time but these Monday calls are simply professionally impossible to catch up with (sometimes it is put on Thursdays with IDN regular meetings as well as the leadership meeting; simply too much ICANN for a day)

I would be happy to be replaced with someone who as more time.


Meilleures salutations,



Am 21. Mai 2024 um 03:01:08 +02:00, hat Tomslin Samme-Nlar <mesumbeslin at gmail.com> geschrieben:

> Dear Farell and Bolutife,
> 
> Please read the below concern from the SPIRT leadership regarding attendance.
> 
> Despite the general concern, I note that Bolu's attendance is above average but it appears when you can't make it, no apologies are given. Can I encourage you to please send apologies in advance to staff and leadership when you genuinely can't make the meeting?
> 
> @Farell Folly <farellfolly at gmail.com> Could you please let us know whether your circumstances have changed and if the time and day of the meetings no longer work for you so that we can assess together whether it makes sense for someone else to attend the meetings in your place or not?
> 
> 
> Warmly,
> Tomslin
> 
> 
> 
> ---------- Forwarded message ---------
> From: Anne ICANN via council <<council at icann.org>>
> 
> Date: Tue, 21 May 2024 at 08:33
> Subject: [council] Fwd: Attendance record
> To: Terri Agnew via cou. <<council at gnso.icann.org>>, <<gnso-spirt-dt at icann.org>>
> 
> 
> 
> Dear Councilors,
> 
> I am providing an update on the SPIRT Charter Drafting Team work in my role as Council Liaison. With help from Steve and Saewon, we are making progress but there are concerns regarding attendance. Could you please follow up with your respective stakeholder groups and constituencies to encourage attendance and participation in this drafting process? We need broad participation in order to present the best possible output for Council to review in July.
> 
> As mentioned in chat in our last Council meeting in relation to the Action Decision Radar, there are some possible variations to the Sub Pro Final Report Annex E Implementation Guidance being discussed by this team so it's especially important for everyone who signed up to in fact participate.
> 
> Beyond those members represented on the Council per se, many thanks to Alan Greenberg of the ALAC for acting as Vice Chair and bringing the issue of poor attendance by some to our attention. Thanks as well to Nigel Hickson for his input into the Charter document and his participation in the meetings on behalf of the GAC. Special thanks to Nitin Walia for his able chairing of the meetings!
> 
> Anne
> 
> 
> Anne Aikman-Scalese
> GNSO Councilor
> NomCom Non-Voting 2022-2024
> <anneicanngnso at gmail.com>
> 
> 
> 
> ---------- Forwarded message ---------
> From: Alan Greenberg <<greenberg.alan at gmail.com>>
> 
> Date: Mon, May 20, 2024 at 2:34?PM
> Subject: Re: Attendance record
> To: ICANN Policy Calendar <<PolicyCalendar at icann.org>>
> Cc: <nitin at data.in> <<nitin at data.in>>, <anneicanngnso at gmail.com> <<anneicanngnso at gmail.com>>, Steve Chan <<steve.chan at icann.org>>, Julie Hedlund <<julie.hedlund at icann.org>>, Saewon Lee <<saewon.lee at icann.org>>, Julie Bisland <<julie.bisland at icann.org>>, Devan Reed <<devan.reed at icann.org>>, Terri Agnew <<terri.agnew at icann.org>>
> 
> 
> 
> 
> 
> > 
> > 
> _______________________________________________
> council mailing list -- <council at icann.org>
> To unsubscribe send an email to <council-leave at icann.org>
> 
> 
> _______________________________________________
> By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<https://www.icann.org/privacy/policy>) and the website Terms of Service (<https://www.icann.org/privacy/tos>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
> 

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

From Kathy at KathyKleiman.com  Thu May 23 00:41:46 2024
From: Kathy at KathyKleiman.com (Kathy Kleiman)
Date: Wed, 22 May 2024 17:41:46 -0400
Subject: [NCSG-PC] EFF as alternate subject matter expert - SubPro Small
 Team Plus
Message-ID: <9863d230-7820-4a64-8d4b-c0efb73a207c@KathyKleiman.com>

Hi All,

I would like to request that Cara Gagliano of member EFF (Electronic 
Frontier Foundation) join us in the SubPro Small Team Plus as Alternate 
Subject Matter Expert. She certainly has the credentials, and as 
Emmanuel's response pointed out, there is much work ahead!

Best and tx,

Kathy

------------- Bio of Cara Gagliano ------------------


  Cara Gagliano

Senior Staff Attorney, EFF

Cara focuses on trademark, copyright, and free speech issues as a staff 
attorney on EFF's intellectual property team. She also works on EFF's 
Coders' Rights Project <https://www.eff.org/issues/coders>, assisting 
programmers, developers, and researchers who are helping to build a 
safer future for us all. Cara came to EFF from O'Melveny & Myers LLP, 
where her practice focused on trademark litigation and counseling. As a 
law student, Cara worked on First and Fourth Amendment issues at the 
American Civil Liberties Union?s Speech, Privacy, and Technology 
Project, the New York Civil Liberties Union, and the Foundation for 
Individual Rights in Education, and she was awarded a fellowship in the 
Arthur Garfield Hays Civil Liberties Program at NYU School of Law. Cara 
holds a J.D. from New York University and a B.A. in linguistics from 
Northwestern University.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240522/241d983e/attachment.htm>

From julf at Julf.com  Sun May 26 18:31:10 2024
From: julf at Julf.com (Johan Helsingius)
Date: Sun, 26 May 2024 17:31:10 +0200
Subject: [NCSG-PC] EFF as alternate subject matter expert - SubPro Small
 Team Plus
In-Reply-To: <9863d230-7820-4a64-8d4b-c0efb73a207c@KathyKleiman.com>
References: <9863d230-7820-4a64-8d4b-c0efb73a207c@KathyKleiman.com>
Message-ID: <036cc881-1b36-478d-a896-8586db7de185@Julf.com>

OK with me!

	Julf

On 22/05/2024 23:41, Kathy Kleiman wrote:
> Hi All,
> 
> I would like to request that Cara Gagliano of member EFF (Electronic 
> Frontier Foundation) join us in the SubPro Small Team Plus as Alternate 
> Subject Matter Expert. She certainly has the credentials, and as 
> Emmanuel's response pointed out, there is much work ahead!
> 
> Best and tx,
> 
> Kathy
> 
> ------------- Bio of Cara Gagliano ------------------
> 
> 
>   Cara Gagliano
> 
> Senior Staff Attorney, EFF
> 
> Cara focuses on trademark, copyright, and free speech issues as a staff 
> attorney on EFF's intellectual property team. She also works on EFF's 
> Coders' Rights Project <https://www.eff.org/issues/coders>, assisting 
> programmers, developers, and researchers who are helping to build a 
> safer future for us all. Cara came to EFF from O'Melveny & Myers LLP, 
> where her practice focused on trademark litigation and counseling. As a 
> law student, Cara worked on First and Fourth Amendment issues at the 
> American Civil Liberties Union?s Speech, Privacy, and Technology 
> Project, the New York Civil Liberties Union, and the Foundation for 
> Individual Rights in Education, and she was awarded a fellowship in the 
> Arthur Garfield Hays Civil Liberties Program at NYU School of Law. Cara 
> holds a J.D. from New York University and a B.A. in linguistics from 
> Northwestern University.
> 
> 
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc


From mesumbeslin at gmail.com  Mon May 27 12:52:16 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Mon, 27 May 2024 19:52:16 +1000
Subject: [NCSG-PC] [Call for Volunteers] Appointment of representative and
 alternate to the PPSAI IRT
In-Reply-To: <ee28ed26-ea0c-4aa3-ba5f-46e9aa43bcbf@julf.com>
References: <CB52871E-374F-48BF-97D7-D184C00AD654@contoso.com>
 <ee28ed26-ea0c-4aa3-ba5f-46e9aa43bcbf@julf.com>
Message-ID: <CAM8DdeUFVZ18WfoH28uMpys9dO20V=mZuTXqERZ2BYRqDerYEw@mail.gmail.com>

Dear members,

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

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

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

Warmly,
Tomslin




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



Dear All,

Following the publication of the Call for Volunteers
<
https://www.icann.org/en/announcements/details/icann-seeks-volunteers-for-the-ppsai-implementation-review-team-20-05-2024-en>,

the Internet Corporation for Assigned Names and Numbers (ICANN)
organization (org) is pleased to invite you to nominate a representative
and an alternate to the Proxy & Privacy Services (PPSAI) policy
Implementation Review Team (IRT).

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

The goal is to provide a structure that allows for efficient resolution
of issues that may occur.

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

Putting forward a representative and alternate is optional; all members
of the GNSO Group are welcome to join the IRT as participants. In fact,
we urge anyone who is interested in being selected as a representative
to join the IRT as a participant first (call for volunteers
<
https://www.icann.org/en/announcements/details/icann-seeks-volunteers-for-the-ppsai-implementation-review-team-20-05-2024-en>).

As you will see below, the roles of participants and representatives are
nearly identical, with the representatives? main function being that of
an information-bridge to their community groups.

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

Why Have Representatives?

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

In addition, when determining the level of consensus in the circumstance
described in Section V.E. of the IRT Principles & Guidelines
<
https://www.icann.org/en/system/files/files/irt-principles-guidelines-23aug16-en.pdf>,

the GNSO Liaison, in the Open + Representative model, shall take into
consideration that members who are representatives are expected to
express the viewpoint of their respective community groups and
participants to express their own views. This does not impact each
member?s ability to raise any concern they may have, nor does it absolve
ICANN org or the GNSO Council liaison from ?exercis[ing] all reasonable
efforts to resolve disagreements? within the IRT.

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

-- 

Kind Regards,

Dennis S. Chang

GDD Programs Director

Phone: +1 213 293 7889

Sykpe: dennisSchang

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

_______________________________________________
NCSG-PC mailing list
NCSG-PC at lists.ncsg.is
https://lists.ncsg.is/mailman/listinfo/ncsg-pc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240527/bef61e6c/attachment.htm>

From emmanuelvitus at gmail.com  Mon May 27 19:24:09 2024
From: emmanuelvitus at gmail.com (Emmanuel Vitus)
Date: Mon, 27 May 2024 16:24:09 +0000
Subject: [NCSG-PC] EFF as alternate subject matter expert - SubPro Small
 Team Plus
In-Reply-To: <9863d230-7820-4a64-8d4b-c0efb73a207c@KathyKleiman.com>
References: <9863d230-7820-4a64-8d4b-c0efb73a207c@KathyKleiman.com>
Message-ID: <CAGKde+3HaAP_u9EoOUYq0UyhG8qV7wVsM+73PkVZEu5rrQCYJw@mail.gmail.com>

Hello.
I?m ok with this.
We definitely need subject matter experts on these issues.
 Best,

Emmanuel


Sent from iPhone. Excuse brevity and typos.


On Wed 22 May 2024 at 21:41, Kathy Kleiman <Kathy at kathykleiman.com> wrote:

> Hi All,
>
> I would like to request that Cara Gagliano of member EFF (Electronic
> Frontier Foundation) join us in the SubPro Small Team Plus as Alternate
> Subject Matter Expert. She certainly has the credentials, and as Emmanuel's
> response pointed out, there is much work ahead!
>
> Best and tx,
>
> Kathy
>
> ------------- Bio of Cara Gagliano ------------------
> Cara Gagliano
> Senior Staff Attorney, EFF
>
> Cara focuses on trademark, copyright, and free speech issues as a staff
> attorney on EFF's intellectual property team. She also works on EFF's Coders'
> Rights Project <https://www.eff.org/issues/coders>, assisting
> programmers, developers, and researchers who are helping to build a safer
> future for us all. Cara came to EFF from O'Melveny & Myers LLP, where her
> practice focused on trademark litigation and counseling. As a law student,
> Cara worked on First and Fourth Amendment issues at the American Civil
> Liberties Union?s Speech, Privacy, and Technology Project, the New York
> Civil Liberties Union, and the Foundation for Individual Rights in
> Education, and she was awarded a fellowship in the Arthur Garfield Hays
> Civil Liberties Program at NYU School of Law. Cara holds a J.D. from New
> York University and a B.A. in linguistics from Northwestern University.
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240527/362a3c82/attachment.htm>

From mesumbeslin at gmail.com  Tue May 28 02:55:39 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Tue, 28 May 2024 09:55:39 +1000
Subject: [NCSG-PC] EFF as alternate subject matter expert - SubPro Small
 Team Plus
In-Reply-To: <CAGKde+3HaAP_u9EoOUYq0UyhG8qV7wVsM+73PkVZEu5rrQCYJw@mail.gmail.com>
References: <9863d230-7820-4a64-8d4b-c0efb73a207c@KathyKleiman.com>
 <CAGKde+3HaAP_u9EoOUYq0UyhG8qV7wVsM+73PkVZEu5rrQCYJw@mail.gmail.com>
Message-ID: <CAM8DdeUNE0km3JkFf-DN26+PSos54SriYTRzOwkF+L4QUYFsxg@mail.gmail.com>

Hi all,

Seeing no objection, I am submitting Cara's name as an alternative
immediately.

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


On Tue, 28 May 2024 at 02:24, Emmanuel Vitus <emmanuelvitus at gmail.com>
wrote:

> Hello.
> I?m ok with this.
> We definitely need subject matter experts on these issues.
>  Best,
>
> Emmanuel
>
>
> Sent from iPhone. Excuse brevity and typos.
>
>
> On Wed 22 May 2024 at 21:41, Kathy Kleiman <Kathy at kathykleiman.com> wrote:
>
>> Hi All,
>>
>> I would like to request that Cara Gagliano of member EFF (Electronic
>> Frontier Foundation) join us in the SubPro Small Team Plus as Alternate
>> Subject Matter Expert. She certainly has the credentials, and as Emmanuel's
>> response pointed out, there is much work ahead!
>>
>> Best and tx,
>>
>> Kathy
>>
>> ------------- Bio of Cara Gagliano ------------------
>> Cara Gagliano
>> Senior Staff Attorney, EFF
>>
>> Cara focuses on trademark, copyright, and free speech issues as a staff
>> attorney on EFF's intellectual property team. She also works on EFF's Coders'
>> Rights Project <https://www.eff.org/issues/coders>, assisting
>> programmers, developers, and researchers who are helping to build a safer
>> future for us all. Cara came to EFF from O'Melveny & Myers LLP, where her
>> practice focused on trademark litigation and counseling. As a law student,
>> Cara worked on First and Fourth Amendment issues at the American Civil
>> Liberties Union?s Speech, Privacy, and Technology Project, the New York
>> Civil Liberties Union, and the Foundation for Individual Rights in
>> Education, and she was awarded a fellowship in the Arthur Garfield Hays
>> Civil Liberties Program at NYU School of Law. Cara holds a J.D. from New
>> York University and a B.A. in linguistics from Northwestern University.
>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240528/ba6cd656/attachment.htm>

From kathy at kathykleiman.com  Tue May 28 18:25:45 2024
From: kathy at kathykleiman.com (Kathy Kleiman)
Date: Tue, 28 May 2024 11:25:45 -0400
Subject: [NCSG-PC] Singulars/Plurals in New gTLDs and future rounds
In-Reply-To: <67f99a62-23db-4d5d-a138-3b00de078041@KathyKleiman.com>
References: <c2a3ea36-4b3d-4aa9-98c2-e51d7384a279@KathyKleiman.com>
 <CAGKde+1cGeH3L6BpB4Rx8A2ZfX9LwQfAG9gRKFDFz1wzO6jhiw@mail.gmail.com>
 <67f99a62-23db-4d5d-a138-3b00de078041@KathyKleiman.com>
Message-ID: <50f5e706-1a91-4042-b6ce-ee773ac23e15@kathykleiman.com>

Hi All,

Tx you for appointing Cara Gagliano from the Electronic Frontier 
Foundation. She and I were both able to speak in today's meeting.

Following up on our discussion below, we raised many concerns about the 
"collapse" of future applications for singular and plural gTLDs into a 
single content set, and the harm that will take place to noncommercial 
speech.? .SPRING (for seasons) and .SPRINGS for elastic objects, 
according to the SubPro Working Group, should be allowed to co-exist.? 
Yet, under these proposed rules, as we discussed earlier, they will go 
into "contention sets" with the deepest commercial pockets winning the 
auctions, and much noncommercial speech will be lost.

As Cara said, this proposed rule for throwing all singular and plural 
new gTLD strings into one contention set is both overly inclusive and 
overbroad - and we never want that result when it comes to Free 
Expression.?? She's right!

/*It's a busy season, but how about a short session to discuss this 
matter with our community - does Friday work (same time as today's 
candidates' session)? *(Our next SubPro Small Team Plus meeting is next 
Monday,? 6/3)./

Best, Kathy


> On 5/22/2024 2:03 PM, Emmanuel Vitus wrote:
>>
>> Hi Kathy,
>> Thanks for sharing this.
>> I still don?t get why the Board worries that allowing singular and 
>> plural forms of gTLDs will make them delve too much into ?content.? 
>> Were there any practical examples of arguments given to support this 
>> concern?
>> I completely agree that delegations must be in the same language to 
>> avoid confusion. For example, in Spanish, ?casa? (house) and ?casas? 
>> (houses) shouldn?t both be delegated as gTLDs since they are simply 
>> singular and plural forms of the same word. However, I agree that if 
>> they are just homonyms, they should be allowed to be delegated. For 
>> instance, in English, ?bank? (financial institution) and ?bank? (side 
>> of a river) are homonyms and could be delegated as they represent 
>> different meanings, but on a first?come first serve basis. Similarly, 
>> in French, ?cour? (court) and ?cours? (lessons) are homonyms and 
>> should be treated as separate entities.
>>
>> I?m strongly against the proposal to exclude future trademarked gTLDs 
>> from these rules. As you mentioned, there?s no legal precedent for 
>> such a rule, and it clearly doesn?t favor non-commercial 
>> stakeholders. For instance, if a commercial french entity applied for 
>> .SOLIDARITE (solidarity) as a brand, a non-commercial organization 
>> wanting to use .SOLIDARITES(solidarities) to promote unity and 
>> support in communities would be unfairly blocked. Similarly, .LIBERTE 
>> (freedom) for a brand could block .LIBERTES(freedoms) for a human 
>> rights organization. These examples show how such exclusions could 
>> severely disadvantage non-commercial interests.
>>
>> We should oppose this. Non-commercial entities often don?t have the 
>> resources for trademarks or the priority given to them(as we 
>> discussed in the recent Trademark Clearinghouse conversation 
>> regarding the IDNs EPDP report). The internet should be for 
>> everyone.My 2cent.
>> Thanks.
>>
>> Emmanuel Vitus
>>
>> Le?mer. 22 mai 2024 ??15:00, Kathy Kleiman <Kathy at kathykleiman.com> a 
>> ?crit?:
>>
>>     To NCSG Policy Committee,
>>
>>     I have been asked to circulate the Singular/Plurals ideas of the
>>     SubPro Small Team Plus created by Council to reconcile
>>     recommendations of the SubPro Working Group rejected by the ICANN
>>     Board,
>>     */https://docs.google.com/document/d/19AckdQ_GkPaqCkwcfWdnu8eSKK4YliRjYuP2iVBh4Vs/edit?usp=sharing
>>     /*
>>
>>     The problem is singular and plural gTLDs. In the First Round of
>>     New gTLDs, in 2012, singulars and plurals went forward. The idea
>>     was that one registry might use .SPRING for domain names about
>>     seasons and another might use .SPRINGS for metal coils. A wide
>>     use of words has always been NCSG?s position: that there are many
>>     meanings for words and we should allow them to flourish in domain
>>     names and gTLDs.
>>
>>     This is what the SubPro Working Group recommended, but the ICANN
>>     Board expressed concerns and said no. The Board worries that they
>>     will be forced to inquire too deeply into the ?content? of a
>>     future gTLD ? how it will be used ? rather than analyzing what
>>     the gTLD looks like only. As you know, ICANN cannot regulate
>>     ?content? under its new Bylaws.
>>
>>     The SubPro Small Team Plus returned to the Board and offered to
>>     put into the same contention set future plural such as .example
>>     and .examples ? these are likely ?confusingly similar? to
>>     Internet users and only one should be delegated. And
>>     singular/plurals must be in/the same language /(not across
>>     languages).
>>
>>     */Please look at the Board?s current proposal, from the
>>     perspective of the languages we speak, and the similarities and
>>     differences of singulars and plurals,
>>     https://docs.google.com/document/d/19AckdQ_GkPaqCkwcfWdnu8eSKK4YliRjYuP2iVBh4Vs/edit?usp=sharing
>>     We will be debating this
>>     "compromise proposal" (that comes from ICANN Org) on Tuesday at
>>     the next Small Team Plus meeting.
>>     /*
>>
>>     Unfortunately, Jeff Neuman just added? language to remove future
>>     trademarked gTLDs (.BRANDS) from these rules completely. I am
>>     concerned as that would elevate commercial gTLD uses over
>>     noncommercial gTLD uses. I can envision a Liberty Gas Station (a
>>     chain in the US) that wants .LIBERTY and a noncommercial group
>>     that wants .LIBERTIES to promote rights in their countries and
>>     communities, and a few similar ones.? The noncommercial
>>     .LIBERTIES is blocked and the commercial .LIBERTY gas station
>>     goes forward. I know of no legal precedent for such a rule.
>>
>>     Please let me know your thoughts ? soon ?as the SubTeam meets
>>     again on Tuesday.
>>
>>     Best regards and tx,
>>
>>     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: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240528/6ffacee7/attachment.htm>

From stephanie.perrin at mail.utoronto.ca  Thu May 30 16:10:37 2024
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Thu, 30 May 2024 13:10:37 +0000
Subject: [NCSG-PC] Aspirational Statements
Message-ID: <6084E33A-20C2-4E63-800B-21BE74D7B745@mail.utoronto.ca>

Dear NCSG members

For some time, there has been a process going on at the GNSO Council to craft an ?aspirational statement? that would encourage members not to vote against the work of Working groups.  This is in keeping with our ongoing work on continuous improvement, and in my opinion may have sprung from recent surprises when work was tossed out by votes in council.  Obviously, we all hate work being thrown out with the bathwater at the last minute, but I have rather consistently spoken against such a statement because I feel we are already constrained by commitments to act in good faith.
Given the rise in small teams to deliver work product to Council, I am also very worried that this ?aspirational statement? will be applied to situations where we have been under-represented in the "Working Groups?.  May I add that capitalising a term is very out of fashion in scholarly publication style, and does nothing to clarify its meaning.  

The GNSO Council is the formal body that votes on the results of the PDPs.  I do not believe we should attempt to constrain its ability to vote something down.  I would remind you that the holistic review is coming, and we will need to brush up on all the work that has been done on structural improvements.  I see this as a backward step, weakening the overall policy role of the GNSO.  I would welcome a discussion on this list to see what the members think.  It is up for voting at the next council meeting.

Aspirational Statement
The members of GNSO Council strive to be effective managers of the GNSO Policy
Development Process (?PDP?). As managers of the PDP, the GNSO Council charters Working
Groups in a way that accounts for both relevant expertise and stakeholder diversity within
Working Group membership, then oversees the PDPs? work throughout the PDP lifecycle. The
GNSO Council recognizes that many deliberations occur within the Working Group during a
PDP, and these deliberations lead to the consensus required for final policy recommendations.
While individual GNSO Councilors and the groups they represent may not fully agree with the
final policy recommendation text, GNSO Councilors strive to support recommendations that
follow the PDP?s consensus-building processes because doing so supports the broader
multistakeholder model. In recognition of the multistakeholder model, when a Working Group
delivers a Final Report with consensus recommendations to the GNSO Council, the GNSO
Council will always try to vote in favor of the policy recommendations absent truly exceptional
circumstances.


Stephanie Perrin
GNSO Councillor

From julf at julf.com  Fri May 31 11:03:39 2024
From: julf at julf.com (Johan Helsingius)
Date: Fri, 31 May 2024 10:03:39 +0200
Subject: [NCSG-PC] Fwd: Call for Expressions of Interest: GNSO Liaison to
 the Governmental Advisory Committee (GAC)
In-Reply-To: <F26549E1-AFF6-4F2F-B5C2-9A88A13C9FA1@icann.org>
References: <F26549E1-AFF6-4F2F-B5C2-9A88A13C9FA1@icann.org>
Message-ID: <916c169e-07fd-44be-8889-00e2d887a8be@julf.com>




-------- Forwarded Message --------
Subject: 	[GNSO-SG-C-Leadership] Call for Expressions of Interest: GNSO 
Liaison to the Governmental Advisory Committee (GAC)
Date: 	Thu, 30 May 2024 17:40:37 +0000
From: 	Terri Agnew via GNSO-SG-C-Leadership <gnso-sg-c-leadership at icann.org>
Reply-To: 	Terri Agnew <terri.agnew at icann.org>
To: 	gnso-sg-c-leadership at icann.org <gnso-sg-c-leadership at icann.org>
CC: 	gnso-secs at icann.org <gnso-secs at icann.org>, gnso-chairs at icann.org 
<gnso-chairs at icann.org>



Dear GNSO Stakeholder Group and Constituency (SG/C) Leaders,

Please see the attached Call for Expressions of Interest for the GNSO 
Liaison to the Governmental Advisory Committee (GAC)

The leadership of each Stakeholder Group / Constituency has the 
opportunity to submit the application of one or more candidate(s) it 
supports for the role, but it is not required to submit any applications.

Consistent with the original recommendation of the GAC-GNSO Consultation 
Group and previous practice, applications will not be accepted from 
individuals for this process. If an individual attempts to submit an 
application, they will be requested to contact the leadership of their SG/C.

The deadline for submitting applications via the attached application 
template is on *_08 July 2024_ *to allow for the intervening ICANN80 
meeting and accommodate SG/Cs who may need additional time to consider 
candidates before the deadline.? Candidates should submit applications 
to the GNSO Secretariat at:gnso-secs at icann.org <mailto:gnso-secs at icann.org>.

Please note that GNSO Liaison to the GAC officially takes up its role at 
the*ICANN Annual General Meeting (AGM)*(by*_14 November 2024_*).

Thank you for your consideration.

Kind regards,

GNSO Secretariat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Expression of Interest-GNSO Council GAC liaison 28 May 2024[2].docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 22949 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240531/c61ed1a5/attachment.docx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Application Template-GNSO Council GAC liaison 28 May 2024[2].docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 20520 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240531/c61ed1a5/attachment-0001.docx>
-------------- next part --------------
_______________________________________________
GNSO-SG-C-Leadership mailing list -- gnso-sg-c-leadership at icann.org
To unsubscribe send an email to gnso-sg-c-leadership-leave at icann.org

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

From mesumbeslin at gmail.com  Fri May 31 12:38:37 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Fri, 31 May 2024 19:38:37 +1000
Subject: [NCSG-PC] Fwd: SPIRT Attendance record
In-Reply-To: <1716408517661.7.5962@webmail-backend-production-8555699db7-47xnv>
References: <6f71db0799f04d20bc8ce68efbf57e8f@icann.org>
 <CAA5i5mckY9_5-nwSkkjGGgN7djhjuLvMiS5jtRjv52EWoR2dcw@mail.gmail.com>
 <CANsVcEx4Ensb535oXoNXxsgdX-87R==QGRCNp6cFmgur6nrj-Q@mail.gmail.com>
 <CAM8DdeXR99qwObCpwgqtw1oL+M_SDCvSP6+MdxPARXsmRqntAw@mail.gmail.com>
 <1716408517661.7.5962@webmail-backend-production-8555699db7-47xnv>
Message-ID: <CAM8DdeW38=10+HBFWTfd2-v_DRsFTjebpKct-jWTw1otMEVcpw@mail.gmail.com>

Hi Farell,

Thank you so much for your reply and clarification. We will try to get
someone who can attend the Monday calls.

Thank you again for the time you have given to the SPIRT group so far.

Warmly,
Tomslin

On Thu, 23 May 2024, 06:08 , <farell at benin2point0.org> wrote:

> Hi Tomslin and all,
>
> I am sorry for this behaviour and my sinceres apologies to the team.
>
>
> As you could have already noticed, Monday is not a good time for me for
> meetings, and it is also the reason why I don't attend NCSG Policy calls.
>
> Meetings of the SPIRT have been put on Mondays after I joined, then it
> became very difficult for me to attend. And I also missed sending
> apologies, because I usually expect to join last minutes but it rarely
> worked. I am involved in IDN WG with more than 85% of attendance in 3 years
> and having leadership meetings until 1 am my local time but these Monday
> calls are simply professionally impossible to catch up with (sometimes it
> is put on Thursdays with IDN regular meetings as well as the leadership
> meeting; simply too much ICANN for a day)
>
> I would be happy to be replaced with someone who as more time.
>
> Meilleures salutations,
>
>
>
> Am 21. Mai 2024 um 03:01:08 +02:00, hat Tomslin Samme-Nlar <
> mesumbeslin at gmail.com> geschrieben:
>
> Dear Farell and Bolutife,
>
> Please read the below concern from the SPIRT leadership regarding
> attendance.
>
> Despite the general concern, I note that Bolu's attendance is above
> average but it appears when you can't make it, no apologies are given. Can
> I encourage you to please send apologies in advance to staff and leadership
> when you genuinely can't make the meeting?
>
> @Farell Folly <farellfolly at gmail.com>  Could you please let us know
> whether your circumstances have changed and if the time and day of the
> meetings no longer work for you so that we can assess together whether it
> makes sense for someone else to attend the meetings in your place or not?
>
> Warmly,
> Tomslin
>
>
> ---------- Forwarded message ---------
> From: *Anne ICANN via council* <council at icann.org>
> Date: Tue, 21 May 2024 at 08:33
> Subject: [council] Fwd: Attendance record
> To: Terri Agnew via cou. <council at gnso.icann.org>, <
> gnso-spirt-dt at icann.org>
>
>
> Dear Councilors,
>
> I am providing an update on the SPIRT Charter Drafting Team work in my
> role as Council Liaison.  With help from Steve and Saewon, we are making
> progress but there are concerns regarding attendance.  Could you please
> follow up with your respective stakeholder groups and constituencies to
> encourage attendance and participation in this drafting process?  We need
> broad participation in order to present the best possible output for
> Council to review in July.
>
> As mentioned in chat in our last Council meeting in relation to the Action
> Decision Radar, there are some possible variations to the Sub Pro Final
> Report Annex E Implementation Guidance being discussed by this team so it's
> especially important for everyone who signed up to in fact participate.
>
> Beyond those members represented on the Council per se, many thanks to
> Alan Greenberg of the ALAC for acting as Vice Chair and bringing the issue
> of poor attendance by some to our attention.   Thanks as well to Nigel
> Hickson for his input into the Charter document and his participation in
> the meetings on behalf of the GAC.  Special thanks to Nitin Walia for his
> able chairing of the meetings!
>
> Anne
>
> Anne Aikman-Scalese
> GNSO Councilor
> NomCom Non-Voting 2022-2024
> anneicanngnso at gmail.com
>
>
> ---------- Forwarded message ---------
> From: *Alan Greenberg* <greenberg.alan at gmail.com>
> Date: Mon, May 20, 2024 at 2:34?PM
> Subject: Re: Attendance record
> To: ICANN Policy Calendar <PolicyCalendar at icann.org>
> Cc: nitin at data.in <nitin at data.in>, anneicanngnso at gmail.com <
> anneicanngnso at gmail.com>, Steve Chan <steve.chan at icann.org>, Julie
> Hedlund <julie.hedlund at icann.org>, Saewon Lee <saewon.lee at icann.org>,
> Julie Bisland <julie.bisland at icann.org>, Devan Reed <devan.reed at icann.org>,
> Terri Agnew <terri.agnew at icann.org>
>
>
>
>
> _______________________________________________
> council mailing list -- council at icann.org
> To unsubscribe send an email to council-leave at icann.org
>
> _______________________________________________
> By submitting your personal data, you consent to the processing of your
> personal data for purposes of subscribing to this mailing list accordance
> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). You can
> visit the Mailman link above to change your membership status or
> configuration, including unsubscribing, setting digest-style delivery or
> disabling delivery altogether (e.g., for a vacation), and so on.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240531/923907ae/attachment.htm>

From julf at julf.com  Fri May 31 20:56:44 2024
From: julf at julf.com (Johan Helsingius)
Date: Fri, 31 May 2024 19:56:44 +0200
Subject: [NCSG-PC] Fwd: NomCom changes
In-Reply-To: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
References: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
Message-ID: <aa680b0b-ee62-4297-a704-da8f03cb43ba@julf.com>




-------- Forwarded Message --------
Subject: 	NomCom changes
Date: 	Fri, 31 May 2024 14:41:19 +0000
From: 	DiBiase, Gregory <dibiase at amazon.com>
To: 	aheineman at godaddy.com <aheineman at godaddy.com>, Lori Schulman 
<lschulman at inta.org>, Cole, Mason (POR) <MCole at perkinscoie.com>, Johan 
Helsingius <julf at Julf.com>, sdemetriou at verisign.com 
<sdemetriou at verisign.com>, philippe.fouquart at orange.com 
<philippe.fouquart at orange.com>
CC: 	Steve Chan <steve.chan at icann.org>, gnso-secs at icann.org 
<gnso-secs at icann.org>



Dear Ashley, Julf, Lori, Mason, Philippe, and Samantha,

I am writing to you all in your roles as Chairs of Stakeholder Groups or 
Constituencies that appoint delegates to ICANN?s Nominating Committee 
(NomCom).

You may recall that the NomCom2 Review produced 27 recommendations, 
several of which relate to the composition and terms of the NomCom. In 
order to effectuate these particular recommendations, the ICANN Board 
approved Standard Bylaws Amendments in Articles 8, 12, and 27.

The Bylaws amendments made no change to the number and nature of 
delegates from the GNSO (i.e., 1 each from the RySG, RrSG, ISPCP, IPC, 
NCSG, and 2 from the BC), though the length of terms were extended to 
two years (see Section 8.3 of the Bylaws). However, from Article 27, in 
order to, ?effectuate the introduction of the two-year terms and support 
the goal of staggering delegate terms??, three of the GNSO delegates 
shall serve a one-year term. ARTICLE 27 TRANSITION ARTICLE states that 
the GNSO is responsible for determining which three of the seven 
delegates shall initially serve one-year terms.

Unfortunately, no guidance was provided on how to identify the three of 
seven GNSO delegates to serve one-year terms. For reference, the ALAC 
was also in the position of having to identify a subset of delegates to 
serve one-year terms. They elected to rely on random selection during a 
live call.

The GNSO may want to rely on a similarly simple approach. An important 
point in considering the approach is that the level of representation on 
the NomCom is not affected by the term-length. However, the SG/Cs with 
one-year terms will have to replace those delegates after one year 
rather than two.

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

If you believe that there may be concerns (e.g., we may want to avoid 
having the one-year terms concentrated in particular areas), please 
share them with Council leadership no later than 31 May 2024.

If however there are no concerns, Council leadership can perform the 
random selection process with staff or if you prefer, on a Zoom call 
with all of you.

Thanks,

Greg DiBiase, GNSO Chair