On 7 Sep 2017, at 11:42, Stephane Bortzmeyer <bortzme...@nic.fr> wrote:
> On Tue, Sep 05, 2017 at 03:25:39PM -0400, > tjw ietf <tjw.i...@gmail.com> wrote > a message of 77 lines which said: > >> This starts a formal Call for Adoption for draft-tale-dnsop-serve-stale >> >> The draft is available here: >> https://datatracker.ietf.org/doc/draft-tale-dnsop-serve-stale/ > > I'm not enthousiastic. We should focus on making the DNS > infrastructure more reliable, not on adding something to a pile of > already fragile protocols. I hear that. I don't have a strong opinion about whether serving stale data in general is desirable or abhorrent. However, the pragmatist in me says that people are already implementing things like this anyway, and a standard approach is better for all concerned than a fragmented set of uncomfortably-different implementations, which will surely make troubleshooting problems harder. I also think if a standard specification can be obtained it ought to include appropriate instrumentation to allow a response to indicate whether data is stale or not. This seems to me just one example of a set of additional components we might expect the working group to come up with, which in my mind is a good reason to make it a working group document. I support adoption with all of that in mind. Joe _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
