From: Simon Barber <simon@superduper.net>
To: Michael Richardson <mcr@sandelman.ca>
Cc: "<bloat@lists.bufferbloat.net>" <bloat@lists.bufferbloat.net>,
"<davehart_gmail_exchange_tee@davehart.net>"
<davehart_gmail_exchange_tee@davehart.net>,
Dauran raza <dauran.raza@gmail.com>
Subject: Re: [Bloat] Bufferbloat research: Help required
Date: Sat, 01 Dec 2012 13:47:42 -0800 [thread overview]
Message-ID: <50BA7AFE.7060102@superduper.net> (raw)
In-Reply-To: <1306.1354395193@obiwan.sandelman.ca>
Voice over data can actually work very well in 3G networks (better than
dedicated voice even), but it requires prioritisation. There is a bunch
of work going on to enable this in existing networks to support the new
services that VoLTE will enable, over older networks (Joyn). This is a
*huge* transition in carrier networks, and will take some time to
arrive. Even today only 1 US carrier uses VoLTE, all the others switch
to 3G to make or receive a phone call.
Simon
On Sat 01 Dec 2012 12:53:13 PM PST, Michael Richardson wrote:
>
>>>>>> "Mark" == Mark Watson <watsonm@netflix.com> writes:
> Mark> It's also interesting to note that cellular wireless [DATA] systems
> Mark> have been designed with a primary objective of reducing packet
> Mark> loss, at the expense of delay and especially delay variability
> Mark> introduced by link layer ARQ and other schemes. This approach
> Mark> maximizes the throughput of a single long-lived TCP
> Mark> connection, which is not an especially common traffic
> Mark> pattern.
>
> A question, given that I inserted [DATA].
>
> I wonder to what extent the pre-LTE systems were designed this way in
> part to make sure that voice over data would always be crappy?
>
> The LTE roadmap says that voice is now over data, so it's now in the
> carrier's interest to do things differently.
>
> Mark> Furthermore, the throughput of a cellular wireless radio
> Mark> channel varies by orders of magnitude on fairly rapidly
> Mark> (channel conditions are reassessed hundreds of times per
> Mark> second): what was a reasonable sized buffer for the throughput
> Mark> at one moment becomes a bloated one a fraction of a second
> Mark> later.
>
> Does ECN help us here?
>
prev parent reply other threads:[~2012-12-01 21:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPoy_SWZESfxdWv-bp1cT+PrR6su3=S7w1cQOTwgmbA2JvG_tw@mail.gmail.com>
2012-11-25 15:21 ` Dauran raza
2012-11-28 16:39 ` Dave Hart
2012-11-30 18:56 ` Mark Watson
2012-11-30 21:17 ` Simon Barber
2012-12-01 20:53 ` Michael Richardson
2012-12-01 21:47 ` Simon Barber [this message]
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=50BA7AFE.7060102@superduper.net \
--to=simon@superduper.net \
--cc=bloat@lists.bufferbloat.net \
--cc=dauran.raza@gmail.com \
--cc=davehart_gmail_exchange_tee@davehart.net \
--cc=mcr@sandelman.ca \
/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