RFC 5582: Location-to-URL Mapping Architecture and Framework
In plain English — editorial summary, not part of the RFC
This document describes an architecture for a global, scalable, resilient, and administratively distributed system for mapping geographic location information to URLs, using the Location-to-Service Translation (LoST) protocol. The architecture generalizes well-known approaches found in hierarchical lookup systems such as DNS. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5582
- Published
- September 2009
- Authors
- H. Schulzrinne
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- art
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5012Requirements for Emergency Context Resolution with Internet TechnologiesCurrent
January 2008
- RFC 6881Best Current Practice for Communications Services in Support of Emergency CallingUpdated
March 2013
- RFC 5964Specifying Holes in Location-to-Service Translation (LoST) Service BoundariesCurrent
August 2010
- RFC 5069Security Threats and Requirements for Emergency Call Marking and MappingCurrent
January 2008
- RFC 5031A Uniform Resource Name (URN) for Emergency and Other Well-Known ServicesUpdated
January 2008
- RFC 7845Ogg Encapsulation for the Opus Audio CodecUpdated
April 2016
- RFC 4934Extensible Provisioning Protocol (EPP) Transport Over TCPObsoleted
May 2007
- RFC 6970Universal Plug and Play (UPnP) Internet Gateway Device - Port Control Protocol Interworking Function (IGD-PCP IWF)Current
July 2013
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?