Hello All, In doing some DCCP testing, I have identified a bug in the CCID 2 implementation. Right now, CCID 2 will willingly increase it's congestion window (the number of packets it tries to keep in the network) greater than the sequence window. This, of course, causes acknowledgments from the receiver to be deemed sequence invalid which causes a Sync/SyncAck exchange. In at least one test, this has resulted in a loss of 1/3rd of the bandwidth because of repeated Sync/SyncAck exchanges. I am working on a patch; however, I am interested to know if anyone else has seen similar problems and/or is working on a solution... For reference, I discovered this in testing the effectiveness of CCID 2 by running Iperf tests from a machine connected by a 100Mbit link to a machine with only a 10Mbit link. I believe the long RTT is caused by packet queuing in the Linux box that bridges the 100Mbit link to the 10Mbit link and does the packet capture. Samuel Jero Internetworking Research Group Ohio University
Attachment:
signature.asc
Description: This is a digitally signed message part
