RE: [Tsvwg] Comment for the RFC-2960-bis draft.
Ivan.Arias-Rodriguez@nokia.com Wed, 18 July 2001 17:18 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 NAA15714 for <tsvwg-archive@odin.ietf.org>; Wed, 18 Jul 2001 13:18:09 -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 NAA25623; Wed, 18 Jul 2001 13:04:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA25593 for <tsvwg@ns.ietf.org>; Wed, 18 Jul 2001 13:04:39 -0400 (EDT)
Received: from mgw-x4.nokia.com (mgw-x4.nokia.com [131.228.20.27]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA13137 for <tsvwg@ietf.org>; Wed, 18 Jul 2001 13:03:44 -0400 (EDT)
From: Ivan.Arias-Rodriguez@nokia.com
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36]) by mgw-x4.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f6IH7ZG12073 for <tsvwg@ietf.org>; Wed, 18 Jul 2001 20:07:35 +0300 (EET DST)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir04nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.1) with ESMTP id <T54d409db08ac158f24077@esvir04nok.ntc.nokia.com>; Wed, 18 Jul 2001 20:04:28 +0300
Received: by esebh25nok with Internet Mail Service (5.5.2652.78) id <3MSVBP3N>; Wed, 18 Jul 2001 20:04:05 +0300
Message-ID: <E73DD1C4EDB0D84889A4E589B499A8A110B744@esebe001.NOE.Nokia.com>
To: ajung@exp-math.uni-essen.de, tsvwg@ietf.org, SIGTRAN@STANDARDS.NORTELNETWORKS.COM
Subject: RE: [Tsvwg] Comment for the RFC-2960-bis draft.
Date: Wed, 18 Jul 2001 20:04:02 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain; charset="iso-8859-1"
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id NAA25594
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
X-MIME-Autoconverted: from 8bit to quoted-printable by optimus.ietf.org id NAA25623
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA15714
Hi Andreas, > 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 ? Well, I think that it is quite clear from the title of the section, that it is related with reception of DATA chunks... Maybe you could insert "containing DATA chunks" right after "SHOULD be generated for at least every second packet"... but I don't really think that's necessary at all... Besides, I know your question is kind of "fictitious". You know crystal clear what it means, but just looking after (hypothetical) people who could have this doubt, isn't it so? :-) In addition, having such a doubt I think that the best first option would be going to section 4.2 of RFC 2581... There it tells you about data segments, and there is a reference to section 4.2.3.2 of RFC 1122... Reading this, I think that it is quite clear what it is meant in that paragraph of RFC 2960... :-/ > Best regards, > > Andreas Jungmaier BR Iván Arias Rodríguez _______________________________________________ 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