RFC 5582: Location-to-URL Mapping Architecture and Framework

This document describes an architecture for a global, scalable, resilient, and administratively distributed system for mapping geographic location information…

Read RFC 5582 on the RFC Editor

Outgoing relationships (8 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 5222: LoST: A Location-to-Service Translation Protocol
Normative reference — RFC 5031: A Uniform Resource Name (URN) for Emergency and Other Well-Known Services
Normative reference — RFC 5223: Discovering Location-to-Service Translation (LoST) Servers Using the Dynamic Host Configuration Protocol (DHCP)
Informative reference — RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2
Informative reference — RFC 5012: Requirements for Emergency Context Resolution with Internet Technologies
Informative reference — RFC 5069: Security Threats and Requirements for Emergency Call Marking and Mapping
Informative reference — RFC 3528: Mesh-enhanced Service Location Protocol (mSLP)

Incoming relationships (5 related RFCs)

Normatively referenced by — RFC 6451: Location-to-Service Translation (LoST) Protocol Extensions
Informatively referenced by — RFC 7852: Additional Data Related to an Emergency Call
Informatively referenced by — RFC 6739: Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) Protocol
Informatively referenced by — RFC 7840: A Routing Request Extension for the HTTP-Enabled Location Delivery (HELD) Protocol
Informatively referenced by — RFC 8917: The LoST-Validation Straightforward-Naming Authority PoinTeR (S-NAPTR) Application Service Tag