Re: [Int-area] Discovering a Location Server in the Access Network
Yangwoo Ko <newcat@icu.ac.kr> Sat, 15 September 2007 00:46 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 1IWLnz-0007Ro-MV; Fri, 14 Sep 2007 20:46:39 -0400
Received: from int-area by megatron.ietf.org with local (Exim 4.43) id 1IWLny-0007RZ-Nc for int-area-confirm+ok@megatron.ietf.org; Fri, 14 Sep 2007 20:46:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IWLny-0007RQ-DN for int-area@ietf.org; Fri, 14 Sep 2007 20:46:38 -0400
Received: from sniper.icu.ac.kr ([210.107.128.51]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IWLnw-00029j-Fs for int-area@ietf.org; Fri, 14 Sep 2007 20:46:38 -0400
Received: (snipe 5098 invoked by uid 0); 15 Sep 2007 09:47:05 +0900
Received: from newcat@icu.ac.kr with Spamsniper 2.96.00 (Processed in 0.802797 secs);
Received: from unknown (HELO ?210.107.251.4?) (Z???own@210.107.251.4) by unknown with SMTP; 15 Sep 2007 09:47:04 +0900
X-SNIPER-SENDERIP: 210.107.251.4
X-SNIPER-MAILFROM: newcat@icu.ac.kr
X-SNIPER-RCPTTO: alexandru.petrescu@gmail.com, Hannes.Tschofenig@gmx.net, int-area@ietf.org, yangwooko@gmail.com
Message-ID: <46EB2B75.4000902@icu.ac.kr>
Date: Sat, 15 Sep 2007 09:46:45 +0900
From: Yangwoo Ko <newcat@icu.ac.kr>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Subject: Re: [Int-area] Discovering a Location Server in the Access Network
References: <46EA4B08.1060307@gmx.net> <46EA956B.1030700@gmail.com> <46EAA1AF.2000000@gmx.net> <46EAAACD.4000603@gmail.com>
In-Reply-To: <46EAAACD.4000603@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
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
Alexandru Petrescu wrote: > > Hannes Tschofenig wrote: >>>> >>>> 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 >>> >>> I think it should say 'Discover ... address of the LIS', right? And >>> not 'of the end point'(?) >>> >> No; it really means that you learn your own public IP address. That's >> no problem if you already have one but you might also be behind a NAT >> (which is extremely common in a DSL network). Hence, knowing your >> private IP address is not very useful for the discovery of the LIS >> since you will not find a LIS in your own home network. > > But you're sure that it's necessary to discover my IP address when I'm > behind NAT? Does the LIS need to contact me without me needing to > contact it first? What I understood from the first mail sent by Hannes is that discovery of the public address is necessary for the next step (i.e. DNS reverse lookup) to work. If there is other way to get the address of LIS without going through presented steps, then that is just yet another alternative. Regards _______________________________________________ Int-area mailing list Int-area@lists.ietf.org https://www1.ietf.org/mailman/listinfo/int-area
- [Int-area] Discovering a Location Server in the A… Hannes Tschofenig
- Re: [Int-area] Discovering a Location Server in t… Alexandru Petrescu
- Re: [Int-area] Discovering a Location Server in t… Hannes Tschofenig
- Re: [Int-area] Discovering a Location Server in t… Alexandru Petrescu
- Re: [Int-area] Discovering a Location Server in t… Yangwoo Ko
- Re: [Int-area] Discovering a Location Server in t… Hannes Tschofenig
- [Int-area] Re: Discovering a Location Server in t… Hannes Tschofenig
- Re: [Int-area] Re: Discovering a Location Server … Joe Touch
- Re: [Int-area] Re: Discovering a Location Server … Alexandru Petrescu
- Re: [Int-area] Re: Discovering a Location Server … Hannes Tschofenig
- Re: [Int-area] Re: Discovering a Location Server … Joe Touch
- Re: [Int-area] Re: Discovering a Location Server … Hannes Tschofenig
- Re: [Int-area] Re: Discovering a Location Server … Hannes Tschofenig
- Re: [Int-area] Discovering a Location Server in t… Pekka Savola
- Re: [Int-area] Discovering a Location Server in t… Hannes Tschofenig
- Re: [Int-area] Re: Discovering a Location Server … Iljitsch van Beijnum