Re: [Idnet] Architecture and standard opportunities of IDN

김민석 <> Mon, 31 July 2017 02:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1C2B5131919 for <>; Sun, 30 Jul 2017 19:06:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.463
X-Spam-Status: No, score=-1.463 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_RATIO_02=0.437, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id jZKNBjWYYlqk for <>; Sun, 30 Jul 2017 19:06:19 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 54642129AD1 for <>; Sun, 30 Jul 2017 19:06:18 -0700 (PDT)
Received: from unknown (HELO ( by with ESMTP; 31 Jul 2017 11:06:13 +0900
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 31 Jul 2017 11:06:13 +0900
Received: from ([]) by ([]) with mapi id 14.03.0319.002; Mon, 31 Jul 2017 11:06:12 +0900
From: =?utf-8?B?6rmA66+87ISd?= <>
To: Sheng Jiang <>, "" <>
CC: yanshen <>
Thread-Topic: Architecture and standard opportunities of IDN
Thread-Index: AdMGA6fVfWTKGPKySXypIgnjpRC5HgDmjdFx
Date: Mon, 31 Jul 2017 02:06:12 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: ko-KR, en-US
Content-Language: ko-KR
X-MS-Has-Attach: yes
x-originating-ip: []
Content-Type: multipart/related; boundary="_004_5BC916BD50F92F45870ABA46212CB29C019C145DSMTP1etriinfo_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [Idnet] Architecture and standard opportunities of IDN
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "The IDNet \(Intelligence-Defined Network\) " <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 31 Jul 2017 02:06:21 -0000

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.


Min-Suk Kim

Senior Researcher / Ph.D.

보낸 사람 : "Sheng Jiang" <>
보낸 날짜 : 2017-07-26 20:38:50 ( +0900 )
받는 사람 : <>
참조 : yanshen <>
제목 : [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.