🚀 go-pugleaf

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

In <3A7C77CB.48463601@ufl.edu>, "Randy S." <rswitt@ufl.edu> wrote:

>> Yes, this is a correct statement...you are just mis-interpreting it.
>>
>> Window size controls how much *DATA* a SENDER is allowed to send (before
>> requiring RECEIPT of an ACK).
>> Receive window size has no direct bearing on when the RECEIVER actually
>> SENDS the ACKs...this a different part of the RFC.
>>
>> (which for the life of me I can't find...and you made me look).
>
>I figured I was missing something.  Obviously the relevent portion about the actual sending of ACKs
>has not yet made it into my reading list yet.  If you find it, let me know ;-)

RFC 793 "Transmission Control Protocol"
<ftp://ftp.isi.edu/in-notes/rfc793.txt>
RFC 1122 "TRANSPORT LAYER -- TCP"
<ftp://ftp.isi.edu/in-notes/rfc1122.txt>

         4.2.3.2  When to Send an ACK Segment

            A host that is receiving a stream of TCP data segments can
            increase efficiency in both the Internet and the hosts by
            sending fewer than one ACK (acknowledgment) segment per data
            segment received; this is known as a "delayed ACK" [TCP:5].

            A TCP SHOULD implement a delayed ACK, but an ACK should not
            be excessively delayed; in particular, the delay MUST be
            less than 0.5 seconds, and in a stream of full-sized
            segments there SHOULD be an ACK for at least every second
            segment.

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