Thanks Jared. was the 2012 AGB language on letters from "quasi-official" organizations reaffirmed in the Sub Pro policy work? Could you please point us to the trail on the history on that language? Many thanks! Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com On Fri, Aug 22, 2025 at 8:45 AM Jared Erwin <jared.erwin@icann.org> wrote:
Dear IRT Members,
As noted, in addition to the other changes we have made the past few days which were discussed on our calls on 14 August <https://icann-community.atlassian.net/wiki/spaces/SPIR/pages/328106025/2025-...>, 20 August <https://icann-community.atlassian.net/wiki/spaces/SPIR/pages/399704065/2025-...>, and 21 August <https://icann-community.atlassian.net/wiki/spaces/SPIR/pages/328171521/2025-...>, we have made some updates based on our call yesterday. These are described below and in the language here <https://docs.google.com/document/d/1rH19XrXglbfYj-TyioFsj4siNECKeR5J7Gfdvk3_...> .
1. Added the words “and verify” to relevant guidelines: “The panel may review AND VERIFY letters of support or opposition…” We also added a footnote to reference the support/opposition verification guidelines that live under Criterion 4. These changes have been made on all guidelines for all relevant criteria. 1. See first example on page 26 (+ footnote 26) but note that they appear throughout the document. 2. Added footnote 31 on page 29 regarding “double counting.” 1. Note that we also warn of not double counting more generally in section 4.4.6. 3. Made updates to clarify language in scoring table 4-9 on page 35. 1. Note that this was done solely to align with the language above the table at the start of Section 4.7.4.4. 4. Made changes to bullet “e” on page 36 to change “reputable” to “relevant” and provide additional examples of what this means in parentheses. 1. I note Anne’s comment below. I understood that we wanted to keep quasi-official but add official and established. *Or was the IRT suggesting to remove “quasi-official”?* As a reminder, this is language from the 2012 AGB and it will be the panel’s job to verify any letters of support or opposition and review whether any seem “spurious” or “unsubstantiated.”
*I would kindly request IRT members to review and provide their final input by Wednesday, 27 August 2025* so that we can finalize the language.
Thank you,
Jared
*From: *Anne ICANN <anneicanngnso@gmail.com> *Date: *Thursday, August 21, 2025 at 17:07 *To: *Justine Chew <justine.chew.icann@gmail.com> *Cc: *Jared Erwin <jared.erwin@icann.org>, Next Round Policy Implementation via SubPro-IRT <subpro-irt@icann.org> *Subject: *[Ext] Re: [SubPro-IRT] Re: Deck Meeting #154
Thanks Justine. I hope that you and others will review the language about "quasi-official organizations" and others weighing in on the Nexus between the community and the string applied for. Folks seem concerned about community applicants doing the gaming, but the potential for gaming is higher here because the competitor who has applied for the same string and is not a community applicant need only hire a smart lawyer to form a new "quasi-official" organization to file a letter opposing the nexus and the application. There will apparently be no requirement to disclose what money and what party is actually behind such a "quasi-official" organization. This language opens the door to the worst sort of gaming (by the non-community competitor) and we need to avoid it.
Wish we could all keep in mind that for legitimate objectors, we have the Community Objection. I don't think anyone on the IRT should be trying to save an Objector from having to file. It's the remedy that Sub Pro affirmed.
Anne
Anne Aikman-Scalese
GNSO Councilor
NomCom Non-Voting 2022-2026
anneicanngnso@gmail.com
On Thu, Aug 21, 2025 at 9:51 AM Justine Chew via SubPro-IRT < subpro-irt@icann.org> wrote:
Dear Jared,
Thanks for this but I'm afraid I can't make the call later and hence request for time over the weekend to provide comments to the language changes you speak of and any further changes arising from today's call.
Kind regards, Justine ---------
On Fri, 22 Aug 2025, 00:01 Jared Erwin via SubPro-IRT, < subpro-irt@icann.org> wrote:
Dear IRT members,
Also wanted to note that we have made changes to the CPE language based on our discussion yesterday. We can review those changes today.
- See here: https://docs.google.com/document/d/1rH19XrXglbfYj-TyioFsj4siNECKeR5J7Gfdvk3_... [docs.google.com] <https://urldefense.com/v3/__https:/docs.google.com/document/d/1rH19XrXglbfYj...>
Thank you
Jared
*From: *Elisa Busetto via SubPro-IRT <subpro-irt@icann.org> *Reply-To: *Elisa Busetto <elisa.busetto@icann.org> *Date: *Thursday, August 21, 2025 at 08:32 *To: *"subpro-irt@icann.org" <subpro-irt@icann.org> *Subject: *[SubPro-IRT] Deck Meeting #154
Hello IRT members,
Just a quick note to let you know that we have published the deck for the call today: https://icann-community.atlassian.net/wiki/x/AYCPEw [icann-community.atlassian.net] <https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/AYCP...>
Best,
Elisa
_______________________________________________ SubPro-IRT mailing list -- subpro-irt@icann.org To unsubscribe send an email to subpro-irt-leave@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.
_______________________________________________ SubPro-IRT mailing list -- subpro-irt@icann.org To unsubscribe send an email to subpro-irt-leave@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.