Re: [Idnet] Intelligence-Defined Network Architecture and Call for Interests
Brian Njenga <iambrianmuhia@gmail.com> Tue, 28 March 2017 18:38 UTC
Return-Path: <iambrianmuhia@gmail.com>
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 649F31299D3 for <idnet@ietfa.amsl.com>; Tue, 28 Mar 2017 11:38:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 5Z58xtPQwwDr for <idnet@ietfa.amsl.com>; Tue, 28 Mar 2017 11:38:37 -0700 (PDT)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15BFF1299E8 for <idnet@ietf.org>; Tue, 28 Mar 2017 11:38:36 -0700 (PDT)
Received: by mail-oi0-x229.google.com with SMTP id o67so33930467oib.1 for <idnet@ietf.org>; Tue, 28 Mar 2017 11:38:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=n0fimOJuQLRJfgRyRS2se6okFmT3U4c7uU0/x9CXzCM=; b=RY5OkRX3Hr4W/ubIsNTnh5qe3Q7M99zQD1cNhtklTdvV1rHJsM9ZudLq+MsW75lzqs HFBOBXQcifbYLvhoLAcEjNHwkQlKFHeBBi6sShA/Q8dnPlRamNJlQ4L8NryC5uIFCoEF UOLHmTeVkfurg6yEH67QO4udj9SM8RH4haCl6pNBb4JNdDpqW8pTthUoemsWN9yfbBfP O9GJejL/kfyyjRRqyZrwdR80X/G7fBd+BFnVPf00m1wgKVTbTLA2n+SVddvp+fxY6a9A 77OYPhS/fl4ggrpw3GlR8K+cv8aE8PtVq3L9bK/lWsuzkTb9XAoR94NJbhKGagJf6RE+ LtOA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=n0fimOJuQLRJfgRyRS2se6okFmT3U4c7uU0/x9CXzCM=; b=eCvBScLab8m27tSXY2cGnk9q44jRlsYQUd/leC1jvv4u8Q5dg95MBjlDZ5SnQNOM6g GfvUrmj4Y6ezSm5zRsjR08nXPh5kBgooEjcN6SkWE8mFuDIApz0wmKSGblRyR42nIrdt VjiKyjJLd/tNHxjFbKEq7V9E7okZjV1EVBcMrpc+DNIIPc6Hle9hVhkf8QeSG6TeYPlL hphrqiKgfA5aytkQ/0K5aBd0+p/eFWw3QKdXclURDDGe5qjh1sRypseij6tlLYfrrnTQ ZPzi0k6Opaws5E5cmw+wjugT3kisBQl+WQ2XbB/8X4IcitlSDUALV7L8EIqT0vYlGg2r PvTg==
X-Gm-Message-State: AFeK/H0oMrzbn+a+B73eE/o/YibdAunFk7kZZduAw+p0VTLyr22Jo5MJdtV9nULKymF+KCvQiRVLQUzpi8TB9g==
X-Received: by 10.202.225.11 with SMTP id y11mr199528oig.66.1490726310375; Tue, 28 Mar 2017 11:38:30 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <f4a0ef2b-bba1-8b02-ba63-b119438fc13e@inria.fr>
From: Brian Njenga <iambrianmuhia@gmail.com>
Date: Tue, 28 Mar 2017 18:38:20 +0000
Message-ID: <CAAAu=jytqiHmL17z_x6828Jy5YZegV=sJ_RrS0uTsNnSZZr7cg@mail.gmail.com>
To: Jérôme François <jerome.francois@inria.fr>, Oscar Mauricio Caicedo Rendon <omcaicedo@unicauca.edu.co>, Sheng Jiang <jiangsheng@huawei.com>
Cc: "idnet@ietf.org" <idnet@ietf.org>
Content-Type: multipart/alternative; boundary="001a113ce25c2ff588054bcec4c0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idnet/xL-qbA_CLwRKp2lHNSnrf655vqQ>
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 18:38:40 -0000
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> wrote: > Hi, > > > Le 28/03/2017 à 20:06, Brian Njenga a écrit : > > 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). > > 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. > > jerome > > > Thanks, and I'm glad to meet you all. > > Best regards, > Brian Muhia. > > On Tue, 28 Mar 2017, 20:02 Oscar Mauricio Caicedo Rendon, < > omcaicedo@unicauca.edu.co> wrote: > > Hi, all, > > If there is a meeting, I would like to participate remotely. > > Best regards, > > Oscar > > On Tue, Mar 28, 2017 at 11:29 AM, Sheng Jiang <jiangsheng@huawei.com> > wrote: > > Hi, all, > > 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. > > > https://www.ietf.org/proceedings/97/slides/slides-97-nmlrg-intelligence-defined-network-01.pdf > > 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 . 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. > > FYI, we have already working on a Work Item, called IDN in the ETSI NGP > (Next Generation Protocol) ISG, links below. > > https://portal.etsi.org/tb.aspx?tbid=844&SubTB=844 > https://portal.etsi.org/webapp/WorkProgram/Report_WorkItem.asp?WKI_ID=51011 > > Meanwhile, please do use this mail list as a forum to discuss any topics > that may applying AI/ML into network area. > > Best regards, > > Sheng > _______________________________________________ > IDNET mailing list > IDNET@ietf.org > https://www.ietf.org/mailman/listinfo/idnet > > > > > -- > *Oscar Mauricio Caicedo Rendón* > *PhD Computer Science - Federal University of Rio Grande do Sul* > *Full Profesor - University of Cauca* > > ------------------------------ > * Universidad del Cauca: Comprometidos con la calidad. * > _______________________________________________ > IDNET mailing list > IDNET@ietf.org > https://www.ietf.org/mailman/listinfo/idnet > > -- > Some say he really tries to learn efficiently. > > > _______________________________________________ > IDNET mailing listIDNET@ietf.orghttps://www.ietf.org/mailman/listinfo/idnet > > > -- Some say he really tries to learn efficiently.
- 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