On Wed, Sep 11, 2024 at 9:22 AM, Stephane Bortzmeyer <bortzme...@nic.fr>
wrote:

> In the current registry for Extended DNS Error Codes (RFC 8914), there are
> codes that may be interesting to add:
>
> * One to say that the response was deliberately minimal (RFC 8482)
> * One to say that the response comes from a local root (RFC 8806)
> * One to say that the response has been tailored because of ECS (RFC 7871)
> [the most useful, IMHO]
>
> I am thinking about asking for a registration. Policy for this registry is
> "first come, first served". Before I start sending email to IANA, I ask
> your advice. Is it a good idea?
>


Hmmmm. I'm not really sure….
The last one seems like a valuable bit of information.
The first one seems less interesting, but possibly still useful.
I don't really see the point / utility of the middle one, but it's entirely
likely that I'm missing something.

I think that there is a tradeoff between A: providing useful operational
and debugging information and B: additional software complexity and larger
response sizes.

It sort of feels like the EDE document should have included a mechanism for
a client to signal "I'm trying to debug something weird, please send me all
possible information that you have", and then we could have reserved a set
of codepoints for "Random other bits which are only interesting  to DNS
geeks, and only intended for human consumption". This could include things
like 'the actual server that answered' (some NSID systems only lists the
"load-balancer"/anycast site), zone version (see zoneversion :-)), if the
answer came from disk or is secretly forwarded, if the answer is "static"
or dynamically sourced / wildcard expanded, quote of the day, what's for
lunch, etc.

It also seems like there are some set of error codes which I'd be fine
shipping over a TCP connection, but which I don't want to waste UDP bits
on….

W


Will the authors of resolver / authoritative software use it?
>
> _______________________________________________
> DNSOP mailing list -- dnsop@ietf.org
> To unsubscribe send an email to dnsop-le...@ietf.org
>
_______________________________________________
DNSOP mailing list -- dnsop@ietf.org
To unsubscribe send an email to dnsop-le...@ietf.org

Reply via email to