Last Call Review of draft-ietf-avtcore-srtp-encrypted-header-ext-04
review-ietf-avtcore-srtp-encrypted-header-ext-04-secdir-lc-kelly-2013-01-25-00

Request Review of draft-ietf-avtcore-srtp-encrypted-header-ext
Requested rev. no specific revision (document currently at 05)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2013-01-17
Requested 2013-01-10
Draft last updated 2013-01-25
Completed reviews Genart Last Call review of -04 by Martin Thomson (diff)
Genart Telechat review of -04 by Martin Thomson (diff)
Secdir Last Call review of -04 by Scott Kelly (diff)
Assignment Reviewer Scott Kelly
State Completed
Review review-ietf-avtcore-srtp-encrypted-header-ext-04-secdir-lc-kelly-2013-01-25
Reviewed rev. 04 (document currently at 05)
Review result Ready
Review completed: 2013-01-25

Review
review-ietf-avtcore-srtp-encrypted-header-ext-04-secdir-lc-kelly-2013-01-25

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 a modification to the SRTP protocol, wherein header fields which have previously only been protected with authentication may now also be protected with (authenticated) encryption. The document is detailed and well-written, and the document text, together with the security considerations section, seems to address all relevant concerns.

I want to qualify my comments: I had relatively short notice for this document review, I have no prior experience with SRTP, and I have been very busy with post-Holiday catch-up, so I have to apologize for not giving this document more attention. On the other hand, there are a number of highly respected reviewers mentioned in the acknowledgements section, so I think odds are good that this document raises no serious concerns.

--Scott