Re: [Idnet] Summary 20170814 & IDN dedicated session call for case

Haoyu song <> Tue, 15 August 2017 20:10 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 81B881321F6 for <>; Tue, 15 Aug 2017 13:10:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ZUYCcuj6WEIF for <>; Tue, 15 Aug 2017 13:10:09 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9B0E313238E for <>; Tue, 15 Aug 2017 13:10:08 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id DTM49325; Tue, 15 Aug 2017 20:10:05 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.301.0; Tue, 15 Aug 2017 21:10:04 +0100
Received: from ([]) by ([]) with mapi id 14.03.0301.000; Tue, 15 Aug 2017 13:09:54 -0700
From: Haoyu song <>
To: Hesham ElBakoury <>, yanshen <>, "" <>
Thread-Topic: Summary 20170814 & IDN dedicated session call for case
Thread-Index: AdMUrc8Ikmqfd+z8QxaI3D4f5YkgmgBFDo4AAA5JSBA=
Date: Tue, 15 Aug 2017 20:09:53 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_78A2745BE9B57D4F9D27F86655EB87F925997F85SJCEML701CHMchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090205.5993551E.0087, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 6e8070943f36dfba4ff02f5725b4f6b6
Archived-At: <>
Subject: Re: [Idnet] Summary 20170814 & IDN dedicated session call for case
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "The IDNet \(Intelligence-Defined Network\) " <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 15 Aug 2017 20:10:13 -0000

Obviously we are not going to apply ML on networking just for the sake of ML. In my opinion, the only reason to apply ML is that it’s proved to be a better (or only) way to solve a problem. We have seen a few successful examples such as ETA and root cause analysis, and ML approaches seem promising on solving some networking problems, but I also agree that we are still far from  the conclusion (or don’t even have clear understanding) that all these use cases can be better solved by ML. Then it is even farther to think about standardizing the related protocols and interfaces at the current stage. That said, this doesn’t prevent us from studying the possibilities. The most important thing is to develop more solid use cases to demonstrate that ML is not only useful but preferred. The current list is still too high level which doesn’t help me gain such confidence yet. Hopefully more detailed reports will come.


From: IDNET [] On Behalf Of Hesham ElBakoury
Sent: Tuesday, August 15, 2017 5:49 AM
To: yanshen <>om>;
Subject: Re: [Idnet] Summary 20170814 & IDN dedicated session call for case

Hi Yanshen,

In all of these use cases what problems we are trying to solve that have not been solved before or why existing solutions are not good enough ?



From: IDNET [] On Behalf Of yanshen
Sent: Sunday, August 13, 2017 8:36 PM
Subject: [Idnet] Summary 20170814 & IDN dedicated session call for case

Dear all,

Here is a summary and some index (2017.08.14). Till now, whatever the case is supported or not, I tried to organize all the content and keep the core part. It is still welcome to contribute and discuss.

If I miss something important, please let me know. Apologized in advance.


---------  Roadmap  ---------
***Aug. : Collecting the use cases (related with NM). Rough thoughts and requirements
Sep. : Refining the cases and abstract the common elements
Oct. : Deeply analysis. Especially on Data Format, control flow, or other key points
Nov.: F2F discussions on IETF100
---------  Roadmap End  ---------

1. Gap and Requirement Analysis
    1.1 Network Management requirement
    1.2 TBD
2. Use Cases
    2.1 Traffic Prediction
                   Proposed by:<>
                   Abstract: Collect the history traffic data and external data which may influence the traffic. Predict the traffic in short/long/specific term. Avoid the congestion or risk in previously.

    2.2 QoS Management
                   Proposed by:<>
                   Abstract: Use multiple paths to distribute the traffic flows. Adjust the percentages. Avoid congestion and ensure QoS.

    2.3 Application (and/or DDoS) detection
                   Proposed by:<>
                   Abstract: Detect the application (or attack) from network packets (HTTPS or plain) Collect the history traffic data and identify a service or attack (ex: Skype, Viber, DDoS attack etc.)

         2.4 QoE Management
                   Proposed by:<>
                   Abstract: Collect low-level metrics (SNR, latency, jitter, losses, etc) and measure QoE. Then use ML to understand what is the relation between satisfactory QoE and the low-level metrics. As an example learn that when delay>N then QoE is degraded, but when M<delay<N then QoE is satisfactory for the customers (please note that QoE cannot be measured directly over your network). This is useful to understand how the network must be operated to provide satisfactory QoE.

         2.5 (Encrypted) Traffic Classification
                   Proposed by:<>;<>
                   Track: [Jerome] ; [Min-Suk Kim]
                            [Jerome] collect flow-level traffic metrics such as protocol information but also meta metrics such as distribution of packet sizes, inter-arrival times... Then use such information to label the traffic with the underlying application assuming that the granularity of classification may vary (type of application, exact application name, version...)
                            [Min-Suk Kim] continuously collect packet data, then applying learning process for traffic classification with generating application using deep learning models such as CNN (convolutional neural network) and RNN (recurrent neural network). Data-set to apply into the models are generated by processing with features of information from flow in packet data.

         2.6 TBD

3. Data Focus
    3.1 Data attribute
    3.2 Data format
    3.3 TBD

4. Support Technologies
    4.1 Benchmarking Framework
                   Proposed by:<>
                   Abstract: A proper benchmarking framework comprises a set of reference procedures, methods, and models that can (or better *must*) be followed to assess the quality of an AI mechanism proposed to be applied to the network management/control area. Moreover, and much more specific to the IDNET topics, is the inclusion, dependency, or just the general relation of a standard format enforced to the data that is used (input) and produced (output) by the framework, so a kind of "data market" can arise without requiring to transform the data. The initial scope of input/output data would be the datasets, but also the new knowledge items that are stated as a result of applying the benchmarking procedures defined by the framework, which can be collected together to build a database of benchmark results, or just contrasted with other existing entries in the database to know the position of the solution just evaluated. This increases the usefulness of IDNET.

    4.2 TBD