Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) Protocol
RFC 6739
Revision differences
Document history
Date | By | Action |
---|---|---|
2020-01-21
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'The Location-to-Service Translation (LoST) protocol is an XML-based protocol for mapping service identifiers and geodetic or … Received changes through RFC Editor sync (changed abstract to 'The Location-to-Service Translation (LoST) protocol 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 element in the LoST protocol specification encapsulates information about service boundaries 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 elements between two entities. Exchanging cached elements, i.e., non-authoritative elements, is possible but not envisioned. Even though the element format is reused from the LoST specification, the mechanism in this document can be used without the LoST protocol. This document defines an Experimental Protocol for the Internet community.') |
2016-11-30
|
(System) | Closed request for Last Call review by GENART with state 'Unknown' |
2015-10-14
|
(System) | Notify list changed from ecrit-chairs@ietf.org, draft-ietf-ecrit-lost-sync@ietf.org to (None) |
2012-10-25
|
(System) | RFC published |