this case)
> > C) OpenConfig would have a "state" copy of node foo and reading that
> > would return 5 (a bit like B above, although with a 'well known
> > convention')
> >
> > A client could diff the running config vs the applied config and at least
>
t
> know there is a difference (but then there isn't anything standard to know a
> restart is needed to bring them into sync).
>
> Jason
>
>> -Original Message-
>> From: netmod On Behalf Of Hauck Wolfgang
>> (ETAS-DAP/XPC-Fe6)
>> Sent: Wed
iff the running config vs the applied config and at least know
there is a difference (but then there isn't anything standard to know a restart
is needed to bring them into sync).
Jason
> -Original Message-
> From: netmod On Behalf Of Hauck Wolfgang
> (ETAS-DAP/XPC-Fe6)
> S
Hi all!
The use case I think about is as follows:
A configuration node in a YANG model is effective only after a system-restart
(i.e. not only a restart of the NETCONF server). Now I would like to see from a
YANG model if a system-restart actually has to be carried out for that node.
E.g. as
