On Nov 14, 2017, at 09:37, George Michaelson <[email protected]> wrote:
> Stephane, I don't entirely understand your response. old systems can > never understand new code point assignments, or know what to do with > it, no proposed change can alter this. Middleboxes dropping unexpected > things will hit almost any proposed modification of packets in flight. The implication is, I think, that some new code points are more likely to survive the attention of Sauron's Middleware than others. We have seen claims in the past that new RRTYPEs, new EDNS(0) options, new EDNS(i) with i > 0, new records in ADDITIONAL sections, etc that will all fall fail of middleware or other dependent systems. What's not clear is the relative impact of each, but it seems intuitively true that the impact of each is probably not the same. For example, I bet it's more practical to implement a new EDNS(0) option than it is to deploy EDNS(1), but I have no science to back up that intuition. If only there was some kind of research group adept at wide-scale measurement from the end-user perspective that could shed some light on this! Joe _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
