[AVT] Review of draft-ietf-avt-profile-savpf-11

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 does not say whether it is intended to be on the Standards
Track, Informational, etcetera.  I assume it is intended to be on the
Standards Track.

Although some of the text in this document is somewhat confusing, has a
number of grammatical and other editing errors, and in many places fails
to expand acronyms, it is a simple profile of SRTP.  The security
considerations section covers all the areas that I think needed to be
covered, except, perhaps, two things.

In section 3.4 example #2 contains symmetric key material which, as the
description correctly states, requires confidentiality protection by
whatever channel is used to obtain the given session description.  Other
examples, such as example #1, might require at least integrity
protection, but this is not discussed.  It may be that they do not
require integrity protection, but I can't tell as I'm not an expert in
MIKEY (which was used in the example) and, in any case, other key
management frameworks can be used and some might require at least
integrity protection.  For example, when unauthenticated DH key
exchanges are used I would expect integrity protection by some other
channel to be required in order to prevent MITM attacks.  A small amount
of text should cover this case.

Additionally, it's not clear to me whether whether there are any
attributes of an SDP besides a=key-mgmt: and a=crypto: which might need
integrity and even confidentiality protection.  Additional text about
this would be good.

Nico
-- 

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt