Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) Protocol
RFC 6739

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 16
• 17
• 18

Internet Engineering Task Force (IETF)                    H. Schulzrinne
Request for Comments: 6739                           Columbia University
Category: Experimental                                     H. Tschofenig
ISSN: 2070-1721                                   Nokia Siemens Networks
                                                            October 2012

  Synchronizing Service Boundaries and <mapping> Elements Based on the
            Location-to-Service Translation (LoST) Protocol

Abstract

   The Location-to-Service Translation (LoST) protocol is an XML-based
   protocol for mapping service identifiers and geodetic or civic
   location information to service URIs and service boundaries.  In
   particular, it can be used to determine the location-appropriate
   Public Safety Answering Point (PSAP) for emergency services.

   The <mapping> element in the LoST protocol specification encapsulates
   information about service boundaries and circumscribes the region
   within which all locations map to the same service Uniform Resource
   Identifier (URI) or set of URIs for a given service.

   This document defines an XML protocol to exchange these mappings
   between two nodes.  This mechanism is designed for the exchange of
   authoritative <mapping> elements between two entities.  Exchanging
   cached <mapping> elements, i.e., non-authoritative elements, is
   possible but not envisioned.  Even though the <mapping> element
   format is reused from the LoST specification, the mechanism in this
   document can be used without the LoST protocol.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for examination, experimental implementation, and
   evaluation.

   This document defines an Experimental Protocol for the Internet
   community.  This document is a product of the Internet Engineering
   Task Force (IETF).  It represents the consensus of the IETF
   community.  It has received public review and has been approved for
   publication by the Internet Engineering Steering Group (IESG).  Not
   all documents approved by the IESG are a candidate for any level of
   Internet Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6739.

Schulzrinne & Tschofenig      Experimental                      [Page 1]
RFC 6739                        LoST Sync                   October 2012

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  A Motivating Example . . . . . . . . . . . . . . . . . . . . .  4
   4.  Querying for Mappings with a
       <getMappingsRequest>/<getMappingsResponse> Exchange  . . . . .  9
     4.1.  Behavior of the LoST Sync Destination  . . . . . . . . . .  9
     4.2.  Behavior of the LoST Sync Source . . . . . . . . . . . . . 10
     4.3.  Examples . . . . . . . . . . . . . . . . . . . . . . . . . 10
   5.  Pushing Mappings via <pushMappings> and
       <pushMappingsResponse> . . . . . . . . . . . . . . . . . . . . 12
     5.1.  Behavior of the LoST Sync Source . . . . . . . . . . . . . 12
     5.2.  Behavior of the LoST Sync Destination  . . . . . . . . . . 13
     5.3.  Example  . . . . . . . . . . . . . . . . . . . . . . . . . 14
   6.  Transport  . . . . . . . . . . . . . . . . . . . . . . . . . . 16
   7.  RELAX NG . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
   8.  Operational Considerations . . . . . . . . . . . . . . . . . . 19
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 20
   10. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 21
     10.1. Media Type Registration  . . . . . . . . . . . . . . . . . 21
     10.2. LoST Sync RELAX NG Schema Registration . . . . . . . . . . 22
     10.3. LoST Synchronization Namespace Registration  . . . . . . . 22
   11. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 23
   12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 24
     12.1. Normative References . . . . . . . . . . . . . . . . . . . 24
     12.2. Informative References . . . . . . . . . . . . . . . . . . 24