<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-avt-srtp-not-mandatory" target="https://datatracker.ietf.org/doc/html/draft-ietf-avt-srtp-not-mandatory-16">
   <front>
      <title>Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution</title>
      <author initials="C." surname="Perkins" fullname="Colin Perkins">
         <organization>University of Glasgow</organization>
      </author>
      <author initials="M." surname="Westerlund" fullname="Magnus Westerlund">
         <organization>Ericsson</organization>
      </author>
      <date month="January" day="16" year="2014" />
      <abstract>
	 <t>This memo discusses the problem of securing real-time multimedia sessions.  It also explains why the Real-time Transport Protocol (RTP) and the associated RTP Control Protocol (RTCP) do not mandate a single media security mechanism.  This is relevant for designers and reviewers of future RTP extensions to ensure that appropriate security mechanisms are mandated and that any such mechanisms are specified in a manner that conforms with the RTP architecture.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-avt-srtp-not-mandatory-16" />
   
</reference>
