RFC 5222: LoST: A Location-to-Service Translation Protocol

This document describes an XML-based protocol for mapping service identifiers and geodetic or civic location information to service contact URIs. In…

Read RFC 5222 on the RFC Editor

Incoming relationships (14 related RFCs)

Updated by, Normatively referenced by — RFC 6848: Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF-LO)
Updated by, Normatively referenced by — RFC 8917: The LoST-Validation Straightforward-Naming Authority PoinTeR (S-NAPTR) Application Service Tag
Updated by — RFC 9036: Changing the Location-to-Service Translation (LoST) Location Profiles Registry Policy
Normatively referenced by — RFC 5582: Location-to-URL Mapping Architecture and Framework
Normatively referenced by — RFC 5964: Specifying Holes in Location-to-Service Translation (LoST) Service Boundaries
Normatively referenced by — RFC 6739: Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) Protocol
Normatively referenced by — RFC 6444: Location Hiding: Problem Statement and Requirements
Normatively referenced by — RFC 6451: Location-to-Service Translation (LoST) Protocol Extensions
Informatively referenced by — RFC 5986: Discovering the Local Location Information Server (LIS)
Informatively referenced by — RFC 5223: Discovering Location-to-Service Translation (LoST) Servers Using the Dynamic Host Configuration Protocol (DHCP)
Informatively referenced by — RFC 7090: Public Safety Answering Point (PSAP) Callback
Informatively referenced by — RFC 8876: Non-interactive Emergency Calls
Informatively referenced by — RFC 7459: Representation of Uncertainty and Confidence in the Presence Information Data Format Location Object (PIDF-LO)
Informatively referenced by — RFC 7840: A Routing Request Extension for the HTTP-Enabled Location Delivery (HELD) Protocol