From: Jeremy Visser <jeremy@visser.name>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Usage Based Billing - It's All About Perceived Congestion
Date: Tue, 01 Mar 2011 18:37:02 +1100 [thread overview]
Message-ID: <4D6CA21E.2000005@visser.name> (raw)
In-Reply-To: <1298948257.12452.1424819733@webmail.messagingengine.com>
Henrique de Moraes Holschuh said:
> Cutting down service to as low as 100kbit/s
> downstream and 30kbit/s upstream when the consumer goes over a monthly
> quota, limiting concurrent tcp sessions, and extremely severe shaping of
> P2P traffic are used as alternatives to UBB.
Ha. Here in Australia, shaping the service to 64 kbit/s downstream when
quota is exceeded is the norm. Premium services sometimes allow 128 or
256 kbit/s shaping, but that's not very common.
next prev parent reply other threads:[~2011-03-01 7:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 21:56 richard
2011-03-01 2:57 ` Henrique de Moraes Holschuh
2011-03-01 7:37 ` Jeremy Visser [this message]
2011-03-01 9:18 ` Ondřej Bílka
2011-03-01 9:33 ` Steve Davies
2011-03-02 8:20 ` Ondřej Bílka
2011-03-01 13:57 ` Steve Bauer
2011-03-01 15:36 ` Jim Gettys
2011-03-01 16:01 ` richard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D6CA21E.2000005@visser.name \
--to=jeremy@visser.name \
--cc=bloat@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox