On Mon, Feb 15, 2016 at 7:16 AM, Ladislav Lhotka <[email protected]> wrote: > Behcet Sarikaya <[email protected]> writes: > >> Hi Lada, >> >> When trying to validate NETCONF get reply in Appendix D, I ran into a >> problem: > > I assume you mean Appendix D in RFC 7223. >
No I meant your draft. Yes, RFC 7223 also has a similar annex, thanks for pointing it out. >> >> This annex introduces a namespace iana-if-types and none of the YANG >> modules of ietf-routing-cfg is dependent on this namespace. >> As a result, the NETCONF tool that I am using could not recognize >> ethernetCdmacd when it comes to the line >> >> <if:type>ianaift:ethernetCsmacd</if:type> >> >> I know that iana-if-types is defined at the beginning of the rpc reply >> but it seems like those declarations are simply ignored. I noticed that in RFC 7223 iana-if-types (mainly from RFC 2863, or interfaces MIB) is imported, so I did not try it but I can say that it would work on that example. > > Pyang validates this. You have to include the iana-if-types module into > the data model, as explained here: > > https://github.com/mbj4668/pyang/wiki/Tutorial#yang-data-model > > If you use another tool than pyang, then the procedure will be different > but the principle is the same - ietf-if-types needs to be a part of the > data model, otherwise the interface type identities are unknown. > This is what I was pointing to. I did check every YANG module that draft-ietf-netmod-routing-cfg uses, in no place iana-if-types modules is imported. I wonder how you got the <get> reply in Appendix D, you must have added iana-if-types somewhere. Regards, Behcet > Lada > >> >> Do you offer any solution? >> >> Regards, >> >> Behcet > > -- > Ladislav Lhotka, CZ.NIC Labs > PGP Key ID: E74E8C0C _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
