YANG Model Compilation Compilation Results (pyang --ietf). 2.6.1 Compilation Results (pyang). Note: also generates errors for imported files. 2.6.1 Compilation Results (confdc). Note: also generates errors for imported files. confd-8.0 Compilation Results (yangdump-pro). Note: also generates errors for imported files. yangdump-sdk 21.10-12 Compilation Results (yanglint -i). Note: also generates errors for imported files. yanglint 2.1.111
example-dhcpv6-class-select@2022-06-20.yang PASSED WITH WARNINGS     example-dhcpv6-class-select@2022-06-20.yang:1: warning: RFC 8407: 4.1: the module name should start with one of the strings "ietf-" or "iana-"

example-dhcpv6-class-select@2022-06-20.yang:4: warning: RFC 8407: 4.9: namespace value should be "urn:ietf:params:xml:ns:yang:example-dhcpv6-class-select"		    
example-dhcpv6-opt-sip-serv@2022-06-20.yang PASSED WITH WARNINGS     example-dhcpv6-opt-sip-serv@2022-06-20.yang:1: warning: RFC 8407: 4.1: the module name should start with one of the strings "ietf-" or "iana-"

example-dhcpv6-opt-sip-serv@2022-06-20.yang:4: warning: RFC 8407: 4.9: namespace value should be "urn:ietf:params:xml:ns:yang:example-dhcpv6-opt-sip-serv"		    
example-dhcpv6-server-conf@2022-06-20.yang PASSED WITH WARNINGS     example-dhcpv6-server-conf@2022-06-20.yang:1: warning: RFC 8407: 4.1: the module name should start with one of the strings "ietf-" or "iana-"

example-dhcpv6-server-conf@2022-06-20.yang:4: warning: RFC 8407: 4.9: namespace value should be "urn:ietf:params:xml:ns:yang:example-dhcpv6-server-conf"		    
iana-bfd-types@2021-10-21.yang PASSED          
iana-bgp-l2-encaps@2022-09-20.yang PASSED          
iana-crypt-hash@2014-08-06.yang PASSED          
iana-dots-signal-channel@2020-05-28.yang PASSED          
iana-dots-signal-channel@2021-09-02.yang PASSED          
iana-hardware@2018-03-13.yang PASSED          
iana-if-type@2014-05-08.yang FAILED     Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" iana-if-type@2014-05-08.yang --ietf 2>&1":
iana-if-type@2014-05-08.yang:62: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:65: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:68: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:71: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:74: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:98: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:101: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:104: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:117: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:120: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:123: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:126: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:131: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:136: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:172: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:175: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:183: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:225: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:256: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:267: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:272: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:275: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:278: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:289: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:292: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:295: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:309: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement

iana-if-type@2014-05-08.yang:312: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement		    
iana-msd-types@2025-01-10.yang PASSED          
iana-pseudowire-types@2022-09-20.yang PASSED          
iana-routing-types@2017-12-04.yang PASSED          
iana-tls-profile@2025-04-18.yang PASSED          
iana-tunnel-type@2019-11-16.yang PASSED          
ietf-access-control-list@2019-03-04.yang FAILED     Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" ietf-access-control-list@2019-03-04.yang --ietf 2>&1":
ietf-access-control-list@2019-03-04.yang:63: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing or is not correct (see pyang --ietf-help for details).

ietf-access-control-list@2019-03-04.yang:136: error: keyword "if-feature" not in canonical order (see RFC 7950, Section 14)

ietf-access-control-list@2019-03-04.yang:146: error: keyword "if-feature" not in canonical order (see RFC 7950, Section 14)

ietf-access-control-list@2019-03-04.yang:156: error: keyword "if-feature" not in canonical order (see RFC 7950, Section 14)

ietf-access-control-list@2019-03-04.yang:167: error: keyword "if-feature" not in canonical order (see RFC 7950, Section 14)

ietf-access-control-list@2019-03-04.yang:178: error: keyword "if-feature" not in canonical order (see RFC 7950, Section 14)

ietf-access-control-list@2019-03-04.yang:189: error: keyword "if-feature" not in canonical order (see RFC 7950, Section 14)		    
ietf-acl-tls@2025-04-18.yang PASSED          
ietf-acldns@2019-01-28.yang PASSED WITH WARNINGS     ietf-acldns@2019-01-28.yang:41: warning: RFC 8407: Appendix B: The text about which RFC this module is part of seems to be missing or is not correct (see pyang --ietf-help for details).    
ietf-alarms-x733@2019-09-11.yang PASSED          
ietf-alarms@2019-09-11.yang PASSED          
ietf-babel@2024-10-10.yang PASSED          
ietf-bfd-ip-mh@2021-10-21.yang PASSED          
ietf-bfd-ip-mh@2022-09-22.yang PASSED          
ietf-bfd-ip-sh@2021-10-21.yang PASSED          
ietf-bfd-ip-sh@2022-09-22.yang PASSED          
ietf-bfd-lag@2021-10-21.yang PASSED          
ietf-bfd-lag@2022-09-22.yang PASSED          
ietf-bfd-large@2025-04-04.yang PASSED          
ietf-bfd-mpls@2021-10-21.yang PASSED          
ietf-bfd-mpls@2022-09-22.yang PASSED          
ietf-bfd-types@2021-10-21.yang PASSED          
ietf-bfd-types@2022-09-22.yang PASSED          
ietf-bfd-unsolicited@2023-08-31.yang PASSED          
ietf-bfd@2021-10-21.yang PASSED          
ietf-bfd@2022-09-22.yang PASSED          
ietf-complex-types@2011-03-15.yang FAILED     Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" ietf-complex-types@2011-03-15.yang --ietf 2>&1":
ietf-complex-types@2011-03-15.yang:34: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement

ietf-complex-types@2011-03-15.yang:41: error: keyword "argument" not in canonical order (see RFC 6020, Section 12)

ietf-complex-types@2011-03-15.yang:49: error: keyword "argument" not in canonical order (see RFC 6020, Section 12)

ietf-complex-types@2011-03-15.yang:56: error: keyword "argument" not in canonical order (see RFC 6020, Section 12)

ietf-complex-types@2011-03-15.yang:63: error: keyword "argument" not in canonical order (see RFC 6020, Section 12)

ietf-complex-types@2011-03-15.yang:72: error: keyword "argument" not in canonical order (see RFC 6020, Section 12)

