Security functions

You can use Application Transparent Transport Layer Security (AT-TLS) with SMC-R with no restriction. The negotiation of AT-TLS support for a TCP connection takes place after the SMC-R rendezvous exchange, and after that the encryption and decryption of the data occur as normal.

Generally, security functions that require TCP/IP to examine TCP packets cannot be used with SMC-R communications because data that is sent over SMC-R links is not converted into TCP packets. The following security functions do not interoperate with SMC-R:

• IPSec when the TCP connection requires tunneling
• IP filters when the filter would deny a packet for the TCP connection
• Multilevel security when the connection requires packet tagging (that is, when the source and destination zones are both SYSMULTI)

All of the above functions can be activated dynamically through profile changes, with the expectation that the change applies to current active TCP connections. If TCP connections are currently traversing SMC-R links when such a profile change is made, then the stack stops the TCP connections that are not compatible with the new security profiles.