RE: DLB comments

["Dana L. Blair" <dblair@cisco.com>]

>   -----Original Message-----
>   From: owner-more@ops.ietf.org [mailto:owner-more@ops.ietf.org]On Behalf
>   Of tim clifford
>   Sent: Thursday, July 19, 2001 10:57 AM
>   To: more@psg.com
>   Subject: DLB comments
>   
>   
>   
>   well, I agree with your statement here, but I believe there are 
>   significant
>   exceptions to this rule.  As I understand the Digital 
>   Island/C&W and Akamai
>   service offerings, and technologies like the cisco content director and
>   nortel alteon, they specifically place application level ( or 
>   at least above
>   IP) processing in the forwarding path.

Yes, there are some exceptions.

Content caching is usually
applied when congestion occurs or is anticipated in the
core of the network.  For example, retrieve content from
a cache which is "close" to you in terms of IP hops to
limit performance impacts from crossing the globe.

	This doesn't apply to existing or near term wireless
	internet deployments since the radio bandwidth is
	so low compared to the backbone.

Another reason for content caching is scalability of
the server.  Pre-populating caches allows a server to
scale to multiple servers in a farm

	Nothing special is required here for wireless access.

At this point, I don't see any need for application layer
elements within the network that are special for wireless access.
There are some benefits which apply to both wired and
wireless cases.

thanks,
Dana
>   
>   it seems that various activities are pushing this sort of 
>   functionality to
>   the mobile edge.
>   
>   tim
>   
>   
>   >
>   > DLB:	Intelligent entities are needed in the network to 
>   control access and
>   > 	provide QoS capabilities, and route packets but there should be no
>   > application elements
>   > 	within the network as part of the forwarding path.
>   >
>   
>