Re: [Idnet] Benefits of Introducing AI into Network

Javier Antich Romaguera <jantich@juniper.net> Thu, 11 May 2017 22:40 UTC

Return-Path: <jantich@juniper.net>
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 7E22112EC67 for <idnet@ietfa.amsl.com>; Thu, 11 May 2017 15:40:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level:
X-Spam-Status: No, score=-2.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=juniper.net
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 mfEytioRMCPf for <idnet@ietfa.amsl.com>; Thu, 11 May 2017 15:40:49 -0700 (PDT)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0097.outbound.protection.outlook.com [104.47.36.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57D8F12F26D for <idnet@ietf.org>; Thu, 11 May 2017 15:35:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=8dBuSoqPD9LJVD7xpVcGh9IFlArCbje7vtfsJnc3RDY=; b=cg+3Q1oW4IjHQM+8maNA/cqjkANiNi1ObGnCUeRPiGVGdA3V34cOsTLTwoYimbYKZMWJpHDSl74q+Zw1sR3znvNJlhxMcCEF2zFdnSSzNapzqr0xlzVxikd1SMrfIYGjRNdyGKWNJA008WlyPALr1DKwPbpv6V1cBWNu2J/s9Zc=
Received: from CY1PR0501MB1115.namprd05.prod.outlook.com (10.160.144.145) by CY1PR0501MB1114.namprd05.prod.outlook.com (10.160.144.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1084.7; Thu, 11 May 2017 22:35:21 +0000
Received: from CY1PR0501MB1115.namprd05.prod.outlook.com ([10.160.144.145]) by CY1PR0501MB1115.namprd05.prod.outlook.com ([10.160.144.145]) with mapi id 15.01.1084.020; Thu, 11 May 2017 22:35:20 +0000
From: Javier Antich Romaguera <jantich@juniper.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Fang, Luyuan" <lufang@ebay.com>, Sheng Jiang <jiangsheng@huawei.com>, "idnet@ietf.org" <idnet@ietf.org>
Thread-Topic: [Idnet] Benefits of Introducing AI into Network
Thread-Index: AQHSyVZaTGXqFLUbRgO5S4jI02SJ/qHuWyeAgAGBb4A=
Date: Thu, 11 May 2017 22:35:20 +0000
Message-ID: <7D1D8481-335B-4F91-B96D-A50B1F75ECA4@juniper.net>
References: <D9F58892-34F2-4C7C-9A75-6C21B512F6B0@ebay.com> <3e15e008-f2ae-951d-7b2c-7ada800a075d@gmail.com>
In-Reply-To: <3e15e008-f2ae-951d-7b2c-7ada800a075d@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/0.0.0.151206
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=juniper.net;
x-originating-ip: [66.129.239.15]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY1PR0501MB1114; 7:Avh34+8/KaQhsadOkcm08X1Ho/rhqHlpp4LWuUqO8pKJVcuRynMynxRMdLWyAFKNbwpHrsEUyK5auScQTnML/I4+/CJx/a+snJ/68QCXbRuitjSDQx2u8S8P0I277cTRA7I2fEpHAVIBSatUHh1inLOdx/TqsH/dk38CM0wrbp7P1ms233ARyPM02W7CWVhHLs5AMkmIHo8JakkisOwkgvBzky5hkMtVqwzX2Qh144SjJlLQHsjqpLmWCIWO26oj+le3d+WuxazBQk+/pzPdywYQD2gERtZlJR6albOdltKl6xDAwFzCJa2JdvfK6XKnFuGoZKuFkABT9J4DLvRRxQ==
x-ms-office365-filtering-correlation-id: 899fa049-6c91-4bcc-564a-08d498be01bd
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081); SRVR:CY1PR0501MB1114;
x-microsoft-antispam-prvs: <CY1PR0501MB1114B177C67039D42481D666A7ED0@CY1PR0501MB1114.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(55715876382637)(138986009662008)(50582790962513);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700036)(100105000095)(100000701036)(100105300095)(100000702036)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(100000703036)(100105400095)(3002001)(10201501046)(93006095)(93001095)(6055026)(6041248)(20161123564025)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123558100)(20161123560025)(6072148)(100000704036)(100105200095)(100000705036)(100105500095); SRVR:CY1PR0501MB1114; BCL:0; PCL:0; RULEID:(100000800036)(100110000095)(100000801036)(100110300095)(100000802036)(100110100095)(100000803036)(100110400095)(100000804036)(100110200095)(100000805036)(100110500095); SRVR:CY1PR0501MB1114;
x-forefront-prvs: 0304E36CA3
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39400400002)(39840400002)(39850400002)(39450400003)(39860400002)(39410400002)(24454002)(252514010)(377454003)(6246003)(7906003)(8936002)(53546009)(478600001)(8676002)(81166006)(33656002)(3846002)(25786009)(189998001)(2501003)(102836003)(6116002)(83716003)(68736007)(86362001)(82746002)(83506001)(122556002)(2950100002)(7736002)(6486002)(5660300001)(50986999)(76176999)(3660700001)(54356999)(2900100001)(66066001)(99286003)(6506006)(54896002)(6306002)(53936002)(6436002)(4001350100001)(77096006)(3280700002)(2906002)(38730400002)(6512007)(36756003)(39060400002)(236005)(229853002)(606005); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0501MB1114; H:CY1PR0501MB1115.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_7D1D8481335B4F91B96DA50B1F75ECA4junipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 May 2017 22:35:20.4554 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0501MB1114
Archived-At: <https://mailarchive.ietf.org/arch/msg/idnet/3xYkVk8f2yGjiOzPkX_FEFuTYK8>
Subject: Re: [Idnet] Benefits of Introducing AI into Network
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, 11 May 2017 22:40:54 -0000

>>Let's take a specific example: the CASM work in the IETF. One approach to massive scale support of address and prefix management is a massive centralised database and an old-fashioned (NETCONF/YANG style) mechanism to push allocations out into the network. Another approach is a large set of distributed autonomic prefix managers that request new space from a distributed address pool when necessary. The second one is definitely a target for machine learning, in order to set optimal parameters for the individual prefix managers.

I´m sorry, but what is the relationship between something being centralized or distributed and using or not a mechanism like Netconf using YANG models to communicate certain information (in this case prefixes or addresses)? They are entirely orthogonal. Wherever you do your processing (centralized or distributed) or your storage (centralized or distributed) you still need a mechanism to model your data (YANG or other) and a mechanism to encode and transport your data (Netconf or other). Not sure what exactly is old-fashioned on Netconf/YANG for this purposes discussion, and what is has to do with using AI or not.

Thanks
Javier.
______________________________________________
Javier Antich Romaguera
Product Line Manager. JUNOS Team.
Juniper Networks
email: jantich@juniper.net<mailto:jantich@juniper.net>
m. +34639218428
“Achieving the difficult, trying the impossible"


From: IDNET <idnet-bounces@ietf.org<mailto:idnet-bounces@ietf.org>> on behalf of Brian E Carpenter <brian.e.carpenter@gmail.com<mailto:brian.e.carpenter@gmail.com>>
Organization: University of Auckland
Date: Thursday, May 11, 2017 at 3:35 AM
To: "Fang, Luyuan" <lufang@ebay.com<mailto:lufang@ebay.com>>, Sheng Jiang <jiangsheng@huawei.com<mailto:jiangsheng@huawei.com>>, "idnet@ietf.org<mailto:idnet@ietf.org>" <idnet@ietf.org<mailto:idnet@ietf.org>>
Subject: Re: [Idnet] Benefits of Introducing AI into Network

On 10/05/2017 18:26, Fang, Luyuan wrote:
I think what is driving all these points is scale. Without intelligence, very large scale networks simply become unmanageable,

I am not sure that statement is always true. It is safe to say that without *distributed solutions*, very large scale networks become unmanageable, and AI technologies can be used to support distributed solutions.

Let's take a specific example: the CASM work in the IETF. One approach to massive scale support of address and prefix management is a massive centralised database and an old-fashioned (NETCONF/YANG style) mechanism to push allocations out into the network. Another approach is a large set of distributed autonomic prefix managers that request new space from a distributed address pool when necessary. The second one is definitely a target for machine learning, in order to set optimal parameters for the individual prefix managers.

and cannot maintain service availability. Just adding work force would not help.

It will help where the problem can genuinely be tackled by "divide and conquer", for example where localised optimisation and localised repair can help. But when localised solutions are inadequate and traditional centralised solutions do not scale, AI can be the answer.

I would suggest to add
-          ability to manage network at scale (as 2nd point)
-          potential self-healing (after “predictive”)

Agreed.

    Brian
Thx,
Luyuan
From: IDNET <idnet-bounces@ietf.org<mailto:idnet-bounces@ietf.org>> on behalf of Sheng Jiang <jiangsheng@huawei.com<mailto:jiangsheng@huawei.com>>
Date: Tuesday, May 9, 2017 at 7:53 PM
To: "idnet@ietf.org<mailto:idnet@ietf.org>" <idnet@ietf.org<mailto:idnet@ietf.org>>
Subject: [Idnet] Benefits of Introducing AI into Network
In ETSI NGP ISP, we have an Work Item for IDN (Intelligence-Defined Network). In one of the general sections, We briefly describes the benefits of introducing AI into network, as below.
-          Towards Fully Autonomic Network
-          Ability of Handling Complex Issues
-          More Adaptive and Flex
-          Predictive
-          Potential Self-Evolving Ability
-          Potential Decision Efficiency
If there are major benefits that we have not covered, we would like to include.
Regards,
Sheng
_______________________________________________
IDNET mailing list
IDNET@ietf.org<mailto:IDNET@ietf.org>
https://www.ietf.org/mailman/listinfo/idnet

_______________________________________________
IDNET mailing list
IDNET@ietf.org<mailto:IDNET@ietf.org>
https://www.ietf.org/mailman/listinfo/idnet