YANG Model Compilation Compilation Result (pyang --ietf). pyang 2.0-devel Compilation Result (pyang). Note: also generates errors for imported files. pyang 2.0-devel Compilation Results (confdc) Note: also generates errors for imported files. confd version confd-6.6 Compilation Results (yumadump-pro). Note: also generates errors for imported files. yangdump-pro 17.10-11 Compilation Results (yanglint -v). Note: also generates errors for imported files. yanglint 0.16.50
iana-crypt-hash@2014-08-06.yang PASSED WITH WARNINGS iana-crypt-hash@2014-08-06.yang:38: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
iana-hardware@2018-03-13.yang PASSED WITH WARNINGS iana-hardware@2018-03-13.yang:39: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
iana-if-type@2014-05-08.yang FAILED iana-if-type@2014-05-08.yang:43: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
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
    ***
*** 0 Errors, 0 Warnings
 
iana-routing-types@2017-12-04.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
ietf-access-control-list@2019-03-04.yang PASSED WITH WARNINGS ietf-access-control-list@2019-03-04.yang:63: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
ietf-acldns@2019-01-28.yang PASSED WITH WARNINGS ietf-acldns@2019-01-28.yang:41: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
ietf-complex-types@2011-03-15.yang FAILED 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)
    ***
*** 0 Errors, 0 Warnings
 
ietf-connection-oriented-oam@2019-04-16.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
ietf-connectionless-oam-methods@2019-04-16.yang PASSED WITH WARNINGS       ***
*** 0 Errors, 0 Warnings
warn: Identityref "type" comparison with identity "ipv4" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "type = 'ipv4'".
warn: Identityref "type" comparison with identity "ipv6" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "type = 'ipv6'".
ietf-connectionless-oam@2019-04-16.yang PASSED WITH WARNINGS       ***
*** 0 Errors, 0 Warnings
warn: Identityref "type" comparison with identity "ipv4" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "type = 'ipv4'".
warn: Identityref "type" comparison with identity "ipv6" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "type = 'ipv6'".
ietf-datastores@2018-02-14.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
ietf-dc-fabric-topology-state@2019-02-25.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
ietf-dc-fabric-topology@2019-02-25.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
ietf-dc-fabric-types@2019-02-25.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
ietf-dslite@2019-01-10.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
ietf-foo@2016-03-20.yang PASSED WITH WARNINGS ietf-foo@2016-03-20.yang:6: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
ietf-inet-types@2010-09-24.yang FAILED 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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
ietf-inet-types@2013-07-15.yang FAILED 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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
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 (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
    ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
ietf-ip@2014-06-16.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
ietf-ip@2018-02-22.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
ietf-ipfix-psamp@2012-09-05.yang FAILED ietf-ipfix-psamp@2012-09-05.yang:34: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (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 (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
/home/bclaise/ietf/YANG-rfc/ietf-ipfix-psamp@2012-09-05.yang:259:16: warning: illegal character after \
/home/bclaise/ietf/YANG-rfc/ietf-ipfix-psamp@2012-09-05.yang:279:16: warning: illegal character after \
/home/bclaise/ietf/YANG-rfc/ietf-ipfix-psamp@2012-09-05.yang:279:21: warning: illegal character after \
***
*** 0 Errors, 0 Warnings
err : Encountered invalid character sequence "\S+"".
err : Module "ietf-ipfix-psamp" parsing failed.
ietf-ipv4-unicast-routing@2016-11-04.yang PASSED WITH WARNINGS ietf-ipv4-unicast-routing@2016-11-04.yang:55: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
ietf-ipv4-unicast-routing@2018-03-13.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
ietf-ipv6-router-advertisements@2016-11-04.yang PASSED WITH WARNINGS ietf-ipv6-router-advertisements@2016-11-04.yang:59: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-ipv6-router-advertisements@2016-11-04.yang:59: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found (see pyang --ietf-help for details).
  error: cannot compile submodules; compile the module instead
***
*** 0 Errors, 0 Warnings
err : Unable to parse submodule, parse the main module instead.
ietf-ipv6-router-advertisements@2018-03-13.yang PASSED WITH WARNINGS ietf-ipv6-router-advertisements@2018-03-13.yang:117: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found (see pyang --ietf-help for details).
  error: cannot compile submodules; compile the module instead
***
*** 0 Errors, 0 Warnings
err : Unable to parse submodule, parse the main module instead.
ietf-ipv6-unicast-routing@2016-11-04.yang PASSED WITH WARNINGS ietf-ipv6-unicast-routing@2016-11-04.yang:60: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
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 (see pyang --ietf-help for details).
ietf-ipv6-router-advertisements@2016-11-04.yang:59: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
ietf-ipv6-unicast-routing@2018-03-13.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
ietf-key-chain@2017-06-15.yang PASSED WITH WARNINGS 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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
ietf-l3-unicast-topology-state@2018-02-26.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
ietf-l3-unicast-topology@2018-02-26.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
warn: Identityref "rp-discovery-type" comparison with identity "bsr-rp" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "rp-discovery-type = 'bsr-rp'".
warn: Identityref "type" comparison with identity "provider-managed" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[33] "type = 'provider-managed'".
warn: Identityref "type" comparison with identity "co-managed" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[95] "type = 'co-managed'".
warn: Identityref "type" comparison with identity "co-managed" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[33] "type= 'co-managed'".
warn: Identityref "type" comparison with identity "ospf" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "type = 'ospf'".
warn: Identityref "type" comparison with identity "bgp" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "type = 'bgp'".
warn: Identityref "type" comparison with identity "static" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "type = 'static'".
warn: Identityref "type" comparison with identity "rip" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "type = 'rip'".
warn: Identityref "type" comparison with identity "vrrp" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "type = 'vrrp'".
warn: Identityref "type" comparison with identity "customer-managed" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[33] "type = 'customer-managed'".
warn: Identityref "type" comparison with identity "provider-managed" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[33] "type = 'provider-managed'".
warn: Identityref "type" comparison with identity "co-managed" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[95] "type = 'co-managed'".
warn: Identityref "address-allocation-type" comparison with identity "provider-dhcp" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "address-allocation-type = 'provider-dhcp'".
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.
warn: Previous warning generated by XPath subexpression[3] "address-allocation-type = 'provider-dhcp-relay'".
warn: Identityref "address-allocation-type" comparison with identity "static-address" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "address-allocation-type = 'static-address'".
warn: Identityref "address-allocation-type" comparison with identity "provider-dhcp" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "address-allocation-type = 'provider-dhcp'".
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.
warn: Previous warning generated by XPath subexpression[51] "address-allocation-type = 'provider-dhcp-slaac'".
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.
warn: Previous warning generated by XPath subexpression[3] "address-allocation-type = 'provider-dhcp-relay'".
warn: Identityref "address-allocation-type" comparison with identity "static-address" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "address-allocation-type = 'static-address'".
warn: Identityref "type" comparison with identity "ospf" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "type = 'ospf'".
warn: Identityref "type" comparison with identity "bgp" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "type = 'bgp'".
warn: Identityref "type" comparison with identity "static" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "type = 'static'".
warn: Identityref "type" comparison with identity "rip" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "type = 'rip'".
warn: Identityref "type" comparison with identity "vrrp" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "type = 'vrrp'".
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
ietf-lime-time-types@2019-04-16.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
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 (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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
ietf-mud@2019-01-28.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
ietf-nat@2019-01-10.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
ietf-netconf-acm@2012-02-22.yang FAILED 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 (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
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
/home/bclaise/ietf/YANG-rfc/ietf-netconf-acm@2012-02-22.yang:103:16: warning: illegal character after \
/home/bclaise/ietf/YANG-rfc/ietf-netconf-acm@2012-02-22.yang:144:18: warning: illegal character after \
***
*** 0 Errors, 0 Warnings
err : Encountered invalid character sequence "\*"".
err : Module "ietf-netconf-acm" parsing 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 (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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
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 (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
    ***
*** 0 Errors, 0 Warnings
 
ietf-netconf-nmda@2019-01-07.yang PASSED WITH WARNINGS       Warning: no child node '*:datastore' found for parent 'ietf-netconf-nmda:output'
XPath: derived-from-or-self(datastore, "ds:operational")
ietf-netconf-nmda@2019-01-07.yang:193.35: warning(1032): no child node available

***
*** 0 Errors, 1 Warnings
 
ietf-netconf-notifications@2012-02-06.yang FAILED ietf-netconf-notifications@2012-02-06.yang:44: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (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 (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
ietf-netconf-notifications@2012-02-06.yang:286: warning: node ietf-netconf-notifications::confirm-event is not found in module ietf-netconf-notifications
/home/bclaise/ietf/YANG-rfc/ietf-netconf-notifications@2012-02-06.yang:286: error: the node 'confirm-event' from module 'ietf-netconf-notifications' is not found
/home/bclaise/ietf/YANG-rfc/ietf-netconf-notifications@2012-02-06.yang:286: error: the node 'confirm-event' from module 'ietf-netconf-notifications' is not found
/home/bclaise/ietf/YANG-rfc/ietf-netconf-notifications@2012-02-06.yang:286: error: the node 'confirm-event' from module 'ietf-netconf-notifications' is not found
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

***
*** 0 Errors, 1 Warnings
warn: Schema node "confirm-event" not found (../confirm-event) with context node "/ietf-netconf-notifications:netconf-confirmed-commit".
ietf-netconf-partial-lock@2009-10-19.yang FAILED 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 (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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
ietf-netconf-with-defaults@2011-06-01.yang FAILED ietf-netconf-with-defaults@2011-06-01.yang:46: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (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)
    ***
*** 0 Errors, 0 Warnings
 
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 (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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
ietf-network-instance@2019-01-21.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
ietf-network-state@2018-02-26.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
ietf-network-topology-state@2018-02-26.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
ietf-origin@2018-02-14.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
ietf-routing-types@2017-12-04.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
ietf-routing@2016-11-04.yang PASSED WITH WARNINGS ietf-routing@2016-11-04.yang:56: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
ietf-snmp-common@2014-12-10.yang FAILED 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
  error: cannot compile submodules; compile the module instead
***
*** 0 Errors, 0 Warnings
err : Unable to parse submodule, parse the main module instead.
ietf-snmp-community@2014-12-10.yang FAILED 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:156: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found (see pyang --ietf-help for details).
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-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-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-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-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
/home/bclaise/ietf/YANG-rfc/ietf-snmp-community@2014-12-10.yang:220: error: the node 'v2c' from module 'ietf-snmp' (in node 'target' from 'ietf-snmp') is not found
/home/bclaise/ietf/YANG-rfc/ietf-snmp-community@2014-12-10.yang:220: error: the node 'v1' from module 'ietf-snmp' (in node 'target' from 'ietf-snmp') is not found
***
*** 0 Errors, 0 Warnings
err : Unable to parse submodule, parse the main module instead.
ietf-snmp-engine@2014-12-10.yang FAILED 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-engine@2014-12-10.yang:135: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found (see pyang --ietf-help for details).
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
  error: cannot compile submodules; compile the module instead
***
*** 0 Errors, 0 Warnings
err : Unable to parse submodule, parse the main module instead.
ietf-snmp-notification@2014-12-10.yang FAILED 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:99: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found (see pyang --ietf-help for details).
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-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-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
  error: cannot compile submodules; compile the module instead
***
*** 0 Errors, 0 Warnings
err : Unable to parse submodule, parse the main module instead.
ietf-snmp-proxy@2014-12-10.yang FAILED 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-proxy@2014-12-10.yang:122: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found (see pyang --ietf-help for details).
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-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
  error: cannot compile submodules; compile the module instead
***
*** 0 Errors, 0 Warnings
err : Unable to parse submodule, parse the main module instead.
ietf-snmp-ssh@2014-12-10.yang FAILED 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-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-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-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
  error: cannot compile submodules; compile the module instead
***
*** 0 Errors, 0 Warnings
err : Unable to parse submodule, parse the main module instead.
ietf-snmp-target@2014-12-10.yang FAILED 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-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
  error: cannot compile submodules; compile the module instead
***
*** 0 Errors, 0 Warnings
err : Unable to parse submodule, parse the main module instead.
ietf-snmp-tls@2014-12-10.yang FAILED 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-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-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-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
  error: cannot compile submodules; compile the module instead
***
*** 0 Errors, 0 Warnings
err : Unable to parse submodule, parse the main module instead.
ietf-snmp-tsm@2014-12-10.yang FAILED 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-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-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-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
  error: cannot compile submodules; compile the module instead
***
*** 0 Errors, 0 Warnings
err : Unable to parse submodule, parse the main module instead.
ietf-snmp-usm@2014-12-10.yang FAILED 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-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-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-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
  error: cannot compile submodules; compile the module instead
***
*** 0 Errors, 0 Warnings
err : Unable to parse submodule, parse the main module instead.
ietf-snmp-vacm@2014-12-10.yang FAILED 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:109: warning: the module seems to use RFC 2119 keywords, but the required text from RFC 8174 is not found (see pyang --ietf-help for details).
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
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
  error: cannot compile submodules; compile the module instead
***
*** 0 Errors, 0 Warnings
err : Unable to parse submodule, parse the main module instead.
ietf-snmp@2014-12-10.yang FAILED 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
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
/home/bclaise/yang/modules/ietf-snmp-community@2014-12-10.yang:220: error: the node 'v2c' from module 'ietf-snmp' (in node 'target' from 'ietf-snmp') is not found
/home/bclaise/yang/modules/ietf-snmp-community@2014-12-10.yang:220: error: the node 'v1' from module 'ietf-snmp' (in node 'target' from 'ietf-snmp') is not found
***
*** 0 Errors, 0 Warnings
warn: Schema node "ietf-snmp:v1" not found (ietf-snmp:v1) with context node "/ietf-snmp:snmp/target".
warn: Schema node "ietf-snmp:v2c" not found (ietf-snmp:v1 or ietf-snmp:v2c) with context node "/ietf-snmp:snmp/target".
warn: Identity found, but in a non-implemented module "ietf-x509-cert-to-name".
warn: Failed to resolve identityref "ietf-x509-cert-to-name:specified". (/ietf-snmp:map-type)
warn: Previous warning generated by XPath subexpression[3] "map-type = 'ietf-x509-cert-to-name:specified'".
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
ietf-sztp-bootstrap-server@2019-04-30.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
ietf-sztp-conveyed-info@2019-04-30.yang FAILED     /home/bclaise/ietf/YANG-rfc/ietf-sztp-conveyed-info@2019-04-30.yang:95: error: unexpected keyword 'choice'
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

***
*** 1 Errors, 0 Warnings
 
ietf-template@2010-05-18.yang FAILED ietf-template@2010-05-18.yang:47: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (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
    ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
ietf-voucher@2018-05-09.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
ietf-yang-library@2019-01-04.yang PASSED WITH WARNINGS       ***
*** 0 Errors, 0 Warnings
warn: Missing status in deprecated subtree (/ietf-yang-library:{grouping}[module-list]/{grouping}[schema-leaf]/schema), inheriting.
ietf-yang-metadata@2016-08-05.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
ietf-yang-patch@2017-02-22.yang PASSED WITH WARNINGS 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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
ietf-yang-schema-mount@2019-01-14.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
ietf-yang-smiv2@2012-06-22.yang PASSED       ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings
 
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 (see pyang --ietf-help for details).
    ***
*** 0 Errors, 0 Warnings