| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
IPSec General Operation, Components and Protocols (Page 1 of 3) I have a confession to make: I considered not writing about IPSec in this Guide. When you find yourself writing a tome as large as this one, you lose stamina sometimes and there's this urge to avoid writing about confusing subjects. J IPSec isn't the only difficult topic in this Guide but it is definitely a subject that baffles many because it's hard to get your hands around. Most discussions of it jump straight to describing the mechanisms and protocols without providing a general description of what it does and how the pieces fit together. Well, I recognized that IPSec is important and I don't shy away from a challenge. Thus, here's my attempt to provide a framework for understanding IPSec's various bits and pieces. So, what exactly does IPSec do and how does it do it? In general terms, it provides security services at the IP layer for other TCP/IP protocols and applications to use. What this means is that IPSec provides the tools that devices on a TCP/IP network need in order to communicate securely. When two devices (either end user hosts or intermediate devices such as routers or firewalls) want to engage in secure communications, they set up a secure path between themselves that may traverse across many insecure intermediate systems. To accomplish this, they must perform (at least) the following tasks:
Home - Table Of Contents - Contact Us The TCP/IP Guide (http://www.TCPIPGuide.com) Version 3.0 - Version Date: September 20, 2005 © Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved. Not responsible for any loss resulting from the use of this site. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||