Re: [Tsvwg] draft-ietf-tsvwg-rfc2960-bis-00.txt: SACK & rcv consumption

Vern Paxson <vern@ee.lbl.gov> Fri, 20 July 2001 19:47 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA19754 for <tsvwg-archive@odin.ietf.org>; Fri, 20 Jul 2001 15:47:51 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA14899; Fri, 20 Jul 2001 15:36:11 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA14870 for <tsvwg@ns.ietf.org>; Fri, 20 Jul 2001 15:36:09 -0400 (EDT)
Received: from daffy.ee.lbl.gov (daffy.ee.lbl.gov [131.243.1.31]) by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA14768 for <tsvwg@ietf.org>; Fri, 20 Jul 2001 15:35:12 -0400 (EDT)
Received: (from vern@localhost) by daffy.ee.lbl.gov (8.10.0/8.10.0) id f6KJZYa21084; Fri, 20 Jul 2001 12:35:35 -0700 (PDT)
Message-Id: <200107201935.f6KJZYa21084@daffy.ee.lbl.gov>
To: Randall Stewart <randall@stewart.chicago.il.us>
Cc: Jon Grimm <jgrimm@austin.ibm.com>, tsvwg@ietf.org
Subject: Re: [Tsvwg] draft-ietf-tsvwg-rfc2960-bis-00.txt: SACK & rcv consumption
In-reply-to: Your message of Fri, 20 Jul 2001 11:57:50 PDT.
Date: Fri, 20 Jul 2001 12:35:34 -0700
From: Vern Paxson <vern@ee.lbl.gov>
Sender: tsvwg-admin@ietf.org
Errors-To: tsvwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Transport Area Working Group <tsvwg.ietf.org>
X-BeenThere: tsvwg@ietf.org

> > The second part makes me wonder, as I do not see other references to
> > SACK generation purely due to the receive application consuming data and
> > the consequent change to rwnd (as opposed to DATA chunk ack.)  Does this
> > happen (and what are the rules) or is there another situation that this
> > second clause refers to?
> > 
> 
> Yes, I think in TCP it does happen. It is a more rare event (I think)
> and not something that happens often...

It's not particularly rare - it can happen any time the receiving application
consumes arriving data in bursts.  The window diminishes as the receiving
kernel queues up data for the app to read, and then expands once the app
reads it.

		Vern

_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
http://www1.ietf.org/mailman/listinfo/tsvwg