Return-Path: 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 806D6C14F691; Tue, 18 Jun 2024 07:46:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.265 X-Spam-Level: X-Spam-Status: No, score=0.265 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_HELO_IP_MISMATCH=2.368, 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, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=insa-lyon.fr 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 HddHZSprOiq5; Tue, 18 Jun 2024 07:46:12 -0700 (PDT) Received: from smtpout01-ext2.partage.renater.fr (smtpout01-ext2.partage.renater.fr [194.254.240.33]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1031C14F686; Tue, 18 Jun 2024 07:46:08 -0700 (PDT) Received: from zmtaauth01.partage.renater.fr (zmtaauth01.partage.renater.fr [194.254.240.25]) by smtpout10.partage.renater.fr (Postfix) with ESMTP id D773B65072; Tue, 18 Jun 2024 16:46:03 +0200 (CEST) Received: from zmtaauth01.partage.renater.fr (localhost [127.0.0.1]) by zmtaauth01.partage.renater.fr (Postfix) with ESMTPS id D9024140190; Tue, 18 Jun 2024 16:46:03 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by zmtaauth01.partage.renater.fr (Postfix) with ESMTP id C7358140187; Tue, 18 Jun 2024 16:46:03 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.10.3 zmtaauth01.partage.renater.fr C7358140187 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=insa-lyon.fr; s=CB289C06-95B8-49FE-9C4B-D197C6D2E7CB; t=1718721963; bh=p9KPgR/R6XVEucsWlpue2v6VANzlvWvYv/hLjgxDu54=; h=From:Mime-Version:Date:To:Message-Id; b=iuvfFNkAA6oUYozZdVpcQ+39IH/eSjGKjw/fzI6CCt9OqvyuDwlpExbBemBKLF4Bn gG4mqGWESXg9baDll7Il1Nq2LJ9F3YyANH8n1PmewQ+kPjiSihMfHmKvqIBQIW0YFV l9oMBBxGW3ArJFakKc3ETw235owQBQdCovy37KkceVKMwZpIUY+gKiU3s57XRJ/9xS 2wT5ZtRFNAZkQRwdjX5dr9DYraAiKghYtqmIinJ19BfAPOXD6CPhm6nVdIPnFDnhtS wgJ5MDztz0FBjwNdD9pJyFNTgwUNi/OS6ar6hzgZ5H6qg6tSOorRlseOwG6TXl9MNc iofGq0LYBzJSw== Received: from zmtaauth01.partage.renater.fr ([127.0.0.1]) by localhost (zmtaauth01.partage.renater.fr [127.0.0.1]) (amavis, port 10026) with ESMTP id 3pYcgsJ2qw1H; Tue, 18 Jun 2024 16:46:03 +0200 (CEST) Received: from 176.146.148.215 (unknown [194.254.241.250]) by zmtaauth01.partage.renater.fr (Postfix) with ESMTPA id 7E924140186; Tue, 18 Jun 2024 16:46:03 +0200 (CEST) From: Alex Huang Feng Content-Type: multipart/alternative; boundary="Apple-Mail=_B3B64D74-788D-42C1-BAE7-D7A6831E2121" Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\)) Date: Tue, 18 Jun 2024 16:45:53 +0200 References: <171872158441.3149.13198013629440679290@ietfa.amsl.com> To: netconf Message-Id: X-Mailer: Apple Mail (2.3774.600.62) X-Virus-Scanned: clamav-milter 0.103.8 at clamav04 X-Virus-Status: Clean X-Renater-Ptge-SpamState: clean X-Renater-Ptge-SpamScore: 0 X-Renater-Ptge-SpamCause: gggruggvucftvghtrhhoucdtuddrgedvledrfedvkedgheduucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecutffgpfetvffgtfenuceurghilhhouhhtmecufedttdenucenucfjughrpefhtggguffffhevvffkofesrgdtmherhhdtjeenucfhrhhomheptehlvgigucfjuhgrnhhgucfhvghnghcuoegrlhgvgidrhhhurghnghdqfhgvnhhgsehinhhsrgdqlhihohhnrdhfrheqnecuggftrfgrthhtvghrnhepgeelffehheelhedtueeiueegheefuedvieejtdettefgfeejkedtkeekudehgeeinecuffhomhgrihhnpehivghtfhdrohhrghenucfkphepudelgedrvdehgedrvdeguddrvdehtdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepihhnvghtpeduleegrddvheegrddvgedurddvhedtpdhhvghlohepudejiedrudegiedrudegkedrvdduhedpmhgrihhlfhhrohhmpegrlhgvgidrhhhurghnghdqfhgvnhhgsehinhhsrgdqlhihohhnrdhfrhdpnhgspghrtghpthhtohepvddprhgtphhtthhopehnvghttghonhhfsehivghtfhdrohhrghdprhgtphhtthhopegurhgrfhhtqdgrhhhurghnghdqnhgvthgtohhnfhdqnhhothhifhdqhigrnhhgrdgruhhthhhorhhssehivghtfhdrohhrgh Message-ID-Hash: GXAD6O2QTDTB3RGRHXWTEJVL7MZ3MBJV X-Message-ID-Hash: GXAD6O2QTDTB3RGRHXWTEJVL7MZ3MBJV X-MailFrom: alex.huang-feng@insa-lyon.fr 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 CC: draft-ahuang-netconf-notif-yang.authors@ietf.org X-Mailman-Version: 3.3.9rc4 Precedence: list Subject: =?utf-8?q?=5Bnetconf=5D_New_Version_Notification_for_draft-ahuang-netconf-no?= =?utf-8?q?tif-yang-05=2Etxt?= List-Id: NETCONF WG list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --Apple-Mail=_B3B64D74-788D-42C1-BAE7-D7A6831E2121 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Dear NETCONF, In parallel to all the current discussions, I just submitted a new = proposal for the draft-ahuang-netconf-notif-yang draft. https://datatracker.ietf.org/doc/draft-ahuang-netconf-notif-yang/05/ In this iteration, we propose to use normative text rather than just = point to the YANG module for the NETCONF Event Notification header = validation. A bit like how RFC8040 does in = https://datatracker.ietf.org/doc/html/rfc8040#section-6.4 for its own = notifications. We propose to use =E2=80=9Cietf-notification=E2=80=9D as root namespace = and leave RESTCONF out of scope of the document (when notifications are = in RESTCONF environments, they will continue using the namespace defined = in RFC8040). In this proposal, we update the following documents: - RFC5277: because the root structure is defined in this RFC using XML - RFC8639: because Subscribed Notifications uses the structure defined = in RFC5277 - RFC7951: because even though the document states it specifies how = notifications are encoded, they are not explicitly specified - RFC9254: because CBOR states that notifications are container-like = instances and are not consistent with XML and JSON encodings. A detailed section how the document updates the RFC above can be found = in = https://datatracker.ietf.org/doc/html/draft-ahuang-netconf-notif-yang-05#n= ame-relationship-to-past-docume We continue welcoming new comments and proposals to correctly limit the = scope and improve this draft.=20 We understand that there is interest in fixing this gap for current = implementators of YANG-Push. And finally, we would like to thank everyone reading the draft and = raising the issues on the ML (and offline) during the adoption call. Regards, Alex, on behalf of the authors > Begin forwarded message: >=20 > From: internet-drafts@ietf.org > Subject: New Version Notification for = draft-ahuang-netconf-notif-yang-05.txt > Date: 18 June 2024 at 16:39:44 CEST > To: "Alex Feng" , "Alex Huang Feng" = , "Benoit Claise" = , "Pierre Francois" = , "Thomas Graf" >=20 > A new version of Internet-Draft draft-ahuang-netconf-notif-yang-05.txt = has > been successfully submitted by Alex Huang Feng and posted to the > IETF repository. >=20 > Name: draft-ahuang-netconf-notif-yang > Revision: 05 > Title: YANG model for NETCONF Event Notifications > Date: 2024-06-17 > Group: Individual Submission > Pages: 15 > URL: = https://www.ietf.org/archive/id/draft-ahuang-netconf-notif-yang-05.txt > Status: = https://datatracker.ietf.org/doc/draft-ahuang-netconf-notif-yang/ > HTMLized: = https://datatracker.ietf.org/doc/html/draft-ahuang-netconf-notif-yang > Diff: = https://author-tools.ietf.org/iddiff?url2=3Ddraft-ahuang-netconf-notif-yan= g-05 >=20 > Abstract: >=20 > This document defines the structure of NETCONF Event Notification in > a YANG model to be used in NETCONF environments. The definition of > this YANG model allows the encoding of NETCONF Event Notifications = in > YANG compatible encodings such as JSON and CBOR. >=20 >=20 >=20 > The IETF Secretariat >=20 >=20 --Apple-Mail=_B3B64D74-788D-42C1-BAE7-D7A6831E2121 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Dear = NETCONF,

