[rtcweb] RFC 8834 on Media Transport and Use of RTP in WebRTC
rfc-editor@rfc-editor.org Mon, 18 January 2021 23:31 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5483C3A14FC; Mon, 18 Jan 2021 15:31:10 -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 svMaqpMLXpmw; Mon, 18 Jan 2021 15:31:09 -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 C32123A113A; Mon, 18 Jan 2021 15:30:13 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 83008F4079C; Mon, 18 Jan 2021 15:29:58 -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, rtcweb@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210118232958.83008F4079C@rfc-editor.org>
Date: Mon, 18 Jan 2021 15:29:58 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/yO4FQdozNYc3QAMfphqnP8hQyc0>
Subject: [rtcweb] RFC 8834 on Media Transport and Use of RTP in WebRTC
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jan 2021 23:31:17 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8834
Title: Media Transport and Use of RTP in WebRTC
Author: C. Perkins,
M. Westerlund,
J. Ott
Status: Standards Track
Stream: IETF
Date: January 2021
Mailbox: csp@csperkins.org,
magnus.westerlund@ericsson.com,
ott@in.tum.de
Pages: 39
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-rtcweb-rtp-usage-26.txt
URL: https://www.rfc-editor.org/info/rfc8834
DOI: 10.17487/RFC8834
The framework for Web Real-Time Communication (WebRTC) provides
support for direct interactive rich communication using audio, video,
text, collaboration, games, etc. between two peers' web browsers.
This memo describes the media transport aspects of the WebRTC
framework. It specifies how the Real-time Transport Protocol (RTP) is
used in the WebRTC context and gives requirements for which RTP
features, profiles, and extensions need to be supported.
This document is a product of the Real-Time Communication in WEB-browsers 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