The IESG has received a request from the Audio/Video Transport Core Maintenance WG (avtcore) to consider the following document: - 'Securing the RTP Protocol Framework: Why RTP Does Not Mandate a Single Media Security Solution' <draft-ietf-avt-srtp-not-mandatory-14.txt> as Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2013-12-06. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This memo discusses the problem of securing real-time multimedia sessions, and explains why the Real-time Transport Protocol (RTP), and the associated RTP Control Protocol (RTCP), do not mandate a single media security mechanism. Guidelines for designers and reviewers of future RTP extensions are provided, to ensure that appropriate security mechanisms are mandated, and that any such mechanisms are specified in a manner that conforms with the RTP architecture. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-avt-srtp-not-mandatory/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-avt-srtp-not-mandatory/ballot/ No IPR declarations have been submitted directly on this I-D.
