On 05. 11. 24 11:56, Shane Kerr wrote:
I wrote a quick draft to specify that answers returned should be
returned in a random order:
https://datatracker.ietf.org/doc/draft-kerr-everybodys-shuffling/
This comes out of recent experience we had where a customer saw
significant bias in how their servers were used until we randomized the
order where returned our answers. I confirmed that in many cases neither
authority servers nor recursive resolvers shuffle the answers; customer
reports indicate that the actual clients just use the first answer
returned.
This document essentially mandates workaround for dumb stubs into the
core protocol. Don't do that PLEASE!
Reasons were laid out by other people in this thread:
- Implementation complexity (Otto Moerbeek)
- Unreliable anyway (Paul Ebersman, Edward Lewis, I guess others as well)
- Fix closer to app (Mukund Sivaraman) - I'm in this camp as well!
FTR we are gradually removing RR reordering features from BIND (we just
got rid of fixed but user-defined rr order).
--
Petr Špaček
Internet Systems Consortium
_______________________________________________
DNSOP mailing list -- dnsop@ietf.org
To unsubscribe send an email to dnsop-le...@ietf.org
