IETF Logo Mail Archive

Re: [Netconf] WGLC on netconf-event-notifications-13

Tianran Zhou <zhoutianran@huawei.com> Wed, 10 October 2018 02:07 UTC

Return-Path: <zhoutianran@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 B67DF130E50 for <netconf@ietfa.amsl.com>; Tue, 9 Oct 2018 19:07:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 uqHspdWHWLNQ for <netconf@ietfa.amsl.com>; Tue, 9 Oct 2018 19:07:12 -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 BFC55130E4F for <netconf@ietf.org>; Tue, 9 Oct 2018 19:07:12 -0700 (PDT)
Received: from LHREML710-CAH.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 41D071044E6DE for <netconf@ietf.org>; Wed, 10 Oct 2018 03:07:08 +0100 (IST)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by LHREML710-CAH.china.huawei.com (10.201.108.33) with Microsoft SMTP Server (TLS) id 14.3.399.0; Wed, 10 Oct 2018 03:07:09 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0399.000; Wed, 10 Oct 2018 10:07:06 +0800
From: Tianran Zhou <zhoutianran@huawei.com>
To: Kent Watsen <kwatsen@juniper.net>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: WGLC on netconf-event-notifications-13
Thread-Index: AQHUXC8cbkWCNEfz8kWboGz592BIZKUXwePg
Date: Wed, 10 Oct 2018 02:07:06 +0000
Message-ID: <BBA82579FD347748BEADC4C445EA0F21B56C462C@NKGEML515-MBX.china.huawei.com>
References: <C25DFAF6-04FC-44B4-B714-D6CE4E4EFF8C@juniper.net>
In-Reply-To: <C25DFAF6-04FC-44B4-B714-D6CE4E4EFF8C@juniper.net>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.156.116]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/VPNGDWfa7J26xF5AEVBcQ6cZz9I>
Subject: Re: [Netconf] WGLC on netconf-event-notifications-13
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Network Configuration WG mailing 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: Wed, 10 Oct 2018 02:07:15 -0000

Hi,

I have reviewed this document, and think it's OK to move forward.

Only one thing, I am a little lost in the following paragraph.
"  Each error identity will be inserted as the "error-app-tag" using
   JSON encoding following the form <modulename>:<identityname>.  An
   example of such as valid encoding would be "ietf-subscribed-
   notifications:no-such-subscription". "

I do not know why "JSON encoding" is mentioned here.
<modulename>:<identityname> is not JSON like.

Regards,
Tianran

> -----Original Message-----
> From: Netconf [mailto:netconf-bounces@ietf.org] On Behalf Of Kent Watsen
> Sent: Friday, October 05, 2018 6:11 AM
> To: netconf@ietf.org
> Subject: [Netconf] WGLC on netconf-event-notifications-13
> 
> This message starts a Last Call on
> draft-ietf-netconf-netconf-event-notifications-13 (a.k.a.
> "netconf-notif"):
> 
> 
> https://tools.ietf.org/html/draft-ietf-netconf-netconf-event-notificatio
> ns-13
> 
> This, along with the restconf-notif Last Call, started in a separate message,
> marks the last of the last calls on the yang push suite of drafts. As explained
> before, given the size and number of documents, the chairs decided to break
> the reviews up into pieces so as to get focus on each in turn.  We chose to
> go top-down, starting with yang-push and ending with the "notif" drafts.  We
> plan to submit the drafts for publication when they are ready as a collective.
> The goal is to do all this prior to IETF 103.
> 
> While it's always nice to receive messages of support, at this time, the
> question isn't so much if the working group supports the work than if the
> document is ready to progress.  The chairs need to see reviews that indicate
> thorough end-to-end reading of the text.  Of course, if there are any
> objections, these should be brought forward now as well.
> 
> The current version (-13) of this draft was published on Oct 4th (today).
> The datatracker page for the draft is here:
> 
> 
> https://datatracker.ietf.org/doc/draft-ietf-netconf-netconf-event-notifi
> cations.
> 
> 
> Thanks,
> Kent (and Mahesh)
> 
> 
> 
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf

v2.23.0 | Report a Bug | By Email