[Tsvwg] draft-ietf-tsvwg-rfc2960-bis-00.txt: SACK & rcv consumption
Jon Grimm <jgrimm@austin.ibm.com> Fri, 20 July 2001 16:27 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 MAA19211 for <tsvwg-archive@odin.ietf.org>; Fri, 20 Jul 2001 12:27:22 -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 MAA06320; Fri, 20 Jul 2001 12:16:42 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA06289 for <tsvwg@ns.ietf.org>; Fri, 20 Jul 2001 12:16:39 -0400 (EDT)
Received: from mg03.austin.ibm.com (mg03.austin.ibm.com [192.35.232.20]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA16331 for <tsvwg@ietf.org>; Fri, 20 Jul 2001 12:15:43 -0400 (EDT)
Received: from austin.ibm.com (netmail1.austin.ibm.com [9.53.250.96]) by mg03.austin.ibm.com (AIX4.3/8.9.3/8.9.3) with ESMTP id LAA47036 for <tsvwg@ietf.org>; Fri, 20 Jul 2001 11:17:03 -0500
Received: from popmail.austin.ibm.com (popmail.austin.ibm.com [9.53.247.178]) by austin.ibm.com (AIX4.3/8.9.3/8.9.3) with ESMTP id LAA34410 for <tsvwg@ietf.org>; Fri, 20 Jul 2001 11:16:37 -0500
Received: from austin.ibm.com ([9.111.216.148]) by popmail.austin.ibm.com (AIX4.3/8.9.3/8.7-client1.01) with ESMTP id LAA20834 for <tsvwg@ietf.org>; Fri, 20 Jul 2001 11:16:34 -0500
Message-ID: <3B58583D.A7A8A754@austin.ibm.com>
Date: Fri, 20 Jul 2001 11:11:41 -0500
From: Jon Grimm <jgrimm@austin.ibm.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.1 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: tsvwg@ietf.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Tsvwg] draft-ietf-tsvwg-rfc2960-bis-00.txt: SACK & rcv consumption
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
Content-Transfer-Encoding: 7bit
From Section 6.2 .... A SCTP receiver MUST NOT generate more than one SACK for every incoming packet, other than to update the offered window as the receiving application consumes new data. .... The first part of this statement makes sense to me: worst case 1 SACK is sent for every 1 DATA chunk. 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? Thanks in advance for setting me straight, Jon Grimm _______________________________________________ tsvwg mailing list tsvwg@ietf.org http://www1.ietf.org/mailman/listinfo/tsvwg
- [Tsvwg] draft-ietf-tsvwg-rfc2960-bis-00.txt: SACK… Jon Grimm
- Re: [Tsvwg] draft-ietf-tsvwg-rfc2960-bis-00.txt: … Randall Stewart
- Re: [Tsvwg] draft-ietf-tsvwg-rfc2960-bis-00.txt: … Vern Paxson