RFC 8846 on An XML Schema for the Controlling Multiple Streams for Telepresence (CLUE) Data Model
rfc-editor@rfc-editor.org Mon, 18 January 2021 21:33 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 356C13A0D6F; Mon, 18 Jan 2021 13:33:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 th94-ZmuBL5Y; Mon, 18 Jan 2021 13:33:04 -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 CDFD53A0D66; Mon, 18 Jan 2021 13:32:49 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 92E2BF40776; Mon, 18 Jan 2021 13:32:34 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8846 on An XML Schema for the Controlling Multiple Streams for Telepresence (CLUE) Data Model
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: <20210118213234.92E2BF40776@rfc-editor.org>
Date: Mon, 18 Jan 2021 13:32:34 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/dXb2Zp2X5GCJHqIUtpJBqqbEVBw>
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: Mon, 18 Jan 2021 21:33:11 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8846
Title: An XML Schema for the Controlling Multiple Streams
for Telepresence (CLUE) Data Model
Author: R. Presta,
S P. Romano
Status: Standards Track
Stream: IETF
Date: January 2020
Mailbox: roberta.presta@unina.it,
spromano@unina.it
Pages: 66
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-clue-data-model-schema-17.txt
URL: https://www.rfc-editor.org/info/rfc8846
DOI: 10.17487/RFC8846
This document provides an XML schema file for the definition of CLUE
data model types. The term "CLUE" stands for "Controlling Multiple
Streams for Telepresence" and is the name of the IETF working group
in which this document, as well as other companion documents, has
been developed. The document defines a coherent structure for
information associated with the description of a telepresence
scenario.
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