ietf-complex-types@2011-03-15.yang:81: error: keyword "argument" not in canonical order (see RFC 6020, Section 12)		    
ietf-connection-oriented-oam@2019-04-16.yang PASSED          
ietf-connectionless-oam@2019-04-16.yang FAILED       libyang err : Problem occurred while running command "yanglint -i -p /var/yang/yang/modules/ /var/yang/ietf/YANG-rfc/ietf-connectionless-oam@2019-04-16.yang 2>&1":
libyang err : Ext plugin "ly2 schema mount v1": Extension "yangmnt:mount-point" instance allowed only in container or list statement. (Path "/ietf-connectionless-oam:test-point-location-info/root/{extension='yangmnt:mount-point'}/root".)		  
ietf-crypto-types@2024-10-10.yang PASSED          
ietf-datastores@2018-02-14.yang PASSED          
ietf-dc-fabric-topology-state@2019-02-25.yang PASSED          
ietf-dc-fabric-topology@2019-02-25.yang PASSED          
ietf-dc-fabric-types@2019-02-25.yang PASSED          
ietf-detnet@2024-10-28.yang PASSED          
ietf-dhcpv6-client@2022-06-20.yang PASSED          
ietf-dhcpv6-common@2022-06-20.yang PASSED          
ietf-dhcpv6-relay@2022-06-20.yang PASSED          
ietf-dhcpv6-server@2022-06-20.yang PASSED          
ietf-dots-call-home@2021-12-09.yang FAILED   ietf-dots-call-home@2021-12-09.yang:11: warning: imported module "ietf-dots-signal-channel" not used ietf-dots-call-home@2021-12-09.yang:11: warning: imported module "ietf-dots-signal-channel" not used libyang err : Problem occurred while running command "yanglint -i -p /var/yang/yang/modules/ /var/yang/ietf/YANG-rfc/ietf-dots-call-home@2021-12-09.yang 2>&1":
libyang err : Not found node "dots-data" in path. (Schema location "/ietf-dots-signal-channel:message-type/mitigation-scope/scope/direction/server-to-client-only/conflict-information/conflict-scope/acl-list/acl-name".)		  
ietf-dots-data-channel@2020-05-28.yang PASSED          
ietf-dots-mapping@2022-06-20.yang PASSED          
ietf-dots-robust-trans@2023-02-28.yang FAILED   ietf-dots-robust-trans@2023-02-28.yang:6: warning: imported module "ietf-dots-signal-channel" not used ietf-dots-robust-trans@2023-02-28.yang:6: warning: imported module "ietf-dots-signal-channel" not used libyang err : Problem occurred while running command "yanglint -i -p /var/yang/yang/modules/ /var/yang/ietf/YANG-rfc/ietf-dots-robust-trans@2023-02-28.yang 2>&1":
libyang err : Ext plugin "ly2 structure v1": Extension sx:augment-structure does not define any data-def-stmt statements. (Path "/ietf-dots-robust-trans:{extension='sx:augment-structure'}//dots-signal:dots-signal/dots-signal:message-type/dots-signal:signal-config/dots-signal:mitigating-config".)		  
ietf-dots-signal-channel@2020-05-28.yang PASSED          
ietf-dots-signal-channel@2021-09-02.yang FAILED       libyang err : Problem occurred while running command "yanglint -i -p /var/yang/yang/modules/ /var/yang/ietf/YANG-rfc/ietf-dots-signal-channel@2021-09-02.yang 2>&1":
libyang err : Not found node "dots-data" in path. (Schema location "/ietf-dots-signal-channel:message-type/mitigation-scope/scope/direction/server-to-client-only/conflict-information/conflict-scope/acl-list/acl-name".)		  
ietf-dots-signal-control@2021-09-02.yang FAILED   ietf-dots-signal-control@2021-09-02.yang:6: warning: imported module "ietf-dots-signal-channel" not used ietf-dots-signal-control@2021-09-02.yang:6: warning: imported module "ietf-dots-signal-channel" not used libyang err : Problem occurred while running command "yanglint -i -p /var/yang/yang/modules/ /var/yang/ietf/YANG-rfc/ietf-dots-signal-control@2021-09-02.yang 2>&1":
libyang err : Not found node "dots-data" in path. (Schema location "/ietf-dots-signal-channel:message-type/mitigation-scope/scope/direction/server-to-client-only/conflict-information/conflict-scope/acl-list/acl-name".)		  
ietf-dots-telemetry@2022-06-20.yang FAILED   ietf-dots-telemetry@2022-06-20.yang:6: warning: imported module "ietf-dots-signal-channel" not used ietf-dots-telemetry@2022-06-20.yang:6: warning: imported module "ietf-dots-signal-channel" not used libyang err : Problem occurred while running command "yanglint -i -p /var/yang/yang/modules/ /var/yang/ietf/YANG-rfc/ietf-dots-telemetry@2022-06-20.yang 2>&1":
libyang err : Not found node "dots-data" in path. (Schema location "/ietf-dots-signal-channel:message-type/mitigation-scope/scope/direction/server-to-client-only/conflict-information/conflict-scope/acl-list/acl-name".)		  
ietf-dslite@2019-01-10.yang PASSED          
ietf-ethernet-segment@2022-09-20.yang PASSED          
ietf-ethertypes@2019-03-04.yang PASSED WITH WARNINGS     ietf-ethertypes@2019-03-04.yang:35: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing or is not correct (see pyang --ietf-help for details).    
ietf-factory-default@2020-08-31.yang PASSED          
ietf-foo@2016-03-20.yang PASSED WITH WARNINGS     ietf-foo@2016-03-20.yang:7: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing or is not correct (see pyang --ietf-help for details).

ietf-foo@2016-03-20.yang:7: warning: RFC 8407: Appendix B: The text about which RFC this module is part of seems to be missing or is not correct (see pyang --ietf-help for details).		    
ietf-geo-location@2022-02-11.yang PASSED          
ietf-hardware-state@2018-03-13.yang PASSED WITH WARNINGS     ietf-hardware-state@2018-03-13.yang:69: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).    
ietf-hardware@2018-03-13.yang PASSED WITH WARNINGS     ietf-hardware@2018-03-13.yang:347: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).    
ietf-i2nsf-ike@2021-07-14.yang PASSED          
ietf-i2nsf-ikec@2021-07-14.yang PASSED          
ietf-i2nsf-ikeless@2021-07-14.yang PASSED          
ietf-i2rs-rib@2018-09-13.yang PASSED WITH WARNINGS     ietf-i2rs-rib@2018-09-13.yang:320: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).    
ietf-igmp-mld-proxy@2023-05-30.yang PASSED          
ietf-igmp-mld-snooping@2022-01-31.yang PASSED          
ietf-igmp-mld@2019-11-01.yang PASSED          
ietf-inet-types@2010-09-24.yang FAILED     Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" ietf-inet-types@2010-09-24.yang --ietf 2>&1":
ietf-inet-types@2010-09-24.yang:317: error: keyword "length" not in canonical order (see RFC 6020, Section 12)

ietf-inet-types@2010-09-24.yang:354: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).		    
ietf-inet-types@2013-07-15.yang FAILED     Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" ietf-inet-types@2013-07-15.yang --ietf 2>&1":
ietf-inet-types@2013-07-15.yang:361: error: keyword "length" not in canonical order (see RFC 6020, Section 12)

ietf-inet-types@2013-07-15.yang:397: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).		    
ietf-interface-protection@2019-06-19.yang PASSED          
ietf-interfaces@2014-05-08.yang PASSED WITH WARNINGS     ietf-interfaces@2014-05-08.yang:162: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).

ietf-interfaces@2014-05-08.yang:243: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement

ietf-interfaces@2014-05-08.yang:246: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement		    
ietf-interfaces@2018-02-20.yang PASSED WITH WARNINGS     ietf-interfaces@2018-02-20.yang:160: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).    
ietf-ioam@2024-08-27.yang PASSED          
ietf-ip@2014-06-16.yang PASSED          
ietf-ip@2018-02-22.yang PASSED          
ietf-ipfix-psamp@2012-09-05.yang FAILED ietf-ipfix-psamp@2012-09-05.yang:259:16: warning: illegal character after \

ietf-ipfix-psamp@2012-09-05.yang:279:16: warning: illegal character after \

ietf-ipfix-psamp@2012-09-05.yang:279:21: warning: illegal character after \		 ietf-ipfix-psamp@2012-09-05.yang:259: warning: the escape sequence "\S" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning

ietf-ipfix-psamp@2012-09-05.yang:279: warning: the escape sequence "\S" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning		 ietf-ipfix-psamp@2012-09-05.yang:34: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing or is not correct (see pyang --ietf-help for details).

ietf-ipfix-psamp@2012-09-05.yang:34: warning: RFC 8407: Appendix B: The text about which RFC this module is part of seems to be missing or is not correct (see pyang --ietf-help for details).

ietf-ipfix-psamp@2012-09-05.yang:259: warning: the escape sequence "\S" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning

ietf-ipfix-psamp@2012-09-05.yang:279: warning: the escape sequence "\S" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning

ietf-ipfix-psamp@2012-09-05.yang:321: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).		 libyang err : Problem occurred while running command "yanglint -i -p /var/yang/yang/modules/ /var/yang/ietf/YANG-rfc/ietf-ipfix-psamp@2012-09-05.yang 2>&1":
libyang err : Double-quoted string unknown special character '\S'. (Line number 259.)

libyang err : Parsing module "ietf-ipfix-psamp" failed.		  
ietf-ipsec-iptfs@2023-01-31.yang PASSED          
ietf-ipv4-unicast-routing@2016-11-04.yang PASSED WITH WARNINGS     ietf-ipv4-unicast-routing@2016-11-04.yang:55: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).    
ietf-ipv4-unicast-routing@2018-03-13.yang PASSED          
ietf-ipv6-unicast-routing@2016-11-04.yang PASSED WITH WARNINGS     ietf-ipv6-unicast-routing@2016-11-04.yang:60: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).    
ietf-ipv6-unicast-routing@2018-03-13.yang PASSED          
ietf-isis-reverse-metric@2022-10-19.yang PASSED          
ietf-isis@2022-10-19.yang PASSED          
ietf-key-chain@2017-06-15.yang FAILED     Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" ietf-key-chain@2017-06-15.yang --ietf 2>&1":
ietf-key-chain@2017-06-15.yang:80: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).

ietf-key-chain@2017-06-15.yang:107: error: keyword "if-feature" not in canonical order (see RFC 7950, Section 14)

ietf-key-chain@2017-06-15.yang:114: error: keyword "if-feature" not in canonical order (see RFC 7950, Section 14)

ietf-key-chain@2017-06-15.yang:158: error: keyword "if-feature" not in canonical order (see RFC 7950, Section 14)

