< draft-ietf-ecrit-lost-sync-16.txt		draft-ietf-ecrit-lost-sync-17.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: July 16, 2012 Nokia Siemens Networks		Expires: September 12, 2012 Nokia Siemens Networks
	January 13, 2012		March 11, 2012
	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-16.txt		draft-ietf-ecrit-lost-sync-17.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 2, line 4 ¶		skipping to change at page 2, line 4 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		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."
	This Internet-Draft will expire on July 16, 2012.		This Internet-Draft will expire on September 12, 2012.
	Copyright Notice		Copyright Notice
	Copyright (c) 2012 IETF Trust and the persons identified as the		Copyright (c) 2012 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
	skipping to change at page 6, line 5 ¶		skipping to change at page 6, line 5 ¶
	LoST Server 'East': This LoST server would contain all the mappings		LoST Server 'East': This LoST server would contain all the mappings
	to PSAPs covering one half of the country.		to PSAPs covering one half of the country.
	Additionally, the LoST server aggregates all the information it		Additionally, the LoST server aggregates all the information it
	has and provides an abstracted view towards the Forest Guide		has and provides an abstracted view towards the Forest Guide
	indicating that it is responsible for a certain area (for a given		indicating that it is responsible for a certain area (for a given
	service, and for a given location profile). Such a mapping could		service, and for a given location profile). Such a mapping could
	have the following structure:		have the following structure:
	<?xml version="1.0" encoding="UTF-8"?>
	<mapping		<mapping
	xmlns="urn:ietf:params:xml:ns:lost1"		xmlns="urn:ietf:params:xml:ns:lost1"
	xmlns:gml="http://www.opengis.net/gml"		xmlns:gml="http://www.opengis.net/gml"
	expires="2009-01-01T01:44:33Z"		expires="2009-01-01T01:44:33Z"
	lastUpdated="2009-12-01T01:00:00Z"		lastUpdated="2009-12-01T01:00:00Z"
	source="east-austria.lost-example.com"		source="east-austria.lost-example.com"
	sourceId="e8b05a41d8d1415b80f2cdbb96ccf109">		sourceId="e8b05a41d8d1415b80f2cdbb96ccf109">
	<displayName xml:lang="en">LoST Server 'East'</displayName>		<displayName xml:lang="en">LoST Server 'East'</displayName>
	<service>urn:service:sos</service>		<service>urn:service:sos</service>
	<serviceBoundary profile="geodetic-2d">		<serviceBoundary profile="geodetic-2d">
	skipping to change at page 7, line 5 ¶		skipping to change at page 7, line 5 ¶
	LoST Server 'Vienna': This LoST server would contain all the		LoST Server 'Vienna': This LoST server would contain all the
	mappings to PSAPs in the area of Vienna.		mappings to PSAPs in the area of Vienna.
	Forest Guide Finland: In our example we assume that Finland would		Forest Guide Finland: In our example we assume that Finland would
	deploy a single ESRP for the entire country as their IP-based		deploy a single ESRP for the entire country as their IP-based
	emergency services solution. There is only a single LoST server		emergency services solution. There is only a single LoST server
	and it is co-located with the Forest Guide, as shown in Figure 1.		and it is co-located with the Forest Guide, as shown in Figure 1.
	The mapping data this FG would distribute via LoST sync is shown		The mapping data this FG would distribute via LoST sync is shown
	in Figure 3.		in Figure 3.
	<?xml version="1.0" encoding="UTF-8"?>
	<mapping xmlns="urn:ietf:params:xml:ns:lost1"		<mapping xmlns="urn:ietf:params:xml:ns:lost1"
	expires="2007-01-01T01:44:33Z"		expires="2007-01-01T01:44:33Z"
	lastUpdated="2006-11-01T01:00:00Z"		lastUpdated="2006-11-01T01:00:00Z"
	source="finland.lost-example.com"		source="finland.lost-example.com"
	sourceId="7e3f40b098c711dbb6060800200c9a66">		sourceId="7e3f40b098c711dbb6060800200c9a66">
	<displayName xml:lang="en">Finland ESRP</displayName>		<displayName xml:lang="en">Finland ESRP</displayName>
	<service>urn:service:sos</service>		<service>urn:service:sos</service>
	<serviceBoundary profile="civic">		<serviceBoundary profile="civic">
	<civicAddress		<civicAddress
	xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr">		xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr">
	<country>FI</country>		<country>FI</country>
	</civicAddress>		</civicAddress>
	</serviceBoundary>		</serviceBoundary>
	<uri/>		<uri/>
	</mapping>		</mapping>
	Figure 3: Forest Guide Finland Mapping Example		Figure 3: Forest Guide Finland Mapping XML Snippet
	An example mapping stored at the co-located LoST server is shown		An example mapping stored at the co-located LoST server is shown
	in Figure 4.		in Figure 4.
	<?xml version="1.0" encoding="UTF-8"?>
	<mapping xmlns="urn:ietf:params:xml:ns:lost1"		<mapping xmlns="urn:ietf:params:xml:ns:lost1"
	expires="2007-01-01T01:44:33Z"		expires="2007-01-01T01:44:33Z"
	lastUpdated="2006-11-01T01:00:00Z"		lastUpdated="2006-11-01T01:00:00Z"
	source="finland.lost-example.com"		source="finland.lost-example.com"
	sourceId="7e3f40b098c711dbb6060800200c9a66">		sourceId="7e3f40b098c711dbb6060800200c9a66">
	<displayName xml:lang="en">Finland ESRP</displayName>		<displayName xml:lang="en">Finland ESRP</displayName>
	<service>urn:service:sos</service>		<service>urn:service:sos</service>
	<serviceBoundary profile="civic">		<serviceBoundary profile="civic">
	<civicAddress		<civicAddress
	xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr">		xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr">
	<country>FI</country>		<country>FI</country>
	</civicAddress>		</civicAddress>
	</serviceBoundary>		</serviceBoundary>
	<uri>sip:esrp@finland-example.com</uri>		<uri>sip:esrp@finland-example.com</uri>
	<uri>xmpp:esrp@finland-example.com</uri>		<uri>xmpp:esrp@finland-example.com</uri>
	<serviceNumber>112</serviceNumber>		<serviceNumber>112</serviceNumber>
	</mapping>		</mapping>
	Figure 4: Forest Guide Finland / Co-Located LoST Server Mapping		Figure 4: Forest Guide Finland / Co-Located LoST Server Mapping
	Example		XML Snippet
	The LoST sync mechanism described in this document could be run		The LoST sync mechanism described in this document could be run
	between the two Forest Guides. Thereby, the three mappings stored in		between the two Forest Guides. Thereby, the three mappings stored in
	the Austria FG are sent to the FG Finland and a single mapping in the		the Austria FG are sent to the FG Finland and a single mapping in the
	FG Finland is sent to the FG Austria. Additionally, the three		FG Finland is sent to the FG Austria. Additionally, the three
	Austrian LoST servers could utilize LoST sync to inform the Austrian		Austrian LoST servers could utilize LoST sync to inform the Austrian
	FG about their boundaries. These three authoritative mapping servers		FG about their boundaries. These three authoritative mapping servers
	in Austria would be responsible to maintain their own mapping		in Austria would be responsible to maintain their own mapping
	information. Since the amount of data being exchanged is small and		information. Since the amount of data being exchanged is small and
	the expected rate of change is low the nodes are configured to always		the expected rate of change is low the nodes are configured to always
End of changes. 8 change blocks.
	9 lines changed or deleted		6 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/