Last Call Review of draft-ietf-dnsop-serve-stale-08

Request Review of draft-ietf-dnsop-serve-stale
Requested rev. no specific revision (document currently at 10)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2019-09-25
Requested 2019-09-11
Authors David Lawrence, Warren Kumari, Puneet Sood
Draft last updated 2019-09-23
Completed reviews Secdir Last Call review of -08 by Adam Montville (diff)
Genart Last Call review of -07 by Brian Carpenter (diff)
Assignment Reviewer Adam Montville
State Completed
Review review-ietf-dnsop-serve-stale-08-secdir-lc-montville-2019-09-23
Posted at
Reviewed rev. 08 (document currently at 10)
Review result Ready
Review completed: 2019-09-23


I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the security area directors.  Document editors and WG chairs should treat these comments just like any other last call comments.

At first I was confused about offering an option to allow use of stale DNS data, but after reading the draft and realizing that the decision is still left to the operator, this draft is OK. 

The draft brings up-to-date the definition of TTL and offers additional specification on interpreting specific TTL values.  Perhaps some expansion as to the prevalence of bad actors using the caches and fraudulently issued, domain-validated certificates in the Security Considerations section is warranted. 

Nevertheless, it appears that implementations have been fielded and in use operationally for quite some time, presumably without a problem, and, as previously stated, operators don't have to enable this functionality unless they warrant availability of their services to be paramount.