AID: How to handle (reverse) proxy OPC-UA servers?

[wilterdinkrobert]

Some machine vendors supply a (reverse) proxy server for their machines. There can be several reasons to add a (reverse) proxy server, e.g. scaling a resource constraint machine to several clients, increasing security for IT/OT integration, etc. Usually the proxy aggregates data from multiple machines / OPC-UA servers and makes the data available via a new structure / nodeset (e.g. all machine OPC-UA trees (subset?) can be found under Objects -> Machines -> <MACHINE_X>). This resulting nodeset is dynamic and can change when machines are added/removed. Currently I need to manually check and (re)configure the OPC-UA clients after every change (e.g. software update of machine). Additionally, one particular machine vendor I encounter often makes mistakes and explaining the discrepancies between their manual/PDF and the real machine takes a lot of time and effort. I can see a lot of potential in the AID for automating some of these tasks and preventing mistakes in the first place.

How to handle (reverse) proxy OPC-UA servers with/via the Asset Interface Description Submodel? Or perhaps another model?

[sebastiankb]

the WoT TD comes with a proxy term in the security definition:
https://w3c.github.io/wot-thing-description/#table-vocabulary-terms-in-securityscheme-level

We should consider it to support this in the AID 1.1 as well.