Dear Rob, Thank you for explaining how the GWG and RSSAC fit together and for pointing me to the GWG resources. Your summary of the next steps and the caution about plain-language summaries was very helpful — I understand now how the process moves from recommendations to broader community adoption. I’ll review the materials you shared to better follow the upcoming discussions. Best regards, Mohibul Mahmud On Thu, Sep 25, 2025 at 9:18 AM Robert Carolina <rob@isc.org> wrote:
Hello Mohibul Mahmud
You raise a number of interesting questions.
As you may know, GWG is not a part of RSSAC. It is an ad hoc working group. All GWG meetings are recorded and available for review. A detailed history of the GWG, meeting recordings, etc, are on the ICANN web site. Search terms RSS GWG ICANN or link:
https://icann-community.atlassian.net/wiki/spaces/soacabout/pages/116787589/...
Subject to corrections from my colleagues, I believe that the next stage is for the GWG to consider whatever comments have been received which it will very probably do at its next scheduled meeting. I anticipate that after GWG has a chance to consider feedback, and makes whatever amendments (if any) to its draft report, it will forward the package to the ICANN Board and community for consideration. I anticipate that there will be some comments made at the upcoming ICANN 84 in Dublin.
As for materials to assist in understanding the framework, that's an interesting idea that is worth exploring. One challenge is how to create a description of a complex document that is the result of consensus, without accidentally triggering a new and even more complex "consensus explanation documentation" process. :-)
One preliminary point to keep in mind is this: GWG is making recommendations on how to move forward. Actually moving forward will require relevant identified stakeholders to embrace the proposals, to sit down together, to produce more detailed systems and protocols as outlined, and then to finally agree that the resulting structure is ready to "govern". The framework is a path that we hope stakeholders can follow to reach that agreement.
Kind regards
Rob
-- Robert Carolina General Counsel Internet Systems Consortium +447712007095 (mobile, WhatsApp, Signal) rob@isc.org My normal time zone: UTC+0/UTC+1 LinkedIn: www.linkedin.com/in/robertcarolina/
ISC and Internet Systems Consortium are names used by Internet Systems Consortium, Inc (a not-for-profit company) and its wholly owned subsidiary Internet Systems Corporation, both incorporated in Delaware with headquarters in New Hampshire, USA.
This transmission (the email and all attachments) is intended solely for the addressee(s). The contents are confidential and may be legally privileged. If you are not the intended addressee, or if this transmission has been addressed to you in error, you must not disclose, reproduce, or use the transmission or read any attachment. Delivery of this transmission to any person other than the intended recipient(s) does not waive privilege or confidentiality. If you have received this transmission in error, please reply by e-mail to explain receipt in error and then delete.
On 25 Sep 2025, at 12:55, Mohibul Mahmud via rssac-caucus < rssac-caucus@icann.org> wrote:
Dear RSSAC Caucus Members,
My understanding of RSSAC063 is that it expresses support for the Governance Working Group’s proposed Root Server System Governance Principles and Structure, viewing it as an important first milestone toward clearer, stronger, and more accountable management of the root server system.
As someone still new to RSSAC, I would appreciate any guidance on a few points to help me follow and contribute:
-
Are there planned next steps or milestones after this endorsement (e.g., drafts for implementation, further public comment rounds)? -
How can newcomers like me best stay involved or provide input as the governance model evolves? -
Will there be summary materials or explanations of the functional model to help new participants understand the structure more easily?
Thank you again for sharing this important document and for making space for community engagement.
Best regards, Mohibul Mahmud
On Thu, Sep 25, 2025 at 6:49 AM Andrew McConachie via rssac-caucus < rssac-caucus@icann.org> wrote:
Dear RSSAC Caucus Members,
The RSSAC has published RSSAC063: Statement on the Governance Working Group’s Root Server System Governance Structure.
RSSAC063 can be found here.
https://itp.cdn.icann.org/en/files/root-server-system-advisory-committee-rss...
RSSAC063 was also submitted as feedback to the ICANN Public Comment on the Functional Model for Root Server System Governance.
https://www.icann.org/en/public-comment/proceeding/functional-model-for-root...
Thanks, Andrew
_______________________________________________ rssac-caucus mailing list -- rssac-caucus@icann.org To unsubscribe send an email to rssac-caucus-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.
_______________________________________________ rssac-caucus mailing list -- rssac-caucus@icann.org To unsubscribe send an email to rssac-caucus-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.