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

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 08 May 2019 20:13 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 B53751200FA for <nmrg@ietfa.amsl.com>; Wed, 8 May 2019 13:13:52 -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 06m9InDXP27W for <nmrg@ietfa.amsl.com>; Wed, 8 May 2019 13:13:50 -0700 (PDT)
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (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 A858D120026 for <nmrg@irtf.org>; Wed, 8 May 2019 13:13:50 -0700 (PDT)
Received: by mail-pl1-x62a.google.com with SMTP id n8so10440415plp.10 for <nmrg@irtf.org>; Wed, 08 May 2019 13:13:50 -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=J5/zuQk4D4o0ayRLuBhAKU4P1ZlV5FvA4+PDSM5p9qo=; b=NmBSRhszIppPbBbAnc2qL7iqHRSWQcJnpKL+qfaKFbUq6zOWF9P8IjrmTbhrKbHO/y 66/eLkLngC22j52CSzCTzGg+G6hs9wcT6nLjDgVGZxUftslwfBl+MvwnCNuLoa6pm7xj vm9Guzxv+NlbU3fFTaV9SeSWTP4jmfME7bw1YZUIzl9oyMxh/sYb6XMlFGxuNjT/SGEJ sL8JZ9YLn1PGjbWS1Xo/gpvZtfhJV7AhpOnuxfIvyVut7Xh6LtctAxEu6VgquOg1t4QV BuvNkG9ZdGSC/BG1aRonarX425d+mj3beBv2aAaXtykuEqOqj/CN9V5rFD6msYy32s7L tWOA==
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=J5/zuQk4D4o0ayRLuBhAKU4P1ZlV5FvA4+PDSM5p9qo=; b=J17DJS4pse322dSnuJ6w7Z+aCbriMLLwQXhjNYm775ABVncg2ljf7+p+YLNX208x67 6GcsL1t4rgeRDFGQEcNSW18/AD/bnk8I4Yradj8pTTbsJiF2FmQrjCFLe0z61jwlPSQT 2vlxKpBU7UwouOYBYZ8DDnPajDW4kR67HXy0prABYOaKz7niLFi1lkUVmH2IqMr0bsGk Grx4k4L8CCcqVsC8Wo2bsKpMihY9o93Zx/rQ8IyNNDtWa3M4g0Ky7cZB1zXrsB0Mr05M A6aY5+nyFpgWmcCtzghHIKAIvWFC4JJ/34Emm6470zby38gjqu2RSJn7uRQOA/4S+IMr M55g==
X-Gm-Message-State: APjAAAVoRzKgcO++6g/BF/Dnj/1M1sDmXpHc+qk3umo+d+L1duO9k+VP 98JI3og3IjxfoOCdpkXU/II=
X-Google-Smtp-Source: APXvYqxIpoWq5vZG+98GLqTituaE9z1O2vsIKLxQl2LDV0apF3rupkcXPDG4AtPr11iNdeKShIMwmQ==
X-Received: by 2002:a17:902:f096:: with SMTP id go22mr5048042plb.49.1557346429974; Wed, 08 May 2019 13:13:49 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.72.205]) by smtp.gmail.com with ESMTPSA id x66sm96691pfb.78.2019.05.08.13.13.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 May 2019 13:13:48 -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> <ddbf0ba7-0393-da70-b5eb-2f10efc9689e@gmail.com> <C9B5F12337F6F841B35C404CF0554ACB8BDA9AF8@dggeml529-mbx.china.huawei.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <7379081d-2440-99a6-f24a-eb2fb689b5a4@gmail.com>
Date: Thu, 09 May 2019 08:13:45 +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: <C9B5F12337F6F841B35C404CF0554ACB8BDA9AF8@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/fjWDUl4q4e5OFe6z409GRB7_9iU>
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: Wed, 08 May 2019 20:13:53 -0000

On 08-May-19 21:46, Liushucheng (Will Liu) wrote:
> Hi Brian,
> 
> Thanks for your comments. I agree that the first sentence is not accurate and the rest of your comments. 
> 
> The main role of the first sentence is to lead to the second one. :)
> We will modify it in next version to: Management personnel, such as network administrators, may have the knowledge of the underlying network.  
> Is that OK?

Yes, I think so. I hope we can soon have some concrete examples of intent, because for a long time the discussion has been very abstract.

Regards
    Brian

> 
> Regards, / 致礼! 
> Will LIU  / 刘树成
> 
> -----Original Message-----
> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com] 
> Sent: Saturday, May 04, 2019 12:03 PM
> To: Liushucheng (Will Liu) <liushucheng@huawei.com>; nmrg@irtf.org
> Cc: draft-li-nmrg-intent-classification@ietf.org
> Subject: Re: [nmrg] FW: New Version Notification for draft-li-nmrg-intent-classification-00.txt
> 
> 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
>>
>