No subject

The OS won't know about your privately-managed TCP connections, so it w=
on't know that the port(s) you've chosen is/are in use. This means =
that it might try to use the same port for another application's connec=
tion, leading to chaos.</li>
<li style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin=
-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padd=
ing-left: 0px; border-top-width: 0px; border-right-width: 0px; border-botto=
m-width: 0px; border-left-width: 0px; border-style: initial; border-color: =
initial; font-size: 14px; vertical-align: baseline; background-image: initi=
al; background-attachment: initial; background-origin: initial; background-=
clip: initial; background-color: transparent; background-position: initial =
initial; background-repeat: initial initial; ">
The OS won&#39;t know about your privately-managed TCP connections, so unle=
ss you prevent it from seeing those packets, it will send RST packets to re=
set the apparently bogus connection.</li><li style=3D"margin-top: 0px; marg=
in-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padd=
ing-right: 0px; padding-bottom: 0px; padding-left: 0px; border-top-width: 0=
px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0=
px; border-style: initial; border-color: initial; font-size: 14px; vertical=
-align: baseline; background-image: initial; background-attachment: initial=
; background-origin: initial; background-clip: initial; background-color: t=
ransparent; background-position: initial initial; background-repeat: initia=
l initial; ">
Your application won&#39;t automatically be notified of changes to relevant=
 OS-managed data, configured IP addresses and routing tables. You&#39;ll li=
kely have to poll for updates.</li><li style=3D"margin-top: 0px; margin-rig=
ht: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-ri=
ght: 0px; padding-bottom: 0px; padding-left: 0px; border-top-width: 0px; bo=
rder-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; bo=
rder-style: initial; border-color: initial; font-size: 14px; vertical-align=
: baseline; background-image: initial; background-attachment: initial; back=
ground-origin: initial; background-clip: initial; background-color: transpa=
rent; background-position: initial initial; background-repeat: initial init=
ial; ">
Properly implementing the TCP protocol is non-trivial. Most implementations=
, even very well-used ones, had dormant bugs that weren&#39;t found for=A0<=
em style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-=
left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; paddi=
ng-left: 0px; border-top-width: 0px; border-right-width: 0px; border-bottom=
-width: 0px; border-left-width: 0px; border-style: initial; border-color: i=
nitial; font-size: 14px; vertical-align: baseline; background-image: initia=
l; background-attachment: initial; background-origin: initial; background-c=
lip: initial; background-color: transparent; font-style: italic; background=
-position: initial initial; background-repeat: initial initial; ">years</em=
>. Not all the necessary information is in the RFCs, either; there are plac=
es where established practice differs from the documented behaviour, usuall=
y for good reason. There&#39;s also plenty of code in modern TCP stacks spe=
cifically to deal with historical buggy behaviour in other stacks, and repl=
icating all that work isn&#39;t simple.</li>
<li style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin=
-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padd=
ing-left: 0px; border-top-width: 0px; border-right-width: 0px; border-botto=
m-width: 0px; border-left-width: 0px; border-style: initial; border-color: =
initial; font-size: 14px; vertical-align: baseline; background-image: initi=
al; background-attachment: initial; background-origin: initial; background-=
clip: initial; background-color: transparent; background-position: initial =
initial; background-repeat: initial initial; ">
There&#39;s a substantial risk of bad interactions with third party network=
 security software installed on the host, which will expect all TCP connect=
ions to be made via the OS.</li></ul>It seems like a support nightmare to m=
e.<p>
</p></span>

--0015174c12e6be489b048ae0b8ba--