An updated draft for YANG subscriptions was posted in NETCONF WG earlier in the
week at draft-ietf-netconf-yang-push. Enhancements include:
* Refined RPC & Notification definitions
* Multiple targeted YANG subtrees within a single subscription
- includes custom filters for each target
*
I¹m not aware of any IPR that applies to this draft too.
On 2/26/16, 11:16 AM, "Clyde Wildes (cwildes)" wrote:
>No, I'm not aware of any IPR that applies to this draft
>
>
>
>
>
>On 2/22/16, 5:22 PM, "Lou Berger" wrote:
>
>>Authors, Contributors, WG,
>>
Rob,
I think chris spoke to this (indirectly) in an earlier mail -- that
the current approach of not specifying is most flexible from a future
proof stand point, i.e., we really don't want to specify based on what
exists in today's rapidly moving environment.
We have also discussed the
> On 26 Feb 2016, at 15:33, Xufeng Liu wrote:
>
> Hi Acee and Lada,
>
> Have a question: the schema hierarchy will be different after the changes.
> Is the following expected? We will have ro branch and rw branch split in the
> middle of the tree after mounting?
WG,
An update on this topic is overdue (my fault). A large part of the
delay has been figuring out how to proceed with the conclusions from the
analysis. Basically the/my conclusion is that none of the solution
fulfills all requirements/considerations and that having a discussion
centered
Lou, Martin,
Is the network-instance schema-mount (from
draft-rtgyangdt-rtgwg-device-model) an example of where it would be
useful to indicate which modules would be expected to be mounted at that
point?
Certainly it would seem that there are particular modules that you would
expect to be
Hi,
as a part of synchronization of the routing data models that are being
developed by the NETMOD and RTG working groups, the authors of
draft-ietf-netmod-routing-cfg propose to remove the routing-instance level in
the data hierarchy, and leave it to structural-mount/YSDL to provide a top
Hi,
I have posted a new version of the structural mount draft, based on
feedback from the interim. This version adds an option to require
mounting of ietf-yang-library. I also discuss two alternative
solutions in an appendix.
/martin
--- Begin Message ---
A new version of I-D,
Hi Lada,
Hi Benoit,
this was discussed a while ago in this thread:
https://mailarchive.ietf.org/arch/msg/netmod/TehrMAboX-cMmmX537rs81DNl3I
tl;dr: The WG decision then was to introduce a new type in ietf-inet-types, namely
"dotted-quad", that explicitly does NOT have the semantics of an