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

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 04 May 2019 04:03 UTC

Return-Path: <brian.e.carpenter@gmail.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 E5A2C1201A7 for <nmrg@ietfa.amsl.com>; Fri, 3 May 2019 21:03:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 gIW76HADS5ZG for <nmrg@ietfa.amsl.com>; Fri, 3 May 2019 21:03:20 -0700 (PDT)
Received: from mail-pf1-x436.google.com (mail-pf1-x436.google.com [IPv6:2607:f8b0:4864:20::436]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A9B71201CE for <nmrg@irtf.org>; Fri, 3 May 2019 21:03:20 -0700 (PDT)
Received: by mail-pf1-x436.google.com with SMTP id t87so3306817pfa.2 for <nmrg@irtf.org>; Fri, 03 May 2019 21:03:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=QSr1HV6dRjKP41drH1a44H0fhpOmBdmLTqkl6aRRLSA=; b=dOud0p2ow1ScaVyCECxWItj7lN5qXThiYnIENJmaZB5gI63u5ABuYs6G29AN2NeMNj REDQwMQlBFGlOO7jsWAlhUATIm2o/szhPCsEp8rjk/OcMHfezR7wj4uyGqm+XP3Izs5K 9XJg6T2b/g0Q789VRVN32GbMDuHLyDVgx52iz14QSkLE4nSYDGZuQ94mwMNbysFBdEZS iWo/6YTgw0yT6CZWxpw6FEF5steYenGFVf3LsLkcSHOLSd0eR18i/cUPL9U9gntWxr5l XAxjsGQ65Mhn5oItywYn/RZp9dQgu2fr2aODOtZqOEo93wgKIfOIoT/DsF/nUYI7NgWD /eaQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=QSr1HV6dRjKP41drH1a44H0fhpOmBdmLTqkl6aRRLSA=; b=eUs57fjE3s1dKTQUkXNYuhPrE+nxO0WxUnl0xikqEAHTjWqUARhq9he+x7wj4ysJjb KQrYu33UXNwVo5R/1RZtEXGsJ+kmRILqw8SSw34Q/AmOPLIRl0eYyjoEk8afTKUOYRIB YxQsHV8CgVj/hM1HLczHjL690QMsZ4i5rxbp35MXdVY7yFY3Nk9Ta6rtkeQsnVM7mYN9 GGLDmO7yVndsLB/wvMDHjt0S+df0//+snJqPZ10ib7fkyxH1VHamCNlgCUOtlRcL7GlV 92pdKzbRZ32FJlXII8w+cO9THCxd7NviBzSd9KjEUDIrbS7qh36Wj6hMC9tEXWOIUtDQ s7ew==
X-Gm-Message-State: APjAAAU/PN2LmOzwI+ZnJEAyi6vANOawjmuvX5u1+eRAE2ss7wzstXOX axy4BCRSvRGlcwN2BHQa6N8=
X-Google-Smtp-Source: APXvYqyQ3MyGxFfOSnlGtwJfXRpjzpVm5mt3fOKOGt4GW81aaO+JoRv+ih4iW0tz3czJ/62I7uNj/A==
X-Received: by 2002:a65:63d7:: with SMTP id n23mr15674484pgv.26.1556942599961; Fri, 03 May 2019 21:03:19 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.72.205]) by smtp.gmail.com with ESMTPSA id 17sm8083751pfw.65.2019.05.03.21.03.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 03 May 2019 21:03:18 -0700 (PDT)
To: "Liushucheng (Will Liu)" <liushucheng@huawei.com>, "nmrg@irtf.org" <nmrg@irtf.org>
Cc: "draft-li-nmrg-intent-classification@ietf.org" <draft-li-nmrg-intent-classification@ietf.org>
References: <155602323349.32441.10483611247095706610.idtracker@ietfa.amsl.com> <C9B5F12337F6F841B35C404CF0554ACB8BD9A7E5@dggeml529-mbx.china.huawei.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <ddbf0ba7-0393-da70-b5eb-2f10efc9689e@gmail.com>
Date: Sat, 04 May 2019 16:03:17 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <C9B5F12337F6F841B35C404CF0554ACB8BD9A7E5@dggeml529-mbx.china.huawei.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/nmrg/OCLzoVbYVKS2hOUOv10Nt-havuc>
Subject: Re: [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: Sat, 04 May 2019 04:03:24 -0000

Hi,

I appreciate this document as background for what is otherwise quite a confusing discussion.

There is one statement that gives me a bit of difficulty, however:

>    Management personnel, such as network Administrators, have complete
>    knowledge of the underlying network.  However, they may not
>    understand the details of the applications and services of Customers
>    and End-Users.

The second sentence is certainly true. However, especially if autonomic networking is a success, I am not sure about the first sentence. As networks get more and more complex, and especially when virtual networks or slices are created dynamically and automatically, the administrators will *not* have complete knowledge of the underlying network. In fact, the intent itself may be the reason for this: the network is configured as a result of the intent, and the human administrators will then be unaware of the details. (They are presumably aware of the physical structure of the network, and the devices installed, but that is only part of the story.)

Regards
   Brian Carpenter

On 24-Apr-19 14:23, Liushucheng (Will Liu) wrote:
> 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
> 
> _______________________________________________
> nmrg mailing list
> nmrg@irtf.org
> https://www.irtf.org/mailman/listinfo/nmrg
>