From: David Collier-Brown <davec-b@rogers.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Seen in passing: "Three Reasons Why Broadband Is So Unreliable"
Date: Tue, 27 Jun 2017 11:28:00 -0400 [thread overview]
Message-ID: <b8f344a4-d12d-516b-0674-045769bb4eab@rogers.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 456 bytes --]
at
http://www.circleid.com/posts/20170621_three_reasons_why_broadband_is_so_unreliable/
The style is definitely "biz-boy puff piece", but the point is valid:
selling strictly bandwidth when the customer wants performance is a
business risk.
--dave
--
David Collier-Brown, | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net | -- Mark Twain
[-- Attachment #2: Type: text/html, Size: 985 bytes --]
reply other threads:[~2017-06-27 15:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b8f344a4-d12d-516b-0674-045769bb4eab@rogers.com \
--to=davec-b@rogers.com \
--cc=bloat@lists.bufferbloat.net \
--cc=davecb@spamcop.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