Home
Vendor
Project
  Phase I
Press
  Phase I
About
You Are Using IPv4 To Access This Site
Your IP Address is: 38.103.63.61

[moonv6] FW: IPv6 Deployment from NAv6TF

New Message Reply Date view Thread view Subject view Attachment view

From: Bound, Jim (Jim.Bound@hp.com)
Date: 11/29/05


FYI. Got this today and had to respond before end of day. I felt important given where the journalist was coming from and I felt a good place.

/jim

-----Original Message-----
From: Bound, Jim
Sent: Tuesday, November 29, 2005 7:12 PM To: David Geer
Cc: Bound, Jim
Subject: IPv6 Deployment from NAv6TF

Hello David,

Sorry I could not get this response to you until later today. Thanks for understanding I can only speak as CTO IPv6 Forum www.ipv6forum.org and Chair NAv6TF www.nav6tf.org. I also attach a deployment paper for you I wrote with support from members across the IPv6 Forum, and our supporters in both industry and government, that may be of value to your reporting project.

> Obstacles to or reasons for adoption

Obstacles to adoption vary but there are some underlying reasons and different market issues:

Most Providers and large Enterprises have already adopted IPv6 as test network, or at pre-planning stages, and IPv6 is in process. NAv6TF has some providers working with us now on our NAv6TF Moonv6 Project see www.moonv6.org.

Key obstacles are:

IPv6 Services must be available from the variant Providers (e.g. ISPs, Broadband, Wireless, Cellular), but that has already begun with some trials, and we will see services begin in 2006 is my belief based on watching deployment for some time.

The large enterprise and consumer applications need to be ported to IPv6, so there is an application base for IPv6. But, using IPv6 transition mechanisms they can be treated as legacy and access them to them can be done from native IPv6 dominant networks.

IPv6 will be held to a higher bar regarding security than when the Internet was first deployed, thus IPv6 Security and Policies need to be defined. But, IPv6 can be secured it just requires planning.

For the consumer market, the Providers need to support IPv6 addresses, and the current Firewalls/Gateways in the home and small business need to provide the ability to support IPv6 native or IPv6 Tunneling through IPv4 initially to begin that market. There are work around solutions, but those are sub-optimal, and are suspect from security view.

What will cause the adoption of IPv6 in the private sector in the U.S. is as follows:

I cannot think of a vendor or platform that does not support production IPv6 with products today, at least the core IPv6 specifications and add-on base Internet requirements for anyone wanting to develop an IPv6 test network, which is wise to do before production deployment as with any new network component within the Internet protocol architecture suite.

> Opportunity cost of converting from IPv4 to IPv6 questioned by US Gov?

This seems old as the U.S. Government has now a plan to transition to IPv6 by 2008. Have you seen that document if not I can send to you?  

> US deployment too slow and letting Asia etc get an edge?

This is simply an invalid statement by some who do not understand the deployment model of technology, or the economics of change to core technology, in my opinion. US Deployment is not slow I keep telling people, could it be faster, absolutely. The US Government is deploying IPv6, most US Internet Providers are deploying IPv6, many enterprises we cannot reveal are deploying IPv6, and the only market that does not have the necessary strategy at least initially in place is the consumer market. Before any entity can turn on IPv6 they have to set up a network test bed and verify the security guidelines and policy they want to implement to be secure, at least that is the NAv6TF recommendation. NAv6TF supports and endorses completely the security call to action and recommendations within the U.S. GAO report on IPv6 I also have attached for you David. As far as the question, is another region ahead of the U.S., that is simply invalid too. What other region has their entire Government completely planning to transition to IPv6 and in a formal Government document not in a Press Release? What other region has Moonv6? Many of the products that are being deployed world wide for IPv6 are built and developed right in the U.S. and Canada.

Could there be an influx of IPv6 only products into the U.S.? Yes of course there will be at some point in time. But, that is wonderful news for IPv6 deployment, and I would think many businesses will welcome it and that will certainly help accelerate IPv6 adoption in the U.S. and Canada too. Does the U.S. build most of those devices today? Not really, next time you order a laptop from any company track the shipping log. This entire discussion of the U.S. loosing out to other regions is not founded on solid business ground at all. What has changed with IPv6 is that the world has all tuned into the Internet and the entire world will now use the Internet for social, business, and many reasons, and that is a wonderful development and IPv6 will only make it a better experience for all.

We are talking about changing the network plumbing of the Internet and restoring end-to-end, and that is not going to happen overnight or without much testing and verification of connectivity, interoperability, discovery, security, and support of end-to-end, which are the principles and base of net centricity. We do not want to deploy IPv6 as band-aid in the U.S. but correctly, because of some illusion that the U.S. will suffer because other regions are "perceived" to be ahead. That is just a bad technical and business strategy. Any competition for IPv6 is good and natural supportive phenomena to assist the deployment of IPv6. Clearly there will be new markets, but IPv6 is only one small part of that opportunity many reference as the Next Generation Networks market, but without IPv6 I don't think it can happen or evolve to speculation for that new market, at all. IPv6 is required for Next Generation Networks to happen.

> Interoperability of IPv4 and IPv6 during transition?

This is very well understood and products today and services from the private sector can implement the necessary tools to provide a transition to IPv6. That transition is the cornerstone key functional component of the interoperability between the IPv4 and IPv6. There are well defined specifications for this deployment from the IETF standards organization and defacto solutions supported by industry implementation. Clearly we have a learning curve to absorb the eventual 3G/IMS and other Next Generation Network technologies that will drive IPv6 adoption and the end-to-end model. The important take away is there are multiple methods to transition to IPv6 and one-size-does-not-fit-all, and several tools and methods exist to meet different business requirements and rate of adoption to transition to IPv6.

> IPv6 security concerns?

Please see the GAO report attached and NAv6TF site where we respond to the U.S. Government on Security as matter of public record to the Department of Commerce and NAv6TF has worked with other Government Agencies. If one has IPv4 security mechanisms they will need those for IPv6 is the base bottom line. But, as we move to end-to-end we will need a completely new paradigm in Firewalls, Gateways, and at the edge of the network to support and end-to-end secure mobile and peer-to-peer network model.

> IPv6 privacy concerns?

Again way overrated and not much different than IPv4. The IETF in fact developed a specification for IPv6 to reduce attacks on privacy, by changing the identifier for an IPv6 address periodically and that is a first, and good vision on the part of the IETF. But, the issues of privacy on a wireless network, attacks of the network, and all the known issues of privacy on a network from the network being compromised are the same for IPv4 and IPv6. It is something we are working on within the Internet cyberspace technical community in addition to IPv6.

The IPv6 Forum and NAv6TF have more new markets to work with such as Financial, Transportation, Manufacturing, and Health industries, so we still have much to do and as all volunteer non-profit vendor neutral body these are in our plan to show "how you can deploy IPv6" as best we can in 2006. This will entice the Application developers even further, and they will come along too, until they do they can be treated as legacy IPv4 function and tunnels to them with IPv4 can be the deployment strategy. It is now in the business interest today for application developers and providers to support IPv6.

Thanks for the opportunity to respond David, /jim
CTO IPv6 Forum www.ipv6forum.org
Chair NAv6TF www.nav6tf.org

New Message Reply Date view Thread view Subject view Attachment view

This archive was generated by hypermail 2.1.7 : 12/01/06 EST