March 2026 - rssac-caucus - lists.icann.org

RSSAC001v3 – Question on the Removal of E.3.1-B and BCP 40 Collective Expectation
by Mohibul Mahmud April 1, 2026

April 1, 2026

*Subject :* RSSAC001v3 – Question on the Removal of E.3.1-B and BCP 40 Collective Expectation Hello everyone, I was going through the v2-to-v3 diff and noticed that E.3.1-B has been removed in v3. In v2, this expectation read: "The RSOs are collectively expected to deliver the service in conformance to IETF standards and requirements as described in BCP 40." I wanted to ask about this deletion, as it seems like a substantive change rather than simply an editorial one. As I understand it, BCP 40 is what ties the RSS (Root Server System) together from a collective protocol compliance standpoint. If E.3.1-B is removed, v3 doesn't seem to have anything that covers this at the system level anymore. E.3.2-A still covers protocol implementation, but that applies to each RSO individually — not to the RSS as a whole. This seems particularly relevant in light of the recent discussion around draft-ietf-dnsop-3901bis, which is now in the RFC Editor queue. If BCP 40 is updated or complemented by additional BCP guidance over time, the absence of E.3.1-B may leave RSSAC001 without a clear collective point of reference for those developments. So my question is simply: was this intentional, and if so, is there something in v3 that takes its place? I may be missing some context, so please feel free to correct me if I'm overlooking anything. Best regards, Mohibul On Tue, Mar 10, 2026 at 1:12 AM Andrew McConachie via rssac-caucus < rssac-caucus(a)icann.org> wrote: > Dear RSSAC Caucus Members, > > During the RSSAC001v3 call at ICANN 85 a diff document was discussed. This > is the document that the RSSAC used to compare RSSAC001v2 and the > RSSAC001v3 Working Document. It's attached to this mail as a PDF. > > The first page of the document explains more on how it was prepared. > > Thanks, > Andrew > > _______________________________________________ > rssac-caucus mailing list -- rssac-caucus(a)icann.org > To unsubscribe send an email to rssac-caucus-leave(a)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.

3 4

RSSAC Input to Fundamental Bylaws Amendments on IANA-Related Reviews and CSC Charter Update
by Andrew McConachie March 31, 2026

March 31, 2026

Dear RSSAC Caucus Members, The RSSAC has submitted a Public Comment on the Fundamental Bylaws Amendments on IANA-Related Reviews and CSC Charter Update. https://www.icann.org/en/public-comment/proceeding/fundamental-bylaws-amend… The RSSAC's input can be viewed here. https://www.icann.org/en/public-comment/proceeding/fundamental-bylaws-amend… Thanks, Andrew

1 0

RSSAC001v3 WP Teleconferences
by Daniel Gluck March 27, 2026

March 27, 2026

Hello All, I have just sent a calendar invite series for the relaunch of the RSSAC001v3 WP. The calls will be at 16:00 UTC on alternating Tuesdays starting on 7 April. If the WP decides that this time is no longer acceptable, we can re-doodle poll the group and reset the day/time. Thanks, Dan Gluck

1 0

RSSAC001v3 WP Teleconference
by Daniel Gluck March 27, 2026

March 27, 2026

RSSAC001v3 WP Recurring Teleconference Every 2 Weeks on Tuesdays, starting 7 April 2026. (Calendar invite leads to ICANN86) 16:00 UTC for 1 hour https://icann.zoom.us/j/95975697474?pwd=9aOGeBjGwhy7E2O26GPedYnM4c5enm.1 Meeting ID: 959 7569 7474 Passcode: 9tiBMU%4&d

1 0

Diff of RSSAC001v2 and RSSAC001v3 Working Document
by Andrew McConachie March 18, 2026

March 18, 2026

Dear RSSAC Caucus Members, During the RSSAC001v3 call at ICANN 85 a diff document was discussed. This is the document that the RSSAC used to compare RSSAC001v2 and the RSSAC001v3 Working Document. It's attached to this mail as a PDF. The first page of the document explains more on how it was prepared. Thanks, Andrew

2 1

Re: RSSAC001v3 Work Party Update / Meeting at ICANN 85
by Daniel Gluck March 17, 2026

March 17, 2026

