Re: [Idnet] Architecture and standard opportunities of IDN

김민석 <mskim16@etri.re.kr> Tue, 01 August 2017 09:25 UTC

Return-Path: <mskim16@etri.re.kr>
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 3EBE1132CB7 for <idnet@ietfa.amsl.com>; Tue, 1 Aug 2017 02:25:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_RATIO_06=0.001, HTML_MESSAGE=0.001, 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 frP3qH55T846 for <idnet@ietfa.amsl.com>; Tue, 1 Aug 2017 02:25:35 -0700 (PDT)
Received: from ms.etri.re.kr (mscreen.etri.re.kr [129.254.9.16]) by ietfa.amsl.com (Postfix) with ESMTP id 9416D132CB5 for <idnet@ietf.org>; Tue, 1 Aug 2017 02:25:33 -0700 (PDT)
Received: from unknown (HELO smtpeg.etri.re.kr) (129.254.27.141) by 129.254.9.16 with ESMTP; 1 Aug 2017 18:25:36 +0900
X-Original-SENDERIP: 129.254.27.141
X-Original-MAILFROM: mskim16@etri.re.kr
X-Original-RCPTTO: idnet@ietf.org, pedro@nict.go.jp, yanshen@huawei.com
Received: from SMTP5.etri.info (129.254.28.75) by SMTPEG1.etri.info (129.254.27.141) with Microsoft SMTP Server (TLS) id 14.3.319.2; Tue, 1 Aug 2017 18:25:29 +0900
Received: from SMTP1.etri.info ([169.254.1.45]) by SMTP5.etri.info ([129.254.28.75]) with mapi id 14.03.0319.002; Tue, 1 Aug 2017 18:25:27 +0900
From: =?utf-8?B?6rmA66+87ISd?= <mskim16@etri.re.kr>
To: yanshen <yanshen@huawei.com>, Pedro Martinez-Julia <pedro@nict.go.jp>
CC: "idnet@ietf.org" <idnet@ietf.org>
Thread-Topic: Architecture and standard opportunities of IDN
Thread-Index: AdMGA6fVfWTKGPKySXypIgnjpRC5HgDmjdFxABe1v5AAKO8WiA==
Date: Tue, 1 Aug 2017 09:25:26 +0000
Message-ID: <5BC916BD50F92F45870ABA46212CB29C019C4954@SMTP1.etri.info>
References: <5D36713D8A4E7348A7E10DF7437A4B927CE3A673@NKGEML515-MBX.china.huawei.com> <5BC916BD50F92F45870ABA46212CB29C019C145D@SMTP1.etri.info>, <6AE399511121AB42A34ACEF7BF25B4D2979CD3@DGGEMM505-MBS.china.huawei.com>
In-Reply-To: <6AE399511121AB42A34ACEF7BF25B4D2979CD3@DGGEMM505-MBS.china.huawei.com>
Accept-Language: ko-KR, en-US
Content-Language: ko-KR
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [129.254.28.41]
Content-Type: multipart/related; boundary="_004_5BC916BD50F92F45870ABA46212CB29C019C4954SMTP1etriinfo_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idnet/BFCzGFdQENqliARNI8J9VJoclNk>
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: Tue, 01 Aug 2017 09:25:37 -0000

Dear Yansen,


Thoes are good key points!


We firslty need to set real networking model to collect data (Qos Data), then making a scenario which component of data-set can be applied with ML algorithms such as RL, RNN and etc.

It's a little hard to consider key characters for ML-based data structure to be clear, but I can make couple of opinions to the key characters of structure in aspect of ML algorithm.


1) QoS may be convert to reward for RL, but it needs learning processing time. We can set an initial period to collect information for learning process. In general, an initial period should be defined by random process in RL. After then, the data will be continuously updated.


2) Set a policy. Policy is important points for RL. It has all of the next available values for actions so that the policy is a brain involved with opimized data.


3) We should make clear of purpose for "Source-destination". Sheng has a plan to organize a dedicated session in next NMRG meeting so it may be clear for intelligent management before establishment of ML-based data structures.


Regards,



Min-Suk Kim

Senior Researcher / Ph.D.









________________________________
보낸 사람 : "yanshen" <yanshen@huawei.com>
보낸 날짜 : 2017-07-31 22:15:37 ( +09:00 )
받는 사람 : 김민석 <mskim16@etri.re.kr>kr>, Pedro Martinez-Julia <pedro@nict.go.jp>
참조 : idnet@ietf.org <idnet@ietf.org>
제목 : RE: Architecture and standard opportunities of IDN


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