<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-avtcore-rtp-security-options" target="https://datatracker.ietf.org/doc/html/draft-ietf-avtcore-rtp-security-options-02">
   <front>
      <title>Options for Securing RTP Sessions</title>
      <author initials="M." surname="Westerlund" fullname="Magnus Westerlund">
         </author>
      <author initials="C." surname="Perkins" fullname="Colin Perkins">
         </author>
      <date month="February" day="25" year="2013" />
      <abstract>
	 <t>   The Real-time Transport Protocol (RTP) is used in a large number of
   different application domains and environments.  This heterogeneity
   implies that different security mechanisms are needed to provide
   services such as confidentiality, integrity and source authentication
   of RTP/RTCP packets suitable for the various environments.  The range
   of solutions makes it difficult for RTP-based application developers
   to pick the most suitable mechanism.  This document provides an
   overview of a number of security solutions for RTP, and gives
   guidance for developers on how to choose the appropriate security
   mechanism.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-avtcore-rtp-security-options-02" />
   
</reference>
