Skip to main content

Last Call Review of draft-ietf-dnsop-dnssec-dps-framework-
review-ietf-dnsop-dnssec-dps-framework-genart-lc-yee-2012-07-15-00

Request Review of draft-ietf-dnsop-dnssec-dps-framework
Requested revision No specific revision (document currently at 11)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2012-07-17
Requested 2012-07-05
Authors Fredrik Ljunggren , Anne-Marie Eklund-Lowinder , Tomofumi Okubo
I-D last updated 2012-07-15
Completed reviews Genart Last Call review of -?? by Peter E. Yee
Secdir Telechat review of -08 by Stephen Kent (diff)
Assignment Reviewer Peter E. Yee
State Completed
Request Last Call review on draft-ietf-dnsop-dnssec-dps-framework by General Area Review Team (Gen-ART) Assigned
Completed 2012-07-15
review-ietf-dnsop-dnssec-dps-framework-genart-lc-yee-2012-07-15-00
I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<

http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

This draft is ready for publication as an Informational RFC.

Document: draft-ietf-dnsop-dnssec-dps-framework-08
Reviewer: Peter Yee
Review Date: 14-July-2012
IETF LC End Date: 17-July-2012
IESG Telechat date: Pending

Summary: This draft provides a framework for the creation of DNSSEC Policies
and Practice Statements. 

Major Issues: None

Minor Issues: 

Section 4.4.5 discusses how to handle key compromise.  It might be useful to
discuss here or somewhere else in the document how the compromise is
prevented from recurring if there were no attenuating measures in place
beforehand.  That might well lead to a revision of the DP or DPS.  The draft
doesn't really discuss under what circumstances a document should be
iterated or amended.  Of course, that might be considered a meta issue
and outside of the scope of the DP or DPS proper.

Nits/editorial comments: 

In Section 4.6, "behaviour" is spelt in the British manner.  While
most assuredly not incorrect, you may wish to spell it in the
American manner.

Serial commas are used inconsistently.  Nothing as egregious as the
following
example, however. ;-)


http://grammarnowtips.wordpress.com/2011/01/08/a-case-for-the-serial-comma/