Re: [Geopriv] HELD: user-configured data

Henning Schulzrinne <Henning.Schulzrinne@fcc.gov> Sat, 25 April 2015 12:49 UTC

Return-Path: <Henning.Schulzrinne@fcc.gov>
X-Original-To: geopriv@ietfa.amsl.com
Delivered-To: geopriv@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 798B71A8834 for <geopriv@ietfa.amsl.com>; Sat, 25 Apr 2015 05:49:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r8XO5ryY7m1V for <geopriv@ietfa.amsl.com>; Sat, 25 Apr 2015 05:49:34 -0700 (PDT)
Received: from DC-IP-2.fcc.gov (dc-ip-2.fcc.gov [192.104.54.91]) by ietfa.amsl.com (Postfix) with ESMTP id 85AF91A8829 for <geopriv@ietf.org>; Sat, 25 Apr 2015 05:49:34 -0700 (PDT)
Message-ID: <E6A16181E5FD2F46B962315BB05962D07D3376E1@fcc.gov>
From: Henning Schulzrinne <Henning.Schulzrinne@fcc.gov>
To: James Winterbottom <a.james.winterbottom@gmail.com>
Thread-Topic: [Geopriv] HELD: user-configured data
Thread-Index: AdB+DVAsfrtK/5I1T2CjgnoZPVLhZwAKaPIA//+/iq+AAOONAIABmf/X
Date: Sat, 25 Apr 2015 12:49:33 +0000
References: <E6A16181E5FD2F46B962315BB05962D07D336F45@fcc.gov> <,> <CABkgnnWcLErqa4b6CGUKgLVuc6HDQFdiR9nFZnzFDX20G=C3YA@mail.gmail.com> <E6A16181E5FD2F46B962315BB05962D07D337042@fcc.gov>, <30BDAF1D-6F50-4053-AA7F-818BD6E68043@gmail.com>
In-Reply-To: <30BDAF1D-6F50-4053-AA7F-818BD6E68043@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/geopriv/kvtr3KM18nFX_RzSuV62XOVRmIw>
Cc: "geopriv@ietf.org" <geopriv@ietf.org>
Subject: Re: [Geopriv] HELD: user-configured data
X-BeenThere: geopriv@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Geographic Location/Privacy <geopriv.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/geopriv>, <mailto:geopriv-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/geopriv/>
List-Post: <mailto:geopriv@ietf.org>
List-Help: <mailto:geopriv-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Apr 2015 12:49:36 -0000

James,

I'm struggling with the problem that deployment of LIS by ISP has been slow (and this is more glacier-slow than snail-slow). Thus, I'm afraid that user-provided location will be with us for quite a while, for landline and nomadic devices.

In my particular use case (VRS), faking locations seems less likely since the caller is a known entity.

In addition, there is some ability to validate the rough location by IP address.

Besides a custom web page, we don't seem to have any good standards-based options at the moment. I'd like to be able to automate the process a bit, so that the UA can detect changes in network attachment point and prompt the user for new location data.

Henning

________________________________________
From: James Winterbottom [a.james.winterbottom@gmail.com]
Sent: Friday, April 24, 2015 4:16 AM
To: Henning Schulzrinne
Cc: Martin Thomson; geopriv@ietf.org
Subject: Re: [Geopriv] HELD: user-configured data

I guess that this would ensure that location was “valid”, but doesn’t it open the system up to the “Where would I like to be today” issue that is impacting i2 to some extent?
The LIS is supposed to provide some kind of assurances on the location it provides, if it can be independently user-populated it kind of feels like this aspect of the LIS is going away.

Cheers
James



> On 24 Apr 2015, at 8:43 am, Henning Schulzrinne <Henning.Schulzrinne@fcc.gov>; wrote:
>
> I'm not wedded to the method at all, but that was the only one that seemed close... A validation query via LoST might be a good option (i.e., first LoST, then HELD).
>
> ________________________________________
> From: Martin Thomson [martin.thomson@gmail.com]
> Sent: Thursday, April 23, 2015 6:32 PM
> To: Henning Schulzrinne
> Cc: geopriv@ietf.org
> Subject: Re: [Geopriv] HELD: user-configured data
>
> On 23 April 2015 at 14:36, Henning Schulzrinne
> <Henning.Schulzrinne@fcc.gov>; wrote:
>> Can we use a model similar to RFC 7105 for updating user-configured (civic) location data in VoIP scenarios?
>
>
> 'twould require definition of a new measurement type that used the
> civic address schema.
>
> The success response would likely turn into an echo of the address;
> failure would not include the information.  There wouldn't be any way
> to annotate that with extra information about what went wrong in the
> same way that recent additions to LoST might.
>
> _______________________________________________
> Geopriv mailing list
> Geopriv@ietf.org
> https://www.ietf.org/mailman/listinfo/geopriv