IPv6 Network Deployment Monitoring and Analysis

Introduction The emergence of IPv6 can be traced back to the 1990s, when the development of IPv6 was initiated by the Internet Engineering Task Force (IETF) to solve the problem of IPv4 address exhaustion. In 1998, the IPv6 protocol specification was published . As IPv6 adoption accelerating over the past years, the IPv6 protocol was elevated to be an Internet Standard status in 2017.

Current IPv6 Deployment Status In the digital era, IPv6 deployment has become a core driver of network evolution. With the ongoing expansion of network scale and the rise of new applications, IPv6—equipped with extensive address space, enhanced security, and improved performance—serves as a critical enabler for network advancement. How to optimize and promote IPv6 deployment has thus become a widely addressed industry priority. As of 2023, significant strides have been made in the global deployment of IPv6. According to the statistics from the 'Global IPv6 Development Report 2024', in 2023 the deployment of IPv6 networks significantly accelerated, breaking through the 30% mark in global coverage for the first time. Among leading countries, the IPv6 coverage rate has reached or approached 70%, and the percentage of IPv6 mobile traffic has surpassed that of IPv4. documents the state of IPv6 network deployment in 2022, with Section 5 outlining key challenges including transition mechanisms, network management and operations, performance, and end-user experience. Additionally, 'ETSI-GR-IPE-001' also discusses the existing gaps in IPv6-related use cases.

Current Approaches to Monitoring IPv6 Deployment Several tools and platforms monitor IPv6 deployment, such as:

Internet Society Pulse: Curating information about levels of IPv6 adoption in countries and networks around the world.
Akamai IPv6 Adoption Visualization: Reviewing IPv6 adoption trends at a country or network level.
APNIC IPv6 Measurement: Providing an interactive map that users can click on to see the IPv6 deployment rate in a particular country.
Cloudflare IPv6 Adoption Trends: Offering insights into IPv6 adoption across the Internet.
Cisco 6lab IPv6: Displaying IPv6 prefix data.
Regional or National Monitoring Platforms: Examples include the NZ IPv6, the RIPE NCC IPv6 Statistics, and the USG IPv6 & DNSSEC External Service Deployment Status, among others.

While valuable for high-level trend analysis, these tools exhibit significant limitations for operational purposes.

Problem Statement

Fragmented Monitoring Coverage Monitoring points are predominantly concentrated in backbone networks , lacking fine-grained visibility into user terminals, access networks, and application endpoints.

Single-Dimensional Evaluation Assessments primarily rely on basic metrics like connection availability and address allocation rates, lacking a holistic view of service continuity, transmission quality, network element readiness, and active connection states.

Lack of Cross-Domain Correlation Data silos exist between different network domains (e.g., fixed, mobile, core, application), preventing end-to-end path analysis and fault correlation .

Insufficient In-Depth Analysis Incomplete IPv6 transformation in private applications and content delivery chains (e.g., secondary/tertiary links, multimedia content) remains difficult to detect, as deep monitoring capabilities for these scenarios are lacking.

Limited Dynamic Prediction Current models struggle to quantify the impact of external factors (e.g., policy changes, user behavior, market dynamics) on IPv6 evolution, limiting proactive planning.

Framework for IPv6 Deployment Monitoring Analysis This framework is designed to overcome the above challenges through the following core principles:

Unified Data Collection: Standardized interfaces for cross-domain data ingestion.
Correlation analysis: Integrated data fusion and cross-domain analytics.
Service-Oriented Metrics: A comprehensive indicator system aligned with business objectives.
Visualized operation: Dashboards and visual tools to support key operational decisions.
Extensibility: Leverages existing monitoring infrastructure and supports integration with external systems.

IPv6 Network End-to-End Monitoring and Analysis System Architecture The system architecture is divided into three layers from top to bottom (as shown in Figure 1): the Data Collection Layer, the Intelligent Analysis Layer, and the Visualization Layer.

IPv6 Network End to End Monitoring and Analysis System

Data Collection Layer Defines unified interface standards to integrate multi-source data from user, network, and application sides, ensuring compatibility with multi-vendor devices and subsystems. Data collection relies on the existing technical system. The specific methods are:

It adopts the established standardized data collection mechanism to ensure data format uniformity
It accesses the existing network management systems of each professional network, and enables automatic collection and synchronization of indicator data through interface interconnection.

Intelligent Analysis Layer The Intelligent Analysis Layer develops multi-dimensional traffic analysis models to enable granular-level insights.

Multi-domain Traffic Correlation Analysis

