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

"Eric Voit (evoit)" <evoit@cisco.com> Wed, 10 October 2018 14:11 UTC

Return-Path: <evoit@cisco.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 EEBB3130F15 for <netconf@ietfa.amsl.com>; Wed, 10 Oct 2018 07:11:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.957
X-Spam-Level:
X-Spam-Status: No, score=-14.957 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 4FsarfeMSwFT for <netconf@ietfa.amsl.com>; Wed, 10 Oct 2018 07:11:13 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4FA4130F2A for <netconf@ietf.org>; Wed, 10 Oct 2018 07:11:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3131; q=dns/txt; s=iport; t=1539180672; x=1540390272; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=E/k5eAYdbKHeCzqF/zCmMemVzLbyV9Zqc8/62Vbyy1E=; b=cX0JlfOcZZA+utHDtlJNMsB9R86tSfa09OL/AboS6YTlw7grveQR1QRh xCBFD0Rc7st69MXMdKB+0BCOuf4Z/ewo6eXos+OUuN3+YrAPIHvZOjYTO JKp5JgSkw2aSZMy9KLfyddhf+Fij0ktd05TrXssYETs8rSSn4XlFmK5EW g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AEAAAnB75b/4sNJK1ZAQkZAQEBAQE?= =?us-ascii?q?BAQEBAQEBBwEBAQEBAYFRBAEBAQEBCwGBWypmfygKjACMNYINln6BegsBARg?= =?us-ascii?q?LhANGAoRQITQNDQEDAQECAQECbRwMhTkBAQEBAgEBATg0CQcHBAIBCBEEAQE?= =?us-ascii?q?OEQkHJwsUCQgCBAESCIJOSwGBeQgPpgmEMweFVQWLOxeBQT+BEoMSgxsBAQI?= =?us-ascii?q?BAYEyAYYCAokLlHsJAoZPiXgfkAuMMIk1AhEUgSUdOIFVcBU7gmyLF4U+b4s?= =?us-ascii?q?/gR8BAQ?=
X-IronPort-AV: E=Sophos;i="5.54,364,1534809600"; d="scan'208";a="464282559"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Oct 2018 14:11:11 +0000
Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by alln-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id w9AEBBxC004260 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 10 Oct 2018 14:11:11 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-013.cisco.com (64.101.220.153) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 10 Oct 2018 10:11:10 -0400
Received: from xch-rtp-013.cisco.com ([64.101.220.153]) by XCH-RTP-013.cisco.com ([64.101.220.153]) with mapi id 15.00.1395.000; Wed, 10 Oct 2018 10:11:10 -0400
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: Tianran Zhou <zhoutianran@huawei.com>, Kent Watsen <kwatsen@juniper.net>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: WGLC on netconf-event-notifications-13
Thread-Index: AQHUXC8cbkWCNEfz8kWboGz592BIZKUXwePggADIfdA=
Date: Wed, 10 Oct 2018 14:11:10 +0000
Message-ID: <cb486c1d35254010bb8ec8e948304fa7@XCH-RTP-013.cisco.com>
References: <C25DFAF6-04FC-44B4-B714-D6CE4E4EFF8C@juniper.net> <BBA82579FD347748BEADC4C445EA0F21B56C462C@NKGEML515-MBX.china.huawei.com>
In-Reply-To: <BBA82579FD347748BEADC4C445EA0F21B56C462C@NKGEML515-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.56.234]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Outbound-SMTP-Client: 64.101.220.153, xch-rtp-013.cisco.com
X-Outbound-Node: alln-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/cY5Bkx9c93izHHdZkZEmdeXJxaQ>
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 14:11:15 -0000

> From: Tianran Zhou, October 9, 2018 10:07 PM
> 
> 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.

Thanks for the comment Tianran.   In that paragraph we are saying that a way of encoding is needed to uniquely identify a specific identity within the module.  As you point out, It is true that there are not quotes around the "<modulename>" and  "<identityname>".  So you are right that it is not exactly JSON like (although there is some similarity).   

To remove the confusion, I just eliminated the text "using JSON encoding".  Is that sufficient for you?

Eric

 
> 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-notificat
> > io
> > 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-noti
> > fi
> > cations.
> >
> >
> > Thanks,
> > Kent (and Mahesh)
> >
> >
> >
> > _______________________________________________
> > Netconf mailing list
> > Netconf@ietf.org
> > https://www.ietf.org/mailman/listinfo/netconf
> 
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf