From: Dave Taht <dave.taht@gmail.com>
To: libreqos <libreqos@lists.bufferbloat.net>
Subject: [LibreQoS] Fwd: Do ISP's collect and analyze traffic of users?
Date: Tue, 16 May 2023 06:49:40 -0700 [thread overview]
Message-ID: <CAA93jw4=Srhw6MQ6E=G18ymb=ht84Z7_pTkbQ+ap6R=iuB8bsQ@mail.gmail.com> (raw)
In-Reply-To: <bf8e993d-aa4a-40f6-17d6-1c6ad38ef918@mtcc.com>
[-- Attachment #1: Type: text/plain, Size: 595 bytes --]
---------- Forwarded message ---------
From: Michael Thomas <mike@mtcc.com>
Date: Mon, May 15, 2023, 4:01 PM
Subject: Do ISP's collect and analyze traffic of users?
To: nanog@nanog.org <nanog@nanog.org>
And maybe try to monetize it? I'm pretty sure that they can be compelled
to do that, but do they do it for their own reasons too? Or is this way
too much overhead to be doing en mass? (I vaguely recall that netflow,
for example, can make routers unhappy if there is too much "flow").
Obviously this is likely to depend on local laws but since this is NANOG
we can limit it to here.
Mike
[-- Attachment #2: Type: text/html, Size: 991 bytes --]
parent reply other threads:[~2023-05-16 13:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bf8e993d-aa4a-40f6-17d6-1c6ad38ef918@mtcc.com>]
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/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw4=Srhw6MQ6E=G18ymb=ht84Z7_pTkbQ+ap6R=iuB8bsQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=libreqos@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