Hello All, The RSSAC has approved the RSSAC001v3 SOW. The approved SOW is linked here: https://docs.google.com/document/d/1yH3jo5AHhTfVD4pbKAdXd4PHmGB2fUQT8HpYHrl… Here is the sched link again for Sunday March 8 @ 15:00 - 16:00 IST, (09:30 - 10:30 UTC). https://icann85.sched.com/event/2Gwcl/rssac-work-session-4-of-4 Thanks, Dan Gluck On 3/4/26, 3:58 PM, "Andrew McConachie via rssac-caucus" <rssac-caucus(a)icann.org <mailto:rssac-caucus@icann.org>> wrote: I sent the wrong link to the meeting agenda. Please use this one instead. https://docs.google.com/document/d/1q6nJ9xitsw2NC3ghmz2FQ2HZDKb2OIKK27c7xJA… <https://docs.google.com/document/d/1q6nJ9xitsw2NC3ghmz2FQ2HZDKb2OIKK27c7xJA…> --Andrew > On 4 Mar 2026, at 11:26, Andrew McConachie via rssac-caucus <rssac-caucus(a)icann.org <mailto:rssac-caucus@icann.org>> wrote: > > Dear RSSAC Caucus Members, > > The RSSAC has been working on an updated Statement of Work for the RSSAC001v3 Work Party. This new Statement of Work has reached a stable state and is currently being voted on in the RSSAC. The vote should finish at 11:59 AM UTC on Friday, 6 March. > > We have a scheduled RSSAC001v3 Work Party meeting at ICANN 85 that is scheduled for Sunday March 8 @ 15:00 - 16:00 IST, (09:30 - 10:30 UTC). The meeting will be held in person at ICANN 85 in Mumbai, India and online. > > If the new Statement of Work is approved by the RSSAC the meeting will go forward. If the new Statement of Work is not approved by the RSSAC the meeting will be cancelled. ICANN staff will inform this mailing list once we know the result of the vote. > > Remote access for the meeting will be posted here once it is available. > https://icann85.sched.com/event/2Gwcl/rssac-work-session-4-of-4 <https://icann85.sched.com/event/2Gwcl/rssac-work-session-4-of-4> > > Link to the meeting agenda and materials. > > Thanks, > Andrew > > > _______________________________________________ > rssac-caucus mailing list -- rssac-caucus(a)icann.org <mailto:rssac-caucus@icann.org> > To unsubscribe send an email to rssac-caucus-leave(a)icann.org <mailto: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 <https://www.icann.org/privacy/policy>) and the website Terms of Service (https://www.icann.org/privacy/tos <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.

6 12

RSSAC Caucus IETF 126 Vienna Travel Support Results
by Daniel Gluck March 16, 2026

March 16, 2026

Dear RSSAC Caucus Members, Thank you for your consideration of and applications for travel funding for IETF 126 in Vienna, AT from 18-26 July 2026. This email outlines the process for selecting funded participants for IETF 126 based on the RSSAC Caucus IETF Supported Travelers Funding Guidelines.<https://drive.google.com/file/d/1OMp4PZKLV9JCXLYNugJSwey6ONFwhFba/view> 1. Overview * Funded Slots Available: 4 * Funding Requests Received: 11 * First Priority Funding Requests Received: Jeff Osborn, Robert Story, Abdulkarim Oloyede, Daniel Migault * Second Priority Funding Requests Received: James Kunle Olorundare, Naveed Bin Rais, Mohibul Mahmud, Ali Hussein * Third Priority Funding Requests Received: Muhammad Farhan Khan, Ceasar Waweru Kabue, Dessalegn Yehuala The Priority levels were determined by the RSSAC Admin Committee following the guidelines set forth in the RSSAC Caucus IETF Supported Travelers Funding Guidelines.<https://drive.google.com/file/d/1OMp4PZKLV9JCXLYNugJSwey6ONFwhFba/view> 2. Final List of Participants for Selection Funding requests are considered one priority at a time, by descending order. After all requests in a priority category are considered, remaining slots will be moved to the next priority. Within each priority, if there are more requests than the number of available slots, the publicly verifiable random selection as described in RFC 3797 will be conducted. First Priority - Funding Secured (4 Slots Available) * Jeff Osborn * Abdulkarim Oloyede * Robert Story * Daniel Migault Second Priority - Not Selected for IETF 126 Funding (0 slots Remaining) * James Kunle Olorundare * Naveed Bin Rais * Mohibul Mahmud * Ali Hussein Third Priority - Not Selected for IETF 126 Funding (0 Slots Remaining) * Muhammad Farhan Khan * Ceasar Waweru Kabue * Dessalegn Yehuala Please let us know if you have any questions. Thanks, Dan Gluck

