Re: [Int-area] Re: Discovering a Location Server in the Access Network

Joe Touch <touch@ISI.EDU> Fri, 21 September 2007 16:24 UTC

Return-path: <int-area-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IYlIT-0003qH-Up; Fri, 21 Sep 2007 12:24:05 -0400
Received: from int-area by megatron.ietf.org with local (Exim 4.43) id 1IYlIS-0003nn-9q for int-area-confirm+ok@megatron.ietf.org; Fri, 21 Sep 2007 12:24:04 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IYlIR-0003my-TX for int-area@ietf.org; Fri, 21 Sep 2007 12:24:03 -0400
Received: from vapor.isi.edu ([128.9.64.64]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IYlIR-0000cu-91 for int-area@ietf.org; Fri, 21 Sep 2007 12:24:03 -0400
Received: from [127.0.0.1] (pool-71-106-89-188.lsanca.dsl-w.verizon.net [71.106.89.188]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id l8LGNk1b004689; Fri, 21 Sep 2007 09:23:47 -0700 (PDT)
Message-ID: <46F3EFFD.9080109@isi.edu>
Date: Fri, 21 Sep 2007 09:23:25 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
Subject: Re: [Int-area] Re: Discovering a Location Server in the Access Network
References: <46EA4B08.1060307@gmx.net> <46F3A6E1.10803@gmx.net>
In-Reply-To: <46F3A6E1.10803@gmx.net>
X-Enigmail-Version: 0.95.3
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: int-area@ietf.org
X-BeenThere: int-area@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/int-area>
List-Post: <mailto:int-area@lists.ietf.org>
List-Help: <mailto:int-area-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0210742347=="
Errors-To: int-area-bounces@lists.ietf.org


Hannes Tschofenig wrote:
> Hi all,
> 
> I haven't received concerns regarding the suggested discovery approach.
> May I assume from the lack of feedback that the suggested approach is
> reasonable?

I have seen this sort of conclusion claimed before, and it is incorrect.

Silence is not a hum in favor.

I don't have a position on this per se, but if nobody can step forward
and claim this is a reasonable solution, all we have is 'lack of
feedback', not 'consensus'.

Joe

...
>> In short, the current proposal (see
>> http://tools.ietf.org/html/draft-thomson-geopriv-lis-discovery-02.txt;
>> ignoring Section 2 which defines the DHCP portion) essentially does
>> the following:
>>
>> * Discover the public IP address of the end point
>> * Perform a reverse DNS lookup to learn the domain
>> * Lookup the LIS for that domain
>> * Contact the LIS

_______________________________________________
Int-area mailing list
Int-area@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/int-area