Data Center Fast Congestion Management
draft-even-tsvwg-datacenter-fast-congestion-00

Document Type Active Internet-Draft (individual)
Last updated 2020-02-04
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized 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)
TSVWG                                                            R. Even
Internet-Draft                                                    M. Liu
Intended status: Informational                                  Y. Zhang
Expires: August 7, 2020                                           Huawei
                                                        February 4, 2020

                 Data Center Fast Congestion Management
             draft-even-tsvwg-datacenter-fast-congestion-00

Abstract

   A good congestion control for data centers (DC) should provide low
   latency, fast convergence and high link utilization.  Since multiple
   applications with different requirements may run on the DC network it
   is important to provide fairness between different applications that
   may use different congestion algorithms.  An important issue from the
   user perspective is to achieve short Flow Completion Time (FCT).
   This document proposes data center congestion control direction
   aiming to achieve high performance while proving fairness.

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 https://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 August 7, 2020.

Copyright Notice

   Copyright (c) 2020 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
   (https://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

Even, et al.             Expires August 7, 2020                 [Page 1]
Internet-Draft             DC Fast Congestion              February 2020

   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.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Congestion Handling Cases . . . . . . . . . . . . . . . . . .   3
     3.1.  Congestion only in leaf switch connected to receiver  . .   3
     3.2.  Congestion in the Spine switch  . . . . . . . . . . . . .   4
       3.2.1.  ECN case  . . . . . . . . . . . . . . . . . . . . . .   4
       3.2.2.  Spine and leaf switches share information . . . . . .   4
       3.2.3.  FCR from spine and leaf switches  . . . . . . . . . .   4
     3.3.  Congestion in leaf switch connected to data sender  . . .   4
   4.  Summary . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Rate Information  . . . . . . . . . . . . . . . . . . . . . .   5
   6.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   5
   7.  Implementation Options  . . . . . . . . . . . . . . . . . . .   6
   8.  Tests results . . . . . . . . . . . . . . . . . . . . . . . .   6
     8.1.  Many senders to one receiver  . . . . . . . . . . . . . .   6
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     11.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     11.2.  Informative References . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   The major use case that we are looking at is congestion control for
   Data Centers, a controlled environment as specified in
   RFC8085[RFC8085].  With the emerging Distributed Storage, AI/HPC
   (High Performance Computing), Machine Learning, etc., modern
   datacenter applications demand high throughput (40Gbps and above)
   with ultra-low latency of less than 10 microsecond per hop from the
   network, with low CPU overhead.  The end to end latency should be
   less than 50usec, this value is based on DCQCN [DCQCN].  The high
   link speed (>40Gb/s) in Data Centers (DC) are making network
   transfers complete faster and in fewer RTTs.  Network traffic in a
   data center is often a mix of short and long flows, where the short
   flows require low latencies and the long flows require high
Show full document text