ietf-key-chain@2017-06-15.yang:165: error: keyword "if-feature" not in canonical order (see RFC 7950, Section 14)		    
ietf-keystore@2024-10-10.yang PASSED          
ietf-l2-topology-state@2020-11-15.yang PASSED          
ietf-l2-topology@2020-11-15.yang PASSED          
ietf-l2vpn-ntw@2022-09-20.yang FAILED         Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro.conf /var/yang/ietf/YANG-rfc/ietf-l2vpn-ntw@2022-09-20.yang 2>&1":
Error: leaf 'direction' has invalid default value (vpn-common:both)
ietf-l2vpn-ntw@2022-09-20.yang:2377.27: error(258): invalid value
ietf-l2vpn-svc@2018-10-09.yang PASSED WITH WARNINGS     ietf-l2vpn-svc@2018-10-09.yang:1739: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).    
ietf-l3-unicast-topology-state@2018-02-26.yang PASSED          
ietf-l3-unicast-topology@2018-02-26.yang PASSED          
ietf-l3vpn-ntw@2022-02-14.yang FAILED ietf-l3vpn-ntw@2022-02-14.yang:1645: warning: the type leafref (defined at ietf-interfaces@2018-02-20.yang:55) is converted to 'string' when part of a union       Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro.conf /var/yang/ietf/YANG-rfc/ietf-l3vpn-ntw@2022-02-14.yang 2>&1":
Error: leaf 'rp-discovery-type' has invalid default value (vpn-common:static-rp)
ietf-l3vpn-ntw@2022-02-14.yang:396.13: error(258): invalid value

Error: leaf 'version' has invalid default value (vpn-common:igmpv2)
ietf-l3vpn-ntw@2022-02-14.yang:452.11: error(258): invalid value

Error: leaf 'version' has invalid default value (vpn-common:mldv2)
ietf-l3vpn-ntw@2022-02-14.yang:497.11: error(258): invalid value

Error: leaf 'peer-mode' has invalid default value (vpn-common:static-mode)
ietf-l3vpn-ntw@2022-02-14.yang:970.27: error(258): invalid value

Error: leaf 'session-type' has invalid default value (vpn-common:classic-bfd)
ietf-l3vpn-ntw@2022-02-14.yang:2468.23: error(258): invalid value

Error: leaf 'direction' has invalid default value (vpn-common:both)
ietf-l3vpn-ntw@2022-02-14.yang:2762.27: error(258): invalid value

Error: leaf 'version' has invalid default value (vpn-common:igmpv2)
ietf-l3vpn-ntw@2022-02-14.yang:2963.25: error(258): invalid value

Error: leaf 'version' has invalid default value (vpn-common:mldv2)
ietf-l3vpn-ntw@2022-02-14.yang:3014.25: error(258): invalid value
ietf-l3vpn-svc@2017-01-27.yang PASSED WITH WARNINGS     ietf-l3vpn-svc@2017-01-27.yang:30: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing or is not correct (see pyang --ietf-help for details).

ietf-l3vpn-svc@2017-01-27.yang:30: warning: RFC 8407: Appendix B: The text about which RFC this module is part of seems to be missing or is not correct (see pyang --ietf-help for details).		 libyang warn: Identityref "type" comparison with identity "vrrp" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.

libyang warn: Previous warning generated by XPath subexpression[3] "type = 'vrrp'" with context node "/ietf-l3vpn-svc:l3vpn-svc/sites/site/site-network-accesses/site-network-access/routing-protocols/routing-protocol/vrrp".

libyang warn: Identityref "type" comparison with identity "rip" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.

libyang warn: Previous warning generated by XPath subexpression[3] "type = 'rip'" with context node "/ietf-l3vpn-svc:l3vpn-svc/sites/site/site-network-accesses/site-network-access/routing-protocols/routing-protocol/rip".

libyang warn: Identityref "type" comparison with identity "static" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.

libyang warn: Previous warning generated by XPath subexpression[3] "type = 'static'" with context node "/ietf-l3vpn-svc:l3vpn-svc/sites/site/site-network-accesses/site-network-access/routing-protocols/routing-protocol/static".

libyang warn: Identityref "type" comparison with identity "bgp" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.

libyang warn: Previous warning generated by XPath subexpression[3] "type = 'bgp'" with context node "/ietf-l3vpn-svc:l3vpn-svc/sites/site/site-network-accesses/site-network-access/routing-protocols/routing-protocol/bgp".

libyang warn: Identityref "type" comparison with identity "ospf" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.

libyang warn: Previous warning generated by XPath subexpression[3] "type = 'ospf'" with context node "/ietf-l3vpn-svc:l3vpn-svc/sites/site/site-network-accesses/site-network-access/routing-protocols/routing-protocol/ospf".

libyang warn: Identityref "address-allocation-type" comparison with identity "static-address" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.

libyang warn: Previous warning generated by XPath subexpression[3] "address-allocation-type = 'static-address'" with context node "/ietf-l3vpn-svc:l3vpn-svc/sites/site/site-network-accesses/site-network-access/ip-connection/ipv6/addresses".

libyang warn: Identityref "address-allocation-type" comparison with identity "provider-dhcp-relay" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.

libyang warn: Previous warning generated by XPath subexpression[3] "address-allocation-type = 'provider-dhcp-relay'" with context node "/ietf-l3vpn-svc:l3vpn-svc/sites/site/site-network-accesses/site-network-access/ip-connection/ipv6/dhcp-relay".

libyang warn: Identityref "address-allocation-type" comparison with identity "provider-dhcp" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.

libyang warn: Previous warning generated by XPath subexpression[3] "address-allocation-type = 'provider-dhcp'" with context node "/ietf-l3vpn-svc:l3vpn-svc/sites/site/site-network-accesses/site-network-access/ip-connection/ipv6/number-of-dynamic-address".

libyang warn: Identityref "address-allocation-type" comparison with identity "provider-dhcp-slaac" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.

libyang warn: Previous warning generated by XPath subexpression[51] "address-allocation-type = 'provider-dhcp-slaac'" with context node "/ietf-l3vpn-svc:l3vpn-svc/sites/site/site-network-accesses/site-network-access/ip-connection/ipv6/number-of-dynamic-address".

libyang warn: Previous warning generated by XPath subexpression[3] "address-allocation-type = 'static-address'" with context node "/ietf-l3vpn-svc:l3vpn-svc/sites/site/site-network-accesses/site-network-access/ip-connection/ipv4/addresses".

libyang warn: Previous warning generated by XPath subexpression[3] "address-allocation-type = 'provider-dhcp-relay'" with context node "/ietf-l3vpn-svc:l3vpn-svc/sites/site/site-network-accesses/site-network-access/ip-connection/ipv4/dhcp-relay".

libyang warn: Previous warning generated by XPath subexpression[3] "address-allocation-type = 'provider-dhcp'" with context node "/ietf-l3vpn-svc:l3vpn-svc/sites/site/site-network-accesses/site-network-access/ip-connection/ipv4/number-of-dynamic-address".

libyang warn: Identityref "type" comparison with identity "provider-managed" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.

libyang warn: Previous warning generated by XPath subexpression[33] "type = 'provider-managed'" with context node "/ietf-l3vpn-svc:l3vpn-svc/sites/site/site-network-accesses/site-network-access".

libyang warn: Identityref "type" comparison with identity "co-managed" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.

libyang warn: Previous warning generated by XPath subexpression[95] "type = 'co-managed'" with context node "/ietf-l3vpn-svc:l3vpn-svc/sites/site/site-network-accesses/site-network-access".

libyang warn: Identityref "type" comparison with identity "customer-managed" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.

libyang warn: Previous warning generated by XPath subexpression[33] "type = 'customer-managed'" with context node "/ietf-l3vpn-svc:l3vpn-svc/sites/site/site-network-accesses/site-network-access".

libyang warn: Previous warning generated by XPath subexpression[3] "type = 'vrrp'" with context node "/ietf-l3vpn-svc:l3vpn-svc/sites/site/routing-protocols/routing-protocol/vrrp".

libyang warn: Previous warning generated by XPath subexpression[3] "type = 'rip'" with context node "/ietf-l3vpn-svc:l3vpn-svc/sites/site/routing-protocols/routing-protocol/rip".

libyang warn: Previous warning generated by XPath subexpression[3] "type = 'static'" with context node "/ietf-l3vpn-svc:l3vpn-svc/sites/site/routing-protocols/routing-protocol/static".

libyang warn: Previous warning generated by XPath subexpression[3] "type = 'bgp'" with context node "/ietf-l3vpn-svc:l3vpn-svc/sites/site/routing-protocols/routing-protocol/bgp".

libyang warn: Previous warning generated by XPath subexpression[3] "type = 'ospf'" with context node "/ietf-l3vpn-svc:l3vpn-svc/sites/site/routing-protocols/routing-protocol/ospf".

libyang warn: Identityref "rp-discovery-type" comparison with identity "bsr-rp" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.

libyang warn: Previous warning generated by XPath subexpression[3] "rp-discovery-type = 'bsr-rp'" with context node "/ietf-l3vpn-svc:l3vpn-svc/vpn-services/vpn-service/multicast/rp/rp-discovery/bsr-candidates".

