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

Hannes Tschofenig <Hannes.Tschofenig@gmx.net> Fri, 21 September 2007 18:28 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 1IYnFK-0002du-G2; Fri, 21 Sep 2007 14:28:58 -0400
Received: from int-area by megatron.ietf.org with local (Exim 4.43) id 1IYnFI-0002dB-7q for int-area-confirm+ok@megatron.ietf.org; Fri, 21 Sep 2007 14:28:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IYnFH-0002Wh-UT for int-area@ietf.org; Fri, 21 Sep 2007 14:28:55 -0400
Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IYnFA-00020I-In for int-area@ietf.org; Fri, 21 Sep 2007 14:28:49 -0400
Received: (qmail invoked by alias); 21 Sep 2007 18:28:37 -0000
Received: from p5498485F.dip.t-dialin.net (EHLO [192.168.1.4]) [84.152.72.95] by mail.gmx.net (mp056) with SMTP; 21 Sep 2007 20:28:37 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1/dEX9r+ADdDRDfbfvemwA/IOTmDYmvXXAGtSrULP 0+UsFDpqpCZFE7
Message-ID: <46F40D55.9050209@gmx.net>
Date: Fri, 21 Sep 2007 20:28:37 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
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> <46F40902.2040405@gmx.net> <46F40AE4.9010702@isi.edu>
In-Reply-To: <46F40AE4.9010702@isi.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
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

Hi Joe,

Joe Touch wrote:
> Hi, Hannes,
>
> I appreciate the idea of a 'ping' to the group. I also appreciate that
> everyone has their area of focus, and not all things brought to a WG
> receive the attention that's needed to move them forward.
>
>   
Agree.

> IETFers have discussed incentive systems to encourage people to read
> things that 'need to be reviewed', but let's not discuss that here.
>
>   
Certainly a complicated subject.

> Until we have that or an alternative - in the absence of positive
> feedback - items should not move forward in a WG based on silence as
> implicit approval.
>   
So far this issue is non-blocking. I just fear that this issue will 
surface again during IETF Last Call.

> If there is an absence of positive community support - either explicit,
> or implicit by the community's lack of interest and silence - IMO, the
> best path forward is to *revert* an item to individual submission, even
> if it's on the WG charter.
>   
There is another discovery mechanism, namely based on DHCP, that is 
pretty uncontroversial. I believe that it will progress quite smoothly 
in the group. Hence, the HELD specification itself would not be blocked 
since there is this other discovery mechanism. I do, however, believe 
that it is important to consider real world constraints that might slow 
down the deployment of certain mechanisms. If there is a way todo 
something about them then (in my believe) we should be looking at them.

Ciao
Hannes

> Joe
>
> Hannes Tschofenig wrote:
>   
>> My mail was a new (and different) attempt to receive some feedback.
>> So far, didn't work. Just bad luck.
>>
>> Ciao
>> Hannes
>>
>> 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'.
>>>
>>> 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