<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffcc" text="#000000">
<br>
On 4/16/2010 11:33 AM, Chris Engel wrote:<br>
<br>
.. snip..<br>
<br>
<blockquote
cite="mid:F55FF9C4FDB76643AE0CEC06D0F5CEB3048D8EA635@Skyhawk"
type="cite">The bottom line is that people deploy NAT on thier OWN
networks because they CHOOSE to do so. Other people interact with those
networks because they CHOOSE to do so. Vendors offer NAT support in
thier products and services because they CHOOSE to be marketable to all
those customers.<br>
<br>
</blockquote>
and you, my dear friend, who choose to deploy a network without NAT and
without the cost burden placed on the vendor selling their product to
you... You end up paying for both the nat development the vendor had to
do and the ongoing support costs he has with his nat customers. It may
be that he *choose* to sell to natted customers, but it's you who ends
up paying for that nat guy's decision to both, deploy nat *and* have
the nerve to expect more than simple http to function.<br>
<br>
that's the crux of the issue. Nat costs money, NRE and support, and
everyone pays. It's billions of dollars that could have been spent in
more useful pursuits.<br>
<br>
<br>
-lee<br>
</body>
</html>