IETF Logo Mail Archive

Re: [multipathtcp] draft-ietf-mptcp-architecture, proposed extra text on congestion control

<philip.eardley@bt.com> Fri, 10 December 2010 09:58 UTC

Return-Path: <philip.eardley@bt.com>
X-Original-To: multipathtcp@core3.amsl.com
Delivered-To: multipathtcp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E62DE3A6C96 for <multipathtcp@core3.amsl.com>; Fri, 10 Dec 2010 01:58:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.976
X-Spam-Level:
X-Spam-Status: No, score=-101.976 tagged_above=-999 required=5 tests=[AWL=0.070, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, USER_IN_WHITELIST=-100]
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 z7mAbGCHrXFC for <multipathtcp@core3.amsl.com>; Fri, 10 Dec 2010 01:58:10 -0800 (PST)
Received: from smtpe1.intersmtp.com (smtp61.intersmtp.COM [62.239.224.234]) by core3.amsl.com (Postfix) with ESMTP id DA8C13A6C92 for <multipathtcp@ietf.org>; Fri, 10 Dec 2010 01:58:09 -0800 (PST)
Received: from EVMHT68-UKRD.domain1.systemhost.net (10.36.3.105) by RDW083A005ED61.smtp-e1.hygiene.service (10.187.98.10) with Microsoft SMTP Server (TLS) id 8.3.106.1; Fri, 10 Dec 2010 09:59:40 +0000
Received: from EMV65-UKRD.domain1.systemhost.net ([169.254.2.51]) by EVMHT68-UKRD.domain1.systemhost.net ([10.36.3.105]) with mapi; Fri, 10 Dec 2010 09:59:40 +0000
From: philip.eardley@bt.com
To: Michael.Scharf@alcatel-lucent.com, multipathtcp@ietf.org
Date: Fri, 10 Dec 2010 09:59:39 +0000
Thread-Topic: [multipathtcp] draft-ietf-mptcp-architecture, proposed extra text on congestion control
Thread-Index: AcuXi2KiTOzDwZSzQOSamsMA5A1LnAAMxyhwACSN1PA=
Message-ID: <9510D26531EF184D9017DF24659BB87F32727BF8CF@EMV65-UKRD.domain1.systemhost.net>
References: <9510D26531EF184D9017DF24659BB87F32727BEF6A@EMV65-UKRD.domain1.systemhost.net> <133D9897FB9C5E4E9DF2779DC91E947C0498D52A@SLFSNX.rcs.alcatel-research.de>
In-Reply-To: <133D9897FB9C5E4E9DF2779DC91E947C0498D52A@SLFSNX.rcs.alcatel-research.de>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [multipathtcp] draft-ietf-mptcp-architecture, proposed extra text on congestion control
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multipathtcp>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Dec 2010 09:58:11 -0000

Ok, we won't add this level of detail, in order to get it into the iesg without delay.

-----Original Message-----
From: multipathtcp-bounces@ietf.org [mailto:multipathtcp-bounces@ietf.org] On Behalf Of SCHARF, Michael
Sent: 09 December 2010 18:02
To: multipathtcp@ietf.org
Subject: Re: [multipathtcp] draft-ietf-mptcp-architecture, proposed extra text on congestion control

I am not sure whether the architecture document should really outline a
specific congestion window manipulation algorithm, which may still be
subject to change.

A comment on not changing slow-start and error recovery phases could
IMHO be possible. But, in that case the question is what "is the same as
in TCP". Probably, RFC 5681? But we all know that this is not exactly
what TCP in the wild happens to use...

Michael


> -----Original Message-----
> From: multipathtcp-bounces@ietf.org 
> [mailto:multipathtcp-bounces@ietf.org] On Behalf Of 
> philip.eardley@bt.com
> Sent: Thursday, December 09, 2010 11:25 AM
> To: multipathtcp@ietf.org
> Subject: [multipathtcp] draft-ietf-mptcp-architecture, 
> proposed extra text on congestion control
> 
> Hi,
> 
> I've just been doing a review on the architecture draft 
> before submission to IESG.
> 
>  
> 
> I think it doesn't quite fully capture what (I believe) is 
> the WG consensus about the high-level design for congestion 
> control. My suggestion is to add the following:-
> 
>  
> 
> MPTCP uses an algorithm that links the increase phases of the 
> congestion avoidance state (specifying how the window 
> inflates upon receiving acknowledgements over the various 
> paths). The multiplicative decrease of the congestion 
> avoidance state is the same as in TCP, as are the slow start, 
> fast retransmit, and fast recovery algorithms.
> 
>  
> 
> Please shout whether you think it's ok to add this text, or 
> whether you think there isn't yet consensus.
> 
>  
> 
> http://tools.ietf.org/html/draft-ietf-mptcp-architecture-03#se
> ction-5.7
> 
>  
> 
> Thanks
> 
> Phil/ 
> 
>                                                               
>                                                               
>                                                    
> 
> 
_______________________________________________
multipathtcp mailing list
multipathtcp@ietf.org
https://www.ietf.org/mailman/listinfo/multipathtcp

v2.23.0 | Report a Bug | By Email