Transmission of DATA Chunks - question on CMT SCTP

<Karen.Nielsen@tieto.com> Thu, 27 January 2011 11:47 UTC

Return-Path: <Karen.Nielsen@tieto.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3EC4B3A698D for <tsvwg@core3.amsl.com>; Thu, 27 Jan 2011 03:47:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.555
X-Spam-Level:
X-Spam-Status: No, score=-6.555 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HlyTfIHZy6e6 for <tsvwg@core3.amsl.com>; Thu, 27 Jan 2011 03:47:56 -0800 (PST)
Received: from ebb05.tieto.com (ebb05.tieto.com [131.207.168.36]) by core3.amsl.com (Postfix) with ESMTP id 7D74A28C13B for <tsvwg@ietf.org>; Thu, 27 Jan 2011 03:47:55 -0800 (PST)
X-AuditID: 83cfa824-b7c66ae000000a29-4b-4d415c21f966
Received: from FIVLA-EXHUB02.eu.tieto.com ( [131.207.136.42]) by ebb05.tieto.com (SMTP Mailer) with SMTP id F9.D7.02601.12C514D4; Thu, 27 Jan 2011 13:50:58 +0200 (EET)
Received: from EXMB03.eu.tieto.com ([131.207.136.30]) by FIVLA-EXHUB02.eu.tieto.com ([131.207.136.42]) with mapi; Thu, 27 Jan 2011 13:50:57 +0200
From: Karen.Nielsen@tieto.com
To: dreibh@iem.uni-due.de, tsvwg@ietf.org
Date: Thu, 27 Jan 2011 13:50:57 +0200
Subject: Transmission of DATA Chunks - question on CMT SCTP
Thread-Topic: Transmission of DATA Chunks - question on CMT SCTP
Thread-Index: Acu+GHWnvdq0027TR82egdLIA61OHw==
Message-ID: <CF340E42AED0874C81947E18863DE77B0A52FB6D22@EXMB03.eu.tieto.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_CF340E42AED0874C81947E18863DE77B0A52FB6D22EXMB03eutieto_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAARci5Uo=
X-Mailman-Approved-At: Thu, 27 Jan 2011 04:49:56 -0800
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jan 2011 11:47:57 -0000

Hi,

In RFC 4960 Section 6.1 it is stated that transmission of new data should await retransmissions.
That is:

   C) When the time comes for the sender to transmit, before sending new
      DATA chunks, the sender MUST first transmit any outstanding DATA
      chunks that are marked for retransmission (limited by the current
      cwnd).

In our SCTP implementation we have followed this rule literally on a per association basis. That is, we do not send new data on any path of the association, if there
is data marked for retransmission which is awaiting transmittal. But I also know of SCTP implementations where this rule is obeyed only on an path basis. I.e. data for retransmission
is somehow locked to a particular path and new data may flow out on other paths even if there is data waiting to be retransmitted on a per association basis.

I would like to know if anybody knows what is the chosen approach in the CMT setting in this respect  - ?

Also I am interesting in knowing  if there is any clear consensus on how the RFC 4690 should be interpreted in the non CMT case - ?

Thanks !

BR, Karen


*****************************************************************************************
Karen Egede Nielsen
Software Architect, Ph.D.

Tieto Denmark A/S
IP Solutions, Telecom & Media
Skanderborgvej 232, 8260 Viby J, DK-Denmark
Direct Phone / Mobile +45 25134336
E-mail: karen.nielsen@tieto.com
*****************************************************************************************
www.tieto.com