Merging IPv4 and IPv6 Multicast Trees via mLDP Root Identification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In networks transitioning from IPv4 to IPv6, dual stack border nodes may create separate multicast trees rooted at the same node using IPv4 and IPv6 addresses, leading to tree redundancies and increased bandwidth consumption as intermediary nodes treat these trees separately, resulting in inefficient resource utilization.
Innovation Solution
Implementing a multicast label distribution protocol (mLDP) that allows dual stack devices to receive and analyze label mapping messages containing both IPv4 and IPv6 addresses of a root node, enabling the merging of corresponding multicast trees by adding devices to the same tree based on matching opaque values, thus eliminating redundant tree records in routing tables.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If dual stack border nodes create separate multicast trees for IPv4 and IPv6 addresses of the same root node, then protocol compatibility and backward compatibility are maintained, but tree redundancies occur and bandwidth consumption increases
Solution Approach 1:
The patent merges overlapping IPv4 and IPv6 multicast trees by having intermediary nodes identify and combine trees that share the same root node, using a common representation that allows both IPv4 and IPv6 addresses to reference the same tree structure, thereby eliminating redundant packet transmissions while maintaining dual-stack compatibility
Solution Approach 2:
The patent creates a universal tree representation that can serve both IPv4 and IPv6 multicast traffic. By allowing a single tree structure to handle multiple address families through a common root node identification mechanism, the system achieves multi-functionality without requiring separate dedicated trees for each protocol
2Reliability
If dual stack border nodes create separate multicast trees for IPv4 and IPv6, then protocol-specific routing is maintained, but device complexity and routing table size increase
Solution Approach 1:
The patent reduces routing table complexity by merging duplicate tree entries for IPv4 and IPv6 into a single unified entry. Intermediary nodes store one tree representation per root node regardless of address family, significantly reducing the number of routing table entries needed while preserving protocol-specific routing capabilities through address family identification fields
3Reliability
If intermediary nodes treat overlapping IPv4 and IPv6 trees separately, then protocol isolation is maintained, but resource utilization efficiency decreases
Solution Approach 1:
The patent enables intermediary nodes to merge the handling of overlapping IPv4 and IPv6 trees into a single processing path. By identifying trees with the same root node and combining their forwarding operations, the system maintains protocol isolation where needed while achieving efficient resource utilization through shared tree structures and consolidated packet forwarding
Data Source
AI summary
In one embodiment, a first device in a multicast label distribution (mLDP) network receives a first label mapping message that includes IPv4 and IPv6 addresses of a root node of a multicast tree. The first device also receives a second label mapping message from a second device that identifies the multicast tree and includes one of: the IPv4 address or the IPv6 address of the root node. The first device determines that the second label mapping message is associated with the multicast tree. In response to determining that the second label mapping message is associated with the multicast tree, the first device adds the second device to the multicast tree.