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

Simone Ferlin <simone@ferlin.io> Thu, 27 July 2017 03:06 UTC

Return-Path: <simone@ferlin.io>
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 D110112711E for <idnet@ietfa.amsl.com>; Wed, 26 Jul 2017 20:06:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.31
X-Spam-Level:
X-Spam-Status: No, score=-1.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=ferlin.io
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 3nwkAhJ6CKTM for <idnet@ietfa.amsl.com>; Wed, 26 Jul 2017 20:06:25 -0700 (PDT)
Received: from n1nlsmtp03.shr.prod.ams1.secureserver.net (n1nlsmtp03.shr.prod.ams1.secureserver.net [188.121.43.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBE18124BE8 for <idnet@ietf.org>; Wed, 26 Jul 2017 20:06:24 -0700 (PDT)
Received: from n1plcpnl0047.prod.ams1.secureserver.net ([46.252.205.173]) by : HOSTING RELAY : with SMTP id aZ74dTAP92Fv0aZ74dwZCG; Wed, 26 Jul 2017 20:05:22 -0700
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ferlin.io; s=default; h=Content-Type:Cc:To:Subject:Message-ID:Date:From:References: In-Reply-To:MIME-Version:Sender:Reply-To:Content-Transfer-Encoding:Content-ID :Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To: Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe :List-Post:List-Owner:List-Archive; bh=3gX0x0pO28RdCy5nhI4yEsQoElt1EKg/TDh3u2EIH3s=; b=PLgTf5qM0lS/YBQgNwxwIxmX/s dujSCFKYKrXC6Zy0WEhdwl2WBEFkz58t8O4ga+6tSlPoMdpcGhllu9zEYOeMxhUI5R6GpL2rSx/X1 QGAtuNfMGHLiQ/E9lS68vg8AiH2bvMoZlVJfhgv5n7ICRLPQrNTMAvpPjHcxE3z3LtcNA6MaWINXg cvN7Xgpv6G6k/8CtnblL/+TGiPa4wkmH4XAW2IjH1DVzgZxwj875+jDdzUGWmbqn9wljZhSz5G4+A eqdSD/GbmqmBQI1FCNYmt24GMCupiV1TfL1AxnZn2vfWTOESfYLayzZn2p2kwxwPHDLBngQkY0TuH J14cXNvg==;
Received: from mail-pg0-f42.google.com ([74.125.83.42]:37985) by n1plcpnl0047.prod.ams1.secureserver.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.88) (envelope-from <simone@ferlin.io>) id 1daZ74-003fCF-OD for idnet@ietf.org; Wed, 26 Jul 2017 20:05:22 -0700
Received: by mail-pg0-f42.google.com with SMTP id k190so26467849pgk.5 for <idnet@ietf.org>; Wed, 26 Jul 2017 20:05:22 -0700 (PDT)
X-Gm-Message-State: AIVw110fjS9X+VzuaayciQh49KZuhyjUFl8IoZd2zZQWonY1rp/fQ4fB t3z2CfADcECs5lsKg3BTj5HioPbqQA==
X-Received: by 10.84.225.129 with SMTP id u1mr2902349plj.255.1501124721418; Wed, 26 Jul 2017 20:05:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.153.80 with HTTP; Wed, 26 Jul 2017 20:04:58 -0700 (PDT)
In-Reply-To: <20170727021622.GD18300@spectre>
References: <015d4fb0-496a-a9a0-e8c5-7fcf6c52caee@inria.fr> <20170720171907.GF15832@spectre> <6AE399511121AB42A34ACEF7BF25B4D29783BD@DGGEMM505-MBS.china.huawei.com> <20170721091729.GJ15832@spectre> <6AE399511121AB42A34ACEF7BF25B4D29786F4@DGGEMM505-MBS.china.huawei.com> <20170724085956.GI18300@spectre> <6AE399511121AB42A34ACEF7BF25B4D2978A40@DGGEMM505-MBS.china.huawei.com> <20170726002417.GZ18300@spectre> <6AE399511121AB42A34ACEF7BF25B4D2978F9C@DGGEMM505-MBS.china.huawei.com> <20170727021622.GD18300@spectre>
From: Simone Ferlin <simone@ferlin.io>
Date: Thu, 27 Jul 2017 12:04:58 +0900
X-Gmail-Original-Message-ID: <CACOM=L+C0VN_FL9WyNj0QVe0G86XfX4VUXaXjLh2rWYe1kxChA@mail.gmail.com>
Message-ID: <CACOM=L+C0VN_FL9WyNj0QVe0G86XfX4VUXaXjLh2rWYe1kxChA@mail.gmail.com>
To: Pedro Martinez-Julia <pedro@nict.go.jp>
Cc: yanshen <yanshen@huawei.com>, "idnet@ietf.org" <idnet@ietf.org>
Content-Type: text/plain; charset="UTF-8"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - n1plcpnl0047.prod.ams1.secureserver.net
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ferlin.io
X-Get-Message-Sender-Via: n1plcpnl0047.prod.ams1.secureserver.net: authenticated_id: simone@ferlin.io
X-Authenticated-Sender: n1plcpnl0047.prod.ams1.secureserver.net: simone@ferlin.io
X-Source:
X-Source-Args:
X-Source-Dir:
X-CMAE-Envelope: MS4wfFNSSyHC5Ahr+NKyHTuef4FTHxnqnFlTSuFyTNnIgAtZFDz7D4TwwE22Jn87E66PHi0Q1Mnm8M+WI6p75ADUmg3AgkMpN1wUbYrPeKswwFePNm6eTnL+ ER2Uf/DXwIYvHafXw6wNeLWU1NPhBKWPQzA9pB637I1BmApVMME9n0fasrRxXPs7vjgDVQXv2mYwBspQmII6QvmVX1xGX3jrIaE=
Archived-At: <https://mailarchive.ietf.org/arch/msg/idnet/tbHrXC0jOivthJMAHxJZ5wDB-rs>
X-Mailman-Approved-At: Wed, 26 Jul 2017 20:08:14 -0700
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, 27 Jul 2017 03:06:27 -0000

Hello everyone,

I have been following this list for some time, but I have not been in
the meetings (f2f nor online) yet due to lack of time.
Do you have a summary of these meetings, including the topics
discussed at IETF'99, so that people like me could engage in the
discussions? I see you started a thread here, but not with much I
could understand the starting point.

Thanks and cheers,
Simone

On Thu, Jul 27, 2017 at 11:16 AM, Pedro Martinez-Julia <pedro@nict.go.jp> wrote:
> Dear Yanshen,
>
> Thanks for your comments, please find my reply in-line.
>
> On Thu, Jul 27, 2017 at 01:54:58AM +0000, yanshen wrote:
>> > For me that depends on the algorithmic representation. We have two types of
>> > variables:
>> >
>> > - Measurable and controllable variables, such as the load of a resource
>> >   managed by the solution, which can be known and can be altered by some
>> >   decision of such solution (increase/decrease the amount of resources).
>> >
>> > - Measurable but non-controllable, which are outside the control of the
>> >   solution. They can be known and used to take decisions but cannot be
>> >   altered (directly or indirectly) by the solution. A simple example can
>> >   be found in the occurrence of some event that can affect to a system,
>> >   such as the number of attendees to a baseball match. The management
>> >   solution cannot control such variable but uses it to determine the
>> >   amount of network resources assigned to the network of the stadium.
>>
>> I have a similar thought. I try to divide the variables into objective
>> and subjective (may corresponding to your controllable and
>> non-controllable. Perhaps a little different).
>>
>>       - The objective data means that we can capture, input or measure it
>>       periodically from any source (whatever it is). This class of data
>>       needs to be focused and formatted, including the context and format
>>       and so on. One of the cases is QoS value which I just mentioned.
>>
>>       - The subjective data means that it is imported into the machine
>>       (AI/Brain/Knowledge system) temporarily or irregularly. This class
>>       of data may be high-level and diversity. The solution for them I
>>       think should be pushed to application layer. It is not our dishes.
>>       Another thought is that we should try to obtain more subjective data
>>       by objective way, for example, we should try to change the way of
>>       obtaining the "reward" feedback from "user randomly report" to
>>       "periodically capture". Unless such, it should not be included into
>>       our consideration.
>>
>> I think it is significant to combine our two dimensions into one. Of
>> course other dimensions may also considerable.
>
> They are different aspects and, of course, they must be combined. My
> classification is based on the "control theory", which clearly states
> what a controlled variable means and the strict definition of the loop
> closure (closed-loop controller), which implies to check such variables
> and confirm they are changed according to the intended objective after
> some change/s is/are applied to the controlled environment.
>
> On the other hand, your view is more practical in terms of the scope of
> the information in relation to the AI algorithm and its needs. It would
> be good to simplify/unify both dimensions but also to simplify/unify the
> differences within them. I mean that it would be probably a good option
> to consider any kind of data homogeneously. I am using a simple ontology
> to resolve such problem, so we could probably use it and a corresponding
> YANG model, as I proposed in my other message, to achieve such unified
> view. Please, let me know your thoughts. Thank you very much.
>
> 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 ***
>
> _______________________________________________
> IDNET mailing list
> IDNET@ietf.org
> https://www.ietf.org/mailman/listinfo/idnet