RE: Notification Decision Point: Named Profiles

["Sharon Chisholm" <schishol@nortel.com>]

Hi

Putting them in the same named profile does not make them related. It
says that when applied to a subscription, that I apply some filters
against the contents of the stream, just like it does when I do it
directly against the create-subscription.

It is a collection of stuff that allows someone to easily reproduce a
particular subscription.

Sharon 

-----Original Message-----
From: David B Harrington [mailto:dbharrington@comcast.net] 
Sent: Tuesday, July 03, 2007 1:15 PM
To: 'Andy Bierman'; Chisholm, Sharon (CAR:ZZ00)
Cc: 'Netconf (E-mail)'
Subject: RE: Notification Decision Point: Named Profiles

Hi,

I think this is relevant to the question,
 
> Why is the filter coupled to a stream?
> There is nothing in the draft (or the design) that makes this 
> assumption.
> 
From the minutes of the Montreal interim meeting:
"h) Notification suppression filtering is data-model and 
   stream dependent."

My interpretation of this is that a filter might be (might need to be)
designed to apply to a particular (type of) stream. If, for example, the
SIP community developed a new stream format, then some SIP-specific
filters might only make protocol-sense with that stream.
Therefore, one might want to define the relevant stream as part of the
namedProfile.

dbh



--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>