RFC 8849 on Mapping RTP Streams to Controlling Multiple Streams for Telepresence (CLUE) Media Captures
rfc-editor@rfc-editor.org Mon, 18 January 2021 21:33 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 C1D263A0C8F; Mon, 18 Jan 2021 13:33:27 -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 cjA6r2IbjKaY; Mon, 18 Jan 2021 13:33:25 -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 3E9733A10DB; Mon, 18 Jan 2021 13:33:04 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 0BDFEF4078E; Mon, 18 Jan 2021 13:32:49 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8849 on Mapping RTP Streams to Controlling Multiple Streams for Telepresence (CLUE) Media Captures
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, clue@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210118213249.0BDFEF4078E@rfc-editor.org>
Date: Mon, 18 Jan 2021 13:32:49 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/lRx-BaTMBsi9R-Trf0vZoNKDjsc>
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: Mon, 18 Jan 2021 21:33:34 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8849 Title: Mapping RTP Streams to Controlling Multiple Streams for Telepresence (CLUE) Media Captures Author: R. Even, J. Lennox Status: Standards Track Stream: IETF Date: January 2020 Mailbox: ron.even.tlv@gmail.com, jonathan.lennox@8x8.com Pages: 12 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-clue-rtp-mapping-14.txt URL: https://www.rfc-editor.org/info/rfc8849 DOI: 10.17487/RFC8849 This document describes how the Real-time Transport Protocol (RTP) is used in the context of the Controlling Multiple Streams for Telepresence (CLUE) protocol. It also describes the mechanisms and recommended practice for mapping RTP media streams, as defined in the Session Description Protocol (SDP), to CLUE Media Captures and defines a new RTP header extension (CaptureID). This document is a product of the ControLling mUltiple streams for tElepresence 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