W3C home > Mailing lists > Public > public-device-apis@w3.org > December 2013

Re: Network Information API

From: <Frederick.Hirsch@nokia.com>
Date: Mon, 9 Dec 2013 15:45:50 +0000
To: <jsoref@blackberry.com>
CC: <Frederick.Hirsch@nokia.com>, <w3c@marcosc.com>, <anssi.kostiainen@intel.com>, <public-device-apis@w3.org>
Message-ID: <E9CC545F-D372-46A2-8DFA-349FF4A3C8BA@nokia.com>

this seems aligned with recent discussions elsewhere that a low level interface is required to allow agility in use; however I appreciate Anssi's goal of simplification/abstraction.

how does this interface communicate the performance characteristics of each interface, or is that assumed to be known to the application (based on what, the names?)

a couple of privacy questions:

does this API enhance fingerprinting possibilities by allowing enumeration of interfaces?

does exposing a  persistent uuid provide user identifying information to applications enabling correlation of activity across applications thus creating a privacy risk?

regards, Frederick

Frederick Hirsch

On Dec 6, 2013, at 11:39 AM, ext Josh Soref wrote:

> Fwiw, Iım considering a network information api which is based on network
> interfaces.
> interface NetworkAdapter {
>  string uuid;
>  bool connected;
>  string[] localaddresses;
>  string[] gateways;
>  /* possibly exposing dns server information */
> }
> With a notice going out for each up/down of each interface.
> When I take my phone and it switches from only having cellular to having
> cellular + wifi, Iıd get a notification for the new adapter, that
> notification is a hint that routing may have changed and performance
> characteristics may be different.
> For BlackBerry devices, there is a third network which can easily go
> up/down which is the Work network (itıs roughly a VPN), and then thereıs
> also a normal VPN connection available ‹ each would notify (but only if
> theyıre available to the given application ‹ the Work network may or may
> not be exposed to non Work applications at the user/adminıs discretion).
> I havenıt started prototyping this, but I believe that in theory this
> covers all the actual use cases I can imagine.
> When routing changes, itıs quite likely that performance characteristics
> will change.
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Received on Monday, 9 December 2013 15:54:51 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:01 UTC