Re: [Nmlrg] Machine Learning in network - solicitation for use cases
"Liubing (Leo)" <leo.liubing@huawei.com> Tue, 08 September 2015 04:00 UTC
Return-Path: <leo.liubing@huawei.com>
X-Original-To: nmlrg@ietfa.amsl.com
Delivered-To: nmlrg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 331221A8925
for <nmlrg@ietfa.amsl.com>; Mon, 7 Sep 2015 21:00:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001,
T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 e_IEbpCYXHXB for <nmlrg@ietfa.amsl.com>;
Mon, 7 Sep 2015 21:00:55 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [58.251.152.64])
(using TLSv1 with cipher RC4-SHA (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id F16C41A8909
for <nmlrg@irtf.org>; Mon, 7 Sep 2015 21:00:54 -0700 (PDT)
Received: from 172.24.1.51 (EHLO nkgeml402-hub.china.huawei.com)
([172.24.1.51])
by szxrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued)
with ESMTP id CUN60406; Tue, 08 Sep 2015 12:00:43 +0800 (CST)
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.214]) by
nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.03.0235.001;
Tue, 8 Sep 2015 12:00:30 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Sheng Jiang <jiangsheng@huawei.com>, Brian E Carpenter
<brian.e.carpenter@gmail.com>, Dacheng Zhang <dacheng.zdc@alibaba-inc.com>,
"nmlrg@irtf.org" <nmlrg@irtf.org>
Thread-Topic: [Nmlrg] Machine Learning in network - solicitation for use cases
Thread-Index: AQHQ48AegVsK0UL1fk+2fNxpqlcTQp4u5gnE///RqACAALXdgIAAbfMAgAAYC4CAAYcXgIAAi5ug
Date: Tue, 8 Sep 2015 04:00:29 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F45C227BE52@nkgeml506-mbx.china.huawei.com>
References: <D20A251E.25E52%dacheng.zdc@alibaba-inc.com>
<5D36713D8A4E7348A7E10DF7437A4B927BB2B192@nkgeml512-mbx.china.huawei.com>
<D20B2C03.25EC7%dacheng.zdc@alibaba-inc.com>
<5D36713D8A4E7348A7E10DF7437A4B927BB2D062@nkgeml512-mbx.china.huawei.com>
<D211D160.26495%dacheng.zdc@alibaba-inc.com>
<D211D7F2.2651C%dacheng.zdc@alibaba-inc.com>
<5D36713D8A4E7348A7E10DF7437A4B927BB2D300@nkgeml512-mbx.china.huawei.com>
<55EC9987.9030002@gmail.com>
<5D36713D8A4E7348A7E10DF7437A4B927BB2D65D@nkgeml512-mbx.china.huawei.com>
<55ED09ED.3090406@gmail.com>
<5D36713D8A4E7348A7E10DF7437A4B927BB2DD75@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B927BB2DD75@nkgeml512-mbx.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.98.117]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/nmlrg/sSV6RsOzSaR9vraO98DPT2EHjaQ>
Subject: Re: [Nmlrg] Machine Learning in network - solicitation for use cases
X-BeenThere: nmlrg@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Network Machine Learning Research Group <nmlrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/nmlrg>,
<mailto:nmlrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nmlrg/>
List-Post: <mailto:nmlrg@irtf.org>
List-Help: <mailto:nmlrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/nmlrg>,
<mailto:nmlrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Sep 2015 04:00:58 -0000
> >> Hi, Brian, > >> > >> I believe there is feedback-style training in spam processing. But > >> what do > >you mean by "human" training? Do you mean the feedback is decided and > >feed by human administrators? I believe this could be done by machine > >learning mechanisms. > > > >In the spam case it is definitely a real live human who must detect an > >error by the classifier. In my case I estimate that maybe 0.5% of the > >messages in my Gmail spam folder are not spam, and maybe 1% in my > Gmail > >Inbox are actually spam. > > > >I think that for real-time DDOS protection, the solution has to include > >real-time input from an operator for both cases: "This is not an > >attack" and "You missed an attack". I think that means that the > >machine-learning system will always run in training mode, even if > >training is only needed in 1% of cases. > > The automatic in DDoS scenarios may be more critic than the SPAM > scenarios. In the worst case, the time of waiting human input/feedback may > already be enough for attackers to make significant damage. [Bing] For SPAM machine learning case, I guess the human feedback is only the source of labeled training data. All the Gmail users (I read there were 900M users) are together training the SPAM filter. So, the filter might not directly response to one single feedback. If DDoS is the similar approach, then I guess the human feedback won't make the learning program react either? But I'm curious about what is the item that could be labeled as "This is not an attack " or " You missed an attack ". E.g., the item is an packet, a stream, or any other kind of N-tuple things. Best regards, Bing > However, this may not be directly relative to machine learning. The programs that react > according to machine learning results may be if-else style. It may also > potentially be another machine learning mechanism. > > Sheng > > >> Actually, spam filtering was one of the earliest network-relevant > >> area that > >starts to use machine learning. It would worth to study the machine > >learning applications in spam filtering. Or we could invite some expert > >in this area to join nmlrg discussion. > > > >Agreed > > Brian > > > >> > >> Best regards, > >> > >> Sheng > >> > >>> How can > >>> human training be achieved for a real-time case like DDOS? > >>> > >>> Brian > >>> > >>>> > >>>> Best regards, > >>>> > >>>> Sheng > >>>> > >>>>> There were some related discussions in Dots. If you are > >>>>> interested, I could find them out later. > >>>>> > >>>>> _______________________________________________ > >>>>> nmlrg mailing list > >>>>> nmlrg@irtf.org > >>>>> https://www.irtf.org/mailman/listinfo/nmlrg > >>>> _______________________________________________ > >>>> nmlrg mailing list > >>>> nmlrg@irtf.org > >>>> https://www.irtf.org/mailman/listinfo/nmlrg > >>>> > > > >_______________________________________________ > >nmlrg mailing list > >nmlrg@irtf.org > >https://www.irtf.org/mailman/listinfo/nmlrg > _______________________________________________ > nmlrg mailing list > nmlrg@irtf.org > https://www.irtf.org/mailman/listinfo/nmlrg
- [Nmlrg] Machine Learning in network - solicitatio… Sheng Jiang
- Re: [Nmlrg] Machine Learning in network - solicit… Dacheng Zhang
- [Nmlrg] Using Machine Learning for Network Device… Liubing (Leo)
- Re: [Nmlrg] Using Machine Learning for Network De… Sheng Jiang
- Re: [Nmlrg] Using Machine Learning for Network De… Liubing (Leo)
- Re: [Nmlrg] Using Machine Learning for Network De… Sheng Jiang
- Re: [Nmlrg] Using Machine Learning for Network De… Liubing (Leo)
- Re: [Nmlrg] Machine Learning in network - solicit… Dacheng Zhang
- Re: [Nmlrg] Machine Learning in network - solicit… Sheng Jiang
- Re: [Nmlrg] Machine Learning in network - solicit… Brian E Carpenter
- Re: [Nmlrg] Machine Learning in network - solicit… Dacheng Zhang
- Re: [Nmlrg] Machine Learning in network - solicit… Dacheng Zhang
- Re: [Nmlrg] Machine Learning in network - solicit… Sheng Jiang
- Re: [Nmlrg] Machine Learning in network - solicit… Brian E Carpenter
- Re: [Nmlrg] Machine Learning in network - solicit… Sheng Jiang
- Re: [Nmlrg] Machine Learning in network - solicit… Sheng Jiang
- Re: [Nmlrg] Machine Learning in network - solicit… Liubing (Leo)
- Re: [Nmlrg] Machine Learning in network - solicit… Brian E Carpenter
- Re: [Nmlrg] Machine Learning in network - solicit… Liubing (Leo)
- Re: [Nmlrg] Machine Learning in network - solicit… Brian E Carpenter
- Re: [Nmlrg] Machine Learning in network - solicit… Liubing (Leo)
- Re: [Nmlrg] Machine Learning in network - solicit… Jérôme François
- Re: [Nmlrg] Machine Learning in network - solicit… Jérôme François
- Re: [Nmlrg] Machine Learning in network - solicit… Sheng Jiang
- Re: [Nmlrg] Machine Learning in network - solicit… Sebastian Abt
- Re: [Nmlrg] Machine Learning in network - solicit… Sebastian Abt
- Re: [Nmlrg] Machine Learning in network - solicit… Sebastian Abt
- Re: [Nmlrg] Machine Learning in network - solicit… Sebastian Abt
- Re: [Nmlrg] Machine Learning in network - solicit… Sebastian Abt
- Re: [Nmlrg] Machine Learning in network - solicit… Brian E Carpenter
- Re: [Nmlrg] Machine Learning in network - solicit… Jérôme François
- Re: [Nmlrg] Machine Learning in network - solicit… Liubing (Leo)
- Re: [Nmlrg] Machine Learning in network - solicit… Jérôme François
- Re: [Nmlrg] Machine Learning in network - solicit… Sheng Jiang
- Re: [Nmlrg] Machine Learning in network - solicit… Sheng Jiang
- Re: [Nmlrg] Machine Learning in network - solicit… Liubing (Leo)
- Re: [Nmlrg] Machine Learning in network - solicit… Sheng Jiang