IETF Logo Mail Archive

Re: [netconf] Adoption call for notif-yang-04

"maqiufang (A)" <maqiufang1@huawei.com> Mon, 15 April 2024 06:46 UTC

Return-Path: <maqiufang1@huawei.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82B89C14F68C for <netconf@ietfa.amsl.com>; Sun, 14 Apr 2024 23:46:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mc5XrPYkldbT for <netconf@ietfa.amsl.com>; Sun, 14 Apr 2024 23:46:38 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BA84C14F686 for <netconf@ietf.org>; Sun, 14 Apr 2024 23:46:38 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4VHyMZ3p1Lz6K6V4 for <netconf@ietf.org>; Mon, 15 Apr 2024 14:44:42 +0800 (CST)
Received: from lhrpeml500004.china.huawei.com (unknown [7.191.163.9]) by mail.maildlp.com (Postfix) with ESMTPS id 60D4A1400E7 for <netconf@ietf.org>; Mon, 15 Apr 2024 14:46:35 +0800 (CST)
Received: from kwepemm600019.china.huawei.com (7.193.23.64) by lhrpeml500004.china.huawei.com (7.191.163.9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Mon, 15 Apr 2024 07:46:34 +0100
Received: from kwepemm600017.china.huawei.com (7.193.23.234) by kwepemm600019.china.huawei.com (7.193.23.64) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Mon, 15 Apr 2024 14:46:33 +0800
Received: from kwepemm600017.china.huawei.com ([7.193.23.234]) by kwepemm600017.china.huawei.com ([7.193.23.234]) with mapi id 15.01.2507.035; Mon, 15 Apr 2024 14:46:32 +0800
From: "maqiufang (A)" <maqiufang1@huawei.com>
To: Kent Watsen <kent+ietf@watsen.net>, netconf <netconf@ietf.org>
Thread-Topic: [netconf] Adoption call for notif-yang-04
Thread-Index: AQHaiG/1YMfJc3Yg1EO4dueZhtQtJLFo7DRg
Date: Mon, 15 Apr 2024 06:46:32 +0000
Message-ID: <96782541b814443eb3a7cdc636dd3603@huawei.com>
References: <0100018eb57a21d8-26b38f41-a625-4d44-9248-09b349fd4212-000000@email.amazonses.com>
In-Reply-To: <0100018eb57a21d8-26b38f41-a625-4d44-9248-09b349fd4212-000000@email.amazonses.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.118.147]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/QgcrBd06kEQbW--43eCY0X_O1Mg>
Subject: Re: [netconf] Adoption call for notif-yang-04
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Apr 2024 06:46:44 -0000

Hi, Kent, all,

I also support the adoption of this doc. I agree that it's quite useful. I am unsure whether we still want to name it as "YANG model for NETCONF Event Notifications", given RFC 8639 has already extended this event notification initially defined in 5277 to be transport-independent, i.e., not specific to NETCONF protocol.

Sec.3.1 should call out the reference to 8340, see the guidelines specified in https://datatracker.ietf.org/doc/html/draft-ietf-netmod-rfc8407bis-09#section-3.4. 

Best Regards,
Qiufang

-----Original Message-----
From: netconf [mailto:netconf-bounces@ietf.org] On Behalf Of Kent Watsen
Sent: Sunday, April 7, 2024 6:14 AM
To: netconf@ietf.org
Subject: [netconf] Adoption call for notif-yang-04

NETCONF WG,

This message starts a two week poll on adopting the following document:

	YANG model for NETCONF Event Notifications
	https://datatracker.ietf.org/doc/html/draft-ahuang-netconf-notif-yang-04

The poll ends April 20.

Please send email to the list indicating "yes/support” or "no/do not support".  If indicating no, please state your reservations with the document.  If yes, please also feel free to provide comments you'd like to see addressed once the document is a WG document.

No IPR is known for this document:  https://mailarchive.ietf.org/arch/msg/netconf/oQVZ6Pf_novNfMB4RsnDxQibHpM/

PS: this document received strong support before, being very focused, providing just a module enabling validation of YANG “notification” messages.

Kent and Per (as co-chairs)





_______________________________________________
netconf mailing list
netconf@ietf.org
https://www.ietf.org/mailman/listinfo/netconf

v2.23.0 | Report a Bug | By Email