RFC 6356 on Coupled Congestion Control for Multipath Transport Protocols

rfc-editor@rfc-editor.org Sat, 15 October 2011 01:37 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C4C821F8CCF; Fri, 14 Oct 2011 18:37:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.559
X-Spam-Level:
X-Spam-Status: No, score=-102.559 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 hxV94qztjNRR; Fri, 14 Oct 2011 18:37:37 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 9E5A621F8CBF; Fri, 14 Oct 2011 18:37:37 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 810AB98C262; Fri, 14 Oct 2011 18:37:37 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6356 on Coupled Congestion Control for Multipath Transport Protocols
From: rfc-editor@rfc-editor.org
Message-Id: <20111015013737.810AB98C262@rfc-editor.org>
Date: Fri, 14 Oct 2011 18:37:37 -0700
Cc: multipathtcp@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Oct 2011 01:37:38 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6356

        Title:      Coupled Congestion Control for Multipath 
                    Transport Protocols 
        Author:     C. Raiciu, M. Handley,
                    D. Wischik
        Status:     Experimental
        Stream:     IETF
        Date:       October 2011
        Mailbox:    costin.raiciu@cs.pub.ro, 
                    m.handley@cs.ucl.ac.uk, 
                    d.wischik@cs.ucl.ac.uk
        Pages:      12
        Characters: 27961
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mptcp-congestion-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6356.txt

Often endpoints are connected by multiple paths, but communications
are usually restricted to a single path per connection.  Resource
usage within the network would be more efficient were it possible for
these multiple paths to be used concurrently.  Multipath TCP is a
proposal to achieve multipath transport in TCP.

New congestion control algorithms are needed for multipath transport
protocols such as Multipath TCP, as single path algorithms have a
series of issues in the multipath context.  One of the prominent
problems is that running existing algorithms such as standard TCP
independently on each path would give the multipath flow more than
its fair share at a bottleneck link traversed by more than one of its
subflows.  Further, it is desirable that a source with multiple paths
available will transfer more traffic using the least congested of the
paths, achieving a property called "resource pooling" where a bundle
of links effectively behaves like one shared link with bigger
capacity.  This would increase the overall efficiency of the network
and also its robustness to failure.

This document presents a congestion control algorithm that couples
the congestion control algorithms running on different subflows by
linking their increase functions, and dynamically controls the
overall aggressiveness of the multipath flow.  The result is a
practical algorithm that is fair to TCP at bottlenecks while moving
traffic away from congested links.  This document defines an Experimental 
Protocol for the Internet community.

This document is a product of the Multipath TCP Working Group of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC