IETF Logo Mail Archive

Re: [Netconf] LC on subscribed-notifications-10 review

"Eric Voit (evoit)" <evoit@cisco.com> Mon, 26 March 2018 06:10 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 AAEF412DA03 for <netconf@ietfa.amsl.com>; Sun, 25 Mar 2018 23:10:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.531
X-Spam-Level:
X-Spam-Status: No, score=-14.531 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 boMC1gvQd9-r for <netconf@ietfa.amsl.com>; Sun, 25 Mar 2018 23:10:03 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BD8312D88E for <netconf@ietf.org>; Sun, 25 Mar 2018 23:10:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2127; q=dns/txt; s=iport; t=1522044602; x=1523254202; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=g1OEirQIbM+kycc5t+txhi8ALUT0FwDHJCtISn9Ehwo=; b=Ws5a1d8pPlKSp/FGJO0yu1m/STIzuvyR3KwyYFcR16mY3p/kQi9MCNSg T/Wv/6anm4lmtAyc7vI7FqxmY0ynt2hVN54JSqy+EJ1WYg+4avrfSCUbF rcjchZs+gvEQeY/YBMJF74izngY6rI0r07thRngo3X/0WQmPw4u8UmMrd w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B4AgB8jrha/4gNJK1eGQEBAQEBAQEBAQEBAQcBAQEBAYNBYXAoCphfgXSBEZJRFIFyCyOEYgKDeCE2FgECAQEBAQEBAmsohSUBAQEDAXcCBQcEAgEIDgMEAQEBLjIdCAIEDgUIE4RrCA+tXYg+ghUFh1iBVECEE4MTAoFGhW0DhwmFH4sXCAKFUIhXjEGJE4Y8AhETAYEkASMKJ4FScBWCfZBQb48SgRcBAQ
X-IronPort-AV: E=Sophos;i="5.48,363,1517875200"; d="scan'208";a="88802476"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Mar 2018 06:09:35 +0000
Received: from XCH-RTP-015.cisco.com (xch-rtp-015.cisco.com [64.101.220.155]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id w2Q69Yle014066 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 26 Mar 2018 06:09:35 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-015.cisco.com (64.101.220.155) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 26 Mar 2018 02:09:34 -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.1320.000; Mon, 26 Mar 2018 02:09:34 -0400
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: Martin Bjorklund <mbj@tail-f.com>
CC: "balazs.lengyel@ericsson.com" <balazs.lengyel@ericsson.com>, "kwatsen@juniper.net" <kwatsen@juniper.net>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [Netconf] LC on subscribed-notifications-10 review
Thread-Index: AQHTvkPdeAg1cO1SX0ecJskr0Q4sn6PbSnvggAFgBICAAToMsA==
Date: Mon, 26 Mar 2018 06:09:34 +0000
Message-ID: <de2c03f67652448ab5953a8af2a5b5f7@XCH-RTP-013.cisco.com>
References: <DA8A1569-826D-4744-B780-90CDA064D0BD@juniper.net> <ef9c874b-35dc-7f88-07de-fc6ce57d6d2b@ericsson.com> <a8b3a1f5d724498499f0c5ab291b40ae@XCH-RTP-013.cisco.com> <20180322.152519.755067735748831842.mbj@tail-f.com>
In-Reply-To: <20180322.152519.755067735748831842.mbj@tail-f.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.24.107.151]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/wlCSDZpGw7vlU2SLStt-Yylr6Js>
Subject: Re: [Netconf] LC on subscribed-notifications-10 review
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 26 Mar 2018 06:10:13 -0000

> From: Martin Bjorklund, March 22, 2018 11:25 AM
> 
> Hi,
> 
> "Eric Voit (evoit)" <evoit@cisco.com> wrote:
> > Hi Balazs,
> >
> > All changes listed below should be addressed.  The results can also be
> > seen in...
> > https://github.com/netconf-wg/rfc5277bis/blob/master/draft-ietf-
> netcon
> > f-subscribed-notifications-11.txt
> >
> > > -----Original Message-----
> > > From: Netconf <netconf-bounces@ietf.org> On Behalf Of Balazs Lengyel
> > > Sent: Saturday, March 17, 2018 7:01 PM
> > > To: Kent Watsen <kwatsen@juniper.net>; netconf@ietf.org
> > > Subject: Re: [Netconf] LC on subscribed-notifications-10 review
> > >
> > > Hello,
> > >
> > > My last call review. Sorry if some of the comments are already
> > > mentioned.
> > > I  think the document is in a good shape, ready to progress onwards
> > > (if my MAJOR comments are clarified.).
> > >
> > > Abstract:  "Also defined are delivery mechanisms for instances of
> > > the resulting notification messages."
> > > Aren't these in other drafts?
> >
> > Notification message definition mechanisms are defined in this
> > document.  But a complete solution requires a transport draft as well.
> 
> I agree with Balazs.  Shouldn't this sentence be removed?  If not, where in
> this document are these delivery mechanmisms defined?

I guess it depends on one's definition of delivery mechanisms.  To avoid all confusion, I reworded to:

This document defines mechanisms and a YANG Data Model enabling subscriber-specific subscriptions to a publisher's event streams.  Applying these elements allows a subscriber to request for and receive a continuous, custom feed of publisher generated information.

Eric

> [...]
> 
> > > P34) There really should be a filter example to show how it is
> > > applied against the notification.
> >
> > We took the same path as other YANG documents expressing XPATH or
> > subtree filters.
> >
> > In any case, filters documented for those examples should work here
> > without change.
> 
> Can you point to one such example?
> 
> 
> /martin

v2.23.0 | Report a Bug | By Email