I would have to disagree. From an ISP standpoint, when we supply a capped service to a customer, we use a combination of rate-limiting and traffic shaping. I Rate-limit the input, and traffic shape the output. I suppose it is more resource-intensive on our end, however don't you agree that it is better quality of service from the ISP?
On Sun, 2002-09-01 at 04:29, YASSER ALY wrote: > Rate-limiting is what we call policing and it is done from the ISP side. > It is bi-directional so you can rate limit input & output. You can define > what is the policy to be followed when traffic is within range and what > to be done once exceeded like pass, mark, drop. > > Traffic-shapping is done from the client side and it is unidirectional ( > Controlling the outgoing traffic from an interface. Shapping helps when 2 > sites are communicating with each other, one of them is 1M while the > other is 256K, traffic shapping would be defined from the 1M side inorder > not to flood the 256K link and lots or retransmission occurs. > > >From: "Mohamed Saro" > >what is the difference and the direction of > rate-limit and traffic shapping > >FAQ, list archives, and subscription > info: http://www.groupstudy.com/list/cisco.html >Report misconduct and > Nondisclosure violations to [EMAIL PROTECTED] > > ------------------------------------------------------------------------ > > Chat with friends online, try MSN Messenger: Click Here Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=52665&t=52468 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
