Re: [Netconf] stream-filter list in draft-ietf-netconf-subscribed-notifications

"Reshad Rahman (rrahman)" <> Fri, 15 June 2018 16:15 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0B220130FE6; Fri, 15 Jun 2018 09:15:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id z_e_kPXp8lYz; Fri, 15 Jun 2018 09:15:30 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 70B4E131021; Fri, 15 Jun 2018 09:15:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=17774; q=dns/txt; s=iport; t=1529079321; x=1530288921; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=1dW6fpu2eqvXQVfVAFfJGI9Ps8jQEz49fcOSN3Fkmmo=; b=Kz/TaRfB5e9P+KCvOYNfKqkc98zJIk06VKWpocfvPAZQI0bGubcDGjsW 41knxR0Kvpq56sske90svfZNoVlcSKNieF2YK/rBue5WnyPjKTn/yjWMK UlwbbSoEtlUmk2s3jz+fAHy3pDkBdhVSozqKFsixOBMK/e2Q5K5jmI/Qg I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CaAQCr5SNb/5JdJa1cGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYJTdWJ/KAqDb5RWgX+PcIZ3CyyEQAIXgjshOBQBAgEBAQE?= =?us-ascii?q?BAQJtKIUoAQEBBCNUAhACAQgRAwECKwICAjAdCAIEAQ0FgyICgRtkqV+CHIh?= =?us-ascii?q?IgWiITIFUP4EzgmiFDAmCYTGCJAKIPIkAh1IJAo5/jTiRGgIREwGBJDQhgVJ?= =?us-ascii?q?wFTsqAYIYCZBGb4EVjioBgRkBAQ?=
X-IronPort-AV: E=Sophos;i="5.51,227,1526342400"; d="scan'208,217";a="407684420"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Jun 2018 16:15:20 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id w5FGFK58018924 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 15 Jun 2018 16:15:20 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1320.4; Fri, 15 Jun 2018 11:15:19 -0500
Received: from ([]) by ([]) with mapi id 15.00.1320.000; Fri, 15 Jun 2018 11:15:19 -0500
From: "Reshad Rahman (rrahman)" <>
To: "Eric Voit (evoit)" <>, "" <>
CC: "" <>
Thread-Topic: stream-filter list in draft-ietf-netconf-subscribed-notifications
Thread-Index: AQHUBLhL2E/DTySvS0ezm0kgqZ0mbKRhbFzAgAAjEoA=
Date: Fri, 15 Jun 2018 16:15:19 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/10.b.0.180311
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_08BA9A74FF84464E9F51EADD189E1554ciscocom_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [Netconf] stream-filter list in draft-ietf-netconf-subscribed-notifications
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Network Configuration WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 15 Jun 2018 16:15:44 -0000

Thanks Eric, makes sense.

From: "Eric Voit (evoit)" <>
Date: Friday, June 15, 2018 at 11:23 AM
To: "Reshad Rahman (rrahman)" <>om>, "" <>
Cc: "" <>
Subject: RE: stream-filter list in draft-ietf-netconf-subscribed-notifications

Hi Reshad,

From: Reshad Rahman, June 15, 2018 10:51 AM

Minor question: why don’t the names of the container wrapper (filters) and the list (stream-filter) match (e.g. filters and filter or stream-filters and stream-filter), is it because we could have another list with other types of filters?

<Eric>  This is exactly why.  YANG-Push augments in selection-filters.

If that’s the case, shouldn’t there be a container wrapper stream-filters for the list stream-filter. Looked in the archive and didn’t find discussions on this.

<Eric> The container “filters” is because there it is a top level container.  It doesn’t seem necessary to have independent containers underneath for the lists of stream-filters and selection-filters.



  container filters {
      "This container contains a list of configurable filters
       that can be applied to subscriptions.  This facilitates
       the reuse of complex filters once defined.";
    list stream-filter {
      key "identifier";
        "A list of pre-configured filters that can be applied to
      leaf identifier {
        type filter-id;
          "An identifier to differentiate between filters.";
      uses stream-filter-elements;