"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.
I'm not sure I understand the use-case either btw, but this rebuttal smells like the classic 'FUD it out of existence' IETF approach. Warren is smart. I'm sure he thought of this. -G 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. _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
