Hi,
Vladimir Vassilev <[email protected]> wrote:
>
> On 12/13/2017 04:26 PM, Vladimir Vassilev wrote:
> > Hi,
> >
> > On 12/13/2017 03:47 PM, Martin Bjorklund wrote:
> >
> >> Hi,
> >>
> >> Thanks for reporting this. I'll add the missing origin. But why did
> >> you think forwarding and mtu should be removed?
> > 1. IMO since <mtu> is not present in the <ipv4> container in the
> > Appendix A (<get-config>) example and does not have default value in
> > the model I still think it should be removed.
> Alternatively the ipv4/mtu node can be a good example of a
> origin="or:system" configuration.
Yes.
> >> In fact, I think I
> >> missed <enabled>,
> > 2. IMO both fixes adding <enabled> or removing <forwarding> should be
> > OK depending on the RFC6243 defined with-defaults capability
> > 'basic-mode' parameter advertised by the server. I was running the
> > example with basic-mode=explicit
Right. I now have this:
<!-- other parameters from ietf-interfaces omitted -->
<ipv4 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip">
<enabled or:origin="or:default">true</enabled>
<forwarding or:origin="or:default">false</forwarding>
<mtu or:origin="or:system">1500</mtu>
<address>
<ip>192.0.2.1</ip>
<prefix-length>24</prefix-length>
<origin>static</origin>
</address>
<neighbor or:origin="or:learned">
<ip>192.0.2.2</ip>
<link-layer-address>00:01:02:03:04:05</link-layer-address>
</neighbor>
</ipv4>
<ipv6 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip">
<enabled or:origin="or:default">true</enabled>
<forwarding or:origin="or:default">false</forwarding>
<mtu>1280</mtu>
...
Do you think this is ok?
/martin
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
