Called by RemCon to get the TSP to address an outgoing notify command (from a connectionless controller client) to zero or one remote. The implementor need to get the connection list from which to chose the only one target device and then call OutgoingNotifyCommandAddressed on the observer with an appropriate error. Note that only one of AddressOutgoingNotifyCommand and PermitOutgoingNotifyCommand 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 AddressOutgoingNotify.

Called by RemCon to cancel the current AddressOutgoingNotify or PermitOutgoingNotifyCommand command. On receipt, the TSP must stop dereferencing any data given in the AddressOutgoingNotify or PermitOutgoingNotifyCommand request. The TSP should not subsequently call OutgoingNotifyCommandAddressed or OutgoingNotifyCommandPermitted, except in response to a subsequent new AddressOutgoingNotify or PermitOutgoingNotifyCommand command. If an AddressOutgoingNotify 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 notify command to the given remote at this time. The implementor should call PermitOutgoingNotifyCommand with either ETrue, if the send is permitted, or EFalse, if the send is not permitted. Note that only one of AddressOutgoingNotify and PermitOutgoingNotifyCommand is outstanding at once. Note that a capability check will have been done by RemCon before PermitOutgoingNotifyCommand is called- actually at GoConnectionOriented time.