As broadband networks evolve and the number of connected devices continues to grow, IPv6 adoption has become essential for ISPs seeking scalability, performance, and long-term readiness. The netElastic Virtual BNG (vBNG) is designed to help service providers efficiently manage and deliver both IPv4 and IPv6 services at scale, while benefiting from the flexibility and cost efficiency of a software-based, disaggregated platform.
While enabling IPv6 is an important first step, deploying it effectively requires understanding of best practices for IPv6 address assignment—including both global IPv6 address allocation and IPv6 prefix delegation (PD). ISPs must assign IPv6 resources to subscribers in a manner that is consistent, efficient, most adaptive to existing CPE inventories, and aligned with global standards.
netElastic vBNG supports dual stack IPv4 and IPv6. Its IPv6 stack supports a wide range of IPv6 address and prefix assignment options, allowing operators to accommodate diverse CPE capabilities and deployment scenarios.
Why IPv6 Address Assignment Matters
IPv6 introduces a virtually unlimited address space, but the challenge lies in structuring assignments in a consistent and scalable manner. Effective IPv6 address and prefix assignment ensures:
- Subscriber service consistency: Each subscriber is assigned an appropriately sized IPv6 prefix—commonly a /56 or /48—in accordance with industry best practices, enabling compatibility with a wide range of end devices and supporting internal subscriber networks. A robust BNG should accommodate diverse CPE behaviors to ensure consistent service delivery across devices.
- Simplified network operations: Predictable, consistent, and well-planned assignments improve routing stability, behavioral consistency, monitoring, and troubleshooting.
- Scalability and automation: Dynamic assignment mechanisms such as DHCPv6 global address assignment and prefix Delegation (PD) or SLAAC, enable networks to scale efficiently without manual intervention.
The netElastic vBNG supports stateful address assignment via DHCPv6 IANA and prefix delegation via DHCPv6 IAPD, along with stateless address configuration using SLAAC. It also supports either assigning a global address to CPEs or using only link-local addresses for CPE connectivity, providing operators with the flexibility to accommodate the full spectrum of CPE behaviors encountered in the field.
Field Proven IPv6 Dual-stack Best Practices
The following are field proven guidelines recommendations for IPv6 dual stack deployment, address assignment and prefix delegation:
- Dual-stack
- /64 Prefix Delegation is generally recommended for residential subscribers. This provides the most flexibility for home-connected devices.
- /56 Prefix for CPEs that support SLAAC address allocation is generally recommended for residential subscribers, providing up to 256 internal subnets.
- /48 Prefix for CPEs that support SLAAC address allocation is generally recommended for business customers or advanced users with complex internal topologies.
- Static vs. dynamic allocation should be selected based on service type—static assignments for business services and dynamic assignments for residential or mobile access.
- Stable prefixes are encouraged to improve user experience and simplify security and firewall configurations.
How netElastic vBNG Helps ISPs Roll Out IPv6
netElastic Virtual BNG enables ISPs to deploy IPv6 through:
- Dual stack support that allows ISP to roll out IPv6 at their own pace without breaking IPv4 end-to-end connectivity.
- Flexible IPv6 address assignment options, including DHCPv6-IANA, DHCPv6-IAPD, SLAAC, and mixed-mode deployments that allow for maximum compatibility with various CPE devices in the field.
- Full IPv6 flow visibility through IPfix flow export and RADIUS accounting.
- High-performance IPv6 forwarding : A structure processing pipeline design ensures that IPv6 forwarding can be implemented without any performance loss compared with IPv4 forwarding.
- Centralized management and automation through netVision,delivering operational visibility for both IPv4 and IPv6 traffic.