Re: [OPSAWG] WGLC for draft-ietf-opsawg-ntf [CORRECT]

Qin Wu <bill.wu@huawei.com> Wed, 30 September 2020 02:00 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06AAF3A0B2A; Tue, 29 Sep 2020 19:00:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, 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 vr0YKVQKpx7J; Tue, 29 Sep 2020 19:00:40 -0700 (PDT)
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 283013A0AC8; Tue, 29 Sep 2020 19:00:40 -0700 (PDT)
Received: from lhreml743-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id D0DAF4794AF82BDB88CA; Wed, 30 Sep 2020 03:00:38 +0100 (IST)
Received: from lhreml743-chm.china.huawei.com (10.201.108.193) by lhreml743-chm.china.huawei.com (10.201.108.193) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Wed, 30 Sep 2020 03:00:38 +0100
Received: from DGGEML423-HUB.china.huawei.com (10.1.199.40) by lhreml743-chm.china.huawei.com (10.201.108.193) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1913.5 via Frontend Transport; Wed, 30 Sep 2020 03:00:38 +0100
Received: from DGGEML531-MBS.china.huawei.com ([169.254.5.245]) by dggeml423-hub.china.huawei.com ([10.1.199.40]) with mapi id 14.03.0487.000; Wed, 30 Sep 2020 10:00:26 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Tianran Zhou <zhoutianran@huawei.com>, opsawg <opsawg@ietf.org>
CC: "draft-ietf-opsawg-ntf@ietf.org" <draft-ietf-opsawg-ntf@ietf.org>
Thread-Topic: [OPSAWG] WGLC for draft-ietf-opsawg-ntf [CORRECT]
Thread-Index: AdaWzRTJqins0g2gRuSrJeJxiUWNag==
Date: Wed, 30 Sep 2020 02:00:25 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABAADA346E4@dggeml531-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.101.103]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABAADA346E4dggeml531mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/4AwwzaihX-NMDCW3SGsXczF2BMo>
Subject: Re: [OPSAWG] WGLC for draft-ietf-opsawg-ntf [CORRECT]
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Sep 2020 02:00:42 -0000

Support for publication.
A quick comment, regarding event triggered data, I think FSM is just one example of how event is modelled, but not the only way.
Suggest to make this clear in the text.
-Qin
From: Tianran Zhou <zhoutianran@huawei.com<mailto:zhoutianran@huawei.com>>
Sent: Thursday, September 24, 2020 08:39
To: opsawg <opsawg@ietf.org<mailto:opsawg@ietf.org>>
Cc: draft-ietf-opsawg-ntf@ietf.org<mailto:draft-ietf-opsawg-ntf@ietf.org>
Subject: WGLC for draft-ietf-opsawg-ntf [CORRECT]


Sorry for attaching a wrong link to the draft. Please see as follows.



Hi WG,



This email starts a working group last call for draft-ietf-opsawg-ntf.

https://datatracker.ietf.org/doc/draft-ietf-opsawg-ntf/



Please indicate your support or concern for this draft. If you are opposed to the progression of the draft to RFC, please articulate your concern. If you support it, please indicate that you have read the latest version and it is ready for publication in your opinion. As always, review comments and nits are welcome.



The WG LC will end on 9st Oct 2020.



Thanks,

Tianran