Layer 3 Quantized Congestion Notification(L3QCN)in the Converged Network
draft-yu-tsvwg-l3qcn-00

Document Type Active Internet-Draft (individual)
Last updated 2016-10-31
Stream (None)
Intended RFC status (None)
Formats plain text 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-DRAFT                                                      Y.Yu
Intended Status: Standard Track                      HUAWEI Technologies
Expires: May 4, 2017                                    October 31, 2016

Layer 3 Quantized Congestion Notification(L3QCN)in the Converged Network
                        draft-yu-tsvwg-l3qcn-00

Abstract

   The more demands for the lossless and low latency network in the
   modern datacenter appear because the proliferation of demanding
   applications. Some congestion control schemes such as CN, PFC, ETS
   which is introduced by IEEE 802.1 focus on the L2 network domain.
   While current TCP/IP stacks can't meet these requirement on L3 or
   above networks. This draft introduces the L3QCN(Layer 3 Quantized
   Congestion Notification), an end to end congestion control scheme
   which adopt QCN and DCQCN on L2 network. It specifies protocols,
   procedures, and managed objects to support congestion control on the
   datacenter network.

Status of this Memo

   This Internet-Draft is submitted to IETF 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.

Copyright and License 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
 

Yolanda Yu                Expires May 4, 2017                   [Page 1]
INTERNET DRAFT    L3 Quantized Congestion Notification  October 31, 2016

   (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  . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1  Terminology . . . . . . . . . . . . . . . . . . . . . . . .  3
   2  Current Congestion Control method . . . . . . . . . . . . . . .  4
     2.1 QCN Introduction . . . . . . . . . . . . . . . . . . . . . .  4
       2.1.1 QCN Technical Solution . . . . . . . . . . . . . . . . .  4
       2.1.2 The limitation of QCN  . . . . . . . . . . . . . . . . .  5
     2.2 Introduction of DCQCN  . . . . . . . . . . . . . . . . . . .  6
       2.2.1 DCQCN technical solution . . . . . . . . . . . . . . . .  6
       2.2.2 The limitation of DCQCN  . . . . . . . . . . . . . . . .  6
   3. Layer3 QCN  . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     3.1 L3QCN Introduction . . . . . . . . . . . . . . . . . . . . .  6
     3.2 Use case of L3QCN  . . . . . . . . . . . . . . . . . . . . .  6
       3.2.1 A hybrid method with QCN . . . . . . . . . . . . . . . .  6
       3.2.2 L3QCN in CLOS fat-tree . . . . . . . . . . . . . . . . .  7
   4. Conclusion  . . . . . . . . . . . . . . . . . . . . . . . . . . 11
   5  Security Considerations . . . . . . . . . . . . . . . . . . . . 11
   6  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 11
   7  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     7.1  Normative References  . . . . . . . . . . . . . . . . . . . 11
     7.2  Informative References  . . . . . . . . . . . . . . . . . . 11
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12

 

Yolanda Yu                Expires May 4, 2017                   [Page 2]
INTERNET DRAFT    L3 Quantized Congestion Notification  October 31, 2016

1  Introduction

Currently, there are 3 classes of streams in the DC network:
1)Storage Traffic (Lossless)
2)High Compute Traffic(Low latency) 
3)Ethernet Traffic (Certain packet loss& latency tolerance)
Traditional DC network treat different traffic with different network
bearer which exist in the small scale DC. While with the expand of the
DC scale, there is an available method which use the Ethernet to bear
the streams by applying the congestion control method. IEEE has
introduced the following specifications:
Show full document text