[ipv6hackers] IPv6 security (slides and training)

[Fred Bovy]

Jim,

I said it reminds me. I did not say it was analog to Y2K!

For me it is the same fud to generate anxiety and fear to make people think that something really bad is about to happen. 

Ok y2k costs money to upgrade applications but ipv6 will also cost money for the same reason!

You say there is no deadline but we don't have any more ipv4 @ so there is à deadline for entreprises which do not own à large ipv4 block and will have no choice than starting ipv6!

Ok I am not going to continue to answer point by point as again I did not say it was the same but just remind me all the noise we did for a very simple operation. I think that upgrading an ip application for ipv6 will even be simpler than fixing y2k applications. 

But still there is a strong lobbying to convince the customers that upgrading a network protocol is going to be a very complex thing and it is the first time in the networking history that there is so many tools and discussion for a simple migration!

Fred Bovy

Mobile:33676198206
Skype:fredericbovy



Le Nov 11, 2011 à 12:42 AM, "Leinweber, James" <jim.leinweber at slh.wisc.edu> a écrit :

> Fred Bovy:
>> This transition to IPv6 more and more reminds me the Y2KŠ Which was just a
>> non-event!
> 
> I think that's an unhelpful analogy.
> 
>  - Y2K was a non-event for consumers
> 
>  - Y2K was a very expensive event for businesses, involving much work by
>     DBA's and application programmers
> 
>  - Y2K had a hard deadline
> 
> In contrast, IPv4 exhaustion and the  IPv6 transition
> 
>  * doesn't make the IPv4 internet stop working
>     (whereas failure to act on Y2K caused applications to fail)
> 
>  * doesn't have a hard deadline
> 
>  * is more pervasive
>     (You can't limit the impact to your DBA's and app developers)
> 
>  * is less expensive than Y2k
>      (you can support IPv6 on your front end without ripping
>       IPv4 out of your back end;
>       a lot of your equipment and OS's have already picked up
>       IPv6 support as a side effect of your normal replace/upgrade
>       cycles;
>       converting apps to support IPv6 is less work than Y2K, because
>       we store fewer addresses than dates and manipulate them much
>       less.)
> 
>  * is more visible to consumers
>     (OK, so dual-stack web browsers with happy eyeballs and native
>      dual-stack uplinks are pretty invisible.       
>      Negotiating v6 access with your ISP, replacing your wifi and
>      broadband gear with v6 capable stuff, and the vagaries of
>      watching your applications fail to cope with tunnels and carrier
>      NAT are highly visible.)
> 
> The analogy I have been using in my own presentations is that IPv6 is
> like the conversion from analog to digital TV (at least in the US);
> new gear all around for mostly the same content.
> 
> -- Jim Leinweber
> State Laboratory of Hygiene, University of Wisconsin - Madison
> <jim.leinweber at slh.wisc.edu>       phone +1 608 221 6281
> PGP fp: D573 AF7D F484 EE2A F0B6  B7DB A870 7518 F87D A0D1
> 
> 
> 
> 
> _______________________________________________
> Ipv6hackers mailing list
> Ipv6hackers at lists.si6networks.com
> http://lists.si6networks.com/listinfo/ipv6hackers