On 02/05/17 10:25, Martin Bjorklund wrote:
> Robert Varga wrote:
>> On 20/04/17 18:35, Andy Bierman wrote:
>>>
>>> Yes -- it looks correct.
>>> The structure is defined in RFC 6020:
>>> https://tools.ietf.org/html/rfc6020#section-5.6.4
>>>
>>
>> Hello Andy,
>>
>> One thing that is not
Robert Varga wrote:
> On 20/04/17 18:35, Andy Bierman wrote:
> >
> > Yes -- it looks correct.
> > The structure is defined in RFC 6020:
> > https://tools.ietf.org/html/rfc6020#section-5.6.4
> >
>
> Hello Andy,
>
> One thing that is not quite clear in RFC6020 due to not being clear
On 20/04/17 18:35, Andy Bierman wrote:
>
> Yes -- it looks correct.
> The structure is defined in RFC 6020:
> https://tools.ietf.org/html/rfc6020#section-5.6.4
>
Hello Andy,
One thing that is not quite clear in RFC6020 due to not being clear what
'supported module' means.
Should deviations be
On Thu, Apr 20, 2017 at 9:26 AM, Kent Watsen 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
On Thu, Apr 20, 2017 at 6:36 AM, Dhirendra Trivedi
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
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
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