Last Call: <draft-ietf-clue-datachannel-13.txt> (CLUE Protocol data channel) to Proposed Standard

The IESG <> Thu, 07 July 2016 21:56 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (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 <>
To: "IETF-Announce" <>
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: <>
Message-ID: <>
Date: Thu, 07 Jul 2016 14:56:20 -0700
Archived-At: <>
X-Mailman-Version: 2.1.17
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-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 mailing lists by 2016-07-21. Exceptionally, comments may be
sent to instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   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

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.