[MMUSIC] RFC 6871 on Session Description Protocol (SDP) Media Capabilities Negotiation

rfc-editor@rfc-editor.org Wed, 27 February 2013 19:35 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34AE021F8AFE; Wed, 27 Feb 2013 11:35:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.031
X-Spam-Level:
X-Spam-Status: No, score=-102.031 tagged_above=-999 required=5 tests=[AWL=-0.031, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yr6bUWIp1jHn; Wed, 27 Feb 2013 11:35:58 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:126c::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id C968021F8AC8; Wed, 27 Feb 2013 11:35:58 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 58A0C72E14C; Wed, 27 Feb 2013 11:34:42 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130227193442.58A0C72E14C@rfc-editor.org>
Date: Wed, 27 Feb 2013 11:34:42 -0800
Cc: mmusic@ietf.org, rfc-editor@rfc-editor.org
Subject: [MMUSIC] RFC 6871 on Session Description Protocol (SDP) Media Capabilities Negotiation
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 19:35:59 -0000

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

        
        RFC 6871

        Title:      Session Description Protocol (SDP) Media 
                    Capabilities Negotiation 
        Author:     R. Gilman, R. Even,
                    F. Andreasen
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2013
        Mailbox:    bob_gilman@comcast.net, 
                    roni.even@mail01.huawei.com, 
                    fandreas@cisco.com
        Pages:      55
        Characters: 124829
        Updates:    RFC5939

        I-D Tag:    draft-ietf-mmusic-sdp-media-capabilities-17.txt

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

Session Description Protocol (SDP) capability negotiation provides a
general framework for indicating and negotiating capabilities in SDP.
The base framework defines only capabilities for negotiating
transport protocols and attributes.  This documents extends the
framework by defining media capabilities that can be used to
negotiate media types and their associated parameters.

This document updates the IANA Considerations of RFC 5939.

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

This is now a Proposed Standard.

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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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