Re: [Netconf] New version for draft-clemm-netconf-yang-push-01.txt

Hi Alex, Thanks.

It is clear about stream. But we can do the same stuff with filter. 

What is the difference between filter and stream is not clear? When I am subscribing to a stream, can I apply filters? If yes, then is the filter should be validated based on stream definition?

Cloud you please explain on filters of subscription and streams and relation?

Br,
Ambika

-----Original Message-----
From: Alexander Clemm (alex) 
Sent: Monday, July 13, 2015 2:19 AM
To: Ambika Prasad Tripathy (ambtripa); Eric Voit (evoit); Juergen Schoenwaelder
Cc: netconf@ietf.org
Subject: RE: [Netconf] New version for draft-clemm-netconf-yang-push-01.txt

Hi Ambika,

there is one conceptual stream that is predefined, datastore-push.  

One item for discussion concerns whether there should be other conceptual streams that are predefined:  specifically, one stream with all operational data (in effect, datastore-push with all config data removed) - e.g. "operational-push", and (potentiallly) one stream with all operational data minus counters (specifically for on-change subscriptions, which make little sense for ocunters).  While strictly speaking you could define filters on datastore-push instead, having a dedicated stream is more convenient as the articulation of a separate filter is more tedious and makes the mechanism harder to use.  

To let users define streams is strictly speaking not required, but makes for a "convenience function".  Among other things, again it saves subscribers from having to articulate filters, in particular if an administrator preconfigures corresponding streams.  

In any event, yes, the stream is a mandatory parameter.  You always subscribe to a stream (well, with datastore-push as a default, we can argue if it should therefore whether as a parameter it should be optional after all).  This is also one of the parameters that have  already introduced in RFC 5277 (create-subscription for notifications).  

Thanks
--- Alex

-----Original Message-----
From: Ambika Prasad Tripathy (ambtripa) 
Sent: Sunday, July 12, 2015 7:16 AM
To: Eric Voit (evoit); Juergen Schoenwaelder; Alexander Clemm (alex)
Cc: netconf@ietf.org
Subject: RE: [Netconf] New version for draft-clemm-netconf-yang-push-01.txt

Hi Alex/Eric,

Few doubts  

1) who will define streams? What is the practical use of it? Doesn't the filter will address the requirement?

2) If user is defining the streams, how to subscribe to the stream? Is stream is a mandatory parameter for subscription? 

Br,
Ambika Prasad Tripathy

-----Original Message-----
From: Netconf [mailto:netconf-bounces@ietf.org] On Behalf Of Eric Voit (evoit)
Sent: Friday, July 10, 2015 7:06 AM
To: Juergen Schoenwaelder
Cc: netconf@ietf.org
Subject: Re: [Netconf] New version for draft-clemm-netconf-yang-push-01.txt

> From: Juergen Schoenwaelder, July 10, 2015 3:30 AM
>
>> On Thu, Jul 09, 2015 at 08:59:52PM +0000, Eric Voit (evoit) wrote:
>> 
>>  (3) Are there filters which should be provided beyond RFC 5277 Subtree and Property Filters?
>>
>
> What is a 'Property Filter'?

RFC 5277 XPATH Filters for attribute match expressions is what I believe is achievable right now upon YANG objects.  But other PubSub  technologies like DDS (OMG) and MQTT (OASIS) can pass PubSub topic filters which are more flexible.  With this question I was hoping to leave space open for someone willing to argue for a solution here.

Eric

> /js

_______________________________________________
Netconf mailing list
Netconf@ietf.org
https://www.ietf.org/mailman/listinfo/netconf