Re: [nmrg] [EXT] Re: Adoption call for draft-li-nmrg-intent-classification-02

Olga Havel <olga.havel@huawei.com> Fri, 06 December 2019 13:22 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 553041200A4; Fri, 6 Dec 2019 05:22:12 -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, RCVD_IN_DNSWL_MED=-2.3, 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 dBOIaI5932eJ; Fri, 6 Dec 2019 05:22:10 -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 02BA412001E; Fri, 6 Dec 2019 05:22:10 -0800 (PST)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 2D61252FFF2C3ECBD469; Fri, 6 Dec 2019 13:22:07 +0000 (GMT)
Received: from fraeml704-chm.china.huawei.com (10.206.15.53) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 6 Dec 2019 13:22:06 +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; Fri, 6 Dec 2019 14:22:06 +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 14:22:06 +0100
From: Olga Havel <olga.havel@huawei.com>
To: "Natale, Bob" <RNATALE@mitre.org>, Jérôme François <jerome.francois@inria.fr>
CC: "nmrg-chairs@irtf.org" <nmrg-chairs@irtf.org>, "nmrg@irtf.org" <nmrg@irtf.org>
Thread-Topic: [nmrg] [EXT] Re: Adoption call for draft-li-nmrg-intent-classification-02
Thread-Index: AQHVqzl90BjzpeVdEk6W6/xdhk/SoaetD4fg
Date: Fri, 06 Dec 2019 13:22:06 +0000
Message-ID: <2aeedaaad5f04224b3776655e04b5789@huawei.com>
References: <d2f3bcea-ac67-0350-259e-fa68eeeee889@inria.fr> <2739_1575494701_5DE8242D_2739_507_1_20191204212450.g4oiwym4ocor5b35@anna.jacobs.jacobs-university.de> <DM6PR09MB4073F0D0327099F5465B96C9A85C0@DM6PR09MB4073.namprd09.prod.outlook.com>
In-Reply-To: <DM6PR09MB4073F0D0327099F5465B96C9A85C0@DM6PR09MB4073.namprd09.prod.outlook.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: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/nmrg/0rGHSCPWxPtz2LcDhdEU9S8OCdc>
Subject: Re: [nmrg] [EXT] Re: Adoption call for draft-li-nmrg-intent-classification-02
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 13:22:12 -0000

Hi BobN,

Thank you very much for your comments, I absolutely agree with you about it all. But I do think that we need to have additional drafts to address some of the comments you have and that maybe not all of them are in the scope of this draft. The scope of this draft is intent classification - from the perspective of different solutions and intent users, where intent user is any human interacting with the network (existing network and future autonomous network). I think this draft should be foundation for discussion of intent related topics and other drafts that would be coming - intent engine architecture (including translation, layering) and intent DSLs.

- Policy Continuum.  I agree but we intentionally reduced it in order to focus this draft on intent classification from the solution and user perspective, for both technical & non-technical user, without need to understand the black box and layering. This draft is the starting point to continue working on formal definitions (intents, APIs, DSLs) & architecture. I do believe we need to start working on additional drafts that would address other aspects and the work on Policy Continuum will be the core input in these drafts. 

- Translation of policies, intent-based policy expression, operation of Policy Continuum
[Olga] This draft did not look at translation, intent DSLs / models / APIs and is focused on identifying solutions, users and intent types. I think your comments are very valuable and it is definitely something we have to focus in other drafts that would look at intent architecture and intent models / DSLs.  There is already some work started on the architecture draft.

I do believe the value of this draft and the adoption of version 02 will be continued discussion and hopefully final agreement in the group about how to classify intents, but starting from business / intent user - what is needed by different solutions & different intent users in those solutions. I do not think version 02 means that we agreed about all categories and classification, it means we are continuing discussion. 

Best Regards,
Olga

-----Original Message-----
From: nmrg [mailto:nmrg-bounces@irtf.org] On Behalf Of Natale, Bob
Sent: Thursday 5 December 2019 06:58
To: Jérôme François <jerome.francois@inria.fr>
Cc: nmrg-chairs@irtf.org; nmrg@irtf.org
Subject: Re: [nmrg] [EXT] Re: Adoption call for draft-li-nmrg-intent-classification-02
Importance: Low

