Help to write detail plan to implement SSL offloading on environment.

These days there's very little point to this.

If you use HTTP/2, then only one SSL negotiation occurs per visit, with all assets multiplexed over a single connection.

If you're using HTTP/1.1, every single asset requires it's own SSL negotiation.

So the real fix is not offloading, rather...

1) Use HTTP/2

2) Use OSCP Stapling

3) Use Strict Transport (with 1+ year duration)

Do this and you can avoid all the complexity of managing offloading.

Tip: If you do the 3x steps above, no offloading solution can come close to speed, because anytime you offload, you must run a proxy connection between offload device + real Webserver... which will always be slower than connecting directly to a Webserver...

Just so long as the 3x items above are correctly configured.

Thank David. We have 2 F5 load balance in our prod environment. We have to implement for one web application. Now we have to test in QA environment first. But QA environment we don't have load balance. What is the best approach to test on QA environment? And what are things i need to take care? (Like new DNS etc)

Thank you for your help.

Your question is illogical.

I have a car in Mexico, how can I test drive it in Canada, makes the same amount of sense.

Hi David,
 Sorry for the confusion.

David,
  I was looking for the steps to implement. I wanted to write down all the point which i need take care while implementing SSL offloading for one SharePoint web application.