RFC 5888 on The Session Description Protocol (SDP) Grouping Framework

rfc-editor@rfc-editor.org Fri, 11 June 2010 23:24 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 [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 65E2A28C156; Fri, 11 Jun 2010 16:24:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.621
X-Spam-Level:
X-Spam-Status: No, score=-1.621 tagged_above=-999 required=5 tests=[AWL=0.379, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ctr-lkT+24fY; Fri, 11 Jun 2010 16:24:26 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id CE18228C198; Fri, 11 Jun 2010 16:24:25 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id DC6B3E06B8; Fri, 11 Jun 2010 16:24:28 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5888 on The Session Description Protocol (SDP) Grouping Framework
From: rfc-editor@rfc-editor.org
Message-Id: <20100611232428.DC6B3E06B8@rfc-editor.org>
Date: Fri, 11 Jun 2010 16:24:28 -0700
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: Fri, 11 Jun 2010 23:24:27 -0000

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

        
        RFC 5888

        Title:      The Session Description Protocol (SDP) 
                    Grouping Framework 
        Author:     G. Camarillo, H. Schulzrinne
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2010
        Mailbox:    Gonzalo.Camarillo@ericsson.com, 
                    schulzrinne@cs.columbia.edu
        Pages:      21
        Characters: 43924
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mmusic-rfc3388bis-04.txt

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

In this specification, we define a framework to group "m" lines in
the Session Description Protocol (SDP) for different purposes.  This
framework uses the "group" and "mid" SDP attributes, both of which
are defined in this specification.  Additionally, we specify how to
use the framework for two different purposes: for lip synchronization
and for receiving a media flow consisting of several media streams on
different transport addresses.  This document obsoletes RFC 3388.
[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
  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