[Teas] A Data Plane TE/QoS Machnism

"Liubing (Leo)" <leo.liubing@huawei.com> Wed, 10 July 2019 09:59 UTC

Return-Path: <leo.liubing@huawei.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id D4D11120119 for <teas@ietfa.amsl.com>; Wed, 10 Jul 2019 02:59:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id xti_UdDxP9am for <teas@ietfa.amsl.com>; Wed, 10 Jul 2019 02:58:59 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 177BE120099 for <teas@ietf.org>; Wed, 10 Jul 2019 02:58:59 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown []) by Forcepoint Email with ESMTP id DED203A7B54ADE26C3A9 for <teas@ietf.org>; Wed, 10 Jul 2019 10:58:56 +0100 (IST)
Received: from DGGEML406-HUB.china.huawei.com ( by lhreml704-cah.china.huawei.com ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 10 Jul 2019 10:58:54 +0100
Received: from DGGEML512-MBX.china.huawei.com ([]) by dggeml406-hub.china.huawei.com ([]) with mapi id 14.03.0439.000; Wed, 10 Jul 2019 17:57:20 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: "teas@ietf.org" <teas@ietf.org>
Thread-Topic: A Data Plane TE/QoS Machnism
Thread-Index: AdU3BRClG/HFfWwhR6WKHYyUgVv0kg==
Date: Wed, 10 Jul 2019 09:57:19 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F45DA480A48@dggeml512-mbx.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_8AE0F17B87264D4CAC7DE0AA6C406F45DA480A48dggeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/EG28_OKqf2ZBrTS7l5PQEefxMUc>
Subject: [Teas] A Data Plane TE/QoS Machnism
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jul 2019 09:59:02 -0000

Hi Dear all,

I've uploaded a new draft (as below), which introduces a mechanism to allow the devices to switch flows among multiple paths between a pairs of Ingress/Egress routers. The flow switch is based on real-time measurement of congestion situation of the paths.

Such mechanism could be used to do load balancing, SLA assurance and reliability etc. And we've had a commercial router hardware based prototype in our lab (SRv6 data plane) for network load balancing use case.

Since the mechanism is to adjust the paths, I guess it might be overall within the scope of our WG. Your comments would be appreciated very much!

Best regards,

*************************************Draft Info*************************************

Name:                  draft-liu-ican

Revision:              00

Title:                     Instant Congestion Assessment Network (iCAN) for Data Plane Traffic Engineering

Document date: 2019-07-08

Group:                  Individual Submission

Pages:                  8

URL:            https://www.ietf.org/internet-drafts/draft-liu-ican-00.txt

Status:         https://datatracker.ietf.org/doc/draft-liu-ican/

Htmlized:       https://tools.ietf.org/html/draft-liu-ican-00

Htmlized:       https://datatracker.ietf.org/doc/html/draft-liu-ican


   iCAN (instant Congestion Assessment Network) is a set of mechanisms

   running directly on network nodes:

   o  To adjust the flows paths based on real-time measurement of the

      candidate paths.

   o  The measurement is to reflect the congestion situation of each

      path, so that the ingress nodes could decide which flows need to

      be switched from a path to another.

   This is something that current SDN and TE technologies can hardly


   o  SDN Controller is slow and far from the data plane, it is neither

      able to assess the real-time congestion situation of each path,

      nor able to assure the data plane always go as expected

      (especially in SRv6 scenarios).  However, iCAN can work with SDN

      perfectly: controller planning multi-path transmission, and iCAN

      does the flow optimization automatically.

   o  Traditional TE is not able to adjust the flow paths in real-time.