[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: hard questions: request routing
- Subject: RE: hard questions: request routing
- From: "Hilarie Orman" <HORMAN@volera.com>
- Date: Sat, 31 Mar 2001 23:17:26 -0700
- Cc: <cdn@ops.ietf.org>
- Delivery-date: Sat, 31 Mar 2001 22:18:50 -0800
- Envelope-to: cdn-data@psg.com
How do you quantify "very sure"? For how long is the guarantee
good? Suppose the premises on which the guarantee was made
become invalid, what recovery is possible?
Hilarie
>>> Eric Dean <eric@crystalballinc.com> 03/31/01 04:40PM >>>
I'm a bit confused how routing loops would occur, whether transient or
not, on an internetwork interface especially when the content delivery
uses a completely different network protocol.
Request routing to a peered network should usually result in an utltimate
if not penultimate resolution to a surrogate. Even during transients, it
would be assumed that a CDN network should be converged prior to making
a CDI advertisement. MPLS makes such an assumption.
In other words, a CDN should be very sure of being capable of delivering
end-to-end content prior to making a CDI advertisement.