Plugfest 2018: Concurrent EO/IO connections are rejected when connection parameters mismatch (in case of multicast T->O transports)

If an exclusive owner connection is open with the adapter which uses a T->O multicast transport with, e.g., a certain RPI, and a second connection (of type input only) is opened and that second connection also requests a multicast T->O transport, but specifies a different RPI value, then the later connection attempt is rejected. It seems as the device tries to reuse the first transport and rejects the connection due to a mismatch in the connection parameters. Instead, it is expected that a second, independent transport is created and exclusively used by the input only connection.