From: William Allen Simpson <william.allen.simpson@gmail.com>
To: Ketan Kulkarni <ketkulka@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Google working on experimental 3.8 Linux kernel for Android
Date: Sat, 02 Mar 2013 08:27:28 -0500 [thread overview]
Message-ID: <5131FE40.5030809@gmail.com> (raw)
In-Reply-To: <CAD6NSj7ubMFyBpGu=EKezuLOVQzLDDFydV+YVU2TY5Vgr6tsZA@mail.gmail.com>
On 3/1/13 10:39 PM, Ketan Kulkarni wrote:
> Consider from end-user perspective, getting a voice call while surfing/downloading on 2G/3G interrupts all the download and it is annoying.
Ummm, this isn't entirely accurate. When Karn and I designed CDMA IS-99
circa '93 -'94 with data in the control channel, data never stopped
during voice calls.
Maybe some versions of 2G/3G couldn't do that, but better versions.... ;-)
> Similarly going ahead we might very well have handoff from wifi to LTE - why not?
>
Agreed. But again, we've known how to do soft hand-off for a long time.
> On Fri, Mar 1, 2013 at 9:57 PM, <dpreed@reed.com <mailto:dpreed@reed.com>> wrote:
> This is why "more buffering is better" continues to be the law of the land - the spec is defined to be "no lost packets under load". I'm sure that the primary measure under load for RRUL will be "no lost packets" by the time it gets to field
> engineers in the form of "specs" - because that's what they've *always* been told, and they will disregard any changes as "typos".
>
We've had this problem with bell-heads forever. Even back in the days
with heavy packet loss at MAE-East, bell-heads would continue to
insist that any packet loss was an alarm condition. Even after PPP
LQM showed they mangled bits and bytes on even their most prized T3
links (and had been lying to the FCC about uptime for decades), we
never could shake off the syndrome.
It's the "every bit is sacred" mentality.
next prev parent reply other threads:[~2013-03-02 13:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 18:03 Maciej Soltysiak
2013-02-28 18:57 ` dpreed
2013-02-28 19:08 ` Dave Taht
2013-02-28 20:03 ` Jim Gettys
2013-02-28 20:58 ` dpreed
2013-02-28 21:02 ` Jim Gettys
2013-02-28 21:10 ` dpreed
2013-03-01 8:00 ` Ketan Kulkarni
2013-03-01 15:40 ` dpreed
2013-03-01 16:09 ` Jim Gettys
2013-03-01 16:27 ` dpreed
2013-03-02 3:39 ` Ketan Kulkarni
2013-03-02 13:27 ` William Allen Simpson [this message]
2013-03-02 14:20 ` dpreed
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5131FE40.5030809@gmail.com \
--to=william.allen.simpson@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=ketkulka@gmail.com \
/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