datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

Session Description Protocol (SDP) Capability Negotiation
draft-ietf-mmusic-sdp-capability-negotiation-13

RFC
Document Stream: IETF
Last updated: 2010-03-25
Replaces: draft-andreasen-mmusic-sdp-capability-negotiation
Intended RFC status: Proposed Standard
Other versions: (expired, archived): plain text, pdf, html

IETF State: WG Document (mmusic)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 5939
IANA Action State: RFC-Ed-Ack 
Responsible AD: Robert Sparks
Send notices to: mmusic-chairs@tools.ietf.org, draft-ietf-mmusic-sdp-capability-negotiation@tools.ietf.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-mmusic-sdp-capability-negotiation.

Abstract:
The Session Description Protocol (SDP) was intended to describe 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, notably in the form of the offer/answer model defined in RFC 3264. SDP does not define how to negotiate one or more alternative transport protocols (e.g., RTP profiles) or attributes. This makes it difficult to deploy new RTP profiles such as Secure RTP or RTP with RTCP-based feedback, negotiate use of different security keying mechanisms, etc. It also presents problems for some forms of media negotiation.

Authors:
Flemming Andreasen <fandreas@cisco.com>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)