Re: [tcpm] New Version Notification for draft-you-tcpm-configuring-tcp-initial-window-00.txt

"Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com> Mon, 20 October 2014 12:52 UTC

Return-Path: <michael.scharf@alcatel-lucent.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 889CA1A8718 for <tcpm@ietfa.amsl.com>; Mon, 20 Oct 2014 05:52:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.879
X-Spam-Level:
X-Spam-Status: No, score=0.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45, T_RP_MATCHES_RCVD=-0.01] autolearn=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 tf3oVP3CjY0L for <tcpm@ietfa.amsl.com>; Mon, 20 Oct 2014 05:52:31 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81A1F1A8714 for <tcpm@ietf.org>; Mon, 20 Oct 2014 05:52:31 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id 84DE88ED8EC38; Mon, 20 Oct 2014 12:52:27 +0000 (GMT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s9KCqRar025759 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 20 Oct 2014 14:52:27 +0200
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.81]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0195.001; Mon, 20 Oct 2014 14:52:27 +0200
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: Runa Barik <runabk@ifi.uio.no>, Youjianjie <youjianjie@huawei.com>, "tcpm@ietf.org" <tcpm@ietf.org>
Thread-Topic: New Version Notification for draft-you-tcpm-configuring-tcp-initial-window-00.txt
Thread-Index: AQHP7C6yn6URl1adl0qtQLFH/DuYRJw4hSEggAAvm5WAABaK1oAAIeJg
Date: Mon, 20 Oct 2014 12:52:26 +0000
Message-ID: <655C07320163294895BBADA28372AF5D1667E5EE@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <F6C28B32DA084644BB6C8D0BD65B669D11BC91@nkgeml509-mbs.china.huawei.com>, <8b40056997754129b96351e867d2e0c9@mail-ex12.exprod.uio.no> <4d2c316f002248ca91fcaa8d968d6a1b@mail-ex12.exprod.uio.no>
In-Reply-To: <4d2c316f002248ca91fcaa8d968d6a1b@mail-ex12.exprod.uio.no>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.39]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tcpm/9x7fBC1qAk1CHnQYn0_VubfkdCQ
Cc: "tag@iitmandi.ac.in" <tag@iitmandi.ac.in>, "divakarand@i2r.a-star.edu.sg" <divakarand@i2r.a-star.edu.sg>
Subject: Re: [tcpm] New Version Notification for draft-you-tcpm-configuring-tcp-initial-window-00.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Oct 2014 12:52:33 -0000

Jianjie, Runa,

Research results regarding how to (automatically) set the IW are probably better discussed in the ICCRG, at least until ICCRG can give TCPM a good recommendation how to actually engineer a solution.

Furthermore, in the past there has been a certain consensus that IETF working groups only standardize abstract APIs to the network stack. The actual implementation e.g. as a socket option depends on the operating system.

Best regards

Michael


