datatracker.ietf.org
Sign in
Version 5.6.2.p5, 2014-08-04
Report a bug

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

Network Working Group                                          T. Hardie
Request for Comments: 5222                                Qualcomm, Inc.
Category: Standards Track                                      A. Newton
                                  American Registry for Internet Numbers
                                                          H. Schulzrinne
                                                     Columbia University
                                                           H. Tschofenig
                                                  Nokia Siemens Networks
                                                             August 2008

            LoST: A Location-to-Service Translation Protocol

Status of This Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

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.

Table of Contents

1.  Introduction .................................................. 3
2.  Terminology and Requirements Notation ......................... 4
3.  Overview of Protocol Usage .................................... 5
4.  LoST Servers and Their Resolution  ............................ 6
5.  The <mapping> Element  ........................................ 7
  5.1.  The Mapping Data Source: 'source', 'sourceId', and
        'lastUpdated' Attributes .................................. 7
  5.2.  Mapping Validity:  The 'expires' Attribute ................ 8
  5.3.  Describing the Service with the <displayName> Element  .... 8
  5.4.  The Mapped Service: The <service> Element ................. 8
  5.5.  Defining the Service Region with the <serviceBoundary>
        Element  .................................................. 9
  5.6.  Service Boundaries by Reference: The
        <serviceBoundaryReference> Element ........................ 9
  5.7.  The Service Number: The <serviceNumber> Element  ......... 10
  5.8.  Service URLs: The <uri> Element  ......................... 10

Hardie, et al.              Standards Track                     [Page 1]
RFC 5222                          LoST                       August 2008

6.  Path of a Request: The <path> Element  ....................... 10
7.  Identifying the Location Element Used for Mapping:
    <locationUsed> ............................................... 11
8.  Mapping a Location and Service to URLs: <findService>  ....... 11
  8.1.  Overview ................................................. 11
  8.2.  Examples ................................................. 11
    8.2.1.  Example Using Geodetic Coordinates ................... 11
    8.2.2.  Civic Address Mapping Example  ....................... 13
  8.3.  Components of the <findService> Request  ................. 15
    8.3.1.  The <location> Element ............................... 15
    8.3.2.  Identifying the Service:  The <service> Element  ..... 16
    8.3.3.  Recursion and Iteration  ............................. 16
    8.3.4.  Service Boundary ..................................... 16
    8.3.5.  Requesting Civic Location Validation ................. 16
  8.4.  Components of the Mapping Response
        <findServiceResponse>  ................................... 18
    8.4.1.  Overview ............................................. 18
    8.4.2.  Civic Address Validation: The <locationValidation>
            Element  ............................................. 19
9.  Retrieving the Service Boundary via <getServiceBoundary> ..... 19
10. List Services: <listServices>  ............................... 21
11. List Services By Location: <listServicesByLocation>  ......... 22
12. Location Profiles  ........................................... 24
  12.1. Location Profile Usage ................................... 25
  12.2. Two-Dimensional Geodetic Profile ......................... 30
  12.3. Basic Civic Profile  ..................................... 31
13. Errors, Warnings, and Redirects  ............................. 32
  13.1. Errors ................................................... 32
  13.2. Warnings ................................................. 34
  13.3. Redirects  ............................................... 36
14. LoST Transport: HTTP ......................................... 36

[include full document text]