[netconf] New Version Notification for draft-ahuang-netconf-notif-yang-05.txt

Alex Huang Feng <alex.huang-feng@insa-lyon.fr> Tue, 18 June 2024 14:46 UTC

From: Alex Huang Feng <alex.huang-feng@insa-lyon.fr>
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 <netconf@ietf.org>
Message-Id: <B0FF9EB6-6E56-4629-B4D0-AAEBD12EAD3E@insa-lyon.fr>
Message-ID-Hash: GXAD6O2QTDTB3RGRHXWTEJVL7MZ3MBJV
CC: draft-ahuang-netconf-notif-yang.authors@ietf.org
Precedence: list
Subject: [netconf] New Version Notification for draft-ahuang-netconf-notif-yang-05.txt
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/mI31HDCLZ4PRees_8walfRjisF8>

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 “ietf-notification” 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

We continue welcoming new comments and proposals to correctly limit the scope and improve this draft. 

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:
> 
> 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-yang/
> HTMLized: https://datatracker.ietf.org/doc/html/draft-ahuang-netconf-notif-yang
> Diff:     https://author-tools.ietf.org/iddiff?url2=draft-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
> 
>

[netconf] New Version Notification for draft-ahua… Alex Huang Feng