TCP-CCC: single-path TCP congestion control coupling
draft-welzl-tcp-ccc-00

Document Type Active Internet-Draft (individual)
Last updated 2016-10-31
Replaces draft-welzl-irtf-iccrg-tcp-in-udp
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Congestion Control Research Group                      M. Welzl
Internet-Draft                                                  S. Islam
Intended status: Experimental                                  K. Hiorth
Expires: May 4, 2017                                  University of Oslo
                                                                  J. You
                                                                  Huawei
                                                        October 31, 2016

          TCP-CCC: single-path TCP congestion control coupling
                         draft-welzl-tcp-ccc-00

Abstract

   This document specifies a method, TCP-CCC, to combine the congestion
   controls of multiple TCP connections between the same pair of hosts.
   This can have several performance benefits, and it makes it possible
   to precisely assign a share of the congestion window to the
   connections based on priorities.  This document also addresses the
   problem that TCP connections between the same pair of hosts may not
   share the same path.  We discuss methods to detect if, or enforce
   that connections traverse a common bottleneck.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 4, 2017.

Welzl, et al.              Expires May 4, 2017                  [Page 1]
Internet-Draft                   TCP-CCC                    October 2016

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Coupled Congestion Control  . . . . . . . . . . . . . . . . .   3
   3.  Ensuring a Common Bottleneck  . . . . . . . . . . . . . . . .   6
     3.1.  Encapsulation . . . . . . . . . . . . . . . . . . . . . .   7
       3.1.1.  TCP in UDP  . . . . . . . . . . . . . . . . . . . . .   7
       3.1.2.  Other Methods . . . . . . . . . . . . . . . . . . . .  14
   4.  Related Work  . . . . . . . . . . . . . . . . . . . . . . . .  14
   5.  Implementation Status . . . . . . . . . . . . . . . . . . . .  15
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  16
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  16
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  19

1.  Introduction

   When multiple TCP connections between the same host pair compete on
   the same bottleneck, they often incur more delay and losses than a
   single TCP connection.  Moreover, it is often not possible to
   precisely divide the available capacity among the connections.  To
   address this problem, this document presents TCP-CCC, a method to
   combine the congestion controls of multiple TCP connections between
   the same pair of hosts.  This can have several performance benefits:

   o  Reduced average loss and queuing delay (because the competition
      between the encapsulated TCP connections is avoided)
Show full document text