Last Call Review of draft-ietf-avtcore-5761-update-01
review-ietf-avtcore-5761-update-01-secdir-lc-kelly-2016-09-22-00

Request Review of draft-ietf-avtcore-5761-update
Requested rev. no specific revision (document currently at 06)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2016-09-22
Requested 2016-09-15
Other Reviews Genart Last Call review of -02 by Elwyn Davies (diff)
Genart Telechat review of -05 by Elwyn Davies (diff)
Opsdir Last Call review of -01 by Rick Casarez (diff)
Review State Completed
Reviewer Scott Kelly
Review review-ietf-avtcore-5761-update-01-secdir-lc-kelly-2016-09-22
Posted at https://www.ietf.org/mail-archive/web/secdir/current/msg06810.html
Reviewed rev. 01 (document currently at 06)
Review result Ready
Draft last updated 2016-09-22
Review completed: 2016-09-22

Review
review-ietf-avtcore-5761-update-01-secdir-lc-kelly-2016-09-22

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.

From the abstract:

   This document updates RFC 5761 by clarifying the SDP offer/answer
   negotiation of RTP and RTCP multiplexing.  It makes it clear that an
   answerer can only include an "a=rtcp-mux" attribute in an SDP answer
   if the associated SDP offer contained the attribute.

The security considerations section says

   The security considerations for RTP and RTCP multiplexing are
   described in RFC 5761.  This specification does not impact those
   security considerations.

I agree, I see no new security issues with this draft.