libyang warn: Previous warning generated by XPath subexpression[33] "type = 'provider-managed'" with context node "/ietf-l3vpn-svc:l3vpn-svc/sites/site/devices".

libyang warn: Previous warning generated by XPath subexpression[95] "type = 'co-managed'" with context node "/ietf-l3vpn-svc:l3vpn-svc/sites/site/devices".

libyang warn: Previous warning generated by XPath subexpression[33] "type= 'co-managed'" with context node "/ietf-l3vpn-svc:l3vpn-svc/sites/site/devices/device/management".		  
ietf-l3vpn-svc@2018-01-19.yang PASSED WITH WARNINGS     ietf-l3vpn-svc@2018-01-19.yang:633: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).    
ietf-layer0-types@2021-08-13.yang PASSED          
ietf-lime-time-types@2019-04-16.yang PASSED          
ietf-lmap-common@2017-08-08.yang PASSED WITH WARNINGS     ietf-lmap-common@2017-08-08.yang:29: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing or is not correct (see pyang --ietf-help for details).

ietf-lmap-common@2017-08-08.yang:29: warning: RFC 8407: Appendix B: The text about which RFC this module is part of seems to be missing or is not correct (see pyang --ietf-help for details).		    
ietf-lmap-control@2017-08-08.yang PASSED WITH WARNINGS     ietf-lmap-control@2017-08-08.yang:35: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing or is not correct (see pyang --ietf-help for details).

ietf-lmap-control@2017-08-08.yang:35: warning: RFC 8407: Appendix B: The text about which RFC this module is part of seems to be missing or is not correct (see pyang --ietf-help for details).

ietf-lmap-control@2017-08-08.yang:283: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).		    
ietf-lmap-report@2017-08-08.yang PASSED WITH WARNINGS     ietf-lmap-report@2017-08-08.yang:32: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing or is not correct (see pyang --ietf-help for details).

ietf-lmap-report@2017-08-08.yang:32: warning: RFC 8407: Appendix B: The text about which RFC this module is part of seems to be missing or is not correct (see pyang --ietf-help for details).		    
ietf-logical-network-element@2019-01-25.yang PASSED WITH WARNINGS     ietf-logical-network-element@2019-01-25.yang:107: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).    
ietf-microwave-radio-link@2019-06-19.yang PASSED          
ietf-microwave-topology@2024-09-30.yang PASSED          
ietf-microwave-types@2019-06-19.yang PASSED          
ietf-module-tags-state@2021-01-04.yang PASSED          
ietf-module-tags@2021-01-04.yang PASSED          
ietf-mpls-ldp-extended@2022-03-14.yang FAILED         Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro.conf /var/yang/ietf/YANG-rfc/ietf-mpls-ldp-extended@2022-03-14.yang 2>&1":
Error: Key predicates found for list 'peer' which does not define any keys
Error: path failed (invalid value):
'../../../../../../../ldp:peers/ldp:peer[ldp:lsr-id=current()/../lsr-id]/ldp:label-space-id'

Error: Key predicates found for list 'peer' which does not define any keys
Error: path failed (invalid value):
'../../../../../../../../../ldp:peers/ldp:peer[ldp:lsr-id=current()/../lsr-id]/ldp:label-space-id'

Error: Key predicates found for list 'peer' which does not define any keys
Error: path failed (invalid value):
'../../../../../../../../ldp:peers/ldp:peer[ldp:lsr-id=current()/../lsr-id]/ldp:label-space-id'

Error: 'ietf-mpls-ldp-extended@2022-03-14.yang' import of module 'ietf-mpls-ldp' failed
ietf-mpls-ldp-extended@2022-03-14.yang:22.3: error(258): invalid value

Error: grouping definition for 'ldp:ldp-interface-ref' not found in module ietf-mpls-ldp
ietf-mpls-ldp-extended@2022-03-14.yang:341.11: error(250): definition not found

Error: grouping definition for 'ldp:basic-discovery-timers' not found in module ietf-mpls-ldp
ietf-mpls-ldp-extended@2022-03-14.yang:428.5: error(250): definition not found

Error: grouping definition for 'ldp:graceful-restart-attributes-per-peer' not found in module ietf-mpls-ldp
ietf-mpls-ldp-extended@2022-03-14.yang:493.5: error(250): definition not found

Error: grouping definition for 'ldp:peer-attributes' not found in module ietf-mpls-ldp
ietf-mpls-ldp-extended@2022-03-14.yang:496.5: error(250): definition not found

Error: grouping definition for 'ldp:binding-address-state-attributes' not found in module ietf-mpls-ldp
ietf-mpls-ldp-extended@2022-03-14.yang:703.11: error(250): definition not found

Error: grouping definition for 'ldp:binding-label-state-attributes' not found in module ietf-mpls-ldp
ietf-mpls-ldp-extended@2022-03-14.yang:716.11: error(250): definition not found

Error: grouping definition for 'ldp:adjacency-state-attributes' not found in module ietf-mpls-ldp
ietf-mpls-ldp-extended@2022-03-14.yang:755.11: error(250): definition not found

Error: grouping definition for 'ldp:ldp-peer-ref-from-interface' not found in module ietf-mpls-ldp
ietf-mpls-ldp-extended@2022-03-14.yang:756.11: error(250): definition not found

Error: grouping definition for 'ldp:adjacency-state-attributes' not found in module ietf-mpls-ldp
ietf-mpls-ldp-extended@2022-03-14.yang:792.11: error(250): definition not found

Error: grouping definition for 'ldp:ldp-peer-ref-from-target' not found in module ietf-mpls-ldp
ietf-mpls-ldp-extended@2022-03-14.yang:793.11: error(250): definition not found

Error: grouping definition for 'ldp:adjacency-state-attributes' not found in module ietf-mpls-ldp
ietf-mpls-ldp-extended@2022-03-14.yang:853.11: error(250): definition not found

Error: grouping 'ldp-interface-ref' not found
ietf-mpls-ldp-extended@2022-03-14.yang:341.11: error(250): definition not found

Error: grouping 'basic-discovery-timers' not found
ietf-mpls-ldp-extended@2022-03-14.yang:428.5: error(250): definition not found

Error: grouping 'graceful-restart-attributes-per-peer' not found
ietf-mpls-ldp-extended@2022-03-14.yang:493.5: error(250): definition not found

Error: grouping 'peer-attributes' not found
ietf-mpls-ldp-extended@2022-03-14.yang:496.5: error(250): definition not found

Error: grouping 'binding-address-state-attributes' not found
ietf-mpls-ldp-extended@2022-03-14.yang:703.11: error(250): definition not found

Error: grouping 'binding-label-state-attributes' not found
ietf-mpls-ldp-extended@2022-03-14.yang:716.11: error(250): definition not found

Error: grouping 'adjacency-state-attributes' not found
ietf-mpls-ldp-extended@2022-03-14.yang:755.11: error(250): definition not found

Error: grouping 'ldp-peer-ref-from-interface' not found
ietf-mpls-ldp-extended@2022-03-14.yang:756.11: error(250): definition not found

Error: grouping 'adjacency-state-attributes' not found
ietf-mpls-ldp-extended@2022-03-14.yang:792.11: error(250): definition not found

Error: grouping 'ldp-peer-ref-from-target' not found
ietf-mpls-ldp-extended@2022-03-14.yang:793.11: error(250): definition not found

Error: grouping 'adjacency-state-attributes' not found
ietf-mpls-ldp-extended@2022-03-14.yang:853.11: error(250): definition not found

Error: object 'mpls-ldp' not found in path '/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ldp:mpls-ldp/ldp:global'
ietf-mpls-ldp-extended@2022-03-14.yang:639.3: error(251): definition segment not found

Error: object 'mpls-ldp' not found in path '/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ldp:mpls-ldp/ldp:global'
ietf-mpls-ldp-extended@2022-03-14.yang:868.3: error(251): definition segment not found

Error: object 'mpls-ldp' not found in path '/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers'
ietf-mpls-ldp-extended@2022-03-14.yang:941.3: error(251): definition segment not found

Error: object 'mpls-ldp' not found in path '/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/ldp:address-families'
ietf-mpls-ldp-extended@2022-03-14.yang:648.3: error(251): definition segment not found

Error: object 'mpls-ldp' not found in path '/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/ldp:capability'
ietf-mpls-ldp-extended@2022-03-14.yang:875.3: error(251): definition segment not found

Error: object 'mpls-ldp' not found in path '/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/ldp:graceful-restart'
ietf-mpls-ldp-extended@2022-03-14.yang:883.3: error(251): definition segment not found

Error: object 'mpls-ldp' not found in path '/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/ldp:peer'
ietf-mpls-ldp-extended@2022-03-14.yang:959.3: error(251): definition segment not found

