Clarify description of IPSec configuration format and encryption options

[Andrey9kin]

Signed-off-by: Andrey Devyatkin andrey.devyatkin@fivexl.io

Please ensure your pull request adheres to the following guidelines:

• For first time contributors, read Submitting a pull request
• All code is covered by unit and/or runtime tests where feasible.
• All commits contain a well written commit description including a title,
  description and a Fixes: #XXX line if the commit addresses a particular
  GitHub issue.
• All commits are signed off. See the section Developer’s Certificate of Origin
• Provide a title or release-note blurb suitable for the release notes.
• Thanks for contributing!

Clarify description of IPSec configuration format and encryption options based on this conversation https://cilium.slack.com/archives/C1MATJ5U5/p1611678079108700

Clarify description of IPSec configuration format and encryption options

[pchaigno]

Thanks for the improvements! 🚀

[maintainer-s-little-helper]

Commit 058c007f4e75b22e37d9dd0e2543f62702704b7f does not contain "Signed-off-by".

Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin

[Andrey9kin]

@pchaigno how about now? Dropped pod-to-pod/host-to-host to avoid confusion. So that section is mostly untouched. Though it might be useful to describe all the cases but i'm to new to the project to cover it as you already observed

[pchaigno]

Yep, looks better 🚀

For maintainer-s-little-helper to stop complaining, you'll need to squash your commits and add a Signed-off-by: Name <email.address> to the commit message.

[Andrey9kin]

All the changes as one commit with signed-off message

[qmonnet]

Looks good to me, thank you!
Commit formatting and SOB tag are good now.