North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
Re: Another driver for v6?
Google's statistics are using themselves as the subject, a fixed point in the network. It's hard to guarantee that subjective experience is going to be equal across the entirety of the network, but let us presume for the purpose of discussion that they are. I think the point in the final analysis for customer-facing FQDN's is; 1) How much in USD is 0.09% loss of sales/customer-experience/etc? 2) What amount in USD is acceptable to lose, in order to gain IPv6's advantages? Be sure to include recurring support costs, abuse, and engineering manhours for the design and deployment. Note that the second question is a subjective cost/value analysis, and the typical operator may not find much value in IPv6 (today). So again, in summary, I absolutely think every network needs to be getting IPv6 into their workshops. You have to be prepared for what's coming. I'm still recommending a variety of caution in that first deployment on production systems. -- Ash bugud-gul durbatuluk agh burzum-ishi krimpatul. Why settle for the lesser evil? https://secure.isc.org/store/t-shirt/ -- David W. Hankins "If you don't do it right the first time, Software Engineer you'll just have to do it again." Internet Systems Consortium, Inc. -- Jack T. Hankins