[RSSAC Caucus] [SPAM] Re: Security Incident Reporting and c-root incident

[Ondřej Surý]

Paul,

correct me if I'm wrong, but the reported delay was 3 full days, right?

That's about 4320 minutes just this month, and divided by 60 that's about 70 minutes on average?

Ondřej
--
Ondřej Surý (He/Him)
ondrej at sury.org

> On 23. 5. 2024, at 0:39, Paul Hoffman <paul.hoffman at icann.org> wrote:
> 
> Focusing on the "stale data" point:
> 
> On May 22, 2024, at 14:20, David Conrad <david.conrad at layer9.tech> wrote:
>> If you’re talking about the RSS SIR Working Document, section 4.2 states:
>> 
>> "Data integrity refers to the "correctness" of the data in responses generated by the RSS.
>> […]
>> Examples of reportable incidents that affect Integrity:
>> * Any part of the RSS serving incorrect data for the root zone”
>> 
>> Providing stale data would appear to me to be “serving incorrect data for the root zone.
> 
> The question of "how long is it acceptable to serve a version of a root zone after the RZM has issued a new version" was debated extensively during the development of RSSAC047. The recommended threshold in that document is 65 minutes, over the course of an entire month. That is, an RSO would only not pass this metric if its publication latency is worse than 65 minutes averaged over the approximately 60 zones published in a month.
> 
> --Paul Hoffman
> 
> _______________________________________________
> rssac-caucus mailing list
> rssac-caucus at icann.org
> https://mm.icann.org/mailman/listinfo/rssac-caucus
> 
> _______________________________________________
> 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.