LARTC - Oct 2000 - Shaping incoming traffic to limit traffic-bills?

Hi there,

I was just thinking.. When I limit my incoming bandwidth to keep the bills
low (no flat-rate) but the only thing the system does is drop packets, then
I do have to pay for this traffic since it gets dropped on my side. It does
however reduce the amount of outgoing traffic, but are there ways to let
''the other side'' know that I can''t handle their
traffic instead of just
dropping it? I know Cisco (and others?) have some things like RED and
others..

Greetings again,

Clemens Sibon
--
Pettemerstraat 12A                                  T r I p l e
1823 CW Alkmaar                                         T
Tel. +31 (0)72-5129516
fax. +31 (0)72-5129520                              Automatisering
www.triple-it.nl                                 "Laat uw Net Werken!"

On Wed, Oct 25, 2000 at 04:20:24PM +0200, Clemens Sibon
wrote:
> Hi there,
> 
> I was just thinking.. When I limit my incoming bandwidth to keep the bills
> low (no flat-rate) but the only thing the system does is drop packets, then
> I do have to pay for this traffic since it gets dropped on my side. It does
Yes. But, as the HOWTO explains, TCP/IP responds to lost packets by slowing
down. If people just stream you lots of packets, you do need to pay.
> however reduce the amount of outgoing traffic, but are there ways to let
> ''the other side'' know that I can''t handle their
traffic instead of just
> dropping it? I know Cisco (and others?) have some things like RED and
> others..
RED, ICMP Source Quench, ECN all don''t do what you want I''m
afraid. Simple
per hop networks just don''t work like that. You need to shape upstream
to be
really sure.

Regards,

bert hubert

-- 
PowerDNS                     Versatile DNS Services  
Trilab                       The Technology People   
''SYN! .. SYN|ACK! .. ACK!'' - the mating call of the internet