W3C home > Mailing lists > Public > public-coremob@w3.org > July 2012

Re: Network Information Use Cases

From: Tobie Langel <tobie@fb.com>
Date: Thu, 5 Jul 2012 10:53:56 +0000
To: "jeanfrancois.moy@orange.com" <jeanfrancois.moy@orange.com>, "public-coremob@w3.org" <public-coremob@w3.org>
Message-ID: <CC1B35C9.890A%tobie@fb.com>
On 7/5/12 12:04 PM, "jeanfrancois.moy@orange.com"
<jeanfrancois.moy@orange.com> wrote:

>> -----Original Message-----
>> From: Tobie Langel [mailto:tobie@fb.com]
>> Sent: 05 July 2012 10:56
>> To: MOY Jean Francois RD-ILAB-LON; public-coremob@w3.org
>> Subject: Re: Network Information Use Cases
>> 
>> On 7/5/12 11:43 AM, "jeanfrancois.moy@orange.com"
>> <jeanfrancois.moy@orange.com> wrote:
>> 
>> >I am aware of the fact that the current specification would not allow
>> >switching from one network to another, but still the fact of knowing
>> of
>> >which network we are currently on is of interest.
>> 
>> In order to reconsider including Network Info API in coremob level 1,
>> there needs to be compelling use cases where Network Info API _in its
>> current form_ is both necessary and sufficient. None of the use cases
>> you mentioned can be met using Network Info only. They all also
>require
>> a way to change the network.
>> 
>> --tobie
>
>The current version of the specification does not answer the whole
>problem; Indeed, a way to make sure that a request goes through a
>specific interface (does not have to change the network) would be ideal.

That's out of scope of the DAP WG's current charter. It's also non-trivial
to implement, spec or agree upon in any kind of reasonable timeframe, if
at all.

Unless other compelling use cases for Network Info come up, I'll leave it
out of coremob level 1.

--tobie
Received on Thursday, 5 July 2012 10:54:27 UTC

This archive was generated by hypermail 2.3.1 : Friday, 19 April 2013 17:36:46 UTC