Re: [Int-area] Discovering a Location Server in the Access Network
Pekka Savola <pekkas@netcore.fi> Sat, 22 September 2007 04: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 1IYx0W-0006W4-Dm; Sat, 22 Sep 2007 00:54:20 -0400
Received: from int-area by megatron.ietf.org with local (Exim 4.43) id 1IYx0V-0006Vx-41 for int-area-confirm+ok@megatron.ietf.org; Sat, 22 Sep 2007 00:54:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IYx0U-0006U2-QO for int-area@ietf.org; Sat, 22 Sep 2007 00:54:18 -0400
Received: from eunet-gw.ipv6.netcore.fi ([2001:670:86:3001::1] helo=netcore.fi) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IYx0O-0001rw-Ec for int-area@ietf.org; Sat, 22 Sep 2007 00:54:13 -0400
Received: from netcore.fi (localhost [127.0.0.1]) by netcore.fi (8.13.8/8.13.8) with ESMTP id l8M4rpKA021653; Sat, 22 Sep 2007 07:53:52 +0300
Received: from localhost (pekkas@localhost) by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id l8M4rp9b021650; Sat, 22 Sep 2007 07:53:51 +0300
Date: Sat, 22 Sep 2007 07:53:51 +0300
From: Pekka Savola <pekkas@netcore.fi>
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
Subject: Re: [Int-area] Discovering a Location Server in the Access Network
In-Reply-To: <46EA4B08.1060307@gmx.net>
Message-ID: <Pine.LNX.4.64.0709220738510.21065@netcore.fi>
References: <46EA4B08.1060307@gmx.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Virus-Scanned: ClamAV 0.91.2/4357/Fri Sep 21 12:55:46 2007 on otso.netcore.fi
X-Virus-Status: Clean
X-Spam-Status: No, score=-3.5 required=5.0 tests=ALL_TRUSTED, AWL, BAYES_00 autolearn=ham version=3.2.3
X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on otso.netcore.fi
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
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
On Fri, 14 Sep 2007, 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 > * Perform a reverse DNS lookup to learn the domain > * Lookup the LIS for that domain > * Contact the LIS 2-3 years ago we had the similar problem with IPv6-in-IPv4 tunnel endpoint discovery, only that the endpoint could reside outside the L2/L3 network as well. The approaches identified then were described at: http://tools.ietf.org/html/draft-palet-v6ops-tun-auto-disc-03 Personally, I thought anycast made most sense. Some other folks preferred reverse DNS population (e.g. [1]), but that also has problems with private address use of a more recent approach to try to push the NAT boxes to act as authoritative for private address spaces [2] in which case the ISP could not populate its DNS resolvers for private addresses either. In your case where the L2/L3 provider is required to provide this information in order for the methodology could work, though personally I'm somewhat concerned about 1) how reliable the public IP address discovery could be, 2) what happens if the ISP doesn't provide reverse DNS entry for the public IP, and 3) whether the operator who's providing L3 service and public IP does in fact even know where the user is located (if the user's ADSL session is provided by a L2 provider and just tunneled - in bulk - using L2TP to L3 provider). The last issue is probably the biggest and you may need to consider in more detail how such "L2 different from L3" network would work. Realistically any solution I could think of that doesn't involve DHCP or PPP is likely to require coordination in this case. Would it required that the local regular requires L3 provider to also keep track of the physical location? [1] http://tools.ietf.org/html/draft-yamamoto-naptr-service-discovery-01 [2] http://tools.ietf.org/html/draft-ietf-dnsop-default-local-zones-02 -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings _______________________________________________ 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