Clarification regarding the receive window (reported by Michael Scharf):

Section 4.3 of RFC 4782, second paragraph says:

   "The QS Nonce in the
   Response is set to the received value of the QS Nonce in the Quick-
   Start Option."

It should say:

   "The QS Nonce in the
   Response is set to the received value of the QS Nonce in the Quick-
   Start Option.

   "If the TCP host has sufficient receive buffer space, it could
   estimate the required buffer space as the product of the approved
   Quick-Start rate and the round-trip time, and advertise a receive
   window based on this required buffer space.  This receive window
   should allow the other TCP host to fully use the approved Quick-Start
   Request.

   If the TCP host doesn't know the round-trip time, the TCP host
   could use an estimate of the round-trip time in calculating the
   required buffer space.  Alternately, the TCP host could base the
   advertised receive window on the available buffer space, without
   calculating the buffer space required for the other TCP host to
   fully use the approved Quick-Start Request.

   If the Quick-Start Response is sent in a SYN/ACK packet, then
   window scaling of the receive window is not allowed [RFC1323];
   if necessary, the TCP host could send a scaled receive window
   in a separate ACK packet following the SYN/ACK packet."


Clarification regarding the receive window (reported by Michael Scharf):

Section 4.4 of RFC 4782, fourth paragraph, says:

   "The TCP host SHOULD set its congestion window cwnd to QS-cwnd only if
   QS-cwnd is greater than cwnd; otherwise, QS-cwnd is ignored."

It should say:

   "The TCP host SHOULD set its congestion window cwnd to QS-cwnd
   only if QS-cwnd is greater than cwnd; otherwise, QS-cwnd is
   ignored.  In either case, the sender can transmit up to the
   minimum of the cwnd and the receiver's advertised window rwnd,
   as specified in [RFC2581]."