RE: [Geopriv] Geopriv L7 LCP: New Requirement

From: Dawson, Martin ^lt;>
Date: Thu Feb 15 2007 - 17:04:08 EST

I agree with Andy - I think you could come up with the same scheme for identity communication; it's just a protocol after all. I just don't see why you would suddenly want to use a different protocol for this special case of an OBO. I don't see any value in that. A lot of requirements have come up for location acquisition protocols - request for location reference, request for signed location, nomination of response time QoS, location assertion... There is the potential for any or all of these functions to be relevant in the LIS-LIS special OBO case. There's no point in redefining them in another protocol. Cheers, Martin -----Original Message----- From: Andrew Newton [] Sent: Friday, 16 February 2007 7:51 AM To: Stark, Barbara Cc:; Otmar Lendl Subject: Re: [Geopriv] Geopriv L7 LCP: New Requirement On Feb 15, 2007, at 12:50 PM, Stark, Barbara wrote: > What is difficult, is figuring out a standard format for a URI user > part > that would allow for all the variations in combinations of IDs that > exist, so that a standard format could be defined that would cover all > interconnection models. Section 8 of the NENA Location TID > ( provides 5 > different examples of interconnection models, and the IDs that would > need to be used in each of these cases. In this document, scenario 1 > uses the IP address, scenario 2 uses NAS-ID and ATM PVC, scenario 3 > uses > 2 VLAN tags, scenario 4 uses IP address, and scenario 5 uses L2TP > tunnel > ID (source and destination) and PPPoE session ID. These are just 5 > possible examples, and should not be considered exhaustive. > Interconnection models are still evolving. Well, that's easily solved with a BCP for formulating URIs based on the ID. You don't need a new protocol or to conflate the LCP protocol with this functionality. -andy _______________________________________________ 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 Thu, 15 Feb 2007 16:04:08 -0600

This archive was generated by hypermail 2.1.8 : Thu Feb 15 2007 - 17:03:33 EST