What is the implementation path for the evolution from IPv4 to IPv6?

Technical model for transformation from IPv4 to IPv6

The industry provides three solutions for the transformation from IPv4 to IPv6, namely dual-stack technology mode, tunnel technology mode, and address translation mode.

1. Dual-stack technology model: Run two independent planes on the same network: an IPv4 network plane and an IPv6 network plane, each maintaining its own IGP. /EGP status and routing. In this mode, IPv4 and IPv6 coexist, which does not affect existing IPv4 services and can also meet the new needs of IPv6. However, the implementation cost in this mode is relatively high. Firstly, it requires the support of network equipment of the entire network. Secondly, it is difficult to adjust IGP/EGP of the entire network equipment. If it is only implemented in a small area, this is a better choice. model.

2. Tunnel technology mode: This mode is used at the boundary between IPv4 and IPv6. First, use the IPv4 network to establish an IPv4 tunnel, and then implement IPv6 point-to-point access, which is usually used for IDC egress boundaries or internal IGP cross-domain access. Technical protocols include 6in4 tunnel, DS NAT, DS-Lite, etc. Tunnel mode is the most convenient of the three transformation methods, but it has certain requirements for the intranet IGP protocol and key link traffic usage.

3. Conversion mode: That is, without changing the existing network structure, IPv4 to IPv6 or IPv6 to IPv4 access conversion is performed through the address translation protocol. It can meet the bidirectional access requirements between IPv4 and IPv6. Technology deployment protocols include NAT 46, which is generally oriented to data center egress and provides mapping from outside to inside and from inside to outside. This mode has high requirements for device performance and difficulty in supporting high concurrent services, so it is suitable for services with small sessions.

Hard conditions on which the implementation of IPv4 to IPv6 relies

1. Network equipment : The switches, firewalls and operating systems involved are all To support the IPv6 protocol suite.
2. Export operator: Need to provide IPv6 access capabilities.
3. Internal business transformation: At the business code level, it is necessary to add support for the IPv6 protocol stack.

IPv6 implementation progress

1. Selection of transformation model
To implement IPv6, we must first meet the requirements for implementing IPv6 At the same time, the core requirement is to not only meet the high-quality, low-latency access of IPv4 users, but also further ensure the access of new IPv6 users. Through the analysis of the three transformation models, the "dual-stack model" is more suitable as the technical support guide for Gitui in promoting the IPv6 transformation process.

2. Transform the topology

This transformation is divided into two parts: First, complete the IPv6 access transformation of the directly connected public network server group: adopt Dual-stack technology model, one network card interface runs both IPv4 and IPv6 addresses. By binding the domain name A record, the traffic diversion from the public network to the IPv4 network card is completed, and by binding the AAAA record, the traffic diversion from the public network to the IPv6 network card is completed. The second is business transformation: complete the transformation of the SDK's support for the IPv6 protocol family.

3. Implementation progress

The above is the detailed content of What is the implementation path for the evolution from IPv4 to IPv6?. For more information, please follow other related articles on the PHP Chinese website!