errata logo graphic

Found 3 records.

Status: Reported (1)

RFC1323, "TCP Extensions for High Performance", May 1992

Note: This RFC has been obsoleted by RFC7323

Source of RFC: tcplw (tsv)

Errata ID: 4346

Status: Reported
Type: Technical

Reported By: Niels Laukens
Date Reported: 2015-04-24

Section 2.3 says:

      Since the max window is 2**S (where S is the scaling shift count)
      times at most 2**16 - 1 (the maximum unscaled window), the maximum
      window is guaranteed to be < 2*30 if S <= 14.  Thus, the shift
      count must be limited to 14 (which allows windows of 2**30 = 1
      Gbyte).  If a Window Scale option is received with a shift.cnt
      value exceeding 14, the TCP should log the error but use 14
      instead of the specified value.

It should say:

      Since the max window is 2**S (where S is the scaling shift count)
      times at most 2**16 - 1 (the maximum unscaled window), the maximum
      window is guaranteed to be < 2**30 if S <= 14.  Thus, the shift
      count must be limited to 14 (which allows windows of 2**30 = 1
      Gbyte).  If a Window Scale option is received with a shift.cnt
      value exceeding 14, the TCP should log the error but use 14
      instead of the specified value.

Notes:

Typo in the 3rd line: the window should be less than 2 to the power of 30, instead of 2 multiplied by 30.


Status: Held for Document Update (1)

RFC1323, "TCP Extensions for High Performance", May 1992

Note: This RFC has been obsoleted by RFC7323

Source of RFC: tcplw (tsv)

Errata ID: 2278

Status: Held for Document Update
Type: Editorial

Reported By: Nikolai Malykh
Date Reported: 2010-05-19
Held for Document Update by: Wes Eddy

Section 1.1 says:

           Section 4 introduces a new TCP option, "Timestamps", and then
           defines a mechanism using this option that allows nearly
           every segment, including retransmissions, to be timed at
           negligible computational cost.  We use the mnemonic RTTM
           (Round Trip Time Measurement) for this mechanism, to
           distinguish it from other uses of the Timestamps option.


It should say:

           Section 3.2 introduces a new TCP option, "Timestamps", and then
           defines a mechanism using this option that allows nearly
           every segment, including retransmissions, to be timed at
           negligible computational cost.  We use the mnemonic RTTM
           (Round Trip Time Measurement) for this mechanism, to
           distinguish it from other uses of the Timestamps option.


Notes:

Incorrect reference to Section 4.


Status: Rejected (1)

RFC1323, "TCP Extensions for High Performance", May 1992

Note: This RFC has been obsoleted by RFC7323

Source of RFC: tcplw (tsv)

Errata ID: 3685

Status: Rejected
Type: Technical

Reported By: Arul Kumar Chellappan
Date Reported: 2013-07-16
Rejected by: Martin Stiemerling
Date Rejected: 2014-01-22

Section 2 says:

         This option is an offer, not a promise; both sides must send
         Window Scale options in their SYN segments to enable window
         scaling in either direction.  If window scaling is enabled,
         then the TCP that sent this option will right-shift its true
         receive-window values by 'shift.cnt' bits for transmission in
         SEG.WND.  The value 'shift.cnt' may be zero (offering to scale,
         while applying a scale factor of 1 to the receive window).

It should say:

         This option is an offer, not a promise; both sides must send
         Window Scale options in their SYN segments to enable window
         scaling in either direction.  If window scaling is enabled,
         then the TCP that sent this option will left-shift its true
         receive-window values by 'shift.cnt' bits for transmission in
         SEG.WND.  The value 'shift.cnt' may be zero (offering to scale,
         while applying a scale factor of 1 to the receive window).

Notes:

This need to be left shift
--VERIFIER NOTES--
The text in RFC 1323 is correct.


Report New Errata