Last Call Review of draft-ietf-dnsext-dnssec-algo-signal-09

Request Review of draft-ietf-dnsext-dnssec-algo-signal
Requested rev. no specific revision (document currently at 10)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2013-04-03
Requested 2013-03-21
Authors Steve Crocker, Scott Rose
Draft last updated 2013-04-04
Completed reviews Genart Last Call review of -09 by Meral Shirazipour (diff)
Genart Telechat review of -10 by Meral Shirazipour
Secdir Last Call review of -09 by Kathleen Moriarty (diff)
Assignment Reviewer Meral Shirazipour
State Completed
Review review-ietf-dnsext-dnssec-algo-signal-09-genart-lc-shirazipour-2013-04-04
Reviewed rev. 09 (document currently at 10)
Review result Almost Ready
Review completed: 2013-04-04


I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at



Please resolve these comments along with any other Last Call comments you may receive.


Document: draft-ietf-dnsext-dnssec-algo-signal-09

Reviewer: Meral Shirazipour

Review Date: 2013-04-03

IETF LC End Date: 2013-04-03

IESG Telechat date: N/A



This draft is almost ready to be published as Standard RFC but I do have some editorial comments.


Nits/editorial comments:

- Reading the abstract does not tell why these options are necessary. The 4th paragraph in Intro mentions the purpose of these options as well as Section 8.

Please consider adding a similar sentence as Section 8 to the abstract:

"The proposed extensions allow the signaling of new algorithm uptake in client code to allow zone administrators to know when it is possible to complete an algorithm rollover in a DNSSEC signed zone."


-[Page 4], last sentence: "in a potential future example". Suggestion: "in potential future examples".


-[Page 7], Section 9, [I-D.ietf-dnsext-rfc2671bis-edns0], latest version is 10.


Best Regards,




Meral Shirazipour