[nmrg] Alignment between the 2 drafts: New Version Notification for draft-li-nmrg-intent-classification-02.txt

Olga Havel <olga.havel@huawei.com> Fri, 06 December 2019 14:05 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 1DC1812081C for <nmrg@ietfa.amsl.com>; Fri, 6 Dec 2019 06:05:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 mMux-9W8UUuq for <nmrg@ietfa.amsl.com>; Fri, 6 Dec 2019 06:05:33 -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 AA773120817 for <nmrg@irtf.org>; Fri, 6 Dec 2019 06:05:32 -0800 (PST)
Received: from LHREML712-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 7B269B004D0FB1641478; Fri, 6 Dec 2019 14:05:28 +0000 (GMT)
Received: from fraeml706-chm.china.huawei.com (10.206.15.55) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 6 Dec 2019 14:05:28 +0000
Received: from fraeml706-chm.china.huawei.com (10.206.15.55) by fraeml706-chm.china.huawei.com (10.206.15.55) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Fri, 6 Dec 2019 15:05:27 +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; Fri, 6 Dec 2019 15:05:27 +0100
From: Olga Havel <olga.havel@huawei.com>
To: Alexander Clemm <alexander.clemm@huawei.com>, 李晨 <lichen6@chinatelecom.cn>, Jéferson Campos Nobre <jcnobre@inf.ufrgs.br>, "Liushucheng (Will Liu)" <liushucheng@huawei.com>, "Pedro Martinez-Julia (pedro@nict.go.jp)" <pedro@nict.go.jp>, "Diego R. Lopez" <diego.r.lopez@telefonica.com>, "Liushucheng (Will Liu)" <liushucheng@huawei.com>
CC: "nmrg@irtf.org" <nmrg@irtf.org>, "draft-li-nmrg-intent-classification@ietf.org" <draft-li-nmrg-intent-classification@ietf.org>
Thread-Topic: Alignment between the 2 drafts: New Version Notification for draft-li-nmrg-intent-classification-02.txt
Thread-Index: AdWsOMNZDFug1rGQQrqumbUxl3YvbQ==
Date: Fri, 06 Dec 2019 14:05:27 +0000
Message-ID: <6e44d017a84f461889b7e762eba7ca7b@huawei.com>
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_6e44d017a84f461889b7e762eba7ca7bhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/nmrg/pFdzCf9-YxSL46szzmQXBnVR37s>
Subject: [nmrg] Alignment between the 2 drafts: 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: Fri, 06 Dec 2019 14:05:35 -0000

Hi Alex,

As you already know from the emails sent to the group, there has been few questions about alignment of two drafts. I have not been involved in intent classification draft from the beginning, but was told that 2 drafts were agreed with chairs in previous meetings and that your draft is about concepts and overview and our draft is about intent classification. I also did not encounter any questions / issues about the overlap between the two drafts at f2f meeting in Rome and the comments we received for v1 prior to the last week have not been related to this.

But as it seems that there are still open questions, I think we need to align between us. The following are some of my suggestions, please let me know your opinion.

-          You draft owns intent definition & terminology and general overview – our future versions (03 +) would be fully aligned

-          Our draft owns intent classification, focusing on what solutions, intent users, intent types and categories we consider in scope – intent definition (04+) would encompass all solutions, users, intent types and categories

-          We need other drafts for architecture (including intent translation) and intent DSLs, these are out of scope for the current drafts and the current adoption.

Any comments from others are welcome, especially from Chairs.

Best Regards,
Olga