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

Sheng Jiang <jiangsheng@huawei.com> Thu, 27 July 2017 11:26 UTC

Return-Path: <jiangsheng@huawei.com>
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 E3AEA131FD9 for <idnet@ietfa.amsl.com>; Thu, 27 Jul 2017 04:26:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 IZzBXsLLzk6u for <idnet@ietfa.amsl.com>; Thu, 27 Jul 2017 04:26:02 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 308E1131FCC for <idnet@ietf.org>; Thu, 27 Jul 2017 04:26:01 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml703-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DSD63087; Thu, 27 Jul 2017 11:25:59 +0000 (GMT)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 27 Jul 2017 12:25:58 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0235.001; Thu, 27 Jul 2017 19:25:50 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: =?iso-8859-1?Q?J=E9r=F4me_Fran=E7ois?= <jerome.francois@inria.fr>, yanshen <yanshen@huawei.com>, "idnet@ietf.org" <idnet@ietf.org>
Thread-Topic: [Idnet] IETF99 for applying AI/ML into network management: Follow-up
Thread-Index: AQHTAXpo4KCW4nTbjkWrHqBAIakpSKJdXhUAgAa8uQCAAVV4cIAAk1OAgAGEelA=
Date: Thu, 27 Jul 2017 11:25:50 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B927CE3B0F3@NKGEML515-MBX.china.huawei.com>
References: <015d4fb0-496a-a9a0-e8c5-7fcf6c52caee@inria.fr> <6AE399511121AB42A34ACEF7BF25B4D297836D@DGGEMM505-MBS.china.huawei.com> <b496321d-a1d0-9ed6-6e43-be155e1eb31f@inria.fr> <5D36713D8A4E7348A7E10DF7437A4B927CE3A581@NKGEML515-MBX.china.huawei.com> <0e18964e-3544-20dc-62b1-feb096137e87@inria.fr>
In-Reply-To: <0e18964e-3544-20dc-62b1-feb096137e87@inria.fr>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.185.119]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090205.5979CDC7.0088, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 8278677a77aa3ed625b196cca4ff8843
Archived-At: <https://mailarchive.ietf.org/arch/msg/idnet/RMDHeDVOrkM9wDIX6iOfhRukuLo>
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 11:26:04 -0000

Hi, Jerome,

I do understand your concern. One of the historic stories is that we had two NMRG sessions/workshops back to IETF 88, 89. It served us both purposes - community building and scope refinement well. Because these two sessions, we developed two RFC 7575 & 7576. It gives us good foundation to form ANIMA WG. The problem we have now is actually TOO open and wide. If we could convergent on GENERIC problem across use case, interfaces, foundation functionalities, it would be the best. If we don't know what might be GENERIC for now, we may have to deeply study various use cases, then try to find the common among them.

Regards,

Sheng

> -----Original Message-----
> From: Jérôme François [mailto:jerome.francois@inria.fr]
> Sent: Thursday, July 27, 2017 3:35 AM
> To: Sheng Jiang; yanshen; idnet@ietf.org
> Subject: Re: [Idnet] IETF99 for applying AI/ML into network management:
> Follow-up
> 
> Hi,
> 
> > Of course, we would like to target a WG if we could. However, so far, we have
> not converged at all. It seems there are full of possibilities to apply AI/ML in
> networks. It seems everybody is talking about their own use cases. Until we
> converged with one or two very specific use cases that are also generic and
> significance, or we might find some fundamental functionalities that are
> generically support various AI use cases, we may not have anything to
> standardized. So far, we are still in the way to find these work items. So, let's
> keep discussing use cases and fundamental functionalities. Hopefully, with
> more discussion, we could reduce our scope to be more and more focus. Then
> we may have concrete work items to form a WG.
> >
> >
> I agree that before formally targeting a WG, we need something specific to be
> address. I said "something" because it could be a use case where AI is applied,
> a generic problem across use case, interfaces....
> 
> But my little concern is that I would avoid that planned workshop would be
> stricly limited to particular use cases, problems or architecture.
> In my opinion, we have to take care of the two items (community building with
> the workshop and scope refinement) in parallel but we could, of course, expect
> that the workshop gives us some input to refine our target in the proper way.
> 
> jerome