RFC 8853 on Using Simulcast in Session Description Protocol (SDP) and RTP Sessions

rfc-editor@rfc-editor.org Tue, 19 January 2021 22:54 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61EA13A190F; Tue, 19 Jan 2021 14:54:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9PSPaU2yJlQ3; Tue, 19 Jan 2021 14:54:43 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C77A33A1912; Tue, 19 Jan 2021 14:54:27 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 97FF3F4076D; Tue, 19 Jan 2021 14:54:11 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg4NTMgb24gVXNpbmcgU2ltdWxjYXN0IGluIFNlc3Npb24gRGVzY3JpcHRpb24gUHJvdG9jb2wgKFNEUCkgYW5kIFJUUCBTZXNzaW9ucw==?=
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: <20210119225411.97FF3F4076D@rfc-editor.org>
Date: Tue, 19 Jan 2021 14:54:11 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/hz1TgrThOARoAa_LzgRuFcWRYFk>
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: Tue, 19 Jan 2021 22:54:52 -0000

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

        
        RFC 8853

        Title:      Using Simulcast in Session Description 
                    Protocol (SDP) and RTP Sessions 
        Author:     B. Burman,
                    M. Westerlund,
                    S. Nandakumar,
                    M. Zanaty
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    bo.burman@ericsson.com,
                    magnus.westerlund@ericsson.com,
                    snandaku@cisco.com,
                    mzanaty@cisco.com
        Pages:      30
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mmusic-sdp-simulcast-14.txt

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

        DOI:        10.17487/RFC8853

In some application scenarios, it may be desirable to send multiple
differently encoded versions of the same media source in different
RTP streams. This is called simulcast. This document describes how to
accomplish simulcast in RTP and how to signal it in the Session
Description Protocol (SDP).  The described solution uses an RTP/RTCP
identification method to identify RTP streams belonging to the same
media source and makes an extension to SDP to indicate that those RTP
streams are different simulcast formats of that media source. The SDP
extension consists of a new media-level SDP attribute that expresses
capability to send and/or receive simulcast RTP streams.

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

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