IETF Logo Mail Archive

Re: [Tsvwg] Re: WGLC on draft-ietf-tsvwg-prsctp-00

"Armando L. Caro Jr." <acaro@mail.eecis.udel.edu> Wed, 02 July 2003 15: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 ESMTP id LAA27907 for <tsvwg-archive@odin.ietf.org>; Wed, 2 Jul 2003 11:47:21 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xjoj-0000Jg-Ks for tsvwg-archive@odin.ietf.org; Wed, 02 Jul 2003 11:46:54 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h62FkjNa001201 for tsvwg-archive@odin.ietf.org; Wed, 2 Jul 2003 11:46:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xjo8-0008NB-BN; Wed, 02 Jul 2003 11:46:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XQXx-00029T-BE for tsvwg@optimus.ietf.org; Tue, 01 Jul 2003 15:12:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07703 for <tsvwg@ietf.org>; Tue, 1 Jul 2003 13:34:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XP17-0006Uu-00 for tsvwg@ietf.org; Tue, 01 Jul 2003 13:34:09 -0400
Received: from louie.udel.edu ([128.4.40.12] helo=mail.eecis.udel.edu) by ietf-mx with esmtp (Exim 4.12) id 19XP16-0006Ur-00 for tsvwg@ietf.org; Tue, 01 Jul 2003 13:34:08 -0400
Received: by mail.eecis.udel.edu (Postfix, from userid 62) id 2510E329C1; Tue, 1 Jul 2003 13:33:59 -0400 (EDT)
Received: from stimpy.eecis.udel.edu (stimpy.eecis.udel.edu [128.4.40.17]) by mail.eecis.udel.edu (Postfix) with ESMTP id 637CC329BF; Tue, 1 Jul 2003 13:33:58 -0400 (EDT)
Date: Tue, 01 Jul 2003 13:33:58 -0400
From: "Armando L. Caro Jr." <acaro@mail.eecis.udel.edu>
X-X-Sender: <acaro@stimpy.eecis.udel.edu>
Reply-To: "Armando L. Caro Jr." <acaro@acm.org>
To: "Randall R. Stewart (home)" <randall@stewart.chicago.il.us>
Cc: "'tsvwg@ietf.org'" <tsvwg@ietf.org>
Subject: Re: [Tsvwg] Re: WGLC on draft-ietf-tsvwg-prsctp-00
In-Reply-To: <3F019E38.3020702@stewart.chicago.il.us>
Message-ID: <Pine.GSO.4.33.0307011327590.12434-100000@stimpy.eecis.udel.edu>
X-Spam-Status: No, hits=-5.0 required=6.0 tests=DEPT_RCVD,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, SPAM_PHRASE_00_01,USER_AGENT_PINE version=2.43
X-Sanitizer: This message has been sanitized!
X-Sanitizer-URL: http://mailtools.anomy.net/
X-Sanitizer-Rev: UDEL-ECECIS: Sanitizer.pm, v 1.64 2002/10/22 MIME-Version: 1.0
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: tsvwg-admin@ietf.org
Errors-To: tsvwg-admin@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>

On Tue, 1 Jul 2003, Randall R. Stewart (home) wrote:

> 2) We have not a consensus either way on if we need to limit the number
>      of forward TSN's.. I had put out a proposed text change... and asked
>      for comments... Brian and Armando chimed in that no change was
>      needed.. I am open to the group opinion... there are 3 basic things
>      I have  heard of (onlist and off):
>     a) No change
>     b) only one FWD-TSN out per RTT (I lean towards this if we do
>          anything)
>     c) send a FWD-TSN every other SACK

If people feel that there is a need to reduce the number of FWD-TSNs, then
I vote for option b. Note that in doing so, the timeliness of the FWD-TNSs
may make PR-SCTP useless. If the forward path is lossy, then TSNs will get
lost and their corresponding FWD-TSNs will get lost as well. Reducing the
number of FWD-TSNs increases the number of RTTs needed to notify the peer
that a TSN is being abandoned by the sender. Since the sender can bundle
FWD-TSNs with outgoing data, I am not concerned about too many on the
wire.

~armando

0--                                                  --0
| Armando L. Caro Jr.      |  Protocol Engineering Lab |
| www.cis.udel.edu/~acaro  |    University of Delaware |
0--                                                  --0


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

v2.23.0 | Report a Bug | By Email