> -----Original Message-----
> From: tcpm [mailto:tcpm-bounces@ietf.org] On Behalf Of Runa Barik
> Sent: Monday, October 20, 2014 12:41 PM
> To: Youjianjie; tcpm@ietf.org
> Cc: divakarand@i2r.a-star.edu.sg; tag@iitmandi.ac.in
> Subject: Re: [tcpm] New Version Notification for draft-you-tcpm-
> configuring-tcp-initial-window-00.txt
> 
> Hi all,
> 
>  I forgot to mention the publications on this work.
>  1. http://link.springer.com/chapter/10.1007%2F978-3-642-30630-3_25
> 2.  http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=6761284&tag=1
> 3. http://www.network-of-the-future.org
> 
> We are about to submit a paper ``Characterizing the effects of TCP
> Initial Window".
> 
> Regards,
> - Runa Barik
> ________________________________________
> From: tcpm <tcpm-bounces@ietf.org> on behalf of Runa Barik
> <runabk@ifi.uio.no>
> Sent: Monday, October 20, 2014 11:41 AM
> To: Youjianjie; tcpm@ietf.org
> Cc: tag@iitmandi.ac.in; divakarand@i2r.a-star.edu.sg
> Subject: Re: [tcpm] New Version Notification for draft-you-tcpm-
> configuring-tcp-initial-window-00.txt
> 
> Hi all,
> 
> First, I appreciate the authors submitting a draft on this work. In
> this draft, TCP Initial Window (IW) is computed based on the size of
> the resources, say flow-size. However, it is more important to consider
> when the application does not know the size in advance. And the authors
> set the IW using socket options.
> 
> I worked on the problem related to deciding the TCP Initial Window (IW)
> in my Master thesis `` Improving Latency of Mice in the Internet: An
> Approach Based on TCP Initial Window" (problem focus started in 2011)
> under Dr. Dinil Mon Divakaran in IIT Mandi, India. We concluded that a
> constant value of IW is not appropriate both from Simulations, and
> Analytical tech, and understood that IW can be a function of resources
> in sender-side, and network state. For simplicity, we considered IW as
> a function  of flow-size. There are a couple of papers already
> published in WWIC'12, LCN'13, NoF'14 (accepted for publication). We
> also implemented an user library, and inside Linux kernel, and then
> experimented on a real testbed network. The nice thing about this work
> is that, even not knowing  the network state, the flow-size based IW
> function works well in various scenarios.
> 
> There are various ideas that can done for computing IW. These can be:
> 
>  1. Based on the number of connections that faces in IW loss in the
> previous RTT, for computing the IW for new connection;
> 2. Based on the number of previous connections
> (https://tools.ietf.org/html/draft-touch-tcpm-automatic-iw-03), and IW
> loss;
> 3. Based on flow characteristics.
> 
> I think this is a nice work to consider further, and I can contribute
> more on this.
> 
> Regards,
>  - Runa Barik
>    Department of Informatics
>   UiO, Oslo, Norway.
> 
> 
> 
> 
> ________________________________________
> From: tcpm <tcpm-bounces@ietf.org> on behalf of Youjianjie
> <youjianjie@huawei.com>
> Sent: Monday, October 20, 2014 8:32 AM
> To: tcpm@ietf.org
> Subject: [tcpm] 转发: New Version Notification for draft-you-tcpm-
> configuring-tcp-initial-window-00.txt
> 
> Hi all,
> 
> This document discusses a method to configure TCP's initial congestion
> window by a new API.
> Your questions and comments are appreciated.
> 
> Best Regards,
> Jianjie
> 
> -----邮件原件-----
> 发件人: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> 发送时间: 2014年10月20日 14:26
> 收件人: Youjianjie; Huangyihong (Rachel); Huangyihong (Rachel);
> Youjianjie
> 主题: New Version Notification for draft-you-tcpm-configuring-tcp-
> initial-window-00.txt
> 
> 
> A new version of I-D, draft-you-tcpm-configuring-tcp-initial-window-
> 00.txt
> has been successfully submitted by Jianjie You and posted to the IETF
> repository.
> 
> Name:           draft-you-tcpm-configuring-tcp-initial-window
> Revision:       00
> Title:          Configuring TCP's Initial Window
> Document date:  2014-10-19
> Group:          Individual Submission
> Pages:          8
> URL:            http://www.ietf.org/internet-drafts/draft-you-tcpm-
> configuring-tcp-initial-window-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-you-tcpm-
> configuring-tcp-initial-window/
> Htmlized:       http://tools.ietf.org/html/draft-you-tcpm-configuring-
> tcp-initial-window-00
> 
> 
> Abstract:
>    This document discusses that TCP's initial congestion window is not
> a
>    constant in different use cases.  It proposes a flexible method to
>    configure the initial window in order to keep up with the current
>    network state.
> 
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of
> submission until the htmlized version and diff are available at
> tools.ietf.org.
> 
> The IETF Secretariat
> 
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm