From: Alex Burr <ajb44.geo@yahoo.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] I have a new record for bloat
Date: Fri, 31 Mar 2017 22:07:24 +0000 (UTC) [thread overview]
Message-ID: <1198438634.8472041.1490998044375@mail.yahoo.com> (raw)
In-Reply-To: <99097E93-05AB-46F8-8545-E140C37ACAF3@pnsol.com>
On Saturday, February 11, 2017 9:05 AM, Neil Davies <neil.davies@pnsol.com> wrote:
> The same mindset that created these sort of performance artefacts is also driving changes in DSL
> standards, so watch out for these sort of artefacts (again induced by things that you have no direct
> control over) starting to occur in “high speed” DSL systems (such as VDSL) when conditions are less
> than perfect.
Are you referring to G.998.4? That's supposed to introduce a max of 63ms delay. But it's been a while since I was involved in DSL, so maybe it's something new...
Alex
next prev parent reply other threads:[~2017-03-31 22:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 20:02 Aaron Wood
2017-01-31 20:13 ` Dave Taht
2017-01-31 20:22 ` Dave Taht
2017-01-31 20:30 ` Toke Høiland-Jørgensen
2017-01-31 20:42 ` Jim Gettys
2017-02-11 9:04 ` Neil Davies
2017-02-11 18:24 ` Dave Taht
2017-03-31 22:07 ` Alex Burr [this message]
2017-04-01 4:05 ` Dave Täht
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=1198438634.8472041.1490998044375@mail.yahoo.com \
--to=ajb44.geo@yahoo.com \
--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