I would like to add that the extremely brief section on the Policy Continuum in the draft seems superfluous in light of its brevity and consequent over-simplification. (If John Strassner feels otherwise, then please ignore my comments here!)

While the existing text is a reasonable facsimile of early descriptions of the Policy Continuum, as thought developed the concept matured: E.g., "The Policy Continuum - Policy authoring and conflict analysis" (2008), http://brendanjennings.net/papers/2008_COMCOM_SDavy_et_al_published.pdf, esp. sec. 2.1.4, but most of the rest of the paper is essential to a useful level of understanding. 

Alas, at some point the Policy Continuum concept seems to have fallen relatively dormant. Regardless, wrt the discussion topic at hand, I believe that several points must be considered:

- Non-person entity "actors" as policy authors will be essential to translation of policy expressions in the Intent-based operating model.
- It is (and always has been) the translation of policies across levels. The translation activity is what makes the model a continuum as opposed to (only) a set of interworking differentiated layers.
- Applying Intent-based policy expression adds a distinct dimension to operation of the Policy Continuum ... this new dimension is compatible with existing common understanding of the Policy Continuum but introduces additional translations at some layers.

So, I think it's necessary to cover the Policy Continuum (by whatever name might be preferable today, if that term is out of vogue) in an explanation of Intent-based policy implementation. I am not sure it belongs in a document defining Intent classification. And it almost certainly does not fit into this particular draft in its present form. I do see the connection you are presumably making with your Intent User and Intent Type breakouts and the Policy Continuum but (to coin a phrase?) it's "too little too early" to add any real value.

FWIW (from a lurker),
BobN

-----Original Message-----
From: nmrg <nmrg-bounces@irtf.org> On Behalf Of Schönwälder, Jürgen
Sent: Wednesday, December 4, 2019 4:25 PM
To: Jérôme François <jerome.francois@inria.fr>
Cc: nmrg-chairs@irtf.org; nmrg@irtf.org
Subject: [EXT] Re: [nmrg] Adoption call for draft-li-nmrg-intent-classification-02

I am still not sure what the value of this document is. What is the insight that these big tables deliver? How do they help doing ultimately better work in the IETF?

I am sure I will get some answer quickly from the authors but what I am saying is that I prefer to see the value of this document very clearly explained in the document before adopting it. Note that I also expect that this document would align with the other document defining intent concepts and terminology. Perhaps this is more intended like a survey paper but then it has gone a bit in the wrong direction since a decent survey would explain how intent is defined and used in concrete projects (hint: lots of concrete descriptions and references) and then you would classify things. But right now, we have big tables with empty cells or cells with text that seems to come from rather unknown sources.

For the above reasons, I do not support adoption at this point in time.

/js

On Wed, Dec 04, 2019 at 06:24:44PM +0100, Jérôme François wrote:
> Dear all,
> 
> We recently received an RG adoption request for
> draft-li-nmrg-intent-classification-02
> (https://www.ietf.org/id/draft-li-nmrg-intent-classification-02.txt)
> 
> Please let us know if you support the work becoming a RG document or 
> if you think it should not be adopted. In all cases, provide detailed 
> comments to support your opinion and send them on the mailing list.
> 
> This call for adoption is open for two weeks and ends up on 19 December 2019.
> 
> The procedure for RG document adoption and important criteria are 
> detailed
> here: 
> https://mailarchive.ietf.org/arch/msg/nmrg/CVEyLUvfxJk1Ud5WdM9Y5LGvQmU
> 
> Best regards
> NMRG chairs
> Laurent & Jérôme
> 
> _______________________________________________
> nmrg mailing list
> nmrg@irtf.org
> https://www.irtf.org/mailman/listinfo/nmrg

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>

_______________________________________________
nmrg mailing list
nmrg@irtf.org
https://www.irtf.org/mailman/listinfo/nmrg

_______________________________________________
nmrg mailing list
nmrg@irtf.org
https://www.irtf.org/mailman/listinfo/nmrg