Error: object 'mpls-ldp' not found in path '/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ldp:mpls-ldp/ldp:discovery/ldp:targeted/ldp:address-families'
ietf-mpls-ldp-extended@2022-03-14.yang:764.3: error(251): definition segment not found

Error: object 'mpls-ldp' not found in path '/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/ldp:peer/ldp:address-families'
ietf-mpls-ldp-extended@2022-03-14.yang:826.3: error(251): definition segment not found

Error: object 'mpls-ldp' not found in path '/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/ldp:address-families/ldp:ipv4'
ietf-mpls-ldp-extended@2022-03-14.yang:891.3: error(251): definition segment not found

Error: object 'mpls-ldp' not found in path '/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ldp:mpls-ldp/ldp:discovery/ldp:interfaces/ldp:interface'
ietf-mpls-ldp-extended@2022-03-14.yang:899.3: error(251): definition segment not found

Error: object 'mpls-ldp' not found in path '/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ldp:mpls-ldp/ldp:discovery/ldp:targeted/ldp:hello-accept'
ietf-mpls-ldp-extended@2022-03-14.yang:925.3: error(251): definition segment not found

Error: object 'mpls-ldp' not found in path '/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/ldp:authentication/ldp:authentication-type'
ietf-mpls-ldp-extended@2022-03-14.yang:948.3: error(251): definition segment not found

Error: object 'mpls-ldp' not found in path '/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ldp:mpls-ldp/ldp:discovery/ldp:interfaces/ldp:interface/ldp:address-families'
ietf-mpls-ldp-extended@2022-03-14.yang:724.3: error(251): definition segment not found

Error: object 'mpls-ldp' not found in path '/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/ldp:peer/ldp:authentication/ldp:authentication-type'
ietf-mpls-ldp-extended@2022-03-14.yang:967.3: error(251): definition segment not found

Error: object 'mpls-ldp' not found in path '/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/ldp:peer/ldp:address-families/ldp:ipv4'
ietf-mpls-ldp-extended@2022-03-14.yang:978.3: error(251): definition segment not found

Error: object 'mpls-ldp' not found in path '/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/ldp:peer/ldp:address-families/ldp-ext:ipv6'
ietf-mpls-ldp-extended@2022-03-14.yang:986.3: error(251): definition segment not found

Error: object 'mpls-ldp' not found in path '/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ldp:mpls-ldp/ldp:discovery/ldp:interfaces/ldp:interface/ldp:address-families/ldp:ipv4'
ietf-mpls-ldp-extended@2022-03-14.yang:907.3: error(251): definition segment not found

Error: object 'mpls-ldp' not found in path '/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ldp:mpls-ldp/ldp:discovery/ldp:interfaces/ldp:interface/ldp:address-families/ldp-ext:ipv6'
ietf-mpls-ldp-extended@2022-03-14.yang:916.3: error(251): definition segment not found

Error: object 'name' not found in module ietf-mpls-ldp-extended in Xpath target name
ietf-mpls-ldp-extended@2022-03-14.yang:337.11: error(250): definition not found

Error: invalid identifier in key for list 'interface' (name)
ietf-mpls-ldp-extended@2022-03-14.yang:337.11: error(250): definition not found

Error: object 'name' not found in module ietf-mpls-ldp-extended in Xpath target name
ietf-mpls-ldp-extended@2022-03-14.yang:336.9: error(250): definition not found

Error: invalid identifier in key for list 'interface' (name)
ietf-mpls-ldp-extended@2022-03-14.yang:336.9: error(250): definition not found
ietf-mpls-ldp@2022-03-14.yang FAILED         Error: Key predicates found for list 'peer' which does not define any keys
Error: path failed (invalid value):
'../../../../../../../ldp:peers/ldp:peer[ldp:lsr-id=current()/../lsr-id]/ldp:label-space-id'

Error: Key predicates found for list 'peer' which does not define any keys
Error: path failed (invalid value):
'../../../../../../../../../ldp:peers/ldp:peer[ldp:lsr-id=current()/../lsr-id]/ldp:label-space-id'

Error: Key predicates found for list 'peer' which does not define any keys
Error: path failed (invalid value):
'../../../../../../../../ldp:peers/ldp:peer[ldp:lsr-id=current()/../lsr-id]/ldp:label-space-id'
ietf-mpls-msd@2025-01-10.yang PASSED          
ietf-mpls@2020-12-18.yang PASSED          
ietf-msdp@2020-10-31.yang PASSED          
ietf-mud-detext-example@2019-01-28.yang PASSED WITH WARNINGS     ietf-mud-detext-example@2019-01-28.yang:27: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing or is not correct (see pyang --ietf-help for details).

ietf-mud-detext-example@2019-01-28.yang:27: warning: RFC 8407: Appendix B: The text about which RFC this module is part of seems to be missing or is not correct (see pyang --ietf-help for details).		    
ietf-mud-tls@2025-04-18.yang PASSED          
ietf-mud-transparency@2023-10-10.yang PASSED          
ietf-mud@2019-01-28.yang PASSED          
ietf-nat@2019-01-10.yang PASSED          
ietf-netconf-acm@2012-02-22.yang FAILED ietf-netconf-acm@2012-02-22.yang:103:16: warning: illegal character after \

ietf-netconf-acm@2012-02-22.yang:144:18: warning: illegal character after \		 ietf-netconf-acm@2012-02-22.yang:103: warning: the escape sequence "\*" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning

ietf-netconf-acm@2012-02-22.yang:144: warning: the escape sequence "\*" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning		 ietf-netconf-acm@2012-02-22.yang:70: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).

ietf-netconf-acm@2012-02-22.yang:103: warning: the escape sequence "\*" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning

ietf-netconf-acm@2012-02-22.yang:144: warning: the escape sequence "\*" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning		 libyang err : Problem occurred while running command "yanglint -i -p /var/yang/yang/modules/ /var/yang/ietf/YANG-rfc/ietf-netconf-acm@2012-02-22.yang 2>&1":
libyang err : Double-quoted string unknown special character '\*'. (Line number 103.)

libyang err : Parsing module "ietf-netconf-acm" failed.		  
ietf-netconf-acm@2018-02-14.yang PASSED WITH WARNINGS     ietf-netconf-acm@2018-02-14.yang:38: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing or is not correct (see pyang --ietf-help for details).

ietf-netconf-acm@2018-02-14.yang:75: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).		    
ietf-netconf-monitoring@2010-10-04.yang PASSED WITH WARNINGS     ietf-netconf-monitoring@2010-10-04.yang:54: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement

ietf-netconf-monitoring@2010-10-04.yang:55: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement

ietf-netconf-monitoring@2010-10-04.yang:56: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement

ietf-netconf-monitoring@2010-10-04.yang:260: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).

ietf-netconf-monitoring@2010-10-04.yang:384: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement		    
ietf-netconf-nmda@2019-01-07.yang PASSED          
ietf-netconf-notifications@2012-02-06.yang FAILED ietf-netconf-notifications@2012-02-06.yang:286: warning: The XPath expression references an undefined node: the node 'confirm-event' from module 'ietf-netconf-notifications' is not found

ietf-netconf-notifications@2012-02-06.yang:286: warning: The XPath expression references an undefined node: the node 'confirm-event' from module 'ietf-netconf-notifications' is not found

ietf-netconf-notifications@2012-02-06.yang:286: warning: The XPath expression references an undefined node: the node 'confirm-event' from module 'ietf-netconf-notifications' is not found		 ietf-netconf-notifications@2012-02-06.yang:286: warning: node "ietf-netconf-notifications::confirm-event" is not found in module "ietf-netconf-notifications" Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" ietf-netconf-notifications@2012-02-06.yang --ietf 2>&1":
ietf-netconf-notifications@2012-02-06.yang:44: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing or is not correct (see pyang --ietf-help for details).

ietf-netconf-notifications@2012-02-06.yang:71: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).

ietf-netconf-notifications@2012-02-06.yang:95: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement

ietf-netconf-notifications@2012-02-06.yang:286: warning: node "ietf-netconf-notifications::confirm-event" is not found in module "ietf-netconf-notifications"		 libyang warn: Schema node "confirm-event" for parent "" not found; in expr "../confirm-event" with context node "/ietf-netconf-notifications:netconf-confirmed-commit". Warning: no parent found in XPath expr '../confirm-event != 'timeout''
ietf-netconf-notifications@2012-02-06.yang:286.12: warning(1031): no parent node available
ietf-netconf-partial-lock@2009-10-19.yang FAILED     Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" ietf-netconf-partial-lock@2009-10-19.yang --ietf 2>&1":
ietf-netconf-partial-lock@2009-10-19.yang:3: warning: RFC 8407: 4.9: namespace value should be "urn:ietf:params:xml:ns:yang:ietf-netconf-partial-lock"

ietf-netconf-partial-lock@2009-10-19.yang:19: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing or is not correct (see pyang --ietf-help for details).

ietf-netconf-partial-lock@2009-10-19.yang:19: warning: RFC 8407: Appendix B: The text about which RFC this module is part of seems to be missing or is not correct (see pyang --ietf-help for details).

ietf-netconf-partial-lock@2009-10-19.yang:21: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement

ietf-netconf-partial-lock@2009-10-19.yang:31: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).		    
ietf-netconf-time@2016-01-26.yang PASSED WITH WARNINGS     ietf-netconf-time@2016-01-26.yang:38: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing or is not correct (see pyang --ietf-help for details).

ietf-netconf-time@2016-01-26.yang:38: warning: RFC 8407: Appendix B: The text about which RFC this module is part of seems to be missing or is not correct (see pyang --ietf-help for details).		    
ietf-netconf-with-defaults@2011-06-01.yang FAILED     Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" ietf-netconf-with-defaults@2011-06-01.yang --ietf 2>&1":
ietf-netconf-with-defaults@2011-06-01.yang:46: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing or is not correct (see pyang --ietf-help for details).

ietf-netconf-with-defaults@2011-06-01.yang:56: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)

ietf-netconf-with-defaults@2011-06-01.yang:59: error: keyword "type" not in canonical order (see RFC 6020, Section 12)

ietf-netconf-with-defaults@2011-06-01.yang:97: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)

ietf-netconf-with-defaults@2011-06-01.yang:101: error: keyword "type" not in canonical order (see RFC 6020, Section 12)		    
ietf-netconf@2011-06-01.yang PASSED WITH WARNINGS     ietf-netconf@2011-06-01.yang:5: warning: RFC 8407: 4.9: namespace value should be "urn:ietf:params:xml:ns:yang:ietf-netconf"

ietf-netconf@2011-06-01.yang:48: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing or is not correct (see pyang --ietf-help for details).

ietf-netconf@2011-06-01.yang:275: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).		    
ietf-network-instance@2019-01-21.yang PASSED          
ietf-network-state@2018-02-26.yang PASSED          
ietf-network-topology-state@2018-02-26.yang PASSED          
ietf-network-topology@2018-02-26.yang PASSED WITH WARNINGS     ietf-network-topology@2018-02-26.yang:79: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).    
ietf-network-vpn-pm@2023-03-20.yang PASSED          
ietf-network@2018-02-26.yang PASSED WITH WARNINGS     ietf-network@2018-02-26.yang:72: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).    
ietf-nmda-compare@2021-12-10.yang PASSED          
ietf-notification-capabilities@2022-02-17.yang PASSED          
ietf-ntp@2022-07-05.yang PASSED WITH WARNINGS       libyang warn: Ext plugin "ly2 NACM v1": Extension nacm:default-deny-all is not allowed in unknown statement. (Path "/ietf-ntp:key/{extension='nacm:default-deny-all'}".)  
ietf-origin@2018-02-14.yang PASSED          
ietf-ospf@2022-10-19.yang PASSED          
ietf-ospfv3-extended-lsa@2024-06-07.yang PASSED          
ietf-packet-fields@2019-03-04.yang PASSED WITH WARNINGS     ietf-packet-fields@2019-03-04.yang:58: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing or is not correct (see pyang --ietf-help for details).    
ietf-pim-base@2022-10-19.yang PASSED          
ietf-pim-bidir@2022-10-19.yang PASSED          
ietf-pim-dm@2022-10-19.yang PASSED          
ietf-pim-rp@2022-10-19.yang PASSED          
ietf-pim-sm@2022-10-19.yang PASSED          
ietf-ptp@2019-05-07.yang PASSED WITH WARNINGS     ietf-ptp@2019-05-07.yang:24: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing or is not correct (see pyang --ietf-help for details).

ietf-ptp@2019-05-07.yang:24: warning: RFC 8407: Appendix B: The text about which RFC this module is part of seems to be missing or is not correct (see pyang --ietf-help for details).		    
ietf-restconf-monitoring@2017-01-26.yang PASSED WITH WARNINGS     ietf-restconf-monitoring@2017-01-26.yang:99: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).    
ietf-restconf-subscribed-notifications@2019-11-17.yang PASSED          
ietf-restconf@2017-01-26.yang PASSED WITH WARNINGS     ietf-restconf@2017-01-26.yang:115: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).    
ietf-rib-extension@2023-11-20.yang PASSED          
ietf-rift@2025-04-04.yang PASSED          
ietf-rip@2020-02-20.yang PASSED          
ietf-routing-policy@2021-10-11.yang PASSED          
ietf-routing-types@2017-12-04.yang PASSED          
ietf-routing@2016-11-04.yang PASSED WITH WARNINGS     ietf-routing@2016-11-04.yang:56: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).    
ietf-routing@2018-03-13.yang PASSED WITH WARNINGS     ietf-routing@2018-03-13.yang:72: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).    
ietf-sap-ntw@2023-06-20.yang PASSED          
ietf-schc-compound-ack@2023-07-26.yang PASSED          
ietf-schc@2023-03-01.yang PASSED          
ietf-segment-routing-common@2021-05-26.yang PASSED          
ietf-segment-routing-mpls@2021-05-26.yang PASSED          
ietf-segment-routing@2021-05-26.yang PASSED          
ietf-service-assurance-device@2023-07-11.yang PASSED          
ietf-service-assurance-interface@2023-07-11.yang PASSED          
ietf-service-assurance@2023-07-11.yang PASSED          
ietf-sid-file@2024-07-31.yang PASSED          
ietf-snmp@2014-12-10.yang FAILED ietf-snmp-community@2014-12-10.yang:220: warning: The XPath expression references an undefined node: the node 'v1' from module 'ietf-snmp' (in node 'target' from 'ietf-snmp') is not found

ietf-snmp-community@2014-12-10.yang:220: warning: The XPath expression references an undefined node: the node 'v2c' from module 'ietf-snmp' (in node 'target' from 'ietf-snmp') is not found		 ietf-snmp-community@2014-12-10.yang:220: warning: node "ietf-snmp::v1" is not found in "ietf-snmp::target"

ietf-snmp-community@2014-12-10.yang:220: warning: node "ietf-snmp::v2c" is not found in "ietf-snmp::target"		 Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" ietf-snmp@2014-12-10.yang --ietf 2>&1":
ietf-snmp-common@2014-12-10.yang:102: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement

ietf-snmp-common@2014-12-10.yang:105: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement

ietf-snmp-common@2014-12-10.yang:106: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement

ietf-snmp-common@2014-12-10.yang:107: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement

ietf-snmp-common@2014-12-10.yang:108: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement

ietf-snmp-common@2014-12-10.yang:119: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement

ietf-snmp-common@2014-12-10.yang:122: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement

ietf-snmp-common@2014-12-10.yang:131: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement

ietf-snmp-common@2014-12-10.yang:133: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement

ietf-snmp-common@2014-12-10.yang:134: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement

ietf-snmp-common@2014-12-10.yang:135: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement

ietf-snmp-community@2014-12-10.yang:62: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement

ietf-snmp-community@2014-12-10.yang:166: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement

ietf-snmp-community@2014-12-10.yang:188: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement

ietf-snmp-community@2014-12-10.yang:210: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement

ietf-snmp-community@2014-12-10.yang:219: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement

ietf-snmp-community@2014-12-10.yang:220: warning: node "ietf-snmp::v1" is not found in "ietf-snmp::target"

ietf-snmp-community@2014-12-10.yang:220: warning: node "ietf-snmp::v2c" is not found in "ietf-snmp::target"

ietf-snmp-community@2014-12-10.yang:224: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement

ietf-snmp-engine@2014-12-10.yang:55: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement

ietf-snmp-engine@2014-12-10.yang:89: error: RFC 8407: 4.14: statement "container" must have a "description" substatement

ietf-snmp-engine@2014-12-10.yang:115: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-engine@2014-12-10.yang:118: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-engine@2014-12-10.yang:121: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-notification@2014-12-10.yang:65: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement

ietf-snmp-notification@2014-12-10.yang:107: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement

ietf-snmp-notification@2014-12-10.yang:108: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement

ietf-snmp-notification@2014-12-10.yang:183: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement

ietf-snmp-proxy@2014-12-10.yang:65: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement

ietf-snmp-proxy@2014-12-10.yang:87: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-proxy@2014-12-10.yang:89: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement

ietf-snmp-proxy@2014-12-10.yang:90: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement

ietf-snmp-proxy@2014-12-10.yang:91: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement

ietf-snmp-proxy@2014-12-10.yang:92: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement

ietf-snmp-proxy@2014-12-10.yang:100: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-proxy@2014-12-10.yang:108: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-ssh@2014-12-10.yang:72: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement

ietf-snmp-ssh@2014-12-10.yang:102: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement

ietf-snmp-ssh@2014-12-10.yang:109: error: RFC 8407: 4.14: statement "container" must have a "description" substatement

ietf-snmp-ssh@2014-12-10.yang:110: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-ssh@2014-12-10.yang:121: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-ssh@2014-12-10.yang:132: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-target@2014-12-10.yang:59: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement

ietf-snmp-target@2014-12-10.yang:105: error: RFC 8407: 4.14: statement "container" must have a "description" substatement

ietf-snmp-target@2014-12-10.yang:106: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-target@2014-12-10.yang:178: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-target@2014-12-10.yang:197: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-tls@2014-12-10.yang:75: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement

ietf-snmp-tls@2014-12-10.yang:131: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement

ietf-snmp-tls@2014-12-10.yang:133: error: RFC 8407: 4.14: statement "container" must have a "description" substatement

ietf-snmp-tls@2014-12-10.yang:151: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement

ietf-snmp-tls@2014-12-10.yang:152: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-tls@2014-12-10.yang:163: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-tls@2014-12-10.yang:174: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-tls@2014-12-10.yang:181: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-tls@2014-12-10.yang:188: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-tls@2014-12-10.yang:197: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement

ietf-snmp-tls@2014-12-10.yang:204: error: RFC 8407: 4.14: statement "container" must have a "description" substatement

ietf-snmp-tls@2014-12-10.yang:210: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement

ietf-snmp-tls@2014-12-10.yang:217: error: RFC 8407: 4.14: statement "container" must have a "description" substatement

ietf-snmp-tsm@2014-12-10.yang:66: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement

ietf-snmp-tsm@2014-12-10.yang:72: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-tsm@2014-12-10.yang:83: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement

ietf-snmp-tsm@2014-12-10.yang:90: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-tsm@2014-12-10.yang:98: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-tsm@2014-12-10.yang:109: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement

ietf-snmp-usm@2014-12-10.yang:65: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement

ietf-snmp-usm@2014-12-10.yang:76: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement

ietf-snmp-usm@2014-12-10.yang:77: error: RFC 8407: 4.14: statement "list" must have a "description" substatement

ietf-snmp-usm@2014-12-10.yang:85: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-usm@2014-12-10.yang:96: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement

ietf-snmp-usm@2014-12-10.yang:102: error: RFC 8407: 4.14: statement "container" must have a "description" substatement

ietf-snmp-usm@2014-12-10.yang:110: error: RFC 8407: 4.14: statement "container" must have a "description" substatement

ietf-snmp-usm@2014-12-10.yang:130: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement

ietf-snmp-usm@2014-12-10.yang:136: error: RFC 8407: 4.14: statement "container" must have a "description" substatement

ietf-snmp-usm@2014-12-10.yang:144: error: RFC 8407: 4.14: statement "container" must have a "description" substatement

ietf-snmp-usm@2014-12-10.yang:158: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement

ietf-snmp-usm@2014-12-10.yang:163: error: RFC 8407: 4.14: statement "container" must have a "description" substatement

ietf-snmp-usm@2014-12-10.yang:167: error: RFC 8407: 4.14: statement "list" must have a "description" substatement

ietf-snmp-usm@2014-12-10.yang:170: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-usm@2014-12-10.yang:183: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement

ietf-snmp-usm@2014-12-10.yang:190: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-usm@2014-12-10.yang:199: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-usm@2014-12-10.yang:210: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement

ietf-snmp-vacm@2014-12-10.yang:69: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement

ietf-snmp-vacm@2014-12-10.yang:158: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement

ietf-snmp-vacm@2014-12-10.yang:160: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement

ietf-snmp-vacm@2014-12-10.yang:161: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement		 libyang warn: Schema node "v1" not found; in expr "snmp:v1" with context node "/ietf-snmp:snmp/target".

libyang warn: Schema node "v2c" not found; in expr "snmp:v1 or snmp:v2c" with context node "/ietf-snmp:snmp/target".		  
ietf-softwire-br@2019-11-16.yang PASSED          
ietf-softwire-ce@2019-11-16.yang PASSED          
ietf-softwire-common@2019-11-16.yang PASSED          
ietf-ssh-client@2024-10-10.yang UNKNOWN         Warning: path failed (no nodes available):
'/ts:truststore/ts:certificate-bags/ts:certificate-bag[ts:name = current()/../certificate-bag]/ts:certificate/ts:name'

Warning: path failed (no nodes available):
'/ts:truststore/ts:public-key-bags/ts:public-key-bag[ts:name = current()/../public-key-bag]/ts:public-key/ts:name'
ietf-ssh-common@2024-10-10.yang PASSED          
ietf-ssh-server@2024-10-10.yang PASSED WITH WARNINGS         Warning: path failed (no nodes available):
'/ts:truststore/ts:certificate-bags/ts:certificate-bag[ts:name = current()/../certificate-bag]/ts:certificate/ts:name'

Warning: path failed (no nodes available):
'/ts:truststore/ts:public-key-bags/ts:public-key-bag[ts:name = current()/../public-key-bag]/ts:public-key/ts:name'

Warning: Module 'ietf-crypto-types' not used
ietf-ssh-server@2024-10-10.yang:24.3: warning(1015): import not used
ietf-subscribed-notifications@2019-09-09.yang FAILED     Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" ietf-subscribed-notifications@2019-09-09.yang --ietf 2>&1":
ietf-subscribed-notifications@2019-09-09.yang:222: error: keyword "if-feature" not in canonical order (see RFC 7950, Section 14)

ietf-subscribed-notifications@2019-09-09.yang:276: error: keyword "if-feature" not in canonical order (see RFC 7950, Section 14)

ietf-subscribed-notifications@2019-09-09.yang:335: error: keyword "if-feature" not in canonical order (see RFC 7950, Section 14)

ietf-subscribed-notifications@2019-09-09.yang:344: error: keyword "if-feature" not in canonical order (see RFC 7950, Section 14)		 libyang err : Problem occurred while running command "yanglint -i -p /var/yang/yang/modules/ /var/yang/ietf/YANG-rfc/ietf-subscribed-notifications@2019-09-09.yang 2>&1":
libyang err : Data model "ietf-restconf" not found in local searchdirs.

libyang err : Loading "ietf-restconf" module failed.

libyang err : Parsing module "ietf-subscribed-notifications" failed.		  
ietf-system-capabilities@2022-02-17.yang PASSED          
ietf-system-tacacs-plus@2021-08-05.yang PASSED          
ietf-system@2014-08-06.yang PASSED WITH WARNINGS     ietf-system@2014-08-06.yang:225: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).    
ietf-sztp-bootstrap-server@2019-04-30.yang PASSED          
ietf-sztp-conveyed-info@2019-04-30.yang FAILED Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/yang/modules/ieee.802.published:/var/yang/yang/modules/ieee.1588.published:/var/yang/yang/modules/ieee.802.11.published:/var/yang/yang/modules/openconfig-main:/var/yang/yang/modules/ieee.802.1.published:/var/yang/yang/modules/iana:/var/yang/yang/modules/ieee.published:/var/yang/yang/modules/mef:/var/yang/yang/modules/YANG-rfc:/var/yang/yang/modules/ieee.802.3.published -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/ietf/YANG-rfc/ietf-sztp-conveyed-info@2019-04-30.yang 2>&1":
ietf-sztp-conveyed-info@2019-04-30.yang:95: error: unexpected keyword 'choice'		     libyang err : Problem occurred while running command "yanglint -i -p /var/yang/yang/modules/ /var/yang/ietf/YANG-rfc/ietf-sztp-conveyed-info@2019-04-30.yang 2>&1":
libyang err : Data model "ietf-restconf" not found in local searchdirs.

libyang err : Loading "ietf-restconf" module failed.

libyang err : Parsing module "ietf-sztp-conveyed-info" failed.		 Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro.conf /var/yang/ietf/YANG-rfc/ietf-sztp-conveyed-info@2019-04-30.yang 2>&1":
Error: yang-data ietf-sztp-conveyed-info:conveyed-information does not resolve to 1 container object (0)
ietf-sztp-conveyed-info@2019-04-30.yang:267.5: error(258): invalid value
ietf-sztp-csr@2024-10-10.yang PASSED          
ietf-tcg-algs@2024-12-05.yang PASSED          
ietf-tcp-client@2024-10-10.yang FAILED         *** Error: memory leak (m:841134 f:841131)
ietf-tcp-common@2024-10-10.yang PASSED          
ietf-tcp-server@2024-10-10.yang FAILED         *** Error: memory leak (m:833065 f:833062)
ietf-tcp@2024-10-10.yang PASSED          
ietf-te-packet-types@2020-06-10.yang PASSED          
ietf-te-topology-state@2020-08-06.yang PASSED          
ietf-te-topology@2020-08-06.yang PASSED          
ietf-te-types@2020-06-10.yang PASSED          
ietf-template@2010-05-18.yang FAILED     Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" ietf-template@2010-05-18.yang --ietf 2>&1":
ietf-template@2010-05-18.yang:47: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing or is not correct (see pyang --ietf-help for details).

