Re: [tsvwg] WGLC Announcement for draft-ietf-tsvwg-sctp-sack-immediately-02: 19th March 2013

Yoshifumi Nishida <nishida@sfc.wide.ad.jp> Tue, 02 April 2013 18:09 UTC

Return-Path: <nishida@sfc.wide.ad.jp>
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 6985721F8CE9 for <tsvwg@ietfa.amsl.com>; Tue, 2 Apr 2013 11:09:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.977
X-Spam-Level:
X-Spam-Status: No, score=-101.977 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id grFwKflWrO3E for <tsvwg@ietfa.amsl.com>; Tue, 2 Apr 2013 11:09:20 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (ns.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:143]) by ietfa.amsl.com (Postfix) with ESMTP id F2D8421F8B19 for <tsvwg@ietf.org>; Tue, 2 Apr 2013 11:09:19 -0700 (PDT)
Received: from mail-lb0-f180.google.com (mail-lb0-f180.google.com [209.85.217.180]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 4A87F2780BC for <tsvwg@ietf.org>; Wed, 3 Apr 2013 03:09:16 +0900 (JST)
Received: by mail-lb0-f180.google.com with SMTP id t11so773335lbi.11 for <tsvwg@ietf.org>; Tue, 02 Apr 2013 11:09:13 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.112.143.10 with SMTP id sa10mr4152902lbb.36.1364926153355; Tue, 02 Apr 2013 11:09:13 -0700 (PDT)
Received: by 10.114.4.39 with HTTP; Tue, 2 Apr 2013 11:09:13 -0700 (PDT)
In-Reply-To: <A7378318-1AA0-4B8C-B2A6-DF45B7F5A63B@lurchi.franken.de>
References: <4F605902.40009@erg.abdn.ac.uk> <5148B330.3000304@erg.abdn.ac.uk> <CAO249ycs-1at532RQWHzJVpH49p-PyXX4Sh=e=DGTs7WqMKOzQ@mail.gmail.com> <A7378318-1AA0-4B8C-B2A6-DF45B7F5A63B@lurchi.franken.de>
Date: Tue, 02 Apr 2013 11:09:13 -0700
Message-ID: <CAO249yfqpN+fufYpfc_wbg3Mv5+P_pHP3kjjVH_1miLJGZ8mEg@mail.gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] WGLC Announcement for draft-ietf-tsvwg-sctp-sack-immediately-02: 19th March 2013
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
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: <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: Tue, 02 Apr 2013 18:09:20 -0000

Hi Michael,

On Tue, Apr 2, 2013 at 12:27 AM, Michael Tuexen
<Michael.Tuexen@lurchi.franken.de> wrote:
> On Apr 2, 2013, at 8:29 AM, Yoshifumi Nishida wrote:

>> 2: Because this rule will be checked on every packet transmission, I
>> would like to know if the draft suggests to set I-bit everytime we
>> have a chance or there might be a case where we shouldn't.
> The sender could do it to switch off delayed SACK. However, this
> might not be useful. Therefore, as stated, the sender should set it,
> when he is waiting for an SACK.

OK. I just wanted to mention that in ideal equilibrium state, we might
need to set I-bit every packet since you'll get an ACK for 1 MSS,
which opens 1 MSS in cwnd.
But, as far as I can think this won't be a problem as the receiver has
a freedom to ignore it if it's necessary. (e.g. too much overhead)

BTW, we might want to set I-bit when we find there's no more packet to
send in buffer after sending a packet, even though
SCTP_SACK_IMMEDIATELY is not used.
Do you have any comment on this?

Thanks,
--
Yoshifumi