Re: [Nmlrg] Closedown of the proposed NMLRG and NMLRG mail list

"Natale, Bob" <RNATALE@mitre.org> Thu, 08 December 2016 08:10 UTC

Return-Path: <RNATALE@mitre.org>
X-Original-To: nmlrg@ietfa.amsl.com
Delivered-To: nmlrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE3C6129CC0 for <nmlrg@ietfa.amsl.com>; Thu, 8 Dec 2016 00:10:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level:
X-Spam-Status: No, score=-7.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.896] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mitre.onmicrosoft.com
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 qqOdlfMc4pXX for <nmlrg@ietfa.amsl.com>; Thu, 8 Dec 2016 00:10:22 -0800 (PST)
Received: from smtpvmsrv1.mitre.org (smtpvmsrv1.mitre.org [192.52.194.136]) by ietfa.amsl.com (Postfix) with ESMTP id 3C32C129B58 for <nmlrg@irtf.org>; Thu, 8 Dec 2016 00:10:22 -0800 (PST)
Received: from smtpvmsrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id C2E5F6C1A96; Thu, 8 Dec 2016 03:10:21 -0500 (EST)
Received: from imshyb02.MITRE.ORG (imshyb02.mitre.org [129.83.29.3]) by smtpvmsrv1.mitre.org (Postfix) with ESMTP id B4AB36C1A95; Thu, 8 Dec 2016 03:10:21 -0500 (EST)
Received: from imshyb02.MITRE.ORG (129.83.29.3) by imshyb02.MITRE.ORG (129.83.29.3) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Thu, 8 Dec 2016 03:10:21 -0500
Received: from gcc01-dm2-obe.outbound.protection.outlook.com (10.140.19.249) by imshyb02.MITRE.ORG (129.83.29.3) with Microsoft SMTP Server (TLS) id 15.0.1130.7 via Frontend Transport; Thu, 8 Dec 2016 03:10:21 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mitre.onmicrosoft.com; s=selector1-mitre-org; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=wok0b+d9C/e1o8vWZRYKkPjHILzGKCKNyKuWbPyW+5k=; b=GvjV2vXoLV6FP1j8jO/i68McRgUrRmCku4NSgLh7oUzYj3H+IPuwMfoh2pYUwVVx+8AmJaBNwgkQ3ODfW7eI+oo/K/2eNpPwg4x6QR34HEJKlAQqtap8UrQW2PLMI/yHOW7WotvwoYybVa5Djx73hw4YSwkfFZVOdg2HNnVY+0I=
Received: from CY1PR09MB0922.namprd09.prod.outlook.com (10.163.89.140) by CY1PR09MB0921.namprd09.prod.outlook.com (10.163.89.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.771.8; Thu, 8 Dec 2016 08:10:15 +0000
Received: from CY1PR09MB0922.namprd09.prod.outlook.com ([10.163.89.140]) by CY1PR09MB0922.namprd09.prod.outlook.com ([10.163.89.140]) with mapi id 15.01.0771.010; Thu, 8 Dec 2016 08:10:14 +0000
From: "Natale, Bob" <RNATALE@mitre.org>
To: Pedro Martinez-Julia <pedro@nict.go.jp>, Sheng Jiang <jiangsheng@huawei.com>
Thread-Topic: [Nmlrg] Closedown of the proposed NMLRG and NMLRG mail list
Thread-Index: AdJQ/peYmu12xrH1Tb+ozhDq6CZgawAF+6eAAAFzCoAAAiQRgAABK/Og
Date: Thu, 08 Dec 2016 08:10:14 +0000
Message-ID: <CY1PR09MB09223FF7D9846CF2165B4E92A8840@CY1PR09MB0922.namprd09.prod.outlook.com>
References: <5D36713D8A4E7348A7E10DF7437A4B927CC7230F@NKGEML515-MBX.china.huawei.com> <20161208054709.GA964@spectre> <5D36713D8A4E7348A7E10DF7437A4B927CC72423@NKGEML515-MBX.china.huawei.com> <20161208072948.GB964@spectre>
In-Reply-To: <20161208072948.GB964@spectre>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=RNATALE@mitre.org;
x-originating-ip: [192.80.55.86]
x-ms-office365-filtering-correlation-id: b92a38a9-54f7-4809-bb12-08d41f41a3d7
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:CY1PR09MB0921;
x-microsoft-exchange-diagnostics: 1; CY1PR09MB0921; 7:4KM0AUjIztTNkKgYE3b9HYk4cd6b92Hy/1P9kS0LhAwgwMtDWJRVhR6CR/8l+AXwLaPMMF17pvatM4h77Ye4AD0alRU0gXnmXJrD/viDoyOIoecWClmMJE8HekOjXQiIXAgYo6kkUep8Jcy7UVdrXtyh3vp5go7EaBmTZ+qh5J98lWJ+N8kiAXqbAmKfMMv0Hq+YTxLKMAyCZ31cj9vXGbEf3sONSA8tVGX0LD7uYICrbT3/txRUU2UktrHymHgSufrDiAFOVeUGwXpWoBA7KgiladdMSzUlYVbNIt0VbwTTa+6qXe6OXxO07rzcT96nBIsBizdyd9sg9ltc/05pD7ogka2m81n8Ry8PKAhIQHhVFm5TNPaNJiCpX3UPO5CwYhQznDxn3WQPKYqaVm57y7TA3/xJhu9eWDIGDLWgrAVQlwHaovSCPHfbBXlyXGi/ZxpqMU8ti1PnlVfb50NNqw==
x-microsoft-antispam-prvs: <CY1PR09MB09211E0C9A230046ED90F39EA8840@CY1PR09MB0921.namprd09.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(50582790962513);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026)(6041248)(20161123562025)(20161123564025)(20161123555025)(20161123560025)(20161123558021)(6072148); SRVR:CY1PR09MB0921; BCL:0; PCL:0; RULEID:; SRVR:CY1PR09MB0921;
x-forefront-prvs: 0150F3F97D
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39840400002)(39850400002)(39860400002)(39450400003)(39410400002)(189002)(252514010)(377454003)(199003)(24454002)(13464003)(377424004)(189998001)(122556002)(9686002)(39060400001)(105586002)(3846002)(102836003)(6116002)(305945005)(86362001)(7846002)(2906002)(74316002)(7736002)(6506006)(38730400001)(77096006)(68736007)(4326007)(3280700002)(92566002)(3660700001)(76576001)(5001770100001)(97736004)(5660300001)(66066001)(7696004)(561944003)(93886004)(8936002)(81166006)(33656002)(81156014)(2950100002)(106356001)(99286002)(229853002)(50986999)(8676002)(2900100001)(76176999)(54356999)(101416001); DIR:OUT; SFP:1101; SCL:1; SRVR:CY1PR09MB0921; H:CY1PR09MB0922.namprd09.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: mitre.org does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Dec 2016 08:10:14.1056 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: c620dc48-1d50-4952-8b39-df4d54d74d82
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR09MB0921
X-OriginatorOrg: mitre.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/nmlrg/uUsLzUAX8IeOb7-to3vnk0HMc_c>
Cc: "nmlrg@irtf.org" <nmlrg@irtf.org>, Albert Cabellos <albert.cabellos@gmail.com>
Subject: Re: [Nmlrg] Closedown of the proposed NMLRG and NMLRG mail list
X-BeenThere: nmlrg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Network Machine Learning Research Group <nmlrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/nmlrg>, <mailto:nmlrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nmlrg/>
List-Post: <mailto:nmlrg@irtf.org>
List-Help: <mailto:nmlrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/nmlrg>, <mailto:nmlrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Dec 2016 08:10:24 -0000

