[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Ecrit] Consensus Call: Precise Location Information not available to End Host
I think one of the objectives should be that a UA can copy location
information from a PIDF-LO-speaking protocol to LoST without knowing
anything about the content. It really doesn't care and it won't
really be able to manipulate location information in any event. I'm
not sure this is currently as easy as it could be. Obviously, LCP
can't just dump random stuff into LoST queries, as this is likely to
fail, but the number of LoST servers is always going to be much
smaller than the number of clients (and LoST servers are more likely
to be upgradeable).
On Apr 20, 2007, at 5:29 PM, Andrew Newton wrote:
Well, the point I was trying to make was that each new location
profile would have to account for location providing. So, if we do
geodetic-3d or rfc3825 or linser-locrel or whatever else comes
along, we have to account for the fact that output has to also be
the input. I know that may not be such a big deal, but we never
really know. A simple key is easier on databases than the complex
searching needed for location information, especially as the
location profiles get more complex.
I agree about the special case. But the behavior does not have to
be a special case, it can be done all the time. Essentially, a
reference always exists inside a LoST mapping. Anytime a LoST
mapping is converted into a PIDF-LO, such as when the LIS is trying
to get a the service boundary for a PSAP to use as location
information, that reference goes along with it. Later on, a VSP or
whoever can simply use that reference to check the PSAP URI vs.
using the location.
I admit, this is an optimization. But we already have to change
LoST a little bit. We might as well try to make the subsequent
policing against abuse as low cost as possible.
_______________________________________________
Ecrit mailing list
Ecrit at ietf.org
https://www1.ietf.org/mailman/listinfo/ecrit