🚀 go-pugleaf

[POSTED TO comp.dcom.modems.cable; PLEASE REPLY THERE]

In <3A7C6810.E737A367@home.com>, James Knott
<the.lights.are.on.but.no.one.is@home.com> wrote:

>Here's what it says in "Internetworking with TCP/IP vol 1,
>Douglas Commer (1991). pg 176.
>
>"Technically, the number of packets that can be
>unacknowledged at any given time is constrained by the
>window size and is limited to a small fixed number.  For
>example, in a sliding widnow protocol with a window size 8,
>the sender is permitted to transmit 8 packets before it
>receives an acknowledgement.

Yikes!  In TCP/IP, the Receive Window is always a matter of bytes
(octets in RFCspeak), not packets.  See RFC 793 "Transmission Control
Protocol" (TCP):

  Flow Control:

    TCP provides a means for the receiver to govern the amount of data
    sent by the sender.  This is achieved by returning a "window" with
    every ACK indicating a range of acceptable sequence numbers beyond
    the last segment successfully received.  The window indicates an
    allowed number of octets that the sender may transmit before
    receiving further permission.

    ...

  To govern the flow of data between TCPs, a flow control mechanism is
  employed.  The receiving TCP reports a "window" to the sending TCP.
  This window specifies the number of octets, starting with the
  acknowledgment number, that the receiving TCP is currently prepared to
  receive.

Note that the current window size in bytes/octets is reported on every
ACK.

See also RFC 1323 "TCP Extensions for High Performance"


p.s.  To de-spam an email address, use ".invalid" as the TLD (top level
domain) rather than ".com"/".net"/".org" (or any other potentially valid
TLD) in order to avoid unauthorized use of a valid domain and to
minimize unnecessary load on Internet infrastructure.  Examples:
"userid@myisp.invalid" or "no@spam.invalid"  (Reference: RFC 2606)

-- 
Best regards,
John Navas     <http://navasgrp.home.att.net/>
     CABLE MODEM/DSL GUIDE:  <http://Cable-DSL.home.att.net/>