[dcc2] Other comments

[Trent Lloyd]

> > The reason a UDP transport is usefull is because in most NAT situations
> > you can send a UDP packet, but you can't maintian a TCP connection, and
> > henceforth sending a file will just work if you use UDP, and then use a
> > TFTP-like mechanism.
> 
> For file transfers etc, there will be activity to keep the NAT table
> filled. UDP times out too -- it just takes longer by default, since
> there is no knowing when it is 'done'. I don't have a NAT box to test
> on at the moment, but can anyone tell me if UDP source ports get
> changed when passing outwards through a NAT setup just like TCP does?
> Or does it just bind the port that was used to send the packet if not
> in use? (I'm thinking the former, but the latter would be quite
> useful...)

It depends on the implemention, and if it does, if that source port is
in use, it would choose another, etc

-- 
Trent Lloyd <lathiat at bur.st>
Bur.st Networking Inc.