So, it’s been a while since I’ve had the chance to post to my blog.
One of the reasons is I’ve been heads down working on some new content for our IPsec and Server and Domain Isolation offerings. One thing that keeps catching my attention, is that IPsec can be found spelled a number of different ways.
The most common variants are IPsec (which is the official IETF way), IPSec (the older IETF way) and IPSEC (how folks truly passionate about IPsec spell it at the top of their lungs).
All kidding aside, it’s interesting to see how this Internet standard doesn’t appear to be expressed in any standard fashion. Maybe it’s just the marketing guy in me.
I learned recently while working on some new web content and materials that the official spelling was changed some time in 2001. Our Windows releases at the time were already out the door with the old spelling (i.e. IPSec) so we’ve been spending this whole set of releases (Windows Vista and Windows Server “Longhorn”) getting the spelling just right.
Not only are we “releasing” a new spelling “feature”, we’ve done a whole bunch to make deploying IPsec that much easier. This includes new configuration tools to make policies simpler to create and maintain and, of course, the new Windows Firewall with Advanced Security.
Network Access Protection (NAP) is another area that IPsec is getting a facelift for. IPsec will be a key enforcement mechanism for NAP and the integration is virtually seamless.
So, when you look at reports from folks like TheInfoPro (this is a link to their press release), “end-point authentication” is a hot topic amongst enterprises. According to TIP, end-point authentication is set to grow 13% since their last survey. It’s not surprising as we’ve witnessed the blurring of the perimeter between “trusted” intranet and the “untrusted” Internet.
I may be biased, but it’s certainly worth taking a look at what this new world of IPsec can offer you today and what’s coming in the next releases of Windows to make it better…with the correct spelling to boot!