Update Changelog, Release Notes, and File Headers for release 1.5

[dccp2tcp] / README

diff --git a/README b/README
index 4364d412ac05d37971adac9904554ac7edcd6982..4ef844a480557fd1542e87cbda4b8157288689b8 100644 (file)
--- a/README
+++ b/README
@@ -22,7 +22,7 @@ dccp2tcp dccp_file tcp_file [-d] [-y] [-g] [-s]
        -g shifts the ack line in tcptrace (green) to the highest received acknowledgment. Normally this line is the standard TCP ack number, which, for DCCP, translates to the highest contiguous acknowledgement in the ack vector.
        -s converts the DCCP ack vector to TCP SACKS. Specify -s twice to only see those Ack vectors with a loss interval in them. This is convenient way to see loss events.
 
-For typical usage, you probably just want -s.
+For typical usage, you probably want -s -s.
 
 Once you run dccp2tcp, you will then want to run tcptrace on the tcp_file to generate graphs. The command should be something like this:
 tcptrace -lGt tcp_file
@@ -32,14 +32,11 @@ xplot a2b_tsg.xpl a2b_rtt.xpl
 
 
 This program does have several important limitations:
-       1)Supports only a single DCCP connection per capture.
-       2)Source Port can't equal Destination Port. If the two are equal, this program will get very confused.
-       3)DCCP MUST use 48 bit sequence numbers.
-       4)Checksums are not computed (they are zeroed).
-       5)Only converts those packet types used by the Linux implementation at this date
-       6)DCCP Ack packets show up as TCP packets containing one byte
-       7)Very little error checking of DCCP
-
+       1)CCID2 ONLY
+       2)DCCP MUST use 48 bit sequence numbers.
+       3)Checksums are not computed (they are zeroed).
+       4)DCCP DATA packets are not implemented (Linux doesn't use them)
+       5)DCCP Ack packets show up as TCP packets containing one byte
 
 
 dccp2tcp is free software: you can redistribute it and/or modify