On Fri, 3 Jul 2020, Brian Dickson wrote:
It makes clear the difference between implied and inferred. The flag clearly indicates that some glue which would otherwise be considered necessary has not been sent.
That sounds a lot like the TC flag. I realize that some people have interpreted the TC flag to mean something else, but I think its actual meaning is pretty clear.
Additionally, the flag would signal compliance with updated 1035, for starters.
This would in effect be a version number. Our experience with version numbers in old protocols has not been great.
Also, it would facilitate lower effort in figuring out if a TC is referral related or not, which could be important for implementers/operators doing large scale stuff.
I don't understand this. Caches surely already know when a response is a referral. If a referral response has TC set, in what way could that not be referral related?
Most importantly, this is all about interoperability, including not just the wire format but the operational signaling.
Turning on bits that have been zero for 35 years doesn't have a great history of interop, either. Look at the history of queries with EDNS0 never getting a response.
Regards, John Levine, jo...@taugh.com, Taughannock Networks, Trumansburg NY Please consider the environment before reading this e-mail. https://jl.ly _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