In parallel to all the current discussions, = I just submitted a new proposal for the = draft-ahuang-netconf-notif-yang draft.


We propose to use = =E2=80=9Cietf-notification=E2=80=9D as root namespace and leave RESTCONF = out of scope of the document (when notifications are in RESTCONF = environments, they will continue using the namespace defined in = RFC8040).

In this proposal, we update the = following documents:
- RFC5277: because the root structure is = defined in this RFC using XML
- RFC8639: because Subscribed = Notifications uses the structure defined in RFC5277
- RFC7951: = because even though the document states it specifies how notifications = are encoded, they are not explicitly specified
- RFC9254: = because CBOR states that notifications are container-like instances and = are not consistent with XML and JSON = encodings.

A detailed section how the document = updates the RFC above can be found in https://datatracker.ietf.org/doc/= html/draft-ahuang-netconf-notif-yang-05#name-relationship-to-past-docume




Begin forwarded message:

From: internet-drafts@ietf.org
Subject: New = Version Notification for = draft-ahuang-netconf-notif-yang-05.txt
Date: 18 June = 2024 at 16:39:44 CEST
To: "Alex Feng" <alex.huang-feng@insa-lyon.fr>, "Alex = Huang Feng" <alex.huang-feng@insa-lyon.fr>, "Benoit Claise" = <benoit.claise@huawei.com>, "Pierre Francois" = <pierre.francois@insa-lyon.fr>, "Thomas Graf" = <thomas.graf@swisscom.com>

A new = version of Internet-Draft draft-ahuang-netconf-notif-yang-05.txt = has
been successfully submitted by Alex Huang Feng and posted to = the
IETF repository.

Name: =     draft-ahuang-netconf-notif-yang
Revision: = 05
Title:    YANG model for NETCONF Event = Notifications
Date:     2024-06-17
Group: =    Individual Submission
Pages: =    15
URL: =      https://www.ietf.org/archive/id/draft-ahuang= -netconf-notif-yang-05.txt
Status: =   https://datatracker.ietf.org/doc/draft-ahuang-netconf-notif-ya= ng/
HTMLized: = https://datatracker.ietf.org/doc/html/draft-ahuang-netconf-notif-yang
D= iff: =     https://author-tools.ietf.org/iddiff?url2=3Ddraft-= ahuang-netconf-notif-yang-05

Abstract:

  This = document defines the structure of NETCONF Event Notification in
=   a YANG model to be used in NETCONF environments.  The = definition of
  this YANG model allows the encoding of = NETCONF Event Notifications in
  YANG compatible encodings = such as JSON and CBOR.



The IETF = Secretariat



= --Apple-Mail=_B3B64D74-788D-42C1-BAE7-D7A6831E2121--