[clue] RFC 8847 on Protocol for Controlling Multiple Streams for Telepresence (CLUE)
rfc-editor@rfc-editor.org Mon, 18 January 2021 21:33 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DDCF3A0D6F; Mon, 18 Jan 2021 13:33:11 -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 6SVv3phiVFxA; Mon, 18 Jan 2021 13:33: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 72C163A0FEB; Mon, 18 Jan 2021 13:32:54 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 9D6F1F40776; Mon, 18 Jan 2021 13:32:38 -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, clue@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210118213238.9D6F1F40776@rfc-editor.org>
Date: Mon, 18 Jan 2021 13:32:38 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/fZp4Ds2_wjdRiYmy638ky93w57Q>
Subject: [clue] RFC 8847 on Protocol for Controlling Multiple Streams for Telepresence (CLUE)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jan 2021 21:33:17 -0000
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 2020
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