[nmrg] FW: New Version Notification for draft-li-nmrg-intent-classification-00.txt

"Liushucheng (Will Liu)" <liushucheng@huawei.com> Wed, 24 April 2019 02:24 UTC

Return-Path: <liushucheng@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 27680120105 for <nmrg@ietfa.amsl.com>; Tue, 23 Apr 2019 19:24:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 FJgNPNrBDoRp for <nmrg@ietfa.amsl.com>; Tue, 23 Apr 2019 19:24:00 -0700 (PDT)
Received: from huawei.com (szxga03-in.huawei.com [45.249.212.189]) (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 9297A1200F1 for <nmrg@irtf.org>; Tue, 23 Apr 2019 19:23:59 -0700 (PDT)
Received: from DGGEML403-HUB.china.huawei.com (unknown [172.30.72.54]) by Forcepoint Email with ESMTP id A255490C91B39B24891E for <nmrg@irtf.org>; Wed, 24 Apr 2019 10:23:54 +0800 (CST)
Received: from DGGEML529-MBX.china.huawei.com ([169.254.6.176]) by DGGEML403-HUB.china.huawei.com ([fe80::74d9:c659:fbec:21fa%31]) with mapi id 14.03.0439.000; Wed, 24 Apr 2019 10:23:51 +0800
From: "Liushucheng (Will Liu)" <liushucheng@huawei.com>
To: "nmrg@irtf.org" <nmrg@irtf.org>
CC: "draft-li-nmrg-intent-classification@ietf.org" <draft-li-nmrg-intent-classification@ietf.org>
Thread-Topic: New Version Notification for draft-li-nmrg-intent-classification-00.txt
Thread-Index: AQHU+dHEoY6LybTRvUWM4jRkKabzE6ZKk1lw
Date: Wed, 24 Apr 2019 02:23:51 +0000
Message-ID: <C9B5F12337F6F841B35C404CF0554ACB8BD9A7E5@dggeml529-mbx.china.huawei.com>
References: <155602323349.32441.10483611247095706610.idtracker@ietfa.amsl.com>
In-Reply-To: <155602323349.32441.10483611247095706610.idtracker@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.25.127.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/nmrg/AWGO-lxevZ9Jrzh7wjWt9rFNuz4>
Subject: [nmrg] FW: New Version Notification for draft-li-nmrg-intent-classification-00.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: Wed, 24 Apr 2019 02:24:02 -0000

Hi,

I just did some small modifications and submit this draft as -nmrg, which replaced the old draft-li version.

As we presented during last NMRG meeting, there are several shared principles between SDOs:
  -intent should be declarative, using and depending on as few deployment details as possible and focusing on what and not how
  -intent should provide an easy-to-use interface, and use terminology and concepts familiar to its target audience
  -intent should be vendor-independent and portable across platforms
  -the intent framework should be able to detect and resolve conflicts between multiple intents

This document goal is to discuss and propose how to classify intents, so that  can be a good foundation for future discussion related to intent in IETF scope.

In the draft we've listed Intent Classification based on :
-Solutions, Users and their Purpose
-When to Activate
-Lifecycle Management Requirements
-Granularity

Slides we presented: 
https://datatracker.ietf.org/meeting/104/materials/slides-104-nmrg-sessb-intent-classification-00
                                 
Your comments and contributions are welcome!

Regards, / 致礼! 
Will LIU  / 刘树成


-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Tuesday, April 23, 2019 8:41 PM
To: Liushucheng (Will Liu) <liushucheng@huawei.com>; John Strassner <John.sc.Strassner@huawei.com>; Olga Havel <olga.havel@huawei.com>; Xuweiping (David) <xuweiping@huawei.com>; Ying Cheng <chengying10@chinaunicom.cn>; Liushucheng (Will Liu) <liushucheng@huawei.com>; Chen Li <lichen.bri@chinatelecom.cn>
Subject: New Version Notification for draft-li-nmrg-intent-classification-00.txt


A new version of I-D, draft-li-nmrg-intent-classification-00.txt
has been successfully submitted by Will (Shucheng) Liu and posted to the IETF repository.

Name:		draft-li-nmrg-intent-classification
Revision:	00
Title:		Intent Classification
Document date:	2019-04-22
Group:		Individual Submission
Pages:		13
URL:            https://www.ietf.org/internet-drafts/draft-li-nmrg-intent-classification-00.txt
Status:         https://datatracker.ietf.org/doc/draft-li-nmrg-intent-classification/
Htmlized:       https://tools.ietf.org/html/draft-li-nmrg-intent-classification-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-li-nmrg-intent-classification


Abstract:
   RFC 7575 defines Intent as an abstract high-level policy used to
   operate the network. Intent management system includes an interface
   for users to input requests and an engine to translate the intents
   into the network configuration and manage their lifecycle. Up to
   now, there is no commonly agreed definition, interface or model of
   intent.

   This document discusses what intent means to different stakeholders,
   describes different ways to classify intent, and an associated
   taxonomy of this classification. This is a foundation for discussion
   intent related topics.

                                                                                  


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat