@@ Page 6 @@
     we rely partially on existing TCP documentation, such as RFC 793,
     RFC 2581, RFC 3465, and RFC 3517.  TCP congestion control continues
     to evolve, but CCID 2 implementations SHOULD wait for explicit
-    updates to CCID 2 rather than track TCP's evolution directly.  The
-    differences between CCID 2 and straight TCP include: CCID 2 applies
-    congestion control to acknowledgements, a mechanism not currently
-    standardized for use in TCP.  DCCP is a datagram protocol, so
-    several parameters whose units are specified in bytes in TCP, such
-    as the congestion window cwnd, have units of packets in DCCP.
-    Unreliability also leads to differences from TCP: DCCP never
-    retransmits a packet, so congestion control mechanisms that
-    distinguish retransmissions from new packets have been redesigned
-    for the DCCP context.
+    updates to CCID 2 rather than track TCP's evolution directly.
+    Differences between CCID 2 and straight TCP congestion control
+    include the following:
+
+    o  CCID 2 applies congestion control to acknowledgements, a
+       mechanism not currently standardized for use in TCP.
+
+    o  DCCP is a datagram protocol, so several parameters whose units
+       are specified in bytes in TCP, such as the congestion window
+       cwnd, have units of packets in DCCP.
+
+    o  As an unreliable protocol, DCCP never retransmits a packet, so
+       congestion control mechanisms that distinguish retransmissions
+       from new packets have been redesigned for the DCCP context.
 
 
 
@@ Page 14 @@
 
 
     sender SHOULD NOT attempt to renegotiate the Ack Ratio more than
-    once per round-trip time.  Additionally, it MAY bound Ack Ratio
-    below by two, or it MAY set Ack Ratio to one for half-connections
-    with persistent congestion windows of 1 or 2 packets.
+    once per round-trip time.  Additionally, it MAY enforce a minimum
+    Ack Ratio of two, or it MAY set Ack Ratio to one for half-
+    connections with persistent congestion windows of 1 or 2 packets.
 
     Putting it all together, the receiver always sends at least one
     acknowledgement per window of data when cwnd = 1, and at least two