When the NMU in the dynamic region accesses the NSU in the static region, you have more flexibility when determining the path ownership. You can either keep the ownership within the static region or within the dynamic region. If the ownership is within the static region, you cannot add any more NSUs in the dynamic region that the NMU can communicate with in subsequent child implementations. However, if the ownership is within the dynamic region, you can add more NSUs in the dynamic region that the dynamic region NMU can communicate with in subsequent child implementations.
In the following figure, Network-2a is a path from the NMU in the dynamic region to the NSU in the static region. This path is configured to be owned by the static region. Therefore, in subsequent implementations, NMU2a retains its existing configuration and does not undergo reconfiguration. The communication capabilities for Network-2a remain limited to NSU2a in any future RM variations.
The following figure also shows Network-2b, which represents a similar communication path extending from the NMU (NMU2b) in the dynamic region to the NSU (NSU2b) in the static region. Unlike Network-2a, this path is configured to be owned by the dynamic region. Therefore, in subsequent child implementations, you have the flexibility to reconfigure this path with different QoS requirements. Additionally, you have the option to expand communication capabilities of this NMU by introducing additional NSUs (NSU2b`) within the dynamic region that NMU2b can communicate with.
