The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] net neutrality
Date: Mon, 11 Dec 2017 15:10:22 -0500 (EST)	[thread overview]
Message-ID: <20171211201022.26C4418C08C@mercury.lcs.mit.edu> (raw)

    > From: Larry McVoy <lm at mcvoy.com>

    > look at the history, various ISPs like Verizon, Comcast, etc, have done
    > stuff like block bittorrent, skype, etc

Bittorrent is a complex situation, some ISPs were ordered by a court to block
it.

As to Skype, I agree ISPs shouldn't block sites - but if you read my message,
I already said that.


    > The problem is I paid for the bits.  Bits is bits.  I paid for a rate,
    > that's what they got paid for, why should they get to charge a second
    > time for the same bits? That's exactly what they want to do.

Fine, you pay your money, you get X Mbits/second.

If you (or the site you're getting bits from) wants _more_ than X
Mbits/second, charging you - or them, which is I gather mostly what ISPs want
to do - for that privilege is a problem... how?

   Noel




             reply	other threads:[~2017-12-11 20:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-11 20:10 Noel Chiappa [this message]
2017-12-11 20:13 ` Larry McVoy
  -- strict thread matches above, loose matches on Subject: below --
2017-12-11 20:27 Noel Chiappa
2017-12-11 21:09 ` ron minnich
2017-12-11 20:13 Noel Chiappa
2017-12-11 20:14 ` Larry McVoy
2017-12-11 20:18   ` Warren Toomey
2017-12-11 19:23 [TUHS] V7 Addendem [ really lawyers and AT&T consent decree ] Noel Chiappa
2017-12-11 19:36 ` [TUHS] net neutrality Larry McVoy
2017-12-11 19:48   ` Clem Cole

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171211201022.26C4418C08C@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).