1. March 2009 (IETF 74)IETF - ECRIT1 LoST synchronization draft-ietf-ecrit-lost-sync-04 Henning Schulzrinne Hannes Tschofenig IETF 74, San Francisco

2. December 2007IETF70 - ECRIT2 Memory refresh: Peering western Canada YT BC AB pushMappingsRequest (whole coverage region) FGs.ca.us

3. Cluster March 2009 (IETF 74)IETF - ECRIT3 LoST server LoST server automated synchronization for fault recovery re-synchronization after failures external data source (e.g., GIS)

4. Draft status update Implementation in progress (Columbia U. LoST server) Removed for all source mappings for simplicity March 2009 (IETF 74)IETF - ECRIT4

5. TBD Can a “virgin” node join a cluster? Discussion: relationship to other efforts –DB: single vendor only? would need to agree on database schema want diversity of implementations within cluster for robustness –see DNS geographic diversity –see SLP synchronization work (mSLP: RFC 3528, April 2003) March 2009 (IETF 74)IETF - ECRIT5