Hello, Pasi, Thanks so much for your response. Comments in-line... > 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. > This might > affect how one would like to phrase the issues below, in a case when two > connections use different service codes. On the other hand, even then it > might be safer to require that only unused DCCP ports are used as > ephemeral ports, also in the interests of being consistent with TCP. FWIW, the same applies to SCTP. -- Fernando Gont e-mail: fernando@xxxxxxxxxxx || fgont@xxxxxxx PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
