Re: DCCP & port randomization

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Jan 31, 2010, at 1:51 AM, Fernando Gont wrote:

Similar to TCP, DCCP is also connection-oriented and has a LISTEN state for server sockets. I also believe that implementations use the socket API for opening server DCCP sockets in a similar way that TCP does, so
many issues are probably similar. But there is a relevant difference:
DCCP service codes are intended to allow more flexible allocation of the
ports, or even sharing a port by multiple applications.

Is that mandated by the specs? IIRC, when I reviewed Gorry's
dccp-service-codes I-D (now RFC5595), it was still open what to do with
services codes.

Yes, I think RFC5595 says that sharing a port for multiple SCs at a server should be possible, and it also proposes an algorithm on how to pick a dynamic port based on service code.

- Pasi


[Index of Archives]     [Linux Kernel Development]     [Linux DCCP]     [IETF Annouce]     [Linux Networking]     [Git]     [Security]     [Linux Assembly]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [DDR & Rambus]

  Powered by Linux