The section has the statement:

"Configuration of these parameters can be performed through the OPC UA Information Model for PubSub configuration defined in clause 9 or through vendor-specific mechanisms."

It is not clear what "parameters can be performed' means, but after replacing "performed" by managed I can guess the idea. My concern is that for this purpose we must use OPC UA Services (Client/Server session), but not OPC UA Information Model. OPC UA Information Model provides only types definition, and to be useful must be exposed as the OPC UA Address Space.

If the vendor-specific mechanism is the case, all the mapping referring to Configuration Information Model doesn't make sense, because the Address Space doesn't exist. For example, RequestedDeliveryGuarantee refereed in Section 7.3.4.5 doesn't have any impact on the Publisher/Subscriber interoperability and maybe not considered for mapping.

The specification should define the following parameters group:

• mandatory for Publisher/Subscriber interoperability
• common knowledge the Publisher and appropriate Subscribers must have to be interoperable
• mandatory for Configuration Services interoperability
• mandatory for the Security Services interoperability

and mapping should be defined in the context of these parameters (OPC UA IM).