| Internet-Draft | IPv6 Network Monitoring Deployment | March 2026 |
| Pang, et al. | Expires 3 September 2026 | [Page] |
This document addresses key operational challenges in large-scale IPv6 deployment and proposes an architecture for IPv6 deployment monitoring and analysis. It describes an architectural approach and comprehensive metrics to provide end-to-end visibility across network infrastructure, cloud services, edge computing, and end-user domains.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 3 September 2026.¶
Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
The IPv6 protocol specification was published in 1998. As IPv6 adoption has accelerated in recent years, IPv6 was standardized as an Internet Standard [RFC8200] in 2017.¶
The deployment of IPv6 has become a core driving force for network development. With the continuous expansion of network scale and the emergence of new services, IPv6 provides abundant address space, enhanced security, and improved network performance, making it a key component in network evolution. The efficient deployment and promotion of IPv6 networks have become critical priorities for operators and service providers.¶
As of 2023, significant progress has been made in global IPv6 deployment. According to the Global IPv6 Development Report 2024 [GlobalIPv6Report2024], IPv6 deployment accelerated notably in 2023, with global coverage exceeding 30% for the first time. In leading countries, IPv6 coverage has reached or approached 70%, and the proportion of IPv6 mobile traffic has surpassed that of IPv4.¶
[RFC9386] describes the IPv6 deployment status in 2022, and Section 5 lists common challenges including transition mechanisms, network management and operation, performance, and customer experience. ETSI-GR-IPE-001 [ETSI-GR-IPE-001] also analyzes existing gaps in IPv6-related use cases.¶
Several tools and platforms are used to monitor IPv6 deployment, such as:¶
Internet Society Pulse: Curates information about IPv6 adoption levels in countries and networks worldwide.¶
Akamai IPv6 Adoption Visualization: Tracks IPv6 adoption trends at country or network level.¶
APNIC IPv6 Measurement: Provides an interactive map for viewing IPv6 deployment rates in specific countries.¶
Cloudflare IPv6 Adoption Trends: Offers IPv6 adoption insights across the Internet.¶
Cisco 6lab IPv6: Displays IPv6 prefix data.¶
Regional or National Monitoring Platforms: Examples include NZ IPv6, RIPE NCC IPv6 Statistics, and USG IPv6 & DNSSEC External Service Deployment Status.¶
While valuable for high-level trend analysis, these tools have significant limitations for carrier-grade operational use.¶
Inadequate IPv6 monitoring can lead to unrecognized service degradation, increased operational costs, and poor end-user experience, which hinders the large-scale adoption of IPv6.¶
Monitoring points are predominantly concentrated in backbone networks [RFC7707], lacking fine-grained visibility into user terminals, access networks, and application endpoints.¶
Assessments mainly rely on basic metrics such as connection availability [RFC9099] and address allocation rates, lacking a holistic view of service continuity, transmission quality, network element readiness, and active connection states.¶
Data silos exist among different network domains (fixed, mobile, core, application), preventing end-to-end path analysis and fault correlation [RFC9312].¶
Incomplete IPv6 transformation in applications and content delivery chains (e.g., deeply nested links, multimedia content) is difficult to characterize without in-depth monitoring capabilities for such scenarios.¶
Current models cannot effectively quantify the impact of external factors (policy changes, user behavior, market dynamics) on IPv6 evolution, which limits proactive network planning.¶
To address the above challenges, this document describes an end-to-end IPv6 monitoring and analysis architecture. The architecture provides full visibility into IPv6 deployment while ensuring interoperability and scalability.¶
The monitoring framework follows these key principles:¶
Standardized Data Models: Use standardized data models (e.g., YANG) for consistent data representation across domains to ensure interoperability.¶
Modular Design: Deploy independent functional components with well-defined interfaces to support incremental deployment.¶
Cross-Domain Correlation: Enable end-to-end visibility via integrated data analysis across administrative domains.¶
Service-Oriented Metrics: Use a comprehensive monitoring metrics framework aligned with operational objectives.¶
Visualization Tools: Dashboards and visual interfaces to support key operational decisions.¶
Extensibility: Support integration with existing monitoring systems and allow future extensions.¶
The architecture consists of three layers, as shown in Figure 1: the Data Collection Layer, the Intelligent Analysis Layer, and the Visualization Layer.¶
+---------------------------------------+
| Visualization Layer |
| (Dashboards, Topology, Fault Alerts) |
+---------------------------------------+
^ ^
| API/REST |
+------------------------------------------+
| Intelligent Analysis Layer |
| +-----------+ +-----------+ +---------+ |
| | Traffic | | Dynamic | | Quality | |
| |Correlation| |Attribution| | Analysis| |
| +-----------+ +-----------+ +---------+ |
+------------------------------------------+
^ ^
| |
+-----------------------------------------------------------+
| Data Collection Layer |
| +-----------+ +-----------+ +-----------+ +---------+ |
| | Home | | | | | | | |
| | Broadband | | Mobile | | Bearer | | App | |
| | Network | | Network | | Network | | Domain | |
| +-----------+ +-----------+ +-----------+ +---------+ |
+-----------------------------------------------------------+
This layer defines unified interface standards to integrate multi-source data from the home broadband network, mobile network, IP bearer network, and application domain. The framework supports interworking with multi-vendor devices and subsystems.¶
Implementations SHOULD leverage existing IETF standards for data collection where applicable.¶
Integration with existing network management systems can provide daily-level monitoring data through standardized interfaces.¶
The architecture leverages mature, standardized collection mechanisms (such as Telemetry, NETCONF/YANG etc.) to ensure uniform data formats and meet high-frequency traffic monitoring requirements.¶
The Intelligent Analysis Layer processes traffic data collected from the four major service domains. Using multi-dimensional traffic analysis models and comprehensive metrics, it provides fine-grained insights and supports cross-domain root cause diagnosis. This layer also supports AI-based model extensions, including anomaly detection for unexpected drops in IPv6 traffic and predictive analytics for forecasting IPv6 traffic growth based on historical data and external factors (e.g., regional policy rollouts).¶
Network Traffic Analysis: Supports collection of IPv6/IPv4 inbound and outbound traffic at key network nodes. Analyzes traffic evolution trends.¶
User-Side Traffic Analysis: Monitors user-side devices and access networks (fixed and mobile), including IPv6 capability monitoring of home ONTs, routers, end-user devices, and access networks.¶
Application Traffic Analysis: Supports collection and analysis of IPv6/IPv4 active applications, and calculates IPv6 traffic for different services.¶
Inter-network Traffic Analysis: Builds region-application matrices to analyze cross-operator paths and locate regional bottlenecks.¶
Based on traffic analysis results from each domain, this component identifies regions with anomalous IPv6 traffic. Using multi-domain correlation analysis (e.g., by region, network layer, or application type), it attributes traffic fluctuations to specific subsystems.¶
Optionally, monitoring insights can inform network policy adjustments that influence client-side path selection behaviors, such as those defined in Happy Eyeballs [RFC8305].¶
User-level Topology Reconstruction: Models service chains and reconstructs end-to-end topologies, supporting segmented diagnosis of latency and packet loss (home terminal, access network, application segments).¶
Deterioration Localization: Compares IPv4/IPv6 performance segment by segment to locate underperforming network elements.¶
IPv6 Application Access Quality Assessment: Evaluates KPIs of application systems in IPv6 environments, including response time, connection success rate, and data transmission rate.¶
The Visualization Layer presents analyzed data via operational dashboards to support network management decisions.¶
Key functions include:¶
Unified Operational Dashboard: Presents an overview of key IPv6 deployment metrics and ecosystem trends using real-time widgets, charts, and graphs.¶
Cross-Domain Topology Views: Displays interactive topology maps for each network domain, showing the status of IPv6-enabled resources, connections, and operational state.¶
Multi-Dimensional Data Exploration: Provides chart-based views (traffic distribution, quality trends, application support comparison etc.) that allow operators to filter metrics by time, region, service type, and other dimensions.¶
Fault and Status Visualization: Converts root cause analysis results into visual alerts on dashboards and topologies (color-coded nodes, heat maps etc.) to speed up fault identification and troubleshooting.¶
The comprehensive IPv6 monitoring metrics framework includes the following categories:¶
Readiness Metrics¶
Network Element Readiness: IPv6 readiness of network equipment, end-user devices, and security devices.¶
Application Readiness: IPv6 support rates for websites and service systems.¶
Infrastructure Readiness: IPv6 readiness of fixed Internet, mobile Internet, dedicated lines, and data center network (DCN) infrastructure.¶
Network Readiness:¶
Cloud Readiness: IPv6 readiness of CDNs, cloud services, cloud platforms, and DNS servers.¶
Operational Metrics¶
Performance and Quality Metrics¶
This architecture and its associated metrics have been deployed in operational networks, delivering measurable improvements in IPv6 deployment effectiveness. Based on experiences from large-scale operator networks, the following key recommendations are provided:¶
Phase 1: Prioritize monitoring of key nodes in core and metro networks to quickly obtain basic IPv6 traffic visibility.¶
Phase 2: Extend to user-side terminal collection and application-side active probing to establish end-to-end monitoring capabilities.¶
Phase 3: Enhance intelligent analysis models to support automated root cause localization and predictive analytics.¶
The architecture and metrics described in this document have been deployed on the operational networks of major operators (e.g., China Unicom), covering fixed broadband, mobile, IP bearer, and application domains.¶
Implementations MUST provide:¶
Role-based access control.¶
Anonymization of user-related data.¶
Secure data transmission protocols.¶
Integrity verification for collected metrics.¶
The monitoring mechanism described in this document uses passive monitoring only. It does NOT modify, insert, or delete any IPv6 or IPv4 packet headers, payloads, or user traffic. No changes are made to packet content or format during collection and analysis, ensuring user traffic integrity and no impact on network services. No personally identifiable information (PII) is collected, processed, or reported, thus eliminating end-user privacy risks.¶
This document has no IANA actions.¶