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

yanshen <yanshen@huawei.com> Thu, 27 July 2017 01:59 UTC

Return-Path: <yanshen@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 AA445131F2C for <idnet@ietfa.amsl.com>; Wed, 26 Jul 2017 18:59:12 -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 d7Tqtw7L20Cp for <idnet@ietfa.amsl.com>; Wed, 26 Jul 2017 18:59:11 -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 22D8E1270AC for <idnet@ietf.org>; Wed, 26 Jul 2017 18:59:11 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DSC76581; Thu, 27 Jul 2017 01:59:09 +0000 (GMT)
Received: from DGGEMM405-HUB.china.huawei.com (10.3.20.213) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 27 Jul 2017 02:59:08 +0100
Received: from DGGEMM505-MBS.china.huawei.com ([169.254.2.173]) by DGGEMM405-HUB.china.huawei.com ([10.3.20.213]) with mapi id 14.03.0301.000; Thu, 27 Jul 2017 09:59:02 +0800
From: yanshen <yanshen@huawei.com>
To: =?iso-8859-1?Q?J=E9r=F4me_Fran=E7ois?= <jerome.francois@inria.fr>
CC: "idnet@ietf.org" <idnet@ietf.org>
Thread-Topic: [Idnet] IETF99 for applying AI/ML into network management: Follow-up
Thread-Index: AQHTAXpo1/qEM484V0O2Qui8QzokZKJd1xaAgAZDuACAAtlnEA==
Date: Thu, 27 Jul 2017 01:59:02 +0000
Message-ID: <6AE399511121AB42A34ACEF7BF25B4D2978FB3@DGGEMM505-MBS.china.huawei.com>
References: <015d4fb0-496a-a9a0-e8c5-7fcf6c52caee@inria.fr> <6AE399511121AB42A34ACEF7BF25B4D297836D@DGGEMM505-MBS.china.huawei.com> <b496321d-a1d0-9ed6-6e43-be155e1eb31f@inria.fr>
In-Reply-To: <b496321d-a1d0-9ed6-6e43-be155e1eb31f@inria.fr>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.179.89]
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.0A020201.597948ED.012B, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.2.173, 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/ia-VrmqY8VfwftfqTjT-dgcG4Hw>
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 01:59:12 -0000

Hi Jerome,

> -----Original Message-----
> From: Jérôme François [mailto:jerome.francois@inria.fr]
> Sent: Tuesday, July 25, 2017 10:26 PM
> To: yanshen <yanshen@huawei.com>om>; idnet@ietf.org
> Subject: Re: [Idnet] IETF99 for applying AI/ML into network management:
> Follow-up
> 
> Hi,
> 
> Le 21/07/2017 à 09:32, yanshen a écrit :
> > - the immediate plan is to organize a regular workshop (probably
> > within NMRG). I fully support the idea as this helps to federate the
> > community first to ambition then coordinated actions (regarding the
> > issues with datasets for example). But recall that that will be
> > workshop within a RG group and it is probably too early to identify
> > what should be standardized  (or look at a WG in that case). Looking
> > at the experience with flow measurement workshop (within NMRG as
> > well), it should be more open for presentations and discussions and if a
> potential standard is identified, this can be targeted afterwards.
> > I support the regular workshop (whatever in any form). I fully understand your
> worried about the "too early". However, I think it is better to find a common or
> say a potential standardized point to concentrate the focus. After that, we can
> expand our focus to other valuable area. A details point may help us to clear up
> the thought, during which we may evolve a clear methodology for the future
> work. Of course I totally agree with your open attitude. I mean only to
> concentrate the topic firstly.
> >
> >
> So, why not targeting a WG (rather than a RG because in my understanding
> primary focus of RG is not standardization) ?

I am troubled in finding a satisfied WG. Any suggestion? For example, in measurement area.

Thanks for your reply.

Regards,

Yansen

> 
> 
> best regards,
> jerome