RE: dual stack & IPv6 on by default

["Bound, Jim" <Jim.Bound@hp.com>]

> 
> So for people who want to go dual-stack in their workplace 
> yet take devices 
> to IPv4-only networks that's the problem they face.   Of 
> course you get what 
> you deserve maybe for the application writer trusting 
> presence of a DNS 
> record as an indication of connectivity.

This is for me key.  I believe in punishment, penalties, and
accountability :--) So if you do stupid things you will learn from that.

But also we cannot possibly correct every network problem like this in
IPv4 or IPv6.  Again it is not indicative of just IPv6 but IPv4 too.

Also I want to restate.  For some if IPv6 don't work then they are dead.
Fall back to IPv4 is not an option.  I know users who are going to adopt
IPv6 with the intention of phasing out IPv4 as quickly as possible and
immediately move to dominant IPv6 routing backbones on their Intranet as
a strategy.  This is also becoming more and more prevalent exponentially
too.  My guess is they see the cost and decide lets just go to IPv6 as
quick as possible and get the pain over with.

This view is now as predominant as any other for deployment and I feel
many on this list don't "get it".  This is not mean't to be negative or
a challenge merely a statement.

/jim