[Tsvwg] Comment for the RFC-2960-bis draft.
Andreas Jungmaier <ajung@exp-math.uni-essen.de> Wed, 18 July 2001 16:51 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 MAA11051 for <tsvwg-archive@odin.ietf.org>; Wed, 18 Jul 2001 12:51:32 -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 MAA19269; Wed, 18 Jul 2001 12:36:04 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA19237 for <tsvwg@ns.ietf.org>; Wed, 18 Jul 2001 12:36:01 -0400 (EDT)
Received: from irmgard.exp-math.uni-essen.de (irmgard.exp-math.uni-essen.de [132.252.150.18]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA07478 for <tsvwg@ietf.org>; Wed, 18 Jul 2001 12:35:06 -0400 (EDT)
Received: from biene.exp-math.uni-essen.de (biene.exp-math.uni-essen.de [132.252.150.215]) by irmgard.exp-math.uni-essen.de (8.9.3/8.9.3) with ESMTP id SAA08480; Wed, 18 Jul 2001 18:35:55 +0200
Received: from biene.exp-math.uni-essen.de (localhost.localdomain [127.0.0.1]) by biene.exp-math.uni-essen.de (Postfix) with SMTP id 16681BC06; Wed, 18 Jul 2001 18:36:19 -0400 (EDT)
Content-Type: text/plain; charset="iso-8859-1"
From: Andreas Jungmaier <ajung@exp-math.uni-essen.de>
Organization: University of Essen, Germany
To: TSVWG Liste <tsvwg@ietf.org>, SIGTRAN Liste <SIGTRAN@STANDARDS.NORTELNETWORKS.COM>
Date: Wed, 18 Jul 2001 18:36:10 -0400
X-Mailer: KMail [version 1.2]
MIME-Version: 1.0
Message-Id: <01071818361000.31493@biene.exp-math.uni-essen.de>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [Tsvwg] Comment for the RFC-2960-bis draft.
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: 8bit
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear all, I have a remark for section 6.2. of the current RFC 2960 respectively the same section in the document draft-ietf-tsvwg-rfc2960-bis-00.txt It says there: 6.2 Acknowledgement on Reception of DATA Chunks The SCTP endpoint MUST always acknowledge the reception of each valid DATA chunk. The guidelines on delayed acknowledgement algorithm specified in Section 4.2 of [RFC2581] SHOULD be followed. Specifically, an acknowledgement SHOULD be generated for at least every second packet (not every second DATA chunk) received, and SHOULD be generated within 200 ms of the arrival of any unacknowledged DATA chunk. Now, it is, IMHO, not clear from that section whether that only applies to packets containing data chunks (as one could think according to the section header), or it applies to _all_ packets (well, it says "EVERY SECOND PACKET"). I am not sure whether it would make sense to send a SACK after two Heartbeat chunks have been received ?! Any comments ? Best regards, Andreas Jungmaier - ---------------------------------------------------------------------------- \|/ _____ \|/ Andreas Jungmaier, Dipl.-Ing. "@'/ , . \`@" University of Essen ajung@exp-math.uni-essen.de /_| \___/ |__\ -> Computer Networking Tel. : +49 (0201) 183-7636 \___U_/ Technology Group <- - ---------------------------------------------------------------------------- PGP Public Key and Fingerprint: see http://www.exp-math.uni-essen.de/~ajung - ---------------------------------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.5 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7Vg9gd2Uw+xBvGUIRAkdnAJ92WGOZOS4Pd3rwKF/GtBsBcD9QTQCgns3V Hql19wXuTlwQDf1yxGYnA3Q= =PP9M -----END PGP SIGNATURE----- _______________________________________________ tsvwg mailing list tsvwg@ietf.org http://www1.ietf.org/mailman/listinfo/tsvwg
- [Tsvwg] Comment for the RFC-2960-bis draft. Andreas Jungmaier
- RE: [Tsvwg] Comment for the RFC-2960-bis draft. Ivan.Arias-Rodriguez