Re: [Idnet] Architecture and standard opportunities of IDN

yanshen <yanshen@huawei.com> Mon, 31 July 2017 13:15 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 66EA0132016 for <idnet@ietfa.amsl.com>; Mon, 31 Jul 2017 06:15:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.664
X-Spam-Level:
X-Spam-Status: No, score=-3.664 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_RATIO_04=0.556, HTML_MESSAGE=0.001, 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 YrAk_5Crwzdb for <idnet@ietfa.amsl.com>; Mon, 31 Jul 2017 06:15:52 -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 3B325132293 for <idnet@ietf.org>; Mon, 31 Jul 2017 06:15:49 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml709-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DLQ23276; Mon, 31 Jul 2017 13:15:46 +0000 (GMT)
Received: from DGGEMM405-HUB.china.huawei.com (10.3.20.213) by lhreml709-cah.china.huawei.com (10.201.108.32) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 31 Jul 2017 14:15:46 +0100
Received: from DGGEMM505-MBS.china.huawei.com ([169.254.2.173]) by DGGEMM405-HUB.china.huawei.com ([10.3.20.213]) with mapi id 14.03.0301.000; Mon, 31 Jul 2017 21:15:25 +0800
From: yanshen <yanshen@huawei.com>
To: =?utf-8?B?6rmA66+87ISd?= <mskim16@etri.re.kr>, Pedro Martinez-Julia <pedro@nict.go.jp>
CC: "idnet@ietf.org" <idnet@ietf.org>
Thread-Topic: Architecture and standard opportunities of IDN
Thread-Index: AdMGA6fVfWTKGPKySXypIgnjpRC5HgDmjdFxABe1v5A=
Date: Mon, 31 Jul 2017 13:15:24 +0000
Message-ID: <6AE399511121AB42A34ACEF7BF25B4D2979CD3@DGGEMM505-MBS.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B927CE3A673@NKGEML515-MBX.china.huawei.com> <5BC916BD50F92F45870ABA46212CB29C019C145D@SMTP1.etri.info>
In-Reply-To: <5BC916BD50F92F45870ABA46212CB29C019C145D@SMTP1.etri.info>
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/related; boundary="_004_6AE399511121AB42A34ACEF7BF25B4D2979CD3DGGEMM505MBSchina_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090204.597F2D83.0112, 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: 0e17801ecf48b6a58db91c7a8c862c3e
Archived-At: <https://mailarchive.ietf.org/arch/msg/idnet/L1kSlyEFJLVWQ6VUnbhNajnuYPE>
Subject: Re: [Idnet] Architecture and standard opportunities of IDN
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, 31 Jul 2017 13:15:57 -0000

Dear Kim,

May you have seen that we have a consensus on the potential standardization point of data and data format.

In your experience, what the structure or feature that ML-based algorithm potentially tend to? If we have a consensus and full view in this question, the data structure may be clear.

For example, if we want to train a model with QoS data (or reward). Assume that these data can be captured via some method. Some following key characters of data structure may be needed:

-          QoS data, such as delay. It may be organized with time series/quantized (the “reward”) / ...

-          Starting-ending time. It is significant and should be differentiated.

-          Time interval. We can capture the delay values in different frequency. High frequency time series delay value may be “down-sampled” when it is used in training low frequency model.

-          Source-destination. Obviously.

-          TBD

Any other keys?

Yansen

From: 김민석 [mailto:mskim16@etri.re.kr]
Sent: Monday, July 31, 2017 10:06 AM
To: Sheng Jiang <jiangsheng@huawei.com>om>; idnet@ietf.org
Cc: yanshen <yanshen@huawei.com>
Subject: RE: Architecture and standard opportunities of IDN


Dear Sheng,



Thank  you for giving us last IDNET side-meeting in Prague.

Many guys mentioned data-set problems in the IDN archetecture, so I strongly agree with these kinds of opinions.

BUT, we should carefully consider a ML-based algorithm set-up for Reinforcement Learning (RL) that you described in the other slide. Reward is one of the components in RL algorithm so that we should take all of the options of RL into consideration, such as which action we can take in the loop, which state should be optimized for reward, how policy will cover and dominate for learning process.



I submitted and presented our related internet draft based on RL in NMRG, Prague so that it might help to figure out more specifically. Hopefully. we are additionally able to discuss related RL setting-up more by email discussion or next meeting.



Best,


Min-Suk Kim

Senior Researcher / Ph.D.




________________________________
보낸 사람 : "Sheng Jiang" <jiangsheng@huawei.com<mailto:jiangsheng@huawei.com>>
보낸 날짜 : 2017-07-26 20:38:50 ( +0900 )
받는 사람 : idnet@ietf.org<mailto:idnet@ietf.org> <idnet@ietf.org<mailto:idnet@ietf.org>>
참조 : yanshen <yanshen@huawei.com<mailto:yanshen@huawei.com>>
제목 : [Idnet] Architecture and standard opportunities of IDN


Hi, all,

Please find the below figure that I shared in the IDN discussion meeting last week in Prague. This illustrates the IDN architecture in a very generic way. The on-site participants had the very similar understanding that the upper left box – the unified and selected data is should be the prior work towards standardization. Also, the participants shared the same opinion that the data structure may be various among use cases. So, we should keep discussing on use cases with the target to converge on one or two significant and specific use cases.
[cid:image001.png@01D30A40.BAD87910]

Regards,

Sheng