On 14/10/2015 15:55, Tony Finch wrote:
> Yes. Perhaps "transport tuple" is an excessively clever way of saying > "same connection". When I wrote that I wanted to allow independent choice > of query ID per connection (rather than implying a single global ID). Hmm, ยง6.2.1 talks about not re-using Message ID's but that's supposed to be in the context of a single connection. Across connections the Message ID space is of course independent. > Also, for UDP if you don't match the transport tuple then you lose (some > of) the benefit of port randomization, I think (depending on how many > ports you keep open). That's true, but this document isn't about UDP ;-) Ray _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
