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.
Basically, I don't think any proposed modification of DNS in this space can be done, which doesn't face this risk: therefore, I don't see it having directing force. If there is some trick to doing something which doesn't expose the risk, What is it? cheers -George On Tue, Nov 14, 2017 at 9:30 AM, Stephane Bortzmeyer <bortzme...@nic.fr> wrote: > On Mon, Nov 13, 2017 at 08:54:16PM +0800, > Ray Bellis <r...@bellis.me.uk> wrote > a message of 29 lines which said: > >> Would it be feasible to reserve a standard RCODE value in the header >> that just means "see extended error"? > > First reaction: no. Middleboxes would block these responses, or old > clients would not know what to do with it. > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
