WIndows Updates Fail Via IPv6 - Update!

Thu Mar 7 16:06:54 UTC 2019

Hey Saku,

> From: Saku Ytti <saku at ytti.fi>
> Sent: Thursday, March 7, 2019 3:29 PM
> 
> On Thu, Mar 7, 2019 at 5:19 PM <adamv0025 at netconsultings.com> wrote:
> 
> > From past experience my assumptions would be more along the lines of if
> it's not mainstream there's a higher likelihood that it might trigger exceptions
> in code.
> 
> My point is, let it break. Don't pre-emptively drop things that you don't know
> to be harmful, but where dropping definitely is harmful.
> 
> After risk has realised you have more data about the risk. If it has never
> realised you have no idea. If we extrapolate this culture of fear, we will only
> have HTTPS open, nothing else, and we have to build then next-gen stuff as
> an overlay using HTTPS transport.
> 
Sure I get it it's a very valid and a noble point, 
But what you're asking is let it break (yes potentially -it's just probability until it happens) for 1000s of subs just so that one kiddo has a working niche feature, I can already see what board has to say about that -screw that kid we have money to make there's our brand at stake (yes again just potentially -it's just probability until it actually happens) -but you'll already know what they're gonna say.
So yes on a technical level I agree with you, but on a commercial level it's a tough case to make.

And the same logic applies to the other thread around BGP communities filtering...

adam