Data Path Restriction vs Broadcast Domain Isolation

[dsdr0]

Currently, Broadcast Domain Isolation exists. This also provides SDN as an example, which does not match well. Suggest a new (or replace Broadcast Domain Isolation) D3Code for "Data Path Restriction" (or something similar), "to broaden the scope.

Broadcast Domain Isolation is a method to reduce broadcast collisions, but does not restrict data paths.

Network Traffic Filtering restricts traffic at a certain point, regardless of approved paths of the application.

Data Path Restriction may fill the gap of authorized paths that the data may travel. I think this works logically.

This would be more intuitive for ZT initiatives. This could be over IP networks or any other type of path within a resource or through a network, whether software or hardware-based. I think it may be worth a discussion.

=============
Currently...
Definition
Broadcast isolation restricts the number of computers a host can contact on their LAN.
<Suggested: Data Path Restriction restricts data to flow through only approved paths within a resource or a network>

Synonyms: Network Segmentation, Software Defined Networking (SDN), Virtual Private Network (VPN)

How it works
Software Defined Networking, or other network encapsulation technologies intercept host broadcast traffic then route it to a specified destination per a configured policy.
This can be implemented within hypervisors, networking hardware (WAPs, switches, routers), or virutal hardware.
Traffic restriction through methods including software defined networking (SDN), and ???. Isolation may using either hardware-based, software-based, or a combination of both. This includes any method to restrict the paths that data may take, whether through static or dynamic rules.

Considerations
This technique is highly dependent on network infrastructure and networking requirements.
<Suggestion: <???>