W3C home > Mailing lists > Public > public-webrtc@w3.org > June 2018

Re: WebRTC NV use case Mobility and cost of access

From: Peter Thatcher <pthatcher@google.com>
Date: Mon, 18 Jun 2018 02:19:43 -0700
Message-ID: <CAJrXDUHctkuh-gWrp3qJUeGfCyHXzdKKNy1EYCnA2Et3ow8hXg@mail.gmail.com>
To: Göran Eriksson AP <goran.ap.eriksson@ericsson.com>
Cc: W3C WEBRTC <public-webrtc@w3.org>
wifi/cell is crude, but it's better than what we have now.

Something better would be nice, but how would it be implemented?  Operating
systems don't make this info available.  Would we expect users to go into
some browser setting and tell the browser info like this?  Would anyone
ever use such a setting? It seems like something like this would need to be
automatic, but I don't see how it could be implemented.

On Fri, Jun 15, 2018 at 11:24 PM Göran Eriksson AP <
goran.ap.eriksson@ericsson.com> wrote:

> Hi,
>
>
>
> Reading the use case document, including references, the question about
> how the UA get to know the cost of the Internet access comes to my mind
> that just want to get 100% clear before the face2face next week.
>
>
>
> In one solution, the web app acquires this cost information and provides
> it to the [ICE agent in] UA via a JS API.
>
>
>
> Is this the assumed option or are there other alternatives
> assumed/considered. If so which and what 'observability and control' of the
> this will be provided to the web site (and the user)?
>
>
>
> I expect all of us are aware that the 'simple' way to figure out the cost
> in the device by just looking at the 'interface type'="cellular" is not
> enough. We need for instance to take into account there being/coming
> license free cellular access networks as well as licensed networks with
> "all-U-can-eat".
>
>
>
> Regards
>
> Göran
>
>
>
Received on Monday, 18 June 2018 09:20:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:42 UTC