Re: [v6ops] reclassify 464XLAT as standard instead of info

[Gert Doering <[e-mail]>]

Hi,

On Fri, Sep 22, 2017 at 06:10:18PM +0200, Gert Doering wrote:
> Right now, there's so much *content* IPv4-only that eyeball networks need
> to put up CGN boxes to enable reachability to that content - and if these
> boxes are in place anyway, what incentives does content have to enable
> IPv6?  Looking at the Alexa Top sites, I see lots of red on Eric's 
> page.  Basically, everything that's not Google or happens to sit behind
> Cloudflare (for DE)... :-(

Oh.  As a side note, "a fried" tells me that a major audio streaming
platform in DE had to turn off IPv6, because Samsung.

"If we listen to the stream over IPv4, and the phone goes to sleep, the
stream will continue playing.  If we listen over IPv6 and the phone goes
to sleep, it will stop".

Since there is no way to get Samsung to fix their shit (like, Google,
having proper requirements for Android vendors...) the radio station
decided that it's not worth the hassle and just turned off IPv6 again -
much less work than building something into their platforms that redirects
broken clients to an IPv4-only site and keeps IPv6 for the rest.


And stories like this is why I'm not overly optimistic anymore, after
barely 20 years of advocating IPv6.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: [phone]           USt-IdNr.: DE813185279