Re: [Idnet] Architecture and standard opportunities of IDN

Sheng Jiang <> Tue, 01 August 2017 08:16 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 02FAA132B3B for <>; Tue, 1 Aug 2017 01:16:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.784
X-Spam-Status: No, score=-3.784 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_RATIO_02=0.437, 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] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id wwTpHtQKiFpd for <>; Tue, 1 Aug 2017 01:16:48 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CCAE4132B7F for <>; Tue, 1 Aug 2017 01:16:46 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id DLR50953; Tue, 01 Aug 2017 08:16:44 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.301.0; Tue, 1 Aug 2017 09:14:35 +0100
Received: from ([fe80::a54a:89d2:c471:ff]) by ([]) with mapi id 14.03.0235.001; Tue, 1 Aug 2017 16:14:24 +0800
From: Sheng Jiang <>
To: =?utf-8?B?6rmA66+87ISd?= <>, "" <>
CC: yanshen <>
Thread-Topic: Architecture and standard opportunities of IDN
Thread-Index: AdMGA6fVfWTKGPKySXypIgnjpRC5HgDmjdFxAD+wjUA=
Date: Tue, 1 Aug 2017 08:14:23 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: yes
x-originating-ip: []
Content-Type: multipart/related; boundary="_004_5D36713D8A4E7348A7E10DF7437A4B927CE3D850NKGEML515MBXchi_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020205.598038ED.0099, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 0e17801ecf48b6a58db91c7a8c862c3e
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: Tue, 01 Aug 2017 08:16:50 -0000

Hi, Kim,

Agree your concern regarding to Reinforcement Learning. Actually, it was just a symbol in the slide to represent machine learning in general.

The current plan, if workable, is to organize a dedicated session in NMRG, IETF100, for applying AI into network management. You are more than welcome to take part in.



From: 김민석 []
Sent: Monday, July 31, 2017 10:06 AM
To: Sheng Jiang <>om>;
Cc: yanshen <>
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.


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.