<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Apr 30, 2009, at 3:59 PM, Tony Valenti wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">I personally would love for us to be able to provision new equipment on IPV6, but the fact remains, as a small-time web hosting service provider, if I put websites on an IPV6 address, according to Network World (<a href="http://www.computerworld.com.au/article/279477/ipv6_fails_reach_5_percent_internet">http://www.computerworld.com.au/article/279477/ipv6_fails_reach_5_percent_internet</a><span class="Apple-converted-space"> </span>), 95% of the internet would not be able to talk to our gear, and of course, we'd go out of business if we told customers "Don't worry about your website and email being down - the most tech savy 5% of the internet can still email you".</span></blockquote></div><br><div>Following up on Joe's comment that running dual stack is going to be de rigeur for a while.</div><div><br></div><div>I understand why you might want to start deploying IPv6 in addition to IPv4 connectivity. At this point, I don't at all understand why someone would shut down IPv4 while doing so. That point will come (see previous note on this list about a possible projection for the next 20 years), but it will come when business requirements don't support IPv4 any more.</div></body></html>