[DNSOP] Last Call: (A Common Operational Problem in DNS Servers - Failure To Communicate.) to Best Current Practice

2019-12-05 Thread The IESG
The IESG has received a request from the Domain Name System Operations WG (dnsop) to consider the following document: - 'A Common Operational Problem in DNS Servers - Failure To Communicate.' as Best Current Practice The IESG plans to make a decision in the next few weeks, and solicits final

Re: [DNSOP] Benjamin Kaduk's No Objection on draft-ietf-dnsop-serve-stale-09: (with COMMENT)

2019-12-05 Thread Benjamin Kaduk
On Thu, Dec 05, 2019 at 02:59:16PM -0500, Dave Lawrence wrote: > Thank you very much for your review, Ben. > > Benjamin Kaduk via Datatracker writes: > >For a comprehensive treatment of DNS terms, please see [RFC8499]. > > > > (side note: I myself would not use the word "comprehensive" when i

Re: [DNSOP] Benjamin Kaduk's No Objection on draft-ietf-dnsop-serve-stale-09: (with COMMENT)

2019-12-05 Thread Dave Lawrence
Thank you very much for your review, Ben. Benjamin Kaduk via Datatracker writes: >For a comprehensive treatment of DNS terms, please see [RFC8499]. > > (side note: I myself would not use the word "comprehensive" when it > explicitly says that "some DNS-related terms are interpreted quite > di

Re: [DNSOP] Roman Danyliw's No Objection on draft-ietf-dnsop-serve-stale-09: (with COMMENT)

2019-12-05 Thread Dave Lawrence
Thank you for the review, Roman. Roman Danyliw via Datatracker writes: > * I agree with Mirja, Section 8 is more informative than what is > alluded to the paragraph starting with “Several recursive resolvers > …” in Section 3, and IMO is worth keeping. I've already updated the GitHub copy in resp