Re: [Taps] TCP components
Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch> Thu, 11 June 2015 14:43 UTC
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 178301A8730 for <taps@ietfa.amsl.com>; Thu, 11 Jun 2015 07:43:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.91
X-Spam-Level:
X-Spam-Status: No, score=-3.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 tur4LjBkS9Si for <taps@ietfa.amsl.com>; Thu, 11 Jun 2015 07:42:58 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1E451A890F for <taps@ietf.org>; Thu, 11 Jun 2015 07:42:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 949F4D9307; Thu, 11 Jun 2015 16:42:27 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id KGGOIoN0nEBe; Thu, 11 Jun 2015 16:42:27 +0200 (MEST)
Received: from [82.130.103.143] (nb-10510.ethz.ch [82.130.103.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mirjak) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 5BB97D9305; Thu, 11 Jun 2015 16:42:27 +0200 (MEST)
Message-ID: <55799E53.2050200@tik.ee.ethz.ch>
Date: Thu, 11 Jun 2015 16:42:27 +0200
From: Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Mohamed Oulmahdi <m.oulmahdi@gmail.com>
References: <5579768E.5060402@tik.ee.ethz.ch> <2e1ca6a7e239e671b7516431ad5db93c.squirrel@erg.abdn.ac.uk> <5579971D.9040509@tik.ee.ethz.ch> <CAJ+dxNAM1OycSj6J9Qirb9=gbwFnrCUoBicRQafPO=bBXK-nnQ@mail.gmail.com>
In-Reply-To: <CAJ+dxNAM1OycSj6J9Qirb9=gbwFnrCUoBicRQafPO=bBXK-nnQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/pCBXfFVBLBCxJxgSfeS5ek1Pqy4>
Cc: gorry@erg.abdn.ac.uk, Brian Trammell <ietf@trammell.ch>, taps@ietf.org
Subject: Re: [Taps] TCP components
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions on Transport Services <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jun 2015 14:43:00 -0000
Hi Mohamed, see below. >>>> - Limited control over segment transmission scheduling (Nagle's >>>> algorithm): >>>> This allows for delay minimization in interactive applications. >>> >>> >>> GF: Not quite - To me, it prevents increased delay from the TCP protocol. >>> It doesn't really control anything to reduce delay. >> >> >> Yes, I think we wanted to say the same thing here; don't really see the difference... > > I don't understand this delay optimization. Is it thanks to Nagle's algorithm > or for the possibility of its deactivation? Because it's known that this > algorithm increase delay and so became unsuitable for delay-sensitive > applications... Yes, the delay is reduced if you deactivate it. The component is the fact that there is an algorithm that will influence when packets are sent (if data is available and the sending window is large enough). Mirja
- [Taps] TCP components Mirja Kühlewind
- Re: [Taps] TCP components gorry
- Re: [Taps] TCP components Mirja Kühlewind
- Re: [Taps] TCP components gorry
- Re: [Taps] TCP components Mohamed Oulmahdi
- Re: [Taps] TCP components Mirja Kühlewind
- Re: [Taps] TCP components Joe Touch
- Re: [Taps] TCP components Michael Welzl
- Re: [Taps] TCP components Mirja Kühlewind
- Re: [Taps] TCP components Michael Welzl
- Re: [Taps] TCP components Brian Trammell
- Re: [Taps] TCP components Erik Nygren
- Re: [Taps] TCP components Joe Touch
- Re: [Taps] TCP components Aaron Falk
- Re: [Taps] TCP components Mirja Kühlewind
- Re: [Taps] TCP components Michael Welzl
- Re: [Taps] TCP components Michael Welzl
- Re: [Taps] TCP components Mirja Kühlewind
- Re: [Taps] TCP components Michael Welzl
- Re: [Taps] TCP components Joe Touch
- Re: [Taps] TCP components Brian Trammell
- Re: [Taps] TCP components Michael Welzl
- Re: [Taps] TCP components Mirja Kühlewind
- Re: [Taps] TCP components Brian Trammell
- Re: [Taps] TCP components Michael Welzl
- Re: [Taps] TCP components Michael Welzl
- Re: [Taps] TCP components Mirja Kühlewind
- Re: [Taps] TCP components Joe Touch
- Re: [Taps] TCP components Joe Touch
- Re: [Taps] TCP components Mohamed Oulmahdi
- Re: [Taps] TCP components Joe Touch
- Re: [Taps] TCP components Mohamed Oulmahdi
- Re: [Taps] TCP components Joe Touch
- Re: [Taps] TCP components Michael Welzl
- Re: [Taps] TCP components Jon Crowcroft
- Re: [Taps] TCP components Joe Touch
- Re: [Taps] TCP components Wesley Eddy
- Re: [Taps] TCP components Karen Elisabeth Egede Nielsen
- Re: [Taps] TCP components Michael Welzl
- Re: [Taps] TCP components Karen Elisabeth Egede Nielsen
- Re: [Taps] TCP components Michael Welzl
- Re: [Taps] TCP components Joe Touch
- Re: [Taps] TCP components Karen Elisabeth Egede Nielsen
- Re: [Taps] TCP components Joe Touch