Dear YANG Model experts:
Draft-ietf-netmod-acl-model-07 has matching criteria for Destination Address
and Source for IPv4 and IPv6 respectively, like:
[cid:image001.png@01D1A720.430CA7F0]
IDR FlowSpec also has defined YANG model for matching criteria for IPv6/
IPv4-prefix plus other header fi
Hi all,
I think one important question is how to flexibly use “Schema mount”.
Currently, it support mount the modules which be listed in the
ietf-yang-library.
But how to extend the mount? Or how to support other modules (these not include
in yang library)?
One example is draft-rtgyangdt-rtgwg-d
The chairs received the final IPR disclosure from Dan Romascanu. This means
that the draft is now officially adopted by the working group.
Authors,
Please resubmit the draft with the only change being to rename the draft to
draft-ietf-netmod-entitydt-entity-00.
Thank you!
Kent (and co-chairs
On Thu, May 5, 2016 at 7:44 AM, Balazs Lengyel
wrote:
> Hello,
>
> 1) Will mounted YANG modules be listed in the base ietf-yang-library? Even
> the mounted ones?
>
Does the server providing the mounted modules claim conformance
to those models?
IMO YANG mount breaks the "YANG API contract" if e
Hello,
1) Will mounted YANG modules be listed in the base
ietf-yang-library? Even the mounted ones?
2) What does conformance to a YANG module e.g. ietf-system mean
now? Do we need to load the module at the top level, or is it
enough to mount it “somewhere” in t
Hello,
As I see it the problem is that as we don't know the mount
relationships early. All you can say in the constraint is "point
at some interface". So having a specific path statement is not
feasible.
Using instance-identifiers may help. While it is har