Hi Shane! On 5 Nov 2024, at 13:13, Shane Kerr <sh...@time-travellers.org> 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/ I think that you might need to nail down what "random" means. I presume you don't mean random in the xkcd-221 sense, for example. You probably don't mean lava-lamp or double-pendulum random either, at least not as a MUST. Would it be ok for an rrset to be shuffled once per minute rather than every time a response is generated? More generally from your OARC talk I think your experience is that (paraphrasing) not shuffling is fine for most people, but sometimes causes problems. Does it make sense to translate that into a normative MUST for the protocol? I think good practice on the consumer end of this is to understand that addresses obtained from a dns response be treated as an unordered set and not an ordered list. Maybe it makes sense to talk about recommendations there as well as recommendations for DNS responders? Joe _______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
