On Thu, Apr 20, 2017 at 9:26 AM, Kent Watsen <kwat...@juniper.net> wrote:
> Is there a typo in your capability line? s/netocnf/netconf/ > > Is your server also advertising jnx-ietf-netocnf-monitoring-dev in its > hello message? > > > > BTW, be aware that servers supporting RFC7950 no longer have "deviations=" > in the > > capability string, as the server is now expected to use YANG Library to > announce > > conformance. > > > Not quite. YANG 1.0 modules are still advertised according to RFC 6020. YANG 1.1 module capability URIs are left out of the <hello>. We ignore that rule and put them in the server <hello> because most client tools don't follow the RFC 7950 rules correctly. In our client, if the server advertises "module-set-id" then we read the /modules-state subtree (unless our cached data matches the module-set-id). We read /netconf-state/schemas if needed as well. > K. > > > Andy > > > On 4/20/17, 9:36 AM, "netmod on behalf of Dhirendra Trivedi" < > netmod-boun...@ietf.org on behalf of dhirutriv...@gmail.com> wrote: > > > > Hi All, > > > > We had requirement of implementing ietf-netconf-monitoring YANG model > > and we did it but partially. Now we need to advertise the deviation module > > in the netconf server capability. > > I tried doing it like > > <capability> > > urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring? > module=ietf-netconf-monitoring&deviations=jnx- > ietf-netocnf-monitoring-dev > > </capability> > > > > but it seems OpenDaylight controller is not taking it as valid capability. > Not sure > > if the capability is syntactically incorrect or OpenDaylight controller is > having bug. > > > > Is there way to validate the syntax of above capability? > > > > Regards, > > Dhirendra > > > > > > > > > > _______________________________________________ > netmod mailing list > netmod@ietf.org > https://www.ietf.org/mailman/listinfo/netmod > >
_______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
