On Thu, Sep 07, 2017 at 02:25:14PM -0400, Joe Abley <jab...@hopcount.ca> wrote a message of 35 lines which said:
> 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'm not convinced by this reasoning. Either the opinion of the IETF carries some weight with some actors, or it doesn't. In the first case, we have to be careful of what we publish. In the second case, we should close the shop immediately and go back playing video games, since we are useless. Also, in the specific case of draft-tale-dnsop-serve-stale, there is another point: it is a local, unilateral decision by the resolver, not _directly_ affecting interoperability. People can do strange things on their resolvers (they already do). We should set rules (see first paragraph) but, on resolver behavior, we have to be modest. So, I don't think "a standard approach" is _mandatory_ in that specific case. _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
