RFC 5939 on Session Description Protocol (SDP) Capability Negotiation

rfc-editor@rfc-editor.org Tue, 14 September 2010 19:37 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 07E2D3A6B14; Tue, 14 Sep 2010 12:37:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.886
X-Spam-Status: No, score=-102.886 tagged_above=-999 required=5 tests=[AWL=1.115, BAYES_00=-2.599, GB_I_INVITATION=-2, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id YR+aeceOdFCJ; Tue, 14 Sep 2010 12:37:51 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id E45913A6AC5; Tue, 14 Sep 2010 12:37:41 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B4F2EE06DE; Tue, 14 Sep 2010 12:38:07 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5939 on Session Description Protocol (SDP) Capability Negotiation
From: rfc-editor@rfc-editor.org
Message-Id: <20100914193807.B4F2EE06DE@rfc-editor.org>
Date: Tue, 14 Sep 2010 12:38:07 -0700 (PDT)
Cc: mmusic@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Sep 2010 19:37:53 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 5939

        Title:      Session Description Protocol (SDP) Capability 
        Author:     F. Andreasen
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2010
        Mailbox:    fandreas@cisco.com
        Pages:      77
        Characters: 188116
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mmusic-sdp-capability-negotiation-13.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5939.txt

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.

The purpose of this document is to address these shortcomings by
extending SDP with capability negotiation parameters and associated
offer/answer procedures to use those parameters in a backwards
compatible manner.

The document defines a general SDP Capability Negotiation framework.
It also specifies how to provide attributes and transport protocols
as capabilities and negotiate them using the framework.  Extensions
for other types of capabilities (e.g., media types and media formats)
may be provided in other documents.  [STANDARDS TRACK]

This document is a product of the Multiparty Multimedia Session Control Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC