> 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.
The big question for this draft is why is it not sufficient for the authoritative to shuffle. The authoritative is under control or contracted by the party that suffers from the load imbalance. We can assume that in general there are enough recursive resolvers in the world that when each recursive resolver gets a shuffled reply, the overall effect of applications contacting the service will be randomized. Maybe there are exceptions, but then it is best to discuss them before placing requirements on every part of the stack. _______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
