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

yanshen <yanshen@huawei.com> Tue, 25 July 2017 14:11 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 0126C131CBD for <idnet@ietfa.amsl.com>; Tue, 25 Jul 2017 07:11:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 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, 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 tuz2UKnMD_0u for <idnet@ietfa.amsl.com>; Tue, 25 Jul 2017 07:11:21 -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 8D78C124217 for <idnet@ietf.org>; Tue, 25 Jul 2017 07:11:20 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML712-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DLG87562; Tue, 25 Jul 2017 14:11:18 +0000 (GMT)
Received: from DGGEMM404-HUB.china.huawei.com (10.3.20.212) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.301.0; Tue, 25 Jul 2017 15:11:17 +0100
Received: from DGGEMM505-MBS.china.huawei.com ([169.254.2.173]) by DGGEMM404-HUB.china.huawei.com ([10.3.20.212]) with mapi id 14.03.0301.000; Tue, 25 Jul 2017 22:10:27 +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//+JN4CAAiamwA==
Date: Tue, 25 Jul 2017 14:10:26 +0000
Message-ID: <6AE399511121AB42A34ACEF7BF25B4D2978A40@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> <6AE399511121AB42A34ACEF7BF25B4D29786F4@DGGEMM505-MBS.china.huawei.com> <20170724085956.GI18300@spectre>
In-Reply-To: <20170724085956.GI18300@spectre>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.109.108.52]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090202.59775186.00D0, 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/8SQKMTDJZSImYIbDiSe8jCZXcNc>
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: Tue, 25 Jul 2017 14:11:24 -0000

Dear Pedro,

Sorry for replying late. 

> -----Original Message-----
> From: Pedro Martinez-Julia [mailto:pedro@nict.go.jp]
> Sent: Monday, July 24, 2017 5:00 PM
> To: yanshen <yanshen@huawei.com>
> Cc: idnet@ietf.org
> Subject: Re: [Idnet] IETF99 for applying AI/ML into network management:
> Follow-up
> 
> On Mon, Jul 24, 2017 at 08:44:01AM +0000, yanshen wrote:
> > Dear Pedro,
> 
> Dear Yanshen,
> 
> > Indeed. So that there should be a little complement in the loops. [see
> > the attachment]
> 
> I see and I find it a perfect representation and fit for the role that external data
> would have (fed directly to the brain!).
> 

Recently I meet an interesting question is what data should belong to internal and what data should be external?

A simple case is the ML algorithm, such as reinforcement learning, needs "rewards" to  correct the error and improve its model during iterations. Some reward parameters may be from subscribers. For example, when we use the QoE value to present the reward in each period. These feedback QoE values should be internal or external? 

BTW, I think there should be some methods to support the "reward" feedback. For instance, there is some proposal to use RSVP protocol's option to transmit the QoS value. And in the scenarios of video transmission, some proposal uses TCP option to feedback the QoS of current flow. 

Maybe there is room for the future.

Thanks for your reply and suggestions.

Yansen

> > For compatible, there may be an interface or device to "receive" the
> > external data?
> 
> I think it would be nice to have such interface and standardize it so data
> producers/owners can be easily plugged to data consumers, promoting the
> proliferation of different solutions that could be exchanged and/or
> complemented to each other...
> 
> > 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 ***