EthernetInterface schema in NDF for SmartNIC

/redfish/v1/Chassis/{ChassisId}/NetworkAdapters/{NetworkAdapterId}/NetworkDeviceFunctions/{NetworkDeviceFunctionId}/EthernetInterfaces/{EthernetInterfaceId} is specifically for non-system types of interfaces. One example is an EBOF where there are network controllers embedded in an enclosure that serve as an NVMe-oF to PCIe bridge; there's no ComputerSystem here since it's a box of network-connected drives, but a user needs to be able to configure the IP address of those controllers. We have this in the long description for EthernetInterfaces in NetworkDeviceFunctions:

> This property shall not be present if this network device function is not referenced by a NetworkInterface resource.

For the case you're describing, you'd need to add EthernetInterface resources subordinate to the appropriate ComputerSystem resource to go alongside the NetworkInterface resources.

I'll admit this is not the most intuitive approach. We expected NetworkInterface, NetworkDeviceFunction, and other advanced communication device resources to replace EthernetInterface in the same manner Storage can fully replace SimpleStorage. Unfortunately as new use cases came up (virtual NICs, bonding, virtual machines, etc), we realized that EthernetInterface is still needed, and we likely would have taken a different modeling approach had this been apparent to us.