testing: Fixed description of swanctl/frags-iv4 scenario

diff --git a/testing/tests/swanctl/frags-ipv4/description.txt b/testing/tests/swanctl/frags-ipv4/description.txt
index 51744cf7c99a71cfa32e617d01eb38937ce7dd84..b5b8711264938c9e9ea754173c3defdda4e24d63 100755 (executable)
--- a/testing/tests/swanctl/frags-ipv4/description.txt
+++ b/testing/tests/swanctl/frags-ipv4/description.txt
@@ -1,7 +1,7 @@
-The roadwarriors <b>carol</b> and <b>dave</b> set up a connection each 
-to gateway <b>moon</b> using the <b>IKEv2</b> key exchange protocol. The
-authentication is based on <b>X.509 certificates</b>. <b>dave</b> advertises 
-the support of the IKEv2 fragmentation protocol defined in <b>RFC 7383</b> 
+The roadwarriors <b>carol</b> and <b>dave</b> set up an IPv4 connection each to
+gateway <b>moon</b> using the <b>IKEv1</b> and <b>IKEv2</b> key exchange protocol,
+respectively. The authentication is based on <b>X.509 certificates</b>. <b>dave</b>
+advertises the support of the IKEv2 fragmentation protocol defined in <b>RFC 7383</b> 
 which prevents the IP fragmentation of the IKEv2 messages carrying large X.509 
 certificates whereas <b>carol</b> announces support of non-standardized
 IKEv1 fragmentation.