"Susan Hares" <[email protected]> wrote:
> Martin:
> 
> Does this mean if the I2RS model provides additional functions that are not
> a base configuration model that the xpath should just work? 

It means that the protocol specification does not lock down the set of
XPath functions available in a filter.

However, there is no standard way currently to declare new XPath
functions in YANG data models.  (see the expired
https://tools.ietf.org/html/draft-bjorklund-netmod-yang-xpath-extensions-00
for some ideas in this area).

(For the set of core XPath functions see http://www.w3.org/TR/xpath/#corelib)


/martin


> Xpath1- Config - ISIS Yang model that configures 
> Xpath2 - I2RS ISIS  empheral - inherits all the configuration state 
> ____       I2RS ISIS actions -     report on the interface changes on ISIS
> L1 interfaces
> 
> Is my I2RS ISIS model a combination of the inherited state and the I2RS
> actions? 
> 
> Sue 
> 
> 
> -----Original Message-----
> From: i2rs [mailto:[email protected]] On Behalf Of Martin Bjorklund
> Sent: Wednesday, September 24, 2014 3:27 AM
> To: [email protected]
> Cc: [email protected]; [email protected]; [email protected]
> Subject: Re: [i2rs] [netmod] Summary of discussion from netmod interim on
> i2rs requirements on netmod/netconf
> 
> Juergen Schoenwaelder <[email protected]> wrote:
> > On Mon, Sep 22, 2014 at 05:05:46PM -0400, Jeffrey Haas wrote:
> > > Some discussion was given to the filtering considerations.  
> > > Extending the filtering options of the ietf-inet-types module may be
> appropriate.
> > > [Juergen, is this an action item for yang 1.1?]
> > 
> > The YANG 1.1 issue Y20 is about adding a set of built-in xpath 
> > functions. I like to ask I2RS to tell us what functions they need. We 
> > do have IP prefix-length matching on our radar. If other functions are 
> > required, please let us know as soon as possible.
> > 
> > Now, this mostly is about the xpath function set that can be used in 
> > must and when expressions. You probably want to use them also in 
> > filtering expressions in the protocol. This is where things again 
> > become a protocol issues. Note that RFC 6241 says on page 17:
> > 
> >       The XPath expression is interpreted in the following context:
> > 
> >       [...]
> > 
> >       *  The function library is the core function library.
> 
> The quoted text is for the error-path.  For the filter, rfc 6241 says (p
> 67):
> 
>    o  The function library is the core function library, plus any
>       functions defined by the data model.
> 
> 
> /martin
> 
> _______________________________________________
> i2rs mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/i2rs
> 

_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs

Reply via email to