RE: [Geopriv] Geopriv L7 LCP: New Requirement

From: Winterbottom, James ^lt;>
Date: Sat Feb 10 2007 - 18:14:34 EST

I think that you guys really need to look at these networks and how they are constructed in more detail. What Otmar is talking about is not OBO in the same sense that it has been talked about in the past. It is LIS to LIS communications because each LIS provides slightly different information and you NEED information from both in order to be able to determine location. I can point you at several texts on this topic, the easiest one to start with is If you plan to look at this document it would also be worthwhile looking at the requirements section in there as I don't believe that all of the NENA location acquisition protocol requirements are currently addressed in the LCP requirements draft either. The most obvious one that springs to mind is the need for a quality of service response time parameter DA-12. Hannes, the terms and definitions section of this document is also quite extensive and are the terms that and definitions that are now being used widely through carrier and service provider groups. So they may also be a good place to start. Cheers James > -----Original Message----- > From: Hannes Tschofenig [] > Sent: Sunday, 11 February 2007 7:53 AM > To: Henning Schulzrinne > Cc: GEOPRIV > Subject: Re: [Geopriv] Geopriv L7 LCP: New Requirement > > I agree that this is a fuzzy term. > > I wonder whether we can make it a bit more precise. > > Two conditions seem to be necessary for the mechanism to work: > * The OBO-Client needs to learn the identifier. For some identifiers > that already requires being quite close to the Target. > * The OBO-Client needs to be authorized to perform the > identifier-to-location information resolution step. > > I think that the latter aspect is the restrictive part here. > > Ciao > Hannes > > Henning Schulzrinne wrote: > > Right. But 'having a relationship' with the network means very little. > > I have a relationship with Verizon DSL. Should I be able to get the > > addresses of all other Verizon DSL customers? > > > > On Feb 10, 2007, at 3:40 PM, Hannes Tschofenig wrote: > > > >> Hi Henning, > >> > >> some terminology first: > >> * Target -- RFC 3693 > >> * Location Information Server (LIS) -- entity that knows the location > >> of the Target > >> * OBO-Client -- entity that requests the location of the Target > >> without being the Target itself. > >> > >> If I understood the requirement correctly then it is > >> * applicable only if the OBO-Client is in the same network as the > >> Target or has a relationship to it, > >> This aspect is necessary since (a) the security issues are > >> difficult to handle and (b) the identifier might not be resolvable > >> outside this "realm". > >> * uses identifiers like the VCI/VPI (and not the URI) > >> > > > _______________________________________________ > Geopriv mailing list > > ------------------------------------------------------------------------------------------------ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any unauthorized use of this email is prohibited. ------------------------------------------------------------------------------------------------ [mf2]

Geopriv mailing list
Received on Sat, 10 Feb 2007 17:14:34 -0600

This archive was generated by hypermail 2.1.8 : Sat Feb 10 2007 - 18:14:33 EST