[dcc2] Other comments

[myndzi]

> If they can't maintain a TCP connection, how would they stay on IRC?
> Or do much of anything on the Internet, really.

>From past experience with NAT, it's more like "can't maintain an
*idle* TCP connection". As data goes outwards the timeout on the NAT
table is refreshed. UDP has a longer timeout generally because it does
not have any specific means of signifying and end to transmissions
(and therefore no further need of a NAT table entry).

> However, each DCC2 application protocol should pick
> either TCP or UDP; only one.

Why should such a restriction be in place? There's no need for it. If
it makes sense to only support one of the two, any application
designed to use DCC2 can simply use that one and only that one. If an
application wants to use either or both, there's no reason for us to
say nay...

-myndzi