Last Call: <draft-ietf-clue-datachannel-13.txt> (CLUE Protocol data channel) to Proposed Standard
The IESG <iesg-secretary@ietf.org> Thu, 07 July 2016 21:56 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3295F12D5CD; Thu, 7 Jul 2016 14:56:20 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-clue-datachannel-13.txt> (CLUE Protocol data channel) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 6.25.1
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
Message-ID: <20160707215620.18849.71255.idtracker@ietfa.amsl.com>
Date: Thu, 07 Jul 2016 14:56:20 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/tF1QtXo6qR5bZerBUwr-v2V0zQU>
Cc: clue-chairs@ietf.org, pkyzivat@cisco.com, clue@ietf.org, draft-ietf-clue-datachannel@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org
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: Thu, 07 Jul 2016 21:56:20 -0000
The IESG has received a request from the ControLling mUltiple streams for tElepresence WG (clue) to consider the following document: - 'CLUE Protocol data channel' <draft-ietf-clue-datachannel-13.txt> as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2016-07-21. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document defines how to use the WebRTC data channel mechanism in order to realize a data channel, referred to as a CLUE data channel, for transporting CLUE protocol messages between two CLUE entities. The document defines how to describe the SCTPoDTLS association used to realize the CLUE data channel using the Session Description Protocol (SDP), and defines usage of SDP-based "SCTP over DTLS" data channel negotiation mechanism for establishing a CLUE data channel. Details and procedures associated with the CLUE protocol, and the SDP Offer/Answer procedures for negotiating usage of a CLUE data channel, are outside the scope of this document. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-clue-datachannel/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-clue-datachannel/ballot/ No IPR declarations have been submitted directly on this I-D.