RFC 8843 on Negotiating Media Multiplexing Using the Session Description Protocol (SDP)

rfc-editor@rfc-editor.org Thu, 21 January 2021 00:32 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id DD1593A163C; Wed, 20 Jan 2021 16:32:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id cB1854jt12sk; Wed, 20 Jan 2021 16:32:38 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C23603A1236; Wed, 20 Jan 2021 16:32:15 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 86441F4071F; Wed, 20 Jan 2021 16:31:58 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8843 on Negotiating Media Multiplexing Using the Session Description Protocol (SDP)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, mmusic@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210121003158.86441F4071F@rfc-editor.org>
Date: Wed, 20 Jan 2021 16:31:58 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/XudQiopYmmLwd1ejvBkL8D5jUqI>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Thu, 21 Jan 2021 00:32:40 -0000

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

        RFC 8843

        Title:      Negotiating Media Multiplexing Using 
                    the Session Description Protocol (SDP) 
        Author:     C. Holmberg,
                    H. Alvestrand,
                    C. Jennings
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    christer.holmberg@ericsson.com,
        Pages:      50
        Updates:    RFC 3264, RFC 5888, RFC 7941

        I-D Tag:    draft-ietf-mmusic-sdp-bundle-negotiation-54.txt

        URL:        https://www.rfc-editor.org/info/rfc8843

        DOI:        10.17487/RFC8843

This specification defines a new Session Description Protocol (SDP)
Grouping Framework extension called 'BUNDLE'. The extension can be
used with the SDP offer/answer mechanism to negotiate the usage of a
single transport (5-tuple) for sending and receiving media described
by multiple SDP media descriptions ("m=" sections). Such transport is
referred to as a BUNDLE transport, and the media is referred to as
bundled media. The "m=" sections that use the BUNDLE transport form a
BUNDLE group. 

This specification defines a new RTP Control Protocol (RTCP) Source
Description (SDES) item and a new RTP header extension.

This specification updates RFCs 3264, 5888, and 7941.

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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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 https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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