Will IPv6 deployment fail?

If I do not deploy IPv6, will it collapse? Will the end of the world come? Will the Internet continue to run? Will enterprise computers crash into a pool of data? The answer is simple: No. At least not yet. However, enterprises may have to consider some things.

ISP (Internet Service Providers) will not be stupid to cut off IPv4 access when they start to launch IPv6. If they do this, only a few websites can access the Internet at that time, because most content providers have not connected their systems that can access the Internet to the IPv6 internet. ISP users send a large number of service calls to the ISP and transfer their services to other places.

However, this shows an interesting dilemma for ISP. If the report on IPv4 address shortage is true, how can service providers continue to expand their user base? This issue is particularly prominent in Asia. The increasing middle-class in Asia is using the Internet, and the IPv4 address space of ISP is beginning to run out. When the IPv4 addresses in the United States and Europe are used up, they are not far away.

In this situation, the ISP is starting to deploy IPv4 and IPv6 in dual-stack configuration mode for its customers. IPv6 addresses are globally unique. However, IPv4 addresses share IPv4 addresses with multiple users through NAT.

The obvious advantage of this solution is that an IPv4 address can support thousands of users, significantly improving the available IPv4 lifecycle. So what is the problem? If the ISP ensures that their IPv6 users can still use the shared IPv4 address's dual-stack solution for IPv4 connections in the foreseeable future, why are you eager to put your organization's content on the IPv6 Internet?

Large Scale NATLSN)

To answer this question, we must learn this LSN technology more carefully and ask ourselves if this technology will cause problems when users try to connect to your system. Indeed, in many cases, there are three types of problems:

1. features: the isp lsn solution cannot be guaranteed to be compatible with your applications. Each ISP may deploy the LSN solution of different vendors, which means that you do not have a reasonable method to test every possible technology. The result may be that your application cannot be applied to a large number of global users.

2. Performance: like the traditional network address resolution solution, the LSN solution maintains a status table for the communication flow through this device. Each data packet from this device starts to view this status table. Have you seen the problem here? In fact, there are many problems.

First of all, this may cause bottlenecks and slow loading of your website on your browser. Worse, the LSN device is disconnected. As the load on the LSN device increases, this will be a hybrid problem. Second, because all the two-way communication traffic at a specified time must pass through this LSN device, there is only one way for your communication to access the ISP network. Think about the golden gate bridge. What if all the cars use a one-way street to the other side.

3. Reliability: The LSN device may generate a single fault point in the ISP network. The Internet is designed to allow communication to use many paths to reach the destination. However, as discussed above, because the LSN requires that all data packets in the communication traffic use the same path through this LSN device, an LSN fault can isolate the ISP customer from the IPv4 internet. Let's continue with the Jin men bridge. Imagine what would happen if the Jin men bridge was closed for repair or collapsed.

You may think that many problems here are managed by the ISP, not just me. You are right. However, when your customers and users cannot access your website, the ISP problem becomes your problem.

Therefore, as we can see, although ISP is planning to provide a mechanism to maintain IPv4 connections to their IPv6 user base, the effect is not ideal. Frankly speaking, you cannot rely on others (in this case, ISP) to do heavy work for you. Only you can ensure that your user group can access your applications, whether on an IPv4 or IPv6 network. This ensures that your application can be accessed through IPv4 or IPv6.

Therefore, if you do not use IPv6 at present, the end of the world will not come. However, this is a bad omen. So where do you start? If your organization has not yet begun to transition to IPv6, do not panic. There are many resources to help.

Three key points of IPv6 deployment

First, focus on the big environment. You (or the supervisor responsible for IPv6 transition) need to be detached. To transition to IPv6, you need to complete a large number of small tasks, which can easily cause you to get stuck. Someone needs to guide the actions of the entire institution. That person will not have time to modify the vro or server settings. Make sure that you see the deep forests and do not indulge in several trees.

Second, do not do this independently. If you focus on the big environment, who is responsible for the task of transferring the organization to IPv6 (such as software upgrade, hardware upgrade, route modification, operating system modification, firewall policy, and so on ). This is where the concept of "transitional region" plays a role. The basic idea is to divide the organization into a functional group, distribute the workload to the whole organization, and use each person's time to complete small tasks. This not only reduces the burden on a few people, but also achieves another important goal-introducing IPv6 into culture so that everyone can consider this matter.

Third, implementation is prioritized. You do not need to upgrade multiple products at the same time or use IPv6 addresses to replace the IPv4 addresses of the entire organization. You need to focus on a target over a period of time. The most important thing is your internet applications (mainly websites and emails ). Make sure that as IPv6 users around the world get online, you will not share your Internet. Next, let the desktop team of your organization ensure that the internal user workstation is transitioned to IPv6. In this way, they can access the Internet and business partners on IPv6. Once these two goals are completed, you can quickly and stably transition the rest of the infrastructure and internal applications to IPv6.

Therefore, if we do not deploy IPv6 at present, will the sky collapse? Probably not. However, the longer you wait to connect your content to the IPv6 Internet, the higher the risk that your users will not be able to access. Now you have to prepare the Transition to ensure that the content is continuously provided to users.

Edit recommendations]