- rssac-caucus - lists.icann.org

RSSAC064: Statement on KSK Algorithm Rollover
by Daniel Gluck April 9, 2026

April 9, 2026

Dear RSSAC Caucus Members, The RSSAC has submitted a public comment for the Proposed Root KSK Algorithm Rollover.<https://www.icann.org/en/public-comment/proceeding/proposed-root-ksk-algori…> It is a numbered RSSAC Publication, RSSAC064. That document can be viewed here.<https://itp.cdn.icann.org/en/files/publications/rssac064-statement-on-ksk-a…> Thanks, Dan Gluck

1 0

RSSAC Public Comment Response: Standard Bylaws Amendment – Transition Article on Specific Reviews
by Daniel Gluck April 8, 2026

April 8, 2026

Hello RSSAC Caucus Members, The RSSAC has submitted a public comment response for the Standard Bylaws Amendment – Transition Article on Specific Reviews<https://www.icann.org/en/public-comment/proceeding/standard-bylaws-amendmen…> proceeding. The comment can be viewed here<https://itp.cdn.icann.org/public-comment/proceeding/Standard%20Bylaws%20Ame…>. Thanks, Dan Gluck

1 0

RSSAC001v3 Work Party Update
by Andrew McConachie April 8, 2026

April 8, 2026

Dear RSSAC Caucus Members, The RSSAC001v3 Caucus Work Party met yesterday and discussed v2 of the SoW and the Working Document. It was agreed to continue moving forward with Working Document v2. The feedback received by the RSSAC was discussed and Working Document v2 was annotated with the work party's disposition on each element of feedback. This discussion will continue and if you have opinions on the feedback received from the RSSAC please add those as Suggestions to Working Document v2. The work party will also begin to discuss the differences between RSSAC001v2 and Working Document v1. The question is whether any of these changes should be ported over to Working Document v2. These can be seen in the attached MS Word file. The work party would like to know from the larger Caucus whether there are members who would like to join the work party meetings, but cannot because the standing meeting time does not work for them. If you would like to join work party meetings but cannot the standing meeting time please mail rssac-staff(a)icann.org directly. Our next meeting will be held on April 21 @ 16:00 UTC. Thanks, Andrew Statement of Work v2 https://drive.google.com/file/d/1vJFXZgUR3gK2lsHmickVbpq8ErYnRRiB/edit Working Document v2 https://docs.google.com/document/d/1pYOVR9ApZAAL23yY5mFHzOdJ6db8tHXrwO43iQb… Diff of RSSAC001v2 and Working Document v1

1 0

RSSAC001v3 Caucus Work Party Update
by Andrew McConachie April 7, 2026

April 7, 2026

Dear RSSAC Caucus Members, The RSSAC001v3 Caucus Work Party will meet next week on April 7th @ 16:00 UTC. Yesterday staff met with the work party co-Chairs (Robert and Abdulkarim) and we decided on an agenda for this meeting. The agenda is basically to discuss the new Statement of Work and then discuss the new working document. I'm calling the new SoW and new Working Document version 2, or v2. Agenda for RSSAC001v3 Caucus Work Party Meeting 15 (April 7, 2026) https://docs.google.com/document/d/1vNE5nzFVFjeITlgGS62HCanE1XnCzqEF9eYTvjq… RSSAC001v3 Statement of Work v2 https://drive.google.com/file/d/1vJFXZgUR3gK2lsHmickVbpq8ErYnRRiB/ I created a new working document for the work party that starts from RSSAC001v2 and then Suggests everything that the RSSAC agreed was a good change. This is version 2 of the Working Document. Version 1 has been set to View Only for a while now and it will stay that way. RSSAC001v3 Working Document v2 https://docs.google.com/document/d/1pYOVR9ApZAAL23yY5mFHzOdJ6db8tHXrwO43iQb… There is also a diff document that shows changes between RSSAC001v2 and where the work party left off (v1). I've attached this as an MS Word document so that we can view the tracked changes. There are probably some useful changes in this diff document that the work party may wish to port over to Working Document v2. Thanks, Andrew

4 3

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 Teleconference - 7 April 2026
by Daniel Gluck April 1, 2026

April 1, 2026

Hello RSSAC Caucus Members, The next RSSAC Teleconference will take place on Tuesday, 7 April at 14:00 UTC. Please let me know if you would like an invitation to this meeting. All standing invitations have been sent. Thanks! Dan Gluck Draft Agenda (* = Vote) 1. Call to Order (Jeff Osborn) 2. Roll Call (Jeff Osborn) 3. Agenda Review (Jeff Osborn) 4. Administration * ICANN85 RSSAC Meeting Draft Minutes* (Daniel Gluck) * RSSAC Caucus Membership Committee Update (Ken Renard) i. RSSAC Caucus Member Activity Tracking * ICANN86 Planning i. Draft Agenda ii. Session Requests iii. Community Plenaries 1. Work Items * RSSAC001v3 Work Party Discussion (Daniel Migault, Duane Wessels) * RSSAC000 Statement of Work Discussion (Andrew McConachie) * Public Comment (Daniel Gluck) i. Standard Bylaws Amendment – Transition Article on Specific Reviews* * RSSAC Capacity Discussion (Jeff Osborn) * GAC Communique Issue of Importance (Andrew McConachie) 1. Reports * Chair/Vice Chair (Jeff Osborn and Hans Petter Holen) * Liaison to the ICANN Board (Wes Hardaker) * Liaison to the CSC (Hiro Hotta) * Liaison to the RZERC (Lars-Johan Liman) * Delegate to the ICANN NomCom (Abdulkarim Oloyede) * Liaison from the IAB (Daniel Migault) * Liaison from the SSAC (Russ Mundy) * Liaison from the IANA Functions Operator (James Mitchell) * Liaison from the Root Zone Maintainer (Duane Wessels) * RSS GWG report (All) * Review of Reviews CG (Jeff Osborn and Ken Renard) * Participant on GNSO PDP on DNS Abuse Mitigation (Erum Welling) 2. Any Other Business (Jeff Osborn) * Next meeting: Tuesday 5 May at 14:00 UTC 3. Adjournment (Jeff Osborn)

1 0

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