[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Executive summary of: RE: hard questions: request routing



Title: RE: Executive summary of: RE: hard questions: request routing


> -----Original Message-----
> From: Francis Zane [mailto:francis@research.bell-labs.com]

> 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).
>

yes, the matrix approach. Content hops are cumulative, you always know where content
came from. You know the whole path.

abbie