Re: [dispatch] Media Stream related signaling

Harald Alvestrand <harald@alvestrand.no> Fri, 27 January 2012 08:42 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBDD221F8566 for <dispatch@ietfa.amsl.com>; Fri, 27 Jan 2012 00:42:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.074
X-Spam-Level:
X-Spam-Status: No, score=-110.074 tagged_above=-999 required=5 tests=[AWL=-0.074, BAYES_00=-2.599, J_CHICKENPOX_26=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7frNz4TyDsVe for <dispatch@ietfa.amsl.com>; Fri, 27 Jan 2012 00:42:06 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id CA09221F8562 for <dispatch@ietf.org>; Fri, 27 Jan 2012 00:42:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 9B8A339E0FA; Fri, 27 Jan 2012 09:42:04 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KxREoOENT-Vf; Fri, 27 Jan 2012 09:42:03 +0100 (CET)
Received: from [192.168.0.14] (c213-89-141-213.bredband.comhem.se [213.89.141.213]) by eikenes.alvestrand.no (Postfix) with ESMTPS id C697539E0BE; Fri, 27 Jan 2012 09:42:03 +0100 (CET)
Message-ID: <4F22635B.1030708@alvestrand.no>
Date: Fri, 27 Jan 2012 09:42:03 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111124 Thunderbird/8.0
MIME-Version: 1.0
To: Bo Burman <bo.burman@ericsson.com>
References: <05F760EF51FA6A4F804F9759C239313A3271BADD0B@ESESSCMS0361.eemea.ericsson.se>
In-Reply-To: <05F760EF51FA6A4F804F9759C239313A3271BADD0B@ESESSCMS0361.eemea.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: "dispatch@ietf.org" <dispatch@ietf.org>
Subject: Re: [dispatch] Media Stream related signaling
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jan 2012 08:42:07 -0000

Note - a related draft is this one (expired):

draft-lennox-mmusic-sdp-source-selection-02.txt

It proposes an SDP-based mechanism for turning streams on and off.
This subject has also been discussed in RTCWEB, and may also be in scope 
for CLUE.

           Harald


On 01/23/2012 04:50 PM, Bo Burman wrote:
> Dispatch,
>
> We have requested agenda time for the upcoming meeting to discuss the subject of Media Stream related signaling. From the feedback we got in AVTEXT WG on the discussion for a certain problem, the one related to pausing and resuming sender to middlebox media traffic, it is clear that a more high level discussion needs to happen.
>
> We have two Internet drafts related to the issues we would like to discuss.
> Media Stream Selection (MESS)
>   - draft-westerlund-dispatch-stream-selection-00
> RTP Media Stream Pause and Resume
>   - draft-westerlund-avtext-rtp-stream-pause-00
>
> The first one (MESS) proposes that for the general selection of media streams, an end-point within a centralized conferencing scenario desires to receive a media plane oriented rather than RTP/RTCP based signaling, which appears to have benefits as discussed in the draft.
>
> As mentioned, the pause resume draft is targeted for a different use case where a media plane solution has potential for other benefits. This was discussed and the main outcome of that discussion was three quite different opinions;
>
> a) We already do this signaling using TMMBR (RFC 5104) by setting the bit-rate value to 0, which the current specs doesn't allow.
>
> b) This should be done in signalling plane, RTP/RTCP shouldn't be bloated. (But I did interpret this as not necessarily needing to be SIP).
>
> c) When it comes to pause/resume, unless it is done using SIP/SDP it will not work through any Session Border Gateway as the session will be torn down after n seconds.
>
> Thus I think it important that we take a discussion around the use cases, existing solutions, limitations in those or the proposal to try to determine what is the most reasonable way of solving the problems and how to enable;
>
> 1) Receiver based selection of media streams from a larger set of streams, including different quality levels like video resolutions, in a centralized conferencing application.
>
> 2) Optimize the transport so that media streams currently not used can be turned off temporarily and then quickly resumed when someone determines a need for the media stream. For example using mechanism (1) but also for voice activity based, centrally controlled or other mechanisms to select which media streams are delivered to other session participants.
>
> We are working to revise our Internet drafts. We seek as much input as possible into this prior to the meeting so that we can ensure that any discussion are as on topic and focused as possible.
>
> Regards
>
> Bo Burman&  Magnus Westerlund
>
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  +46 10 7141311
> Färögatan 6                | Mobile +46 73 0949021
> SE-164 80 Stockholm, Sweden| mailto: bo.burman at ericsson.com
> ----------------------------------------------------------------------
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>