At the bottom of that page, there is a question “Was this answer helpful.” I clicked NO. It gave me a free form text box to explain why I felt it was not helpful… Here’s what I typed:

The advice is just bad and the facts are incorrect.
IPv6 is not blocking the Disney application. Either IPv6 is broken in the users environment (in which case, the user should work with their network administrator to resolve this) or Disney has failed to implement IPv6 correctly on their DRM platform.

IPv6 cannot "Block" an application.

Turning off IPv6 will degrade several other services and cause additional problems. This is simply very bad advice and shame on Disney for issuing it.

Hopefully if enough people follow suit, Disney will get the idea.

Owen

On Jan 21, 2021, at 18:29 , Travis Garrison <tgarrison@netviscom.com> wrote:

What's all your opinion when company's such as Disney actively recommend disabling IPv6? They are presenting it as IPv6 is blocking their app. We all know that isn’t possible. Several people have issues with their app and Amazon firesticks. I use my phone and a chromecast and I see the issues when IPv6 is enabled. We are in the testing phase on rolling out IPv6 on our network. All the scripts are ready, just trying to work through the few issues like this one.

https://help.disneyplus.com/csp?id=csp_article_content&sys_kb_id=c91af021dbe46850b03cc58a139619ed

Thank you
Travis



-----Original Message-----
From: NANOG <nanog-bounces+tgarrison=netviscom.com@nanog.org> On Behalf Of Mark Andrews
Sent: Thursday, January 21, 2021 7:45 PM
To: Sabri Berisha <sabri@cluecentral.net>
Cc: nanog <nanog@nanog.org>
Subject: Re: DoD IP Space

IPv6 doesn’t need a hard date.  It is coming, slowly, but it is coming.
Every data set says the same thing.  It may not be coming as fast as a lot of us would want or actually think is reasonable as ISP’s are currently being forced to deploy CGNs (NAT44 and NAT64) because there are laggards that are not doing their part.

If you offer a service over the Internet then it should be available over
IPv6 otherwise you are costing your customers more to reach you.  CGNs are not free.

Mark

On 22 Jan 2021, at 06:07, Sabri Berisha <sabri@cluecentral.net> wrote:

----- On Jan 21, 2021, at 6:40 AM, Andy Ringsmuth andy@andyring.com wrote:

Hi,

I’m sure we all remember Y2k

Ah, yes. As a young IT consultant wearing a suit and tie (rofl), I
upgraded many bioses in many office buildings in the months leading up to it...

I’d love to see a line in the concrete of, say, January 1, 2025,
whereby IPv6 will be the default.

The challenge with that is the market. Y2K was a problem that was
existed. It was a brick wall that we would hit no matter what. The
faulty code was released years before the date.

We, IETF, or even the UN could come up with 1/1/25 as the date where
we switch off IPv4, and you will still find networks that run IPv4 for
the simple reason that the people who own those networks have a choice. With Y2K there was no choice.

The best way to have IPv6 implemented worldwide is by having an
incentive for the executives that make the decisions. From experience,
as I've said on this list a few times before, I can tell you that
decision makers with a limited budget that have to choose between a
new revenue generating feature, or a company-wide implementation of
IPv6, will choose the one that's best for their own short-term interests.

On that note, I did have a perhaps silly idea: One way to create the
demand could be to have browser makers add a warning to the URL bar,
similar to the HTTPS warnings we see today. If a site is IPv4 only,
warn that the site is using deprecated technology.

Financial incentives also work. Perhaps we can convince Mr. Biden to
give a .5% tax cut to corporations that fully implement v6. That will
create some bonus targets.

Thanks,

Sabri

--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org