LoST: A Location-to-Service Translation Protocol

Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) Protocol

“…Only the <badRequest>, <forbidden>, <internalError>, and <serverTimeout> errors, defined in [RFC5222], are used by this specification. Neither the <redirect> nor the <warnings> messages are reused by this message.…”

“…If it does not keep state information, then it always has to push the complete data set. As discussed in Section 5.1 of [RFC5222], <mapping> elements are identified by the 'source', 'sourceID', and 'lastUpdated' attributes. A mapping is considered the same if these three attributes match.…”

“…With this specification, a successful response message returns no additional elements, whereas an <errors> response is returned in the response message if the request failed. Only the <badRequest>, <forbidden>, <internalError>, or <serverTimeout> errors defined in Section 13.1 of [RFC5222] are used. The <redirect> and <warnings> messages are not used for this query/response.…”

“…Note: In order to avoid copying pattern definitions from the LoST Regular Language for XML Next Generation (RELAX NG) schema [RFC5222] to this document, we include it as "lost.rng" (XML syntax) in the RELAX NG schema below. LoST Sync October 2012 </define> <define name="pushMappingsResponse"> <element name="pushMappingsResponse"> <ref name="extensionPoint"/> </element> </define> <define name="getMappingsRequest"> <element name="getMappingsRequest"> <choice> <ref name="exists"></ref> <ref name="extensionPoint"/> </choice> </element> </define> <define name="exists"> <element name="exists"> <oneOrMore> <element name="mapping-fingerprint"> <attribute name="source"> <data type="token"/> </attribute> <attribute name="sourceId"> <data type="token"/> </attribute> <attribute name="lastUpdated"> <data type="dateTime"/> </attribute> <ref name="extensionPoint"/> </element> </oneOrMore> </element> </define> <define name="getMappingsResponse"> <element name="getMappingsResponse"> <oneOrMore> <ref name="mapping"/> </oneOrMore> <ref name="extensionPoint"/> </element> </define> <!--error messages --> <define name="notDeleted"> <element name="notDeleted"> <ref name="basicException"/> <oneOrMore> <ref name="mapping"/> </oneOrMore> </element> </define> </grammar>…”

“…For this purpose each PSAP discloses one or more service boundaries so that this information can be used to select the appropriate PSAP and to route the call to it. RFC 5222 [RFC5222] defines this data structure in the following way:…”