On 03. 12. 25 16:28, Vladimír Čunát wrote:
On 16/10/2025 21.57, Petr Špaček wrote:
How would people here feel about EDE code for signaling that
particular query ended up as SERVFAIL because some limit was exceeded?
Would that also include cases like replying with TC=1 because exceeding
rate limits?
Indeed a good question! Originally I was thinking this would apply only
to SERVFAIL answers and TC=1 generated by RRL is not the case.
Is there a use-case for 'soft' vs 'hard' limit distinction?
Hard limit exceeded = SERVFAIL, go away.
Soft limit exceeded = TC=1, you might want to try again?
I don't know. WDYT?
--
Petr Špaček
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]