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

Kent Watsen <kent+ietf@watsen.net> Thu, 13 June 2024 16:32 UTC

Return-Path: <0100019012711c3f-d2317fe0-30c0-4207-bb1f-855190e3ea3f-000000@amazonses.watsen.net>
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 17E89C14F71E for <netconf@ietfa.amsl.com>; Thu, 13 Jun 2024 09:32:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.com
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 zE0m42uTWuIi for <netconf@ietfa.amsl.com>; Thu, 13 Jun 2024 09:32:02 -0700 (PDT)
Received: from a8-96.smtp-out.amazonses.com (a8-96.smtp-out.amazonses.com [54.240.8.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26844C14F6FF for <netconf@ietf.org>; Thu, 13 Jun 2024 09:32:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1718296321; h=From:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Date:References:To:In-Reply-To:Message-Id:Feedback-ID; bh=s2RvGX5ydx6CL5pVi4hELmkT+FopHSDawaqyxzhcGcM=; b=qqk+MOk+sqGFicTaFl9TihrfIw30quFZztdPo2Tq8XXmP11f/t5b7KADi8/mz2tj Fy89IYRndV+1BS6c6bGA9nueA6sEQxKJT6dAPdXp00qwrKIHzZAgqZOskBu78qrETl9 7o4pxm0LKEgZzwx7XwDfD47UUHURIgzT7nroFucQ=
From: Kent Watsen <kent+ietf@watsen.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
Date: Thu, 13 Jun 2024 16:32:01 +0000
References: <0100018eb57a21d8-26b38f41-a625-4d44-9248-09b349fd4212-000000@email.amazonses.com>
To: "netconf@ietf.org" <netconf@ietf.org>
In-Reply-To: <0100018eb57a21d8-26b38f41-a625-4d44-9248-09b349fd4212-000000@email.amazonses.com>
Message-ID: <0100019012711c3f-d2317fe0-30c0-4207-bb1f-855190e3ea3f-000000@email.amazonses.com>
X-Mailer: Apple Mail (2.3774.400.31)
Feedback-ID: ::1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2024.06.13-54.240.8.96
Message-ID-Hash: H4BOHMDBWRVFD637MXEJTGSPYKGP3EB3
X-Message-ID-Hash: H4BOHMDBWRVFD637MXEJTGSPYKGP3EB3
X-MailFrom: 0100019012711c3f-d2317fe0-30c0-4207-bb1f-855190e3ea3f-000000@amazonses.watsen.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-netconf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [netconf] Re: Adoption call for notif-yang-04
List-Id: NETCONF WG list <netconf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/unkhLcJAPoa12YFPhWt9P6JO5rA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Owner: <mailto:netconf-owner@ietf.org>
List-Post: <mailto:netconf@ietf.org>
List-Subscribe: <mailto:netconf-join@ietf.org>
List-Unsubscribe: <mailto:netconf-leave@ietf.org>

Dear WG,

This adoption call was unsuccessful.

There is obviously a lot of interest, but the solution doesn’t seem adequate, given the comments made on the list.  Not to disparage the effort, but the problem is rather intractable!

Andy mentioned that an Interim may be needed, which seems right (+1 if you agree), but I wonder if there isn’t more that can be done in preparation first.  Specifically, as this effort challenges fundamentals, it would help to clarify the motivation and expected outcomes.

One high-level question I have, is there anything wrong with the “notification” statement in RFC 7950?  That is, is this at all a YANG-next issue for the NETMOD WG, or is to purely NETCONF WG issue?

Kent


> On Apr 6, 2024, at 6:14 PM, Kent Watsen <kent+ietf@watsen.net> wrote:
> 
> 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