Correction: RFC 8845 on Framework for Telepresence Multi-Streams

rfc-editor@rfc-editor.org Tue, 19 January 2021 01:39 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 EE02F3A1158; Mon, 18 Jan 2021 17:39:29 -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 AeFfBcDM2rux; Mon, 18 Jan 2021 17:39:28 -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 80E733A0F4A; Mon, 18 Jan 2021 17:39:24 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 22D80F4080C; Mon, 18 Jan 2021 17:39:09 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?Q29ycmVjdGlvbjogUkZDIDg4NDUgb24gRnJhbWV3b3JrIGZvciBUZWxlcHJlc2VuY2UgTXVsdGktU3RyZWFtcw==?=
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: <20210119013909.22D80F4080C@rfc-editor.org>
Date: Mon, 18 Jan 2021 17:39:09 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/7CI6wSvqXTACHtJrHy0TglrXGwM>
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 01:39:36 -0000

[Year corrected to "2021" below.]

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


       RFC 8845

       Title:      Framework for Telepresence Multi-Streams 
       Author:     M. Duckworth, Ed.,
                   A. Pepperell,
                   S. Wenger
       Status:     Standards Track
       Stream:     IETF
       Date:       January 2021
       Mailbox:    mrducky73@outlook.com,
                   apeppere@gmail.com,
                   stewe@stewe.org
       Pages:      61
       Updates/Obsoletes/SeeAlso:   None

       I-D Tag:    draft-ietf-clue-framework-25.txt

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

       DOI:        10.17487/RFC8845

This document defines a framework for a protocol to enable devices in
a telepresence conference to interoperate.  The protocol enables
communication of information about multiple media streams so a
sending system and receiving system can make reasonable decisions
about transmitting, selecting, and rendering the media streams. This
protocol is used in addition to SIP signaling and Session Description
Protocol (SDP) negotiation for setting up a telepresence session.

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