Multi-Domain Traffic Correlation
- Network traffic analysis: Supports collection of IPv6/IPv4 inbound and outbound traffic at key network nodes. Analyze traffic change trends.
- Application traffic analysis: Support collection and analysis of IPv6/IPv4 active applications on the user side and application side. Calculate IPv6 traffic data for different service applications.
- Inter-network traffic analysis: Constructs region-application traffic matrices to analyze cross-operator paths and identify regional bottlenecks.
Dynamic traffic attribution
- It identifies traffic-constrained areas, formulates multi-dimensional investigation plans (i.e., network, user, and application)

Quality Deterioration Delimitation and Topology Restoration

User-level Topology Reconstruction: Models service chains to reconstruct end-to-end network topologies, enabling segmented diagnosis of latency/packet loss (e.g., home terminal, access network, application segments).
Segmented Quality Degradation Localization: Compares IPv4 and IPv6 performance segment by segment to pinpoint degraded network elements.

Visualization Layer The Visualization Layer provides indicator-driven presentation and decision support capabilities.

Indicator-Based Presentation It monitors and analyzes IPv6 support across all domains, decomposing metrics by business type and network segments.

Decision Support

Indicator System Based on a standardized indicator system, conduct IPv6 support monitoring and analysis for each professional domain, breaking down monitoring metrics into specific services and network segments.

Readiness Indicators
- Network Element Readiness: IPv6 Readiness of Network Equipment, End-User Devices, and Security Devices.
- Application Readiness: IPv6 Support Rate of Website Applications and Business Systems.
- Infrastructure Readiness: IPv6 Readiness of Fixed Internet, Mobile Internet, Private Lines, and Data Center Network (DCN) Infrastructure.
- Network Readiness:
  - IPv6 Network Coverage of Backbone Networks, Metropolitan Area Networks (MANs), Internet Data Centers (IDCs), and Private Lines.
  - End-to-End IPv6 Network Performance of Backbone Networks, Metropolitan Area Networks (MANs), Internet Data Centers (IDCs), Private Lines, and Access Networks.
- Cloud Readiness: IPv6 Readiness of Content Delivery Networks (CDNs), Cloud Services, Cloud Platforms, and DNS Servers.
Operational Metrics
- IPv6 Traffic: IPv6 Traffic Share in Cross-Border, Inter-Domain, Intra-Domain, Fixed Metropolitan Area Networks (MANs), Mobile Core Networks, Internet Data Centers (IDCs), Private Lines, and Applications.
- Active IPv6 Connections: Active IPv6 Connection Share in Fixed Metropolitan Area Networks (MANs), Mobile Core Networks, Internet Data Centers (IDCs), Private Lines, and Applications.
Quality Metrics
- DNS Resolution Performance
- End-to-End Latency
- Packet Loss Ratio
Policy Compliance Indicators.

Scenario-Based Capability Examples

IPv6 Monitoring and Analysis on the User Side Monitor and analyze data from fixed and mobile network user sides, including: IPv6 support monitoring and IPv6 traffic quality analysis. Support end-to-end data analysis at the intelligent analysis layer.

IPv6 Support and Application Access Quality Monitoring for Application Systems Through application monitoring points, monitor and analyze the IPv6 support of application systems, including: website and APP monitoring, IPv6 application access quality evaluation, and DNS resolution capability monitoring. TBD.

Use cases

User Network Quality Issue Localization

Scenario: User A experiences lag during cloud gaming at home.
Challenge: Isolating the cause requires correlating performance data across multiple segments (N1: terminal to ONT; N2: ONT to BRAS; N3: BRAS to application), but domains are independently managed. Traditional monitoring could only obtain fragmented data of single-segment IPv4/IPv6, failing to achieve end-to-end collaborative analysis.

Network schematic diagram based on home broadband network access application | | | | |<--------- N2 ---------->| | | | |<--------- N3 ---------->| ]]>

Solution: The system first detected the degradation of end-to-end IPv6 connection quality. Through its segmented traffic analysis function, it captured core metrics (such as latency and packet loss rate) of each IPv6 link segment in real time, and finally accurately pinpointed abnormal latency in the N3 IPv6 link segment. Meanwhile, the system retrieved IPv6 scheduling logs of CDN nodes in a linked manner, and found that the content source had switched from the local IDC's IPv6 node to a remote cross-province IPv6 node, confirming that the abnormality was directly related to the IPv6 traffic scheduling path.
Conclusion: Quality degradation was caused by CDN remote scheduling and N3 inter-network link congestion.

Home terminals and router Traffic Analysis

Solution: System detected below-average IPv6 traffic share in a demo community.
Investigation: Correlation with terminal data showed a high proportion of bridge-mode optical network terminals (ONTs) and older routers supporting only IPv4/NAT.
Root Cause: Legacy routers forced IPv6 traffic to fall back to IPv4.
Action: Targeted replacement of bridge-mode ONTs with router-mode ONTs and upgrading old routers.
Effectiveness: A significant increase in the proportion of IPv6 traffic.

Security Considerations TBD.

IANA Considerations TBD.