Synchronizing Location-to-Service Translation (LoST) Servers draft-schulzrinne-lost-sync-00

1
Synchronizing Location-to-Service Translation
(LoST) Serversdraft-schulzrinne-lost-sync-00

• Henning Schulzrinne

2
Motivation

• Synchronization of forest guides (FG), resolver
  clusters and authoritative servers (AS)
• Particularly if operated by different
  jurisdictions or across different vendors
• may not be able to use standard database sync

3
Peering

• FG - FG
• AS - FG, AS - AS
• AS push coverage regions up the tree, towards
  the FG
• create summaries
• manually configured peering relationships
• long-term static

4
Peering
.us
FGs
.ca
western Canada
pushMappingsRequest
BC
YT
AB
5
Distribution (push)

• ltpushMappingsRequestgt
• pushed to peers
• can be summary
• replace existing mappings with same id

6
Example pushMappingsRequest
ltpushMappingsRequest xmlns"urnietfparamsxmlns
lost1sync"gt ltmappingsgt ltmapping
sourceId"lostleonia.nj.us.example"
version"1" lastUpdated"2006-11-26T010000Z"
timeToLive"2007-12-26T010000Z"gt
ltdisplayName xmllang"en"gt Leonia
Police Department lt/displayNamegt
... lt/mappinggt ltmapping
source"lostnj.us.example" sourceId"englewood"/gt
lt/mappingsgt lt/pushMappingsRequestgt
add or update mapping
delete mapping
7
Pull synchronization

• ltgetMappingsRequestgt
• provide current list of mappings
• obtain missing or updated mappings

lt?xml version"1.0" encoding"UTF-8"?gt
ltgetMappingsRequest xmlns"urn...sync"gt
ltm source"lostauthoritative.example
sourceId"abc123" version"1"/gt lt/getMappingsReque
stgt
8
Open Issues - still...

• WG document?
• Error conditions
• Update ltmappinggt according to LoST