Re: [nmrg] New Version Notification for draft-li-nmrg-intent-classification-02.txt

Olga Havel <olga.havel@huawei.com> Thu, 21 November 2019 13:34 UTC

Return-Path: <olga.havel@huawei.com>
X-Original-To: nmrg@ietfa.amsl.com
Delivered-To: nmrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAA9F120863 for <nmrg@ietfa.amsl.com>; Thu, 21 Nov 2019 05:34:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 hSVQL5bubwAo for <nmrg@ietfa.amsl.com>; Thu, 21 Nov 2019 05:34:02 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1810312083C for <nmrg@irtf.org>; Thu, 21 Nov 2019 05:34:02 -0800 (PST)
Received: from lhreml708-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id C66E0C34C85E6E628690; Thu, 21 Nov 2019 13:33:59 +0000 (GMT)
Received: from fraeml704-chm.china.huawei.com (10.206.15.53) by lhreml708-cah.china.huawei.com (10.201.108.49) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 21 Nov 2019 13:33:55 +0000
Received: from fraeml706-chm.china.huawei.com (10.206.15.55) by fraeml704-chm.china.huawei.com (10.206.15.53) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Thu, 21 Nov 2019 14:33:54 +0100
Received: from fraeml706-chm.china.huawei.com ([10.206.112.184]) by fraeml706-chm.china.huawei.com ([10.206.112.184]) with mapi id 15.01.1713.004; Thu, 21 Nov 2019 14:33:54 +0100
From: Olga Havel <olga.havel@huawei.com>
To: 孙雪媛 <sunxy11@chinatelecom.cn>, "nmrg@irtf.org" <nmrg@irtf.org>, "Liushucheng (Will Liu)" <liushucheng@huawei.com>
CC: "draft-li-nmrg-intent-classification@ietf.org" <draft-li-nmrg-intent-classification@ietf.org>
Thread-Topic: [nmrg] New Version Notification for draft-li-nmrg-intent-classification-02.txt
Thread-Index: AdWeGk5mqiBD3UkURBmor0qB5c9oFgCJuUtHAAmmF3A=
Date: Thu, 21 Nov 2019 13:33:54 +0000
Message-ID: <937482347df542b6bef548ea37d247af@huawei.com>
References: <2da6212a5b1e4da89bb09572bcc85659@huawei.com> <2019112115562968203521@chinatelecom.cn>
In-Reply-To: <2019112115562968203521@chinatelecom.cn>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.206.138.163]
Content-Type: multipart/alternative; boundary="_000_937482347df542b6bef548ea37d247afhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/nmrg/85PPmRuvCkZhHvVzBScrj8KUJhQ>
Subject: Re: [nmrg] New Version Notification for draft-li-nmrg-intent-classification-02.txt
X-BeenThere: nmrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Network Management Research Group discussion list <nmrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/nmrg>, <mailto:nmrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nmrg/>
List-Post: <mailto:nmrg@irtf.org>
List-Help: <mailto:nmrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/nmrg>, <mailto:nmrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Nov 2019 13:34:06 -0000

Hi Xueyuan Sun,

Thank you very much for your comments.

This current table was for classification of user intents, independent of how they are implemented  (ML/AI used or not during intent translation/closed-loop/security). But it is a great suggestion to add more info to Chapter 5 that would link with Section 7. In that case I would suggest that we move Section 5 after Section 7. The following are some things that come to my mind, please let me know what you think about them.


1.       We can add new categories / sub-categories to the existing tables:

a)      Related to the first part of Section 7. Add category mentioned in regards to intent: goal intent versus policy intent.

b)      Related to the second part of Section 7. Add category for how intents are realized in regards to ML/AI techniques: AI used in realization (YES/NO): AI for security, AI for intent translation, AI for adaptive adjustment

c)       Related to the third part of Section 7. Add a new category or sub-category (maybe to abstraction category– technical with feedback (human) / non-technical (human) / machine) that specifically mentions resulting actions determine by AI control modules

d)      Related to the forth part of Section 7. Do we utilize ML/AI to classify intents, maybe we can add new sub-category to lifecycle (intent discovery – automatic intent classification via AI), which would mean that intent categories would be determined / recommended by AI.

e)      Related to Intent Translation definition in Section 7? Please let me know what category you would suggest if you want to relate it just to intent translation?  Please suggest if you think your suggestion has not be covered by 1a) to 1d).



2.       Another option is that instead of adding some categories / sub-categories in the existing tables, we add a section 5.4 that would focuses on the classification based on adoption of different AI/ML approaches / techniques in
different stages of intent implementation on the network. I believe this approach may bring the most value. We could include 1a) to 1e) and we do not need to split between different solutions and intent users, as classification would be more focused on how intents are implemented in regards to adoption of AI/ML, independent of solutions, intent users and intent types.

Best Regards,
Olga


From: 孙雪媛 [mailto:sunxy11@chinatelecom.cn]
Sent: Thursday 21 November 2019 07:57
To: Olga Havel <olga.havel@huawei.com>; nmrg@irtf.org; Liushucheng (Will Liu) <liushucheng@huawei.com>
Cc: draft-li-nmrg-intent-classification@ietf.org
Subject: Re: [nmrg] New Version Notification for draft-li-nmrg-intent-classification-02.txt

Hi Olga,
I noticed that the draft has been added intent classification table in section five. Is there a consideration for adding  the correspondence between the content of the section five  and the description of the intention translation of AI in section seven? I think this would make the draft more complete.

Best Regards,
Xueyuan SUN

________________________________
Xueyuan Sun
China Telecom Strategy and Innovation Research Institute
Email:sunxy11@chinatelecom.cn<mailto:sunxy11@chinatelecom.cn>
Tel: +86-10-50902887
Mobile: +86-17316269362


==============================
孙雪媛
中国电信战略与创新研究院
Tel:010-50902887/ 17316269362
Email:sunxy11@chinatelecom.cn<mailto:sunxy11@chinatelecom.cn>

From: Olga Havel<mailto:olga.havel@huawei.com>
Date: 2019-11-18 22:22
To: nmrg@irtf.org<mailto:nmrg@irtf.org>
CC: draft-li-nmrg-intent-classification@ietf.org<mailto:draft-li-nmrg-intent-classification@ietf.org>
Subject: [nmrg] New Version Notification for draft-li-nmrg-intent-classification-02.txt

Hi,


We’ve just uploaded 02 version of intent classification draft (https://www.ietf.org/internet-drafts/draft-li-nmrg-intent-classification-02.txt) according to the comments in the list and offline discussions.



Updates from previous version from July:
1.                   Addressed Brain’s comments about “Adding solid use cases”. Addressed by adding use cases in section 3.2.
2.                   Addressed Diego’s comments about “Provide a framework for further intent evolution”.  Addressed by adding a new draft: draft-sun-nmrg-intent-framework-00
3.                   Addressed Laurent’s comments “Suggest to use parameter/classification table to do classification”. Addressed by adding the whole Section 5 with classification tables for Carrier, DC and Enterprise.
4.                   Addressed comments from Ericsson “Classify based on granularity is not accurate, may change granularity to abstraction of service description”. Addressed by changing Section 4.2 from Granularity Section to Feedback Section and adding column Abstraction to the classification table.
5.                   Chapters 5 and 6 became 6 and 7, as a result of adding new chapter 5
6.                   Section 7: Added explanation about AI related content
7.                   Moved the sections of Policy Continuum and AI after the section for Intent Classification Table
8.                   Updated contributors
9.                   Fixed document format and typos



Your comments and contributions are welcome!.


Best Regards,
Olga