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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 21 September 2007 17:54 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 1IYmi1-0006f9-F0; Fri, 21 Sep 2007 13:54:33 -0400
Received: from int-area by megatron.ietf.org with local (Exim 4.43) id 1IYmhz-0006aa-Ib for int-area-confirm+ok@megatron.ietf.org; Fri, 21 Sep 2007 13:54:31 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IYmhx-0006Vz-OG for int-area@ietf.org; Fri, 21 Sep 2007 13:54:31 -0400
Received: from mail153.messagelabs.com ([216.82.253.51]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IYmhx-0004kS-1A for int-area@ietf.org; Fri, 21 Sep 2007 13:54:29 -0400
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-15.tower-153.messagelabs.com!1190397267!6576987!1
X-StarScan-Version: 5.5.12.14.2; banners=.,-,-
X-Originating-IP: [144.189.100.105]
Received: (qmail 2851 invoked from network); 21 Sep 2007 17:54:27 -0000
Received: from motgate5.mot.com (HELO motgate5.mot.com) (144.189.100.105) by server-15.tower-153.messagelabs.com with SMTP; 21 Sep 2007 17:54:27 -0000
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233]) by motgate5.mot.com (8.12.11/Motorola) with ESMTP id l8LHsRlq003347; Fri, 21 Sep 2007 10:54:27 -0700 (MST)
Received: from az10vts01 (az10vts01.mot.com [10.64.251.242]) by az33exr03.mot.com (8.13.1/Vontu) with SMTP id l8LHsQGk010453; Fri, 21 Sep 2007 12:54:26 -0500 (CDT)
Received: from [127.0.0.1] (mvp-10-169-4-127.corp.mot.com [10.169.4.127]) by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id l8LHsG4n010372; Fri, 21 Sep 2007 12:54:19 -0500 (CDT)
Message-ID: <46F40546.3010005@gmail.com>
Date: Fri, 21 Sep 2007 19:54:14 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Joe Touch <touch@ISI.EDU>
Subject: Re: [Int-area] Re: Discovering a Location Server in the Access Network
References: <46EA4B08.1060307@gmx.net> <46F3A6E1.10803@gmx.net> <46F3EFFD.9080109@isi.edu>
In-Reply-To: <46F3EFFD.9080109@isi.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 000775-4, 20/09/2007), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
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>
Errors-To: int-area-bounces@lists.ietf.org

Joe Touch wrote:
> 
> 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'.

I think I can agree.

I'm interested in all discovery mechanisms existing out there, and then
making some new...  But at some point one can easily wonder whether
there aren't too many of them those discovery mechanisms, and maybe some
more reuse can be possible.

So can I turn your (Hannes) question: how much does your new discovery
protocol reuse?  Of what?  Please don't argument that that and that
group believes the requirements eliminate all existing discovery
mechanisms, because I'm speechless in front of these requirements
because I haven't followed them, sorry :-)

Then of course another question to you (Hannes) is whether we have any
IPR issues around this new method of discovery, any entanglement.  If
there's IPR, on which side would one prefer to err, and so.

But without at least these little things one can say little, and even
less call it 'consensus', In My Humble Oppinion.

Alex

> 
> 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


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________


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