Hi Authors, Recently, we are preparing to use the L3VPN yang model, we check it with the yang-validator at https://yangcatalog.org/yangvalidator, and found the following errors:
Pyang Validation /var/yang/tmp/yangvalidator/yangvalidator-v2-workdir-TwlCIaOZ/[email protected]:508: error: node ietf-bgp::bgp is not found /var/yang/tmp/yangvalidator/yangvalidator-v2-workdir-TwlCIaOZ/[email protected]:515: error: node ietf-bgp::bgp is not found /var/yang/tmp/yangvalidator/yangvalidator-v2-workdir-TwlCIaOZ/[email protected]:523: error: node ietf-bgp::bgp is not found /var/yang/tmp/yangvalidator/yangvalidator-v2-workdir-TwlCIaOZ/[email protected]:532: error: node ietf-bgp::bgp is not found These errors appears to be model reference error. The yang info are defined like this: augment "/bgp:bgp/bgp:global/bgp:afi-safis/" + "bgp:afi-safi/bgp:l3vpn-ipv4-unicast" { description "Retain route targets for ASBR scenario"; uses retain-route-targets; uses vpn-pfx-limit; } Reference to the correct model, eg. ietf-bgp-sr , it looks like should be defined like this: augment "/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/" + "bgp:bgp/bgp:global/bgp:afi-safis/bgp:afi-safi/bgp:ipv4-unicast" { description "Augment BGP SAFI route"; uses common-bgp-route-grouping; } Please confirm this issue and hope to update the document to fix it. Regards, Haibo
_______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
