Skip to main content

Last Call Review of draft-ietf-dnsext-axfr-clarify-
review-ietf-dnsext-axfr-clarify-secdir-lc-lonvick-2010-03-03-00

Request Review of draft-ietf-dnsext-axfr-clarify
Requested revision No specific revision (document currently at 14)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2010-03-09
Requested 2010-02-24
Authors Edward P. Lewis , Alfred Hoenes
Draft last updated 2010-03-03
Completed reviews Secdir Last Call review of -?? by Chris M. Lonvick
Assignment Reviewer Chris M. Lonvick
State Completed
Review review-ietf-dnsext-axfr-clarify-secdir-lc-lonvick-2010-03-03
Completed 2010-03-03
review-ietf-dnsext-axfr-clarify-secdir-lc-lonvick-2010-03-03-00
Hi,

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.



Overall, I found no problems with the document.  It is well written and 


very explanatory.  The following notes and suggestions are editorial.






It would be nice to reference the security considerations of RFCs 1034 and 


1035 just to say that this specification doesn't add any new 


considerations, however those documents don't have any security 


considerations sections.  Would the authors then consider something like 


the following (which would be the first paragraph in Section 8):



   This document is a clarification of a mechanism outlined in RFCs 1034
   and 1035 and as such does not add any new security considerations.  The
   security considerations relevent to the deployment of this
   specification are noted in RFC 4033.



In my first reading of the document, I was unfamiliar with the term "mbz". 


I'd suggest expanding the acronym in one place.




Thanks,
Chris