ietf-template@2010-05-18.yang:58: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement		    
ietf-template@2016-03-20.yang PASSED WITH WARNINGS     ietf-template@2016-03-20.yang:49: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing or is not correct (see pyang --ietf-help for details).    
ietf-tls-client@2024-10-10.yang FAILED       libyang err : Problem occurred while running command "yanglint -i -p /var/yang/yang/modules/ /var/yang/all_modules/ietf-tls-client@2024-10-10.yang 2>&1":
libyang err : Feature "client-ident-tls12-psk" cannot be enabled because its "if-feature" is not satisfied.		 Warning: path failed (no nodes available):
'/ts:truststore/ts:certificate-bags/ts:certificate-bag[ts:name = current()/../certificate-bag]/ts:certificate/ts:name'

Warning: path failed (no nodes available):
'/ts:truststore/ts:public-key-bags/ts:public-key-bag[ts:name = current()/../public-key-bag]/ts:public-key/ts:name'

Warning: Module 'ietf-crypto-types' not used
ietf-tls-client@2024-10-10.yang:11.3: warning(1015): import not used
ietf-tls-common@2024-10-10.yang PASSED          
ietf-tls-server@2024-10-10.yang FAILED       libyang err : Problem occurred while running command "yanglint -i -p /var/yang/yang/modules/ /var/yang/all_modules/ietf-tls-server@2024-10-10.yang 2>&1":
libyang err : Feature "server-ident-tls12-psk" cannot be enabled because its "if-feature" is not satisfied.		 Warning: path failed (no nodes available):
'/ts:truststore/ts:certificate-bags/ts:certificate-bag[ts:name = current()/../certificate-bag]/ts:certificate/ts:name'

Warning: path failed (no nodes available):
'/ts:truststore/ts:public-key-bags/ts:public-key-bag[ts:name = current()/../public-key-bag]/ts:public-key/ts:name'

Warning: Module 'ietf-crypto-types' not used
ietf-tls-server@2024-10-10.yang:11.3: warning(1015): import not used
ietf-tpm-remote-attestation@2024-12-05.yang PASSED          
ietf-truststore@2024-10-10.yang UNKNOWN       Warning: path failed (no nodes available):
'/ts:truststore/ts:certificate-bags/ts:certificate-bag[ts:name = current()/../certificate-bag]/ts:certificate/ts:name'

Warning: path failed (no nodes available):
'/ts:truststore/ts:public-key-bags/ts:public-key-bag[ts:name = current()/../public-key-bag]/ts:public-key/ts:name'		  
ietf-twamp@2021-11-17.yang PASSED          
ietf-vn@2025-03-27.yang PASSED          
ietf-voucher-request@2021-05-20.yang FAILED       libyang err : Problem occurred while running command "yanglint -i -p /var/yang/yang/modules/ /var/yang/ietf/YANG-rfc/ietf-voucher-request@2021-05-20.yang 2>&1":
libyang err : Augment target node "voucher" in grouping "voucher-artifact-grouping" was not found. (Path "/ietf-voucher-request:{extension='rc:yang-data'}/voucher-request-artifact/{uses='voucher-request-grouping'}/{uses='vch:voucher-artifact-grouping'}".)		  
ietf-voucher@2018-05-09.yang FAILED       libyang err : Problem occurred while running command "yanglint -i -p /var/yang/yang/modules/ /var/yang/ietf/YANG-rfc/ietf-voucher@2018-05-09.yang 2>&1":
libyang err : Data model "ietf-restconf" not found in local searchdirs.

libyang err : Loading "ietf-restconf" module failed.

libyang err : Parsing module "ietf-voucher" failed.		  
ietf-vpn-common@2022-02-11.yang PASSED          
ietf-vrrp@2018-03-13.yang PASSED WITH WARNINGS     ietf-vrrp@2018-03-13.yang:394: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).    
ietf-wson-topology@2021-08-13.yang FAILED Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/yang/modules/ieee.802.published:/var/yang/yang/modules/ieee.1588.published:/var/yang/yang/modules/ieee.802.11.published:/var/yang/yang/modules/openconfig-main:/var/yang/yang/modules/ieee.802.1.published:/var/yang/yang/modules/iana:/var/yang/yang/modules/ieee.published:/var/yang/yang/modules/mef:/var/yang/yang/modules/YANG-rfc:/var/yang/yang/modules/ieee.802.3.published -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/ietf-wson-topology@2021-08-13.yang 2>&1":
./ietf-layer0-types@2024-07-23.yang:755: error: the type empty (defined at ./ietf-layer0-types@2024-07-23.yang:755) cannot be part of a union

./ietf-layer0-types@2024-07-23.yang:803: error: the type empty (defined at ./ietf-layer0-types@2024-07-23.yang:803) cannot be part of a union

./ietf-layer0-types@2024-07-23.yang:822: error: the type empty (defined at ./ietf-layer0-types@2024-07-23.yang:822) cannot be part of a union

./ietf-layer0-types@2024-07-23.yang:841: error: the type empty (defined at ./ietf-layer0-types@2024-07-23.yang:841) cannot be part of a union

./ietf-layer0-types@2024-07-23.yang:858: error: the type empty (defined at ./ietf-layer0-types@2024-07-23.yang:858) cannot be part of a union

./ietf-layer0-types@2024-07-23.yang:875: error: the type empty (defined at ./ietf-layer0-types@2024-07-23.yang:875) cannot be part of a union

./ietf-layer0-types@2024-07-23.yang:893: error: the type empty (defined at ./ietf-layer0-types@2024-07-23.yang:893) cannot be part of a union

./ietf-layer0-types@2024-07-23.yang:917: error: the type empty (defined at ./ietf-layer0-types@2024-07-23.yang:917) cannot be part of a union

./ietf-layer0-types@2024-07-23.yang:935: error: the type empty (defined at ./ietf-layer0-types@2024-07-23.yang:935) cannot be part of a union

./ietf-layer0-types@2024-07-23.yang:1705: error: the type empty (defined at ./ietf-layer0-types@2024-07-23.yang:1705) cannot be part of a union		        
ietf-x509-cert-to-name@2014-12-10.yang PASSED WITH WARNINGS     ietf-x509-cert-to-name@2014-12-10.yang:171: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).    
ietf-yang-instance-data@2022-02-17.yang PASSED          
ietf-yang-library@2016-06-21.yang PASSED WITH WARNINGS     ietf-yang-library@2016-06-21.yang:152: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).    
ietf-yang-library@2019-01-04.yang PASSED          
ietf-yang-metadata@2016-08-05.yang PASSED          
ietf-yang-patch@2017-02-22.yang FAILED     ietf-yang-patch@2017-02-22.yang:94: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details). libyang err : Problem occurred while running command "yanglint -i -p /var/yang/yang/modules/ /var/yang/ietf/YANG-rfc/ietf-yang-patch@2017-02-22.yang 2>&1":
libyang err : Data model "ietf-restconf" not found in local searchdirs.

libyang err : Loading "ietf-restconf" module failed.

libyang err : Parsing module "ietf-yang-patch" failed.		  
ietf-yang-push@2019-09-09.yang FAILED       libyang err : Problem occurred while running command "yanglint -i -p /var/yang/yang/modules/ /var/yang/ietf/YANG-rfc/ietf-yang-push@2019-09-09.yang 2>&1":
libyang err : Data model "ietf-restconf" not found in local searchdirs.

libyang err : Loading "ietf-restconf" module failed.

libyang err : Parsing module "ietf-subscribed-notifications" failed.

libyang err : Loading "ietf-subscribed-notifications" module failed.

libyang err : Parsing module "ietf-yang-push" failed.		  
ietf-yang-schema-mount@2019-01-14.yang PASSED          
ietf-yang-smiv2@2012-06-22.yang PASSED          
ietf-yang-structure-ext@2020-06-17.yang PASSED          
ietf-yang-types@2010-09-24.yang PASSED WITH WARNINGS     ietf-yang-types@2010-09-24.yang:71: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).    
ietf-yang-types@2013-07-15.yang PASSED WITH WARNINGS     ietf-yang-types@2013-07-15.yang:84: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found or is not correct (see pyang --ietf-help for details).    
ietf-ztp-types@2024-10-10.yang PASSED