edmonds> Overall I think it might make sense to have an informational edmonds> document that describes the problem, the mechanisms that could edmonds> be used in the DNS to address that problem (various kinds of edmonds> reordering at different points in the stack, etc.), makes edmonds> operational recommendations and encourages implementers to edmonds> adopt those recommendations as good defaults, but I don't think edmonds> it makes sense to try to enforce a new, normative protocol edmonds> requirement like this on DNS servers or applications.
I like the idea of describing the problem, along with the challenges of trying to randomize, then preserve that randomized order. Verious server implementations have already had an option to randomize for years and it hasn't helped, so perhaps advice in "don't play with it if you're in the middle", definitely advice for app folks on when/why this might matter. Doing a MUST on the auth server side doesn't at all seem like the droid we're looking for. _______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
