Re: [Idnet] Intelligence-Defined Network Architecture and Call for Interests

김민석 <mskim16@etri.re.kr> Tue, 28 March 2017 23:04 UTC

Return-Path: <mskim16@etri.re.kr>
X-Original-To: idnet@ietfa.amsl.com
Delivered-To: idnet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A2B1129546 for <idnet@ietfa.amsl.com>; Tue, 28 Mar 2017 16:04:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c1g-fzVf-GqF for <idnet@ietfa.amsl.com>; Tue, 28 Mar 2017 16:04:36 -0700 (PDT)
Received: from smtpeg.etri.re.kr (smtpeg2.etri.re.kr [129.254.27.142]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD998128E19 for <idnet@ietf.org>; Tue, 28 Mar 2017 16:04:35 -0700 (PDT)
Received: from SMTP2.etri.info (129.254.28.72) by SMTPEG2.etri.info (129.254.27.142) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 29 Mar 2017 08:04:33 +0900
Received: from SMTP1.etri.info ([169.254.1.111]) by SMTP2.etri.info ([169.254.2.142]) with mapi id 14.03.0319.002; Wed, 29 Mar 2017 08:04:29 +0900
From: =?utf-8?B?6rmA66+87ISd?= <mskim16@etri.re.kr>
To: Brian Njenga <iambrianmuhia@gmail.com>, =?utf-8?B?SsOpcsO0bWUgRnJhbsOnb2lz?= <jerome.francois@inria.fr>, "Oscar Mauricio Caicedo Rendon" <omcaicedo@unicauca.edu.co>, Sheng Jiang <jiangsheng@huawei.com>
CC: "idnet@ietf.org" <idnet@ietf.org>
Thread-Topic: [Idnet] Intelligence-Defined Network Architecture and Call for Interests
Thread-Index: AQHSp96NotmNK6LAE0GQptHszQd4taGp43QAgAAR6oCAAAWvAIAAA0cAgADS4nw=
Date: Tue, 28 Mar 2017 23:04:29 +0000
Message-ID: <5BC916BD50F92F45870ABA46212CB29CE4C966@SMTP1.etri.info>
References: <5D36713D8A4E7348A7E10DF7437A4B927CD15A18@NKGEML515-MBS.china.huawei.com> <CABo5upUAQaGXTP5Q+pp++ABipMc-Yu2rKp=DGVFky+L3qzdUEg@mail.gmail.com> <CAAAu=jwv=gmtFPJC3RQ9YBjTSukz5p7BoGLmHubJnHCWgkQnCA@mail.gmail.com> <f4a0ef2b-bba1-8b02-ba63-b119438fc13e@inria.fr>, <CAAAu=jytqiHmL17z_x6828Jy5YZegV=sJ_RrS0uTsNnSZZr7cg@mail.gmail.com>
In-Reply-To: <CAAAu=jytqiHmL17z_x6828Jy5YZegV=sJ_RrS0uTsNnSZZr7cg@mail.gmail.com>
Accept-Language: ko-KR, en-US
Content-Language: ko-KR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [129.254.28.42]
Content-Type: multipart/alternative; boundary="_000_5BC916BD50F92F45870ABA46212CB29CE4C966SMTP1etriinfo_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idnet/kOC7OQ82rlPtj16rpqLHXxP2kwQ>
Subject: Re: [Idnet] Intelligence-Defined Network Architecture and Call for Interests
X-BeenThere: idnet@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "The IDNet \(Intelligence-Defined Network\) " <idnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idnet>, <mailto:idnet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idnet/>
List-Post: <mailto:idnet@ietf.org>
List-Help: <mailto:idnet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idnet>, <mailto:idnet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Mar 2017 23:04:46 -0000

Hi Brian,


As you mentioned by the prior email, anticipating network DDos attacks is really trendy issue to solve by ML techniques.

We also make some efforts how to avoid fagile nodes by a trustworthy communication, that means quantifying trustworthiness of node with normalization of various requirements such as security function, bandwidth and etc.

We are freshly approaching in routing layer with confidence using our own requirements, TPD(Trust Policy Distribution) and TD(Trust Degree). These requirements are considered to be solved by Reinforcement Learning (RL) that is one of the ML algorithms. RL is useful to control some of network policy about specific actions and states with reinforced and purnished rewards (+/-), but the problem is too slow to acquire satisified performance. Other ways to say it, anormaly dectection and regression analysis might be both efficient approaching methods to solve the issues Dave mentioned.


Best Regards,



Min-Suk Kim

Senior Researcher / Ph.D.
Intelligent IoE Network Research Section,
Electronics and Telecommunications Research Institute (ETRI)
e-mail          :  mskim16@etri.re.kr<mailto:nskim@etri.re.kr>
http://www.etri.re.kr/











________________________________
보낸 사람 : "Brian Njenga" <iambrianmuhia@gmail.com>
보낸 날짜 : 2017-03-29 03:38:49 ( +09:00 )
받는 사람 : Jérôme François <jerome.francois@inria.fr>fr>, Oscar Mauricio Caicedo Rendon <omcaicedo@unicauca.edu.co>co>, Sheng Jiang <jiangsheng@huawei.com>
참조 : idnet@ietf.org <idnet@ietf.org>
제목 : Re: [Idnet] Intelligence-Defined Network Architecture and Call for Interests



Got it, thanks! Great response. What other research questions do people have?



On Tue, 28 Mar 2017, 21:26 Jérôme François, <jerome.francois@inria.fr<mailto:jerome.francois@inria.fr>> wrote:



Hi,



class="gmail_msg">



class="gmail_msg">
Le 28/03/2017 à 20:06, Brian Njenga a écrit :



class="gmail_msg">

I'm glad that the discussions​ on how to make AI/ML useful in the design of the internet's architecture are continuing, albeit under a different name. I'd like to participate remotely as well.

I have a question that someone more thoughtful​ than I could answer: Are there research questions on how to anticipate network-threatening DDOS attacks, such as those coming from the Mirai botnet family, using ML? Even going as far as designing and standardising an efficient, secure network protocol for IoT devices. This is a complicated issue, which involves emerging markets, so I'm interested in useful ideas from any angle.

Regarding DDoS, I think we have to consider two angles even when considering protecting the network. The flooding-like attacks (1) and the most sophisticated attack that can highly degrade service performance even with few packets (2) (and of course this also concerns network service, even more than before with network softwarization which puts network functions into VM, being thus more exposed than before in my opinion).



class="gmail_msg">



class="gmail_msg">For type 1, there are usually observable signs of a future attack (without ML) in the hours or days before with an increasing load. However even if you observe it, it is very hard to fully characterize it and so prevent it to really happen. For type 2, you basically need to predict what should be the load induced by a packet or flow when considering the targeted service. Assuming you have no complete knwoledge of the service, you can try to use some learning and regression techniques to do it but assuming also that the trafic is encrypted, the problem becomes more difficult.



class="gmail_msg">



class="gmail_msg">jerome



class="gmail_msg">



class="gmail_msg">

Thanks, and I'm glad to meet you all.

Best regards,



class="gmail_msg">Brian Muhia.



class="gmail_msg">
On Tue, 28 Mar 2017, 20:02 Oscar Mauricio Caicedo Rendon, <omcaicedo@unicauca.edu.co<mailto:omcaicedo@unicauca.edu.co>> wrote:



class="gmail_msg">
Hi, all,



class="gmail_msg">



class="gmail_msg">
If there is a meeting, I would like to participate remotely.



class="gmail_msg">



class="gmail_msg">
Best regards,



class="gmail_msg">



class="gmail_msg">
Oscar



class="gmail_msg">



class="gmail_msg">
On Tue, Mar 28, 2017 at 11:29 AM, Sheng Jiang <jiangsheng@huawei.com<mailto:jiangsheng@huawei.com>> wrote:



class="gmail_msg">
Hi, all,



class="gmail_msg">



class="gmail_msg">Although there are many understanding for Intelligence-Defined Network, we are actually using this IDN as a term reference to the SDN-beyond architecture that we presented in IETF97, see the below link. A reference model is presented in page 3, while potential standardization works is presented in page 9.



class="gmail_msg">



class="gmail_msg">https://www.ietf.org/proceedings/97/slides/slides-97-nmlrg-intelligence-defined-network-01.pdf



class="gmail_msg">



class="gmail_msg">Although it might be a little bit too early for AI/ML in network giving the recent story of the concluded proposed NMLRG, we still would like to call for interests in IDN. Anybody (on site in Chicago this week) are interested in this or even wider topics regarding to AI/ML in network, please contact me on jiangsheng@huawei.com<mailto:jiangsheng@huawei.com> . Then we may have an informal meeting to discuss some common interests and potential future activities (not any activities in IETF, but also other STO or experimental trails, etc.)  on Thursday morning.



class="gmail_msg">



class="gmail_msg">FYI, we have already working on a Work Item, called IDN in the ETSI NGP (Next Generation Protocol) ISG, links below.



class="gmail_msg">



class="gmail_msg">https://portal.etsi.org/tb.aspx?tbid=844&SubTB=844



class="gmail_msg">https://portal.etsi.org/webapp/WorkProgram/Report_WorkItem.asp?WKI_ID=51011



class="gmail_msg">



class="gmail_msg">Meanwhile, please do use this mail list as a forum to discuss any topics that may applying AI/ML into network area.



class="gmail_msg">



class="gmail_msg">Best regards,



class="gmail_msg">



class="gmail_msg">Sheng



class="gmail_msg">_______________________________________________



class="gmail_msg">IDNET mailing list



class="gmail_msg">IDNET@ietf.org<mailto:IDNET@ietf.org>



class="gmail_msg">https://www.ietf.org/mailman/listinfo/idnet



class="gmail_msg">



class="gmail_msg">



class="gmail_msg" clear="all">



class="gmail_msg">--



class="gmail_msg">
Oscar Mauricio Caicedo Rendón
PhD Computer Science - Federal University of Rio Grande do Sul
Full Profesor - University of Cauca



class="gmail_msg">
________________________________
Universidad del Cauca: Comprometidos con la calidad.
_______________________________________________



class="gmail_msg">IDNET mailing list



class="gmail_msg">IDNET@ietf.org<mailto:IDNET@ietf.org>



class="gmail_msg">https://www.ietf.org/mailman/listinfo/idnet



class="gmail_msg">
--



class="gmail_msg">
Some say he really tries to learn efficiently.



class="gmail_msg">




class="gmail_msg">

_______________________________________________
IDNET mailing list
IDNET@ietf.org<mailto:IDNET@ietf.org>
https://www.ietf.org/mailman/listinfo/idnet




class="gmail_msg">
--



Some say he really tries to learn efficiently.