[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Executive summary of: RE: hard questions: request routing
You present the case for standardization quite well!
It seems to me that the different proposals require impose
differing levels of complexity on the CDN's. In particular,
with only one level of redirection, there is more overhead
on the authoritative CDN for the content, and a pressure
to have fewer content groups (?).
Am I alone in needing a recap of terminology along with
the executive summary? Content topology vs. content
routing, content path, The Matrix, etc.?
>>> Francis Zane <email@example.com> 04/04/01 12:17PM >>>
My main concern with fully general forwarding mechanisms remains the
ability to deal with different (particularly non-DNS) RRS mechanisms
and all the cases which could arise. As a (mostly thought-experiment)
example, here's a weird case that concerns me: Suppose I have an RRS
which spans two specific RR mechanisms: DNS (based on local DNS IP)
and some form of L7 (based on client IP). Is there a way to guarantee
correct (ie, non-looping) behaviour? (CDN A DNS redirects to CDN B
based on local DNS, which HTTP redirects to CDN A based on client IP).