Re: [tsvwg] SCTP ABC

Michael Tuexen <michael.tuexen@lurchi.franken.de> Thu, 24 June 2021 07:54 UTC

Return-Path: <michael.tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 507383A0DCE for <tsvwg@ietfa.amsl.com>; Thu, 24 Jun 2021 00:54:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lXPcjIq0kjEs for <tsvwg@ietfa.amsl.com>; Thu, 24 Jun 2021 00:54:07 -0700 (PDT)
Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC7E83A0DD3 for <tsvwg@ietf.org>; Thu, 24 Jun 2021 00:54:07 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2a02:8109:1140:c3d:81f7:3c45:843e:4a2e]) (Authenticated sender: lurchi) by mail-n.franken.de (Postfix) with ESMTPSA id 1C6AD721E2808; Thu, 24 Jun 2021 09:54:02 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\))
From: Michael Tuexen <michael.tuexen@lurchi.franken.de>
In-Reply-To: <591ED4DE-4649-423E-9A2A-123A864D498F@erg.abdn.ac.uk>
Date: Thu, 24 Jun 2021 09:53:51 +0200
Cc: Timo Völker <timo.voelker@fh-muenster.de>, tsvwg@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <2F041EB5-682A-4B89-A142-F324D37F2E91@lurchi.franken.de>
References: <376640B5-D7BB-4E4E-8E97-374A7014C3EF@fh-muenster.de> <591ED4DE-4649-423E-9A2A-123A864D498F@erg.abdn.ac.uk>
To: "Gorry (erg)" <gorry@erg.abdn.ac.uk>
X-Mailer: Apple Mail (2.3654.100.0.2.22)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/hio3EnMYb8Y92B_ZB6C91bpDYok>
Subject: Re: [tsvwg] SCTP ABC
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 24 Jun 2021 07:54:12 -0000

> On 24. Jun 2021, at 09:45, Gorry (erg) <gorry@erg.abdn.ac.uk> wrote:
> 
> See below:
> 
>> On 23 Jun 2021, at 16:02, Timo Völker <timo.voelker@fh-muenster.de> wrote:
>> 
>> Hi,
>> 
>> SCTP (RFC4960) limits the increase of its cwnd in slow start to one PMTU (or PMDCS as named in the rfc4960-bis document) as stated in Section 7.2.1. This means the cwnd may be increased less when the receiver sends an ack on every second packet compared to on every packet.
>> 
>> ---
>> Ex:
>> 1. A sender in slow start with PMTU=1200 sends two packets with 1000 byte of data each.
>> 
>>> DATA(len=1000, tsn=1)
>>> DATA(len=1000, tsn=2)
>> 
>> 2a. In case the receiver sends an ack on every packet, the sender receives two acks.
>> 
>> < ACK(cum_tsn=1)
>> --> cwnd += 1000
>> < ACK(cum_tsn=2)
>> --> cwnd += 1000
>> 
>> resulting in a cwnd increased by 2000 byte.
>> 
>> 2b. In case the receiver sends an ack on every second packet, the sender receives one ack for both packets.
>> 
>> < ACK(cum_tsn=2)
>> --> cwnd += 1200
>> 
>> resulting in a cwnd increased by only 1200 byte due to the PMTU limit.
>> ---
>> 
>> TCP's Appropriate Byte Counting (ABC) specified in RFC3465 addresses that with the parameter L set to 2*SMSS.
>> 
>> Adding a note for that in rfc4960-bis would help, I think.
>> 
>> Timo
> 
> What do others think?
> 
> Are the SCTP implementors happy with this proposal?
I would support integrating the ABC idea. This has been implemented in the FreeBSD kernel stack
and the userland stack for a long time.

Best regards
Michael
> 
> Gorry