Correction: RFC 8848 on Session Signaling for Controlling Multiple Streams for Telepresence (CLUE)
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 E8C183A10E3; Mon, 18 Jan 2021 17:39:41 -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=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 lKJkdL83z645; Mon, 18 Jan 2021 17:39:40 -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 015483A1083; Mon, 18 Jan 2021 17:39:32 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 1A3D8F40828; Mon, 18 Jan 2021 17:39:15 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: Correction: RFC 8848 on Session Signaling for Controlling Multiple Streams for Telepresence (CLUE)
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: <20210119013915.1A3D8F40828@rfc-editor.org>
Date: Mon, 18 Jan 2021 17:39:15 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/h1ehwMqxoag_AJ2n9lbaz6TzdKQ>
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:48 -0000
[Year corrected to "2021" below.]
A new Request for Comments is now available in online RFC libraries.
RFC 8848
Title: Session Signaling for Controlling Multiple
Streams for Telepresence (CLUE)
Author: R. Hanton,
P. Kyzivat,
L. Xiao,
C. Groves
Status: Experimental
Stream: IETF
Date: January 2021
Mailbox: rohanse2@cisco.com,
pkyzivat@alum.mit.edu,
lennard.xiao@outlook.com,
cngroves.std@gmail.com
Pages: 29
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-clue-signaling-15.txt
URL: https://www.rfc-editor.org/info/rfc8848
DOI: 10.17487/RFC8848
This document is about Controlling Multiple Streams for Telepresence
(CLUE) signaling. It specifies how the CLUE protocol and the CLUE
data channel are used in conjunction with each other and with
existing signaling mechanisms, such as SIP and the Session
Description Protocol (SDP), to produce a telepresence call.
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