nanog mailing list archives
Re: How to force rapid ipv6 adoption
From: "George, Wes" <wesley.george () twcable com>
Date: Fri, 2 Oct 2015 16:01:54 +0000
On 10/2/15, 10:48 AM, "NANOG on behalf of Cryptographrix" <nanog-bounces () nanog org on behalf of cryptographrix () gmail com> wrote:
For ISPs that already exist, what benefit do they get from providing/allowing IPv6 transit to their customers?
If they'd like to continue growing at something above churn rate, they need additional IP addresses to give their new customers. Buying those addresses, undertaking projects to free up addresses from other internal uses, or using CGN to share existing ones all have nontrivial costs. The fewer things they need to make work on legacy IPv4, the lower those costs can be (less CGN capacity since IPv6 traffic bypasses the NAT, less support costs because less stuff breaks by going through the NAT, etc).[1,2,3] But that's dependent on content and CPE supporting it, so a number of large ISPs have chosen to go ahead and deploy[4], and focus on pushing the progress on the other fronts so that they can see that benefit of deploying. Wes George [1] https://www.nanog.org/meetings/abstract?id=2025 [2] https://www.nanog.org/meetings/abstract?id=2075 [3] http://nanog.org/meetings/abstract?id=2130 [4] http://www.worldipv6launch.org/measurements/ Anything below this line has been added by my company’s mail server, I have no control over it. ----------- ________________________________ This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
Current thread:
- Re: How to wish you hadn't forced ipv6 adoption (was "How to force, (continued)
- Re: How to wish you hadn't forced ipv6 adoption (was "How to force Joe Greco (Oct 02)
- Re: How to wish you hadn't forced ipv6 adoption (was "How to force rapid ipv6 adoption") Stephen Satchell (Oct 02)
- Re: How to wish you hadn't forced ipv6 adoption (was "How to force rapid ipv6 adoption") Måns Nilsson (Oct 06)
- Re: How to wish you hadn't forced ipv6 adoption (was "How to force rapid ipv6 adoption") George Michaelson (Oct 06)
- Re: How to wish you hadn't forced ipv6 adoption (was "How to force rapid ipv6 adoption") John Levine (Oct 07)
- Re: How to force rapid ipv6 adoption Valdis . Kletnieks (Oct 02)
- RE: How to force rapid ipv6 adoption Steve Mikulasik (Oct 02)
- Re: How to force rapid ipv6 adoption Cryptographrix (Oct 02)
- Re: How to force rapid ipv6 adoption Stephen Satchell (Oct 02)
- Re: How to force rapid ipv6 adoption Cryptographrix (Oct 02)
- Re: How to force rapid ipv6 adoption George, Wes (Oct 02)
- Re: How to force rapid ipv6 adoption Cryptographrix (Oct 02)
- Re: How to force rapid ipv6 adoption George, Wes (Oct 02)
- Re: How to force rapid ipv6 adoption Owen DeLong (Oct 03)
- Re: How to force rapid ipv6 adoption Stephen Satchell (Oct 02)
- Re: How to force rapid ipv6 adoption Mark Andrews (Oct 02)
- Re: How to force rapid ipv6 adoption Brett A Mansfield (Oct 02)
- Re: How to force rapid ipv6 adoption Robin Johansson (Oct 02)
- Re: How to force rapid ipv6 adoption Owen DeLong (Oct 03)
- Re: How to force rapid ipv6 adoption Israel G. Lugo (Oct 07)
- Re: How to force rapid ipv6 adoption Mark Andrews (Oct 07)