RFC 8860 on Sending Multiple Types of Media in a Single RTP Session
rfc-editor@rfc-editor.org Tue, 19 January 2021 00:46 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 352803A1037; Mon, 18 Jan 2021 16:46:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 2jbYL5ayWayO; Mon, 18 Jan 2021 16:46:39 -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 318103A0FCD; Mon, 18 Jan 2021 16:46:38 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B4709F407B3; Mon, 18 Jan 2021 16:46:22 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8860 on Sending Multiple Types of Media in a Single RTP Session
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, avt@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210119004622.B4709F407B3@rfc-editor.org>
Date: Mon, 18 Jan 2021 16:46:22 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/OxaZu4rTgGTwJ8ytktYUIFyN76Y>
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 00:46:48 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8860
Title: Sending Multiple Types of Media
in a Single RTP Session
Author: M. Westerlund,
C. Perkins,
J. Lennox
Status: Standards Track
Stream: IETF
Date: January 2021
Mailbox: magnus.westerlund@ericsson.com,
csp@csperkins.org,
jonathan.lennox@8x8.com
Pages: 15
Updates: RFC 3550, RFC 3551
I-D Tag: draft-ietf-avtcore-multi-media-rtp-session-13.txt
URL: https://www.rfc-editor.org/info/rfc8860
DOI: 10.17487/RFC8860
This document specifies how an RTP session can contain RTP streams
with media from multiple media types such as audio, video, and text.
This has been restricted by the RTP specifications (RFCs 3550 and
3551), and thus this document updates RFCs 3550 and 3551 to enable
this behaviour for applications that satisfy the applicability for
using multiple media types in a single RTP session.
This document is a product of the Audio/Video Transport Core Maintenance 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