On 27/05/2007, at 9:05 PM, Martin Hannigan wrote:
On 5/26/07, Chris L. Morrow <christopher.morrow@verizonbusiness.com> wrote:
On Sat, 26 May 2007, Jared Mauch wrote:
on things, could cost some money. I'd love to see google or Y! with an AAAA record. Or even Microsoft ;)
i agree 100%, which is why I posted something similar almost 2 years ago now :( It'd be very good to get some actual content on v6 that the masses want to view/use.
Isn't the driver going to be scarcity and/or expense of v4 addresses?
Sure, but it's not as simple as just giving v6 addresses to end users one day, even if your entire network and backend systems support it. If you were an end user, calling up your ISP to get a new DSL line, and were told you couldn't have an IPv4 address, only IPv6, and "Sorry sir, Google (etc.) won't work until they upgrade." would you: a) Stick it out with that provider, even though there is no content for you to access. b) Hang up. If you answered (a) to the above, run through that again, from say, your Mother's perspective. Now that NAT-PT is deprecated (ie. can't be used as an excuse to not move), we need to move the large (and small) content providers to dual-stack, before we move any customers to v6-only. Content providers have all the IPv4 addresses they need already, they're not going to be asking for more any time soon. If someone has some bright ideas on how to transition without loss of service to *someone*, I'm all ears. (IPv4 NAT is not a bright idea.) In addition, when 2010 [1] rolls around, are the free CPE that your customers were given in the last 7 days upgradable to support IPv6? This is, of course, assuming we don't hold off until we've got a different IPv6 architecture as a result of the RAWS stuff. [2] While we're here, can someone point me in the direction of any ongoing discussion/work in this area? I attended the APRICOT workshop, but where to go to keep up with things/get involved isn't obvious. -- Nathan Ward [1] http://www.potaroo.net/tools/ipv4 [2] http://tools.ietf.org/id/draft-iab-raws-report-02.txt