|
|
Our vote from the side of Siemens company: the Networks Standard IEEE Std 802.1Q-2022 clearly specifies that
- VLANs are logical Layer 2 constructs
- Physical parameters like MAC, speed, Ethernet Port, etc. are not part of the VLAN definition but belong exclusively to the physical layer interfaces
- VLANs always sit upon a physical interface that provides its physical properties
- VLANs are identified by tagging in Ethernat frames, means basically just by their VIDs
Hence we claim that it is possible to design the OPC UA BNM interfaces correspondingly conformous to the IEEE networks standard, mentioned above.
Hence our interfaces will have the following TypeDefinitions: VLAN-ITF is of BaseObjecType and physical ITF is of IetfBaseNetworkInterfaceType):
see attached figure "Proposal from Claudia"
In addition to the standard-conformance this ITF modeling offers the following benefits:
- Avoidance of redundant physical parameters
- Clear layering approach /Layered architecture
- Reusability: one physical ITF can be referenced by multiple(!) VLANs which allows modularity in the model, reusage of physical ITF definitions, scalability e.g. if many VLANs are used
- Semantic clarity (a VLAN ITF is not a physical ITF but a logical abstraction on a higher layer)
- Optimal validation, model integrity and maintainability: the separation allows clean validation because a physical ITF must have certain mandatory(!) parameters – a VLAN ITF may only have specific parameters.
This following ITF design is allowed just as an Option for a device/server that own just one single ITF that acts as physical ITF and as VLAN ITF as well:
see attached figure "Current"
|
