Protocol Action: 'Framework for Telepresence Multi-Streams' to Proposed Standard (draft-ietf-clue-framework-25.txt)

The IESG <> Thu, 14 January 2016 17:10 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 757EA1A21C2; Thu, 14 Jan 2016 09:10:28 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Protocol Action: 'Framework for Telepresence Multi-Streams' to Proposed Standard (draft-ietf-clue-framework-25.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.12.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Thu, 14 Jan 2016 09:10:28 -0800
Archived-At: <>
Cc:,,, The IESG <>,,,
X-Mailman-Version: 2.1.15
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 14 Jan 2016 17:10:28 -0000

The IESG has approved the following document:
- 'Framework for Telepresence Multi-Streams'
  (draft-ietf-clue-framework-25.txt) as Proposed Standard

This document is the product of the ControLling mUltiple streams for
tElepresence Working Group.

The IESG contact persons are Ben Campbell, Barry Leiba and Alissa Cooper.

A URL of this Internet Draft is:

Technical Summary:
This document defines a framework for a protocol to enable devices in a 
telepresence conference to interoperate.  The protocol enables 
communication of information about multiple media streams so a sending 
system and receiving system can make reasonable decisions about 
transmitting, selecting and rendering the media streams. This protocol 
is used in addition to SIP signaling and SDP negotiation for setting up 
a telepresence session.

Working Group Summary:
Was there anything in WG process that is worth noting? For example, was 
there controversy about particular points or were there decisions where 
the consensus was particularly rough?

The document was discussed in the meeting, in conferences calls and on 
the mailing list. The open issues were addressed and there are no open 
issues, there was consensus on the content of the document.

Document Quality:
The actual protocol using the attributes defined in the network is 
almost done, it is aligned with this document and there is an 
implementation of the protocol. There are no specific reviews that need 
to be mentioned.

Roni Even is the Document Shepherd.
The responsible AD is Alissa Cooper.