Re: [rtcweb] FW: New Version Notification for draft-reddy-rtcweb-mobile-00.txt

Inline as SD:

-----Original Message-----
From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of Martin Thomson
Sent: Wednesday, January 16, 2013 3:29 PM
To: Tirumaleswar Reddy (tireddy)
Cc: John Kaippallimalil; rtcweb@ietf.org; bpatil@ovi.com
Subject: Re: [rtcweb] FW: New Version Notification for draft-reddy-rtcweb-mobile-00.txt

There are many characteristics of mobile networks that make poorly designed applications perform poorly.  Honestly, WebRTC isn't special in this regard.  I'd prefer to see something that is less negatively worded that instead aims to improve awareness of the limitations of the network and how a well-designed application might avoid the problems that these cause.  See:
http://developer.android.com/training/efficient-downloads/efficient-network-access.html#RadioStateMachine

For example, I find the assertion that is made here, namely multiplexing will degrade the quality of experiences, to be specious.
The assertion is true, but it presumes that multiplexing is or must be used.

SD: the question is what assumption is made regarding DSCP values for the single UDP flow which has multiplexed RTP flows?
- If the assumption is that multiple DSCP is used for the single flow, then the document states that it does not work in the 3G network. However, the assumption is premature at this stage as it is not a foregone conclusion. On the other hand with this assumption, the user experience should not degrade because it is no different from different flows with their own DSCPs.

- If the assumption is that a single DSCP for a multiplexed flow, then there is a chance that the experience will degrade but then it should not be a problem since the DSCP value in TFT for the bearer should match with the DSCP value in the RTP packets sent by the UE. 

However, if the mobile elements turn down the multiplexing as is suggested by the rtcweb usage draft then either of the above scenarios ceases to exist.
Regards,
Subha

--Martin

On 14 January 2013 06:35, Tirumaleswar Reddy (tireddy) <tireddy@cisco.com> wrote:
> Hi all,'
>
>
>
> This document describes a set of scenarios in which WebRTC 
> applications have problems in Mobile Networks related to QOS, Mobility 
> (SIPTO). Thanks to Magnus, Markus, Dan and Basavraj for their help and 
> comments. The URL of the new draft:
>
>
>
> http://tools.ietf.org/html/draft-reddy-rtcweb-mobile-00
>
>
>
> comments and suggestions are welcome.
>
>
>
> Best Regards,
>
> --authors.
>
>
>
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Monday, January 14, 2013 1:40 PM
> To: Tirumaleswar Reddy (tireddy)
> Cc: john.kaippallimalil@huawei.com; Ram Mohan R (rmohanr)
> Subject: New Version Notification for draft-reddy-rtcweb-mobile-00.txt
>
>
>
>
>
> A new version of I-D, draft-reddy-rtcweb-mobile-00.txt
>
> has been successfully submitted by Tirumaleswar Reddy and posted to 
> the
>
> IETF repository.
>
>
>
> Filename:   draft-reddy-rtcweb-mobile
>
> Revision:   00
>
> Title:            Problems with WebRTC in Mobile Networks
>
> Creation date:    2013-01-14
>
> WG ID:            Individual Submission
>
> Number of pages: 14
>
> URL:
> http://www.ietf.org/internet-drafts/draft-reddy-rtcweb-mobile-00.txt
>
> Status:          http://datatracker.ietf.org/doc/draft-reddy-rtcweb-mobile
>
> Htmlized:        http://tools.ietf.org/html/draft-reddy-rtcweb-mobile-00
>
>
>
>
>
> Abstract:
>
>    This document describes a set of scenarios in which WebRTC
>
>    applications have problems in Mobile Networks.
>
>
>
>
>
>
>
>
>
> The IETF Secretariat
>
>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb