november 2006ietf 67 - ecrit location-to-url mapping architecture and framework...
TRANSCRIPT
November 2006 IETF 67 - ECRIT
Location-to-URL Mapping Architecture and Framework
draft-ietf-ecrit-mapping-arch
Henning Schulzrinne
Columbia University
November 2006 IETF 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 2006 IETF 67 - ECRIT
LoST: Location-to-URL Mapping
clusterserves VSP2
NYUS
NJUS
Bergen CountyNJ US
123 Broad AveLeoniaBergen CountyNJ US
cluster serving VSP1
replicateroot information
searchreferral
rootnodes
LeoniaNJ US
VSP1
November 2006 IETF 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 2006 IETF 67 - ECRIT
LoST architecture
T1
(.us)
T2
(.de) T3
(.dk)
G
G
G G
Gbroadcast (gossip)T1: .us
T2: .de
resolver
seeker313 Westview
Leonia, NJ US
Leonia, NJ sip:[email protected]
tree guide
November 2006 IETF 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