draft-ietf-ecrit-lost-sync-09.txt   draft-ietf-ecrit-lost-sync-10.txt 
ECRIT H. Schulzrinne ECRIT H. Schulzrinne
Internet-Draft Columbia University Internet-Draft Columbia University
Intended status: Experimental H. Tschofenig Intended status: Experimental H. Tschofenig
Expires: September 7, 2010 Nokia Siemens Networks Expires: September 30, 2011 Nokia Siemens Networks
March 6, 2010 March 29, 2011
Synchronizing Location-to-Service Translation (LoST) Protocol based Synchronizing Location-to-Service Translation (LoST) Protocol based
Service Boundaries and Mapping Elements Service Boundaries and Mapping Elements
draft-ietf-ecrit-lost-sync-09.txt draft-ietf-ecrit-lost-sync-10.txt
Abstract Abstract
The Location-to-Service Translation (LoST) protocol is an XML-based The Location-to-Service Translation (LoST) protocol is an XML-based
protocol for mapping service identifiers and geodetic or civic protocol for mapping service identifiers and geodetic or civic
location information to service URIs and service boundaries. In location information to service URIs and service boundaries. In
particular, it can be used to determine the location-appropriate particular, it can be used to determine the location-appropriate
Public Safety Answering Point (PSAP) for emergency services. Public Safety Answering Point (PSAP) for emergency services.
The main data structure, the <mapping> element, used for The main data structure, the <mapping> element, used for
skipping to change at page 1, line 37 skipping to change at page 1, line 37
This document defines an XML protocol to exchange these mappings This document defines an XML protocol to exchange these mappings
between two nodes. This mechanism is designed for the exchange of between two nodes. This mechanism is designed for the exchange of
authoritative <mapping> elements between two entities. Exchanging authoritative <mapping> elements between two entities. Exchanging
cached <mapping> elements, i.e. non-authoritative elements, is cached <mapping> elements, i.e. non-authoritative elements, is
possible but not envisioned. In any case, this document can also be possible but not envisioned. In any case, this document can also be
used without the LoST protocol even though the format of the used without the LoST protocol even though the format of the
<mapping> element is re-used from the LoST specification. <mapping> element is re-used from the LoST specification.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on September 30, 2011.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 7, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 10 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 10
3. Querying for Mappings with a <getMappingsRequest> / 3. Querying for Mappings with a <getMappingsRequest> /
<getMappingsResponse> Exchange . . . . . . . . . . . . . . . . 11 <getMappingsResponse> Exchange . . . . . . . . . . . . . . . . 11
3.1. Behavior of the LoST Sync Source . . . . . . . . . . . . . 11 3.1. Behavior of the LoST Sync Source . . . . . . . . . . . . . 11
3.2. Behavior of the LoST Sync Source . . . . . . . . . . . . . 11 3.2. Behavior of the LoST Sync Source . . . . . . . . . . . . . 11
3.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . 12 3.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . 12
 End of changes. 7 change blocks. 
16 lines changed or deleted 10 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/