Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) Protocol
Draft of message to be sent after approval:
From: The IESG <firstname.lastname@example.org> To: IETF-Announce <email@example.com> Cc: RFC Editor <firstname.lastname@example.org>, ecrit mailing list <email@example.com>, ecrit chair <firstname.lastname@example.org> Subject: Document Action: 'Synchronizing Location-to-Service Translation (LoST) Protocol based Service Boundaries and Mapping Elements' to Experimental RFC (draft-ietf-ecrit-lost-sync-18.txt) The IESG has approved the following document: - 'Synchronizing Location-to-Service Translation (LoST) Protocol based Service Boundaries and Mapping Elements' (draft-ietf-ecrit-lost-sync-18.txt) as Experimental RFC This document is the product of the Emergency Context Resolution with Internet Technologies Working Group. The IESG contact persons are Robert Sparks and Gonzalo Camarillo. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-ecrit-lost-sync/
Technical Summary The Location-to-Service Translation (LoST) protocol (RFC5222) is an XML-based protocol for mapping service identifiers and geodetic or civic location information to service URIs and service boundaries. In particular, it can be used to determine the location-appropriate Public Safety Answering Point (PSAP) for emergency services. The main data structure, the <mapping> element, used for encapsulating information about service boundaries is defined in the LoST protocol specification and circumscribes the region within which all locations map to the same service Uniform Resource Identifier (URI) or set of URIs for a given service. This document defines an XML protocol to exchange these mappings between two nodes. This mechanism is designed for the exchange of authoritative <mapping> elements between two entities. Exchanging cached <mapping> elements, i.e. non-authoritative elements, is possible but not envisioned. In any case, this document can also be used without the LoST protocol even though the format of the <mapping> element is re-used from the LoST specification. Working Group Summary There is consensus in the WG to publish this document. Document Quality The LoST Sync protocol was implemented during the development of RFC 5222 specification. This extension has been tested in various company-internal implementations, as reported to the wg chairs. Two open source implementations were made available by Columbia University and by Goettingen University. Interoperability tests between them have been made. The code produced by Goettingen University is available (at the time of this announcement) at: http://sourceforge.net/projects/heldandlost/files/ The LoST specification has experienced extensive review, including reviews by other SDOs.