Hello everyone, As the work party works through what to keep, update, or remove from v2, I wanted to raise a question about E.3.7-A. The expectation currently asks each RSO to monitor elements within its infrastructure to identify and mitigate failures in a timely manner. The outcome-focused language makes sense — it avoids locking RSOs into specific implementation choices. That said, monitoring and observability practices have changed considerably since v2 was written. One example worth noting is OpenTelemetry, a vendor-neutral observability framework that is seeing increasing adoption in infrastructure-heavy environments. It offers more granular visibility into where failures or delays occur across a query path — something traditional monitoring does not always capture well. There was also a recent DNS-OARC presentation by Peter van Dijk of PowerDNS exploring OpenTelemetry tracing specifically in a DNS context. This is not a suggestion to mandate any specific tool in v3. The question is simply whether the descriptive text under E.3.7-A should acknowledge that monitoring practices have evolved, while keeping the expectation itself outcome-based. Curious to hear others' thoughts. Best regards, Mohibul