As used for emergency services, I assume LoST produces the following
A. ) given location as input, LoST returns service identifier (e.g.
B. ) given location + service identifier as input, LoST returns PSAP URI
C. ) given location + service identifier as input, LoST returns PSAP URI
+ dial string
D. ) given location + service identifier as input, LoST returns PSAP URI
+ dial string + PSAP_preference_info
Are there more cases?
>From: Henning Schulzrinne [mailto:hgs@xxxxxxxxxxxxxxx]
>Sent: Wednesday, May 17, 2006 2:56 PM
>To: Spencer Dawkins
>Subject: Re: [Ecrit] Re: Commments I.D-ecrit-service-urn-03
>LoST maps location and service URN to a set of answers. Thus, you have
>query to LoST: "I'm in Tokyo, Japan and interested in the fire brigade"
>response: "Your dialstring is XYZ and the PSAP URL is
>Spencer Dawkins wrote:
>> Having looked at this yesterday, "dialstring" is part of the LoST
>> RESPONSE example in the current LoST draft, not part of the request,
>> so I think we are confused here (which may be as simple as the LoST
>> draft being out of phase with what people think, or may be
>> Please check my math in draft-hardie-ecrit-lost-00.txt.
>> Comments? It's "location *to* service translation", right? :-)
>Ecrit mailing list
Ecrit mailing list