Re: [Ecrit] PhoneBCP

"Brian Rosen" <br@brianrosen.net> Fri, 15 May 2009 12:10 UTC

Return-Path: <br@brianrosen.net>
X-Original-To: ecrit@core3.amsl.com
Delivered-To: ecrit@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EC15D3A70CC for <ecrit@core3.amsl.com>; Fri, 15 May 2009 05:10:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.503
X-Spam-Level:
X-Spam-Status: No, score=-2.503 tagged_above=-999 required=5 tests=[AWL=0.096, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZLzHDmtlGETV for <ecrit@core3.amsl.com>; Fri, 15 May 2009 05:10:39 -0700 (PDT)
Received: from ebru.winwebhosting.com (ebru.winwebhosting.com [74.55.202.130]) by core3.amsl.com (Postfix) with ESMTP id 3E7753A6768 for <ecrit@ietf.org>; Fri, 15 May 2009 05:10:39 -0700 (PDT)
Received: from neustargw.va.neustar.com ([209.173.53.233] helo=BROS3VMxp) by ebru.winwebhosting.com with esmtpa (Exim 4.69) (envelope-from <br@brianrosen.net>) id 1M4wGk-0007lw-Iz; Fri, 15 May 2009 07:12:06 -0500
From: Brian Rosen <br@brianrosen.net>
To: 'Randall Gellens' <randy@qualcomm.com>, "'DRAGE, Keith (Keith)'" <drage@alcatel-lucent.com>, 'Ted Hardie' <hardie@qualcomm.com>, 'Marc Linsner' <mlinsner@cisco.com>, ecrit@ietf.org
References: <C61F79BD.14AA4%mlinsner@cisco.com> <p06240805c61fb26aa4e1@[10.0.1.197]> <28B7C3AA2A7ABA4A841F11217ABE78D6759ED5FD@FRMRSSXCHMBSB3.dc-m.alcatel- lucent.com> <029001c9d49e$3bdf6ff0$b39e4fd0$@net> <p06240604c6326f220721@[192.168.99.14]> <039a01c9d4fd$c60e4c50$522ae4f0$@net> <p06240609c632a3859181@[192.168.99.14]>
In-Reply-To: <p06240609c632a3859181@[192.168.99.14]>
Date: Fri, 15 May 2009 08:12:09 -0400
Message-ID: <045f01c9d556$60eb58f0$22c20ad0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcnVGPaaldy+WM/zSbCDdv0JgPIq/gAPS3Kw
Content-language: en-us
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ebru.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Source:
X-Source-Args:
X-Source-Dir:
Subject: Re: [Ecrit] PhoneBCP
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 May 2009 12:10:40 -0000

Since an increasing proportion of devices are used with location based
services, that would seem to be incorrect.  The text says "periodically" not
"frequently", and the location you acquire is routing location, which is
cell tower based for most mobiles.  That is not in the least onerous.

Brian

> -----Original Message-----
> From: Randall Gellens [mailto:randy@qualcomm.com]
> Sent: Friday, May 15, 2009 12:47 AM
> To: Brian Rosen; 'DRAGE, Keith (Keith)'; 'Ted Hardie'; 'Marc Linsner';
> ecrit@ietf.org
> Subject: Re: [Ecrit] PhoneBCP
> 
> At 9:37 PM -0400 5/14/09, Brian Rosen wrote:
> 
> >  Please cite an instance.
> >
> >  We do not believe that the requirement for the endpoint to query the
> LIS or
> >  the LoST server is onerous on any cellular network.  In the scheme
> of things
> >  that IP based devices (we are talking about IP connected devices,
> not
> >  current GSM/CDMA systems) are expected to do, a HELD and LoST query
> is very
> >  modest in bandwidth, code size and compute power.
> 
> The instructions are for devices to determine their location when
> powered on and frequently thereafter, and do LoST queries afterwards.
> This may be fine for many devices, but not for cellphones.