1 / 8

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

Synchronizing Location-to-Service Translation (LoST) Servers draft-schulzrinne-lost-sync-00. Henning Schulzrinne. Motivation. Synchronization of forest guides (FG), resolver clusters and authoritative servers (AS) Particularly if operated by different jurisdictions or across different vendors

paulgomez
Télécharger la présentation

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

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Synchronizing Location-to-Service Translation (LoST) Serversdraft-schulzrinne-lost-sync-00 Henning Schulzrinne IETF70 - ECRIT

  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 IETF70 - ECRIT

  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 IETF70 - ECRIT

  4. Peering .us FGs .ca western Canada pushMappingsRequest BC YT AB IETF70 - ECRIT

  5. Distribution (push) • <pushMappingsRequest> • pushed to peers • can be summary • replace existing mappings with same id IETF70 - ECRIT

  6. Example pushMappingsRequest <pushMappingsRequest xmlns="urn:ietf:params:xml:ns:lost1:sync"> <mappings> <mapping sourceId="lost:leonia.nj.us.example" version="1" lastUpdated="2006-11-26T01:00:00Z" timeToLive="2007-12-26T01:00:00Z"> <displayName xml:lang="en"> Leonia Police Department </displayName> ... </mapping> <mapping source="lost:nj.us.example" sourceId="englewood"/> </mappings> </pushMappingsRequest> add or update mapping delete mapping IETF70 - ECRIT

  7. Pull synchronization • <getMappingsRequest> • provide current list of mappings • obtain missing or updated mappings <?xml version="1.0" encoding="UTF-8"?> <getMappingsRequest xmlns="urn:...:sync"> <m source="lost:authoritative.example” sourceId="abc123" version="1"/> </getMappingsRequest> IETF70 - ECRIT

  8. Open Issues - still... • WG document? • Error conditions • Update <mapping> according to LoST IETF70 - ECRIT

More Related