Synchronizing Location-to-Service Translation (LoST) Protocol based Service Boundaries and Mapping Elements
draft-ietf-ecrit-lost-sync-17

The information below is for an old version of the document
Document Type Active Internet-Draft (ecrit WG)
Last updated 2012-04-26 (latest revision 2012-03-11)
Replaces draft-schulzrinne-ecrit-lost-sync
Stream IETF
Intended RFC status Experimental
Formats plain text pdf html
Stream WG state WG Document
Consensus Unknown
Document shepherd None
IESG IESG state IESG Evaluation::Revised I-D Needed
Telechat date
Needs a YES.
Responsible AD Robert Sparks
IESG note Marc Linsner (mlinsner@cisco.com) is the document shepherd.
Send notices to ecrit-chairs@tools.ietf.org, draft-ietf-ecrit-lost-sync@tools.ietf.org
ECRIT                                                     H. Schulzrinne
Internet-Draft                                       Columbia University
Intended status: Experimental                              H. Tschofenig
Expires: September 12, 2012                       Nokia Siemens Networks
                                                          March 11, 2012

  Synchronizing Location-to-Service Translation (LoST) Protocol based
                Service Boundaries and Mapping Elements
                   draft-ietf-ecrit-lost-sync-17.txt

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 main data structure, the <mapping> element, used for
   encapsulating information about service boundaries is defined in the
   LoST protocol specification 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.  In any case, this document can also be
   used without the LoST protocol even though the format of the
   <mapping> element is re-used from the LoST specification.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Schulzrinne & Tschofenig  Expires September 12, 2012            [Page 1]
Internet-Draft                  LoST Sync                     March 2012

   This Internet-Draft will expire on September 12, 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.

Schulzrinne & Tschofenig  Expires September 12, 2012            [Page 2]
Internet-Draft                  LoST Sync                     March 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . . 10
   3.  Querying for Mappings with a <getMappingsRequest> /
       <getMappingsResponse> Exchange . . . . . . . . . . . . . . . . 11
     3.1.  Behavior of the LoST Sync Destination  . . . . . . . . . . 11
     3.2.  Behavior of the LoST Sync Source . . . . . . . . . . . . . 11
     3.3.  Examples . . . . . . . . . . . . . . . . . . . . . . . . . 12
   4.  Pushing Mappings via <pushMappings> and
       <pushMappingsResponse> . . . . . . . . . . . . . . . . . . . . 14
     4.1.  Behavior of the LoST Sync Source . . . . . . . . . . . . . 14
     4.2.  Behavior of the LoST Sync Destination  . . . . . . . . . . 14
     4.3.  Example  . . . . . . . . . . . . . . . . . . . . . . . . . 15
   5.  Transport  . . . . . . . . . . . . . . . . . . . . . . . . . . 19
   6.  RelaxNG  . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
   7.  Operational Considerations . . . . . . . . . . . . . . . . . . 22
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 23
   9.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 24
     9.1.  Content-type registration for
           'application/lostsync+xml' . . . . . . . . . . . . . . . . 24
Show full document text