LoST: A Location-to-Service Translation Protocol
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 69
- Abstract
- This document describes an XML-based protocol for mapping service identifiers and geodetic or civic location information to service contact URIs. In particular, it can be used to determine the location-appropriate Public Safety Answering Point (PSAP) for emergency services. [STANDARDS-TRACK]
- Publication Date
- 2008-08-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC5222- Link
- https://doi.org/10.17487/RFC5222
- Author(s)
- Ted HardieAndy NewtonHenning SchulzrinneHannes Tschofenig
- Keyword(s)
- Emergency Services
Latest version of IETF RFC 5222
Document Versions — IETF RFC 5222
-
▶ IETF RFC 5222 (2008-08-01)THIS DOC [ACTIVE] [LATEST VERSION]
Amended by:
- RFC6848 NOT IN REGISTRY
- RFC8917 NOT IN REGISTRY
- RFC9036 NOT IN REGISTRY
Normative Reference(s)
- Reed, C. and M. Thomson, "GML 3.1.1 PIDF-LO Shape Application Schema for use by the Internet Engineering Task Force (IETF)", Candidate OpenGIS Implementation Specification , December 2006. EXTERNAL
- Cox, S., Daisey, P., Lake, R., Portele, C., and A. Whiteside, "Geographic information - Geography Markup Language (GML)", OGC Standard OpenGIS 03-105r1, April 2004. EXTERNAL
- IETF RFC 2119 [Active*]
- IETF RFC 2616 [Superseded*]
- IETF RFC 2818 [Superseded*]
- IETF RFC 3023 [Superseded*]
- IETF RFC 4119 [Active*]
- IETF RFC 4288 [Superseded*]
- RFC4848 — 8 EXTERNAL
- IETF RFC 5031 [Active*]
- IETF RFC 5139 [Active*]
- IETF RFC 5226 [Superseded*]
Bibliographic Reference(s)
- IETF.draft-ietf-ecrit-lost — 24 EXTERNAL
- Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV PIDF-LO Usage Clarification, Considerations and Recommendations", Work in Progress, February 2008. EXTERNAL
- Rosen, B. and J. Polk, "Best Current Practice for Communications Services in support of Emergency Calling", Work in Progress, February 2008. EXTERNAL
- Schulzrinne, H., "Location-to-URL Mapping Architecture and Framework", Work in Progress, September 2007. EXTERNAL
- IETF RFC 3261 [Active*]
- IETF RFC 3833 [Active*]
- IETF RFC 3921 [Superseded*]
- IETF RFC 3958 [Active*]
- IETF RFC 3966 [Active*]
- IETF RFC 4033 [Active*]
- IETF RFC 5012 [Active*]
- IETF RFC 5069 [Active*]
- IETF RFC 5223 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5222.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 5222, LoST: A Location-to-Service Translation Protocol. Available at https://doi.org/10.17487/RFC5222
Snippet:
IETF RFC 5222, LoST: A Location-to-Service Translation Protocol. Available at https://doi.org/10.17487/RFC5222
HTML (ISO 690 compliant)
Preview:
IETF RFC 5222, LoST: A Location-to-Service Translation Protocol. Available at https://doi.org/10.17487/RFC5222
Snippet:
<span class="citation"><cite>IETF RFC 5222</cite>, LoST: A Location-to-Service Translation Protocol. Available at <a href="https://doi.org/10.17487/RFC5222" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5222</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 5222, LoST: A Location-to-Service Translation Protocol
doi: 10.17487/RFC5222
url: https://doi.org/10.17487/RFC5222
doi: 10.17487/RFC5222
url: https://doi.org/10.17487/RFC5222
Snippet:
<li> <cite id="bib-rfc5222">IETF RFC 5222</cite>, LoST: A Location-to-Service Translation Protocol <span class="doi">10.17487/RFC5222</span> </li>
Referenced By
- IETF RFC 5223 [Active*]
- IETF RFC 6280 [Active*]
- IETF RFC 6443 [Active*]
- IETF RFC 6444 [Active*]
- IETF RFC 6739 [Active*]
- IETF RFC 6881 [Active*]
- IETF RFC 7406 [Active*]