Last Call Review of draft-ietf-dnsext-dnssec-registry-fixes-
review-ietf-dnsext-dnssec-registry-fixes-secdir-lc-barnes-2011-06-23-00

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.

This document describes some minor fixes to the DNSSEC registry of
cryptographic algorithms.  I have some minor questions / nits below, but
overall the document seems in fine shape.

--Richard

1. Why is there a date on the reserved numbers, rather than simply setting the
status to "reserved"?  Is there a desire to provide some guarantee to
implementors?

2. "Registry entries 13-251 remains Unassigned" -> "Registry entries 13-251
remain Unassigned"

3. It might be helpful to say explicitly that the table in the IANA
Considerations replaces the current registry.