Re: [rtcweb] draft-jennings-rtcweb-qos: QCI "marking"?
Cameron Byrne <cb.list6@gmail.com> Tue, 18 September 2012 13:27 UTC
Return-Path: <cb.list6@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C64721E80C1 for <rtcweb@ietfa.amsl.com>; Tue, 18 Sep 2012 06:27:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.332
X-Spam-Level:
X-Spam-Status: No, score=-3.332 tagged_above=-999 required=5 tests=[AWL=0.266, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PLYzFHnXGqFX for <rtcweb@ietfa.amsl.com>; Tue, 18 Sep 2012 06:27:38 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2D1E421F8495 for <rtcweb@ietf.org>; Tue, 18 Sep 2012 06:27:37 -0700 (PDT)
Received: by lbky2 with SMTP id y2so5350139lbk.31 for <rtcweb@ietf.org>; Tue, 18 Sep 2012 06:27:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=y/CtOV2LNkTDCsnxouMuLQdNd5Hai4DMLDFw7FjQ5/g=; b=tNuxhFm0SPVhX2dbzTzQrXKq29g7Yf2KRCHdxLBZjXTFGHx+l7xX8txRZiLpmHhxHW yNgsNcz4ItY/+WTh8/lyuaESLGt26LqRyzOrsWFXzjmMQ+VsgkYSo86Ux3QDLEK2a/jv n5UWd98qpqqWQ0e6IMh20/xu6Y6F3skX/EDFNGxg3eiaYRnAHbfG67JVA2i5BhAsmVDZ 6Rz3cfs+xbRijHY1RRFEhr9GVFg3xVgPrDKBiDZ9LLQzu1+xBfiu3d54/h9B5M9IMixI n1zGQbGRz2/Q1Hgebz42WSP6VfrdzPR9yW6qsCxijPxgJ66Z6C40QkPDs1MMT6ug25Uf pJ7w==
MIME-Version: 1.0
Received: by 10.152.103.146 with SMTP id fw18mr113251lab.30.1347974856992; Tue, 18 Sep 2012 06:27:36 -0700 (PDT)
Received: by 10.112.49.66 with HTTP; Tue, 18 Sep 2012 06:27:36 -0700 (PDT)
Received: by 10.112.49.66 with HTTP; Tue, 18 Sep 2012 06:27:36 -0700 (PDT)
In-Reply-To: <E44893DD4E290745BB608EB23FDDB7622C5EF8@008-AM1MPN1-043.mgdnok.nokia.com>
References: <E44893DD4E290745BB608EB23FDDB7622C5EF8@008-AM1MPN1-043.mgdnok.nokia.com>
Date: Tue, 18 Sep 2012 06:27:36 -0700
Message-ID: <CAD6AjGRtc6cj94ypzts8RxrbN3tqkzwM47pj86Mea+BupVisGQ@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: Markus.Isomaki@nokia.com
Content-Type: multipart/alternative; boundary="f46d040714cf84688c04c9f9dabd"
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] draft-jennings-rtcweb-qos: QCI "marking"?
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Sep 2012 13:27:39 -0000
On Sep 18, 2012 1:08 AM, <Markus.Isomaki@nokia.com> wrote: > > Hi, > > Martin Thomson wrote: > > > >On 10 September 2012 07:15, Harald Alvestrand <harald@alvestrand.no> > >wrote: > >> - Pointers to documentation on how browsers are expected to be able to > >> set QCI and WiFI markings would be a good addition. Compared to those, > >> DSCP codepoint setting is well understood. > > > <snip> > > > >What do people think about NOT including QCI/WiFi markings? Is it not > >possible for a wireless interface to examine DSCP markings in order to > >determine the markings for the link? We should endeavour to maintain the > >proper abstractions. > > > > I'm not even sure if the browser or even the OS can influence much the QCI or bearer selection in LTE. I think the model is such that the "network" sets up these special non-best-effort bearers, and gives the endpoint the classifier rules related to them. The rules tell the endpoint how to map outgoing packets to the bearers. Typically the rules are based on source/destination IP and port, and the transport protocol. Someone may be able to confirm, but I believe DSCP can be used too. But basically the rules come from the network and the endpoint just follows them. > > So, somehow the browser or the JS app would first have to convince the access network provider to setup the special bearer so that the right flows get classified to it. In IMS the SIP proxy reads the SDP and tells some network element what audio or video flows are being setup and what their 5-tuples are, so the network is being able to setup the bearers correctly for them. The endpoint merely waits for this setup and acts accordingly. This works as the SIP proxy is run by the access operator. In RTCWeb the same could work if the calling site had a relationship with the access operator. I've heard that there is some work by some operators to offer Web APIs for 3rd party apps to do the bearer setup requests more ad hoc. Most of this may be outside the scope of RTCWeb but I think the document should have some explanation on how it works from the OS, browser, JS client, calling site, and mobile operator perspective. > > On the "transport" or "data path" level I don't think the browser needs to understand anything about QCIs. DSCP marking should be good enough. > > Anyone with more LTE/mobile clue that could comment on this? > > Markus > Your understanding is similar to mine. Generally speaking, qos in 3gpp networks is network initiated and controlled by a PCRF. The UEs are generally not trusted, as they may abuse qos. I am told that qos is an important differentiator for the operator run services and consequently will not be generally available to 3rd party apps such as webrtc. I am generally sceptical about qos on the internets, and we may be getting into a dangerous area if we start to assume networks will give anything more than best effort to webrtc. CB _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb
- [rtcweb] draft-jennings-rtcweb-qos: QCI "marking"? Markus.Isomaki
- Re: [rtcweb] draft-jennings-rtcweb-qos: QCI "mark… Cameron Byrne
- Re: [rtcweb] draft-jennings-rtcweb-qos: QCI "mark… Hannes Tschofenig
- Re: [rtcweb] draft-jennings-rtcweb-qos: QCI "mark… Cullen Jennings (fluffy)
- Re: [rtcweb] draft-jennings-rtcweb-qos: QCI "mark… Tirumaleswar Reddy (tireddy)