Hi Paul - just a reminder that ICANN Staff asked for Council direction on the Options. Not everyone on the IRT agreed with Option 1. Staff supports Option 2 and there are some on the IRT who agree. There was also a proposal for a third option which came out of the IRT so please don't make this sound as though the topic is simple and that Council is somehow pushing to intervene. The Extraordinary Meeting is a Council Action Item from our September meeting. It provides an opportunity for a full discussion of a fairly complex issue. Susan and I agree, as Co-Liaisons, that the question before the Council is - which Option properly reflects the intent of the policy Recommendations? (Everyone seems to agree that the third option involves a policy change so we are not bringing that before Council.) Susan and I have heard directly from GNSO staff that clear direction from Council to ICANN Org will be helpful. With staff's help, we are finalizing a Motion to be distributed on Monday with appropriate background which will enable Councilors to fully brief their Cs and SGs. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com On Sat, Sep 27, 2025 at 11:15 AM Paul McGrady <paul@elstermcgrady.com> wrote:
Thanks Anne.
All, I hope we don’t take a full hour discussing the Reserved Names issue. It is pretty straightforward. We have a disagreement between the Staff whose job it is to implement policy and members of the IRT whose job it is to advise Staff. Staff doesn’t believe that implementing Option 2 requires any new policy. Certain members of the IRT disagree. What is being asked of Council is whether or not, in what appears to be both a close call on whether or not Staff would be making policy and such policy would only affect applicants in the most outlier of all cases (i.e. applicants unwisely applying for similar things to the Reserved Names), Council wants to take the extraordinary step of interfering in the relationship between the Staff (implementors) and the Board (adopters of policy and supervisor of Staff). For me, that is an easy “no.” If this were a clear-cut case of Staff being wrong or Staff hemming and hawing, that would be a different matter and I would be the first one passing out the picket signs. 😊 I hope we can dispatch this topic quickly in the extraordinary (well named!) meeting and also have time to consider the items Steve raises since it is a topic that was front and center in our Special Session in DC and it would be wonderful to wrap up that work this term ends.
Best,
Paul
*From:* Anne ICANN via council <council@icann.org> *Sent:* Saturday, September 27, 2025 8:53 AM *To:* Steve Chan <steve.chan@icann.org> *Cc:* council@icann.org *Subject:* [council] Re: Draft Proposal: Board Reversal of its Adoption of a GNSO PDP Recommendation
Thanks Steve. I don't think we can add this item to the agenda for the special meeting on October 9. We should not cut short the time to discuss the topic of Reserved Names and associated String Similarity implementation issues. Councilors will have plenty of work to brief Cs and SGs for that special meeting when the draft Motion is published on Monday the 29th (10 days before the special meeting).
I have not had a chance to review these Board reversal redlines to our Operating Procedures and PDP and EPDP manuals, but wanted to ask whether we can add this to the agenda for our working session in Dublin? Hopefully that working session takes place prior to our meeting with the Board.
Thank you,
Anne
Anne Aikman-Scalese
GNSO Councilor
NomCom Non-Voting 2022-2026
anneicanngnso@gmail.com
On Fri, Sep 19, 2025 at 2:37 PM Steve Chan via council <council@icann.org> wrote:
Dear Councilors,
I have an update on the development of the draft redlines for the ICANN Board’s non-adoption of previously adopted GNSO policy recommendations. Having neither seen nor heard any objections, staff has developed proposed redlines to the relevant procedural manuals.
- PDP Manual: A new section 16 has been added (and FYI, there was a numbering issue where 13 was repeated) - https://docs.google.com/document/d/1WxnQEsswTbeLuT-D_iZzD8N9BXGIgiGkYiaADsxH... - EPDP Manual: No edits appear necessary as the relevant sections for the EPDP rely upon the PDP Manual. - GGP Manual: Here, a new section 10 has been added, which is very, very similar to the proposed edits to the PDP Manual - https://docs.google.com/document/d/159UvOrKfigdEvWCB9f4cmHNo8cVVlOMCE2LTTREX...
Staff would like to propose that Councilors review these redlines with their respective groups and provide comments or concerns on Council list. In the likely event that a special meeting will need to be scheduled for the SubPro Reserved Names issue, perhaps this topic can be added for a brief discussion as well; the scheduling of that meeting can help dictate the deadline for feedback on the updated manuals. These next steps are proposed with an eye towards putting the Council in a position where it’s able to discuss the proposed redlines with the Board at ICANN84.
Best,
Steve
*From: *Steve Chan via council <council@icann.org> *Reply-To: *Steve Chan <steve.chan@icann.org> *Date: *Tuesday, August 19, 2025 at 3:52 PM *To: *"council@icann.org" <council@icann.org> *Subject: *[council] Draft Proposal: Board Reversal of its Adoption of a GNSO PDP Recommendation
Dear Councilors,
You will likely recall that during the Council’s last Strategic Planning Session (SPS), the Council came to general agreement on the approach for the ICANN Board to reverse its adoption of a GNSO recommendation. The action item from the SPS was to identify the proper place to document that generally agreed upon process. Your GNSO support staff has coordinated with ICANN legal to determine the most appropriate location to capture the process and in short, the recommendation is to update the EPDP, PDP, and GGP Manuals.
In the attached document, you will see a briefing document that contains about 2.5 pages of text that explains the thought process and rationale for the approach; if you’re able to recall the conversation at the SPS, this text should feel very familiar. What has been included on page 3 is a very brief analysis on which documentation is most appropriate for capturing the process, which specific section could be updated, and the nature of the changes.
Proposed next steps:
- Council to review the attached document and in particular, consider the suggestion of *where to document the process,* and provide any questions or concerns by * 27 August*. - If there are no substantive concerns on how to capture the process, staff to develop proposed redlines to the EPDP, PDP, and GGP Manuals, in time for discussion by the Council during the September meeting. - Again, if no substantive concerns, the ICANN Board and GNSO Council can discuss the proposed redlines during their bilateral at ICANN84. - Once there is a set of mutually agreed upon (i.e., Board and Council) redlines, the amended GNSO Operating Procedures would be put out for public comment, as is required for such changes.
The proposed next steps assume that there are no major concerns that need to be addressed along the way; if that turns out to not be the case, then intervening discussion can and would of course take place, pushing out timelines as needed.
If you have any questions or concerns, about either the attached documentation or the proposed next steps, please do let us know.
Best,
Steve
*Steven Chan*
VP, Policy Development Support & GNSO Relations
Internet Corporation for Assigned Names and Numbers (ICANN)
12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094-2536
Email: steve.chan@icann.org
Skype: steve.chan55
Mobile: +1.310.339.4410
Find out more about the GNSO by visiting: https://learn.icann.org/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwMG...>
Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNS...>
Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_group...>
_______________________________________________ council mailing list -- council@icann.org To unsubscribe send an email to council-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.
This email originated from outside the firm. Please use caution.