[AVTCORE] RFC 8872 on Guidelines for Using the Multiplexing Features of RTP to Support Multiple Media Streams
rfc-editor@rfc-editor.org Tue, 19 January 2021 00:47 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC0F83A11FF; Mon, 18 Jan 2021 16:47:39 -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 o-cSbhsiT6ca; Mon, 18 Jan 2021 16:47:38 -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 867DD3A114C; Mon, 18 Jan 2021 16:47:23 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B343CF407BE; Mon, 18 Jan 2021 16:47:07 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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: <20210119004707.B343CF407BE@rfc-editor.org>
Date: Mon, 18 Jan 2021 16:47:07 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/ytrhPzZk3IydvZ820wIap6CC20U>
Subject: [AVTCORE] RFC 8872 on Guidelines for Using the Multiplexing Features of RTP to Support Multiple Media Streams
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jan 2021 00:47:46 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8872
Title: Guidelines for Using the Multiplexing Features
of RTP to Support Multiple Media Streams
Author: M. Westerlund,
B. Burman,
C. Perkins,
H. Alvestrand,
R. Even
Status: Informational
Stream: IETF
Date: January 2021
Mailbox: magnus.westerlund@ericsson.com,
bo.burman@ericsson.com,
csp@csperkins.org,
harald@alvestrand.no,
ron.even.tlv@gmail.com
Pages: 36
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-avtcore-multiplex-guidelines-12.txt
URL: https://www.rfc-editor.org/info/rfc8872
DOI: 10.17487/RFC8872
The Real-time Transport Protocol (RTP) is a flexible protocol that
can be used in a wide range of applications, networks, and system
topologies. That flexibility makes for wide applicability but can
complicate the application design process. One particular design
question that has received much attention is how to support multiple
media streams in RTP. This memo discusses the available options and
design trade-offs, and provides guidelines on how to use the
multiplexing features of RTP to support multiple media streams.
This document is a product of the Audio/Video Transport Core Maintenance Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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