<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-mmusic-sdp-capability-negotiation-reqts" target="https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-sdp-capability-negotiation-reqts-01">
   <front>
      <title>SDP Capability Negotiation: Requirements and Review of Existing Work</title>
      <author initials="F." surname="Andreasen" fullname="Flemming Andreasen">
         <organization>Cisco Systems</organization>
      </author>
      <date month="March" day="6" year="2007" />
      <abstract>
	 <t>   The Session Description Protocol (SDP) was intended for describing 
   multimedia sessions for the purposes of session announcement, session 
   invitation, and other forms of multimedia session initiation. SDP was 
   not intended to provide capability indication or capability 
   negotiation, however over the years, SDP has seen widespread adoption 
   and as a result it has been gradually extended to provide limited 
   support for these. SDP and its current extensions however do not 
   have, for example, the ability to negotiate one or more alternative 
   transport protocols (e.g. RTP profiles) which makes it particularly 
   difficult to deploy new RTP profiles such as secure RTP and RTP with 
   RTCP-based feedback. The purpose of this document is to identify a 
   set of requirements for SDP Capability Negotiation and evaluate 
   existing work in this area. The document does not provide any 
   solutions to SDP Capability Negotiation 

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-mmusic-sdp-capability-negotiation-reqts-01" />
   
</reference>
