1. LoST Sync draft-ietf-ecrit-lost-sync-08.txt Henning Schulzrinne Hannes Tschofenig

2. Overview Discussion about the usage of LoST Sync revealed different deployment approaches for LoST. Short summary of the deployment choices and the implication for LoST Sync. Walking through an example of –Austria with 1 FG, 3 LoST servers and many PSAPs –Finland with 1 FG (with co-located LoST server) and several PSAPs hidden behind an ESRP.

3. EastWest

4. 1 LoST Server

5. Architecture +---LoST-Sync-->\\ //<--LoST-Sync----+ | ----- | | | \/ \/ ----- ----- // \\ // \\ / \ / \ | Forest | | Forest | | Guide | | Guide | | Austria | | Finland \ / \ / +--------->\\ //<--------+ \\ // | ----- | ----- | /\ | | LoST | LoST //------\\ Sync LoST Sync |Co-Located| | Sync | | LoST | \/ | \/ | Server | //----\\ \/ //----\\ \\------// | LoST | //----\\ | LoST | | Server | | LoST | | Server | | (East) | | Server | |(Vienna)| \\----// | (West) | \\----// \\----//

6. LoST Server East provides it’s Boundary to the FG <mapping expires="2009-01-01T01:44:33Z" lastUpdated="2009-12-01T01:00:00Z" source="east-austria.lost-example.com" sourceId="e8b05a41d8d1415b80f2cdbb96ccf109"> LoST Server 'East' urn:service:sos........ list of coordinates for boundary of LoST server 'East'...

7. Architecture +---LoST-Sync-->\\ //<--LoST-Sync----+ | ----- | | | \/ \/ ----- ----- // \\ // \\ / \ / \ | Forest | | Forest | | Guide | | Guide | | Austria | | Finland \ / \ / +--------->\\ //<--------+ \\ // | ----- | ----- | /\ | | LoST | LoST //------\\ Sync LoST Sync |Co-Located| | Sync | | LoST | \/ | \/ | Server | //----\\ \/ //----\\ \\------// | LoST | //----\\ | LoST | | Server | | LoST | | Server | | (East) | | Server | |(Vienna)| \\----// | (West) | \\----// \\----//

8. Finland FG <mapping expires="2007-01-01T01:44:33Z" lastUpdated="2006-11-01T01:00:00Z" source="finland.lost-example.com" sourceId="7e3f40b098c711dbb6060800200c9a66"> Finland ESRP urn:service:sos <civicAddress xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"> FI

9. Architecture +---LoST-Sync-->\\ //<--LoST-Sync----+ | ----- | | | \/ \/ ----- ----- // \\ // \\ / \ / \ | Forest | | Forest | | Guide | | Guide | | Austria | | Finland \ / \ / +--------->\\ //<--------+ \\ // | ----- | ----- | /\ | | LoST | LoST //------\\ Sync LoST Sync |Co-Located| | Sync | | LoST | \/ | \/ | Server | //----\\ \/ //----\\ \\------// | LoST | //----\\ | LoST | | Server | | LoST | | Server | | (East) | | Server | |(Vienna)| \\----// | (West) | \\----// \\----//

10. Finland LoST Server <mapping expires="2007-01-01T01:44:33Z" lastUpdated="2006-11-01T01:00:00Z" source="finland.lost-example.com" sourceId="7e3f40b098c711dbb6060800200c9a66"> Finland ESRP urn:service:sos <civicAddress xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"> FI sip:esrp@finland-example.com xmpp:esrp@finland-example.com 112

11. Implications for the document? Express ways to express mapping data to point to –LoST servers –PSAPs/ESRPs. Description about the architectural choices.