[Bloat] lte + cable latency improvement

[Bloat] lte + cable latency improvement

[Dave Taht]

https://www.cablelabs.com/enabling-the-cable-networks-for-mobile-backhaul/
-- 

Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740

Re: [Bloat] lte + cable latency improvement

[Kathleen Nichols]

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

Re: [Bloat] lte + cable latency improvement

[Jim Gettys]

[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]

On Tue, Jan 15, 2019 at 10:04 AM Kathleen Nichols <nichols@pollere.net>
wrote:

> 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.
>

Not to mention the fact the LTE traffic is distorted badly by its own
sources of bufferbloat...

However, getting LTE implementers to understand that the problem exists in
the first place is worthwhile (so long
as they understand it can occur in either/both parts of the path...

JIm

>
> _____________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>

[-- Attachment #2: Type: text/html, Size: 2272 bytes --]