[Int-area] Discovering a Location Server in the Access Network
Hannes Tschofenig <Hannes.Tschofenig@gmx.net> Fri, 14 September 2007 08:49 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 1IW6rW-000734-AG; Fri, 14 Sep 2007 04:49:18 -0400
Received: from int-area by megatron.ietf.org with local (Exim 4.43) id 1IW6rU-00072s-NA for int-area-confirm+ok@megatron.ietf.org; Fri, 14 Sep 2007 04:49:16 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IW6rU-00072j-CA for int-area@ietf.org; Fri, 14 Sep 2007 04:49:16 -0400
Received: from mail.gmx.net ([213.165.64.20]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IW6rT-0005z8-P9 for int-area@ietf.org; Fri, 14 Sep 2007 04:49:16 -0400
Received: (qmail invoked by alias); 14 Sep 2007 08:49:14 -0000
Received: from socks1.netz.sbs.de (EHLO [192.35.17.26]) [192.35.17.26] by mail.gmx.net (mp028) with SMTP; 14 Sep 2007 10:49:14 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+osb0F8Y2ofd0+rfIorWU2fn4xf60vrgOWc9hVR4 BZYBaqhLHCMW7N
Message-ID: <46EA4B08.1060307@gmx.net>
Date: Fri, 14 Sep 2007 10:49:12 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: int-area@ietf.org
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: 8b431ad66d60be2d47c7bfeb879db82c
Cc:
Subject: [Int-area] Discovering a Location Server in the Access Network
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 all, I would need some feedback regarding work that is currently being done in the GEOPRIV working group. For some time we have been working on an application layer protocol that allows the end host to obtain its own location information (or a reference to it) from a server (called LIS) in the access network. This LIS indeed needs to be located in the access network (and not at an arbitrary place on the Internet) since only the layer 2/layer 3 provider is able to determine the precise location of end point. A year ago I lead a design team that captured the problem statement and requirements. The document is available here: http://www.ietf.org/internet-drafts/draft-ietf-geopriv-l7-lcp-ps-05.txt The protocol that provides the functionality of the above-mentioned requirements document is HELD: http://tools.ietf.org/html/draft-ietf-geopriv-http-location-delivery Providing the end host with the address of the LIS is relatively easy if you can use DHCP. However, there are deployment environments (such as DSL networks) where the DSL operator cannot control the DSL home routers and any information that is provided by the DSL operator may not be relayed to the end host via this box. So, to overcome this issue the group had an idea: Let's use a different discovery technique that does not require upgrades to intermediate devices (such as this DSL home router). 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 We have investigated other solutions as well (see Section 4 of http://www.ietf.org/internet-drafts/draft-ietf-geopriv-l7-lcp-ps-05.txt) but the group (or at least a few folks) believes that this is a "good" approach. I had a chat with Jari and we both agree that this topoic falls into the expertise of the Internet Area. Hence, I would like to solicit feedback from you. Ciao Hannes _______________________________________________ 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