[rfc-dist] Correction: RFC 8847 on Protocol for Controlling Multiple Streams for Telepresence (CLUE)
rfc-editor@rfc-editor.org Tue, 19 January 2021 01:41 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54B543A1451 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 18 Jan 2021 17:41:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 7umCCHfTGlAV for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 18 Jan 2021 17:41: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 C058A3A1207 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon, 18 Jan 2021 17:40:54 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 92F1FF40821; Mon, 18 Jan 2021 17:39:14 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 1BECFF4081F; Mon, 18 Jan 2021 17:39:13 -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
Message-Id: <20210119013913.1BECFF4081F@rfc-editor.org>
Date: Mon, 18 Jan 2021 17:39:13 -0800
Subject: [rfc-dist] Correction: RFC 8847 on Protocol for Controlling Multiple Streams for Telepresence (CLUE)
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, clue@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
[Year corrected to "2021" below.]
A new Request for Comments is now available in online RFC libraries.
RFC 8847
Title: Protocol for Controlling Multiple Streams
for Telepresence (CLUE)
Author: R. Presta,
S P. Romano
Status: Experimental
Stream: IETF
Date: January 2021
Mailbox: roberta.presta@unina.it,
spromano@unina.it
Pages: 62
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-clue-protocol-19.txt
URL: https://www.rfc-editor.org/info/rfc8847
DOI: 10.17487/RFC8847
The Controlling Multiple Streams for Telepresence (CLUE) protocol is
an application protocol conceived for the description and negotiation
of a telepresence session. The design of the CLUE protocol takes
into account the requirements and the framework defined within the
IETF CLUE Working Group. A companion document, RFC 8848, delves into
CLUE signaling details as well as the SIP / Session Description
Protocol (SDP) session establishment phase. CLUE messages flow over
the CLUE data channel, based on reliable and ordered SCTP-over-DTLS
transport. ("SCTP" stands for "Stream Control Transmission
Protocol".) Message details, together with the behavior of CLUE
Participants acting as Media Providers and/or Media Consumers, are
herein discussed.
This document is a product of the ControLling mUltiple streams for tElepresence Working Group of the IETF.
EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community. It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
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
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org