Debian Codegraph @

rfc6739.html

raw
1 <pre>Internet Engineering Task Force (IETF) H. Schulzrinne
2 Request for Comments: 6739 Columbia University
3 Category: Experimental H. Tschofenig
4 ISSN: 2070-1721 Nokia Siemens Networks
5 October 2012
6
7
8 <span class="h1">Synchronizing Service Boundaries and &lt;mapping&gt; Elements Based on the</span>
9 <span class="h1">Location-to-Service Translation (LoST) Protocol</span>
10
11 Abstract
12
13 The Location-to-Service Translation (LoST) protocol is an XML-based
14 protocol for mapping service identifiers and geodetic or civic
15 location information to service URIs and service boundaries. In
16 particular, it can be used to determine the location-appropriate
17 Public Safety Answering Point (PSAP) for emergency services.
18
19 The &lt;mapping&gt; element in the LoST protocol specification encapsulates
20 information about service boundaries and circumscribes the region
21 within which all locations map to the same service Uniform Resource
22 Identifier (URI) or set of URIs for a given service.
23
24 This document defines an XML protocol to exchange these mappings
25 between two nodes. This mechanism is designed for the exchange of
26 authoritative &lt;mapping&gt; elements between two entities. Exchanging
27 cached &lt;mapping&gt; elements, i.e., non-authoritative elements, is
28 possible but not envisioned. Even though the &lt;mapping&gt; element
29 format is reused from the LoST specification, the mechanism in this
30 document can be used without the LoST protocol.
31
32 Status of This Memo
33
34 This document is not an Internet Standards Track specification; it is
35 published for examination, experimental implementation, and
36 evaluation.
37
38 This document defines an Experimental Protocol for the Internet
39 community. This document is a product of the Internet Engineering
40 Task Force (IETF). It represents the consensus of the IETF
41 community. It has received public review and has been approved for
42 publication by the Internet Engineering Steering Group (IESG). Not
43 all documents approved by the IESG are a candidate for any level of
44 Internet Standard; see <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
45
46 Information about the current status of this document, any errata,
47 and how to provide feedback on it may be obtained at
48 <a href="http://www.rfc-editor.org/info/rfc6739">http://www.rfc-editor.org/info/rfc6739</a>.
49
50
51
52 <span class="grey">Schulzrinne &amp; Tschofenig Experimental [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc6739">RFC 6739</a> LoST Sync October 2012</span>
55
56
57 Copyright Notice
58
59 Copyright (c) 2012 IETF Trust and the persons identified as the
60 document authors. All rights reserved.
61
62 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
63 Provisions Relating to IETF Documents
64 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
65 publication of this document. Please review these documents
66 carefully, as they describe your rights and restrictions with respect
67 to this document. Code Components extracted from this document must
68 include Simplified BSD License text as described in Section 4.e of
69 the Trust Legal Provisions and are provided without warranty as
70 described in the Simplified BSD License.
71
72 Table of Contents
73
74 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
75 <a href="#section-2">2</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
76 <a href="#section-3">3</a>. A Motivating Example . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
77 4. Querying for Mappings with a
78 &lt;getMappingsRequest&gt;/&lt;getMappingsResponse&gt; Exchange . . . . . <a href="#page-9">9</a>
79 <a href="#section-4.1">4.1</a>. Behavior of the LoST Sync Destination . . . . . . . . . . <a href="#page-9">9</a>
80 <a href="#section-4.2">4.2</a>. Behavior of the LoST Sync Source . . . . . . . . . . . . . <a href="#page-10">10</a>
81 <a href="#section-4.3">4.3</a>. Examples . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
82 5. Pushing Mappings via &lt;pushMappings&gt; and
83 &lt;pushMappingsResponse&gt; . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
84 <a href="#section-5.1">5.1</a>. Behavior of the LoST Sync Source . . . . . . . . . . . . . <a href="#page-12">12</a>
85 <a href="#section-5.2">5.2</a>. Behavior of the LoST Sync Destination . . . . . . . . . . <a href="#page-13">13</a>
86 <a href="#section-5.3">5.3</a>. Example . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
87 <a href="#section-6">6</a>. Transport . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
88 <a href="#section-7">7</a>. RELAX NG . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a>
89 <a href="#section-8">8</a>. Operational Considerations . . . . . . . . . . . . . . . . . . <a href="#page-19">19</a>
90 <a href="#section-9">9</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-20">20</a>
91 <a href="#section-10">10</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-21">21</a>
92 <a href="#section-10.1">10.1</a>. Media Type Registration . . . . . . . . . . . . . . . . . <a href="#page-21">21</a>
93 <a href="#section-10.2">10.2</a>. LoST Sync RELAX NG Schema Registration . . . . . . . . . . <a href="#page-22">22</a>
94 <a href="#section-10.3">10.3</a>. LoST Synchronization Namespace Registration . . . . . . . <a href="#page-22">22</a>
95 <a href="#section-11">11</a>. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-23">23</a>
96 <a href="#section-12">12</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-24">24</a>
97 <a href="#section-12.1">12.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-24">24</a>
98 <a href="#section-12.2">12.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-24">24</a>
99
100
101
102
103
104
105
106
107
108 <span class="grey">Schulzrinne &amp; Tschofenig Experimental [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc6739">RFC 6739</a> LoST Sync October 2012</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
114
115 Since the early days of emergency services, there has been a desire
116 to route emergency calls to Public Safety Answering Points (PSAPs)
117 that are nearest to the location of the emergency caller. For this
118 purpose each PSAP discloses one or more service boundaries so that
119 this information can be used to select the appropriate PSAP and to
120 route the call to it. <a href="./rfc5222">RFC 5222</a> [<a href="./rfc5222" title="&quot;LoST: A Location-to-Service Translation Protocol&quot;">RFC5222</a>] defines this data structure
121 in the following way:
122
123 A service boundary circumscribes the region within which all
124 locations map to the same service URI or set of URIs for a given
125 service. A service boundary may consist of several non-contiguous
126 geometric shapes.
127
128 <a href="./rfc5222">RFC 5222</a> [<a href="./rfc5222" title="&quot;LoST: A Location-to-Service Translation Protocol&quot;">RFC5222</a>] also specifies the data structure itself as the
129 &lt;mapping&gt; element.
130
131 This document reuses this existing data structure and defines an XML-
132 based protocol to exchange authoritative service boundaries between
133 two entities, namely, the LoST Sync source and the LoST Sync
134 destination. This protocol can be used whether or not the LoST
135 protocol is used for querying for service boundary information.
136
137 The rest of the document is structured as follows. <a href="#section-3">Section 3</a> starts
138 with an example usage of the LoST protocol. In Sections <a href="#section-4">4</a>, <a href="#section-5">5</a>, <a href="#section-6">6</a>, and
139 7, we describe the protocol semantics, transport considerations, and
140 the schema. Finally, we conclude with operational, security, and
141 IANA considerations in Sections <a href="#section-8">8</a>, <a href="#section-9">9</a>, and <a href="#section-10">10</a>.
142
143 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
144
145 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
146 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
147 document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
148
149 This document reuses terminology introduced by the mapping
150 architecture document [<a href="./rfc5582" title="&quot;Location-to-URL Mapping Architecture and Framework&quot;">RFC5582</a>], such as 'coverage region', 'forest
151 guide', 'mapping', and 'authoritative mapping server'. This document
152 also uses the term 'ESRP', defined in [<a href="./rfc5012" title="&quot;Requirements for Emergency Context Resolution with Internet Technologies&quot;">RFC5012</a>].
153
154 Throughout this document, we use the terms 'LoST Sync source' and
155 'LoST Sync destination' to denote the protocol endpoints of the
156 exchange. The protocol is referred to as 'LoST Sync' within the
157 text.
158
159
160
161
162
163
164 <span class="grey">Schulzrinne &amp; Tschofenig Experimental [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc6739">RFC 6739</a> LoST Sync October 2012</span>
167
168
169 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. A Motivating Example</span>
170
171 The LoST Sync mechanism can, for example, be used in the LoST
172 architecture, as specified in [<a href="./rfc5582" title="&quot;Location-to-URL Mapping Architecture and Framework&quot;">RFC5582</a>]. There, LoST servers
173 cooperate to provide an ubiquitous, globally scalable, and resilient
174 mapping service. In the LoST mapping architecture, LoST servers can
175 peer, i.e., have an ongoing data exchange relationship. Peering
176 relationships are set up manually, based on local policies. A LoST
177 server may peer with any number of other LoST servers. Forest guides
178 peer with other forest guides; authoritative mapping servers peer
179 with forest guides and other authoritative servers, either in the
180 same cluster or above or below them in the tree. Authoritative
181 mapping servers push coverage regions "up" the tree, i.e., from child
182 nodes to parent nodes. The child informs the parent of the
183 geospatial or civic region that it covers for a specific service.
184
185 Consider a hypothetical deployment of LoST in two countries, for
186 example, Austria and Finland. Austria, in our example, runs three
187 authoritative mapping servers labeled as 'East', 'West', and
188 'Vienna', where the former two cover the entire country except for
189 Vienna, which is covered by a separate LoST server. There may be
190 other caching LoST servers run by ISPs, universities, and Voice
191 Service Providers (VSPs), but they are not relevant for this
192 illustration. Finland, on the other hand, decided to only deploy a
193 single LoST server that also acts as a forest guide. For this
194 simplistic illustration, we assume that only one service is
195 available, namely 'urn:service:sos' since otherwise the number of
196 stored mappings would have to be multiplied by the number of used
197 services.
198
199 Figure 1 shows the example deployment.
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220 <span class="grey">Schulzrinne &amp; Tschofenig Experimental [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc6739">RFC 6739</a> LoST Sync October 2012</span>
223
224
225 +---LoST-Sync--&gt;\\ //&lt;--LoST-Sync----+
226 | ----- |
227 | |
228 \/ \/
229 ----- -----
230 // \\ // \\
231 / \ / \
232 | Forest | | Forest |
233 | Guide | | Guide |
234 | Austria | | Finland
235 \ / \ /
236 +---------&gt;\\ //&lt;--------+ \\ //
237 | ----- | -----
238 | /\ | |
239 LoST | LoST //------\\
240 Sync LoST Sync |Co-Located|
241 | Sync | | LoST |
242 \/ | \/ | Server |
243 //----\\ \/ //----\\ \\------//
244 | LoST | //----\\ | LoST |
245 | Server | | LoST | | Server |
246 | 'East' | | Server | |'Vienna'|
247 \\----// | 'West' | \\----//
248 \\----//
249
250 Figure 1: LoST Deployment Example
251
252 The nodes are configured as follows:
253
254 Forest Guide Austria: This forest guide contains mappings for the
255 three authoritative mapping servers (East, West, and Vienna)
256 describing the area for which they are responsible. Note that
257 each mapping contains a service URN, and these mappings point to
258 LoST servers rather than to PSAPs or Emergency Services Routing
259 Proxies (ESRPs).
260
261 LoST Server 'East': This LoST server contains all the mappings to
262 PSAPs covering the eastern part of the country.
263
264 Additionally, the LoST server aggregates all the information it
265 has and provides an abstracted view towards the forest guide
266 indicating that it is responsible for a certain area (for a given
267 service and for a given location profile). For our example, the
268 structure of a mapping is shown below:
269
270
271
272
273
274
275
276 <span class="grey">Schulzrinne &amp; Tschofenig Experimental [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc6739">RFC 6739</a> LoST Sync October 2012</span>
279
280
281 &lt;mapping
282 xmlns="urn:ietf:params:xml:ns:lost1"
283 xmlns:gml="http://www.opengis.net/gml"
284 expires="2009-01-01T01:44:33Z"
285 lastUpdated="2009-12-01T01:00:00Z"
286 source="east-austria.lost-example.com"
287 sourceId="e8b05a41d8d1415b80f2cdbb96ccf109"&gt;
288 &lt;displayName xml:lang="en"&gt;LoST Server 'East'&lt;/displayName&gt;
289 &lt;service&gt;urn:service:sos&lt;/service&gt;
290 &lt;serviceBoundary profile="geodetic-2d"&gt;
291 &lt;gml:Polygon srsName="urn:ogc:def::crs:EPSG::4326"&gt;
292 &lt;gml:exterior&gt;
293 &lt;gml:LinearRing&gt;
294 &lt;gml:pos&gt; ... &lt;/gml:pos&gt;
295 ..... list of coordinates for
296 boundary of LoST server 'East'
297 &lt;gml:pos&gt; ... &lt;/gml:pos&gt;
298 &lt;/gml:LinearRing&gt;
299 &lt;/gml:exterior&gt;
300 &lt;/gml:Polygon&gt;
301 &lt;/serviceBoundary&gt;
302 &lt;uri/&gt;
303 &lt;/mapping&gt;
304
305 Figure 2: Forest Guide Austria Mapping XML Snippet
306
307 Note that the XML code snippet in Figure 2 serves illustrative
308 purposes only and does not validate. As can be seen in this
309 example, the &lt;uri&gt; element is absent, and the 'source' attribute
310 identifies the LoST server, namely "east-austria.lost-
311 example.com".
312
313 The mapping shown above is what is the LoST server "east-
314 austria.lost-example.com" provides to the Austrian forest guide.
315
316 LoST Server 'West': This LoST server contains all the mappings to
317 PSAPs covering the western half of the country.
318
319 LoST Server 'Vienna': This LoST server contains all the mappings to
320 PSAPs for the city of Vienna.
321
322 Forest Guide Finland: In our example, we assume that Finland deploys
323 a single ESRP for the entire country as their IP-based emergency
324 services solution. There is only a single LoST server, and it is
325 co-located with the forest guide, as shown in Figure 1. The
326 mapping data this forest guide (FG) then distributes via LoST Sync
327 is shown in Figure 3.
328
329
330
331
332 <span class="grey">Schulzrinne &amp; Tschofenig Experimental [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc6739">RFC 6739</a> LoST Sync October 2012</span>
335
336
337 &lt;mapping xmlns="urn:ietf:params:xml:ns:lost1"
338 expires="2007-01-01T01:44:33Z"
339 lastUpdated="2006-11-01T01:00:00Z"
340 source="finland.lost-example.com"
341 sourceId="7e3f40b098c711dbb6060800200c9a66"&gt;
342 &lt;displayName xml:lang="en"&gt;Finland ESRP&lt;/displayName&gt;
343 &lt;service&gt;urn:service:sos&lt;/service&gt;
344 &lt;serviceBoundary profile="civic"&gt;
345 &lt;civicAddress
346 xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"&gt;
347 &lt;country&gt;FI&lt;/country&gt;
348 &lt;/civicAddress&gt;
349 &lt;/serviceBoundary&gt;
350 &lt;uri/&gt;
351 &lt;/mapping&gt;
352
353 Figure 3: Forest Guide Finland Mapping XML Snippet
354
355 An example mapping stored at the co-located LoST server is shown
356 in Figure 4.
357
358 &lt;mapping xmlns="urn:ietf:params:xml:ns:lost1"
359 expires="2007-01-01T01:44:33Z"
360 lastUpdated="2006-11-01T01:00:00Z"
361 source="finland.lost-example.com"
362 sourceId="7e3f40b098c711dbb6060800200c9a66"&gt;
363 &lt;displayName xml:lang="en"&gt;Finland ESRP&lt;/displayName&gt;
364 &lt;service&gt;urn:service:sos&lt;/service&gt;
365 &lt;serviceBoundary profile="civic"&gt;
366 &lt;civicAddress
367 xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"&gt;
368 &lt;country&gt;FI&lt;/country&gt;
369 &lt;/civicAddress&gt;
370 &lt;/serviceBoundary&gt;
371 &lt;uri&gt;sip:[email protected]&lt;/uri&gt;
372 &lt;uri&gt;xmpp:[email protected]&lt;/uri&gt;
373 &lt;serviceNumber&gt;112&lt;/serviceNumber&gt;
374 &lt;/mapping&gt;
375
376 Figure 4: Forest Guide Finland / Co-Located LoST Server Mapping
377 XML Snippet
378
379 The LoST Sync mechanism described in this document can be run between
380 the two forest guides. That way, the three mappings stored in the FG
381 Austria are sent to the FG Finland, and a single mapping in the FG
382 Finland is sent to the FG Austria. Additionally, the three Austrian
383 LoST servers could utilize LoST Sync to inform the Austrian FG about
384 their boundaries. These three authoritative mapping servers in
385
386
387
388 <span class="grey">Schulzrinne &amp; Tschofenig Experimental [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc6739">RFC 6739</a> LoST Sync October 2012</span>
391
392
393 Austria would be responsible for maintaining their own mapping
394 information. Since the amount of data being exchanged is small and
395 the expected rate of change is low, the nodes are configured to
396 always exchange all their mapping information whenever a change
397 happens.
398
399 This document defines two types of exchanges, which are best
400 described by the exchange between two nodes as shown in Figures 5 and
401 6. The protocol exchange always runs between a LoST Sync source and
402 a LoST Sync destination. Node A in the examples of Figures 5 and 6
403 has mappings that Node B is going to retrieve. Node A acts as the
404 source for the data and Node B is the destination.
405
406 The &lt;getMappingsRequest&gt; request allows a LoST Sync source to request
407 mappings from a LoST Sync destination.
408
409 +---------+ +---------+
410 | Node B | | Node A |
411 | acting | | acting |
412 | as | | as |
413 | LoST | | LoST |
414 | Sync | | Sync |
415 | Dest. | | Source |
416 +---------+ +---------+
417 | |
418 | |
419 | |
420 | &lt;getMappingsRequest&gt; |
421 |-----------------------------&gt;|
422 | |
423 | &lt;getMappingsResponse&gt; |
424 |&lt;-----------------------------|
425 | |
426 | |
427 | |
428
429 Figure 5: Querying for Mappings with a &lt;getMappingsRequest&gt; Message
430
431 Note that in the exchange illustrated in Figure 5, Node B is issuing
432 the first request and plays the role of the HTTPS client, and Node A
433 plays the role of the HTTPS server.
434
435 In Figure 6, the &lt;pushMappingsRequest&gt; exchange allows a LoST Sync
436 source to push mappings to a LoST Sync destination. In this example,
437 we assume that Node A has been configured maintain state about the
438 mappings it had pushed to Node B.
439
440
441
442
443
444 <span class="grey">Schulzrinne &amp; Tschofenig Experimental [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc6739">RFC 6739</a> LoST Sync October 2012</span>
447
448
449 This document does not define a publish/subscribe mechanism. Such a
450 mechanism would allow Node B to tell Node A what mappings it is
451 interested in. This document also does not define a mechanism for
452 nodes to find out to which other entities mappings have to be pushed.
453
454 +---------+ +---------+
455 | Node A | | Node B |
456 | acting | | acting |
457 | as | | as |
458 | LoST | | LoST |
459 | Sync | | Sync |
460 | Source | | Dest. |
461 +---------+ +---------+
462 | |
463 | |
464 | |
465 | &lt;pushMappingsRequest&gt; |
466 |-----------------------------&gt;|
467 | |
468 | &lt;pushMappingsResponse&gt; |
469 |&lt;-----------------------------|
470 | |
471 | |
472 | |
473
474 Figure 6: Pushing Mappings with a &lt;pushMappingsRequest&gt; Message
475
476 Node A issuing the first request in Figure 6 plays the role of the
477 HTTPS client, and Node B plays the role of the HTTPS server.
478
479 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Querying for Mappings with a &lt;getMappingsRequest&gt;/</span>
480 &lt;getMappingsResponse&gt; Exchange
481
482 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Behavior of the LoST Sync Destination</span>
483
484 A LoST Sync destination has two ways to retrieve &lt;mapping&gt; elements
485 from a LoST Sync source.
486
487 1. When the Lost Sync destination does not have any mappings, it
488 submits an empty &lt;getMappingsRequest&gt; message, as shown in
489 Figure 7. This indicates that it wishes to retrieve all mappings
490 from the LoST Sync source. Note that the request does not
491 propagate further to other nodes.
492
493
494
495
496
497
498
499
500 <span class="grey">Schulzrinne &amp; Tschofenig Experimental [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc6739">RFC 6739</a> LoST Sync October 2012</span>
503
504
505 2. In case a LoST Sync destination node has already obtained
506 mappings in previous exchanges, then it may want to check whether
507 these mappings have been updated in the meanwhile. The policy
508 regarding when to poll for updated mapping information is outside
509 the scope of this document. The &lt;getMappingsRequest&gt; message
510 with one or more &lt;exists&gt; child element(s) allows the source to
511 only return mappings that are missing at the destination or have
512 been updated.
513
514 After issuing the &lt;getMappingsRequest&gt; message, the LoST Sync
515 destination waits for the &lt;getMappingsResponse&gt; message. In case of
516 a successful response, the LoST Sync destination stores the received
517 mappings and determines which mappings to update.
518
519 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Behavior of the LoST Sync Source</span>
520
521 When a LoST Sync source receives an empty &lt;getMappingsRequest&gt;
522 message, then all locally available mappings MUST be returned.
523
524 When a LoST Sync source receives a &lt;getMappingsRequest&gt; message with
525 one or more &lt;exists&gt; child element(s), then it MUST consult with the
526 local mapping database to determine whether any of the mappings of
527 the client is stale and whether there are mappings locally that the
528 client does not yet have. The former can be determined by finding
529 mappings corresponding to the 'source' and 'sourceID' attributes
530 where a mapping with a more recent 'lastUpdated' date exists.
531
532 Processing a &lt;getMappingsRequest&gt; message MAY lead to a successful
533 response in the form of a &lt;getMappingsResponse&gt; or an &lt;errors&gt;
534 message. Only the &lt;badRequest&gt;, &lt;forbidden&gt;, &lt;internalError&gt;, and
535 &lt;serverTimeout&gt; errors, defined in [<a href="./rfc5222" title="&quot;LoST: A Location-to-Service Translation Protocol&quot;">RFC5222</a>], are used by this
536 specification. Neither the &lt;redirect&gt; nor the &lt;warnings&gt; messages
537 are reused by this message.
538
539 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Examples</span>
540
541 The first example shows an empty &lt;getMappingsRequest&gt; message that
542 would retrieve all locally stored mappings at the LoST Sync source.
543
544 &lt;?xml version="1.0" encoding="UTF-8"?&gt;
545 &lt;getMappingsRequest xmlns="urn:ietf:params:xml:ns:lostsync1"/&gt;
546
547 Figure 7: Example of Empty &lt;getMappingsRequest&gt; Message
548
549 A further example request is shown in Figure 8, and the corresponding
550 response is depicted in Figure 9. In this example, the
551 &lt;getMappingsRequest&gt; element contains information about the mapping
552 that is locally available to the client inside the
553
554
555
556 <span class="grey">Schulzrinne &amp; Tschofenig Experimental [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc6739">RFC 6739</a> LoST Sync October 2012</span>
559
560
561 &lt;mapping-fingerprint&gt; element (with
562 source="authoritative.bar.example",
563 sourceId="7e3f40b098c711dbb6060800200c9a66", and lastUpdated="2006-
564 11-01T01:00:00Z"). The query asks for mappings that are more recent
565 than the available one as well as any missing mapping.
566
567 &lt;?xml version="1.0" encoding="UTF-8"?&gt;
568 &lt;getMappingsRequest xmlns="urn:ietf:params:xml:ns:lostsync1"&gt;
569 &lt;exists&gt;
570 &lt;mapping-fingerprint source="authoritative.bar.example"
571 sourceId="7e3f40b098c711dbb6060800200c9a66"
572 lastUpdated="2006-11-01T01:00:00Z"&gt;
573 &lt;/mapping-fingerprint&gt;
574 &lt;/exists&gt;
575 &lt;/getMappingsRequest&gt;
576
577 Figure 8: Example &lt;getMappingsRequest&gt; Message
578
579 The response to the above request is shown in Figure 9. A more
580 recent mapping was available with the identification of
581 source="authoritative.bar.example" and
582 sourceId="7e3f40b098c711dbb6060800200c9a66". Only one missing
583 mapping, with source "authoritative.foo.example", was found and
584 returned.
585
586 &lt;?xml version="1.0" encoding="UTF-8"?&gt;
587 &lt;sync:getMappingsResponse
588 xmlns:sync="urn:ietf:params:xml:ns:lostsync1"
589 xmlns="urn:ietf:params:xml:ns:lost1"
590 xmlns:gml="http://www.opengis.net/gml"&gt;
591
592 &lt;mapping source="authoritative.bar.example"
593 sourceId="7e3f40b098c711dbb6060800200c9a66"
594 lastUpdated="2008-11-26T01:00:00Z"
595 expires="2009-12-26T01:00:00Z"&gt;
596 &lt;displayName xml:lang="en"&gt;Leonia Police Department
597 &lt;/displayName&gt;
598 &lt;service&gt;urn:service:sos.police&lt;/service&gt;
599 &lt;serviceBoundary
600 profile="urn:ietf:params:lost:location-profile:basic-civic"&gt;
601 &lt;civicAddress
602 xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"&gt;
603 &lt;country&gt;US&lt;/country&gt;
604 &lt;A1&gt;NJ&lt;/A1&gt;
605 &lt;A3&gt;Leonia&lt;/A3&gt;
606 &lt;PC&gt;07605&lt;/PC&gt;
607 &lt;/civicAddress&gt;
608 &lt;/serviceBoundary&gt;
609
610
611
612 <span class="grey">Schulzrinne &amp; Tschofenig Experimental [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc6739">RFC 6739</a> LoST Sync October 2012</span>
615
616
617 &lt;uri&gt;sip:[email protected]&lt;/uri&gt;
618 &lt;serviceNumber&gt;911&lt;/serviceNumber&gt;
619 &lt;/mapping&gt;
620
621 &lt;mapping expires="2009-01-01T01:44:33Z"
622 lastUpdated="2008-11-01T01:00:00Z"
623 source="authoritative.foo.example"
624 sourceId="7e3f40b098c711dbb606011111111111"&gt;
625 &lt;displayName xml:lang="en"&gt;New York City Police Department
626 &lt;/displayName&gt;
627 &lt;service&gt;urn:service:sos.police&lt;/service&gt;
628 &lt;serviceBoundary profile="geodetic-2d"&gt;
629 &lt;gml:Polygon srsName="urn:ogc:def::crs:EPSG::4326"&gt;
630 &lt;gml:exterior&gt;
631 &lt;gml:LinearRing&gt;
632 &lt;gml:pos&gt;37.775 -122.4194&lt;/gml:pos&gt;
633 &lt;gml:pos&gt;37.555 -122.4194&lt;/gml:pos&gt;
634 &lt;gml:pos&gt;37.555 -122.4264&lt;/gml:pos&gt;
635 &lt;gml:pos&gt;37.775 -122.4264&lt;/gml:pos&gt;
636 &lt;gml:pos&gt;37.775 -122.4194&lt;/gml:pos&gt;
637 &lt;/gml:LinearRing&gt;
638 &lt;/gml:exterior&gt;
639 &lt;/gml:Polygon&gt;
640 &lt;/serviceBoundary&gt;
641 &lt;uri&gt;sip:[email protected]&lt;/uri&gt;
642 &lt;uri&gt;xmpp:[email protected]&lt;/uri&gt;
643 &lt;serviceNumber&gt;911&lt;/serviceNumber&gt;
644 &lt;/mapping&gt;
645
646 &lt;/sync:getMappingsResponse&gt;
647
648 Figure 9: Example &lt;getMappingsResponse&gt; Message
649
650 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Pushing Mappings via &lt;pushMappings&gt; and &lt;pushMappingsResponse&gt;</span>
651
652 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Behavior of the LoST Sync Source</span>
653
654 When a LoST Sync source obtains new information that is of interest
655 to its peers, it may push the new mappings to its peers.
656 Configuration settings at both peers decide whether this
657 functionality is used and what mappings are pushed to which other
658 peers. New mappings may arrive through various means, such as a
659 manual addition to the local mapping database, or through the
660 interaction with other entities. Deleting mappings may also trigger
661 a protocol interaction.
662
663
664
665
666
667
668 <span class="grey">Schulzrinne &amp; Tschofenig Experimental [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc6739">RFC 6739</a> LoST Sync October 2012</span>
671
672
673 The LoST Sync source SHOULD keep track of which LoST Sync destination
674 it has pushed &lt;mapping&gt; elements to. If it does not keep state
675 information, then it always has to push the complete data set. As
676 discussed in <a href="./rfc5222#section-5.1">Section&nbsp;5.1 of [RFC5222]</a>, &lt;mapping&gt; elements are
677 identified by the 'source', 'sourceID', and 'lastUpdated' attributes.
678 A mapping is considered the same if these three attributes match.
679
680 A &lt;pushMappings&gt; request sent by a LoST Sync source MUST contain one
681 or more &lt;mapping&gt; elements.
682
683 To delete a mapping, the content of the mapping is left empty, i.e.,
684 the &lt;mapping&gt; element only contains the 'source', 'sourceID',
685 'lastUpdated', and 'expires' attributes. Figure 10 shows an example
686 request where the mapping with the source="nj.us.example",
687 sourceId="123", lastUpdated="2008-11-01T01:00:00Z", and
688 expires="2008-11-01T01:00:00Z" is requested to be deleted. Note that
689 the 'expires' attribute is required per the schema definition but
690 will be ignored in processing the request on the receiving side. A
691 sync source may want to delete the mapping from its internal mapping
692 database but has to remember the peers to which it has distributed
693 this update unless it has other ways to ensure that databases do not
694 get out of sync.
695
696 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Behavior of the LoST Sync Destination</span>
697
698 When a LoST Sync destination receives a &lt;pushMappingsRequest&gt;
699 message, then the cache with the existing mappings is inspected to
700 determine whether the received mapping should lead to an update of an
701 already existing mapping, should create a new mapping in the cache,
702 or should be discarded.
703
704 If a newly received mapping has a more recent time in its
705 'lastUpdated' attribute, it MUST update an existing mapping that has
706 matching 'source' and 'sourceID' attributes.
707
708 If the received mapping does not match with any existing mapping
709 based on the 'source' and 'sourceId', then it MUST be added to the
710 local cache as an independent mapping.
711
712 If a &lt;pushMappingsRequest&gt; message with an empty &lt;mapping&gt; element is
713 received, then a corresponding mapping has to be determined based on
714 the 'source' and the 'sourceID'.
715
716 If no mapping can be identified, then an &lt;errors&gt; response MUST be
717 returned that contains the &lt;notDeleted&gt; child element. The
718 &lt;notDeleted&gt; element MAY contain a 'message' attribute with an error
719 description used for debugging purposes. The &lt;notDeleted&gt; element
720 MUST contain the &lt;mapping&gt; element(s) that caused the error.
721
722
723
724 <span class="grey">Schulzrinne &amp; Tschofenig Experimental [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc6739">RFC 6739</a> LoST Sync October 2012</span>
727
728
729 The response to a &lt;pushMappingsRequest&gt; request is a
730 &lt;pushMappingsResponse&gt; message. With this specification, a
731 successful response message returns no additional elements, whereas
732 an &lt;errors&gt; response is returned in the response message if the
733 request failed. Only the &lt;badRequest&gt;, &lt;forbidden&gt;, &lt;internalError&gt;,
734 or &lt;serverTimeout&gt; errors defined in <a href="./rfc5222#section-13.1">Section&nbsp;13.1 of [RFC5222]</a> are
735 used. The &lt;redirect&gt; and &lt;warnings&gt; messages are not used for this
736 query/response.
737
738 If the set of nodes that are synchronizing their data does not form a
739 tree, it is possible that the same information arrives through
740 several other nodes. This is unavoidable but generally only imposes
741 a modest overhead. (It would be possible to create a spanning tree
742 in the same fashion as IP multicast, but the complexity does not seem
743 warranted, given the relatively low volume of data.)
744
745 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Example</span>
746
747 An example is shown in Figure 10. Imagine a LoST node that obtained
748 two new mappings identified as follows:
749
750 o source="authoritative.example"
751 sourceId="7e3f40b098c711dbb6060800200c9a66"
752 lastUpdated="2008-11-26T01:00:00Z"
753
754 o source="authoritative.example"
755 sourceId="7e3f40b098c711dbb606011111111111"
756 lastUpdated="2008-11-01T01:00:00Z"
757
758 These two mappings have to be added to the peer's mapping database.
759
760 Additionally, the following mapping has to be deleted:
761
762 o source="nj.us.example"
763 sourceId="123"
764 lastUpdated="2008-11-01T01:00:00Z"
765
766 &lt;?xml version="1.0" encoding="UTF-8"?&gt;
767 &lt;sync:pushMappings
768 xmlns:sync="urn:ietf:params:xml:ns:lostsync1"
769 xmlns="urn:ietf:params:xml:ns:lost1"
770 xmlns:gml="http://www.opengis.net/gml"&gt;
771
772
773
774
775
776
777
778
779
780 <span class="grey">Schulzrinne &amp; Tschofenig Experimental [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc6739">RFC 6739</a> LoST Sync October 2012</span>
783
784
785 &lt;mapping source="authoritative.example"
786 sourceId="7e3f40b098c711dbb6060800200c9a66"
787 lastUpdated="2008-11-26T01:00:00Z"
788 expires="2009-12-26T01:00:00Z"&gt;
789 &lt;displayName xml:lang="en"&gt;Leonia Police Department
790 &lt;/displayName&gt;
791 &lt;service&gt;urn:service:sos.police&lt;/service&gt;
792 &lt;serviceBoundary
793 profile="urn:ietf:params:lost:location-profile:basic-civic"&gt;
794 &lt;civicAddress
795 xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"&gt;
796 &lt;country&gt;US&lt;/country&gt;
797 &lt;A1&gt;NJ&lt;/A1&gt;
798 &lt;A3&gt;Leonia&lt;/A3&gt;
799 &lt;PC&gt;07605&lt;/PC&gt;
800 &lt;/civicAddress&gt;
801 &lt;/serviceBoundary&gt;
802 &lt;uri&gt;sip:[email protected]&lt;/uri&gt;
803 &lt;serviceNumber&gt;911&lt;/serviceNumber&gt;
804 &lt;/mapping&gt;
805
806 &lt;mapping expires="2009-01-01T01:44:33Z"
807 lastUpdated="2008-11-01T01:00:00Z"
808 source="authoritative.example"
809 sourceId="7e3f40b098c711dbb606011111111111"&gt;
810 &lt;displayName xml:lang="en"&gt;New York City Police Department
811 &lt;/displayName&gt;
812 &lt;service&gt;urn:service:sos.police&lt;/service&gt;
813 &lt;serviceBoundary profile="geodetic-2d"&gt;
814 &lt;gml:Polygon srsName="urn:ogc:def::crs:EPSG::4326"&gt;
815 &lt;gml:exterior&gt;
816 &lt;gml:LinearRing&gt;
817 &lt;gml:pos&gt;37.775 -122.4194&lt;/gml:pos&gt;
818 &lt;gml:pos&gt;37.555 -122.4194&lt;/gml:pos&gt;
819 &lt;gml:pos&gt;37.555 -122.4264&lt;/gml:pos&gt;
820 &lt;gml:pos&gt;37.775 -122.4264&lt;/gml:pos&gt;
821 &lt;gml:pos&gt;37.775 -122.4194&lt;/gml:pos&gt;
822 &lt;/gml:LinearRing&gt;
823 &lt;/gml:exterior&gt;
824 &lt;/gml:Polygon&gt;
825 &lt;/serviceBoundary&gt;
826 &lt;uri&gt;sip:[email protected]&lt;/uri&gt;
827 &lt;uri&gt;xmpp:[email protected]&lt;/uri&gt;
828 &lt;serviceNumber&gt;911&lt;/serviceNumber&gt;
829 &lt;/mapping&gt;
830
831
832
833
834
835
836 <span class="grey">Schulzrinne &amp; Tschofenig Experimental [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc6739">RFC 6739</a> LoST Sync October 2012</span>
839
840
841 &lt;mapping source="nj.us.example"
842 sourceId="123"
843 lastUpdated="2008-11-01T01:00:00Z"
844 expires="2008-11-01T01:00:00Z"/&gt;
845
846 &lt;/sync:pushMappings&gt;
847
848 Figure 10: Example &lt;pushMappingsRequest&gt; Message
849
850 In response, the peer performs the necessary operations and updates
851 its mapping database. In particular, it will check whether the other
852 peer is authorized to perform the update and whether the elements and
853 attributes contain values that it understands. In our example, a
854 positive response is returned as shown in Figure 11.
855
856 &lt;?xml version="1.0" encoding="UTF-8"?&gt;
857 &lt;pushMappingsResponse xmlns="urn:ietf:params:xml:ns:lostsync1" /&gt;
858
859 Figure 11: Example &lt;pushMappingsResponse&gt;
860
861 In case a mapping could not be deleted as requested, the following
862 error response might be returned instead.
863
864 &lt;?xml version="1.0" encoding="UTF-8"?&gt;
865 &lt;errors xmlns="urn:ietf:params:xml:ns:lost1"
866 xmlns:sync="urn:ietf:params:xml:ns:lostsync1"
867 source="nodeA.example.com"&gt;
868
869 &lt;sync:notDeleted
870 message="Could not delete the indicated mapping."
871 xml:lang="en"&gt;
872
873 &lt;mapping source="nj.us.example"
874 sourceId="123"
875 lastUpdated="2008-11-01T01:00:00Z"
876 expires="2008-11-01T01:00:00Z"/&gt;
877 &lt;/sync:notDeleted&gt;
878 &lt;/errors&gt;
879
880 Figure 12: Example &lt;errors&gt; Message
881
882 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Transport</span>
883
884 LoST Sync needs an underlying protocol transport mechanism to carry
885 requests and responses. This document uses HTTPS as a transport to
886 exchange XML documents. No fallback to HTTP is provided.
887
888
889
890
891
892 <span class="grey">Schulzrinne &amp; Tschofenig Experimental [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc6739">RFC 6739</a> LoST Sync October 2012</span>
895
896
897 When using HTTP over Transport Layer Security (TLS) [<a href="./rfc2818" title="&quot;HTTP Over TLS&quot;">RFC2818</a>], LoST
898 Sync messages use the POST method. Requests MUST use the Cache-
899 Control response directive "no-cache".
900
901 All LoST Sync responses, including those indicating a LoST warning or
902 error, are carried in 2xx responses, typically 200 (OK). 3xx, 4xx,
903 and 5xx HTTP response codes indicate that the request itself failed
904 or was redirected; these responses do not contain any LoST Sync XML
905 elements.
906
907 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. RELAX NG</span>
908
909 Note: In order to avoid copying pattern definitions from the LoST
910 Regular Language for XML Next Generation (RELAX NG) schema [<a href="./rfc5222" title="&quot;LoST: A Location-to-Service Translation Protocol&quot;">RFC5222</a>]
911 to this document, we include it as "lost.rng" (XML syntax) in the
912 RELAX NG schema below.
913
914 &lt;?xml version="1.0" encoding="utf-8"?&gt;
915
916 &lt;grammar ns="urn:ietf:params:xml:ns:lostsync1"
917 xmlns="http://relaxng.org/ns/structure/1.0"
918 xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0"
919 datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes"&gt;
920
921 &lt;include href="lost.rng"/&gt;
922
923 &lt;start combine="choice"&gt;
924
925 &lt;a:documentation&gt; Location-to-Service Translation (LoST)
926 Synchronization Protocol&lt;/a:documentation&gt;
927
928 &lt;choice&gt;
929 &lt;ref name="pushMappings"/&gt;
930 &lt;ref name="pushMappingsResponse"/&gt;
931 &lt;ref name="getMappingsRequest"/&gt;
932 &lt;ref name="getMappingsResponse"/&gt;
933 &lt;/choice&gt;
934 &lt;/start&gt;
935
936
937 &lt;define name="pushMappings"&gt;
938 &lt;element name="pushMappings"&gt;
939 &lt;oneOrMore&gt;
940 &lt;ref name="mapping"/&gt;
941 &lt;/oneOrMore&gt;
942
943 &lt;ref name="extensionPoint"/&gt;
944 &lt;/element&gt;
945
946
947
948 <span class="grey">Schulzrinne &amp; Tschofenig Experimental [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc6739">RFC 6739</a> LoST Sync October 2012</span>
951
952
953 &lt;/define&gt;
954
955 &lt;define name="pushMappingsResponse"&gt;
956 &lt;element name="pushMappingsResponse"&gt;
957 &lt;ref name="extensionPoint"/&gt;
958 &lt;/element&gt;
959 &lt;/define&gt;
960
961 &lt;define name="getMappingsRequest"&gt;
962 &lt;element name="getMappingsRequest"&gt;
963 &lt;choice&gt;
964 &lt;ref name="exists"&gt;&lt;/ref&gt;
965 &lt;ref name="extensionPoint"/&gt;
966 &lt;/choice&gt;
967 &lt;/element&gt;
968 &lt;/define&gt;
969
970 &lt;define name="exists"&gt;
971 &lt;element name="exists"&gt;
972 &lt;oneOrMore&gt;
973 &lt;element name="mapping-fingerprint"&gt;
974 &lt;attribute name="source"&gt;
975 &lt;data type="token"/&gt;
976 &lt;/attribute&gt;
977 &lt;attribute name="sourceId"&gt;
978 &lt;data type="token"/&gt;
979 &lt;/attribute&gt;
980 &lt;attribute name="lastUpdated"&gt;
981 &lt;data type="dateTime"/&gt;
982 &lt;/attribute&gt;
983 &lt;ref name="extensionPoint"/&gt;
984 &lt;/element&gt;
985 &lt;/oneOrMore&gt;
986 &lt;/element&gt;
987 &lt;/define&gt;
988
989 &lt;define name="getMappingsResponse"&gt;
990 &lt;element name="getMappingsResponse"&gt;
991 &lt;oneOrMore&gt;
992 &lt;ref name="mapping"/&gt;
993 &lt;/oneOrMore&gt;
994 &lt;ref name="extensionPoint"/&gt;
995 &lt;/element&gt;
996 &lt;/define&gt;
997
998 &lt;!-- error messages --&gt;
999
1000 &lt;define name="notDeleted"&gt;
1001
1002
1003
1004 <span class="grey">Schulzrinne &amp; Tschofenig Experimental [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc6739">RFC 6739</a> LoST Sync October 2012</span>
1007
1008
1009 &lt;element name="notDeleted"&gt;
1010 &lt;ref name="basicException"/&gt;
1011 &lt;oneOrMore&gt;
1012 &lt;ref name="mapping"/&gt;
1013 &lt;/oneOrMore&gt;
1014 &lt;/element&gt;
1015 &lt;/define&gt;
1016 &lt;/grammar&gt;
1017
1018 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Operational Considerations</span>
1019
1020 It is important to avoid loops when more than two LoST servers use
1021 the mechanism described in this document. The example shown in
1022 Figure 13 with three LoST servers A, B, and C (each of them acts as a
1023 sync source and a sync destination) illustrates the challenge in more
1024 detail. A and B synchronize data between each other; the same is
1025 true for A and C, and B and C, respectively.
1026
1027 A -------- B
1028 \ /
1029 \ /
1030 \ /
1031 \ /
1032 C
1033
1034 Figure 13: Synchronization Configuration Example
1035
1036 Now, imagine that server A adds a new mapping. This mapping is
1037 uniquely identified by the combination of "source", "sourceid", and
1038 "last updated". Assume that A wants to push this new mapping to B
1039 and C. When B obtains this new mapping, it determines that it has to
1040 distribute it to its peer C. C also needs to distribute the mapping
1041 to its peer B. If the original mapping with the "source",
1042 "sourceid", and "last updated" is not modified by either B or C, then
1043 these two servers would recognize that they already possess the
1044 mapping and can ignore the update.
1045
1046 Implementations MUST NOT modify mappings they receive. An entity
1047 acting maliciously would, however, intentionally modify mappings or
1048 inject bogus mappings. To avoid the possibility of an untrustworthy
1049 member claiming a coverage region for which it is not authorized,
1050 authoritative mapping servers MUST sign mappings they distribute
1051 using an XML digital signature [<a href="#ref-W3C.REC-xmldsig-core-20020212">W3C.REC-xmldsig-core-20020212</a>]. A
1052 recipient MUST verify that the signing entity is indeed authorized to
1053 speak for that region. In many cases, this will require an out-of-
1054 band agreement to be in place to agree on specific entities to take
1055 on this role. Determining who can speak for a particular region is
1056 inherently difficult unless there is a small set of authorizing
1057
1058
1059
1060 <span class="grey">Schulzrinne &amp; Tschofenig Experimental [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc6739">RFC 6739</a> LoST Sync October 2012</span>
1063
1064
1065 entities that participants in the mapping architecture can trust.
1066 Receiving systems should be particularly suspicious if an existing
1067 coverage region is replaced by a new one that contains a different
1068 value in the &lt;uri&gt; element. When mappings are digitally signed, they
1069 cannot be modified by intermediate LoST servers.
1070
1071 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Security Considerations</span>
1072
1073 This document defines a protocol for exchange of authoritative
1074 mapping information between two entities. Hence, the protocol
1075 operations described in this document require authentication of
1076 neighboring nodes.
1077
1078 The LoST Sync client and servers MUST implement TLS and use TLS.
1079 Which version(s) ought to be implemented will vary over time and
1080 depend on the widespread deployment and known security
1081 vulnerabilities at the time of implementation. At the time of this
1082 writing, TLS version 1.2 [<a href="./rfc5246" title="&quot;The Transport Layer Security (TLS) Protocol Version 1.2&quot;">RFC5246</a>] is the most recent version but has
1083 very limited actual deployment and might not be readily available in
1084 implementation tool kits. TLS version 1.0 [<a href="./rfc2246" title="&quot;The TLS Protocol Version 1.0&quot;">RFC2246</a>] is the most
1085 widely deployed version and will give the broadest interoperability.
1086
1087 Mutual authentication between the LoST Sync source and the LoST Sync
1088 destination is not necessarily required in all deployments unless an
1089 emergency service authority wants to enforce access control prior to
1090 the distribution of their &lt;mapping&gt; elements. This may, for example,
1091 be the case when certain emergency services networks distribute
1092 internal mappings that are not meant for public distribution.
1093
1094 An additional threat is caused by compromised or misconfigured LoST
1095 servers. A denial of service could be the consequence of an injected
1096 mapping. If the mapping data contains a URL that does not exist,
1097 then emergency services for the indicated area are not reachable. If
1098 all mapping data contains URLs that point to a single PSAP (rather
1099 than a large number of PSAPs), then this PSAP is likely to experience
1100 overload conditions. If the mapping data contains a URL that points
1101 to a server controlled by the adversary itself, then it might
1102 impersonate PSAPs.
1103
1104 <a href="#section-8">Section 8</a> discusses this security threat and mandates signed
1105 mappings. For unusual changes to the mapping database, approval by a
1106 system administrator of the emergency services infrastructure (or a
1107 similar expert) may be required before any mappings are installed.
1108
1109
1110
1111
1112
1113
1114
1115
1116 <span class="grey">Schulzrinne &amp; Tschofenig Experimental [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc6739">RFC 6739</a> LoST Sync October 2012</span>
1119
1120
1121 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. IANA Considerations</span>
1122
1123 <span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Media Type Registration</span>
1124
1125 This specification requests the registration of a new media type
1126 according to the procedures of <a href="./rfc4288">RFC 4288</a> [<a href="./rfc4288" title="&quot;Media Type Specifications and Registration Procedures&quot;">RFC4288</a>] and guidelines in
1127 <a href="./rfc3023">RFC 3023</a> [<a href="./rfc3023" title="&quot;XML Media Types&quot;">RFC3023</a>].
1128
1129 Type name: application
1130
1131 Subtype name: lostsync+xml
1132
1133 Required parameters: none
1134
1135 Optional parameters: charset
1136
1137 Same as charset parameter of application/xml as specified in <a href="./rfc3023">RFC</a>
1138 <a href="./rfc3023">3023</a> [<a href="./rfc3023" title="&quot;XML Media Types&quot;">RFC3023</a>].
1139
1140 Encoding considerations: Identical to those of "application/xml" as
1141 described in <a href="./rfc3023#section-3.2">[RFC3023], Section&nbsp;3.2</a>.
1142
1143 Security considerations: This content type is designed to carry LoST
1144 Synchronization protocol payloads, and the security considerations
1145 section of <a href="./rfc6739">RFC 6739</a> is applicable. In addition, as this media
1146 type uses the "+xml" convention, it shares the same security
1147 considerations as described in <a href="./rfc3023#section-10">[RFC3023], Section&nbsp;10</a>.
1148
1149 Interoperability considerations: None
1150
1151 Published specification: <a href="./rfc6739">RFC 6739</a>
1152
1153 Applications that use this media type: Emergency and Location-based
1154 Systems
1155
1156 Additional information:
1157
1158 Magic number(s): None
1159
1160 File extension(s): .lostsyncxml
1161
1162 Macintosh file type code(s): 'TEXT'
1163
1164 Person &amp; email address to contact for further information:
1165 Hannes Tschofenig &lt;[email protected]&gt;
1166
1167 Intended usage: LIMITED USE
1168
1169
1170
1171
1172 <span class="grey">Schulzrinne &amp; Tschofenig Experimental [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc6739">RFC 6739</a> LoST Sync October 2012</span>
1175
1176
1177 Restrictions on usage: None
1178
1179 Author: Hannes Tschofenig &lt;[email protected]&gt;
1180
1181 Change controller:
1182
1183 This specification is a work item of the IETF ECRIT working group,
1184 with mailing list address &lt;[email protected]&gt;.
1185
1186 Change controller:
1187
1188 The IESG &lt;[email protected]&gt;
1189
1190 <span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. LoST Sync RELAX NG Schema Registration</span>
1191
1192 The schema defined in this document has been registered under the XML
1193 schema registry at
1194 <a href="http://www.iana.org/assignments/xml-registry/schema.html">http://www.iana.org/assignments/xml-registry/schema.html</a>
1195
1196 URI: urn:ietf:params:xml:schema:lostsync1
1197
1198 Registrant Contact: IETF ECRIT Working Group, Hannes Tschofenig
1199 ([email protected]).
1200
1201 RELAX NG Schema: The RELAX NG schema that has been registered is
1202 contained in <a href="#section-7">Section 7</a>.
1203
1204 <span class="h3"><a class="selflink" id="section-10.3" href="#section-10.3">10.3</a>. LoST Synchronization Namespace Registration</span>
1205
1206 The namespace defined in this document has been registered under the
1207 XML namespace registry at
1208 <a href="http://www.iana.org/assignments/xml-registry/ns.html">http://www.iana.org/assignments/xml-registry/ns.html</a>
1209
1210 URI: urn:ietf:params:xml:ns:lostsync1
1211
1212 Registrant Contact: IETF ECRIT Working Group, Hannes Tschofenig
1213 ([email protected]).
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228 <span class="grey">Schulzrinne &amp; Tschofenig Experimental [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc6739">RFC 6739</a> LoST Sync October 2012</span>
1231
1232
1233 XML:
1234
1235 BEGIN
1236 &lt;?xml version="1.0"?&gt;
1237 &lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
1238 "<a href="http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd</a>"&gt;
1239 &lt;html xmlns="http://www.w3.org/1999/xhtml"&gt;
1240 &lt;head&gt;
1241 &lt;meta http-equiv="content-type"
1242 content="text/html;charset=iso-8859-1"/&gt;
1243 &lt;title&gt;LoST Synchronization Namespace&lt;/title&gt;
1244 &lt;/head&gt;
1245 &lt;body&gt;
1246 &lt;h1&gt;Namespace for LoST server synchronization&lt;/h1&gt;
1247 &lt;h2&gt;urn:ietf:params:xml:ns:lostsync1&lt;/h2&gt;
1248 &lt;p&gt;See &lt;a href="[URL of published RFC]"&gt;<a href="./rfc6739">RFC 6739</a>
1249 &lt;/a&gt;.&lt;/p&gt;
1250 &lt;/body&gt;
1251 &lt;/html&gt;
1252
1253 END
1254
1255 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Acknowledgments</span>
1256
1257 Robins George, Cullen Jennings, Karl Heinz Wolf, Richard Barnes,
1258 Mayutan Arumaithurai, Alexander Mayrhofer, and Andrew Newton provided
1259 helpful input. Jari Urpalainen assisted with the RELAX NG schema.
1260 We would also like to thank our document shepherd Roger Marshall for
1261 his help with the document.
1262
1263 We would like to particularly thank Andrew Newton for his timely and
1264 valuable review of the XML-related content.
1265
1266 We would like to thank Robert Sparks, Barry Leiba, Stephen Farrell,
1267 Brian Haberman, Pete Resnick, and Sean Turner for their AD reviews.
1268 We would also like to thank Bjoern Hoehrmann for his media type
1269 review, Julian Reschke and Martin Duerst for their applications area
1270 reviews, and Wassim Haddad for his Gen-ART review.
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284 <span class="grey">Schulzrinne &amp; Tschofenig Experimental [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc6739">RFC 6739</a> LoST Sync October 2012</span>
1287
1288
1289 <span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. References</span>
1290
1291 <span class="h3"><a class="selflink" id="section-12.1" href="#section-12.1">12.1</a>. Normative References</span>
1292
1293 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
1294 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
1295
1296 [<a id="ref-RFC2246">RFC2246</a>] Dierks, T. and C. Allen, "The TLS Protocol Version 1.0",
1297 <a href="./rfc2246">RFC 2246</a>, January 1999.
1298
1299 [<a id="ref-RFC2818">RFC2818</a>] Rescorla, E., "HTTP Over TLS", <a href="./rfc2818">RFC 2818</a>, May 2000.
1300
1301 [<a id="ref-RFC3023">RFC3023</a>] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
1302 Types", <a href="./rfc3023">RFC 3023</a>, January 2001.
1303
1304 [<a id="ref-RFC4288">RFC4288</a>] Freed, N. and J. Klensin, "Media Type Specifications and
1305 Registration Procedures", <a href="https://www.rfc-editor.org/bcp/bcp13">BCP 13</a>, <a href="./rfc4288">RFC 4288</a>, December 2005.
1306
1307 [<a id="ref-RFC5222">RFC5222</a>] Hardie, T., Newton, A., Schulzrinne, H., and H.
1308 Tschofenig, "LoST: A Location-to-Service Translation
1309 Protocol", <a href="./rfc5222">RFC 5222</a>, August 2008.
1310
1311 [<a id="ref-RFC5246">RFC5246</a>] Dierks, T. and E. Rescorla, "The Transport Layer Security
1312 (TLS) Protocol Version 1.2", <a href="./rfc5246">RFC 5246</a>, August 2008.
1313
1314 [<a id="ref-W3C.REC-xmldsig-core-20020212">W3C.REC-xmldsig-core-20020212</a>]
1315 Eastlake, D., Reagle, J., Solo, D., Hirsch, F., and T.
1316 Roessler, "XML-Signature Syntax and Processing", World
1317 Wide Web Consortium, Second Edition, REC-xmldsig-core-
1318 20020212, June 2008.
1319
1320 <span class="h3"><a class="selflink" id="section-12.2" href="#section-12.2">12.2</a>. Informative References</span>
1321
1322 [<a id="ref-RFC5012">RFC5012</a>] Schulzrinne, H. and R. Marshall, "Requirements for
1323 Emergency Context Resolution with Internet Technologies",
1324 <a href="./rfc5012">RFC 5012</a>, January 2008.
1325
1326 [<a id="ref-RFC5582">RFC5582</a>] Schulzrinne, H., "Location-to-URL Mapping Architecture and
1327 Framework", <a href="./rfc5582">RFC 5582</a>, September 2009.
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340 <span class="grey">Schulzrinne &amp; Tschofenig Experimental [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc6739">RFC 6739</a> LoST Sync October 2012</span>
1343
1344
1345 Authors' Addresses
1346
1347 Henning Schulzrinne
1348 Columbia University
1349 Department of Computer Science
1350 450 Computer Science Building
1351 New York, NY 10027
1352 USA
1353
1354 Phone: +1 212 939 7004
1355 EMail: [email protected]
1356 URI: <a href="http://www.cs.columbia.edu">http://www.cs.columbia.edu</a>
1357
1358
1359 Hannes Tschofenig
1360 Nokia Siemens Networks
1361 Linnoitustie 6
1362 Espoo 02600
1363 Finland
1364
1365 Phone: +358 (50) 4871445
1366 EMail: [email protected]
1367 URI: <a href="http://www.tschofenig.priv.at">http://www.tschofenig.priv.at</a>
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396 Schulzrinne &amp; Tschofenig Experimental [Page 25]
1397 </pre>