OCPBUGS#10296: Change the IPsec related text

Author: xenolinux

modules/nw-ovn-ipsec-encryption.adoc

@@ -4,8 +4,8 @@
 
 :_content-type: CONCEPT
 [id="nw-ovn-ipsec-encryption_{context}"]
-= Encryption protocol and tunnel mode for IPsec
+= Encryption protocol and IPsec mode
 
 The encrypt cipher used is `AES-GCM-16-256`. The integrity check value (ICV) is `16` bytes. The key length is `256` bits.
 
-The IPsec tunnel mode used is _Transport mode_, a mode that encrypts end-to-end communication.
+The IPsec mode used is _Transport mode_, a mode that encrypts end-to-end communication by adding an Encapsulated Security Payload (ESP) header to the IP header of the original packet and encrypts the packet data. {product-title} does not currently use or support IPsec _Tunnel mode_ for pod-to-pod communication.

networking/ovn_kubernetes_network_provider/configuring-ipsec-ovn.adoc

@@ -6,7 +6,7 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-With IPsec enabled, all network traffic between nodes on the OVN-Kubernetes cluster network travels through an encrypted tunnel.
+With IPsec enabled, all pod-to-pod network traffic between nodes on the OVN-Kubernetes cluster network is encrypted with IPsec _Transport mode_.
 
 IPsec is disabled by default. It can be enabled either during or after installing the cluster. For information about cluster installation, see xref:../../installing/index.adoc#ocp-installation-overview[{product-title} installation overview]. If you need to enable IPsec after cluster installation, you must first resize your cluster MTU to account for the overhead of the IPsec ESP IP header.