November 2006IETF 67 - ECRIT Location-to-URL Mapping Architecture and Framework draft-ietf-ecrit-mapping-arch Henning Schulzrinne Columbia University

November 2006IETF 67 - ECRIT 2’ summary Seekers –want information Resolvers –know >= 1 forest guide (but not trees) –may only know some services Forest guides (many) –know trees and their coverage regions (for one or more services) Trees (>= 1) –have authoritative data for particular regions and services

November 2006IETF 67 - ECRIT LoST: Location-to-URL Mapping cluster serves VSP 2 NY US NJ US Bergen County NJ US 123 Broad Ave Leonia Bergen County NJ US cluster serving VSP 1 replicate root information search referral root nodes Leonia NJ US VSP 1

November 2006IETF 67 - ECRIT Caching Resiliency requires caching –failure, DOS on tree, … Caching at multiple levels -- all optional –seeker: results of own queries, for one or more service regions including service regions by reference –resolver: all queries by local seekers –top of tree: lower level results within tree

November 2006IETF 67 - ECRIT LoST architecture T1 (.us) T2 (.de) T3 (.dk) G G G G G broadcast (gossip) T1:.us T2:.de resolver seeker 313 Westview Leonia, NJ US Leonia, NJ  tree guide

November 2006IETF 67 - ECRIT Status & next steps Basic text stable –protocol for intra-cluster and inter-forest-guide left to define Will generalize to multiple services Move operational guidance to BCP (one para) Ready for WGLC after -01