Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) Protocol
Metadata
- Publisher
- IETF
- Doc Type
- Experimental
- Pages
- 25
- Abstract
- 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 <mapping> 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 <mapping> elements between two entities. Exchanging cached <mapping> elements, i.e., non-authoritative elements, is possible but not envisioned. Even though the <mapping> 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.
- Publication Date
- 2012-10-01
- Status Note
- Experimental
- DOI
10.17487/RFC6739- Link
- https://doi.org/10.17487/RFC6739
- Author(s)
- Henning SchulzrinneHannes Tschofenig
Latest version of IETF RFC 6739
Document Versions — IETF RFC 6739
-
▶ IETF RFC 6739 (2012-10-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 2246 [Superseded*]
- IETF RFC 2818 [Superseded*]
- IETF RFC 3023 [Superseded*]
- IETF RFC 4288 [Superseded*]
- IETF RFC 5222 [Active*]
- IETF RFC 5246 [Superseded*]
- W3C XML DSig Core [Superseded]
Bibliographic Reference(s)
- IETF RFC 5012 [Active*]
- RFC5582 — 25 EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC6739.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 6739, Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) Protocol. Available at https://doi.org/10.17487/RFC6739
Snippet:
IETF RFC 6739, Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) Protocol. Available at https://doi.org/10.17487/RFC6739
HTML (ISO 690 compliant)
Preview:
IETF RFC 6739, Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) Protocol. Available at https://doi.org/10.17487/RFC6739
Snippet:
<span class="citation"><cite>IETF RFC 6739</cite>, Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) Protocol. Available at <a href="https://doi.org/10.17487/RFC6739" target="_blank" rel="noopener">https://doi.org/10.17487/RFC6739</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 6739, Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) Protocol
doi: 10.17487/RFC6739
url: https://doi.org/10.17487/RFC6739
doi: 10.17487/RFC6739
url: https://doi.org/10.17487/RFC6739
Snippet:
<li> <cite id="bib-rfc6739">IETF RFC 6739</cite>, Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) Protocol <span class="doi">10.17487/RFC6739</span> </li>
Referenced By
- IETF RFC 8996 [Active*]