Skip to main content

Last Call Review of draft-ietf-dnsop-nxdomain-cut-03

Request Review of draft-ietf-dnsop-nxdomain-cut
Requested revision No specific revision (document currently at 05)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2016-07-29
Requested 2016-07-25
Authors Stéphane Bortzmeyer , Shumon Huque
I-D last updated 2016-08-08
Completed reviews Genart Last Call review of -03 by Meral Shirazipour (diff)
Genart Telechat review of -04 by Meral Shirazipour (diff)
Secdir Last Call review of -03 by Adam W. Montville (diff)
Opsdir Last Call review of -03 by Sheng Jiang (diff)
Assignment Reviewer Sheng Jiang
State Completed
Request Last Call review on draft-ietf-dnsop-nxdomain-cut by Ops Directorate Assigned
Reviewed revision 03 (document currently at 05)
Result Ready
Completed 2016-08-08

Hi, OPS-DIR, Authors,

I have reviewed this document as part of the Operational directorate's ongoing
effort to review all IETF documents being processed by the IESG. These comments
were written with the intent of improving the operational
 aspects of the IETF drafts. Comments that are not addressed in last call may
 be included in AD reviews during the IESG review. Document editors and WG
 chairs should treat these comments just like any other last call comments.

This Standards Track document updates clearly the meaning and rules when a DNS
resolver receives a response with response code of NXDOMAIN. It updates RFC
1034, 2308. This document is well written. I don't see any
 major issues from the operations and management perspective. It is ready to be
 published. There are one of minor comments from me:

Section 11.3 lists two URIs, which is rarely see in RFCs. I am sure the first
URI should be removed by RFC editor, according to author


 note. But the second one seems meaning something in the real use. I guess it
 should be either reorganized as an informational reference or removed.

Best regards,