From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Mark Andrews <marka@isc.org>
Cc: "David P. Reed" <dpreed@deepplum.com>,
Rich Brown <richb.hanover@gmail.com>,
"cerowrt-devel\@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
"bloat\@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cerowrt-devel] OT: Netflix vs 6in4 from HE.net
Date: Thu, 26 Mar 2020 16:29:18 -0400 [thread overview]
Message-ID: <9375.1585254558@localhost> (raw)
In-Reply-To: <8B226A2B-3816-4C4C-BD28-5660544FA4A5@isc.org>
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
Mark Andrews <marka@isc.org> wrote:
> Netflix could just redirect requests from HE.NET address ranges to IPv4
> only servers and that would solve the issue for all HE.NET customers.
> This isn’t the case of attempting to circumvent GEOIP rules. They can
> detect that the connection is coming from a HE.NET address range, they
> can easily install a redirect.
Yeah. That's a good idea.
Maybe even just 404 (maybe faster than host unreachable) even when you
connect from an range they don't like, and make sure their client does Happy Eyeballs.
Users and/or he.net could find a way to (optionally!) blackhole route netflix
IPv6, but that may be very hard to maintain that list.
--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
-= IPv6 IoT consulting =-
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-03-26 20:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 20:20 [Bloat] " Rich Brown
2020-03-21 20:27 ` [Bloat] [Cerowrt-devel] " Dave Taht
2020-03-21 22:06 ` Michael Richardson
2020-03-21 22:14 ` [Bloat] " Sebastian Moeller
2020-03-21 22:41 ` [Bloat] [Cerowrt-devel] " Dave Taht
2020-03-22 0:47 ` [Bloat] " Rich Brown
2020-03-22 21:31 ` [Bloat] [Cerowrt-devel] " David P. Reed
2020-03-24 15:11 ` Colin Dearborn
2020-03-24 17:47 ` Dave Taht
2020-03-24 22:19 ` David P. Reed
[not found] ` <MWHPR04MB06718C00021A4561606ACD8895F10@MWHPR04MB0671.namprd04.prod.outloo k.com>
[not found] ` <MWHPR04MB06718C00021A4561606ACD8895F10@MWHPR04MB0671.namprd04.prod.outlook.c om>
2020-03-24 22:28 ` David P. Reed
2020-03-24 22:47 ` Mark Andrews
2020-03-26 20:29 ` Michael Richardson [this message]
2020-03-25 8:56 ` Toke Høiland-Jørgensen
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=9375.1585254558@localhost \
--to=mcr+ietf@sandelman.ca \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dpreed@deepplum.com \
--cc=marka@isc.org \
--cc=richb.hanover@gmail.com \
/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