Instant Congestion Assessment Network (iCAN) for Data Plane Traffic Engineering
draft-liu-ican-00

Document Type Active Internet-Draft (individual)
Last updated 2019-07-08
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)
Network Working Group                                             B. Liu
Internet-Draft                                       Huawei Technologies
Intended status: Standards Track                            July 8, 2019
Expires: January 9, 2020

  Instant Congestion Assessment Network (iCAN) for Data Plane Traffic
                              Engineering
                           draft-liu-ican-00

Abstract

   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
   achieve:

   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.

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."

Liu                      Expires January 9, 2020                [Page 1]
Internet-Draft                    iCAN                         July 2019

   This Internet-Draft will expire on January 9, 2020.

Copyright Notice

   Copyright (c) 2019 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
   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.  iCAN Architecture and Key Technical Requirements  . . . . . .   3
     2.1.  Architecture  . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Key technical requirements  . . . . . . . . . . . . . . .   5
       2.2.1.  Path quality assessment . . . . . . . . . . . . . . .   5
       2.2.2.  Recognition and statistic of flows in devices . . . .   5
       2.2.3.  Flow switching between paths  . . . . . . . . . . . .   5
   3.  Use Cases of iCAN . . . . . . . . . . . . . . . . . . . . . .   6
     3.1.  Network load balancing  . . . . . . . . . . . . . . . . .   6
     3.2.  SLA assurance . . . . . . . . . . . . . . . . . . . . . .   6
     3.3.  Fine-Granularity reliability  . . . . . . . . . . . . . .   6
   4.  Implementation Scenarios  . . . . . . . . . . . . . . . . . .   6
     4.1.  iCAN with SRv6  . . . . . . . . . . . . . . . . . . . . .   6
     4.2.  iCAN with VxLAN . . . . . . . . . . . . . . . . . . . . .   7
     4.3.  iCAN with MPLS/MPLS-TE  . . . . . . . . . . . . . . . . .   7
   5.  Standardization Requirements  . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   Traditional IP routing is shortest path based on static metrics,
   which can fulfil basic requirement of connectivity.  MPLS-TE brings
   the capability of utilizing non-shortest paths, thus traffic dispatch

Liu                      Expires January 9, 2020                [Page 2]
Internet-Draft                    iCAN                         July 2019
Show full document text