Moin! On 19 Jul 2016, at 8:18, George Michaelson wrote:
> "in reality" is skewing the story. You don't foresee a usecase, but > you do foresee abuse? So deploy cookies or move to TCP, or DTLS or > some other cost space where amplify implies special knowledge, or cost > on the amplifier. Which then introduces a deployment or scaling problem. Granted for Google scaling DNS to TCP is not a problem, but it might be for others. [..] > PS a use case as I understand it, is people (like 8.8.8.8) who see > patterns in otherwise unrelated DNS query and could potentially short > circuit in time, and query chain sequence things which are utterly > predictable. You ask for A? we know in 2 ms you will ask for AAAA, or > DS/DNSKEY of the parent or... because.. well because we have the query > dynamics in the space, and we know what we see. So lets put things > into answers and start converting clients to understand this, and we > drop query load significantly and speed up DNS closure. This feels > like optimizations we'd expect in other protocols. Except that if you have a decent size and hot Cache with refreshing these records will be in there anyway. IMHO you gained nothing, but I agree with Jim Reid that it would be good to have data on this. So long -Ralf _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
