On Thu, Oct 21, 2010 at 10:20 PM, George Bonser <gbon...@seven.com> wrote: > > >> -----Original Message----- >> From: Christopher Morrow > Sent: Thursday, October 21, 2010 9:49 PM >> To: bmanning >> Cc: NANOG >> Subject: Re: IPv4 sunset date revised : 2009-02-05 > > >> >> (now I'm teasing.. .Bill where's your docs on this fantastic new >> teknowlogie?) >> > > I found it here: > > http://www.ivi2.org/ > > But the readme is a bit confusing: > > http://www.ivi2.org/code/00-ivi0.5-README > > Trying to figure out how they map a /70 v6 prefix to a /30 v4 prefix > assuming the mapping is to be 1-1 >
Right, 1 to 1 does not solve any IPv4 exhaustion problems. Going back to the title of the thread, IVI does not help you sunset IPv4 since the same amount of IPv4 is required. NAT64 is the protocol that helps you "sunset" IPv4 by providing native IPv6 to the user and doing a protocol translation similar to NAPT to IPv4 destination. Thusly, IPv6 end to end applications benefit from not having a middle box and experience more features (e2e) and less flaky NAPT, ... keep in mind that NAPT is the status quo in many places, especially in mobile wireless, end to end IPv6 is an upgrade. This is pretty impactful since major internet destinations like Google, Netflix, Facebook have IPv6 deployments in place today. For many, this is a ~50% reduction in NAT which is ~50% increase in E2E communication (less cost, better quality). Since economics and user experience are involved, this is a real path to migrating from IPv4 to IPv6. The right incentive structure is in place for both the service provider who is out of addresses and the consumer who wants rich e2e communication. Shameless plug, i have it working here for over 9 months http://groups.google.com/group/tmoipv6beta Cameron
