Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 06 Mar 2008 01:32:36 +1100
From:      Mark Andrews <Mark_Andrews@isc.org>
To:        Andy Dills <andy@xecu.net>
Cc:        vadim_nuclight@mail.ru, freebsd-stable@freebsd.org
Subject:   Re: INET6 required for SCTP in 7.0? 
Message-ID:  <200803051432.m25EWaeT035807@drugs.dv.isc.org>
In-Reply-To: Your message of "Wed, 05 Mar 2008 08:22:11 CDT." <20080305082031.E37745@shell.xecu.net> 

next in thread | previous in thread | raw e-mail | index | archive | help

> On Wed, 5 Mar 2008, Mark Andrews wrote:
> 
> > 	It would be better to remove the option all together.  IPv6
> > 	is no longer a protocol under development.  There is no
> > 	need to make it optional any more.  Having it there really
> > 	sends the wrong signal.
> 
> With all due respect, let's face a couple of facts.
> 
> IPv4 is going to be the primary protocol for several years to come. There
> are a few critical reasons, and few people like to point out just how
> naked the emperor is:
> 
> - Providing IPv6 currently (and for the forseeable future) provides no
> return on investment (ROI). Service Providers can't make more money with
> IPv6, businesses do not get any sort of competitive or perceived advantage
> from deploying IPv6, and end users certainly don't want to deal with it.
 
	Service providers get paid to push IP packets.  They shouldn't
	care which protocol version is in the header.  What they
	should be worried about is ensuring that they are here in
	4 years time.
	
	It actually takes time to fill in the missing pieces and
	the only way to find the missing pieces is to bring up IPv6
	networks.

	Most end users won't even know that they are running IPv6
	connections.  I had to look at netstat to see which protocol
	was being choosen on my father's box.  I'm sure he had zero
	knowledge that he was using IPv6 (6-to-4).

	An IPv6 network really is as easy if not easier to run than
	a IPv4 network.

> - To route IPv6 with the same features and packet forwarding rate as with 
> IPv4, nearly every network will be forced to purchase expensive router 
> upgrades with no other real benefit beyond IPv6 connectivity (which again 
> provides no ROI to justify the capex). Nobody is going to do forklift 
> upgrades just for IPv6, but as routers get normally upgraded IPv6 
> functionality will indeed slowly expand.

	And the same arguement was put out 6 years ago.  The backbone
	really has gone dual stack while you wern't paying attention.

	What's needed now is the SOHO CPE equipment sold to the non
	Asian market to catch up.
 
> - IPv6 provides almost no technological upgrades beyond additional address
> space. DHCP addressed the auto configuration feature, VPNs addressed
> IPsec.

	That extra address space really is a big advantage.  It
	really is so much better to be able to get to machines you
	need to without have to manually setup application relays
	because you couldn't get enough address space to be able
	to globally address everything want to.
 
> - IPv4 address spaces will eventually transition to a market commodity
> model, providing a financial incentive that will encourage significant   
> optimization and provide motive for providers to audit their allocations,
> and for businesses to part with IP space that they no longer properly     
> utilize. The cost of acquiring IPv4 space will be less than the cost of
> upgrading to IPv6.
>
> Therefore, given a lack of ROI or sufficient technological motivation, and
> given the significant potential for optimization of existing IPv4 space   
> both via technology and financial incentive, I see a minimum of five years
> before IPv6 is common. 
> 
> In the meantime, I'd like to only enable IPv6 on IPv6 enabled networks.

	So make the network IPv6 enabled.  Both my home network and
	the office networks have bee IPv6 enabled for years now.
	My ISP doesn't support IPv6 yet though I know that have
	IPv6 netbocks for themselves now if not for the customers
	at this stage.

	There is a reasonable chance that this mail will leave here
	over IPv6 for some of the recipients.  It will almost
	certainly travel over IPv6 for at least one hop.

	Mark
 
> Andy
>    
> 
> ---
> Andy Dills
> Xecunet, Inc.
> www.xecu.net
> 301-682-9972
> ---
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200803051432.m25EWaeT035807>