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

Pedro Martinez-Julia <pedro@nict.go.jp> Thu, 20 July 2017 17:19 UTC

Return-Path: <pedro@nict.go.jp>
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 B2AA7131C18 for <idnet@ietfa.amsl.com>; Thu, 20 Jul 2017 10:19:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Zfdm5yQ_Wqqg for <idnet@ietfa.amsl.com>; Thu, 20 Jul 2017 10:19:19 -0700 (PDT)
Received: from ns2.nict.go.jp (ns2.nict.go.jp [IPv6:2001:df0:232:300::2]) by ietfa.amsl.com (Postfix) with ESMTP id B9B60131A84 for <idnet@ietf.org>; Thu, 20 Jul 2017 10:19:18 -0700 (PDT)
Received: from gw2.nict.go.jp (gw2.nict.go.jp [133.243.18.251]) by ns2.nict.go.jp with ESMTP id v6KHJHEJ082134; Fri, 21 Jul 2017 02:19:17 +0900 (JST)
Received: from mail1.nict.go.jp (mail1.nict.go.jp [133.243.18.14]) by gw2.nict.go.jp with ESMTP id v6KHJH2Y082131; Fri, 21 Jul 2017 02:19:17 +0900 (JST)
Received: from spectre (ssh1.nict.go.jp [133.243.3.49]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail1.nict.go.jp (NICT Mail Spool Server1) with ESMTPS id 470A1B6E3; Fri, 21 Jul 2017 02:19:15 +0900 (JST)
Date: Fri, 21 Jul 2017 02:19:08 +0900
From: Pedro Martinez-Julia <pedro@nict.go.jp>
To: =?utf-8?B?SsOpcsO0bWUgRnJhbsOnb2lz?= <jerome.francois@inria.fr>
Cc: "idnet@ietf.org" <idnet@ietf.org>
Message-ID: <20170720171907.GF15832@spectre>
References: <015d4fb0-496a-a9a0-e8c5-7fcf6c52caee@inria.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <015d4fb0-496a-a9a0-e8c5-7fcf6c52caee@inria.fr>
User-Agent: Mutt/1.8.3 (2017-05-23)
X-Virus-Scanned: clamav-milter 0.98.7 at zenith2
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/idnet/iXPo7licMDDUpZsBgQVLEtu0byQ>
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: Thu, 20 Jul 2017 17:19:21 -0000

On Thu, Jul 20, 2017 at 07:05:17PM +0200, Jérôme François wrote:
> Dear all,

Dear Jerome,

Thank you very much for your comments. Please find below some hints from
my side.

> Thanks Sheng for having organized the meeting. As we are running out of
> time, here are some comments I want to share:
> - in the figure with the loop, data to be used could be from other
> sources of data out from the network to enrich the analysis

This is delicate since, strictly speaking, such data cannot form part of
the "control loop" because it is not a variable to control. However, in
a practical view it will be connected to the input of the loop (and I am
currently working on solutions that consider such information in such
point), but it must be clear that it will not form part of the closure
of the loop.

> - regarding use cases, it was unclear for me what is your or the group
> plan. I think many of us express interests for other use cases but I'm
> not sure how to contribute / select use cases (and if we have to ? ->
> see next item)

To my experience, the best option is to find some common requirements to
all use cases we are taking into account and then try to find a smaller
use case that reflects only those requirements. We can then "vote" which
aspects must be considered from the beginning and which can be left for
future use cases.

> - the immediate plan is to organize a regular workshop (probably within
> NMRG). I fully support the idea as this helps to federate the community
> first to ambition then coordinated actions (regarding the issues with
> datasets for example). But recall that that will be workshop within a RG
> group and it is probably too early to identify what should be
> standardized  (or look at a WG in that case). Looking at the experience
> with flow measurement workshop (within NMRG as well), it should be more
> open for presentations and discussions and if a potential standard is
> identified, this can be targeted afterwards.

That is nice, but has some risks. We must first set a strong topic or we
can find a too high diversion from the issues that IDNET must resolve.

I agree with you in that it is good to gather proposals to resolve the
dataset issues and it can be the main (I propose that only) topic of the
first workshop on IDNET.

Those are my 2 cents. Thanks for reading.

> Best regards,
> jerome

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 ***