Re: [Idnet] Intelligence-Defined Network Architecture and Call for Interests

Pedro Martinez-Julia <pedro@nict.go.jp> Tue, 28 March 2017 18:25 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 2A9A1129893 for <idnet@ietfa.amsl.com>; Tue, 28 Mar 2017 11:25:46 -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 We5gLVdvNhM4 for <idnet@ietfa.amsl.com>; Tue, 28 Mar 2017 11:25:44 -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 5B9241299CD for <idnet@ietf.org>; Tue, 28 Mar 2017 11:25:38 -0700 (PDT)
Received: from gw2.nict.go.jp (gw2.nict.go.jp [133.243.18.251]) by ns2.nict.go.jp with ESMTP id v2SIPbwg029333 for <idnet@ietf.org>; Wed, 29 Mar 2017 03:25:37 +0900 (JST)
Received: from mail1.nict.go.jp (mail1.nict.go.jp [133.243.18.14]) by gw2.nict.go.jp with ESMTP id v2SIPbYp029270 for <idnet@ietf.org>; Wed, 29 Mar 2017 03:25:37 +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 C2596A114 for <idnet@ietf.org>; Wed, 29 Mar 2017 03:25:36 +0900 (JST)
Date: Wed, 29 Mar 2017 03:25:30 +0900
From: Pedro Martinez-Julia <pedro@nict.go.jp>
To: idnet@ietf.org
Message-ID: <20170328182530.GP4808@spectre>
References: <5D36713D8A4E7348A7E10DF7437A4B927CD15A18@NKGEML515-MBS.china.huawei.com> <CAHiKxWgT3hKr2VwhbfpmR_siHgiY4PbiKy3QgesG7uqUTnedmw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CAHiKxWgT3hKr2VwhbfpmR_siHgiY4PbiKy3QgesG7uqUTnedmw@mail.gmail.com>
User-Agent: Mutt/1.8.0 (2017-02-23)
X-Virus-Scanned: clamav-milter 0.98.7 at zenith2
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/idnet/OzAQAlIexV3OvCQ0NGfByVo0ASo>
Subject: Re: [Idnet] Intelligence-Defined Network Architecture and Call for Interests
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, 28 Mar 2017 18:25:46 -0000

On Tue, Mar 28, 2017 at 10:59:38AM -0700, David Meyer wrote:
> Hey Sheng,
> 
> I just wanted to revive my key concern on [0] (same one I made at the
> NMRL): The hard parts of getting Machine Learning intelligence into
> Networking is the Machine Learning part. In addition, successful deployment
> of ML requires knowledge of ML combined with domain knowledge. We
> definitely have the domain knowledge; the problem is that we don't have the
> ML knowledge, and this is one of the big factors holding us back; see e.g.
> Andrew's discussion of talent in [1].  Slides such as [0] seem to imply
> that *someone else* (in particular, not us)  will handle the ML part of all
> of this. I'll just note that in general successful deployments of ML don't
> work this way; the domain experts will have to learn ML (and vice versa)
> for us to be successful (again, see [1] and many others).

Dear Dave,

You are true in that ML/domain knowledge is necessary but, however it is
worth to take into account that it is not strictly required and it will
even be counterproductive in some (or maybe most) situations. At the end
of the day, encouraging (or forcing) a network expert to learn ML is
quite difficult, the results will be delayed until the learning phase
ends, and (most probably) s/he will never get a better solution than a
person that has been an expert in ML from a long time ago. Therefore, it
is better to make separate experts (in ML and the domain itself) to
collaborate in a common solution. Therefore, and I think it has been
mentioned before, we have to (try to) enroll experts in ML to the IDNET
group and see what can we do together...

> Perhaps a useful exercise would be to write an ID that makes your
> assumptions explicit?
> 
> Thanks,
> Dave

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