On Thu, Mar 19, 2015 at 09:56:56AM +0100, W.C.A. Wijngaards wrote: > > +1. Backwards compatibility means you cannot specify that existing > implementations have to change. You can specify that 'upgraded' > implementations perform new actions, of course.
No RFC can make changes that apply to implementations that do not conform with that RFC. This is true by definition. The draft does not somehow magically retroactively change the text in RFC 1035. It specifies new behaviour, and old implementations that don't conform to this new text will therefore obviously not exhibit the new behaviour. What's the problem? Best regards, A -- Andrew Sullivan a...@anvilwalrusden.com _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
