[clue] Correction: RFC 8850 on Controlling Multiple Streams for Telepresence (CLUE) Protocol Data Channel

rfc-editor@rfc-editor.org Tue, 19 January 2021 01:39 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 0611F3A1183; Mon, 18 Jan 2021 17:39:47 -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 plf3gryysJ-a; Mon, 18 Jan 2021 17:39:45 -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 43A8E3A10BC; Mon, 18 Jan 2021 17:39:37 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id D7CF1F407DC; Mon, 18 Jan 2021 17:39:21 -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: <20210119013921.D7CF1F407DC@rfc-editor.org>
Date: Mon, 18 Jan 2021 17:39:21 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/Yzvo-KC_Fgc3wg43dD8btNHqy70>
Subject: [clue] =?utf-8?q?Correction=3A_RFC_8850_on_Controlling_Multiple_?= =?utf-8?q?Streams_for_Telepresence_=28CLUE=29_Protocol_Data_Channel?=
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: Tue, 19 Jan 2021 01:39:53 -0000

[Year corrected to "2021" below.]

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


       RFC 8850

       Title:      Controlling Multiple Streams for Telepresence (CLUE)
                   Protocol Data Channel 
       Author:     C. Holmberg
       Status:     Experimental
       Stream:     IETF
       Date:       January 2021
       Mailbox:    christer.holmberg@ericsson.com
       Pages:      9
       Updates/Obsoletes/SeeAlso:   None

       I-D Tag:    draft-ietf-clue-datachannel-18.txt

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

       DOI:        10.17487/RFC8850

This document defines how to use the WebRTC data channel mechanism to
realize a data channel, referred to as a Controlling Multiple Streams
for Telepresence (CLUE) data channel, for transporting CLUE protocol
messages between two CLUE entities.

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