I'm with you jason - the subject of bandwidth management is an important one, and the fact is that new applications (crapplications?!) are appearing all the time which are pushing the business model into a tight spot. We have competing forces - on the one hand, we purchase expensive dedicated bandwidth, and on the other, we sell low cost shared bandwidth. We cannot sell for $34.95 what we pay $300 for. But yet we get customers who come to us and ask us to do exactly that.

The days of the unmanaged bandwidth network are numbered, if they are not already at an end. There's certainly some solutions available for head-end bandwidth management - like the bandwidth arbitrator which was already mentioned - but the most effective management starts with subscriber side and _not allowing_ traffic flows that exceed that subscribers limits, into the network in the first place. The Arbitrator can only deal with it once it reaches your noc (or wherever else you've placed it), but this doesn't do anything for portscanning viruses or other traffic which would get dropped - but also would have also consumed your precious network resouces first before getting to that choke point.

I'd really like to see an isp industry standardization effort on the subject of bandwidth subscription policies, something that we can present to customers as the uniform definition of what we provide in terms of bandwidth and allocation and priority and so forth that could then be used as a 'sticker' when shopping around for services....

Mike (the rambler)

Jason wrote:

Several times in the last few weeks the topic of bandwidth management has been discussed, but "I Still Haven't Found What I'm Lookin' For"... Here's what I'd like to do:

1. Each user starts with a big "Internet Pipe". This way casual surfing and emails, etc. happen nice and snappy.

2. If a user downloads a big chunk of data, he needs to be "shaped" to a lower data rate after a few minutes (I'm thinking 2 or 3 minutes).

3. Step 2 repeats over and over several times if the user continues to download.

4. After the user quits hogging the network, his bandwidth is restored in stages (backwards of 2 and 3).

I know this, or at least similar things to it, are being done out there. The HughesNet satellite FAP works something like this (I don't know the actual values):

1.  Each user has a "Bit Bucket" that holds 1 Gig of bandwidth.

2.  The "Bit Bucket is replenished at 128k.

3.  The speed at which the user can download from his "bit bucket" is 1meg.

4. If the user uses all the bits in his bucket faster than they are replenished, he eventually gets only 128k.

Does anyone know how to get something like this going? I am especially interested in Linux/Ubuntu solutions.


WISPA Wireless List: wireless@wispa.org


Archives: http://lists.wispa.org/pipermail/wireless/

Reply via email to