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

["Reshad Rahman (rrahman)" <[e-mail]>]

Thanks Eric, makes sense.

From: "Eric Voit (evoit)" <[e-mail]>
Date: Friday, June 15, 2018 at 11:23 AM
To: "Reshad Rahman (rrahman)" <[e-mail]>, "[e-mail]" <[e-mail]>
Cc: "[e-mail]" <[e-mail]>
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.

Eric

Regards,
Reshad.

  container filters {
    description
      "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";
      description
        "A list of pre-configured filters that can be applied to
        subscriptions.";
      leaf identifier {
        type filter-id;
        description
          "An identifier to differentiate between filters.";
      }
      uses stream-filter-elements;
    }
  }