Very quick input ... won't be eloquent but I hope is reasonably intelligible:

- I agree with the value of expanding the scope to AI, writ large, possibly under a different name (but I don't shy away from the AI label myself).
- Following a path from Automation -> Autonomics -> Autonomy, where the path is bounded (i.e., Pedro's "borders") via "_instrumented_ governance" (by humans), is one way to ease fears and minimize risks.
- I agree with the need to include ontology ... mainly because that should enforce thinking up front about the kinds of reasoning operations that will facilitate trust in the borders and instrumented governance.

Avanti,
BobN

-----Original Message-----
From: nmlrg [mailto:nmlrg-bounces@irtf.org] On Behalf Of Pedro Martinez-Julia
Sent: Thursday, December 08, 2016 2:30 AM
To: Sheng Jiang <jiangsheng@huawei.com>
Cc: nmlrg@irtf.org; Albert Cabellos <albert.cabellos@gmail.com>
Subject: Re: [Nmlrg] Closedown of the proposed NMLRG and NMLRG mail list

On Thu, Dec 08, 2016 at 06:28:43AM +0000, Sheng Jiang wrote:
> Hi, Pedro,

Hi,

> I fully agree that AI is wider than ML although it is more difficult 
> to give a definition or border of AI technologies. We can certainly 
> extend our scope from ML to AI. On other side, our scope is actually 
> wider than network management. We also targeted autonomic network 
> controlling from the very beginning.

I was tempted to mention "network control" but, from my point of view, management is a broader term that can somehow include control. I agree that Autonomic Networking (AN) would be a direct beneficiary of AI, and therefore it gives more sense to the extended scope of the group.

Regarding the definition and border, from my point of view, they would be naturally derived from the specific application of AI techniques to network control and management. In fact, if we start defining the set of concepts and relations I mentioned (more specifically, an ontology), it would be clear where to establish the specific borders. However, almost any AI technique could be useful in this context.

On the other hand, and maybe a bit against my own proposal, we have to face the concerns (fears?) that many people have about AI mechanisms taking decisions autonomously. We can begin with the definition of some deployment plan (better name, please) that incrementally gives autonomy to the final system, together with a set of rules (standard?) that must be set to every AI-based management and control system. As a note, it can follow the steps of the autonomous cars that are already being left driving alone, also taking into account and learning from their flaws and problems.

Finally, if many group members agree on extending the scope to AI, it would be good to begin right now, with the creation of the new mailing list, and (of course) set a proper name to it :-D.

Let's be in contact.

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

_______________________________________________
nmlrg mailing list
nmlrg@irtf.org
https://www.irtf.org/mailman/listinfo/nmlrg