*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@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@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.