Called by RemCon to get the TSP to address an incoming command (from a remote to zero or more target clients). The implementor should add or remove zero or more items from aClients and then call IncomingCommandAddressed on the observer with a suitable error.

Called by RemCon to get the TSP to address an outgoing command (from a connectionless controller client) to zero or more remotes. The implementor should add zero or more items to aConnections and then call OutgoingCommandAddressed on the observer with an appropriate error. Note that only one of AddressOutgoingCommand and PermitOutgoingCommand is outstanding at once. The implementor is responsible for the capability check. For this reason, aSender contains the client's current send message, and aBearerSecurity contains all the bearer security policies. To reiterate, RemCon does no security check on the client's send request either before calling AddressOutgoingCommand.

Called by RemCon to cancel the current AddressOutgoingCommand or PermitOutgoingCommand command. On receipt, the TSP must stop dereferencing any data given in the AddressOutgoingCommand or PermitOutgoingCommand request. The TSP should not subsequently call OutgoingCommandAddressed or OutgoingCommandPermitted, except in response to a subsequent new AddressOutgoingCommand or PermitOutgoingCommand command. If an AddressOutgoingCommand request is currently being processed, the TSP is responsible for deleting any TRemConAddresses it has already created.

Called by RemCon to find out from the TSP whether the given connection-oriented controller client is permitted to send the given command to the given remote at this time. The implementor should call PermitOutgoingCommand with either ETrue, if the send is permitted, or EFalse, if the send is not permitted. Note that only one of AddressOutgoingCommand and PermitOutgoingCommand is outstanding at once. Note that a capability check will have been done by RemCon before PermitOutgoingCommand is called- actually at GoConnectionOriented time.