3 2

Re: Joint Meeting between the ICANN Board and the Root Server System Advisory Committee (RSSAC), held yesterday, March 10, 2026
by James Olorundare March 13, 2026

March 13, 2026

*Background: Researching the Impact of AI on the DNS* *Why This Matters Now* During the joint meeting between the *ICANN Board* and the *Root Server System Advisory Committee (RSSAC)*, held yesterday, March 10, 2026, at the ongoing *ICANN85* meeting, a critical question was raised. Derived from ICANN’s Five-Year Strategic Plan, the Board requested that the RSSAC identify emerging trends capable of reshaping the Internet. The most significant trend identified during this dialogue is the rapid rise of *Artificial Intelligence (AI)*. While our primary focus is typically the "Root" , it is clear that AI will influence the entire *Domain Name System (DNS) as established during the meeting.* Based on the productive discussions held during that meeting, I would like to advance this conversation as follows: *Moving forward to Facts* Currently, there is much speculation regarding how AI will change the Internet; however, it is vital that we establish a foundation of technical fact. To ensure the Internet remains stable and secure, we cannot rely on assumptions. We require *empirical research*—the collection of real-world data and evidence. We need to analyze how AI-powered applications and automated systems are currently impacting the DNS so that we may adequately prepare for the future. Consequently, I propose the formation of a *Working Group* dedicated to conducting this essential research. *The Objectives/Goals of this Research* This proposal suggests a comprehensive study to examine the "big picture" of AI's interaction with the DNS. The objective is to produce a formal report that will, among other priorities: - *Track Traffic:* Determine if AI is generating increased traffic volumes or unique types of requests and identify the genuine and the fake. To do this the RSOs may be engaged. - *Identify Early Risks:* Detect whether AI integration is placing additional stress on system security or resilience with respect to DNS. - *Support Future Planning:* Equip the global community of experts with the data necessary to develop informed, "fit-for-purpose" *a**dvisory document* for the future. By initiating this research now, we ensure that the Internet remains fast, reliable, and safe as AI technology continues to evolve. This proposal is intended for discussion and refinement. The overarching objective is to generate articulated, empirical data on the impact of AI on the DNS, directly addressing the inquiry posed by the ICANN Board to the RSSAC during our meeting on March 9, 2026 at the ongoing ICANN85 Community Forum. Thank you. *Olorundare, James Kunle* -- +2348036551591

11 13

Your RSSAC Caucus Membership Application
by Daniel Gluck March 10, 2026

March 10, 2026

Dear Sean, On the recommendation of the RSSAC Caucus Membership Committee, the RSSAC approved your application to join the RSSAC Caucus. Congratulations! As a next step, please complete this form <https://forms.gle/1171C64auz9drwsf9> and read this onboarding document<https://docs.google.com/document/d/18IoSBDhQq6cGC0ICmmo7t1bzB8TU3vsQtxsjJAC…>. We (RSSAC support staff – cc’d) will then add and introduce you to the RSSAC Caucus mailing list. Do not hesitate to contact us with any questions or concerns. Thanks, Dan Gluck

1 0

RSSAC Caucus Session on RSSAC001v3 Tomorrow
by Daniel Gluck March 7, 2026

March 7, 2026

Hello All, Please note that there is a session tomorrow for the RSSAC001v3 Work party 15:00-16:00 IST / 09:30 – 10:30 UTC Work Session 4 | RSSAC001v3 | Room 204 A/B https://icann.zoom.us/j/96244916725?pwd=5VY67MIDczFlJz3IkMFlWXrxUOz6HT.1 This is a work session for Root Server System Advisory Committee (RSSAC) Caucus RSSAC001v3 work party which considers updating RSSAC001v2: Service Expectations of Root Server Operators Agenda <https://docs.google.com/document/d/1q6nJ9xitsw2NC3ghmz2FQ2HZDKb2OIKK27c7xJA…> | Working Doc<https://docs.google.com/document/d/1umg_8adr0tcOoRI88rA40-3e9h6fO_bu/edit> | New SOW<https://docs.google.com/document/d/1yH3jo5AHhTfVD4pbKAdXd4PHmGB2fUQT8HpYHrl…> We look forward to seeing you online or in person! Thanks, Dan Gluck

2 1