Re: [AVTCORE] mufti path rtp

lingli deng <denglingli@gmail.com> Wed, 20 March 2013 04:07 UTC

Return-Path: <denglingli@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDECE21F8F1C for <avt@ietfa.amsl.com>; Tue, 19 Mar 2013 21:07:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.451
X-Spam-Level: **
X-Spam-Status: No, score=2.451 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, NO_RELAYS=-0.001]
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 D+AGwT-BH50u for <avt@ietfa.amsl.com>; Tue, 19 Mar 2013 21:06:52 -0700 (PDT)
Received: from mail-vb0-x233.google.com (mail-vb0-x233.google.com [IPv6:2607:f8b0:400c:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 18CFB21F874A for <avt@ietf.org>; Tue, 19 Mar 2013 21:06:51 -0700 (PDT)
Received: by mail-vb0-f51.google.com with SMTP id fq11so849332vbb.10 for <avt@ietf.org>; Tue, 19 Mar 2013 21:06:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=pidC7r/UJYtmURiVQ8UapMtXr8FmUEWwZFsY0gv+DY4=; b=fZD8mbkpwKyzpRwAz/6K5DKVMehSKMGUvHtHwrTjK3LlfS7L4oAXDZBb95EYziadQT t9QdeXAGxRY76+jYjm+NGnKN9YgZ3vTp0tzny7p/7cVyXBfgym6XZqEUlojey+S3YWFt LGQX0QKhjP6Cl7ict8sB0Xt4GKJY0t42GD6+zDzwO57saIO/mWfxVdop8FIx24iGnUei yyZr1h+13+OFfZWxaL22PNVy8zDnNM9mzkIlBqfW8rC2EJHosdN3HNxg2/AuDX0PPchS 54b8EGSUSB2nh0j116NOt/VGGp9Dg22zOy0Y45QRGmzS9CbeLxq0n9pqhBBnbzMOJywf 1Yqg==
MIME-Version: 1.0
X-Received: by 10.52.230.10 with SMTP id su10mr5072551vdc.50.1363752411369; Tue, 19 Mar 2013 21:06:51 -0700 (PDT)
Received: by 10.58.169.45 with HTTP; Tue, 19 Mar 2013 21:06:51 -0700 (PDT)
In-Reply-To: <-8068907073408942395@unknownmsgid>
References: <0E0F8833-99F6-46C3-A44B-FAD5EFA6A75C@gmail.com> <-8068907073408942395@unknownmsgid>
Date: Wed, 20 Mar 2013 12:06:51 +0800
Message-ID: <CAHWmbsOOafASzgKVHHTgxDGM6UrfVXZRdn+hieRdb_1R8+YM2w@mail.gmail.com>
From: lingli deng <denglingli@gmail.com>
To: Varun Singh <vsingh.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="089e0111ae300ac5ad04d8535afb"
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] mufti path rtp
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2013 04:07:01 -0000

Hi Varun,****

** **

Thank you for your sharing~****

The paper is well-written and easy to follow, to which I have the following
comments:****

** **

**1) **Firstly, although it may be out of scope for the current multi-rtp
draft, but I kind of believe that the performance evaluation (between
multipath and singlepath) on packet loss rate and PSNR is not sufficient
for interactive real-time communication apps. Since the user perceived RTT
delay ( or equivalently the MPRTP stack’s application’s perceived RTT
delay) is not included as a metric. What concerns me is that, delay
screwing may eat up all the potential benefit of multiple paths, if the
increased RTT is above the tolerable threshold set by application.
Therefore, I would suggest to add a suite of tests between the QoE gained
from single-path transferring on the most promising candidate channel (e.g.
the one with the biggest bandwidth and tolerable RTT) to multi-path
transferring solution.****

** **

As matter of fact, the current scheduling algorithm is not delay centric
and provides no hard protection for tolerable RTT requirements as it bases
its decision for the most important I-frame streams according to the
channel with the highest bandwidth/delay ratio. This could lead to
suboptimal scheduling results if some of channels looks better in ratio but
actually is unacceptable in terms of RTT constraint.****

** **

**2) **Secondly, even though the paper stresses the work is orthogonal to
congestion control, I can’t help but thinking that the interaction between
individual CC mechanism for sub-flows channels and the application (or
codec) rate control mechanism seems to be at the heart of maximizing QoE
boost gained from heterogeneous channels instead of doing simple traffic
partition for CBR media flows. ****

** **

It may be straightforward to borrow the current work in RTP CC algorithms
in RMCAT WG here. But I still believe there may be case for two-level rate
control in MPRTP stack, which means interfaces for cross-layer
status-sharing and coordinated rate control needs to be considered.****

** **
**3) **Moreover, in this paper, to yield non-linear monitory overhead for
sub-flow RTCP traffic, each sub-RTCP traffic is limited according to the
sub-flow rate of media traffic. It is a clever choice, but one may wonder
given the fact that the unfairness among the sampling and reporting
activity may transfer to the unfairness in cross-channel traffic offloading
and finally hold the ultimate application’s loss in QoE.

If the source code is available, we would like to participate and do some
more exploration.


BR
Lingli****


2013/3/16 Varun Singh <vsingh.ietf@gmail.com>

> Hi Lingli,
>
> We are working towards releasing an open-source version of our
> implementation. The details will emerge over the summer.
>
> The first thing we tested with our implementation was offloading. We have
> some scenarios in the paper [1] that shows how load balancing can be
> achieved, but these can be extended for offloading. Additionally, using
> mobility-ice extensions may help with some of the engineering issues.
>
> There are several ways in which MPRTP can be used, therefore we don't
> discuss the scheduling algorithm in the draft. I urge you to look at the
> research paper for those details.
>
> [1] http://www.netlab.tkk.fi/~varun/2013_MMSYS_Singh_MPRTP.pdf
>
> Regards,
> Varun
>
> ----
> http://www.netlab.tkk.fi/~varun
>
>
> On 15.3.2013, at 0.50, "denglingli@gmail.com" <denglingli@gmail.com>
> wrote:
>
> Hi Varuna,
>
>
> Impressive work.
>
> Do you have any implementation that provide support for real applications?
>
> Have you ever considered to apply this solution for Traffic offloading
> from cellular to wifi networks or vise visa scenarios?
>
>
> BR
>
>
> Lingli
>
> China mobile
>
>
> 发自我的 iPad
>
> _______________________________________________
>
> Audio/Video Transport Core Maintenance
>
> avt@ietf.org
>
> https://www.ietf.org/mailman/listinfo/avt
>
>


-- 
邓灵莉/Lingli Deng
中国移动通信研究院/China Mobile Research Institute
e-mail: denglingli@chinamobile.com
tel: 15801696688-3367
mobile: 13810597148