Re: [Idnet] Intelligence-Defined Network Architecture and Call for Interests
김민석 <mskim16@etri.re.kr> Wed, 29 March 2017 15:29 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 03877129526 for <idnet@ietfa.amsl.com>; Wed, 29 Mar 2017 08:29:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ZNOHJ9DPMgxO for <idnet@ietfa.amsl.com>; Wed, 29 Mar 2017 08:29:39 -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 6CCAB129613 for <idnet@ietf.org>; Wed, 29 Mar 2017 08:29:38 -0700 (PDT)
Received: from SMTP4.etri.info (129.254.28.74) by SMTPEG2.etri.info (129.254.27.142) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 30 Mar 2017 00:29:36 +0900
Received: from SMTP1.etri.info ([169.254.1.111]) by SMTP4.etri.info ([10.2.6.33]) with mapi id 14.03.0319.002; Thu, 30 Mar 2017 00:29:31 +0900
From: 김민석 <mskim16@etri.re.kr>
To: David Meyer <dmm@1-4-5.net>
CC: Brian Njenga <iambrianmuhia@gmail.com>, Jérôme François <jerome.francois@inria.fr>, Oscar Mauricio Caicedo Rendon <omcaicedo@unicauca.edu.co>, Sheng Jiang <jiangsheng@huawei.com>, "idnet@ietf.org" <idnet@ietf.org>
Thread-Topic: [Idnet] Intelligence-Defined Network Architecture and Call for Interests
Thread-Index: AQHSp96NotmNK6LAE0GQptHszQd4taGp43QAgAAR6oCAAAWvAIAAA0cAgADS4nyAAHZ5AIAAAmIAgACdXno=
Date: Wed, 29 Mar 2017 15:29:30 +0000
Message-ID: <5BC916BD50F92F45870ABA46212CB29CE4D07A@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> <5BC916BD50F92F45870ABA46212CB29CE4C966@SMTP1.etri.info> <CAHiKxWg-D3fCj0at2sxSr76MV8jiHO_TXisyiwSwM7hOXUSOdw@mail.gmail.com>, <CAHiKxWjmW6hbTCgKyVPvh98WjOBCOPJsRF9w+pJJdxr6jDv0AQ@mail.gmail.com>
In-Reply-To: <CAHiKxWjmW6hbTCgKyVPvh98WjOBCOPJsRF9w+pJJdxr6jDv0AQ@mail.gmail.com>
Accept-Language: ko-KR, en-US
Content-Language: ko-KR
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [129.254.28.42]
Content-Type: multipart/mixed; boundary="_004_5BC916BD50F92F45870ABA46212CB29CE4D07ASMTP1etriinfo_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idnet/CrC0uU_psdpTTFvAo78chy0Y4Nc>
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: Wed, 29 Mar 2017 15:29:43 -0000
Hi Dave, Thank you for giving me the great information. I absolutely agree your opinion that we need real ML data applied by data pre-processing so that we have been already trying to make available ML data on many ways such as clustering and classification. (using datasets of contents and URL) It's so challenge-able steps before using adaptive ML algorithm to network field. As you mentioned, RL is classical ML algorithm, but it is rapidly going develpment and make great results with tensorflow in many fields, unfortunately not network. For our tutorial, I attach some of practical examples with tensorflow as below, https://github.com/tensorflow/models Additionally, I submitted a personal draft to NMLRG even if it was closed from last meeting. It's about collaborative distributed multi-agent using re-inforcement learning and we trying to apply it to network real architecture. The attachment is on the email. I really appreciate giving me a small piece of your feedback and comment if you have a chance. Sincerely, Min-Suk Kim Senior Researcher / Ph.D. Intelligent IoE Network Research Section, ETRI ________________________________ 보낸 사람 : "David Meyer" <dmm@1-4-5.net> 보낸 날짜 : 2017-03-29 23:25:48 ( +09:00 ) 받는 사람 : 김민석 <mskim16@etri.re.kr> 참조 : Brian Njenga <iambrianmuhia@gmail.com>, Jérôme François <jerome.francois@inria.fr>, Oscar Mauricio Caicedo Rendon <omcaicedo@unicauca.edu.co>, Sheng Jiang <jiangsheng@huawei.com>, idnet@ietf.org <idnet@ietf.org> 제목 : Re: [Idnet] Intelligence-Defined Network Architecture and Call for Interests Apparently you can't attach a .pptx. The attachment is here (pptx and pdf): http://www.1-4-5.net/~dmm/ml/misc/musings.pptx http://www.1-4-5.net/~dmm/ml/misc/musings.pdf Thx, Dave On Wed, Mar 29, 2017 at 7:17 AM, David Meyer <dmm@1-4-5.net<mailto:dmm@1-4-5.net>> wrote: Hey Min-Suk, Totally agree we need to learn from our environment, and RL is a natural approach. After all, the network is always changing, has adversaries, etc. All of this means. among other things, that we can't make simplifying assumptions like stationary distributions, iid data, .... So RL is one way to attack these problems, and the classic algorithms you mention below are certainly a reasonable approach (I've been working with policy gradients [0], trying to model/adapt the two-player game approach of AlphaGo to networking; the problem there is that we don't have a source of labeled expert data like the KGS Go server (https://www.gokgs.com/) to build the supervised policy network....). You might also want to check out the recent "boot" of evolution strategies as a black-box approach to RL (in particular no gradients). See [1], [2], [3]. There is also a ton of code around if you want to try some of this out (see e.g.,https://github.com/dennybritz/reinforcement-learning; this one is in tensorflow). Finally, I've attached a few summary slides with some of my musings on this topic from past talks. Thanks, Dave [BTW, two player minimax games seem to be popping up everywhere: AlphaGo, variational autoencoders [4], GANs [5], and many others; something to thing about for our domain] [0] https://papers.nips.cc/paper/1713-policy-gradient-methods-for-reinforcement-learning-with-function-approximation.pdf [1] https://blog.openai.com/evolution-strategies/ [2] https://arxiv.org/pdf/1703.03864.pdf [3] http://jmlr.csail.mit.edu/papers/volume15/wierstra14a/wierstra14a.pdf [4] http://www.1-4-5.net/~dmm/ml/vae.pdf [5] https://arxiv.org/pdf/1406.2661.pdf On Tue, Mar 28, 2017 at 4:04 PM, 김민석 <mskim16@etri.re.kr<mailto:mskim16@etri.re.kr>> wrote: 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/
- Re: [Idnet] Intelligence-Defined Network Architec… Sheng Jiang
- [Idnet] Intelligence-Defined Network Architecture… Sheng Jiang
- Re: [Idnet] Intelligence-Defined Network Architec… David Meyer
- Re: [Idnet] Intelligence-Defined Network Architec… Shamik Mishra
- Re: [Idnet] Intelligence-Defined Network Architec… Oscar Mauricio Caicedo Rendon
- Re: [Idnet] Intelligence-Defined Network Architec… David Meyer
- Re: [Idnet] Intelligence-Defined Network Architec… David Meyer
- Re: [Idnet] Intelligence-Defined Network Architec… Brian Njenga
- Re: [Idnet] Intelligence-Defined Network Architec… David Meyer
- Re: [Idnet] Intelligence-Defined Network Architec… Pedro Martinez-Julia
- Re: [Idnet] Intelligence-Defined Network Architec… Brian Njenga
- Re: [Idnet] Intelligence-Defined Network Architec… Jérôme François
- Re: [Idnet] Intelligence-Defined Network Architec… David Meyer
- Re: [Idnet] Intelligence-Defined Network Architec… Pedro Martinez-Julia
- Re: [Idnet] Intelligence-Defined Network Architec… David Meyer
- Re: [Idnet] Intelligence-Defined Network Architec… Brian Njenga
- Re: [Idnet] Intelligence-Defined Network Architec… Jérôme François
- Re: [Idnet] Intelligence-Defined Network Architec… 김민석
- [Idnet] 答复: Intelligence-Defined Network Architec… dingxiaojian (A)
- Re: [Idnet] Intelligence-Defined Network Architec… David Meyer
- Re: [Idnet] Intelligence-Defined Network Architec… David Meyer
- Re: [Idnet] Intelligence-Defined Network Architec… Alex Galis
- Re: [Idnet] Intelligence-Defined Network Architec… Chris Hammerschmidt
- Re: [Idnet] Intelligence-Defined Network Architec… David Meyer
- Re: [Idnet] Intelligence-Defined Network Architec… Pedro Martinez-Julia
- Re: [Idnet] Intelligence-Defined Network Architec… 김민석
- Re: [Idnet] Intelligence-Defined Network Architec… David Meyer
- Re: [Idnet] Intelligence-Defined Network Architec… 김민석
- Re: [Idnet] Intelligence-Defined Network Architec… David Meyer
- Re: [Idnet] Intelligence-Defined Network Architec… Sheng Jiang
- Re: [Idnet] Intelligence-Defined Network Architec… YuLing Chen (yulingch)
- Re: [Idnet] Intelligence-Defined Network Architec… Michele Zorzi
- Re: [Idnet] Intelligence-Defined Network Architec… Manav Bhatia
- Re: [Idnet] Intelligence-Defined Network Architec… Sheng Jiang
- Re: [Idnet] Intelligence-Defined Network Architec… Wei Jiang
- Re: [Idnet] Intelligence-Defined Network Architec… Brian E Carpenter
- Re: [Idnet] Intelligence-Defined Network Architec… Aydin Ulas
- Re: [Idnet] Intelligence-Defined Network Architec… dingxiaojian (A)
- Re: [Idnet] Intelligence-Defined Network Architec… Pedro Martinez-Julia
- Re: [Idnet] Intelligence-Defined Network Architec… Laurent Ciavaglia
- Re: [Idnet] Intelligence-Defined Network Architec… Laurent Ciavaglia
- Re: [Idnet] Intelligence-Defined Network Architec… Jérôme François
- Re: [Idnet] Intelligence-Defined Network Architec… Lori Jakab
- Re: [Idnet] Intelligence-Defined Network Architec… Brian E Carpenter
- Re: [Idnet] Intelligence-Defined Network Architec… Brian E Carpenter
- Re: [Idnet] Intelligence-Defined Network Architec… Oscar Mauricio Caicedo Rendon
- Re: [Idnet] Intelligence-Defined Network Architec… Pedro Martinez-Julia
- Re: [Idnet] Intelligence-Defined Network Architec… David Meyer
- Re: [Idnet] Intelligence-Defined Network Architec… Juraj Giertl
- Re: [Idnet] Intelligence-Defined Network Architec… Pedro Martinez-Julia