From: Kathleen Nichols <nichols@pollere.net>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] lte + cable latency improvement
Date: Tue, 15 Jan 2019 07:04:04 -0800 [thread overview]
Message-ID: <8ca74fdb-0618-f04f-9ba2-801e7b235c60@pollere.net> (raw)
In-Reply-To: <CAA93jw7HxeZi3gbH3W1ypf1EK9C=xN_XRpn6Joypvxvb8SM4ww@mail.gmail.com>
On 1/15/19 12:02 AM, Dave Taht wrote:
> https://www.cablelabs.com/enabling-the-cable-networks-for-mobile-backhaul/
>
>
Hmm. From the linked article:
> Additionally, in building the PoC, we have accumulated expertise on
> how to perfect the BWR algorithm to optimally predict the amount of
> data and time egressed from the LTE side. We will pass this knowledge
> on to the LTE implementers during the specification work.
So they can optimally predict the traffic they "loaded [it] up" with.
Dave, you see why I am skeptical of fake traffic.
Kathie
next prev parent reply other threads:[~2019-01-15 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 8:02 Dave Taht
2019-01-15 15:04 ` Kathleen Nichols [this message]
2019-01-15 15:27 ` Jim Gettys
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=8ca74fdb-0618-f04f-9ba2-801e7b235c60@pollere.net \
--to=nichols@pollere.net \
--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