Re: [Idnet] IETF99 for applying AI/ML into network management: Follow-up

yanshen <yanshen@huawei.com> Mon, 24 July 2017 08:44 UTC

Return-Path: <yanshen@huawei.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 CA97212EC30 for <idnet@ietfa.amsl.com>; Mon, 24 Jul 2017 01:44:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.222
X-Spam-Level:
X-Spam-Status: No, score=-4.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 4L7-QVVbpKmL for <idnet@ietfa.amsl.com>; Mon, 24 Jul 2017 01:44:12 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF275129ACD for <idnet@ietf.org>; Mon, 24 Jul 2017 01:44:10 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml708-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DLE41269; Mon, 24 Jul 2017 08:44:08 +0000 (GMT)
Received: from DGGEMM403-HUB.china.huawei.com (10.3.20.211) by lhreml708-cah.china.huawei.com (10.201.108.49) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 24 Jul 2017 09:44:08 +0100
Received: from DGGEMM505-MBS.china.huawei.com ([169.254.2.173]) by DGGEMM403-HUB.china.huawei.com ([10.3.20.211]) with mapi id 14.03.0301.000; Mon, 24 Jul 2017 16:44:00 +0800
From: yanshen <yanshen@huawei.com>
To: Pedro Martinez-Julia <pedro@nict.go.jp>
CC: "idnet@ietf.org" <idnet@ietf.org>
Thread-Topic: [Idnet] IETF99 for applying AI/ML into network management: Follow-up
Thread-Index: AQHTAXpo1/qEM484V0O2Qui8QzokZKJcb4YAgAF0xeD//5b+AIAFKOGQ
Date: Mon, 24 Jul 2017 08:44:01 +0000
Message-ID: <6AE399511121AB42A34ACEF7BF25B4D29786F4@DGGEMM505-MBS.china.huawei.com>
References: <015d4fb0-496a-a9a0-e8c5-7fcf6c52caee@inria.fr> <20170720171907.GF15832@spectre> <6AE399511121AB42A34ACEF7BF25B4D29783BD@DGGEMM505-MBS.china.huawei.com> <20170721091729.GJ15832@spectre>
In-Reply-To: <20170721091729.GJ15832@spectre>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.179.89]
Content-Type: multipart/mixed; boundary="_002_6AE399511121AB42A34ACEF7BF25B4D29786F4DGGEMM505MBSchina_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090206.5975B359.0026, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.2.173, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 73e913ab90d0f3804a58849ec5df98b7
Archived-At: <https://mailarchive.ietf.org/arch/msg/idnet/jr2_MlGDE_ESCoZQwdZ0EMoViN8>
Subject: Re: [Idnet] IETF99 for applying AI/ML into network management: Follow-up
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: Mon, 24 Jul 2017 08:44:14 -0000

Dear Pedro, 

> -----Original Message-----
> From: IDNET [mailto:idnet-bounces@ietf.org] On Behalf Of Pedro Martinez-Julia
> Sent: Friday, July 21, 2017 5:18 PM
> To: yanshen <yanshen@huawei.com>
> Cc: idnet@ietf.org
> Subject: Re: [Idnet] IETF99 for applying AI/ML into network management:
> Follow-up
> 
> Dear Yanshen,
> 
> Please find my reply below.
> 
> On Fri, Jul 21, 2017 at 08:52:33AM +0000, yanshen wrote:
> > Dear Pedro,
> >
> > Thanks for your hints. Please find some hints from my side.
> >
> > I am not sure whether you means that there should be an "interface" or
> > an "entity" between the other source data and control loop?
> 
> I'm sorry, I mean that, by definition, a "closed control loop" intends to maintain a
> particular variable within some defined values by reading it and enforcing the
> necessary actions to affect it. Any external data cannot be considered as such
> variable so they cannot be part of the closed control loop. However, it can be
> used to help controlling other variables, but it must be clearly defined how the
> external data is integrated and derived into the changes to the other variable.
> 

Indeed. So that there should be a little complement in the loops. [see the attachment]

For compatible, there may be an interface or device to "receive" the external data? 

Regards, 

Yansen


> > BTW, have you ever obtain some achievement about such point that can
> > be shared?
> 
> My results are trivial and do not shed any light to this issue and I do not try to fit
> external data into the closed control loop, I just use it to complement the control
> of the "load" variable.
> 
> > I think that since NMRG may be a probably choice, it is better to
> > explore via this thread.
> 
> So let's go that way.
> 
> > Thanks for reading.
> >
> > Regards,
> >
> > Yansen
> 
> Regards,
> Pedro
> 
> --
> Pedro Martinez-Julia
> Network Science and Convergence Device Technology Laboratory Network
> System Research Institute National Institute of Information and Communications
> Technology (NICT) 4-2-1, Nukui-Kitamachi, Koganei, Tokyo 184-8795, Japan
> Email: pedro@nict.go.jp
> ---------------------------------------------------------
> *** Entia non sunt multiplicanda praeter necessitatem ***
> 
> _______________________________________________
> IDNET mailing list
> IDNET@ietf.org
> https://www.ietf.org/mailman/listinfo/idnet