Re: [Netconf] comments on draft-ietf-netconf-subscribed-notifications-12
Tianran Zhou <zhoutianran@huawei.com> Wed, 20 June 2018 22:42 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 DEEA21277BB for <netconf@ietfa.amsl.com>; Wed, 20 Jun 2018 15:42:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable 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 bBRaDIs3hSJj for <netconf@ietfa.amsl.com>; Wed, 20 Jun 2018 15:42:43 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 00855130E2F for <netconf@ietf.org>; Wed, 20 Jun 2018 15:42:42 -0700 (PDT)
Received: from lhreml709-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 9F11F50AB0217 for <netconf@ietf.org>; Wed, 20 Jun 2018 23:42:38 +0100 (IST)
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml709-cah.china.huawei.com (10.201.108.32) with Microsoft SMTP Server (TLS) id 14.3.382.0; Wed, 20 Jun 2018 23:42:40 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0382.000; Thu, 21 Jun 2018 06:42:29 +0800
From: Tianran Zhou <zhoutianran@huawei.com>
To: Andy Bierman <andy@yumaworks.com>, "Eric Voit (evoit)" <evoit=40cisco.com@dmarc.ietf.org>
CC: alex <alex@clemm.org>, netconf <netconf@ietf.org>
Thread-Topic: [Netconf] comments on draft-ietf-netconf-subscribed-notifications-12
Thread-Index: AQHT/nTNearMGgWcrk2d9jozIllFDaRU1FsAgAC3XYCAAEcoAIAAEmGAgAAJooCABrN1gIAABFCAgAAUYgCAAA8nAIAAfEqAgACO9YCAAAdKAIABEdsAgACV3YCAABa5gIAAxceAgABilgCABuq5AIAAGpAAgAACL4CAAggGjw==
Date: Wed, 20 Jun 2018 22:42:28 +0000
Message-ID: <BBA82579FD347748BEADC4C445EA0F21B55D00ED@NKGEML515-MBX.china.huawei.com>
References: <20180613160206.gkutjhxigdxpv2uz@anna.jacobs.jacobs-university.de> <20180614.102216.2199378020340361225.mbj@tail-f.com> <f6f66d0c0a444f2bb0fc770082450037@XCH-RTP-013.cisco.com> <20180614.203959.786029239464099510.mbj@tail-f.com> <20180615062751.obzdeco6oka3ekue@anna.jacobs.jacobs-university.de> <ac1a7a7480da46d4841fcd1bd0ea4ddc@XCH-RTP-013.cisco.com> <A0ECF1FF-FF88-4BE3-A722-D681B9CF6F78@juniper.net> <03a8630197c04815a3aa6d85d667f678@XCH-RTP-013.cisco.com>, <CABCOCHSQvaJ+YZT-rGnmoR=pOFXAEGYPSUg4z_9W2-fopsFTYg@mail.gmail.com>
In-Reply-To: <CABCOCHSQvaJ+YZT-rGnmoR=pOFXAEGYPSUg4z_9W2-fopsFTYg@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_BBA82579FD347748BEADC4C445EA0F21B55D00EDNKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/4LqKId6u6XoHNc3RbExglXN_GyA>
Subject: Re: [Netconf] comments on draft-ietf-netconf-subscribed-notifications-12
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.26
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, 20 Jun 2018 22:42:45 -0000
This makes sense to me. I would like to see messages like syslog can alse be streamed by this notificatuons. Tianran ________________________________ Sent from WeLink 发件人: Andy Bierman 收件人: Eric Voit (evoit)<evoit=40cisco.com@dmarc.ietf.org<mailto:evoit=40cisco.com@dmarc.ietf.org>> 抄送: alex<alex@clemm.org<mailto:alex@clemm.org>>;netconf<netconf@ietf.org<mailto:netconf@ietf.org>> 主题: Re: [Netconf] comments on draft-ietf-netconf-subscribed-notifications-12 时间: 2018-06-20 07:42:09 On Tue, Jun 19, 2018 at 4:33 PM, Eric Voit (evoit) <evoit=40cisco.com@dmarc.ietf.org<mailto:evoit=40cisco.com@dmarc.ietf.org>> wrote: > From: Kent Watsen, June 19, 2018 5:58 PM > > > > > > An event record is not necessarily a YANG notification, as the > > > > > event record's payload might not be driven by the result of a > > > > > YANG statement. > > > > > > > > I don't get this. Can you give an example of when an event record > > > > is not defined as a YANG "notification"? > > > > > > Why do we care about non-YANG-defined notification messages? How are > > > systems expected to interoperate on such opaque data blobs? > > > > Opaque data blobs is what RFC-5277 can carry. The WG asked to update > > RFC-5277 using the improved control plane of YANG-Push. This is what > > makes up the documents in LC. > > > > <snip/> > > > > The drafts in LC adds RPC / signaling mechanisms. The opaque data blobs are > not in scope. > > RFC 5277 may have allowed opaque data blocks, but I think that we should try > to bury that support now. Can this document say that all notifications MUST > be defined by a YANG-defined "notification" statement? Could this break in > compatibility be advertised somehow? MUST be defined in YANG is a bit strong. I would say SHOULD be defined in YANG, for the "NETCONF" stream. Other streams do not have to use YANG notification statements. Andy I had always seen as subscribed-notifications as a control plane improvement to RFC-5277. Explicitly excluding XSD, SYSLOG, vendor structures, etc. seems unnecessary. I can ping a few people who have legacy implementations which might be closer to this than I. Narrowing the scope in this way should be broadly discussed. > > It would be helpful to get some comments on draft-ietf-netconf-notification- > messages. > > This draft address improvements to the opaque data blobs. > > Perhaps tease us with a little more detail? ;) Pretty much all the common headers in Section 3 and the message bundling in Section 4 are both improvements which are relevant to this thread. Tianran likely will have some new headers he wants added as part of the multi-line card work. Eric > Kent > _______________________________________________ Netconf mailing list Netconf@ietf.org<mailto:Netconf@ietf.org> https://www.ietf.org/mailman/listinfo/netconf
- Re: [Netconf] comments on draft-ietf-netconf-subs… Eric Voit (evoit)
- Re: [Netconf] comments on draft-ietf-netconf-subs… Tianran Zhou
- Re: [Netconf] comments on draft-ietf-netconf-subs… Martin Bjorklund
- Re: [Netconf] comments on draft-ietf-netconf-subs… Tianran Zhou
- Re: [Netconf] comments on draft-ietf-netconf-subs… Alexander Clemm
- Re: [Netconf] comments on draft-ietf-netconf-subs… Eric Voit (evoit)
- Re: [Netconf] comments on draft-ietf-netconf-subs… Martin Bjorklund
- Re: [Netconf] comments on draft-ietf-netconf-subs… Eric Voit (evoit)
- Re: [Netconf] comments on draft-ietf-netconf-subs… Kent Watsen
- Re: [Netconf] comments on draft-ietf-netconf-subs… Andy Bierman
- Re: [Netconf] comments on draft-ietf-netconf-subs… Eric Voit (evoit)
- Re: [Netconf] comments on draft-ietf-netconf-subs… Kent Watsen
- Re: [Netconf] comments on draft-ietf-netconf-subs… Kent Watsen
- Re: [Netconf] comments on draft-ietf-netconf-subs… Eric Voit (evoit)
- Re: [Netconf] comments on draft-ietf-netconf-subs… Eric Voit (evoit)
- Re: [Netconf] comments on draft-ietf-netconf-subs… Juergen Schoenwaelder
- Re: [Netconf] comments on draft-ietf-netconf-subs… Henk Birkholz
- Re: [Netconf] comments on draft-ietf-netconf-subs… Martin Bjorklund
- Re: [Netconf] comments on draft-ietf-netconf-subs… Juergen Schoenwaelder
- Re: [Netconf] comments on draft-ietf-netconf-subs… Eric Voit (evoit)
- Re: [Netconf] comments on draft-ietf-netconf-subs… Martin Bjorklund
- Re: [Netconf] comments on draft-ietf-netconf-subs… Eric Voit (evoit)
- Re: [Netconf] comments on draft-ietf-netconf-subs… Martin Bjorklund
- Re: [Netconf] comments on draft-ietf-netconf-subs… Martin Bjorklund
- Re: [Netconf] comments on draft-ietf-netconf-subs… Eric Voit (evoit)
- Re: [Netconf] comments on draft-ietf-netconf-subs… Juergen Schoenwaelder
- Re: [Netconf] comments on draft-ietf-netconf-subs… Alexander Clemm
- Re: [Netconf] comments on draft-ietf-netconf-subs… Eric Voit (evoit)
- Re: [Netconf] comments on draft-ietf-netconf-subs… Juergen Schoenwaelder
- Re: [Netconf] comments on draft-ietf-netconf-subs… Eric Voit (evoit)
- Re: [Netconf] comments on draft-ietf-netconf-subs… Eric Voit (evoit)
- Re: [Netconf] comments on draft-ietf-netconf-subs… Martin Bjorklund
- Re: [Netconf] comments on draft-ietf-netconf-subs… Juergen Schoenwaelder
- Re: [Netconf] comments on draft-ietf-netconf-subs… Alexander Clemm
- Re: [Netconf] comments on draft-ietf-netconf-subs… Kent Watsen
- [Netconf] comments on draft-ietf-netconf-subscrib… Martin Bjorklund
- Re: [Netconf] comments on draft-ietf-netconf-subs… Eric Voit (evoit)
- Re: [Netconf] comments on draft-ietf-netconf-subs… Martin Bjorklund
- Re: [Netconf] comments on draft-ietf-netconf-subs… Eric Voit (evoit)
- Re: [Netconf] comments on draft-ietf-netconf-subs… Eric Voit (evoit)
- Re: [Netconf] comments on draft-ietf-netconf-subs… Martin Bjorklund
- Re: [Netconf] comments on draft-ietf-netconf-subs… Eric Voit (evoit)