YANG Model Draft Name Email Download the 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 (yangdump-pro). Note: also generates errors for imported files. yangdump-pro 17.10-11 Compilation Results (yanglint -V -i). Note: also generates errors for imported files. yanglint 0.16.50
TCP-MIB@2005-02-18.yang draft-scharf-tcpm-yang-tcp-01.txt Email Authors Download the YANG model FAILED TCP-MIB@2005-02-18.yang:1: warning: RFC 8407: 4.1: the module name should start with one of the strings "ietf-" or "iana-"
TCP-MIB@2005-02-18.yang:5: warning: RFC 8407: 4.9: namespace value should be "urn:ietf:params:xml:ns:yang:TCP-MIB"
TCP-MIB@2005-02-18.yang:10: error: module "INET-ADDRESS-MIB" not found in search path
TCP-MIB@2005-02-18.yang:11: error: module "inet-types" not found in search path
TCP-MIB@2005-02-18.yang:12: error: module "yang-types" not found in search path
TCP-MIB@2005-02-18.yang:23: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
TCP-MIB@2005-02-18.yang:25: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
TCP-MIB@2005-02-18.yang:29: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
TCP-MIB@2005-02-18.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
TCP-MIB@2005-02-18.yang:39: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
TCP-MIB@2005-02-18.yang:43: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:44: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:45: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:46: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:47: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:205: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:206: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:207: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:208: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:209: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:210: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:211: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:212: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:213: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:214: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:215: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:216: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:218: warning: RFC 8407: 4.4: statement "config" is given with its default value "true"
TCP-MIB@2005-02-18.yang:241: error: the key "tcpConnLocalAddress" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:254: error: the key "tcpConnLocalPort" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:262: error: the key "tcpConnRemAddress" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:272: error: the key "tcpConnRemPort" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:343: error: the key "tcpConnectionLocalAddressType" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:350: error: the key "tcpConnectionLocalAddress" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:365: error: the key "tcpConnectionLocalPort" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:372: error: the key "tcpConnectionRemAddressType" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:379: error: the key "tcpConnectionRemAddress" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:394: error: the key "tcpConnectionRemPort" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:401: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:402: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:403: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:404: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:405: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:406: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:407: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:408: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:409: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:410: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:411: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:412: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
TCP-MIB@2005-02-18.yang:414: warning: RFC 8407: 4.4: statement "config" is given with its default value "true"
TCP-MIB@2005-02-18.yang:462: error: the key "tcpListenerLocalAddressType" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:471: error: the key "tcpListenerLocalAddress" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:506: error: the key "tcpListenerLocalPort" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:10: error: module "INET-ADDRESS-MIB" not found in search path
TCP-MIB@2005-02-18.yang:11: error: module "inet-types" not found in search path
TCP-MIB@2005-02-18.yang:12: error: module "yang-types" not found in search path
TCP-MIB@2005-02-18.yang:241: error: the key "tcpConnLocalAddress" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:254: error: the key "tcpConnLocalPort" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:262: error: the key "tcpConnRemAddress" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:272: error: the key "tcpConnRemPort" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:343: error: the key "tcpConnectionLocalAddressType" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:350: error: the key "tcpConnectionLocalAddress" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:365: error: the key "tcpConnectionLocalPort" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:372: error: the key "tcpConnectionRemAddressType" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:379: error: the key "tcpConnectionRemAddress" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:394: error: the key "tcpConnectionRemPort" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:462: error: the key "tcpListenerLocalAddressType" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:471: error: the key "tcpListenerLocalAddress" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:506: error: the key "tcpListenerLocalPort" does not have same "config" as its list
TCP-MIB@2005-02-18.yang:10: error: module 'INET-ADDRESS-MIB' not found
TCP-MIB@2005-02-18.yang:11: error: module 'inet-types' not found
TCP-MIB@2005-02-18.yang:12: error: module 'yang-types' not found
Error: 'TCP-MIB@2005-02-18.yang' import of module 'inet-types' failed
TCP-MIB@2005-02-18.yang:11.3: error(236): module not found

Error: 'TCP-MIB@2005-02-18.yang' import of module 'yang-types' failed
TCP-MIB@2005-02-18.yang:12.3: error(236): module not found

Error: typedef definition for 'yang:counter32' not found in module yang-types
TCP-MIB@2005-02-18.yang:99.12: error(250): definition not found

Error: typedef definition for 'yang:counter32' not found in module yang-types
TCP-MIB@2005-02-18.yang:110.12: error(250): definition not found

Error: typedef definition for 'yang:counter32' not found in module yang-types
TCP-MIB@2005-02-18.yang:121.12: error(250): definition not found

Error: typedef definition for 'yang:counter32' not found in module yang-types
TCP-MIB@2005-02-18.yang:135.12: error(250): definition not found

Error: typedef definition for 'yang:gauge32' not found in module yang-types
TCP-MIB@2005-02-18.yang:146.12: error(250): definition not found

Error: typedef definition for 'yang:counter32' not found in module yang-types
TCP-MIB@2005-02-18.yang:154.12: error(250): definition not found

Error: typedef definition for 'yang:counter32' not found in module yang-types
TCP-MIB@2005-02-18.yang:166.12: error(250): definition not found

Error: typedef definition for 'yang:counter32' not found in module yang-types
TCP-MIB@2005-02-18.yang:178.12: error(250): definition not found

Error: typedef definition for 'inet:ipv4-address' not found in module inet-types
TCP-MIB@2005-02-18.yang:240.14: error(250): definition not found

Error: typedef definition for 'inet:ipv4-address' not found in module inet-types
TCP-MIB@2005-02-18.yang:261.14: error(250): definition not found

Error: typedef definition for 'yang:counter32' not found in module yang-types
TCP-MIB@2005-02-18.yang:280.12: error(250): definition not found

Error: typedef definition for 'yang:counter32' not found in module yang-types
TCP-MIB@2005-02-18.yang:291.12: error(250): definition not found

Error: typedef definition for 'yang:counter64' not found in module yang-types
TCP-MIB@2005-02-18.yang:301.12: error(250): definition not found

Error: typedef definition for 'yang:counter64' not found in module yang-types
TCP-MIB@2005-02-18.yang:315.12: error(250): definition not found

Error: object 'tcpConnLocalAddress' not found in module TCP-MIB in Xpath target tcpConnLocalAddress
TCP-MIB@2005-02-18.yang:193.7: error(250): definition not found

Error: invalid identifier in key for list 'tcpConnEntry' (tcpConnLocalAddress)
TCP-MIB@2005-02-18.yang:193.7: error(250): definition not found

Error: 'config-stmt for key leaf 'tcpConnLocalPort' on line 250 must match list 'tcpConnEntry'
TCP-MIB@2005-02-18.yang:193.7: error(304): wrong index type

Error: object 'tcpConnRemAddress' not found in module TCP-MIB in Xpath target tcpConnRemAddress
TCP-MIB@2005-02-18.yang:193.7: error(250): definition not found

Error: invalid identifier in key for list 'tcpConnEntry' (tcpConnRemAddress)
TCP-MIB@2005-02-18.yang:193.7: error(250): definition not found

Error: 'config-stmt for key leaf 'tcpConnRemPort' on line 268 must match list 'tcpConnEntry'
TCP-MIB@2005-02-18.yang:193.7: error(304): wrong index type

Error: 'config-stmt for key leaf 'tcpConnectionLocalAddressType' on line 341 must match list 'tcpConnectionEntry'
TCP-MIB@2005-02-18.yang:330.7: error(304): wrong index type

Error: 'config-stmt for key leaf 'tcpConnectionLocalAddress' on line 348 must match list 'tcpConnectionEntry'
TCP-MIB@2005-02-18.yang:330.7: error(304): wrong index type

Error: 'config-stmt for key leaf 'tcpConnectionLocalPort' on line 363 must match list 'tcpConnectionEntry'
TCP-MIB@2005-02-18.yang:330.7: error(304): wrong index type

Error: 'config-stmt for key leaf 'tcpConnectionRemAddressType' on line 370 must match list 'tcpConnectionEntry'
TCP-MIB@2005-02-18.yang:330.7: error(304): wrong index type

Error: 'config-stmt for key leaf 'tcpConnectionRemAddress' on line 377 must match list 'tcpConnectionEntry'
TCP-MIB@2005-02-18.yang:330.7: error(304): wrong index type

Error: 'config-stmt for key leaf 'tcpConnectionRemPort' on line 392 must match list 'tcpConnectionEntry'
TCP-MIB@2005-02-18.yang:330.7: error(304): wrong index type

Error: 'config-stmt for key leaf 'tcpListenerLocalAddressType' on line 460 must match list 'tcpListenerEntry'
TCP-MIB@2005-02-18.yang:454.7: error(304): wrong index type

Error: 'config-stmt for key leaf 'tcpListenerLocalAddress' on line 469 must match list 'tcpListenerEntry'
TCP-MIB@2005-02-18.yang:454.7: error(304): wrong index type

Error: 'config-stmt for key leaf 'tcpListenerLocalPort' on line 504 must match list 'tcpListenerEntry'
TCP-MIB@2005-02-18.yang:454.7: error(304): wrong index type

***
*** 31 Errors, 0 Warnings
err : Data model "INET-ADDRESS-MIB" not found.
err : Importing "INET-ADDRESS-MIB" module into "TCP-MIB" failed.
err : Module "TCP-MIB" parsing failed.
cira-shg-mud@2017-12-11.yang draft-richardson-shg-mud-quarantined-access-00.txt Email Authors Download the YANG model PASSED WITH WARNINGS cira-shg-mud@2017-12-11.yang:1: warning: RFC 8407: 4.1: the module name should start with one of the strings "ietf-" or "iana-"
cira-shg-mud@2017-12-11.yang:5: warning: RFC 8407: 4.9: namespace value should be "urn:ietf:params:xml:ns:yang:cira-shg-mud"
cira-shg-mud@2017-12-11.yang:26: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
example-bridge@2018-07-15.yang draft-vassilev-netmod-network-bridge-01.txt Email Authors Download the YANG model FAILED example-bridge@2018-07-15.yang:1: warning: RFC 8407: 4.1: the module name should start with one of the strings "ietf-" or "iana-"
example-bridge@2018-07-15.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
example-bridge@2018-07-15.yang:3: warning: RFC 8407: 4.9: namespace value should be "urn:ietf:params:xml:ns:yang:example-bridge"
example-bridge@2018-07-15.yang:16: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
example-bridge@2018-07-15.yang:18: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
example-bridge@2018-07-15.yang:22: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement
example-bridge@2018-07-15.yang:26: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement
example-bridge@2018-07-15.yang:30: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement
example-bridge@2018-07-15.yang:34: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement
example-bridge@2018-07-15.yang:38: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement
example-bridge@2018-07-15.yang:43: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement
example-bridge@2018-07-15.yang:47: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement
example-bridge@2018-07-15.yang:52: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement
example-bridge@2018-07-15.yang:57: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement
example-bridge@2018-07-15.yang:63: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement
example-bridge@2018-07-15.yang:67: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement
example-bridge@2018-07-15.yang:72: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement
example-bridge@2018-07-15.yang:78: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
example-bridge@2018-07-15.yang:80: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
example-bridge@2018-07-15.yang:84: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
example-bridge@2018-07-15.yang:88: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
example-bridge@2018-07-15.yang:95: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement
example-bridge@2018-07-15.yang:99: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement
example-bridge@2018-07-15.yang:105: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
example-bridge@2018-07-15.yang:107: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
example-bridge@2018-07-15.yang:111: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
    Error: Key predicates found for list 'gate-controller' which does not define any keys
Error: 'example-bridge@2018-07-15.yang' import of module 'ietf-network-bridge-scheduler' failed
example-bridge@2018-07-15.yang:9.3: error(258): invalid value

Error: Module for prefix 'sched' not found
example-bridge@2018-07-15.yang:79.12: error(236): module not found

Error: Module for prefix 'sched' not found
example-bridge@2018-07-15.yang:106.12: error(236): module not found

***
*** 3 Errors, 0 Warnings
 
foo@2019-02-25.yang draft-kwatsen-git-xiax-automation-01.txt Email Authors Download the YANG model FAILED foo@2019-02-25.yang:1: warning: RFC 8407: 4.1: the module name should start with one of the strings "ietf-" or "iana-"
foo@2019-02-25.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
foo@2019-02-25.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement
foo@2019-02-25.yang:1: error: RFC 8407: 4.8: statement "module" must have a "description" substatement
foo@2019-02-25.yang:3: warning: RFC 8407: 4.9: namespace value should be "urn:ietf:params:xml:ns:yang:foo"
foo@2019-02-25.yang:6: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
foo@2019-02-25.yang:11: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
       
iana-bfd-types@2018-08-01.yang draft-ietf-bfd-yang-17.txt Email Authors Download the YANG model PASSED          
iana-dns-class-rr-type@2019-02-27.yang draft-lhotka-dnsop-iana-class-type-yang-01.txt Email Authors Download the YANG model PASSED          
iana-dots-signal-channel@2019-01-17.yang draft-ietf-dots-signal-channel-34.txt Email Authors Download the YANG model PASSED          
iana-tunnel-type@2019-04-04.yang draft-ietf-softwire-iftunnel-06.txt Email Authors Download the YANG model PASSED          
ietf-aaa-tacacs@2019-03-06.yang draft-zheng-opsawg-tacacs-yang-01.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-aaa-tacacs@2019-03-06.yang:182: 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-alarms-x733@2019-03-21.yang draft-ietf-ccamp-alarm-module-09.txt Email Authors Download the YANG model PASSED          
ietf-alarms@2019-04-10.yang draft-ietf-ccamp-alarm-module-09.txt Email Authors Download the YANG model PASSED          
ietf-ambi-anchor@2018-06-27.yang draft-jholland-mboned-ambi-02.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-ambi-anchor@2018-06-27.yang:47: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
  ietf-ambi-anchor@2018-06-27.yang:139: warning: the type leafref (defined at ietf-ambi-anchor@2018-06-27.yang:139) is converted to 'string' when part of a union
   
ietf-arp@2019-02-21.yang draft-ietf-rtgwg-arp-yang-model-02.txt Email Authors Download the YANG model PASSED          
ietf-babel@2019-03-07.yang draft-ietf-babel-yang-model-01.txt Email Authors Download the YANG model FAILED ietf-babel@2019-03-07.yang:53: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-babel@2019-03-07.yang:278: 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: Mandatory object 'input' not allowed in external augment statement
ietf-babel@2019-03-07.yang:1011.13: error(335): mandatory object not allowed

Error: Mandatory object 'test-string' not allowed in external augment statement
ietf-babel@2019-03-07.yang:1012.15: error(335): mandatory object not allowed

Error: Mandatory object 'resulting-hash' not allowed in external augment statement
ietf-babel@2019-03-07.yang:1021.15: error(335): mandatory object not allowed

Error: Mandatory object 'input' not allowed in external augment statement
ietf-babel@2019-03-07.yang:1172.13: error(335): mandatory object not allowed

Error: Mandatory object 'test-string' not allowed in external augment statement
ietf-babel@2019-03-07.yang:1173.15: error(335): mandatory object not allowed

Error: Mandatory object 'resulting-hash' not allowed in external augment statement
ietf-babel@2019-03-07.yang:1182.15: error(335): mandatory object not allowed

***
*** 6 Errors, 0 Warnings
 
ietf-basic-remote-attestation@2018-06-15.yang draft-birkholz-rats-basic-yang-module-00.txt Email Authors Download the YANG model FAILED ietf-basic-remote-attestation@2018-06-15.yang:11: warning: imported module ietf-crypto-types not used
ietf-basic-remote-attestation@2018-06-15.yang:24: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-basic-remote-attestation@2018-06-15.yang:96: 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-basic-remote-attestation@2018-06-15.yang:518: error: keyword "description" not in canonical order,expected "type" (see RFC 6020, Section 12)
ietf-basic-remote-attestation@2018-06-15.yang:519: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
ietf-basic-remote-attestation@2018-06-15.yang:551: error: keyword "description" not in canonical order,expected "type" (see RFC 6020, Section 12)
ietf-basic-remote-attestation@2018-06-15.yang:552: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
ietf-basic-remote-attestation@2018-06-15.yang:563: error: keyword "description" not in canonical order,expected "type" (see RFC 6020, Section 12)
ietf-basic-remote-attestation@2018-06-15.yang:564: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
ietf-basic-remote-attestation@2018-06-15.yang:614: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
       
ietf-bfd-ip-mh@2018-08-01.yang draft-ietf-bfd-yang-17.txt Email Authors Download the YANG model PASSED          
ietf-bfd-ip-sh@2018-08-01.yang draft-ietf-bfd-yang-17.txt Email Authors Download the YANG model PASSED          
ietf-bfd-lag@2018-08-01.yang draft-ietf-bfd-yang-17.txt Email Authors Download the YANG model PASSED          
ietf-bfd-mpls-te@2018-08-01.yang draft-ietf-bfd-yang-17.txt Email Authors Download the YANG model PASSED WITH WARNINGS     ./ietf-te@2019-04-09.yang:109: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:109) is converted to 'string' when part of a union
./ietf-te@2019-04-09.yang:113: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:113) is converted to 'string' when part of a union
   
ietf-bfd-mpls@2018-08-01.yang draft-ietf-bfd-yang-17.txt Email Authors Download the YANG model PASSED          
ietf-bfd-types@2018-08-01.yang draft-ietf-bfd-yang-17.txt Email Authors Download the YANG model PASSED          
ietf-bfd-unsolicited@2018-10-27.yang draft-ietf-bfd-unsolicited-00.txt Email Authors Download the YANG model PASSED          
ietf-bfd@2018-08-01.yang draft-ietf-bfd-yang-17.txt Email Authors Download the YANG model PASSED          
ietf-bgp-policy@2019-03-21.yang draft-ietf-idr-bgp-model-05.txt Email Authors Download the YANG model FAILED ietf-bgp-policy@2019-03-21.yang:35: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-bgp-policy@2019-03-21.yang:425: warning: node ietf-bgp-policy::config is not found in ietf-bgp-policy::set-community
ietf-bgp-policy@2019-03-21.yang:425: warning: node ietf-bgp-policy::INLINE is not found in ietf-bgp-policy::inline
ietf-bgp-policy@2019-03-21.yang:445: warning: node ietf-bgp-policy::config is not found in ietf-bgp-policy::set-community
ietf-bgp-policy@2019-03-21.yang:445: warning: node ietf-bgp-policy::REFERENCE is not found in ietf-bgp-policy::reference
ietf-bgp-policy@2019-03-21.yang:476: warning: node ietf-bgp-policy::config is not found in ietf-bgp-policy::set-ext-community
ietf-bgp-policy@2019-03-21.yang:476: warning: node ietf-bgp-policy::INLINE is not found in ietf-bgp-policy::inline
ietf-bgp-policy@2019-03-21.yang:496: warning: node ietf-bgp-policy::config is not found in ietf-bgp-policy::set-ext-community
ietf-bgp-policy@2019-03-21.yang:496: warning: node ietf-bgp-policy::REFERENCE is not found in ietf-bgp-policy::reference
ietf-bgp-policy@2019-03-21.yang:425: warning: node ietf-bgp-policy::config is not found in ietf-bgp-policy::set-community
ietf-bgp-policy@2019-03-21.yang:425: warning: node ietf-bgp-policy::INLINE is not found in ietf-bgp-policy::inline
ietf-bgp-policy@2019-03-21.yang:445: warning: node ietf-bgp-policy::config is not found in ietf-bgp-policy::set-community
ietf-bgp-policy@2019-03-21.yang:445: warning: node ietf-bgp-policy::REFERENCE is not found in ietf-bgp-policy::reference
ietf-bgp-policy@2019-03-21.yang:476: warning: node ietf-bgp-policy::config is not found in ietf-bgp-policy::set-ext-community
ietf-bgp-policy@2019-03-21.yang:476: warning: node ietf-bgp-policy::INLINE is not found in ietf-bgp-policy::inline
ietf-bgp-policy@2019-03-21.yang:496: warning: node ietf-bgp-policy::config is not found in ietf-bgp-policy::set-ext-community
ietf-bgp-policy@2019-03-21.yang:496: warning: node ietf-bgp-policy::REFERENCE is not found in ietf-bgp-policy::reference
/home/bclaise/yang/modules/YANG/ietf-if-l3-vlan@2019-03-05.yang:12: warning: imported module iana-if-type not used
./ietf-if-l3-vlan@2019-03-05.yang:16: error: module 'ieee802-dot1q-types' not found
./ietf-if-l3-vlan@2019-03-05.yang:98: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-if-l3-vlan' (in node 'outer-tag' in module 'ietf-if-l3-vlan' from 'ietf-if-l3-vlan') is not found
./ietf-if-l3-vlan@2019-03-05.yang:118: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-if-l3-vlan' (in node 'outer-tag' in module 'ietf-if-l3-vlan' from 'ietf-if-l3-vlan') is not found
./ietf-if-l3-vlan@2019-03-05.yang:118: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-if-l3-vlan' (in node 'second-tag' in module 'ietf-if-l3-vlan' from 'ietf-if-l3-vlan') is not found
./ietf-routing-policy@2019-03-06.yang:441: error: the node 'vlan-id' from module 'ietf-if-l3-vlan' (in node 'outer-tag' in module 'ietf-if-l3-vlan' from 'ietf-if-l3-vlan') is not found
ietf-bgp-policy@2019-03-21.yang:425: error: the node 'config' from module 'ietf-bgp-policy' (in node 'set-community' in module 'ietf-bgp-policy' from 'ietf-bgp-policy') is not found
ietf-bgp-policy@2019-03-21.yang:425: error: the node 'INLINE' from module 'ietf-bgp-policy' (in node 'inline' in module 'ietf-bgp-policy' from 'ietf-bgp-policy') is not found
ietf-bgp-policy@2019-03-21.yang:425: warning: The when expression refers to descendant node 'INLINE', will probably not work as intended.
ietf-bgp-policy@2019-03-21.yang:445: error: the node 'config' from module 'ietf-bgp-policy' (in node 'set-community' in module 'ietf-bgp-policy' from 'ietf-bgp-policy') is not found
ietf-bgp-policy@2019-03-21.yang:445: error: the node 'REFERENCE' from module 'ietf-bgp-policy' (in node 'reference' in module 'ietf-bgp-policy' from 'ietf-bgp-policy') is not found
ietf-bgp-policy@2019-03-21.yang:445: warning: The when expression refers to descendant node 'REFERENCE', will probably not work as intended.
ietf-bgp-policy@2019-03-21.yang:476: error: the node 'config' from module 'ietf-bgp-policy' (in node 'set-ext-community' in module 'ietf-bgp-policy' from 'ietf-bgp-policy') is not found
ietf-bgp-policy@2019-03-21.yang:476: error: the node 'INLINE' from module 'ietf-bgp-policy' (in node 'inline' in module 'ietf-bgp-policy' from 'ietf-bgp-policy') is not found
ietf-bgp-policy@2019-03-21.yang:476: warning: The when expression refers to descendant node 'INLINE', will probably not work as intended.
ietf-bgp-policy@2019-03-21.yang:496: error: the node 'config' from module 'ietf-bgp-policy' (in node 'set-ext-community' in module 'ietf-bgp-policy' from 'ietf-bgp-policy') is not found
ietf-bgp-policy@2019-03-21.yang:496: error: the node 'REFERENCE' from module 'ietf-bgp-policy' (in node 'reference' in module 'ietf-bgp-policy' from 'ietf-bgp-policy') is not found
ietf-bgp-policy@2019-03-21.yang:496: warning: The when expression refers to descendant node 'REFERENCE', will probably not work as intended.
Warning: no child node '*:config' found for parent 'ietf-bgp-policy:set-community'
XPath: ../config/method=INLINE
ietf-bgp-policy@2019-03-21.yang:425.19: warning(1032): no child node available

Warning: no child node '*:INLINE' found for parent 'ietf-bgp-policy:inline'
XPath: ../config/method=INLINE
ietf-bgp-policy@2019-03-21.yang:425.33: warning(1032): no child node available

Warning: no child node '*:config' found for parent 'ietf-bgp-policy:set-community'
XPath: ../config/method=REFERENCE
ietf-bgp-policy@2019-03-21.yang:445.19: warning(1032): no child node available

Warning: no child node '*:REFERENCE' found for parent 'ietf-bgp-policy:reference'
XPath: ../config/method=REFERENCE
ietf-bgp-policy@2019-03-21.yang:445.33: warning(1032): no child node available

Warning: no child node '*:config' found for parent 'ietf-bgp-policy:set-ext-community'
XPath: ../config/method=INLINE
ietf-bgp-policy@2019-03-21.yang:476.19: warning(1032): no child node available

Warning: no child node '*:INLINE' found for parent 'ietf-bgp-policy:inline'
XPath: ../config/method=INLINE
ietf-bgp-policy@2019-03-21.yang:476.33: warning(1032): no child node available

Warning: no child node '*:config' found for parent 'ietf-bgp-policy:set-ext-community'
XPath: ../config/method=REFERENCE
ietf-bgp-policy@2019-03-21.yang:496.19: warning(1032): no child node available

Warning: no child node '*:REFERENCE' found for parent 'ietf-bgp-policy:reference'
XPath: ../config/method=REFERENCE
ietf-bgp-policy@2019-03-21.yang:496.33: warning(1032): no child node available

***
*** 0 Errors, 8 Warnings
warn: Schema node "config" not found (../config) with context node "/ietf-routing-policy:routing-policy/ietf-routing-policy:policy-definitions/ietf-routing-policy:policy-definition/ietf-routing-policy:statements/ietf-routing-policy:statement/ietf-routing-policy:actions/bgp-actions/set-community/inline".
warn: Schema node "method" not found (../config/method) with context node "/ietf-routing-policy:routing-policy/ietf-routing-policy:policy-definitions/ietf-routing-policy:policy-definition/ietf-routing-policy:statements/ietf-routing-policy:statement/ietf-routing-policy:actions/bgp-actions/set-community/inline".
warn: Schema node "INLINE" not found (../config/method=INLINE) with context node "/ietf-routing-policy:routing-policy/ietf-routing-policy:policy-definitions/ietf-routing-policy:policy-definition/ietf-routing-policy:statements/ietf-routing-policy:statement/ietf-routing-policy:actions/bgp-actions/set-community/inline".
warn: Schema node "config" not found (../config) with context node "/ietf-routing-policy:routing-policy/ietf-routing-policy:policy-definitions/ietf-routing-policy:policy-definition/ietf-routing-policy:statements/ietf-routing-policy:statement/ietf-routing-policy:actions/bgp-actions/set-community/reference".
warn: Schema node "method" not found (../config/method) with context node "/ietf-routing-policy:routing-policy/ietf-routing-policy:policy-definitions/ietf-routing-policy:policy-definition/ietf-routing-policy:statements/ietf-routing-policy:statement/ietf-routing-policy:actions/bgp-actions/set-community/reference".
warn: Schema node "REFERENCE" not found (../config/method=REFERENCE) with context node "/ietf-routing-policy:routing-policy/ietf-routing-policy:policy-definitions/ietf-routing-policy:policy-definition/ietf-routing-policy:statements/ietf-routing-policy:statement/ietf-routing-policy:actions/bgp-actions/set-community/reference".
warn: Schema node "config" not found (../config) with context node "/ietf-routing-policy:routing-policy/ietf-routing-policy:policy-definitions/ietf-routing-policy:policy-definition/ietf-routing-policy:statements/ietf-routing-policy:statement/ietf-routing-policy:actions/bgp-actions/set-ext-community/inline".
warn: Schema node "method" not found (../config/method) with context node "/ietf-routing-policy:routing-policy/ietf-routing-policy:policy-definitions/ietf-routing-policy:policy-definition/ietf-routing-policy:statements/ietf-routing-policy:statement/ietf-routing-policy:actions/bgp-actions/set-ext-community/inline".
warn: Schema node "INLINE" not found (../config/method=INLINE) with context node "/ietf-routing-policy:routing-policy/ietf-routing-policy:policy-definitions/ietf-routing-policy:policy-definition/ietf-routing-policy:statements/ietf-routing-policy:statement/ietf-routing-policy:actions/bgp-actions/set-ext-community/inline".
warn: Schema node "config" not found (../config) with context node "/ietf-routing-policy:routing-policy/ietf-routing-policy:policy-definitions/ietf-routing-policy:policy-definition/ietf-routing-policy:statements/ietf-routing-policy:statement/ietf-routing-policy:actions/bgp-actions/set-ext-community/reference".
warn: Schema node "method" not found (../config/method) with context node "/ietf-routing-policy:routing-policy/ietf-routing-policy:policy-definitions/ietf-routing-policy:policy-definition/ietf-routing-policy:statements/ietf-routing-policy:statement/ietf-routing-policy:actions/bgp-actions/set-ext-community/reference".
warn: Schema node "REFERENCE" not found (../config/method=REFERENCE) with context node "/ietf-routing-policy:routing-policy/ietf-routing-policy:policy-definitions/ietf-routing-policy:policy-definition/ietf-routing-policy:statements/ietf-routing-policy:statement/ietf-routing-policy:actions/bgp-actions/set-ext-community/reference".
ietf-bgp-types@2019-03-21.yang draft-ietf-idr-bgp-model-05.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-bgp-types@2019-03-21.yang:26: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-bgp@2019-03-21.yang draft-ietf-idr-bgp-model-05.txt Email Authors Download the YANG model FAILED ietf-bgp@2019-03-21.yang:87: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
/home/bclaise/yang/modules/YANG/ietf-bgp-common-multiprotocol@2019-03-21.yang:31: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
/home/bclaise/yang/modules/YANG/ietf-bgp-common-structure@2019-03-21.yang:27: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
/home/bclaise/yang/modules/YANG/ietf-bgp-common@2019-03-21.yang:29: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
/home/bclaise/yang/modules/YANG/ietf-bgp-global@2019-03-21.yang:30: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
/home/bclaise/yang/modules/YANG/ietf-bgp-neighbor@2019-03-21.yang:40: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
/home/bclaise/yang/modules/YANG/ietf-bgp-peer-group@2019-03-21.yang:30: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
/home/bclaise/yang/modules/YANG/ietf-bgp-rib-attributes@2019-03-21.yang:32: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-bgp@2019-03-21.yang:168 (at /home/bclaise/yang/modules/YANG/ietf-bgp-rib-attributes@2019-03-21.yang:711): error: XPath syntax error: syntax error before 'or..'
ietf-bgp@2019-03-21.yang:168 (at /home/bclaise/yang/modules/YANG/ietf-bgp-rib-attributes@2019-03-21.yang:747): error: XPath syntax error: syntax error before 'or..'
ietf-bgp@2019-03-21.yang:168 (at /home/bclaise/yang/modules/YANG/ietf-bgp-rib-attributes@2019-03-21.yang:781): error: XPath syntax error: syntax error before 'or..'
/home/bclaise/yang/modules/YANG/ietf-bgp-rib-ext@2019-03-21.yang:24: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
/home/bclaise/yang/modules/YANG/ietf-bgp-rib-shared-attributes@2019-03-21.yang:23: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
/home/bclaise/yang/modules/YANG/ietf-bgp-rib-table-attributes@2019-03-21.yang:29: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
/home/bclaise/yang/modules/YANG/ietf-bgp-rib-tables@2019-03-21.yang:37: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
/home/bclaise/yang/modules/YANG/ietf-bgp-rib-types@2019-03-21.yang:20: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
/home/bclaise/yang/modules/YANG/ietf-bgp-rib@2019-03-21.yang:71: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-bgp@2019-03-21.yang:168 (at /home/bclaise/yang/modules/YANG/ietf-bgp-rib-attributes@2019-03-21.yang:711): error: XPath syntax error: syntax error before 'or..'
ietf-bgp@2019-03-21.yang:168 (at /home/bclaise/yang/modules/YANG/ietf-bgp-rib-attributes@2019-03-21.yang:747): error: XPath syntax error: syntax error before 'or..'
ietf-bgp@2019-03-21.yang:168 (at /home/bclaise/yang/modules/YANG/ietf-bgp-rib-attributes@2019-03-21.yang:781): error: XPath syntax error: syntax error before 'or..'
/home/bclaise/yang/modules/YANG/ietf-if-l3-vlan@2019-03-05.yang:12: warning: imported module iana-if-type not used
./ietf-bgp-common@2019-03-21.yang:192: warning: the type leafref (defined at ./ietf-bgp-common@2019-03-21.yang:192) is converted to 'string' when part of a union
./ietf-bgp-rib-attributes@2019-03-21.yang:708: error: XPath error: XPath syntax error
./ietf-bgp-rib-attributes@2019-03-21.yang:744: error: XPath error: XPath syntax error
./ietf-bgp-rib-attributes@2019-03-21.yang:780: error: XPath error: XPath syntax error
./ietf-if-l3-vlan@2019-03-05.yang:16: error: module 'ieee802-dot1q-types' not found
./ietf-if-l3-vlan@2019-03-05.yang:98: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-if-l3-vlan' (in node 'outer-tag' in module 'ietf-if-l3-vlan' from 'ietf-if-l3-vlan') is not found
./ietf-if-l3-vlan@2019-03-05.yang:118: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-if-l3-vlan' (in node 'outer-tag' in module 'ietf-if-l3-vlan' from 'ietf-if-l3-vlan') is not found
./ietf-if-l3-vlan@2019-03-05.yang:118: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-if-l3-vlan' (in node 'second-tag' in module 'ietf-if-l3-vlan' from 'ietf-if-l3-vlan') is not found
./ietf-routing-policy@2019-03-06.yang:441: error: the node 'vlan-id' from module 'ietf-if-l3-vlan' (in node 'outer-tag' in module 'ietf-if-l3-vlan' from 'ietf-if-l3-vlan') is not found
Error: extra tokens in XPath expression '../type = 'IPV4_NODE_ADDRESS' or../type='IPV4_LOCAL_INTF_ID' or ../type='IPV4_LOCAL_REMOTE_ADDR''
ietf-bgp-rib-attributes@2019-03-21.yang:708.60: error(348): invalid XPath expression syntax

Error: extra tokens in XPath expression '../type = 'IPV6_NODE_ADDRESS' or../type='IPV6_LOCAL_INTF_ID' or ../type='IPV6_LOCAL_REMOTE_ADDR''
ietf-bgp-rib-attributes@2019-03-21.yang:744.60: error(348): invalid XPath expression syntax

Error: extra tokens in XPath expression '../type = 'IPV4_LOCAL_INTF_ID' or../type='IPV6_LOCAL_INTF_ID''
ietf-bgp-rib-attributes@2019-03-21.yang:780.61: error(348): invalid XPath expression syntax

Error: include of submodule 'ietf-bgp-rib-attributes' failed
ietf-bgp-rib-tables@2019-03-21.yang:19.3: error(348): invalid XPath expression syntax

Error: include of submodule 'ietf-bgp-rib-tables' failed
ietf-bgp-rib@2019-03-21.yang:17.3: error(348): invalid XPath expression syntax

Error: include of submodule 'ietf-bgp-rib' failed
ietf-bgp@2019-03-21.yang:46.3: error(348): invalid XPath expression syntax

***
*** 6 Errors, 0 Warnings
warn: Failed to resolve identityref "ietf-bgp-types:IPV4_UNICAST". (/ietf-bgp:afi-safi-name)
warn: Previous warning generated by XPath subexpression[3] "afi-safi-name = 'ietf-bgp-types:IPV4_UNICAST'".
warn: Failed to resolve identityref "ietf-bgp-types:IPV6_UNICAST". (/ietf-bgp:afi-safi-name)
warn: Previous warning generated by XPath subexpression[3] "afi-safi-name = 'ietf-bgp-types:IPV6_UNICAST'".
warn: Failed to resolve identityref "ietf-bgp-types:IPV4_UNICAST". (/ietf-bgp:afi-safi-name)
warn: Previous warning generated by XPath subexpression[3] "afi-safi-name = 'ietf-bgp-types:IPV4_UNICAST'".
warn: Failed to resolve identityref "ietf-bgp-types:IPV6_UNICAST". (/ietf-bgp:afi-safi-name)
warn: Previous warning generated by XPath subexpression[3] "afi-safi-name = 'ietf-bgp-types:IPV6_UNICAST'".
warn: Failed to resolve identityref "ietf-bgp-types:IPV4_UNICAST". (/ietf-bgp:afi-safi-name)
warn: Previous warning generated by XPath subexpression[3] "afi-safi-name = 'ietf-bgp-types:IPV4_UNICAST'".
warn: Failed to resolve identityref "ietf-bgp-types:IPV6_UNICAST". (/ietf-bgp:afi-safi-name)
warn: Previous warning generated by XPath subexpression[3] "afi-safi-name = 'ietf-bgp-types:IPV6_UNICAST'".
warn: Identityref "type" comparison with identity "tunnel-color" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "type = 'tunnel-color'".
warn: Identityref "type" comparison with identity "srte-preference" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "type = 'srte-preference'".
warn: Identityref "type" comparison with identity "srte-binding-sid" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "type = 'srte-binding-sid'".
warn: Identityref "type" comparison with identity "tunnel-remote-endpoint" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "type = 'tunnel-remote-endpoint'".
warn: Identityref "type" comparison with identity "srte-segment-list" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "type = 'srte-segment-list'".
warn: Identityref "afi-safi-name" comparison with identity "srte-policy-ipv4" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "afi-safi-name = 'srte-policy-ipv4'".
warn: Failed to resolve identityref "srte-policy-ipv4". (/ietf-bgp:afi-safi-name)
warn: Previous warning generated by XPath subexpression[3] "afi-safi-name = 'srte-policy-ipv4'".
warn: Identityref "afi-safi-name" comparison with identity "srte-policy-ipv6" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "afi-safi-name = 'srte-policy-ipv6'".
warn: Failed to resolve identityref "srte-policy-ipv6". (/ietf-bgp:afi-safi-name)
warn: Previous warning generated by XPath subexpression[3] "afi-safi-name = 'srte-policy-ipv6'".
ietf-bier-te@2019-03-23.yang draft-ietf-bier-te-yang-00.txt Email Authors Download the YANG model PASSED          
ietf-bier@2019-05-14.yang draft-ietf-bier-bier-yang-05.txt Email Authors Download the YANG model FAILED ietf-bier@2019-05-14.yang:14: error: module "ietf-isis" not found in search path
ietf-bier@2019-05-14.yang:47: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-bier@2019-05-14.yang:14: error: module "ietf-isis" not found in search path
ietf-bier@2019-05-14.yang:14: error: module 'ietf-isis' not found
ietf-bier@2019-05-14.yang:381: error: node 'isis' in module 'ietf-isis' not found
Error: 'ietf-bier@2019-05-14.yang' import of module 'ietf-isis' failed
ietf-bier@2019-05-14.yang:14.5: error(236): module not found

Error: object 'isis' not found in module ietf-bier
ietf-bier@2019-05-14.yang:381.6: error(251): definition segment not found

***
*** 2 Errors, 0 Warnings
err : Data model "ietf-isis" not found.
err : Importing "ietf-isis" module into "ietf-bier" failed.
err : Module "ietf-bier" parsing failed.
ietf-bulk-data-export@2019-03-11.yang draft-boydseda-ipfix-psamp-bulk-data-yang-model-01.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-bulk-data-export@2019-03-11.yang:50: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-bulk-data-export@2019-03-11.yang:137: 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-comi@2019-03-28.yang draft-ietf-core-comi-05.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-comi@2019-03-28.yang:36: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-composed-vpn-svc@2018-08-21.yang draft-evenwu-opsawg-yang-composed-vpn-03.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-composed-vpn-svc@2018-08-21.yang:23: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-constrained-voucher-request@2018-09-01.yang draft-ietf-anima-constrained-voucher-03.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-constrained-voucher-request@2018-09-01.yang:54: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-constrained-voucher-request@2018-09-01.yang:54: 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-constrained-voucher@2018-09-01.yang draft-ietf-anima-constrained-voucher-03.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-constrained-voucher@2018-09-01.yang:49: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-constrained-voucher@2018-09-01.yang:49: 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-constrained-yang-library@2019-03-28.yang draft-veillette-core-yang-library-04.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-constrained-yang-library@2019-03-28.yang:153: 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-crypto-types@2019-06-07.yang draft-ietf-netconf-crypto-types-07.txt Email Authors Download the YANG model PASSED          
ietf-detnet-qos@2018-10-13.yang draft-xiong-detnet-qos-yang-01.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-detnet-qos@2018-10-13.yang:26: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-detnet-topology@2018-09-10.yang draft-ietf-detnet-topology-yang-00.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-detnet-topology@2018-09-10.yang:49: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-detnet@2018-09-10.yang draft-ietf-detnet-yang-02.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-detnet@2018-09-10.yang:10: warning: imported module ietf-interfaces not used
ietf-detnet@2018-09-10.yang:22: warning: imported module ietf-routing-types not used
ietf-detnet@2018-09-10.yang:51: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-detnet@2018-09-10.yang:946: 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-detnet@2018-09-10.yang:10: warning: imported module ietf-interfaces not used
ietf-detnet@2018-09-10.yang:22: warning: imported module ietf-routing-types not used
  Warning: Module 'ietf-interfaces' not used
ietf-detnet@2018-09-10.yang:10.3: warning(1015): import not used

Warning: Module 'ietf-routing-types' not used
ietf-detnet@2018-09-10.yang:22.3: warning(1015): import not used

***
*** 0 Errors, 2 Warnings
 
ietf-dhcpv6-client@2018-09-04.yang draft-ietf-dhc-dhcpv6-yang-08.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-dhcpv6-client@2018-09-04.yang:26: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-dhcpv6-options@2018-09-04.yang draft-ietf-dhc-dhcpv6-yang-08.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-dhcpv6-options@2018-09-04.yang:26: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-dhcpv6-options@2018-09-04.yang:1153: 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-dhcpv6-relay@2018-09-04.yang draft-ietf-dhc-dhcpv6-yang-08.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-dhcpv6-relay@2018-09-04.yang:30: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-dhcpv6-server@2018-09-04.yang draft-ietf-dhc-dhcpv6-yang-08.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-dhcpv6-server@2018-09-04.yang:31: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-dhcpv6-server@2018-09-04.yang:323: 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-dhcpv6-types@2018-09-04.yang draft-ietf-dhc-dhcpv6-yang-08.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-dhcpv6-types@2018-09-04.yang:22: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-diam-trafficclassifier@2018-05-17.yang draft-ietf-dmm-fpc-yang-00.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-diam-trafficclassifier@2018-05-17.yang:49: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-diffserv@2019-03-13.yang draft-asechoud-rtgwg-qos-model-09.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-diffserv@2019-03-13.yang:49: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-dmm-fpc-settingsext@2018-05-17.yang draft-ietf-dmm-fpc-yang-00.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-dmm-fpc-settingsext@2018-05-17.yang:54: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-dmm-fpc@2018-05-17.yang draft-ietf-dmm-fpc-yang-00.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-dmm-fpc@2018-05-17.yang:50: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-dmm-fpc@2018-05-17.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-dots-call-home@2019-04-25.yang draft-ietf-dots-signal-call-home-02.txt Email Authors Download the YANG model PASSED WITH WARNINGS   /home/bclaise/yang/modules/YANG/ietf-dots-signal-channel@2019-01-17.yang:474 (at /home/bclaise/yang/modules/YANG/ietf-dots-signal-channel@2019-01-17.yang:178): warning: node ietf-dots-signal-channel::conflict-cause is not found in ietf-dots-signal-channel::conflict-scope
     
ietf-dots-data-channel@2019-05-09.yang draft-ietf-dots-data-channel-29.txt Email Authors Download the YANG model PASSED          
ietf-dots-signal-channel@2019-01-17.yang draft-ietf-dots-signal-channel-34.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-dots-signal-channel@2019-01-17.yang:474 (at ietf-dots-signal-channel@2019-01-17.yang:178): warning: node ietf-dots-signal-channel::conflict-cause is not found in ietf-dots-signal-channel::conflict-scope
ietf-dots-signal-channel@2019-01-17.yang:474 (at ietf-dots-signal-channel@2019-01-17.yang:178): warning: node ietf-dots-signal-channel::conflict-cause is not found in ietf-dots-signal-channel::conflict-scope
     
ietf-dots-signal-control@2019-05-13.yang draft-ietf-dots-signal-filter-control-01.txt Email Authors Download the YANG model PASSED WITH WARNINGS   /home/bclaise/yang/modules/YANG/ietf-dots-signal-channel@2019-01-17.yang:474 (at /home/bclaise/yang/modules/YANG/ietf-dots-signal-channel@2019-01-17.yang:178): warning: node ietf-dots-signal-channel::conflict-cause is not found in ietf-dots-signal-channel::conflict-scope
     
ietf-eth-te-topology@2019-03-01.yang draft-zheng-ccamp-client-topo-yang-05.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-eth-te-topology@2019-03-01.yang:44: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-eth-te-topology@2019-03-01.yang:305: warning: node ietf-network-topology::eth-tran-topology is not found in ietf-te-topology::te-topology
ietf-eth-te-topology@2019-03-01.yang:305: warning: node ietf-network-topology::eth-tran-topology is not found in ietf-te-topology::te-topology
    warn: Schema node "eth-tran-topology" not found (../../ietf-network:network-types/ietf-te-topology:te-topology/eth-tran-topology) with context node "/ietf-network:networks/ietf-network:network/ietf-network:node/termination-point".
ietf-eth-te-tunnel@2018-03-01.yang draft-zheng-ccamp-client-tunnel-yang-04.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-eth-te-tunnel@2018-03-01.yang:31: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
  ./ietf-te@2019-04-09.yang:109: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:109) is converted to 'string' when part of a union
./ietf-te@2019-04-09.yang:113: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:113) is converted to 'string' when part of a union
   
ietf-eth-tran-service@2019-03-27.yang draft-zheng-ccamp-client-signal-yang-07.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-eth-tran-service@2019-03-27.yang:61: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-eth-tran-types@2019-03-27.yang draft-zheng-ccamp-client-signal-yang-07.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-eth-tran-types@2019-03-27.yang:36: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-ethernet-segment@2019-03-09.yang draft-ietf-bess-evpn-yang-07.txt Email Authors Download the YANG model FAILED ietf-ethernet-segment@2019-03-09.yang:21: error: module "ietf-pseudowires" not found in search path
ietf-ethernet-segment@2019-03-09.yang:27: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-ethernet-segment@2019-03-09.yang:21: error: module "ietf-pseudowires" not found in search path
ietf-ethernet-segment@2019-03-09.yang:21: error: module 'ietf-pseudowires' not found
Error: 'ietf-ethernet-segment@2019-03-09.yang' import of module 'ietf-pseudowires' failed
ietf-ethernet-segment@2019-03-09.yang:21.3: error(236): module not found

Error: typedef definition for 'pw:pseudowire-ref' not found in module ietf-pseudowires
ietf-ethernet-segment@2019-03-09.yang:170.18: error(250): definition not found

***
*** 2 Errors, 0 Warnings
err : Data model "ietf-pseudowires" not found.
err : Importing "ietf-pseudowires" module into "ietf-ethernet-segment" failed.
err : Module "ietf-ethernet-segment" parsing failed.
ietf-event-trigger@2018-12-18.yang draft-wwx-netmod-event-yang-01.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-event-trigger@2018-12-18.yang:16: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-event@2018-12-18.yang draft-wwx-netmod-event-yang-01.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-event@2018-12-18.yang:20: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-evpn@2019-03-09.yang draft-ietf-bess-evpn-yang-07.txt Email Authors Download the YANG model FAILED ietf-evpn@2019-03-09.yang:21: error: module "ietf-l2vpn" not found in search path
ietf-evpn@2019-03-09.yang:25: error: module "ietf-pseudowires" not found in search path
ietf-evpn@2019-03-09.yang:35: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-evpn@2019-03-09.yang:21: error: module "ietf-l2vpn" not found in search path
ietf-evpn@2019-03-09.yang:25: error: module "ietf-pseudowires" not found in search path
./ietf-ethernet-segment@2019-03-09.yang:21: error: module 'ietf-pseudowires' not found
ietf-evpn@2019-03-09.yang:21: error: module 'ietf-l2vpn' not found
ietf-evpn@2019-03-09.yang:25: error: module 'ietf-pseudowires' not found
ietf-evpn@2019-03-09.yang:465: error: node 'l2vpn' in module 'ietf-l2vpn' not found
ietf-evpn@2019-03-09.yang:476: error: the node 'type' from module 'ietf-l2vpn' (in node 'network-instance' from 'ietf-network-instance') is not found
ietf-evpn@2019-03-09.yang:481: warning: The 'must' expression will fail: the node 'pseudowires' from module 'ietf-pseudowires' is not found
ietf-evpn@2019-03-09.yang:481: warning: The 'must' expression will fail: the node 'pseudowires' from module 'ietf-pseudowires' is not found
ietf-evpn@2019-03-09.yang:481: warning: The 'must' expression will fail: the node 'pseudowires' from module 'ietf-pseudowires' is not found
ietf-evpn@2019-03-09.yang:481: warning: The 'must' expression will fail: the node 'endpoint' from module 'ietf-l2vpn' (in node 'network-instance' from 'ietf-network-instance') is not found
ietf-evpn@2019-03-09.yang:481: warning: The 'must' expression will fail: the node 'endpoint' from module 'ietf-l2vpn' (in node 'network-instance' from 'ietf-network-instance') is not found
ietf-evpn@2019-03-09.yang:481: warning: The 'must' expression will fail: the node 'endpoint' from module 'ietf-l2vpn' (in node 'network-instance' from 'ietf-network-instance') is not found
Error: 'ietf-evpn@2019-03-09.yang' import of module 'ietf-l2vpn' failed
ietf-evpn@2019-03-09.yang:21.3: error(236): module not found

Error: 'ietf-evpn@2019-03-09.yang' import of module 'ietf-pseudowires' failed
ietf-evpn@2019-03-09.yang:25.3: error(236): module not found

Error: 'ietf-ethernet-segment@2019-03-09.yang' import of module 'ietf-pseudowires' failed
ietf-ethernet-segment@2019-03-09.yang:21.3: error(236): module not found

Error: typedef definition for 'pw:pseudowire-ref' not found in module ietf-pseudowires
ietf-ethernet-segment@2019-03-09.yang:170.18: error(250): definition not found

Error: 'ietf-evpn@2019-03-09.yang' import of module 'ietf-ethernet-segment' failed
ietf-evpn@2019-03-09.yang:29.3: error(250): definition not found

Error: typedef definition for 'es:ethernet-segment-identifier-type' not found in module ietf-ethernet-segment
ietf-evpn@2019-03-09.yang:303.20: error(250): definition not found

Error: typedef definition for 'es:ethernet-segment-identifier-type' not found in module ietf-ethernet-segment
ietf-evpn@2019-03-09.yang:321.20: error(250): definition not found

Error: typedef definition for 'es:ethernet-segment-identifier-type' not found in module ietf-ethernet-segment
ietf-evpn@2019-03-09.yang:367.20: error(250): definition not found

Error: typedef definition for 'es:ethernet-segment-identifier-type' not found in module ietf-ethernet-segment
ietf-evpn@2019-03-09.yang:387.20: error(250): definition not found

Error: Module for prefix 'l2vpn' not found
ietf-evpn@2019-03-09.yang:476.10: error(236): module not found

Error: Module for prefix 'pw' not found
ietf-evpn@2019-03-09.yang:481.25: error(236): module not found

Error: wrong number of parameters got 0, need 1 for function 'boolean'
ietf-evpn@2019-03-09.yang:481.25: error(233): missing parameter

Error: wrong number of parameters got 0, need 1 for function 'not'
ietf-evpn@2019-03-09.yang:481.25: error(233): missing parameter

Error: object 'pseudowires' not found in module ietf-evpn in Xpath target /pw:pseudowires/pw:pseudowire/pw:pw-type
ietf-evpn@2019-03-09.yang:447.3: error(250): definition not found

Error: object 'l2vpn' not found in module ietf-evpn
ietf-evpn@2019-03-09.yang:465.3: error(251): definition segment not found

Error: object 'l2vpn' not found in module ietf-evpn
ietf-evpn@2019-03-09.yang:474.3: error(251): definition segment not found

***
*** 14 Errors, 0 Warnings
err : Data model "ietf-l2vpn" not found.
err : Importing "ietf-l2vpn" module into "ietf-evpn" failed.
err : Module "ietf-evpn" parsing failed.
ietf-ext-xponder-wdm-if@2018-10-22.yang draft-ietf-ccamp-dwdm-if-param-yang-00.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-ext-xponder-wdm-if@2018-10-22.yang:5: warning: imported module ietf-interfaces not used
ietf-ext-xponder-wdm-if@2018-10-22.yang:32: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-ext-xponder-wdm-if@2018-10-22.yang:5: warning: imported module ietf-interfaces not used
  Warning: Module 'ietf-interfaces' not used
ietf-ext-xponder-wdm-if@2018-10-22.yang:5.5: warning(1015): import not used

***
*** 0 Errors, 1 Warnings
 
ietf-factory-default@2019-05-03.yang draft-wu-netmod-factory-default-03.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-factory-default@2019-05-03.yang:55: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-factory-default@2019-05-03.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).
       
ietf-flex-algo@2019-04-26.yang draft-rasool-lsr-flex-algo-yang-00.txt Email Authors Download the YANG model FAILED ietf-flex-algo@2019-04-26.yang:15: error: module "ietf-isis" not found in search path
ietf-flex-algo@2019-04-26.yang:51: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-flex-algo@2019-04-26.yang:111: 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-flex-algo@2019-04-26.yang:15: error: module "ietf-isis" not found in search path
ietf-flex-algo@2019-04-26.yang:15: error: module 'ietf-isis' not found
ietf-flex-algo@2019-04-26.yang:225: error: node 'isis' in module 'ietf-isis' not found
ietf-flex-algo@2019-04-26.yang:225: error: node 'database' in module 'ietf-isis' not found
ietf-flex-algo@2019-04-26.yang:225: error: node 'levels' in module 'ietf-isis' not found
ietf-flex-algo@2019-04-26.yang:225: error: node 'lsp' in module 'ietf-isis' not found
ietf-flex-algo@2019-04-26.yang:225: error: node 'router-capabilities' in module 'ietf-isis' not found
Error: 'ietf-flex-algo@2019-04-26.yang' import of module 'ietf-isis' failed
ietf-flex-algo@2019-04-26.yang:15.3: error(236): module not found

Error: typedef definition for 'isis:level' not found in module ietf-isis
ietf-flex-algo@2019-04-26.yang:256.14: error(250): definition not found

Error: object 'isis' not found in module ietf-flex-algo
ietf-flex-algo@2019-04-26.yang:225.5: error(251): definition segment not found

Error: object 'isis' not found in module ietf-flex-algo
ietf-flex-algo@2019-04-26.yang:239.3: error(251): definition segment not found

***
*** 4 Errors, 0 Warnings
err : Data model "ietf-isis" not found.
err : Importing "ietf-isis" module into "ietf-flex-algo" failed.
err : Module "ietf-flex-algo" parsing failed.
ietf-flexe-types@2019-06-06.yang draft-xiaobn-ccamp-flexe-yang-mod-02.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-flexe-types@2019-06-06.yang:28: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-flexe-yang@2019-06-06.yang draft-xiaobn-ccamp-flexe-yang-mod-02.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-flexe-yang@2019-06-06.yang:39: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-flexe@2019-02-25.yang draft-jiang-ccamp-flexe-yang-00.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-flexe@2019-02-25.yang:27: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
    Warning: compare value 'ianaift:flexethernet' invalid for object 'ietf-interfaces:type type:identityref'
XPath:if:type = 'ianaift:flexethernet'
ietf-flexe@2019-02-25.yang: line 131: warning(1052): XPath compare value invalid for YANG type

***
*** 0 Errors, 1 Warnings
warn: Failed to resolve identityref "iana-if-type:flexethernet". (/ietf-interfaces:type)
warn: Previous warning generated by XPath subexpression[0] "ietf-interfaces:type = 'iana-if-type:flexethernet'".
ietf-flexi-grid-media-channel@2019-03-24.yang draft-ietf-ccamp-flexigrid-media-channel-yang-02.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-flexi-grid-media-channel@2019-03-24.yang:31: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
  ./ietf-te@2019-04-09.yang:109: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:109) is converted to 'string' when part of a union
./ietf-te@2019-04-09.yang:113: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:113) is converted to 'string' when part of a union
   
ietf-flexi-grid-topology@2019-03-24.yang draft-ietf-ccamp-flexigrid-yang-03.txt Email Authors Download the YANG model FAILED ietf-flexi-grid-topology@2019-03-24.yang:68: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-flexi-grid-topology@2019-03-24.yang:1823: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
       
ietf-flexible-encapsulation@2019-03-05.yang draft-ietf-netmod-sub-intf-vlan-model-05.txt Email Authors Download the YANG model FAILED ietf-flexible-encapsulation@2019-03-05.yang:12: warning: imported module iana-if-type not used
ietf-flexible-encapsulation@2019-03-05.yang:45: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-flexible-encapsulation@2019-03-05.yang:12: warning: imported module iana-if-type not used
ietf-flexible-encapsulation@2019-03-05.yang:20: error: module 'ieee802-dot1q-types' not found
ietf-flexible-encapsulation@2019-03-05.yang:135: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-flexible-encapsulation' (in node 'outer-tag' in module 'ietf-flexible-encapsulation' from 'ietf-flexible-encapsulation') is not found
ietf-flexible-encapsulation@2019-03-05.yang:157: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-flexible-encapsulation' (in node 'outer-tag' in module 'ietf-flexible-encapsulation' from 'ietf-flexible-encapsulation') is not found
ietf-flexible-encapsulation@2019-03-05.yang:157: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-flexible-encapsulation' (in node 'second-tag' in module 'ietf-flexible-encapsulation' from 'ietf-flexible-encapsulation') is not found
ietf-flexible-encapsulation@2019-03-05.yang:219: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-flexible-encapsulation' (in node 'outer-tag' in module 'ietf-flexible-encapsulation' from 'ietf-flexible-encapsulation') is not found
ietf-flexible-encapsulation@2019-03-05.yang:219: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-flexible-encapsulation' (in node 'outer-tag' in module 'ietf-flexible-encapsulation' from 'ietf-flexible-encapsulation') is not found
ietf-flexible-encapsulation@2019-03-05.yang:219: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-flexible-encapsulation' (in node 'outer-tag' in module 'ietf-flexible-encapsulation' from 'ietf-flexible-encapsulation') is not found
ietf-flexible-encapsulation@2019-03-05.yang:237: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-flexible-encapsulation' (in node 'outer-tag' in module 'ietf-flexible-encapsulation' from 'ietf-flexible-encapsulation') is not found
ietf-flexible-encapsulation@2019-03-05.yang:237: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-flexible-encapsulation' (in node 'second-tag' in module 'ietf-flexible-encapsulation' from 'ietf-flexible-encapsulation') is not found
ietf-flexible-encapsulation@2019-03-05.yang:237: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-flexible-encapsulation' (in node 'outer-tag' in module 'ietf-flexible-encapsulation' from 'ietf-flexible-encapsulation') is not found
ietf-flexible-encapsulation@2019-03-05.yang:237: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-flexible-encapsulation' (in node 'second-tag' in module 'ietf-flexible-encapsulation' from 'ietf-flexible-encapsulation') is not found
ietf-flexible-encapsulation@2019-03-05.yang:237: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-flexible-encapsulation' (in node 'outer-tag' in module 'ietf-flexible-encapsulation' from 'ietf-flexible-encapsulation') is not found
ietf-flexible-encapsulation@2019-03-05.yang:237: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-flexible-encapsulation' (in node 'second-tag' in module 'ietf-flexible-encapsulation' from 'ietf-flexible-encapsulation') is not found
ietf-flexible-encapsulation@2019-03-05.yang:385: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-flexible-encapsulation' (in node 'outer-tag' in module 'ietf-flexible-encapsulation' from 'ietf-flexible-encapsulation') is not found
ietf-flexible-encapsulation@2019-03-05.yang:404: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-flexible-encapsulation' (in node 'outer-tag' in module 'ietf-flexible-encapsulation' from 'ietf-flexible-encapsulation') is not found
ietf-flexible-encapsulation@2019-03-05.yang:404: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-flexible-encapsulation' (in node 'second-tag' in module 'ietf-flexible-encapsulation' from 'ietf-flexible-encapsulation') is not found
   
ietf-geo-location@2019-02-17.yang draft-ietf-netmod-geo-location-01.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-geo-location@2019-02-17.yang:37: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-geo-location@2019-02-17.yang:37: 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-http-client@2019-06-07.yang draft-kwatsen-netconf-http-client-server-03.txt Email Authors Download the YANG model PASSED          
ietf-http-server@2019-06-07.yang draft-kwatsen-netconf-http-client-server-03.txt Email Authors Download the YANG model PASSED          
ietf-i2nsf-capability@2019-03-28.yang draft-ietf-i2nsf-capability-data-model-04.txt Email Authors Download the YANG model PASSED          
ietf-i2nsf-cfi-policy@2019-04-04.yang draft-ietf-i2nsf-consumer-facing-interface-dm-04.txt Email Authors Download the YANG model PASSED          
ietf-i2nsf-monitor@2019-03-11.yang draft-ietf-i2nsf-nsf-monitoring-data-model-00.txt Email Authors Download the YANG model PASSED          
ietf-i2nsf-policy-rule-for-nsf@2019-03-28.yang draft-ietf-i2nsf-nsf-facing-interface-dm-05.txt Email Authors Download the YANG model PASSED          
ietf-i2nsf-reg-interface@2019-03-28.yang draft-ietf-i2nsf-registration-interface-dm-03.txt Email Authors Download the YANG model PASSED          
ietf-if-l3-vlan@2019-03-05.yang draft-ietf-netmod-sub-intf-vlan-model-05.txt Email Authors Download the YANG model FAILED ietf-if-l3-vlan@2019-03-05.yang:12: warning: imported module iana-if-type not used
ietf-if-l3-vlan@2019-03-05.yang:43: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-if-l3-vlan@2019-03-05.yang:12: warning: imported module iana-if-type not used
ietf-if-l3-vlan@2019-03-05.yang:16: error: module 'ieee802-dot1q-types' not found
ietf-if-l3-vlan@2019-03-05.yang:98: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-if-l3-vlan' (in node 'outer-tag' in module 'ietf-if-l3-vlan' from 'ietf-if-l3-vlan') is not found
ietf-if-l3-vlan@2019-03-05.yang:118: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-if-l3-vlan' (in node 'outer-tag' in module 'ietf-if-l3-vlan' from 'ietf-if-l3-vlan') is not found
ietf-if-l3-vlan@2019-03-05.yang:118: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-if-l3-vlan' (in node 'second-tag' in module 'ietf-if-l3-vlan' from 'ietf-if-l3-vlan') is not found
   
ietf-igmp-mld-proxy@2019-05-14.yang draft-zhao-pim-igmp-mld-proxy-yang-02.txt Email Authors Download the YANG model PASSED          
ietf-igmp-mld-snooping@2019-01-08.yang draft-ietf-pim-igmp-mld-snooping-yang-07.txt Email Authors Download the YANG model FAILED ietf-igmp-mld-snooping@2019-01-08.yang:27: error: module "ietf-l2vpn" not found in search path
ietf-igmp-mld-snooping@2019-01-08.yang:34: error: module "ietf-pseudowires" not found in search path
ietf-igmp-mld-snooping@2019-01-08.yang:27: error: module "ietf-l2vpn" not found in search path
ietf-igmp-mld-snooping@2019-01-08.yang:34: error: module "ietf-pseudowires" not found in search path
ietf-igmp-mld-snooping@2019-01-08.yang:27: error: module 'ietf-l2vpn' not found
ietf-igmp-mld-snooping@2019-01-08.yang:34: error: module 'ietf-pseudowires' not found
ietf-igmp-mld-snooping@2019-01-08.yang:38: error: module 'ieee802-dot1q-bridge' not found
ietf-igmp-mld-snooping@2019-01-08.yang:1026: error: node 'l2vpn' in module 'ietf-l2vpn' not found
Error: 'ietf-igmp-mld-snooping@2019-01-08.yang' import of module 'ietf-l2vpn' failed
ietf-igmp-mld-snooping@2019-01-08.yang:27.3: error(236): module not found

Error: 'ietf-igmp-mld-snooping@2019-01-08.yang' import of module 'ietf-pseudowires' failed
ietf-igmp-mld-snooping@2019-01-08.yang:34.3: error(236): module not found

Error: typedef definition for 'pw:pseudowire-ref' not found in module ietf-pseudowires
ietf-igmp-mld-snooping@2019-01-08.yang:291.14: error(250): definition not found

Error: typedef definition for 'pw:pseudowire-ref' not found in module ietf-pseudowires
ietf-igmp-mld-snooping@2019-01-08.yang:429.12: error(250): definition not found

Error: typedef definition for 'pw:pseudowire-ref' not found in module ietf-pseudowires
ietf-igmp-mld-snooping@2019-01-08.yang:489.13: error(250): definition not found

Error: typedef definition for 'pw:pseudowire-ref' not found in module ietf-pseudowires
ietf-igmp-mld-snooping@2019-01-08.yang:622.12: error(250): definition not found

Error: typedef definition for 'pw:pseudowire-ref' not found in module ietf-pseudowires
ietf-igmp-mld-snooping@2019-01-08.yang:715.12: error(250): definition not found

Error: object 'l2vpn' not found in module ietf-igmp-mld-snooping
ietf-igmp-mld-snooping@2019-01-08.yang:1026.3: error(251): definition segment not found

***
*** 8 Errors, 0 Warnings
err : Data model "ietf-l2vpn" not found.
err : Importing "ietf-l2vpn" module into "ietf-igmp-mld-snooping" failed.
err : Module "ietf-igmp-mld-snooping" parsing failed.
ietf-igmp-mld@2019-05-29.yang draft-ietf-pim-igmp-mld-yang-14.txt Email Authors Download the YANG model FAILED ietf-igmp-mld@2019-05-29.yang:565: 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: Mandatory object 'input' not allowed in external augment statement
ietf-igmp-mld@2019-05-29.yang:1088.9: error(335): mandatory object not allowed

Error: Mandatory object 'interface' not allowed in external augment statement
ietf-igmp-mld@2019-05-29.yang:1089.11: error(335): mandatory object not allowed

Error: Mandatory object 'group-address' not allowed in external augment statement
ietf-igmp-mld@2019-05-29.yang:1114.11: error(335): mandatory object not allowed

Error: Mandatory object 'source-address' not allowed in external augment statement
ietf-igmp-mld@2019-05-29.yang:1130.11: error(335): mandatory object not allowed

Error: Mandatory object 'input' not allowed in external augment statement
ietf-igmp-mld@2019-05-29.yang:1204.9: error(335): mandatory object not allowed

Error: Mandatory object 'interface' not allowed in external augment statement
ietf-igmp-mld@2019-05-29.yang:1205.11: error(335): mandatory object not allowed

***
*** 6 Errors, 0 Warnings
 
ietf-inet-types@2019-03-11.yang draft-schoenw-netmod-rfc6991-bis-01.txt Email Authors Download the YANG model PASSED          
ietf-interface-protection@2018-11-28.yang draft-ietf-ccamp-mw-yang-13.txt Email Authors Download the YANG model PASSED          
ietf-interfaces-common@2019-03-05.yang draft-ietf-netmod-intf-ext-yang-07.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-interfaces-common@2019-03-05.yang:55: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-interfaces-ethernet-like@2019-03-05.yang draft-ietf-netmod-intf-ext-yang-07.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-interfaces-ethernet-like@2019-03-05.yang:17: warning: imported module iana-if-type not used
ietf-interfaces-ethernet-like@2019-03-05.yang:58: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-interfaces-ethernet-like@2019-03-05.yang:17: warning: imported module iana-if-type not used
     
ietf-ioam@2018-07-02.yang draft-zhou-ippm-ioam-yang-03.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-ioam@2018-07-02.yang:23: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
      warn: Identityref "filter-type" comparison with identity "acl-filter" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "filter-type = 'acl-filter'".
warn: Identityref "node-action" comparison with identity "encapsulate" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "node-action = 'encapsulate'".
warn: Identityref "node-action" comparison with identity "encapsulate" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "node-action = 'encapsulate'".
warn: Identityref "node-action" comparison with identity "encapsulate" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "node-action = 'encapsulate'".
warn: Identityref "node-action" comparison with identity "encapsulate" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "node-action = 'encapsulate'".
warn: Identityref "node-action" comparison with identity "encapsulate" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "node-action = 'encapsulate'".
warn: Identityref "node-action" comparison with identity "encapsulate" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "node-action = 'encapsulate'".
ietf-ipfix@2019-03-11.yang draft-boydseda-ipfix-psamp-bulk-data-yang-model-01.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-ipfix@2019-03-11.yang:54: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-ipfix@2019-03-11.yang:264: 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-ipsec-common@2019-03-11.yang draft-ietf-i2nsf-sdn-ipsec-flow-protection-04.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-ipsec-common@2019-03-11.yang:39: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-ipsec-ike@2019-03-11.yang draft-ietf-i2nsf-sdn-ipsec-flow-protection-04.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-ipsec-ike@2019-03-11.yang:44: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-ipsec-ike@2019-03-11.yang:144: 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-ipsec-ikeless@2019-03-11.yang draft-ietf-i2nsf-sdn-ipsec-flow-protection-04.txt Email Authors Download the YANG model FAILED ietf-ipsec-ikeless@2019-03-11.yang:40: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-ipsec-ikeless@2019-03-11.yang:150: 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: identityref has unknown base value (mac-algorithm)
ietf-ipsec-ikeless@2019-03-11.yang:186.76: error(250): definition not found

Error: identityref has unknown base value (encryption-algorithm)
ietf-ipsec-ikeless@2019-03-11.yang:197.77: error(250): definition not found

Error: identityref has unknown base value (mac-algorithm)
ietf-ipsec-ikeless@2019-03-11.yang:204.76: error(250): definition not found

Error: identityref has unknown base value (encryption-algorithm)
ietf-ipsec-ikeless@2019-03-11.yang:239.45: error(250): definition not found

Error: identityref has unknown base value (mac-algorithm)
ietf-ipsec-ikeless@2019-03-11.yang:240.49: error(250): definition not found

***
*** 5 Errors, 0 Warnings
 
ietf-isis-ppr@2019-03-10.yang draft-qct-lsr-ppr-yang-01.txt Email Authors Download the YANG model FAILED ietf-isis-ppr@2019-03-10.yang:19: error: module "ietf-isis" not found in search path
ietf-isis-ppr@2019-03-10.yang:143: 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-isis-ppr@2019-03-10.yang:478: error: the list at "ietf-isis-ppr@2019-03-10.yang:478 (at ietf-isis-ppr@2019-03-10.yang:398)" needs at least one key because it is used as config
ietf-isis-ppr@2019-03-10.yang:478: error: the list at "ietf-isis-ppr@2019-03-10.yang:478 (at ietf-isis-ppr@2019-03-10.yang:87)" needs at least one key because it is used as config
ietf-isis-ppr@2019-03-10.yang:478: error: the list at "ietf-isis-ppr@2019-03-10.yang:478 (at ietf-isis-ppr@2019-03-10.yang:210)" needs at least one key because it is used as config
ietf-isis-ppr@2019-03-10.yang:478: error: the list at "ietf-isis-ppr@2019-03-10.yang:478 (at ietf-isis-ppr@2019-03-10.yang:87)" needs at least one key because it is used as config
ietf-isis-ppr@2019-03-10.yang:19: error: module "ietf-isis" not found in search path
ietf-isis-ppr@2019-03-10.yang:478: error: the list at "ietf-isis-ppr@2019-03-10.yang:478 (at ietf-isis-ppr@2019-03-10.yang:398)" needs at least one key because it is used as config
ietf-isis-ppr@2019-03-10.yang:478: error: the list at "ietf-isis-ppr@2019-03-10.yang:478 (at ietf-isis-ppr@2019-03-10.yang:87)" needs at least one key because it is used as config
ietf-isis-ppr@2019-03-10.yang:478: error: the list at "ietf-isis-ppr@2019-03-10.yang:478 (at ietf-isis-ppr@2019-03-10.yang:210)" needs at least one key because it is used as config
ietf-isis-ppr@2019-03-10.yang:478: error: the list at "ietf-isis-ppr@2019-03-10.yang:478 (at ietf-isis-ppr@2019-03-10.yang:87)" needs at least one key because it is used as config
ietf-isis-ppr@2019-03-10.yang:19: error: module 'ietf-isis' not found
ietf-isis-ppr@2019-03-10.yang:446: error: node 'isis' in module 'ietf-isis' not found
ietf-isis-ppr@2019-03-10.yang:468: error: node 'database' in module 'ietf-isis' not found
ietf-isis-ppr@2019-03-10.yang:468: error: node 'level-db' in module 'ietf-isis' not found
ietf-isis-ppr@2019-03-10.yang:468: error: node 'lsp' in module 'ietf-isis' not found
Error: 'ietf-isis-ppr@2019-03-10.yang' import of module 'ietf-isis' failed
ietf-isis-ppr@2019-03-10.yang:19.3: error(236): module not found

Error: object 'isis' not found in module ietf-isis-ppr
ietf-isis-ppr@2019-03-10.yang:446.3: error(251): definition segment not found

Error: object 'isis' not found in module ietf-isis-ppr
ietf-isis-ppr@2019-03-10.yang:468.3: error(251): definition segment not found

***
*** 3 Errors, 0 Warnings
err : Data model "ietf-isis" not found.
err : Importing "ietf-isis" module into "ietf-isis-ppr" failed.
err : Module "ietf-isis-ppr" parsing failed.
ietf-isis-reverse-metric@2019-03-31.yang draft-hopps-lsr-yang-isis-reverse-metric-00.txt Email Authors Download the YANG model FAILED ietf-isis-reverse-metric@2019-03-31.yang:6: error: module "ietf-isis" not found in search path
ietf-isis-reverse-metric@2019-03-31.yang:6: error: module "ietf-isis" not found in search path
ietf-isis-reverse-metric@2019-03-31.yang:6: error: module 'ietf-isis' not found
ietf-isis-reverse-metric@2019-03-31.yang:88: error: node 'isis' in module 'ietf-isis' not found
ietf-isis-reverse-metric@2019-03-31.yang:88: error: node 'interfaces' in module 'ietf-isis' not found
ietf-isis-reverse-metric@2019-03-31.yang:88: error: node 'interface' in module 'ietf-isis' not found
ietf-isis-reverse-metric@2019-03-31.yang:113: error: node 'adjacencies' in module 'ietf-isis' not found
ietf-isis-reverse-metric@2019-03-31.yang:113: error: node 'adjacency' in module 'ietf-isis' not found
Error: 'ietf-isis-reverse-metric@2019-03-31.yang' import of module 'ietf-isis' failed
ietf-isis-reverse-metric@2019-03-31.yang:6.3: error(236): module not found

Error: typedef definition for 'isis:wide-metric' not found in module ietf-isis
ietf-isis-reverse-metric@2019-03-31.yang:49.14: error(250): definition not found

Error: object 'isis' not found in module ietf-isis-reverse-metric
ietf-isis-reverse-metric@2019-03-31.yang:88.3: error(251): definition segment not found

Error: object 'isis' not found in module ietf-isis-reverse-metric
ietf-isis-reverse-metric@2019-03-31.yang:113.3: error(251): definition segment not found

***
*** 4 Errors, 0 Warnings
err : Data model "ietf-isis" not found.
err : Importing "ietf-isis" module into "ietf-isis-reverse-metric" failed.
err : Module "ietf-isis-reverse-metric" parsing failed.
ietf-isis-sr@2019-03-06.yang draft-ietf-isis-sr-yang-05.txt Email Authors Download the YANG model FAILED ietf-isis-sr@2019-03-06.yang:18: error: module "ietf-isis" not found in search path
ietf-isis-sr@2019-03-06.yang:50: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-isis-sr@2019-03-06.yang:234: 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-isis-sr@2019-03-06.yang:561: error: the list at "ietf-isis-sr@2019-03-06.yang:561 (at ietf-isis-sr@2019-03-06.yang:119)" needs at least one key because it is used as config
ietf-isis-sr@2019-03-06.yang:563: error: the list at "ietf-isis-sr@2019-03-06.yang:563 (at ietf-isis-sr@2019-03-06.yang:150)" needs at least one key because it is used as config
ietf-isis-sr@2019-03-06.yang:18: error: module "ietf-isis" not found in search path
ietf-isis-sr@2019-03-06.yang:561: error: the list at "ietf-isis-sr@2019-03-06.yang:561 (at ietf-isis-sr@2019-03-06.yang:119)" needs at least one key because it is used as config
ietf-isis-sr@2019-03-06.yang:563: error: the list at "ietf-isis-sr@2019-03-06.yang:563 (at ietf-isis-sr@2019-03-06.yang:150)" needs at least one key because it is used as config
ietf-isis-sr@2019-03-06.yang:18: error: module 'ietf-isis' not found
ietf-isis-sr@2019-03-06.yang:449: error: node 'isis' in module 'ietf-isis' not found
ietf-isis-sr@2019-03-06.yang:470: error: node 'interfaces' in module 'ietf-isis' not found
ietf-isis-sr@2019-03-06.yang:470: error: node 'interface' in module 'ietf-isis' not found
ietf-isis-sr@2019-03-06.yang:485: error: node 'fast-reroute' in module 'ietf-isis' not found
ietf-isis-sr@2019-03-06.yang:509: error: node 'lfa' in module 'ietf-isis' not found
ietf-isis-sr@2019-03-06.yang:509: error: node 'remote-lfa' in module 'ietf-isis' not found
ietf-isis-sr@2019-03-06.yang:533: error: node 'adjacencies' in module 'ietf-isis' not found
ietf-isis-sr@2019-03-06.yang:533: error: node 'adjacency' in module 'ietf-isis' not found
ietf-isis-sr@2019-03-06.yang:549: error: node 'database' in module 'ietf-isis' not found
ietf-isis-sr@2019-03-06.yang:549: error: node 'level-db' in module 'ietf-isis' not found
ietf-isis-sr@2019-03-06.yang:549: error: node 'lsp' in module 'ietf-isis' not found
ietf-isis-sr@2019-03-06.yang:549: error: node 'router-capabilities' in module 'ietf-isis' not found
ietf-isis-sr@2019-03-06.yang:567: error: node 'extended-is-neighbor' in module 'ietf-isis' not found
ietf-isis-sr@2019-03-06.yang:567: error: node 'neighbor' in module 'ietf-isis' not found
ietf-isis-sr@2019-03-06.yang:581: error: node 'mt-is-neighbor' in module 'ietf-isis' not found
ietf-isis-sr@2019-03-06.yang:581: error: node 'neighbor' in module 'ietf-isis' not found
ietf-isis-sr@2019-03-06.yang:595: error: node 'extended-ipv4-reachability' in module 'ietf-isis' not found
ietf-isis-sr@2019-03-06.yang:595: error: node 'prefixes' in module 'ietf-isis' not found
ietf-isis-sr@2019-03-06.yang:609: error: node 'mt-extended-ipv4-reachability' in module 'ietf-isis' not found
ietf-isis-sr@2019-03-06.yang:609: error: node 'prefixes' in module 'ietf-isis' not found
ietf-isis-sr@2019-03-06.yang:623: error: node 'ipv6-reachability' in module 'ietf-isis' not found
ietf-isis-sr@2019-03-06.yang:623: error: node 'prefixes' in module 'ietf-isis' not found
ietf-isis-sr@2019-03-06.yang:637: error: node 'mt-ipv6-reachability' in module 'ietf-isis' not found
ietf-isis-sr@2019-03-06.yang:637: error: node 'prefixes' in module 'ietf-isis' not found
Error: 'ietf-isis-sr@2019-03-06.yang' import of module 'ietf-isis' failed
ietf-isis-sr@2019-03-06.yang:18.3: error(236): module not found

Error: typedef definition for 'isis:system-id' not found in module ietf-isis
ietf-isis-sr@2019-03-06.yang:345.14: error(250): definition not found

Error: object 'isis' not found in module ietf-isis-sr
ietf-isis-sr@2019-03-06.yang:449.3: error(251): definition segment not found

Error: object 'isis' not found in module ietf-isis-sr
ietf-isis-sr@2019-03-06.yang:470.3: error(251): definition segment not found

Error: object 'isis' not found in module ietf-isis-sr
ietf-isis-sr@2019-03-06.yang:485.3: error(251): definition segment not found

Error: object 'isis' not found in module ietf-isis-sr
ietf-isis-sr@2019-03-06.yang:509.3: error(251): definition segment not found

Error: object 'isis' not found in module ietf-isis-sr
ietf-isis-sr@2019-03-06.yang:533.3: error(251): definition segment not found

Error: object 'isis' not found in module ietf-isis-sr
ietf-isis-sr@2019-03-06.yang:549.3: error(251): definition segment not found

Error: object 'isis' not found in module ietf-isis-sr
ietf-isis-sr@2019-03-06.yang:567.3: error(251): definition segment not found

Error: object 'isis' not found in module ietf-isis-sr
ietf-isis-sr@2019-03-06.yang:581.3: error(251): definition segment not found

Error: object 'isis' not found in module ietf-isis-sr
ietf-isis-sr@2019-03-06.yang:595.3: error(251): definition segment not found

Error: object 'isis' not found in module ietf-isis-sr
ietf-isis-sr@2019-03-06.yang:609.3: error(251): definition segment not found

Error: object 'isis' not found in module ietf-isis-sr
ietf-isis-sr@2019-03-06.yang:623.3: error(251): definition segment not found

Error: object 'isis' not found in module ietf-isis-sr
ietf-isis-sr@2019-03-06.yang:637.3: error(251): definition segment not found

Error: object 'isis' not found in module ietf-isis-sr
ietf-isis-sr@2019-03-06.yang:651.3: error(251): definition segment not found

***
*** 15 Errors, 0 Warnings
err : Data model "ietf-isis" not found.
err : Importing "ietf-isis" module into "ietf-isis-sr" failed.
err : Module "ietf-isis-sr" parsing failed.
ietf-isis-srv6@2019-03-26.yang draft-hu-isis-srv6-yang-01.txt Email Authors Download the YANG model FAILED ietf-isis-srv6@2019-03-26.yang:10: error: module "ietf-isis" not found in search path
ietf-isis-srv6@2019-03-26.yang:18: warning: imported module iana-routing-types not used
ietf-isis-srv6@2019-03-26.yang:44: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-isis-srv6@2019-03-26.yang:262: 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-isis-srv6@2019-03-26.yang:10: error: module "ietf-isis" not found in search path
ietf-isis-srv6@2019-03-26.yang:18: warning: imported module iana-routing-types not used
ietf-isis-srv6@2019-03-26.yang:10: error: module 'ietf-isis' not found
ietf-isis-srv6@2019-03-26.yang:413: error: node 'isis' in module 'ietf-isis' not found
ietf-isis-srv6@2019-03-26.yang:461: error: node 'interfaces' in module 'ietf-isis' not found
ietf-isis-srv6@2019-03-26.yang:461: error: node 'interface' in module 'ietf-isis' not found
ietf-isis-srv6@2019-03-26.yang:461: error: node 'fast-reroute' in module 'ietf-isis' not found
ietf-isis-srv6@2019-03-26.yang:488: error: node 'database' in module 'ietf-isis' not found
ietf-isis-srv6@2019-03-26.yang:488: error: node 'level-db' in module 'ietf-isis' not found
ietf-isis-srv6@2019-03-26.yang:488: error: node 'lsp' in module 'ietf-isis' not found
ietf-isis-srv6@2019-03-26.yang:488: error: node 'router-capabilities' in module 'ietf-isis' not found
ietf-isis-srv6@2019-03-26.yang:503: error: node 'extended-is-neighbor' in module 'ietf-isis' not found
ietf-isis-srv6@2019-03-26.yang:503: error: node 'neighbor' in module 'ietf-isis' not found
ietf-isis-srv6@2019-03-26.yang:525: error: node 'mt-is-neighbor' in module 'ietf-isis' not found
ietf-isis-srv6@2019-03-26.yang:525: error: node 'neighbor' in module 'ietf-isis' not found
ietf-isis-srv6@2019-03-26.yang:570: error: node 'adjacencies' in module 'ietf-isis' not found
ietf-isis-srv6@2019-03-26.yang:570: error: node 'adjacency' in module 'ietf-isis' not found
Error: 'ietf-isis-srv6@2019-03-26.yang' import of module 'ietf-isis' failed
ietf-isis-srv6@2019-03-26.yang:10.3: error(236): module not found

Error: grouping definition for 'isis:prefix-reachability-attributes' not found in module ietf-isis
ietf-isis-srv6@2019-03-26.yang:301.5: error(250): definition not found

Error: grouping definition for 'isis:prefix-ipv4-source-router-id' not found in module ietf-isis
ietf-isis-srv6@2019-03-26.yang:302.5: error(250): definition not found

Error: grouping definition for 'isis:prefix-ipv6-source-router-id' not found in module ietf-isis
ietf-isis-srv6@2019-03-26.yang:303.5: error(250): definition not found

Error: typedef definition for 'isis:system-id' not found in module ietf-isis
ietf-isis-srv6@2019-03-26.yang:361.12: error(250): definition not found

Error: grouping 'prefix-reachability-attributes' not found
ietf-isis-srv6@2019-03-26.yang:301.5: error(250): definition not found

Error: grouping 'prefix-ipv4-source-router-id' not found
ietf-isis-srv6@2019-03-26.yang:302.5: error(250): definition not found

Error: grouping 'prefix-ipv6-source-router-id' not found
ietf-isis-srv6@2019-03-26.yang:303.5: error(250): definition not found

Error: object 'isis' not found in module ietf-isis-srv6
ietf-isis-srv6@2019-03-26.yang:413.3: error(251): definition segment not found

Error: object 'isis' not found in module ietf-isis-srv6
ietf-isis-srv6@2019-03-26.yang:461.3: error(251): definition segment not found

Error: object 'isis' not found in module ietf-isis-srv6
ietf-isis-srv6@2019-03-26.yang:488.3: error(251): definition segment not found

Error: object 'isis' not found in module ietf-isis-srv6
ietf-isis-srv6@2019-03-26.yang:503.3: error(251): definition segment not found

Error: object 'isis' not found in module ietf-isis-srv6
ietf-isis-srv6@2019-03-26.yang:525.3: error(251): definition segment not found

Error: object 'isis' not found in module ietf-isis-srv6
ietf-isis-srv6@2019-03-26.yang:548.3: error(251): definition segment not found

Error: object 'isis' not found in module ietf-isis-srv6
ietf-isis-srv6@2019-03-26.yang:570.3: error(251): definition segment not found

Warning: Module 'iana-routing-types' not used
ietf-isis-srv6@2019-03-26.yang:18.3: warning(1015): import not used

***
*** 15 Errors, 1 Warnings
err : Data model "ietf-isis" not found.
err : Importing "ietf-isis" module into "ietf-isis-srv6" failed.
err : Module "ietf-isis-srv6" parsing failed.
ietf-keystore@2019-06-07.yang draft-ietf-netconf-keystore-10.txt Email Authors Download the YANG model PASSED          
ietf-l1-service-types@2018-09-12.yang draft-ietf-ccamp-l1csm-yang-09.txt Email Authors Download the YANG model PASSED          
ietf-l1csm-te-service-mapping@2019-03-05.yang draft-ietf-teas-te-service-mapping-yang-01.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-l1csm-te-service-mapping@2019-03-05.yang:24: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
  ./ietf-te@2019-04-09.yang:109: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:109) is converted to 'string' when part of a union
./ietf-te@2019-04-09.yang:113: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:113) is converted to 'string' when part of a union
   
ietf-l1csm@2018-09-12.yang draft-ietf-ccamp-l1csm-yang-09.txt Email Authors Download the YANG model PASSED          
ietf-l2sm-te-service-mapping@2019-03-05.yang draft-ietf-teas-te-service-mapping-yang-01.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-l2sm-te-service-mapping@2019-03-05.yang:25: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
  ./ietf-te@2019-04-09.yang:109: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:109) is converted to 'string' when part of a union
./ietf-te@2019-04-09.yang:113: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:113) is converted to 'string' when part of a union
   
ietf-l3-te-topology-state@2019-02-28.yang draft-ietf-teas-yang-l3-te-topo-04.txt Email Authors Download the YANG model PASSED          
ietf-l3-te-topology@2019-02-28.yang draft-ietf-teas-yang-l3-te-topo-04.txt Email Authors Download the YANG model PASSED          
ietf-l3sm-te-service-mapping@2019-03-05.yang draft-ietf-teas-te-service-mapping-yang-01.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-l3sm-te-service-mapping@2019-03-05.yang:24: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
  ./ietf-te@2019-04-09.yang:109: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:109) is converted to 'string' when part of a union
./ietf-te@2019-04-09.yang:113: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:113) is converted to 'string' when part of a union
   
ietf-layer0-types@2019-05-15.yang draft-ietf-ccamp-layer0-types-01.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-layer0-types@2019-05-15.yang:38: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-layer1-types@2019-06-06.yang draft-ietf-ccamp-layer1-types-00.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-layer1-types@2019-06-06.yang:18: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-lisp-address-types@2019-02-23.yang draft-ietf-lisp-yang-11.txt Email Authors Download the YANG model PASSED          
ietf-lisp-etr@2019-02-23.yang draft-ietf-lisp-yang-11.txt Email Authors Download the YANG model PASSED          
ietf-lisp-itr@2019-02-23.yang draft-ietf-lisp-yang-11.txt Email Authors Download the YANG model PASSED          
ietf-lisp-mapresolver@2019-02-23.yang draft-ietf-lisp-yang-11.txt Email Authors Download the YANG model PASSED          
ietf-lisp-mapserver@2019-03-05.yang draft-ietf-lisp-yang-11.txt Email Authors Download the YANG model PASSED          
ietf-lisp@2019-03-05.yang draft-ietf-lisp-yang-11.txt Email Authors Download the YANG model PASSED          
ietf-loopback@2019-03-09.yang draft-vassilev-bmwg-network-interconnect-tester-00.txt Email Authors Download the YANG model FAILED ietf-loopback@2019-03-09.yang:59: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
ietf-loopback@2019-03-09.yang:60: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
       
ietf-lsp-ping@2018-11-29.yang draft-zheng-mpls-lsp-ping-yang-cfg-10.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-lsp-ping@2018-11-29.yang:53: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-microwave-radio-link@2018-11-28.yang draft-ietf-ccamp-mw-yang-13.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-microwave-radio-link@2018-11-28.yang:11: warning: imported module iana-if-type not used
ietf-microwave-radio-link@2018-11-28.yang:11: warning: imported module iana-if-type not used
     
ietf-microwave-topology@2019-02-27.yang draft-ietf-ccamp-mw-topo-yang-01.txt Email Authors Download the YANG model PASSED          
ietf-microwave-types@2018-11-28.yang draft-ietf-ccamp-mw-yang-13.txt Email Authors Download the YANG model PASSED          
ietf-module-tag-ops@2019-03-10.yang draft-bierman-netconf-module-tag-ops-00.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-module-tag-ops@2019-03-10.yang:41: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
    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
 
ietf-module-tags@2019-05-03.yang draft-ietf-netmod-module-tags-08.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-module-tags@2019-05-03.yang:50: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-module-tags@2019-05-03.yang:50: 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-mpls-ldp-extended@2018-10-22.yang draft-ietf-mpls-ldp-yang-06.txt Email Authors Download the YANG model PASSED          
ietf-mpls-ldp@2018-10-22.yang draft-ietf-mpls-ldp-yang-06.txt Email Authors Download the YANG model PASSED          
ietf-mpls-mldp-extended@2018-10-22.yang draft-ietf-mpls-mldp-yang-06.txt Email Authors Download the YANG model FAILED       Error: object 'ipv6' not found in module ietf-mpls-mldp-extended
ietf-mpls-mldp-extended@2018-10-22.yang:421.3: error(251): definition segment not found

Error: object 'ipv6' not found in module ietf-mpls-mldp-extended
ietf-mpls-mldp-extended@2018-10-22.yang:584.3: error(251): definition segment not found

Error: object 'ipv6' not found in module ietf-mpls-mldp-extended
ietf-mpls-mldp-extended@2018-10-22.yang:688.3: error(251): definition segment not found

***
*** 3 Errors, 0 Warnings
 
ietf-mpls-mldp@2018-10-22.yang draft-ietf-mpls-mldp-yang-06.txt Email Authors Download the YANG model PASSED          
ietf-mpls-static-extended@2019-03-08.yang draft-ietf-mpls-static-yang-09.txt Email Authors Download the YANG model PASSED WITH WARNINGS         warn: Identityref "block-allocation-mode" comparison with identity "label-block-alloc-mode-manager" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[6] "block-allocation-mode = 'label-block-alloc-mode-manager'".
warn: Identityref "block-allocation-mode" comparison with identity "label-block-alloc-mode-manager" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[6] "block-allocation-mode = 'label-block-alloc-mode-manager'".
ietf-mpls-static@2019-03-08.yang draft-ietf-mpls-static-yang-09.txt Email Authors Download the YANG model PASSED WITH WARNINGS         warn: Identityref "block-allocation-mode" comparison with identity "label-block-alloc-mode-manager" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[6] "block-allocation-mode = 'label-block-alloc-mode-manager'".
warn: Identityref "block-allocation-mode" comparison with identity "label-block-alloc-mode-manager" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[6] "block-allocation-mode = 'label-block-alloc-mode-manager'".
ietf-mpls-tp-topology@2019-03-11.yang draft-busizheng-teas-mpls-tp-yang-00.txt Email Authors Download the YANG model FAILED ietf-mpls-tp-topology@2019-03-11.yang:36: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-mpls-tp-topology@2019-03-11.yang:59: error: bad value "/nw:networks/nw:network/nt:link/tet:te/tet:te-link-attributes/tet:interface-switching-capability/tet:max-lsp-
bandwidth/tet:te-bandwidth/tet:technology" (should be schema-nodeid)
ietf-mpls-tp-topology@2019-03-11.yang:75: warning: node ietf-network::network-types is not found in ietf-network::networks
ietf-mpls-tp-topology@2019-03-11.yang:88: warning: node ietf-network::network-types is not found in ietf-network::networks
ietf-mpls-tp-topology@2019-03-11.yang:101: warning: node ietf-network::network-types is not found in ietf-network::networks
ietf-mpls-tp-topology@2019-03-11.yang:114: warning: node ietf-network::network-types is not found in ietf-network::networks
ietf-mpls-tp-topology@2019-03-11.yang:59: error: bad value "/nw:networks/nw:network/nt:link/tet:te/tet:te-link-attributes/tet:interface-switching-capability/tet:max-lsp-
bandwidth/tet:te-bandwidth/tet:technology" (should be schema-nodeid)
ietf-mpls-tp-topology@2019-03-11.yang:75: warning: node ietf-network::network-types is not found in ietf-network::networks
ietf-mpls-tp-topology@2019-03-11.yang:88: warning: node ietf-network::network-types is not found in ietf-network::networks
ietf-mpls-tp-topology@2019-03-11.yang:101: warning: node ietf-network::network-types is not found in ietf-network::networks
ietf-mpls-tp-topology@2019-03-11.yang:114: warning: node ietf-network::network-types is not found in ietf-network::networks
ietf-mpls-tp-topology@2019-03-11.yang:55: error: bad argument value "/nw:networks/nw:network/nt:link/tet:te/tet:te-link-attributes/tet:interface-switching-capability/tet:max-lsp-
bandwidth/tet:te-bandwidth/tet:technology", should be of type schema-nodeid
Error: invalid name string (tet:max-lsp-
bandwidth/tet:te-bandwidth/tet:technology)
ietf-mpls-tp-topology@2019-03-11.yang:55.3: error(228): invalid name

Warning: no child node 'ietf-network:network-types' found for parent 'ietf-network:networks'
XPath: ../../../../../../../nw:network-types/tet:te-topology/mpls-tp-topo:mpls-tp-topology
ietf-mpls-tp-topology@2019-03-11.yang:74.31: warning(1032): no child node available

Warning: no child node 'ietf-network:network-types' found for parent 'ietf-network:networks'
XPath: ../../../../../../nw:network-types/tet:te-topology/mpls-tp-topo:mpls-tp-topology
ietf-mpls-tp-topology@2019-03-11.yang:87.28: warning(1032): no child node available

Warning: no child node 'ietf-network:network-types' found for parent 'ietf-network:networks'
XPath: ../../../../../../nw:network-types/tet:te-topology/mpls-tp-topo:mpls-tp-topology
ietf-mpls-tp-topology@2019-03-11.yang:100.28: warning(1032): no child node available

Warning: no child node 'ietf-network:network-types' found for parent 'ietf-network:networks'
XPath: ../../../../../../nw:network-types/tet:te-topology/mpls-tp-topo:mpls-tp-topology
ietf-mpls-tp-topology@2019-03-11.yang:113.28: warning(1032): no child node available

***
*** 1 Errors, 4 Warnings
err : Unexpected character(s) 'b' (bandwidth/tet:t).
err : Module "ietf-mpls-tp-topology" parsing failed.
ietf-mpls-tp-tunnel@2019-03-11.yang draft-busizheng-teas-mpls-tp-yang-00.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-mpls-tp-tunnel@2019-03-11.yang:26: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
  ./ietf-te@2019-04-09.yang:109: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:109) is converted to 'string' when part of a union
./ietf-te@2019-04-09.yang:113: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:113) is converted to 'string' when part of a union
   
ietf-mpls-tp-types@2019-03-11.yang draft-busizheng-teas-mpls-tp-yang-00.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-mpls-tp-types@2019-03-11.yang:25: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-mpls@2019-02-24.yang draft-ietf-mpls-base-yang-10.txt Email Authors Download the YANG model PASSED WITH WARNINGS         warn: Identityref "block-allocation-mode" comparison with identity "label-block-alloc-mode-manager" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[6] "block-allocation-mode = 'label-block-alloc-mode-manager'".
warn: Identityref "block-allocation-mode" comparison with identity "label-block-alloc-mode-manager" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[6] "block-allocation-mode = 'label-block-alloc-mode-manager'".
ietf-msdp@2018-10-20.yang draft-ietf-pim-msdp-yang-06.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-msdp@2018-10-20.yang:341: 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-mud-brski-masa@2018-02-14.yang draft-ietf-anima-bootstrapping-keyinfra-20.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-mud-brski-masa@2018-02-14.yang:21: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-multicast-model@2018-07-30.yang draft-ietf-mboned-multicast-yang-model-01.txt Email Authors Download the YANG model FAILED ietf-multicast-model@2018-07-30.yang:54: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-multicast-model@2018-07-30.yang:206: error: type "sub-domain-id" not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:212: error: type "bfr-id" not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:224: error: type "bfr-id" not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:260: error: type "sub-domain-id" not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:280: error: type "bsl" not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:285: error: type "si" not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:308: error: type "sub-domain-id" not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:327: error: type "bsl" not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:332: error: type "si" not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:206: error: type "sub-domain-id" not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:212: error: type "bfr-id" not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:224: error: type "bfr-id" not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:260: error: type "sub-domain-id" not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:280: error: type "bsl" not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:285: error: type "si" not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:308: error: type "sub-domain-id" not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:327: error: type "bsl" not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:332: error: type "si" not found in module ietf-bier
/home/bclaise/yang/modules/YANG/ietf-bier@2019-05-14.yang:14: error: module "ietf-isis" not found in search path
./ietf-bier@2019-05-14.yang:14: error: module 'ietf-isis' not found
./ietf-bier@2019-05-14.yang:381: error: node 'isis' in module 'ietf-isis' not found
ietf-multicast-model@2018-07-30.yang:206: error: typedef 'sub-domain-id' in module 'ietf-bier' not found
ietf-multicast-model@2018-07-30.yang:212: error: typedef 'bfr-id' in module 'ietf-bier' not found
ietf-multicast-model@2018-07-30.yang:224: error: typedef 'bfr-id' in module 'ietf-bier' not found
ietf-multicast-model@2018-07-30.yang:260: error: typedef 'sub-domain-id' in module 'ietf-bier' not found
ietf-multicast-model@2018-07-30.yang:280: error: typedef 'bsl' in module 'ietf-bier' not found
ietf-multicast-model@2018-07-30.yang:285: error: typedef 'si' in module 'ietf-bier' not found
ietf-multicast-model@2018-07-30.yang:308: error: typedef 'sub-domain-id' in module 'ietf-bier' not found
ietf-multicast-model@2018-07-30.yang:327: error: typedef 'bsl' in module 'ietf-bier' not found
ietf-multicast-model@2018-07-30.yang:332: error: typedef 'si' in module 'ietf-bier' not found
Error: 'ietf-bier@2019-05-14.yang' import of module 'ietf-isis' failed
ietf-bier@2019-05-14.yang:14.5: error(236): module not found

Error: object 'isis' not found in module ietf-bier
ietf-bier@2019-05-14.yang:381.6: error(251): definition segment not found

Error: 'ietf-multicast-model@2018-07-30.yang' import of module 'ietf-bier' failed
ietf-multicast-model@2018-07-30.yang:18.2: error(250): definition not found

Error: typedef definition for 'bier:sub-domain-id' not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:206.22: error(250): definition not found

Error: typedef definition for 'bier:bfr-id' not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:212.22: error(250): definition not found

Error: typedef definition for 'bier:bfr-id' not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:224.26: error(250): definition not found

Error: typedef definition for 'bier:sub-domain-id' not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:260.22: error(250): definition not found

Error: typedef definition for 'bier:bsl' not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:280.22: error(250): definition not found

Error: typedef definition for 'bier:si' not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:285.22: error(250): definition not found

Error: typedef definition for 'bier:sub-domain-id' not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:308.22: error(250): definition not found

Error: typedef definition for 'bier:bsl' not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:327.22: error(250): definition not found

Error: typedef definition for 'bier:si' not found in module ietf-bier
ietf-multicast-model@2018-07-30.yang:332.22: error(250): definition not found

Error: object 'egress-node' not found in module ietf-multicast-model in Xpath target egress-node
ietf-multicast-model@2018-07-30.yang:218.17: error(250): definition not found

Error: invalid identifier in key for list 'egress-nodes' (egress-node)
ietf-multicast-model@2018-07-30.yang:218.17: error(250): definition not found

Error: object 'egress-node' not found in module ietf-multicast-model in Xpath target egress-node
ietf-multicast-model@2018-07-30.yang:217.13: error(250): definition not found

Error: invalid identifier in key for list 'egress-nodes' (egress-node)
ietf-multicast-model@2018-07-30.yang:217.13: error(250): definition not found

***
*** 14 Errors, 0 Warnings
err : Data model "ietf-isis" not found.
err : Importing "ietf-isis" module into "ietf-bier" failed.
err : Module "ietf-bier" parsing failed.
err : Importing "ietf-bier" module into "ietf-multicast-model" failed.
err : Module "ietf-multicast-model" parsing failed.
ietf-multiple-stream-originators@2019-03-11.yang draft-zhou-netconf-multi-stream-originators-04.txt Email Authors Download the YANG model FAILED         err : The leafref leaf is config but refers to a non-config leaf. (/ietf-subscribed-notifications:subscriptions/subscription/target/stream/stream)
err : Invalid value "subscription-policy" of "uses". (/ietf-subscribed-notifications:subscriptions/subscription/subscription-policy)
err : Copying data from grouping failed. (/ietf-subscribed-notifications:subscriptions/subscription/subscription-policy)
err : Module "ietf-subscribed-notifications" parsing failed.
err : Importing "ietf-subscribed-notifications" module into "ietf-multiple-stream-originators" failed.
err : Module "ietf-multiple-stream-originators" parsing failed.
ietf-mvpn@2019-03-05.yang draft-ietf-bess-mvpn-yang-01.txt Email Authors Download the YANG model FAILED ietf-mvpn@2019-03-05.yang:10: error: module "ietf-bgp-l3vpn" not found in search path
ietf-mvpn@2019-03-05.yang:47: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-mvpn@2019-03-05.yang:10: error: module "ietf-bgp-l3vpn" not found in search path
ietf-mvpn@2019-03-05.yang:10: error: module 'ietf-bgp-l3vpn' not found
ietf-mvpn@2019-03-05.yang:944: error: node 'l3vpn' in module 'ietf-bgp-l3vpn' not found
ietf-mvpn@2019-03-05.yang:944: error: node 'l3vpn' in module 'ietf-bgp-l3vpn' not found
ietf-mvpn@2019-03-05.yang:944: error: node 'ipv4' in module 'ietf-bgp-l3vpn' not found
ietf-mvpn@2019-03-05.yang:960: error: node 'ipv6' in module 'ietf-bgp-l3vpn' not found
Error: 'ietf-mvpn@2019-03-05.yang' import of module 'ietf-bgp-l3vpn' failed
ietf-mvpn@2019-03-05.yang:10.4: error(236): module not found

Error: object 'l3vpn' not found in module ietf-mvpn
ietf-mvpn@2019-03-05.yang:944.4: error(251): definition segment not found

Error: object 'l3vpn' not found in module ietf-mvpn
ietf-mvpn@2019-03-05.yang:960.4: error(251): definition segment not found

***
*** 3 Errors, 0 Warnings
err : Data model "ietf-bgp-l3vpn" not found.
err : Importing "ietf-bgp-l3vpn" module into "ietf-mvpn" failed.
err : Module "ietf-mvpn" parsing failed.
ietf-netconf-client@2019-06-07.yang draft-ietf-netconf-netconf-client-server-13.txt Email Authors Download the YANG model PASSED          
ietf-netconf-server@2019-06-07.yang draft-ietf-netconf-netconf-client-server-13.txt Email Authors Download the YANG model PASSED          
ietf-network-bridge-flows@2018-07-15.yang draft-vassilev-netmod-network-bridge-01.txt Email Authors Download the YANG model FAILED ietf-network-bridge-flows@2018-07-15.yang:28: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-network-bridge-flows@2018-07-15.yang:36: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:40: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:41: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:43: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:48: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:55: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:56: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:61: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:62: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:69: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:70: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:72: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:73: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:76: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:82: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:83: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:89: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:94: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:99: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:100: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:103: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:106: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:109: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:112: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:118: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:119: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:125: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:126: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:132: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:133: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:139: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:150: error: keyword "description" not in canonical order,expected "type" (see RFC 6020, Section 12)
ietf-network-bridge-flows@2018-07-15.yang:151: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
ietf-network-bridge-flows@2018-07-15.yang:156: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:162: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:166: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:167: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:168: error: keyword "mandatory" not in canonical order,expected "type" (see RFC 6020, Section 12)
ietf-network-bridge-flows@2018-07-15.yang:169: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
ietf-network-bridge-flows@2018-07-15.yang:171: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:176: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:180: error: keyword "presence" not in canonical order (see RFC 6020, Section 12)
ietf-network-bridge-flows@2018-07-15.yang:186: error: keyword "presence" not in canonical order (see RFC 6020, Section 12)
ietf-network-bridge-flows@2018-07-15.yang:192: error: keyword "presence" not in canonical order (see RFC 6020, Section 12)
ietf-network-bridge-flows@2018-07-15.yang:193: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:194: error: keyword "mandatory" not in canonical order,expected "type" (see RFC 6020, Section 12)
ietf-network-bridge-flows@2018-07-15.yang:195: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
ietf-network-bridge-flows@2018-07-15.yang:200: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:204: error: keyword "presence" not in canonical order (see RFC 6020, Section 12)
ietf-network-bridge-flows@2018-07-15.yang:205: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:208: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:214: error: keyword "description" not in canonical order,expected "type" (see RFC 6020, Section 12)
ietf-network-bridge-flows@2018-07-15.yang:215: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
ietf-network-bridge-flows@2018-07-15.yang:219: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:220: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:223: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:226: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:234: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:237: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:242: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:243: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:254: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:257: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:289: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:297: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:304: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:306: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:311: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:312: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:315: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:318: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:321: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:324: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:329: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:333: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:334: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
ietf-network-bridge-flows@2018-07-15.yang:336: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
       
ietf-network-bridge-scheduler-state@2019-01-07.yang draft-vassilev-netmod-network-bridge-01.txt Email Authors Download the YANG model FAILED ietf-network-bridge-scheduler-state@2019-01-07.yang:49: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
ietf-network-bridge-scheduler-state@2019-01-07.yang:50: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-scheduler-state@2019-01-07.yang:51: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-scheduler-state@2019-01-07.yang:52: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
ietf-network-bridge-scheduler-state@2019-01-07.yang:54: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler-state@2019-01-07.yang:57: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler-state@2019-01-07.yang:63: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-scheduler-state@2019-01-07.yang:64: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
ietf-network-bridge-scheduler-state@2019-01-07.yang:66: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler-state@2019-01-07.yang:71: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler-state@2019-01-07.yang:77: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-scheduler-state@2019-01-07.yang:78: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
ietf-network-bridge-scheduler-state@2019-01-07.yang:80: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
    Error: Key predicates found for list 'gate-controller' which does not define any keys
Error: 'ietf-network-bridge-scheduler-state@2019-01-07.yang' import of module 'ietf-network-bridge-scheduler' failed
ietf-network-bridge-scheduler-state@2019-01-07.yang:10.3: error(258): invalid value

Error: grouping definition for 'sched:gate-controller-queue-state' not found in module ietf-network-bridge-scheduler
ietf-network-bridge-scheduler-state@2019-01-07.yang:74.15: error(250): definition not found

Error: grouping definition for 'sched:gate-controller-queue-state' not found in module ietf-network-bridge-scheduler
ietf-network-bridge-scheduler-state@2019-01-07.yang:85.15: error(250): definition not found

Error: grouping 'gate-controller-queue-state' not found
ietf-network-bridge-scheduler-state@2019-01-07.yang:74.15: error(250): definition not found

Error: grouping 'gate-controller-queue-state' not found
ietf-network-bridge-scheduler-state@2019-01-07.yang:85.15: error(250): definition not found

***
*** 5 Errors, 0 Warnings
 
ietf-network-bridge-scheduler@2019-01-07.yang draft-vassilev-netmod-network-bridge-01.txt Email Authors Download the YANG model FAILED ietf-network-bridge-scheduler@2019-01-07.yang:128: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:138: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:139: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:142: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:146: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:159: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:160: error: RFC 8407: 4.14: statement "leaf-list" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:166: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:167: error: RFC 8407: 4.14: statement "leaf-list" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:175: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:180: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
ietf-network-bridge-scheduler@2019-01-07.yang:192: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
ietf-network-bridge-scheduler@2019-01-07.yang:194: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:200: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:201: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:202: error: keyword "config" not in canonical order,expected "type" (see RFC 6020, Section 12)
ietf-network-bridge-scheduler@2019-01-07.yang:203: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
ietf-network-bridge-scheduler@2019-01-07.yang:205: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:206: error: keyword "config" not in canonical order,expected "type" (see RFC 6020, Section 12)
ietf-network-bridge-scheduler@2019-01-07.yang:207: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
ietf-network-bridge-scheduler@2019-01-07.yang:210: error: keyword "config" not in canonical order,expected "type" (see RFC 6020, Section 12)
ietf-network-bridge-scheduler@2019-01-07.yang:211: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
ietf-network-bridge-scheduler@2019-01-07.yang:226: error: keyword "config" not in canonical order,expected "type" (see RFC 6020, Section 12)
ietf-network-bridge-scheduler@2019-01-07.yang:227: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
ietf-network-bridge-scheduler@2019-01-07.yang:232: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:233: error: keyword "config" not in canonical order,expected "type" (see RFC 6020, Section 12)
ietf-network-bridge-scheduler@2019-01-07.yang:234: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
ietf-network-bridge-scheduler@2019-01-07.yang:238: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:239: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:240: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:241: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:243: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:246: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:252: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:253: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:255: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:260: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:266: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:267: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:269: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:281: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:282: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:283: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:285: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:288: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:289: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:291: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:294: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:297: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:302: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:309: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:315: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:316: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:318: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:321: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:327: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:328: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:330: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:336: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:342: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:343: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge-scheduler@2019-01-07.yang:348: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
    Error: Key predicates found for list 'gate-controller' which does not define any keys  
ietf-network-bridge@2018-07-15.yang draft-vassilev-netmod-network-bridge-01.txt Email Authors Download the YANG model FAILED ietf-network-bridge@2018-07-15.yang:40: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge@2018-07-15.yang:41: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-network-bridge@2018-07-15.yang:42: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
ietf-network-bridge@2018-07-15.yang:45: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge@2018-07-15.yang:48: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-network-bridge@2018-07-15.yang:54: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
ietf-network-bridge@2018-07-15.yang:55: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
       
ietf-network-vpn-svc-pm@2019-03-01.yang draft-www-bess-yang-vpn-service-pm-02.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-network-vpn-svc-pm@2019-03-01.yang:21: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-nmda-compare@2019-05-23.yang draft-ietf-netmod-nmda-diff-01.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-nmda-compare@2019-05-23.yang:40: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-nmda-notifications@2018-12-26.yang draft-wu-netmod-base-notification-nmda-02.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-nmda-notifications@2018-12-26.yang:43: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-nmda-notifications@2018-12-26.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).
       
ietf-notification-capabilities@2019-02-28.yang draft-ietf-netconf-notification-capabilities-01.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-notification-capabilities@2019-02-28.yang:58: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-notification-capabilities@2019-02-28.yang:58: 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-notification-messages@2018-01-31.yang draft-ietf-netconf-notification-messages-05.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-notification-messages@2018-01-31.yang:32: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-ntp@2018-12-17.yang draft-ietf-ntp-yang-data-model-05.txt Email Authors Download the YANG model PASSED          
ietf-nvo3-base@2019-03-01.yang draft-zhang-nvo3-yang-cfg-05.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-nvo3-base@2019-03-01.yang:15: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-nvo3@2019-03-20.yang draft-chen-nvo3-yang-02.txt Email Authors Download the YANG model FAILED ietf-nvo3@2019-03-20.yang:34: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-nvo3@2019-03-20.yang:72: error: ietf-nvo3:evpn in the path for evpn-instance at ietf-nvo3@2019-03-20.yang:240 is not found
ietf-nvo3@2019-03-20.yang:72: error: ietf-nvo3:evpn in the path for evpn-instance at ietf-nvo3@2019-03-20.yang:362 is not found
ietf-nvo3@2019-03-20.yang:72: error: ietf-nvo3:evpn in the path for evpn-instance-ref at ietf-nvo3@2019-03-20.yang:70 is not found
ietf-nvo3@2019-03-20.yang:72: error: ietf-nvo3:evpn in the path for evpn-instance at ietf-nvo3@2019-03-20.yang:240 is not found
ietf-nvo3@2019-03-20.yang:72: error: ietf-nvo3:evpn in the path for evpn-instance at ietf-nvo3@2019-03-20.yang:362 is not found
ietf-nvo3@2019-03-20.yang:72: error: ietf-nvo3:evpn in the path for evpn-instance-ref at ietf-nvo3@2019-03-20.yang:70 is not found
ietf-nvo3@2019-03-20.yang:72: error: the node 'evpn' from module 'ietf-nvo3' is not found
Error: object not found 'evpn'
ietf-nvo3@2019-03-20.yang:72.16: error(250): definition not found

Error: object not found 'evpn'
ietf-nvo3@2019-03-20.yang:72.16: error(250): definition not found

Error: object not found 'evpn'
ietf-nvo3@2019-03-20.yang:72.16: error(250): definition not found

***
*** 3 Errors, 0 Warnings
err : No resolvents found for leafref "/evpn/evpn-instances/evpn-instance/name". (/ietf-nvo3:nvo3/nvo3-instance/control-plane/evpn/evpn-instance)
err : No resolvents found for leafref "/evpn/evpn-instances/evpn-instance/name". (/ietf-nvo3:nvo3-state/nvo3-instance/control-plane/evpn/evpn-instance)
err : Module "ietf-nvo3" parsing failed.
ietf-opt-parameters-wdm@2018-10-22.yang draft-galimbe-ccamp-iv-yang-08.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-opt-parameters-wdm@2018-10-22.yang:37: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-optical-impairment-topology@2019-05-22.yang draft-ietf-ccamp-optical-impairment-topology-yang-01.txt Email Authors Download the YANG model FAILED ietf-optical-impairment-topology@2019-05-22.yang:54: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-optical-impairment-topology@2019-05-22.yang:771: error: bad value "/nw:networks/nw:network/nw:node/tet:te/tet:tunnel-termination-point/OTSiG-element[OTSiG-
identifier=current()/../OTSiG-ref]/OTSiG-container/OTSi/OTSi-carrier-id" (should be path-arg)
ietf-optical-impairment-topology@2019-05-22.yang:771: error: bad value "/nw:networks/nw:network/nw:node/tet:te/tet:tunnel-termination-point/OTSiG-element[OTSiG-
identifier=current()/../OTSiG-ref]/OTSiG-container/OTSi/OTSi-carrier-id" (should be path-arg)
ietf-optical-impairment-topology@2019-05-22.yang:768: error: bad argument value "/nw:networks/nw:network/nw:node/tet:te/tet:tunnel-termination-point/OTSiG-element[OTSiG-
identifier=current()/../OTSiG-ref]/OTSiG-container/OTSi/OTSi-carrier-id", should be of type path-arg
  err : Unexpected character(s) 'i' (identifier=curr).
err : Perhaps "OTSiG-" is supposed to be a function call.
err : Module "ietf-optical-impairment-topology" parsing failed.
ietf-ose-path-svc.yang draft-wood-rtgwg-sdwan-ose-yang-00.txt Email Authors Download the YANG model FAILED ietf-ose-path-svc.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
ietf-ose-path-svc.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement
ietf-ose-path-svc.yang:1: error: RFC 8407: 4.8: statement "module" must have a "description" substatement
ietf-ose-path-svc.yang:1: error: RFC 8407: 4.8: statement "module" must have a "revision" substatement
ietf-ose-path-svc.yang:103: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-ose-path-svc.yang:104: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
ietf-ose-path-svc.yang:106: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-ose-path-svc.yang:109: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-ose-path-svc.yang:112: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
ietf-ose-path-svc.yang:114: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-ose-path-svc.yang:232: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
ietf-ose-path-svc.yang:234: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-ose-path-svc.yang:237: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-ose-path-svc.yang:240: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-ose-path-svc.yang:244: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-ose-path-svc.yang:245: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-ose-path-svc.yang:248: error: RFC 8407: 4.14: statement "leaf-list" must have a "description" substatement
ietf-ose-path-svc.yang:251: error: RFC 8407: 4.14: statement "leaf-list" must have a "description" substatement
ietf-ose-path-svc.yang:255: error: RFC 8407: 4.14: statement "leaf-list" must have a "description" substatement
ietf-ose-path-svc.yang:258: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-ose-path-svc.yang:260: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-path-svc.yang:261: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-path-svc.yang:262: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-path-svc.yang:263: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-path-svc.yang:264: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-path-svc.yang:265: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-path-svc.yang:266: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-path-svc.yang:269: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-ose-path-svc.yang:270: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-ose-path-svc.yang:272: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-path-svc.yang:273: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-path-svc.yang:274: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-path-svc.yang:277: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-ose-path-svc.yang:280: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-ose-path-svc.yang:282: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-path-svc.yang:283: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-path-svc.yang:284: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-path-svc.yang:287: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-ose-path-svc.yang:291: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-ose-path-svc.yang:293: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-path-svc.yang:294: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-path-svc.yang:295: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-path-svc.yang:300: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-ose-path-svc.yang:317: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-ose-path-svc.yang:319: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
    Warning: no revision statements for module 'ietf-ose-path-svc'
***
*** 0 Errors, 1 Warnings
 
ietf-ose-reachability-svc.yang draft-wood-rtgwg-sdwan-ose-yang-00.txt Email Authors Download the YANG model FAILED ietf-ose-reachability-svc.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
ietf-ose-reachability-svc.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement
ietf-ose-reachability-svc.yang:1: error: RFC 8407: 4.8: statement "module" must have a "description" substatement
ietf-ose-reachability-svc.yang:1: error: RFC 8407: 4.8: statement "module" must have a "revision" substatement
ietf-ose-reachability-svc.yang:5: warning: imported module ietf-inet-types not used
ietf-ose-reachability-svc.yang:8: warning: imported module ietf-yang-types not used
ietf-ose-reachability-svc.yang:41: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-reachability-svc.yang:42: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-reachability-svc.yang:49: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-reachability-svc.yang:50: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-reachability-svc.yang:51: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-reachability-svc.yang:58: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-reachability-svc.yang:59: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-reachability-svc.yang:66: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-reachability-svc.yang:67: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-reachability-svc.yang:68: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-reachability-svc.yang:73: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
ietf-ose-reachability-svc.yang:97: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-reachability-svc.yang:98: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-reachability-svc.yang:105: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-reachability-svc.yang:106: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-reachability-svc.yang:107: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-reachability-svc.yang:114: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-reachability-svc.yang:115: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-reachability-svc.yang:121: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
ietf-ose-reachability-svc.yang:140: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-reachability-svc.yang:141: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ose-reachability-svc.yang:146: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-ose-reachability-svc.yang:5: warning: imported module ietf-inet-types not used
ietf-ose-reachability-svc.yang:8: warning: imported module ietf-yang-types not used
  Warning: no revision statements for module 'ietf-ose-reachability-svc'
Warning: Module 'ietf-inet-types' not used
ietf-ose-reachability-svc.yang:5.3: warning(1015): import not used

Warning: Module 'ietf-yang-types' not used
ietf-ose-reachability-svc.yang:8.3: warning(1015): import not used

***
*** 0 Errors, 3 Warnings
 
ietf-ospf-ppr@2018-06-20.yang draft-qct-lsr-ppr-yang-01.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-ospf-ppr@2018-06-20.yang:11: warning: imported module ietf-yang-types not used
ietf-ospf-ppr@2018-06-20.yang:14: warning: imported module ietf-routing-types not used
ietf-ospf-ppr@2018-06-20.yang:30: warning: imported module ietf-segment-routing-common not used
ietf-ospf-ppr@2018-06-20.yang:132: 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-ospf-ppr@2018-06-20.yang:11: warning: imported module ietf-yang-types not used
ietf-ospf-ppr@2018-06-20.yang:14: warning: imported module ietf-routing-types not used
ietf-ospf-ppr@2018-06-20.yang:30: warning: imported module ietf-segment-routing-common not used
  Warning: Module 'ietf-yang-types' not used
ietf-ospf-ppr@2018-06-20.yang:11.3: warning(1015): import not used

Warning: Module 'ietf-routing-types' not used
ietf-ospf-ppr@2018-06-20.yang:14.3: warning(1015): import not used

Warning: Module 'ietf-segment-routing-common' not used
ietf-ospf-ppr@2018-06-20.yang:30.3: warning(1015): import not used

***
*** 0 Errors, 3 Warnings
 
ietf-ospf-sr@2019-03-05.yang draft-ietf-ospf-sr-yang-07.txt Email Authors Download the YANG model PASSED          
ietf-ospf@2019-01-24.yang draft-ietf-ospf-yang-21.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-ospf@2019-01-24.yang:2467: 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-ospfv3-extended-lsa@2018-10-22.yang draft-acee-lsr-ospfv3-extended-lsa-yang-03.txt Email Authors Download the YANG model PASSED          
ietf-otn-topology@2019-02-25.yang draft-ietf-ccamp-otn-topo-yang-06.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-otn-topology@2019-02-25.yang:74: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-otn-tunnel@2018-08-23.yang draft-ietf-ccamp-otn-tunnel-model-06.txt Email Authors Download the YANG model FAILED ietf-otn-tunnel@2018-08-23.yang:76: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-otn-tunnel@2018-08-23.yang:159: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:185: error: node ietf-te::explicit-route-objects is not found
ietf-otn-tunnel@2018-08-23.yang:196: error: node ietf-te::explicit-route-objects is not found
ietf-otn-tunnel@2018-08-23.yang:207: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:217: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:229: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:240: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:250: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:262: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:274: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:283: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:295: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:306: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:316: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:329: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:366: error: node ietf-te::explicit-route-objects is not found
ietf-otn-tunnel@2018-08-23.yang:379: error: node ietf-te::explicit-route-objects is not found
ietf-otn-tunnel@2018-08-23.yang:390: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:400: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:412: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:423: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:433: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:445: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:456: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:466: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:479: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:490: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:500: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:512: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:526: error: node ietf-te::state is not found
ietf-otn-tunnel@2018-08-23.yang:538: error: node ietf-te::state is not found
ietf-otn-tunnel@2018-08-23.yang:551: error: node ietf-te::state is not found
ietf-otn-tunnel@2018-08-23.yang:566: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:580: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:594: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:608: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:620: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:631: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:644: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:656: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:668: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:681: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:693: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:704: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:718: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:730: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:741: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:754: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:768: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:781: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:795: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:833: error: node ietf-te::explicit-route-objects is not found
ietf-otn-tunnel@2018-08-23.yang:845: error: node ietf-te::explicit-route-objects is not found
ietf-otn-tunnel@2018-08-23.yang:856: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:867: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:879: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:890: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:900: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:912: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:923: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:933: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:945: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:957: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:967: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:979: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:991: error: node ietf-te::state is not found
ietf-otn-tunnel@2018-08-23.yang:1003: error: node ietf-te::state is not found
ietf-otn-tunnel@2018-08-23.yang:1017: error: node ietf-te::state is not found
ietf-otn-tunnel@2018-08-23.yang:1028: error: node ietf-te::lsp-record-route-subobjects is not found
ietf-otn-tunnel@2018-08-23.yang:1201 (at ietf-otn-tunnel@2018-08-23.yang:1058): error: the key "index" does not reference an existing leaf
ietf-otn-tunnel@2018-08-23.yang:1093: error: identity "tunnel-type" not found in module ietf-te-types
ietf-otn-tunnel@2018-08-23.yang:159: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:185: error: node ietf-te::explicit-route-objects is not found
ietf-otn-tunnel@2018-08-23.yang:196: error: node ietf-te::explicit-route-objects is not found
ietf-otn-tunnel@2018-08-23.yang:207: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:217: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:229: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:240: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:250: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:262: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:274: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:283: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:295: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:306: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:316: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:329: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:366: error: node ietf-te::explicit-route-objects is not found
ietf-otn-tunnel@2018-08-23.yang:379: error: node ietf-te::explicit-route-objects is not found
ietf-otn-tunnel@2018-08-23.yang:390: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:400: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:412: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:423: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:433: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:445: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:456: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:466: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:479: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:490: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:500: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:512: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:526: error: node ietf-te::state is not found
ietf-otn-tunnel@2018-08-23.yang:538: error: node ietf-te::state is not found
ietf-otn-tunnel@2018-08-23.yang:551: error: node ietf-te::state is not found
ietf-otn-tunnel@2018-08-23.yang:566: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:580: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:594: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:608: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:620: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:631: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:644: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:656: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:668: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:681: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:693: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:704: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:718: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:730: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:741: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:754: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:768: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:781: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:795: error: node ietf-te::p2p-reverse-primary-path is not found
ietf-otn-tunnel@2018-08-23.yang:833: error: node ietf-te::explicit-route-objects is not found
ietf-otn-tunnel@2018-08-23.yang:845: error: node ietf-te::explicit-route-objects is not found
ietf-otn-tunnel@2018-08-23.yang:856: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:867: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:879: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:890: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:900: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:912: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:923: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:933: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:945: error: node ietf-te::forward is not found
ietf-otn-tunnel@2018-08-23.yang:957: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:967: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:979: error: node ietf-te::reverse is not found
ietf-otn-tunnel@2018-08-23.yang:991: error: node ietf-te::state is not found
ietf-otn-tunnel@2018-08-23.yang:1003: error: node ietf-te::state is not found
ietf-otn-tunnel@2018-08-23.yang:1017: error: node ietf-te::state is not found
ietf-otn-tunnel@2018-08-23.yang:1028: error: node ietf-te::lsp-record-route-subobjects is not found
ietf-otn-tunnel@2018-08-23.yang:1201 (at ietf-otn-tunnel@2018-08-23.yang:1058): error: the key "index" does not reference an existing leaf
ietf-otn-tunnel@2018-08-23.yang:1093: error: identity "tunnel-type" not found in module ietf-te-types
./ietf-te@2019-04-09.yang:109: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:109) is converted to 'string' when part of a union
./ietf-te@2019-04-09.yang:113: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:113) is converted to 'string' when part of a union
ietf-otn-tunnel@2018-08-23.yang:156: error: node 'p2p-reverse-primary-path' not found
ietf-otn-tunnel@2018-08-23.yang:156: error: node 'te-bandwidth' not found
ietf-otn-tunnel@2018-08-23.yang:156: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:182: error: node 'explicit-route-objects' not found
ietf-otn-tunnel@2018-08-23.yang:182: error: node 'route-object-exclude-always' not found
ietf-otn-tunnel@2018-08-23.yang:182: error: node 'type' not found
ietf-otn-tunnel@2018-08-23.yang:182: error: node 'label' not found
ietf-otn-tunnel@2018-08-23.yang:182: error: node 'label-hop' not found
ietf-otn-tunnel@2018-08-23.yang:182: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:182: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:193: error: node 'route-object-include-exclude' not found
ietf-otn-tunnel@2018-08-23.yang:193: error: node 'type' not found
ietf-otn-tunnel@2018-08-23.yang:193: error: node 'label' not found
ietf-otn-tunnel@2018-08-23.yang:193: error: node 'label-hop' not found
ietf-otn-tunnel@2018-08-23.yang:193: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:193: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:204: error: node 'forward' not found
ietf-otn-tunnel@2018-08-23.yang:204: error: node 'label-restrictions' not found
ietf-otn-tunnel@2018-08-23.yang:204: error: node 'label-restriction' not found
ietf-otn-tunnel@2018-08-23.yang:213: error: node 'label-start' not found
ietf-otn-tunnel@2018-08-23.yang:213: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:213: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:225: error: node 'label-end' not found
ietf-otn-tunnel@2018-08-23.yang:225: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:225: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:237: error: node 'reverse' not found
ietf-otn-tunnel@2018-08-23.yang:237: error: node 'label-restrictions' not found
ietf-otn-tunnel@2018-08-23.yang:237: error: node 'label-restriction' not found
ietf-otn-tunnel@2018-08-23.yang:246: error: node 'label-start' not found
ietf-otn-tunnel@2018-08-23.yang:246: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:246: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:258: error: node 'label-end' not found
ietf-otn-tunnel@2018-08-23.yang:258: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:258: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:270: error: node 'forward' not found
ietf-otn-tunnel@2018-08-23.yang:270: error: node 'label-restrictions' not found
ietf-otn-tunnel@2018-08-23.yang:270: error: node 'label-restriction' not found
ietf-otn-tunnel@2018-08-23.yang:279: error: node 'label-start' not found
ietf-otn-tunnel@2018-08-23.yang:279: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:279: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:291: error: node 'label-end' not found
ietf-otn-tunnel@2018-08-23.yang:291: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:291: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:303: error: node 'reverse' not found
ietf-otn-tunnel@2018-08-23.yang:303: error: node 'label-restrictions' not found
ietf-otn-tunnel@2018-08-23.yang:303: error: node 'label-restriction' not found
ietf-otn-tunnel@2018-08-23.yang:312: error: node 'label-start' not found
ietf-otn-tunnel@2018-08-23.yang:312: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:312: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:325: error: node 'label-end' not found
ietf-otn-tunnel@2018-08-23.yang:325: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:325: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:362: error: node 'explicit-route-objects' not found
ietf-otn-tunnel@2018-08-23.yang:362: error: node 'route-object-exclude-always' not found
ietf-otn-tunnel@2018-08-23.yang:362: error: node 'type' not found
ietf-otn-tunnel@2018-08-23.yang:362: error: node 'label' not found
ietf-otn-tunnel@2018-08-23.yang:362: error: node 'label-hop' not found
ietf-otn-tunnel@2018-08-23.yang:362: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:362: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:375: error: node 'route-object-include-exclude' not found
ietf-otn-tunnel@2018-08-23.yang:375: error: node 'type' not found
ietf-otn-tunnel@2018-08-23.yang:375: error: node 'label' not found
ietf-otn-tunnel@2018-08-23.yang:375: error: node 'label-hop' not found
ietf-otn-tunnel@2018-08-23.yang:375: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:375: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:387: error: node 'forward' not found
ietf-otn-tunnel@2018-08-23.yang:387: error: node 'label-restrictions' not found
ietf-otn-tunnel@2018-08-23.yang:387: error: node 'label-restriction' not found
ietf-otn-tunnel@2018-08-23.yang:396: error: node 'label-start' not found
ietf-otn-tunnel@2018-08-23.yang:396: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:396: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:408: error: node 'label-end' not found
ietf-otn-tunnel@2018-08-23.yang:408: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:408: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:420: error: node 'reverse' not found
ietf-otn-tunnel@2018-08-23.yang:420: error: node 'label-restrictions' not found
ietf-otn-tunnel@2018-08-23.yang:420: error: node 'label-restriction' not found
ietf-otn-tunnel@2018-08-23.yang:429: error: node 'label-start' not found
ietf-otn-tunnel@2018-08-23.yang:429: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:429: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:441: error: node 'label-end' not found
ietf-otn-tunnel@2018-08-23.yang:441: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:441: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:453: error: node 'forward' not found
ietf-otn-tunnel@2018-08-23.yang:453: error: node 'label-restrictions' not found
ietf-otn-tunnel@2018-08-23.yang:453: error: node 'label-restriction' not found
ietf-otn-tunnel@2018-08-23.yang:462: error: node 'label-start' not found
ietf-otn-tunnel@2018-08-23.yang:462: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:462: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:475: error: node 'label-end' not found
ietf-otn-tunnel@2018-08-23.yang:475: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:475: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:487: error: node 'reverse' not found
ietf-otn-tunnel@2018-08-23.yang:487: error: node 'label-restrictions' not found
ietf-otn-tunnel@2018-08-23.yang:487: error: node 'label-restriction' not found
ietf-otn-tunnel@2018-08-23.yang:496: error: node 'label-start' not found
ietf-otn-tunnel@2018-08-23.yang:496: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:496: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:508: error: node 'label-end' not found
ietf-otn-tunnel@2018-08-23.yang:508: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:508: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:521: error: node 'state' not found
ietf-otn-tunnel@2018-08-23.yang:521: error: node 'path-properties' not found
ietf-otn-tunnel@2018-08-23.yang:521: error: node 'path-route-objects' not found
ietf-otn-tunnel@2018-08-23.yang:521: error: node 'path-computed-route-object' not found
ietf-otn-tunnel@2018-08-23.yang:521: error: node 'state' not found
ietf-otn-tunnel@2018-08-23.yang:521: error: node 'type' not found
ietf-otn-tunnel@2018-08-23.yang:521: error: node 'label' not found
ietf-otn-tunnel@2018-08-23.yang:521: error: node 'label-hop' not found
ietf-otn-tunnel@2018-08-23.yang:521: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:521: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:534: error: node 'lsps' not found
ietf-otn-tunnel@2018-08-23.yang:534: error: node 'lsp' not found
ietf-otn-tunnel@2018-08-23.yang:534: error: node 'lsp-record-route-subobjects' not found
ietf-otn-tunnel@2018-08-23.yang:534: error: node 'record-route-subobject' not found
ietf-otn-tunnel@2018-08-23.yang:534: error: node 'type' not found
ietf-otn-tunnel@2018-08-23.yang:534: error: node 'label' not found
ietf-otn-tunnel@2018-08-23.yang:534: error: node 'label-hop' not found
ietf-otn-tunnel@2018-08-23.yang:534: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:534: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:546: error: node 'path-properties' not found
ietf-otn-tunnel@2018-08-23.yang:546: error: node 'path-route-objects' not found
ietf-otn-tunnel@2018-08-23.yang:546: error: node 'path-computed-route-object' not found
ietf-otn-tunnel@2018-08-23.yang:546: error: node 'state' not found
ietf-otn-tunnel@2018-08-23.yang:546: error: node 'type' not found
ietf-otn-tunnel@2018-08-23.yang:546: error: node 'label' not found
ietf-otn-tunnel@2018-08-23.yang:546: error: node 'label-hop' not found
ietf-otn-tunnel@2018-08-23.yang:546: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:546: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:559: error: node 'optimizations' not found
ietf-otn-tunnel@2018-08-23.yang:559: error: node 'algorithm' not found
ietf-otn-tunnel@2018-08-23.yang:559: error: node 'metric' not found
ietf-otn-tunnel@2018-08-23.yang:559: error: node 'optimization-metric' not found
ietf-otn-tunnel@2018-08-23.yang:559: error: node 'explicit-route-exclude-objects' not found
ietf-otn-tunnel@2018-08-23.yang:559: error: node 'route-object-exclude-object' not found
ietf-otn-tunnel@2018-08-23.yang:559: error: node 'type' not found
ietf-otn-tunnel@2018-08-23.yang:559: error: node 'label' not found
ietf-otn-tunnel@2018-08-23.yang:559: error: node 'label-hop' not found
ietf-otn-tunnel@2018-08-23.yang:559: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:559: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:574: error: node 'explicit-route-include-objects' not found
ietf-otn-tunnel@2018-08-23.yang:574: error: node 'route-object-include-object' not found
ietf-otn-tunnel@2018-08-23.yang:574: error: node 'type' not found
ietf-otn-tunnel@2018-08-23.yang:574: error: node 'label' not found
ietf-otn-tunnel@2018-08-23.yang:574: error: node 'label-hop' not found
ietf-otn-tunnel@2018-08-23.yang:574: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:574: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:588: error: node 'explicit-route-objects' not found
ietf-otn-tunnel@2018-08-23.yang:588: error: node 'route-object-exclude-always' not found
ietf-otn-tunnel@2018-08-23.yang:588: error: node 'type' not found
ietf-otn-tunnel@2018-08-23.yang:588: error: node 'label' not found
ietf-otn-tunnel@2018-08-23.yang:588: error: node 'label-hop' not found
ietf-otn-tunnel@2018-08-23.yang:588: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:588: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:602: error: node 'route-object-include-exclude' not found
ietf-otn-tunnel@2018-08-23.yang:602: error: node 'type' not found
ietf-otn-tunnel@2018-08-23.yang:602: error: node 'label' not found
ietf-otn-tunnel@2018-08-23.yang:602: error: node 'label-hop' not found
ietf-otn-tunnel@2018-08-23.yang:602: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:602: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:616: error: node 'path-in-segment' not found
ietf-otn-tunnel@2018-08-23.yang:616: error: node 'forward' not found
ietf-otn-tunnel@2018-08-23.yang:616: error: node 'label-restrictions' not found
ietf-otn-tunnel@2018-08-23.yang:616: error: node 'label-restriction' not found
ietf-otn-tunnel@2018-08-23.yang:626: error: node 'label-start' not found
ietf-otn-tunnel@2018-08-23.yang:626: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:626: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:639: error: node 'label-end' not found
ietf-otn-tunnel@2018-08-23.yang:639: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:639: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:652: error: node 'reverse' not found
ietf-otn-tunnel@2018-08-23.yang:652: error: node 'label-restrictions' not found
ietf-otn-tunnel@2018-08-23.yang:652: error: node 'label-restriction' not found
ietf-otn-tunnel@2018-08-23.yang:662: error: node 'label-start' not found
ietf-otn-tunnel@2018-08-23.yang:662: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:662: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:676: error: node 'label-end' not found
ietf-otn-tunnel@2018-08-23.yang:676: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:676: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:689: error: node 'path-out-segment' not found
ietf-otn-tunnel@2018-08-23.yang:689: error: node 'forward' not found
ietf-otn-tunnel@2018-08-23.yang:689: error: node 'label-restrictions' not found
ietf-otn-tunnel@2018-08-23.yang:689: error: node 'label-restriction' not found
ietf-otn-tunnel@2018-08-23.yang:699: error: node 'label-start' not found
ietf-otn-tunnel@2018-08-23.yang:699: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:699: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:713: error: node 'label-end' not found
ietf-otn-tunnel@2018-08-23.yang:713: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:713: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:726: error: node 'reverse' not found
ietf-otn-tunnel@2018-08-23.yang:726: error: node 'label-restrictions' not found
ietf-otn-tunnel@2018-08-23.yang:726: error: node 'label-restriction' not found
ietf-otn-tunnel@2018-08-23.yang:736: error: node 'label-start' not found
ietf-otn-tunnel@2018-08-23.yang:736: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:736: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:749: error: node 'label-end' not found
ietf-otn-tunnel@2018-08-23.yang:749: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:749: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:762: error: node 'state' not found
ietf-otn-tunnel@2018-08-23.yang:762: error: node 'path-properties' not found
ietf-otn-tunnel@2018-08-23.yang:762: error: node 'path-route-objects' not found
ietf-otn-tunnel@2018-08-23.yang:762: error: node 'path-computed-route-object' not found
ietf-otn-tunnel@2018-08-23.yang:762: error: node 'state' not found
ietf-otn-tunnel@2018-08-23.yang:762: error: node 'type' not found
ietf-otn-tunnel@2018-08-23.yang:762: error: node 'label' not found
ietf-otn-tunnel@2018-08-23.yang:762: error: node 'label-hop' not found
ietf-otn-tunnel@2018-08-23.yang:762: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:762: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:776: error: node 'lsps' not found
ietf-otn-tunnel@2018-08-23.yang:776: error: node 'lsp' not found
ietf-otn-tunnel@2018-08-23.yang:776: error: node 'lsp-record-route-subobjects' not found
ietf-otn-tunnel@2018-08-23.yang:776: error: node 'record-route-subobject' not found
ietf-otn-tunnel@2018-08-23.yang:776: error: node 'type' not found
ietf-otn-tunnel@2018-08-23.yang:776: error: node 'label' not found
ietf-otn-tunnel@2018-08-23.yang:776: error: node 'label-hop' not found
ietf-otn-tunnel@2018-08-23.yang:776: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:776: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:789: error: node 'path-properties' not found
ietf-otn-tunnel@2018-08-23.yang:789: error: node 'path-route-objects' not found
ietf-otn-tunnel@2018-08-23.yang:789: error: node 'path-computed-route-object' not found
ietf-otn-tunnel@2018-08-23.yang:789: error: node 'state' not found
ietf-otn-tunnel@2018-08-23.yang:789: error: node 'type' not found
ietf-otn-tunnel@2018-08-23.yang:789: error: node 'label' not found
ietf-otn-tunnel@2018-08-23.yang:789: error: node 'label-hop' not found
ietf-otn-tunnel@2018-08-23.yang:789: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:789: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:829: error: node 'explicit-route-objects' not found
ietf-otn-tunnel@2018-08-23.yang:829: error: node 'route-object-exclude-always' not found
ietf-otn-tunnel@2018-08-23.yang:829: error: node 'type' not found
ietf-otn-tunnel@2018-08-23.yang:829: error: node 'label' not found
ietf-otn-tunnel@2018-08-23.yang:829: error: node 'label-hop' not found
ietf-otn-tunnel@2018-08-23.yang:829: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:829: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:841: error: node 'route-object-include-exclude' not found
ietf-otn-tunnel@2018-08-23.yang:841: error: node 'type' not found
ietf-otn-tunnel@2018-08-23.yang:841: error: node 'label' not found
ietf-otn-tunnel@2018-08-23.yang:841: error: node 'label-hop' not found
ietf-otn-tunnel@2018-08-23.yang:841: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:841: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:853: error: node 'forward' not found
ietf-otn-tunnel@2018-08-23.yang:853: error: node 'label-restrictions' not found
ietf-otn-tunnel@2018-08-23.yang:853: error: node 'label-restriction' not found
ietf-otn-tunnel@2018-08-23.yang:863: error: node 'label-start' not found
ietf-otn-tunnel@2018-08-23.yang:863: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:863: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:875: error: node 'label-end' not found
ietf-otn-tunnel@2018-08-23.yang:875: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:875: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:887: error: node 'reverse' not found
ietf-otn-tunnel@2018-08-23.yang:887: error: node 'label-restrictions' not found
ietf-otn-tunnel@2018-08-23.yang:887: error: node 'label-restriction' not found
ietf-otn-tunnel@2018-08-23.yang:896: error: node 'label-start' not found
ietf-otn-tunnel@2018-08-23.yang:896: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:896: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:908: error: node 'label-end' not found
ietf-otn-tunnel@2018-08-23.yang:908: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:908: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:920: error: node 'forward' not found
ietf-otn-tunnel@2018-08-23.yang:920: error: node 'label-restrictions' not found
ietf-otn-tunnel@2018-08-23.yang:920: error: node 'label-restriction' not found
ietf-otn-tunnel@2018-08-23.yang:929: error: node 'label-start' not found
ietf-otn-tunnel@2018-08-23.yang:929: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:929: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:941: error: node 'label-end' not found
ietf-otn-tunnel@2018-08-23.yang:941: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:941: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:953: error: node 'reverse' not found
ietf-otn-tunnel@2018-08-23.yang:953: error: node 'label-restrictions' not found
ietf-otn-tunnel@2018-08-23.yang:953: error: node 'label-restriction' not found
ietf-otn-tunnel@2018-08-23.yang:963: error: node 'label-start' not found
ietf-otn-tunnel@2018-08-23.yang:963: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:963: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:975: error: node 'label-end' not found
ietf-otn-tunnel@2018-08-23.yang:975: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:975: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:987: error: node 'state' not found
ietf-otn-tunnel@2018-08-23.yang:987: error: node 'path-properties' not found
ietf-otn-tunnel@2018-08-23.yang:987: error: node 'path-route-objects' not found
ietf-otn-tunnel@2018-08-23.yang:987: error: node 'path-computed-route-object' not found
ietf-otn-tunnel@2018-08-23.yang:987: error: node 'state' not found
ietf-otn-tunnel@2018-08-23.yang:987: error: node 'type' not found
ietf-otn-tunnel@2018-08-23.yang:987: error: node 'label' not found
ietf-otn-tunnel@2018-08-23.yang:987: error: node 'label-hop' not found
ietf-otn-tunnel@2018-08-23.yang:987: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:987: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:999: error: node 'lsps' not found
ietf-otn-tunnel@2018-08-23.yang:999: error: node 'lsp' not found
ietf-otn-tunnel@2018-08-23.yang:999: error: node 'lsp-record-route-subobjects' not found
ietf-otn-tunnel@2018-08-23.yang:999: error: node 'record-route-subobject' not found
ietf-otn-tunnel@2018-08-23.yang:999: error: node 'type' not found
ietf-otn-tunnel@2018-08-23.yang:999: error: node 'label' not found
ietf-otn-tunnel@2018-08-23.yang:999: error: node 'label-hop' not found
ietf-otn-tunnel@2018-08-23.yang:999: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:999: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:1012: error: node 'path-properties' not found
ietf-otn-tunnel@2018-08-23.yang:1012: error: node 'path-route-objects' not found
ietf-otn-tunnel@2018-08-23.yang:1012: error: node 'path-computed-route-object' not found
ietf-otn-tunnel@2018-08-23.yang:1012: error: node 'state' not found
ietf-otn-tunnel@2018-08-23.yang:1012: error: node 'type' not found
ietf-otn-tunnel@2018-08-23.yang:1012: error: node 'label' not found
ietf-otn-tunnel@2018-08-23.yang:1012: error: node 'label-hop' not found
ietf-otn-tunnel@2018-08-23.yang:1012: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:1012: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:1025: error: node 'lsp-record-route-subobjects' not found
ietf-otn-tunnel@2018-08-23.yang:1025: error: node 'record-route-subobject' not found
ietf-otn-tunnel@2018-08-23.yang:1025: error: node 'type' not found
ietf-otn-tunnel@2018-08-23.yang:1025: error: node 'label' not found
ietf-otn-tunnel@2018-08-23.yang:1025: error: node 'label-hop' not found
ietf-otn-tunnel@2018-08-23.yang:1025: error: node 'te-label' not found
ietf-otn-tunnel@2018-08-23.yang:1025: error: node 'technology' not found
ietf-otn-tunnel@2018-08-23.yang:1058: error: the key index does not reference an existing leaf
ietf-otn-tunnel@2018-08-23.yang:1093: error: identity 'tunnel-type' in module 'ietf-te-types' not found
Error: identity definition for 'te-types:tunnel-type' not found in module ietf-te-types
ietf-otn-tunnel@2018-08-23.yang:1092.11: error(250): definition not found

Error: identityref has unknown base value (tunnel-type)
ietf-otn-tunnel@2018-08-23.yang:1092.11: error(250): definition not found

Error: object 'p2p-reverse-primary-path' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:156.3: error(251): definition segment not found

Error: object 'explicit-route-objects' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:182.3: error(251): definition segment not found

Error: object 'explicit-route-objects' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:193.3: error(251): definition segment not found

Error: object 'forward' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:204.3: error(251): definition segment not found

Error: object 'forward' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:213.3: error(251): definition segment not found

Error: object 'forward' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:225.3: error(251): definition segment not found

Error: object 'reverse' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:237.3: error(251): definition segment not found

Error: object 'reverse' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:246.3: error(251): definition segment not found

Error: object 'reverse' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:258.3: error(251): definition segment not found

Error: object 'forward' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:270.3: error(251): definition segment not found

Error: object 'forward' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:279.3: error(251): definition segment not found

Error: object 'forward' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:291.3: error(251): definition segment not found

Error: object 'reverse' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:303.3: error(251): definition segment not found

Error: object 'reverse' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:312.3: error(251): definition segment not found

Error: object 'reverse' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:325.3: error(251): definition segment not found

Error: object 'explicit-route-objects' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:362.3: error(251): definition segment not found

Error: object 'explicit-route-objects' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:375.3: error(251): definition segment not found

Error: object 'forward' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:387.3: error(251): definition segment not found

Error: object 'forward' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:396.3: error(251): definition segment not found

Error: object 'forward' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:408.3: error(251): definition segment not found

Error: object 'reverse' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:420.3: error(251): definition segment not found

Error: object 'reverse' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:429.3: error(251): definition segment not found

Error: object 'reverse' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:441.3: error(251): definition segment not found

Error: object 'forward' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:453.3: error(251): definition segment not found

Error: object 'forward' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:462.3: error(251): definition segment not found

Error: object 'forward' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:475.3: error(251): definition segment not found

Error: object 'reverse' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:487.3: error(251): definition segment not found

Error: object 'reverse' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:496.3: error(251): definition segment not found

Error: object 'reverse' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:508.3: error(251): definition segment not found

Error: object 'state' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:521.3: error(251): definition segment not found

Error: object 'state' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:534.3: error(251): definition segment not found

Error: object 'state' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:546.3: error(251): definition segment not found

Error: object 'p2p-reverse-primary-path' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:559.3: error(251): definition segment not found

Error: object 'p2p-reverse-primary-path' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:574.3: error(251): definition segment not found

Error: object 'p2p-reverse-primary-path' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:588.3: error(251): definition segment not found

Error: object 'p2p-reverse-primary-path' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:602.3: error(251): definition segment not found

Error: object 'p2p-reverse-primary-path' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:616.3: error(251): definition segment not found

Error: object 'p2p-reverse-primary-path' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:626.3: error(251): definition segment not found

Error: object 'p2p-reverse-primary-path' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:639.3: error(251): definition segment not found

Error: object 'p2p-reverse-primary-path' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:652.3: error(251): definition segment not found

Error: object 'p2p-reverse-primary-path' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:662.3: error(251): definition segment not found

Error: object 'p2p-reverse-primary-path' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:676.3: error(251): definition segment not found

Error: object 'p2p-reverse-primary-path' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:689.3: error(251): definition segment not found

Error: object 'p2p-reverse-primary-path' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:699.3: error(251): definition segment not found

Error: object 'p2p-reverse-primary-path' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:713.3: error(251): definition segment not found

Error: object 'p2p-reverse-primary-path' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:726.3: error(251): definition segment not found

Error: object 'p2p-reverse-primary-path' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:736.3: error(251): definition segment not found

Error: object 'p2p-reverse-primary-path' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:749.3: error(251): definition segment not found

Error: object 'p2p-reverse-primary-path' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:762.3: error(251): definition segment not found

Error: object 'p2p-reverse-primary-path' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:776.3: error(251): definition segment not found

Error: object 'p2p-reverse-primary-path' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:789.3: error(251): definition segment not found

Error: object 'explicit-route-objects' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:829.3: error(251): definition segment not found

Error: object 'explicit-route-objects' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:841.3: error(251): definition segment not found

Error: object 'forward' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:853.3: error(251): definition segment not found

Error: object 'forward' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:863.3: error(251): definition segment not found

Error: object 'forward' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:875.3: error(251): definition segment not found

Error: object 'reverse' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:887.3: error(251): definition segment not found

Error: object 'reverse' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:896.3: error(251): definition segment not found

Error: object 'reverse' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:908.3: error(251): definition segment not found

Error: object 'forward' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:920.3: error(251): definition segment not found

Error: object 'forward' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:929.3: error(251): definition segment not found

Error: object 'forward' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:941.3: error(251): definition segment not found

Error: object 'reverse' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:953.3: error(251): definition segment not found

Error: object 'reverse' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:963.3: error(251): definition segment not found

Error: object 'reverse' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:975.3: error(251): definition segment not found

Error: object 'state' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:987.3: error(251): definition segment not found

Error: object 'state' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:999.3: error(251): definition segment not found

Error: object 'state' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:1012.3: error(251): definition segment not found

Error: object 'lsp-record-route-subobjects' not found in module ietf-te
ietf-otn-tunnel@2018-08-23.yang:1025.3: error(251): definition segment not found

Error: object 'index' not found in module ietf-otn-tunnel in Xpath target index
ietf-otn-tunnel@2018-08-23.yang:1058.9: error(250): definition not found

Error: invalid identifier in key for list 'explicit-route-object' (index)
ietf-otn-tunnel@2018-08-23.yang:1058.9: error(250): definition not found

Error: object 'index' not found in module ietf-otn-tunnel in Xpath target index
ietf-otn-tunnel@2018-08-23.yang:1057.7: error(250): definition not found

Error: invalid identifier in key for list 'explicit-route-object' (index)
ietf-otn-tunnel@2018-08-23.yang:1057.7: error(250): definition not found

Error: object 'index' not found in module ietf-otn-tunnel in Xpath target index
ietf-otn-tunnel@2018-08-23.yang:1057.7: error(250): definition not found

Error: invalid identifier in key for list 'explicit-route-object' (index)
ietf-otn-tunnel@2018-08-23.yang:1057.7: error(250): definition not found

Error: object 'index' not found in module ietf-otn-tunnel in Xpath target index
ietf-otn-tunnel@2018-08-23.yang:1057.7: error(250): definition not found

Error: invalid identifier in key for list 'explicit-route-object' (index)
ietf-otn-tunnel@2018-08-23.yang:1057.7: error(250): definition not found

Error: object 'index' not found in module ietf-otn-tunnel in Xpath target index
ietf-otn-tunnel@2018-08-23.yang:1057.7: error(250): definition not found

Error: invalid identifier in key for list 'explicit-route-object' (index)
ietf-otn-tunnel@2018-08-23.yang:1057.7: error(250): definition not found

***
*** 81 Errors, 0 Warnings
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:te-bandwidth/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:te-bandwidth/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:explicit-route-objects/ietf-te:route-object-exclude-always/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:explicit-route-objects/ietf-te:route-object-exclude-always/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:explicit-route-objects/ietf-te:route-object-include-exclude/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:explicit-route-objects/ietf-te:route-object-include-exclude/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:path-in-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:path-in-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction])
err : Failed to resolve augment "/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:path-in-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:path-in-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:path-in-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:path-in-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:path-in-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:path-in-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction])
err : Failed to resolve augment "/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:path-in-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:path-in-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:path-in-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:path-in-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:path-out-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:path-out-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction])
err : Failed to resolve augment "/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:path-out-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:path-out-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:path-out-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:path-out-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:path-out-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:path-out-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction])
err : Failed to resolve augment "/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:path-out-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:path-out-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:path-out-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:globals/ietf-te:named-path-constraints/ietf-te:named-path-constraint/ietf-te:path-out-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:explicit-route-objects/ietf-te:route-object-exclude-always/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:explicit-route-objects/ietf-te:route-object-exclude-always/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:explicit-route-objects/ietf-te:route-object-include-exclude/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:explicit-route-objects/ietf-te:route-object-include-exclude/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:path-in-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:path-in-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:path-in-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:path-in-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:path-in-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:path-in-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:path-in-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:path-in-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:path-in-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:path-in-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:path-in-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:path-in-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:path-out-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:path-out-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:path-out-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:path-out-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:path-out-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:path-out-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:path-out-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:path-out-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:path-out-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:path-out-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:path-out-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:path-out-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:state/ietf-te:path-properties/ietf-te:path-route-objects/ietf-te:path-computed-route-object/ietf-te:state/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:state/ietf-te:path-properties/ietf-te:path-route-objects/ietf-te:path-computed-route-object/ietf-te:state/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:state/ietf-te:lsps/ietf-te:lsp/ietf-te:lsp-record-route-subobjects/ietf-te:record-route-subobject/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:state/ietf-te:lsps/ietf-te:lsp/ietf-te:lsp-record-route-subobjects/ietf-te:record-route-subobject/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:state/ietf-te:lsps/ietf-te:lsp/ietf-te:path-properties/ietf-te:path-route-objects/ietf-te:path-computed-route-object/ietf-te:state/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:state/ietf-te:lsps/ietf-te:lsp/ietf-te:path-properties/ietf-te:path-route-objects/ietf-te:path-computed-route-object/ietf-te:state/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:optimizations/ietf-te:algorithm/ietf-te:metric/ietf-te:optimization-metric/ietf-te:explicit-route-exclude-objects/ietf-te:route-object-exclude-object/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:optimizations/ietf-te:algorithm/ietf-te:metric/ietf-te:optimization-metric/ietf-te:explicit-route-exclude-objects/ietf-te:route-object-exclude-object/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:optimizations/ietf-te:algorithm/ietf-te:metric/ietf-te:optimization-metric/ietf-te:explicit-route-include-objects/ietf-te:route-object-include-object/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:optimizations/ietf-te:algorithm/ietf-te:metric/ietf-te:optimization-metric/ietf-te:explicit-route-include-objects/ietf-te:route-object-include-object/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:explicit-route-objects/ietf-te:route-object-exclude-always/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:explicit-route-objects/ietf-te:route-object-exclude-always/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:explicit-route-objects/ietf-te:route-object-include-exclude/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:explicit-route-objects/ietf-te:route-object-include-exclude/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:path-in-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:path-in-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:path-in-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:path-in-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:path-in-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:path-in-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:path-in-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:path-in-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:path-in-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:path-in-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:path-in-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:path-in-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:path-out-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:path-out-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:path-out-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:path-out-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:path-out-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:path-out-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:path-out-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:path-out-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:path-out-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:path-out-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:path-out-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:path-out-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:state/ietf-te:path-properties/ietf-te:path-route-objects/ietf-te:path-computed-route-object/ietf-te:state/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:state/ietf-te:path-properties/ietf-te:path-route-objects/ietf-te:path-computed-route-object/ietf-te:state/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:state/ietf-te:lsps/ietf-te:lsp/ietf-te:lsp-record-route-subobjects/ietf-te:record-route-subobject/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:state/ietf-te:lsps/ietf-te:lsp/ietf-te:lsp-record-route-subobjects/ietf-te:record-route-subobject/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:state/ietf-te:lsps/ietf-te:lsp/ietf-te:path-properties/ietf-te:path-route-objects/ietf-te:path-computed-route-object/ietf-te:state/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-primary-paths/ietf-te:p2p-primary-path/ietf-te:p2p-reverse-primary-path/ietf-te:state/ietf-te:lsps/ietf-te:lsp/ietf-te:path-properties/ietf-te:path-route-objects/ietf-te:path-computed-route-object/ietf-te:state/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:explicit-route-objects/ietf-te:route-object-exclude-always/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:explicit-route-objects/ietf-te:route-object-exclude-always/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:explicit-route-objects/ietf-te:route-object-include-exclude/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:explicit-route-objects/ietf-te:route-object-include-exclude/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:path-in-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:path-in-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:path-in-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:path-in-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:path-in-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:path-in-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:path-in-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:path-in-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:path-in-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:path-in-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:path-in-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:path-in-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:path-out-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:path-out-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:path-out-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:path-out-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:path-out-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:path-out-segment/ietf-te:forward/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:path-out-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:path-out-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:path-out-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:path-out-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-start/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:path-out-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:path-out-segment/ietf-te:reverse/ietf-te:label-restrictions/ietf-te:label-restriction/ietf-te:label-end/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:state/ietf-te:path-properties/ietf-te:path-route-objects/ietf-te:path-computed-route-object/ietf-te:state/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:state/ietf-te:path-properties/ietf-te:path-route-objects/ietf-te:path-computed-route-object/ietf-te:state/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:state/ietf-te:lsps/ietf-te:lsp/ietf-te:lsp-record-route-subobjects/ietf-te:record-route-subobject/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:state/ietf-te:lsps/ietf-te:lsp/ietf-te:lsp-record-route-subobjects/ietf-te:record-route-subobject/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:state/ietf-te:lsps/ietf-te:lsp/ietf-te:path-properties/ietf-te:path-route-objects/ietf-te:path-computed-route-object/ietf-te:state/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:p2p-secondary-paths/ietf-te:p2p-secondary-path/ietf-te:state/ietf-te:lsps/ietf-te:lsp/ietf-te:path-properties/ietf-te:path-route-objects/ietf-te:path-computed-route-object/ietf-te:state/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology])
err : Failed to resolve augment "/ietf-te:te/ietf-te:lsps-state/ietf-te:lsp/ietf-te:lsp-record-route-subobjects/ietf-te:record-route-subobject/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology". (/ietf-otn-tunnel:{augment}[/ietf-te:te/ietf-te:lsps-state/ietf-te:lsp/ietf-te:lsp-record-route-subobjects/ietf-te:record-route-subobject/ietf-te:type/ietf-te:label/ietf-te:label-hop/ietf-te:te-label/ietf-te:technology])
err : Module "ietf-otn-tunnel" parsing failed.
ietf-otn-types@2019-01-15.yang draft-ietf-ccamp-otn-tunnel-model-06.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-otn-types@2019-01-15.yang:39: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-pcep-srv6@2019-03-08.yang draft-li-pce-pcep-srv6-yang-00.txt Email Authors Download the YANG model FAILED ietf-pcep-srv6@2019-03-08.yang:33: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-pcep-srv6@2019-03-08.yang:145: warning: node ietf-pcep-srv6::path-setup-srv6 is not found in ietf-pcep-srv6::srv6
ietf-pcep-srv6@2019-03-08.yang:145: warning: node ietf-pcep-srv6::path-setup-srv6 is not found in ietf-pcep-srv6::srv6
/home/bclaise/yang/modules/YANG/ietf-pcep@2019-03-26.yang:56: error: module "ietf-isis" not found in search path
./ietf-pcep@2019-03-26.yang:56: error: module 'ietf-isis' not found
./ietf-te@2019-04-09.yang:109: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:109) is converted to 'string' when part of a union
./ietf-te@2019-04-09.yang:113: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:113) is converted to 'string' when part of a union
ietf-pcep-srv6@2019-03-08.yang:144: error: the node 'path-setup-srv6' from module 'ietf-pcep-srv6' (in node 'srv6' in module 'ietf-pcep-srv6' from 'ietf-pcep-srv6') is not found
ietf-pcep-srv6@2019-03-08.yang:144: warning: The when expression refers to descendant node 'path-setup-srv6', will probably not work as intended.
Error: 'ietf-pcep@2019-03-26.yang' import of module 'ietf-isis' failed
ietf-pcep@2019-03-26.yang:56.3: error(236): module not found

Error: typedef definition for 'isis:area-address' not found in module ietf-isis
ietf-pcep@2019-03-26.yang:274.10: error(250): definition not found

Error: type 'domain-isis-area' not found
ietf-pcep@2019-03-26.yang:290.7: error(299): unknown data type

Error: 'ietf-pcep-srv6@2019-03-08.yang' import of module 'ietf-pcep' failed
ietf-pcep-srv6@2019-03-08.yang:18.5: error(321): import not found

Error: Module for prefix 'p' not found
ietf-pcep-srv6@2019-03-08.yang:144.19: error(236): module not found

Error: object 'pcep' not found in module ietf-pcep-srv6 in Xpath target /p:pcep/p:entity/p:capability
ietf-pcep-srv6@2019-03-08.yang:130.5: error(250): definition not found

Error: object 'pcep' not found in module ietf-pcep-srv6 in Xpath target /p:pcep/p:entity/p:peers/p:peer/p:capability
ietf-pcep-srv6@2019-03-08.yang:135.5: error(250): definition not found

Error: object 'pcep' not found in module ietf-pcep-srv6 in Xpath target /p:pcep/p:entity/p:lsp-db/p:lsp
ietf-pcep-srv6@2019-03-08.yang:140.5: error(250): definition not found

***
*** 5 Errors, 0 Warnings
err : Data model "ietf-isis" not found.
err : Importing "ietf-isis" module into "ietf-pcep" failed.
err : Module "ietf-pcep" parsing failed.
err : Importing "ietf-pcep" module into "ietf-pcep-srv6" failed.
err : Module "ietf-pcep-srv6" parsing failed.
ietf-pcep-stats@2019-03-26.yang draft-ietf-pce-pcep-yang-11.txt Email Authors Download the YANG model FAILED ietf-pcep-stats@2019-03-26.yang:40: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
/home/bclaise/yang/modules/YANG/ietf-pcep@2019-03-26.yang:56: error: module "ietf-isis" not found in search path
./ietf-pcep@2019-03-26.yang:56: error: module 'ietf-isis' not found
./ietf-te@2019-04-09.yang:109: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:109) is converted to 'string' when part of a union
./ietf-te@2019-04-09.yang:113: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:113) is converted to 'string' when part of a union
Error: 'ietf-pcep@2019-03-26.yang' import of module 'ietf-isis' failed
ietf-pcep@2019-03-26.yang:56.3: error(236): module not found

Error: typedef definition for 'isis:area-address' not found in module ietf-isis
ietf-pcep@2019-03-26.yang:274.10: error(250): definition not found

Error: type 'domain-isis-area' not found
ietf-pcep@2019-03-26.yang:290.7: error(299): unknown data type

Error: 'ietf-pcep-stats@2019-03-26.yang' import of module 'ietf-pcep' failed
ietf-pcep-stats@2019-03-26.yang:6.3: error(321): import not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:59.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:73.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:87.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:101.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:112.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:123.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:134.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:185.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:200.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:212.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:226.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:241.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:256.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:271.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:284.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:297.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:313.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:325.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:339.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:353.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:369.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:385.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:398.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:413.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:430.23: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:443.23: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:455.23: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:468.23: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:486.23: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:497.23: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:508.23: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:519.23: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:530.23: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:545.23: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:561.23: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:574.23: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:589.23: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:605.23: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:620.23: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:635.23: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:652.28: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:663.28: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:674.28: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:690.28: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:706.28: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:723.18: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:799.20: error(236): module not found

Error: Module for prefix 'pcep' not found
ietf-pcep-stats@2019-03-26.yang:812.20: error(236): module not found

Error: 'ietf-pcep@2019-03-26.yang' import of module 'ietf-isis' failed
ietf-pcep@2019-03-26.yang:56.3: error(236): module not found

Load module 'ietf-pcep' failed (imported module has errors)
Error: failure importing module 'ietf-pcep'
ietf-pcep-stats@2019-03-26.yang:426.18: error(332): imported module has errors

Error: Invalid syntax found for if-feature 'pcep:svec'
ietf-pcep-stats@2019-03-26.yang:426.18: error(332): imported module has errors

Error: 'ietf-pcep@2019-03-26.yang' import of module 'ietf-isis' failed
ietf-pcep@2019-03-26.yang:56.3: error(236): module not found

Load module 'ietf-pcep' failed (imported module has errors)
Error: failure importing module 'ietf-pcep'
ietf-pcep-stats@2019-03-26.yang:482.18: error(332): imported module has errors

Error: Invalid syntax found for if-feature 'pcep:stateful'
ietf-pcep-stats@2019-03-26.yang:482.18: error(332): imported module has errors

Error: 'ietf-pcep@2019-03-26.yang' import of module 'ietf-isis' failed
ietf-pcep@2019-03-26.yang:56.3: error(236): module not found

Load module 'ietf-pcep' failed (imported module has errors)
Error: failure importing module 'ietf-pcep'
ietf-pcep-stats@2019-03-26.yang:648.20: error(332): imported module has errors

Error: Invalid syntax found for if-feature 'pcep:pce-initiated'
ietf-pcep-stats@2019-03-26.yang:648.20: error(332): imported module has errors

Error: 'ietf-pcep@2019-03-26.yang' import of module 'ietf-isis' failed
ietf-pcep@2019-03-26.yang:56.3: error(236): module not found

Load module 'ietf-pcep' failed (imported module has errors)
Error: failure importing module 'ietf-pcep'
ietf-pcep-stats@2019-03-26.yang:729.18: error(332): imported module has errors

Error: Invalid syntax found for if-feature 'pcep:path-key'
ietf-pcep-stats@2019-03-26.yang:729.18: error(332): imported module has errors

Error: object 'pcep' not found in module ietf-pcep-stats in Xpath target /pcep:pcep/pcep:entity/pcep:peers/pcep:peer
ietf-pcep-stats@2019-03-26.yang:765.3: error(250): definition not found

Error: object 'pcep' not found in module ietf-pcep-stats in Xpath target /pcep:pcep/pcep:entity/pcep:peers/pcep:peer/pcep:sessions/pcep:session
ietf-pcep-stats@2019-03-26.yang:830.3: error(250): definition not found

***
*** 59 Errors, 0 Warnings
err : Data model "ietf-isis" not found.
err : Importing "ietf-isis" module into "ietf-pcep" failed.
err : Module "ietf-pcep" parsing failed.
err : Importing "ietf-pcep" module into "ietf-pcep-stats" failed.
err : Module "ietf-pcep-stats" parsing failed.
ietf-pcep@2019-03-26.yang draft-ietf-pce-pcep-yang-11.txt Email Authors Download the YANG model FAILED ietf-pcep@2019-03-26.yang:56: error: module "ietf-isis" not found in search path
ietf-pcep@2019-03-26.yang:1317: 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-pcep@2019-03-26.yang:56: error: module "ietf-isis" not found in search path
./ietf-te@2019-04-09.yang:109: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:109) is converted to 'string' when part of a union
./ietf-te@2019-04-09.yang:113: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:113) is converted to 'string' when part of a union
ietf-pcep@2019-03-26.yang:56: error: module 'ietf-isis' not found
Error: 'ietf-pcep@2019-03-26.yang' import of module 'ietf-isis' failed
ietf-pcep@2019-03-26.yang:56.3: error(236): module not found

Error: typedef definition for 'isis:area-address' not found in module ietf-isis
ietf-pcep@2019-03-26.yang:274.10: error(250): definition not found

Error: type 'domain-isis-area' not found
ietf-pcep@2019-03-26.yang:290.7: error(299): unknown data type

***
*** 3 Errors, 0 Warnings
err : Data model "ietf-isis" not found.
err : Importing "ietf-isis" module into "ietf-pcep" failed.
err : Module "ietf-pcep" parsing failed.
ietf-pim-base@2018-04-16.yang draft-ietf-pim-yang-17.txt Email Authors Download the YANG model PASSED          
ietf-pim-bidir@2018-04-16.yang draft-ietf-pim-yang-17.txt Email Authors Download the YANG model PASSED          
ietf-pim-dm@2018-04-16.yang draft-ietf-pim-yang-17.txt Email Authors Download the YANG model PASSED          
ietf-pim-rp@2018-04-16.yang draft-ietf-pim-yang-17.txt Email Authors Download the YANG model PASSED          
ietf-pim-sm@2018-04-16.yang draft-ietf-pim-yang-17.txt Email Authors Download the YANG model PASSED          
ietf-pmip-qos@2018-05-17.yang draft-ietf-dmm-fpc-yang-00.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-pmip-qos@2018-05-17.yang:49: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-pmip-qos@2018-05-17.yang:113: 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-pot-profile@2016-06-15.yang draft-ietf-sfc-proof-of-transit-02.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-pot-profile@2016-06-15.yang:17: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-ppr@2018-06-20.yang draft-qct-lsr-ppr-yang-01.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-ppr@2018-06-20.yang:11: warning: imported module ietf-yang-types not used
ietf-ppr@2018-06-20.yang:15: warning: imported module ietf-routing-types not used
ietf-ppr@2018-06-20.yang:11: warning: imported module ietf-yang-types not used
ietf-ppr@2018-06-20.yang:15: warning: imported module ietf-routing-types not used
  Warning: Module 'ietf-yang-types' not used
ietf-ppr@2018-06-20.yang:11.3: warning(1015): import not used

Warning: Module 'ietf-routing-types' not used
ietf-ppr@2018-06-20.yang:15.3: warning(1015): import not used

***
*** 0 Errors, 2 Warnings
 
ietf-psamp@2019-03-11.yang draft-boydseda-ipfix-psamp-bulk-data-yang-model-01.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-psamp@2019-03-11.yang:56: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-psamp@2019-03-11.yang:276: 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-qos-action@2019-03-13.yang draft-asechoud-rtgwg-qos-model-09.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-qos-action@2019-03-13.yang:39: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-qos-classifier@2019-03-13.yang draft-asechoud-rtgwg-qos-model-09.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-qos-classifier@2019-03-13.yang:33: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-qos-oper@2018-06-28.yang draft-asechoud-rtgwg-qos-oper-model-03.txt Email Authors Download the YANG model PASSED          
ietf-qos-policy@2019-03-13.yang draft-asechoud-rtgwg-qos-model-09.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-qos-policy@2019-03-13.yang:35: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-qos-target@2019-03-13.yang draft-asechoud-rtgwg-qos-model-09.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-qos-target@2019-03-13.yang:41: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-queue-policy@2019-03-13.yang draft-asechoud-rtgwg-qos-model-09.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-queue-policy@2019-03-13.yang:45: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-restconf-client@2019-06-07.yang draft-ietf-netconf-restconf-client-server-13.txt Email Authors Download the YANG model PASSED          
ietf-restconf-server@2019-06-07.yang draft-ietf-netconf-restconf-client-server-13.txt Email Authors Download the YANG model PASSED          
ietf-restconf-subscribed-notifications@2019-01-11.yang draft-ietf-netconf-restconf-notif-14.txt Email Authors Download the YANG model FAILED         err : The leafref leaf is config but refers to a non-config leaf. (/ietf-subscribed-notifications:subscriptions/subscription/target/stream/stream)
err : Invalid value "subscription-policy" of "uses". (/ietf-subscribed-notifications:subscriptions/subscription/subscription-policy)
err : Copying data from grouping failed. (/ietf-subscribed-notifications:subscriptions/subscription/subscription-policy)
err : Module "ietf-subscribed-notifications" parsing failed.
err : Importing "ietf-subscribed-notifications" module into "ietf-restconf-subscribed-notifications" failed.
err : Module "ietf-restconf-subscribed-notifications" parsing failed.
ietf-rib-extension@2019-03-01.yang draft-rtgwg-yang-rib-extend-00.txt Email Authors Download the YANG model PASSED          
ietf-rib-extension@2019-03-11.yang draft-ietf-rtgwg-yang-rib-extend-01.txt Email Authors Download the YANG model PASSED          
ietf-rift@2019-05-05.yang draft-ietf-rift-yang-00.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-rift@2019-05-05.yang:61: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-rift@2019-05-05.yang:194: 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-rip@2018-02-03.yang draft-ietf-rtgwg-yang-rip-10.txt Email Authors Download the YANG model FAILED ietf-rip@2018-02-03.yang:39: error: module "ietf-isis" not found in search path
ietf-rip@2018-02-03.yang:39: warning: imported module ietf-isis not used
ietf-rip@2018-02-03.yang:39: error: module "ietf-isis" not found in search path
ietf-rip@2018-02-03.yang:39: warning: imported module ietf-isis not used
ietf-rip@2018-02-03.yang:39: error: module 'ietf-isis' not found
Error: 'ietf-rip@2018-02-03.yang' import of module 'ietf-isis' failed
ietf-rip@2018-02-03.yang:39.3: error(236): module not found

***
*** 1 Errors, 0 Warnings
err : Data model "ietf-isis" not found.
err : Importing "ietf-isis" module into "ietf-rip" failed.
err : Module "ietf-rip" parsing failed.
ietf-routing-policy@2019-03-06.yang draft-ietf-rtgwg-policy-model-06.txt Email Authors Download the YANG model FAILED ietf-routing-policy@2019-03-06.yang:105: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
/home/bclaise/yang/modules/YANG/ietf-if-l3-vlan@2019-03-05.yang:12: warning: imported module iana-if-type not used
./ietf-if-l3-vlan@2019-03-05.yang:16: error: module 'ieee802-dot1q-types' not found
./ietf-if-l3-vlan@2019-03-05.yang:98: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-if-l3-vlan' (in node 'outer-tag' in module 'ietf-if-l3-vlan' from 'ietf-if-l3-vlan') is not found
./ietf-if-l3-vlan@2019-03-05.yang:118: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-if-l3-vlan' (in node 'outer-tag' in module 'ietf-if-l3-vlan' from 'ietf-if-l3-vlan') is not found
./ietf-if-l3-vlan@2019-03-05.yang:118: warning: The 'must' expression will fail: the node 'tag-type' from module 'ietf-if-l3-vlan' (in node 'second-tag' in module 'ietf-if-l3-vlan' from 'ietf-if-l3-vlan') is not found
ietf-routing-policy@2019-03-06.yang:441: error: the node 'vlan-id' from module 'ietf-if-l3-vlan' (in node 'outer-tag' in module 'ietf-if-l3-vlan' from 'ietf-if-l3-vlan') is not found
   
ietf-rsvp-extended@2019-02-18.yang draft-ietf-teas-yang-rsvp-10.txt Email Authors Download the YANG model PASSED          
ietf-rsvp-te-mpls@2019-04-09.yang draft-ietf-teas-yang-rsvp-te-06.txt Email Authors Download the YANG model PASSED WITH WARNINGS     ./ietf-te@2019-04-09.yang:109: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:109) is converted to 'string' when part of a union
./ietf-te@2019-04-09.yang:113: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:113) is converted to 'string' when part of a union
   
ietf-rsvp-te@2019-04-09.yang draft-ietf-teas-yang-rsvp-te-06.txt Email Authors Download the YANG model PASSED WITH WARNINGS     ./ietf-te@2019-04-09.yang:109: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:109) is converted to 'string' when part of a union
./ietf-te@2019-04-09.yang:113: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:113) is converted to 'string' when part of a union
   
ietf-rsvp@2019-02-18.yang draft-ietf-teas-yang-rsvp-10.txt Email Authors Download the YANG model PASSED          
ietf-scheduler-policy@2019-03-13.yang draft-asechoud-rtgwg-qos-model-09.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-scheduler-policy@2019-03-13.yang:43: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-schema-version-selection@2019-03-11.yang draft-wilton-netmod-yang-ver-selection-00.txt Email Authors Download the YANG model PASSED WITH WARNINGS         warn: Missing status in deprecated subtree (/ietf-yang-library:{grouping}[module-list]/{grouping}[schema-leaf]/schema), inheriting.
ietf-sdwan-vpn-svc@2019-03-10.yang draft-sun-opsawg-sdwan-service-model-02.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-sdwan-vpn-svc@2019-03-10.yang:20: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-sdwan-vpn-svc@2019-03-10.yang:992: 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-segment-routing-common@2019-02-28.yang draft-ietf-spring-sr-yang-12.txt Email Authors Download the YANG model PASSED          
ietf-segment-routing@2019-02-28.yang draft-ietf-spring-sr-yang-12.txt Email Authors Download the YANG model PASSED          
ietf-segment-vpn@2019-01-30.yang draft-evenwu-opsawg-yang-composed-vpn-03.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-segment-vpn@2019-01-30.yang:35: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-sid-file@2017-11-26.yang draft-ietf-core-sid-06.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-sid-file@2017-11-26.yang:27: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-sid-file@2017-11-26.yang:116: 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-softwire-br@2019-01-11.yang draft-ietf-softwire-yang-16.txt Email Authors Download the YANG model PASSED          
ietf-softwire-ce@2019-01-11.yang draft-ietf-softwire-yang-16.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-softwire-ce@2019-01-11.yang:20: warning: imported module iana-tunnel-type not used
ietf-softwire-ce@2019-01-11.yang:20: warning: imported module iana-tunnel-type not used
     
ietf-softwire-common@2019-01-11.yang draft-ietf-softwire-yang-16.txt Email Authors Download the YANG model PASSED          
ietf-sr-policy-types@2018-07-01.yang draft-raza-spring-sr-policy-yang-00.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-sr-policy-types@2018-07-01.yang:2: warning: RFC 8407: 4.9: namespace value should be "urn:ietf:params:xml:ns:yang:ietf-sr-policy-types"
ietf-sr-policy-types@2018-07-01.yang:6: warning: imported module ietf-inet-types not used
ietf-sr-policy-types@2018-07-01.yang:52: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-sr-policy-types@2018-07-01.yang:6: warning: imported module ietf-inet-types not used
  Warning: Module 'ietf-inet-types' not used
ietf-sr-policy-types@2018-07-01.yang:6.3: warning(1015): import not used

***
*** 0 Errors, 1 Warnings
 
ietf-sr-policy@2018-07-01.yang draft-raza-spring-sr-policy-yang-00.txt Email Authors Download the YANG model FAILED ietf-sr-policy@2018-07-01.yang:69: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
/home/bclaise/yang/modules/YANG/ietf-sr-policy-types@2018-07-01.yang:6: warning: imported module ietf-inet-types not used
./ietf-sr-policy-types@2018-07-01.yang:2: error: duplicate namespace 'urn:ietf:params:xml:ns:yang:ietf-sr-policy' found in module 'ietf-sr-policy'
Error: Module 'ietf-sr-policy-types' registering duplicate namespace 'urn:ietf:params:xml:ns:yang:ietf-sr-policy'
registered by module 'ietf-sr-policy'
Warning: Module 'ietf-inet-types' not used
ietf-sr-policy-types@2018-07-01.yang:6.3: warning(1015): import not used

Error: 'ietf-sr-policy@2018-07-01.yang' import of module 'ietf-sr-policy-types' failed
ietf-sr-policy@2018-07-01.yang:31.3: error(211): duplicate namespace

Error: typedef definition for 'sr-policy-types:segment-type' not found in module ietf-sr-policy-types
ietf-sr-policy@2018-07-01.yang:85.12: error(250): definition not found

Error: typedef definition for 'sr-policy-types:dataplane-type' not found in module ietf-sr-policy-types
ietf-sr-policy@2018-07-01.yang:298.14: error(250): definition not found

Error: typedef definition for 'sr-policy-types:sid-value-type' not found in module ietf-sr-policy-types
ietf-sr-policy@2018-07-01.yang:302.14: error(250): definition not found

Error: typedef definition for 'sr-policy-types:binding-sid-alloc-mode' not found in module ietf-sr-policy-types
ietf-sr-policy@2018-07-01.yang:331.12: error(250): definition not found

Error: typedef definition for 'sr-policy-types:sid-value-type' not found in module ietf-sr-policy-types
ietf-sr-policy@2018-07-01.yang:336.12: error(250): definition not found

Error: typedef definition for 'sr-policy-types:binding-sid-oper-state' not found in module ietf-sr-policy-types
ietf-sr-policy@2018-07-01.yang:341.12: error(250): definition not found

Error: typedef definition for 'sr-policy-types:dataplane-type' not found in module ietf-sr-policy-types
ietf-sr-policy@2018-07-01.yang:486.12: error(250): definition not found

Error: typedef definition for 'sr-policy-types:policy-admin-state' not found in module ietf-sr-policy-types
ietf-sr-policy@2018-07-01.yang:552.12: error(250): definition not found

Error: typedef definition for 'sr-policy-types:policy-oper-state' not found in module ietf-sr-policy-types
ietf-sr-policy@2018-07-01.yang:564.12: error(250): definition not found

Error: typedef definition for 'sr-policy-types:protocol-origin-type' not found in module ietf-sr-policy-types
ietf-sr-policy@2018-07-01.yang:620.16: error(250): definition not found

Error: typedef definition for 'sr-policy-types:policy-admin-state' not found in module ietf-sr-policy-types
ietf-sr-policy@2018-07-01.yang:691.16: error(250): definition not found

Error: typedef definition for 'sr-policy-types:explicit-binding-sid-rule-type' not found in module ietf-sr-policy-types
ietf-sr-policy@2018-07-01.yang:723.15: error(250): definition not found

Error: typedef definition for 'sr-policy-types:policy-oper-state' not found in module ietf-sr-policy-types
ietf-sr-policy@2018-07-01.yang:772.12: error(250): definition not found

Error: typedef definition for 'sr-policy-types:dataplane-type' not found in module ietf-sr-policy-types
ietf-sr-policy@2018-07-01.yang:917.11: error(250): definition not found

Error: typedef definition for 'sr-policy-types:sid-value-type' not found in module ietf-sr-policy-types
ietf-sr-policy@2018-07-01.yang:922.11: error(250): definition not found

Error: Module 'ietf-sr-policy-types' registering duplicate namespace 'urn:ietf:params:xml:ns:yang:ietf-sr-policy'
registered by module 'ietf-sr-policy'
Load module 'ietf-sr-policy-types' failed (duplicate namespace)
Error: failure importing module 'ietf-sr-policy-types'
ietf-sr-policy@2018-07-01.yang:519.7: error(211): duplicate namespace

Error: identityref has unknown base value (candidate-path-not-selected-reason)
ietf-sr-policy@2018-07-01.yang:519.7: error(211): duplicate namespace

Error: Module 'ietf-sr-policy-types' registering duplicate namespace 'urn:ietf:params:xml:ns:yang:ietf-sr-policy'
registered by module 'ietf-sr-policy'
Load module 'ietf-sr-policy-types' failed (duplicate namespace)
Error: failure importing module 'ietf-sr-policy-types'
ietf-sr-policy@2018-07-01.yang:777.7: error(211): duplicate namespace

Error: identityref has unknown base value (policy-down-reason)
ietf-sr-policy@2018-07-01.yang:777.7: error(211): duplicate namespace

Error: Module 'ietf-sr-policy-types' registering duplicate namespace 'urn:ietf:params:xml:ns:yang:ietf-sr-policy'
registered by module 'ietf-sr-policy'
Load module 'ietf-sr-policy-types' failed (duplicate namespace)
Error: failure importing module 'ietf-sr-policy-types'
ietf-sr-policy@2018-07-01.yang:852.6: error(211): duplicate namespace

Error: identityref has unknown base value (binding-sid-unavailable-reason)
ietf-sr-policy@2018-07-01.yang:852.6: error(211): duplicate namespace

Error: object 'protocol-origin' not found in module ietf-sr-policy in Xpath target protocol-origin
ietf-sr-policy@2018-07-01.yang:616.9: error(250): definition not found

Error: invalid identifier in key for list 'candidate-path' (protocol-origin)
ietf-sr-policy@2018-07-01.yang:616.9: error(250): definition not found

Error: object 'protocol-origin' not found in module ietf-sr-policy in Xpath target protocol-origin
ietf-sr-policy@2018-07-01.yang:615.7: error(250): definition not found

Error: invalid identifier in key for list 'candidate-path' (protocol-origin)
ietf-sr-policy@2018-07-01.yang:615.7: error(250): definition not found

Error: object 'protocol-origin' not found in module ietf-sr-policy in Xpath target protocol-origin
ietf-sr-policy@2018-07-01.yang:615.7: error(250): definition not found

Error: invalid identifier in key for list 'candidate-path' (protocol-origin)
ietf-sr-policy@2018-07-01.yang:615.7: error(250): definition not found

Error: object 'protocol-origin' not found in module ietf-sr-policy in Xpath target protocol-origin
ietf-sr-policy@2018-07-01.yang:615.7: error(250): definition not found

Error: invalid identifier in key for list 'candidate-path' (protocol-origin)
ietf-sr-policy@2018-07-01.yang:615.7: error(250): definition not found

Error: object not found 'ietf-sr-policy:value'
ietf-sr-policy@2018-07-01.yang:846.154: error(250): definition not found

Error: object not found 'ietf-sr-policy:protocol-origin'
ietf-sr-policy@2018-07-01.yang:880.188: error(250): definition not found

Error: object not found 'ietf-sr-policy:dataplane'
ietf-sr-policy@2018-07-01.yang:894.214: error(250): definition not found

Error: object not found 'ietf-sr-policy:value'
ietf-sr-policy@2018-07-01.yang:901.214: error(250): definition not found

***
*** 34 Errors, 0 Warnings
err : No resolvents found for leafref "/ietf-routing:routing/ietf-sr-policy:segment-routing/ietf-sr-policy:sr-policy/ietf-sr-policy:policies/ietf-sr-policy:policy/ietf-sr-policy:candidate-paths/ietf-sr-policy:candidate-path/ietf-sr-policy:binding-sid/ietf-sr-policy:dataplane". (/ietf-sr-policy:sr-policy-candidate-path-binding-sid-mismatch-event/existing-candidate-path-binding-sid-dataplane-ref)
err : Leafref is not conditional based on "capability-candidate-path-binding-sid" feature as its target. (/ietf-sr-policy:sr-policy-candidate-path-binding-sid-mismatch-event/existing-candidate-path-binding-sid-dataplane-ref)
err : Module "ietf-sr-policy" parsing failed.
ietf-sr-topology-state@2019-03-09.yang draft-ietf-teas-yang-sr-te-topo-04.txt Email Authors Download the YANG model PASSED          
ietf-sr-topology@2019-03-09.yang draft-ietf-teas-yang-sr-te-topo-04.txt Email Authors Download the YANG model PASSED          
ietf-srv6-base@2018-10-22.yang draft-raza-spring-srv6-yang-03.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-srv6-base@2018-10-22.yang:92: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-srv6-static@2018-10-22.yang draft-raza-spring-srv6-yang-03.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-srv6-static@2018-10-22.yang:90: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
    Warning: compare value 'End' invalid for object 'ietf-srv6-static:end-behavior-type type:identityref'
XPath:../end-behavior-type = 'End'
ietf-srv6-static@2018-10-22.yang: line 248: warning(1052): XPath compare value invalid for YANG type

Warning: compare value 'End_PSP' invalid for object 'ietf-srv6-static:end-behavior-type type:identityref'
XPath:../end-behavior-type = 'End_PSP'
ietf-srv6-static@2018-10-22.yang: line 263: warning(1052): XPath compare value invalid for YANG type

Warning: compare value 'End_USP' invalid for object 'ietf-srv6-static:end-behavior-type type:identityref'
XPath:../end-behavior-type = 'End_USP'
ietf-srv6-static@2018-10-22.yang: line 278: warning(1052): XPath compare value invalid for YANG type

Warning: compare value 'End_PSP_USP' invalid for object 'ietf-srv6-static:end-behavior-type type:identityref'
XPath:../end-behavior-type = 'End_PSP_USP'
ietf-srv6-static@2018-10-22.yang: line 293: warning(1052): XPath compare value invalid for YANG type

Warning: compare value 'End.T' invalid for object 'ietf-srv6-static:end-behavior-type type:identityref'
XPath:../end-behavior-type = 'End.T'
ietf-srv6-static@2018-10-22.yang: line 308: warning(1052): XPath compare value invalid for YANG type

Warning: compare value 'End.T_PSP' invalid for object 'ietf-srv6-static:end-behavior-type type:identityref'
XPath:../end-behavior-type = 'End.T_PSP'
ietf-srv6-static@2018-10-22.yang: line 331: warning(1052): XPath compare value invalid for YANG type

Warning: compare value 'End.T_USP' invalid for object 'ietf-srv6-static:end-behavior-type type:identityref'
XPath:../end-behavior-type = 'End.T_USP'
ietf-srv6-static@2018-10-22.yang: line 355: warning(1052): XPath compare value invalid for YANG type

Warning: compare value 'End.T_PSP_USP' invalid for object 'ietf-srv6-static:end-behavior-type type:identityref'
XPath:../end-behavior-type = 'End.T_PSP_USP'
ietf-srv6-static@2018-10-22.yang: line 379: warning(1052): XPath compare value invalid for YANG type

Warning: compare value 'End.X' invalid for object 'ietf-srv6-static:end-behavior-type type:identityref'
XPath:../end-behavior-type = 'End.X'
ietf-srv6-static@2018-10-22.yang: line 403: warning(1052): XPath compare value invalid for YANG type

Warning: compare value 'End.X_PSP' invalid for object 'ietf-srv6-static:end-behavior-type type:identityref'
XPath:../end-behavior-type = 'End.X_PSP'
ietf-srv6-static@2018-10-22.yang: line 425: warning(1052): XPath compare value invalid for YANG type

Warning: compare value 'End.X_USP' invalid for object 'ietf-srv6-static:end-behavior-type type:identityref'
XPath:../end-behavior-type = 'End.X_USP'
ietf-srv6-static@2018-10-22.yang: line 446: warning(1052): XPath compare value invalid for YANG type

Warning: compare value 'End.X_PSP_USP' invalid for object 'ietf-srv6-static:end-behavior-type type:identityref'
XPath:../end-behavior-type = 'End.X_PSP_USP'
ietf-srv6-static@2018-10-22.yang: line 468: warning(1052): XPath compare value invalid for YANG type

Warning: compare value 'End.B6' invalid for object 'ietf-srv6-static:end-behavior-type type:identityref'
XPath:../end-behavior-type = 'End.B6'
ietf-srv6-static@2018-10-22.yang: line 490: warning(1052): XPath compare value invalid for YANG type

Warning: compare value 'End.B6.Encaps' invalid for object 'ietf-srv6-static:end-behavior-type type:identityref'
XPath:../end-behavior-type = 'End.B6.Encaps'
ietf-srv6-static@2018-10-22.yang: line 513: warning(1052): XPath compare value invalid for YANG type

Warning: compare value 'End.BM' invalid for object 'ietf-srv6-static:end-behavior-type type:identityref'
XPath:../end-behavior-type = 'End.BM'
ietf-srv6-static@2018-10-22.yang: line 547: warning(1052): XPath compare value invalid for YANG type

Warning: compare value 'End.DX6' invalid for object 'ietf-srv6-static:end-behavior-type type:identityref'
XPath:../end-behavior-type = 'End.DX6'
ietf-srv6-static@2018-10-22.yang: line 570: warning(1052): XPath compare value invalid for YANG type

Warning: compare value 'End.DX4' invalid for object 'ietf-srv6-static:end-behavior-type type:identityref'
XPath:../end-behavior-type = 'End.DX4'
ietf-srv6-static@2018-10-22.yang: line 585: warning(1052): XPath compare value invalid for YANG type

Warning: compare value 'End.DT6' invalid for object 'ietf-srv6-static:end-behavior-type type:identityref'
XPath:../end-behavior-type = 'End.DT6'
ietf-srv6-static@2018-10-22.yang: line 602: warning(1052): XPath compare value invalid for YANG type

Warning: compare value 'End.DT4' invalid for object 'ietf-srv6-static:end-behavior-type type:identityref'
XPath:../end-behavior-type = 'End.DT4'
ietf-srv6-static@2018-10-22.yang: line 625: warning(1052): XPath compare value invalid for YANG type

Warning: compare value 'End.DT46' invalid for object 'ietf-srv6-static:end-behavior-type type:identityref'
XPath:../end-behavior-type = 'End.DT46'
ietf-srv6-static@2018-10-22.yang: line 649: warning(1052): XPath compare value invalid for YANG type

Warning: compare value 'End.DX2' invalid for object 'ietf-srv6-static:end-behavior-type type:identityref'
XPath:../end-behavior-type = 'End.DX2'
ietf-srv6-static@2018-10-22.yang: line 678: warning(1052): XPath compare value invalid for YANG type

Warning: compare value 'End.OTP' invalid for object 'ietf-srv6-static:end-behavior-type type:identityref'
XPath:../end-behavior-type = 'End.OTP'
ietf-srv6-static@2018-10-22.yang: line 764: warning(1052): XPath compare value invalid for YANG type

***
*** 0 Errors, 22 Warnings
warn: Identityref "end-behavior-type" comparison with identity "End" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End'".
warn: Failed to resolve identityref "End". (/ietf-srv6-static:end-behavior-type)
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End'".
warn: Identityref "end-behavior-type" comparison with identity "End_PSP" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End_PSP'".
warn: Failed to resolve identityref "End_PSP". (/ietf-srv6-static:end-behavior-type)
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End_PSP'".
warn: Identityref "end-behavior-type" comparison with identity "End_USP" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End_USP'".
warn: Failed to resolve identityref "End_USP". (/ietf-srv6-static:end-behavior-type)
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End_USP'".
warn: Identityref "end-behavior-type" comparison with identity "End_PSP_USP" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End_PSP_USP'".
warn: Failed to resolve identityref "End_PSP_USP". (/ietf-srv6-static:end-behavior-type)
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End_PSP_USP'".
warn: Identityref "end-behavior-type" comparison with identity "End.T" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.T'".
warn: Failed to resolve identityref "End.T". (/ietf-srv6-static:end-behavior-type)
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.T'".
warn: Identityref "end-behavior-type" comparison with identity "End.T_PSP" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.T_PSP'".
warn: Failed to resolve identityref "End.T_PSP". (/ietf-srv6-static:end-behavior-type)
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.T_PSP'".
warn: Identityref "end-behavior-type" comparison with identity "End.T_USP" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.T_USP'".
warn: Failed to resolve identityref "End.T_USP". (/ietf-srv6-static:end-behavior-type)
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.T_USP'".
warn: Identityref "end-behavior-type" comparison with identity "End.T_PSP_USP" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.T_PSP_USP'".
warn: Failed to resolve identityref "End.T_PSP_USP". (/ietf-srv6-static:end-behavior-type)
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.T_PSP_USP'".
warn: Identityref "end-behavior-type" comparison with identity "End.X" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.X'".
warn: Failed to resolve identityref "End.X". (/ietf-srv6-static:end-behavior-type)
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.X'".
warn: Identityref "end-behavior-type" comparison with identity "End.X_PSP" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.X_PSP'".
warn: Failed to resolve identityref "End.X_PSP". (/ietf-srv6-static:end-behavior-type)
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.X_PSP'".
warn: Identityref "end-behavior-type" comparison with identity "End.X_USP" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.X_USP'".
warn: Failed to resolve identityref "End.X_USP". (/ietf-srv6-static:end-behavior-type)
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.X_USP'".
warn: Identityref "end-behavior-type" comparison with identity "End.X_PSP_USP" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.X_PSP_USP'".
warn: Failed to resolve identityref "End.X_PSP_USP". (/ietf-srv6-static:end-behavior-type)
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.X_PSP_USP'".
warn: Identityref "end-behavior-type" comparison with identity "End.B6" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.B6'".
warn: Failed to resolve identityref "End.B6". (/ietf-srv6-static:end-behavior-type)
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.B6'".
warn: Identityref "end-behavior-type" comparison with identity "End.B6.Encaps" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.B6.Encaps'".
warn: Failed to resolve identityref "End.B6.Encaps". (/ietf-srv6-static:end-behavior-type)
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.B6.Encaps'".
warn: Identityref "end-behavior-type" comparison with identity "End.BM" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.BM'".
warn: Failed to resolve identityref "End.BM". (/ietf-srv6-static:end-behavior-type)
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.BM'".
warn: Identityref "end-behavior-type" comparison with identity "End.DX6" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.DX6'".
warn: Failed to resolve identityref "End.DX6". (/ietf-srv6-static:end-behavior-type)
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.DX6'".
warn: Identityref "end-behavior-type" comparison with identity "End.DX4" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.DX4'".
warn: Failed to resolve identityref "End.DX4". (/ietf-srv6-static:end-behavior-type)
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.DX4'".
warn: Identityref "end-behavior-type" comparison with identity "End.DT6" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.DT6'".
warn: Failed to resolve identityref "End.DT6". (/ietf-srv6-static:end-behavior-type)
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.DT6'".
warn: Identityref "end-behavior-type" comparison with identity "End.DT4" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.DT4'".
warn: Failed to resolve identityref "End.DT4". (/ietf-srv6-static:end-behavior-type)
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.DT4'".
warn: Identityref "end-behavior-type" comparison with identity "End.DT46" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.DT46'".
warn: Failed to resolve identityref "End.DT46". (/ietf-srv6-static:end-behavior-type)
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.DT46'".
warn: Identityref "end-behavior-type" comparison with identity "End.DX2" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.DX2'".
warn: Failed to resolve identityref "End.DX2". (/ietf-srv6-static:end-behavior-type)
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.DX2'".
warn: Identityref "end-behavior-type" comparison with identity "End.OTP" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.OTP'".
warn: Failed to resolve identityref "End.OTP". (/ietf-srv6-static:end-behavior-type)
warn: Previous warning generated by XPath subexpression[3] "end-behavior-type = 'End.OTP'".
ietf-srv6-types@2018-10-22.yang draft-raza-spring-srv6-yang-03.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-srv6-types@2018-10-22.yang:64: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-ssh-client@2019-06-07.yang draft-ietf-netconf-ssh-client-server-14.txt Email Authors Download the YANG model PASSED          
ietf-ssh-common@2019-06-07.yang draft-ietf-netconf-ssh-client-server-14.txt Email Authors Download the YANG model PASSED          
ietf-ssh-server@2019-06-07.yang draft-ietf-netconf-ssh-client-server-14.txt Email Authors Download the YANG model PASSED          
ietf-stamp@2018-09-07.yang draft-ietf-ippm-stamp-yang-03.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-stamp@2018-09-07.yang:53: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-stamp@2018-09-07.yang:575: 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-subscribed-notifications@2019-05-06.yang draft-ietf-netconf-subscribed-notifications-26.txt Email Authors Download the YANG model FAILED ietf-subscribed-notifications@2019-05-06.yang:634: 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).
      err : The leafref leaf is config but refers to a non-config leaf. (/ietf-subscribed-notifications:subscriptions/subscription/target/stream/stream)
err : Invalid value "subscription-policy" of "uses". (/ietf-subscribed-notifications:subscriptions/subscription/subscription-policy)
err : Copying data from grouping failed. (/ietf-subscribed-notifications:subscriptions/subscription/subscription-policy)
err : Module "ietf-subscribed-notifications" parsing failed.
ietf-syslog@2018-03-15.yang draft-ietf-netmod-syslog-model-26.txt Email Authors Download the YANG model FAILED ietf-syslog@2018-03-15.yang:67: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-syslog@2018-03-15.yang:67: 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-syslog@2018-03-15.yang:761: error: grouping "private-key-grouping" not found in module ietf-keystore
ietf-syslog@2018-03-15.yang:762: error: grouping "certificate-grouping" not found in module ietf-keystore
ietf-syslog@2018-03-15.yang:761: error: grouping "private-key-grouping" not found in module ietf-keystore
ietf-syslog@2018-03-15.yang:762: error: grouping "certificate-grouping" not found in module ietf-keystore
ietf-syslog@2018-03-15.yang:761: error: grouping 'private-key-grouping' in module 'ietf-keystore' not found
ietf-syslog@2018-03-15.yang:762: error: grouping 'certificate-grouping' in module 'ietf-keystore' not found
Error: grouping definition for 'ks:private-key-grouping' not found in module ietf-keystore
ietf-syslog@2018-03-15.yang:761.19: error(250): definition not found

Error: grouping definition for 'ks:certificate-grouping' not found in module ietf-keystore
ietf-syslog@2018-03-15.yang:762.19: error(250): definition not found

Error: grouping 'private-key-grouping' not found
ietf-syslog@2018-03-15.yang:761.19: error(250): definition not found

Error: grouping 'certificate-grouping' not found
ietf-syslog@2018-03-15.yang:762.19: error(250): definition not found

***
*** 4 Errors, 0 Warnings
err : Failed to resolve uses "ks:private-key-grouping". (/ietf-syslog:syslog/actions/remote/destination/signing/cert-signers/cert-signer/cert/ks:private-key-grouping)
err : Failed to resolve uses "ks:certificate-grouping". (/ietf-syslog:syslog/actions/remote/destination/signing/cert-signers/cert-signer/cert/ks:certificate-grouping)
err : Module "ietf-syslog" parsing failed.
ietf-system-aaa@2019-03-06.yang draft-zheng-opsawg-tacacs-yang-01.txt Email Authors Download the YANG model PASSED          
ietf-taps-api@2019-03-09.yang draft-jholland-taps-api-yang-02.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-taps-api@2019-03-09.yang:44: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-tcp-client@2019-04-29.yang draft-kwatsen-netconf-tcp-client-server-02.txt Email Authors Download the YANG model PASSED          
ietf-tcp-client@2019-06-07.yang draft-ietf-netconf-tcp-client-server-01.txt Email Authors Download the YANG model PASSED          
ietf-tcp-common@2019-04-29.yang draft-kwatsen-netconf-tcp-client-server-02.txt Email Authors Download the YANG model PASSED          
ietf-tcp-common@2019-06-07.yang draft-ietf-netconf-tcp-client-server-01.txt Email Authors Download the YANG model PASSED          
ietf-tcp-server@2019-04-29.yang draft-kwatsen-netconf-tcp-client-server-02.txt Email Authors Download the YANG model PASSED          
ietf-tcp-server@2019-06-07.yang draft-ietf-netconf-tcp-client-server-01.txt Email Authors Download the YANG model PASSED          
ietf-te-device@2019-04-09.yang draft-ietf-teas-yang-te-21.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-te-device@2019-04-09.yang:72: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
  ./ietf-te@2019-04-09.yang:109: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:109) is converted to 'string' when part of a union
./ietf-te@2019-04-09.yang:113: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:113) is converted to 'string' when part of a union
   
ietf-te-kpi-telemetry@2019-04-18.yang draft-lee-teas-actn-pm-telemetry-autonomics-17.txt Email Authors Download the YANG model PASSED WITH WARNINGS     ./ietf-te@2019-04-09.yang:109: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:109) is converted to 'string' when part of a union
./ietf-te@2019-04-09.yang:113: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:113) is converted to 'string' when part of a union
   
ietf-te-mpls@2019-02-23.yang draft-ietf-teas-yang-te-mpls-01.txt Email Authors Download the YANG model PASSED WITH WARNINGS     ./ietf-te@2019-04-09.yang:109: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:109) is converted to 'string' when part of a union
./ietf-te@2019-04-09.yang:113: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:113) is converted to 'string' when part of a union
  warn: Identityref "block-allocation-mode" comparison with identity "label-block-alloc-mode-manager" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[6] "block-allocation-mode = 'label-block-alloc-mode-manager'".
warn: Identityref "block-allocation-mode" comparison with identity "label-block-alloc-mode-manager" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
warn: Previous warning generated by XPath subexpression[6] "block-allocation-mode = 'label-block-alloc-mode-manager'".
ietf-te-packet-types@2019-04-09.yang draft-ietf-teas-yang-te-types-09.txt Email Authors Download the YANG model PASSED          
ietf-te-path-computation@2019-03-11.yang draft-ietf-teas-yang-path-computation-05.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-te-path-computation@2019-03-11.yang:35: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
  ./ietf-te@2019-04-09.yang:109: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:109) is converted to 'string' when part of a union
./ietf-te@2019-04-09.yang:113: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:113) is converted to 'string' when part of a union
   
ietf-te-service-mapping-types@2019-03-05.yang draft-ietf-teas-te-service-mapping-yang-01.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-te-service-mapping-types@2019-03-05.yang:33: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
  ./ietf-te@2019-04-09.yang:109: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:109) is converted to 'string' when part of a union
./ietf-te@2019-04-09.yang:113: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:113) is converted to 'string' when part of a union
   
ietf-te-topology-packet-state@2019-02-28.yang draft-ietf-teas-yang-l3-te-topo-04.txt Email Authors Download the YANG model PASSED          
ietf-te-topology-packet@2019-02-28.yang draft-ietf-teas-yang-l3-te-topo-04.txt Email Authors Download the YANG model PASSED          
ietf-te-topology-sf-state@2018-02-27.yang draft-ietf-teas-sf-aware-topo-model-03.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-te-topology-sf-state@2018-02-27.yang:49: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-te-topology-sf@2018-02-27.yang draft-ietf-teas-sf-aware-topo-model-03.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-te-topology-sf@2018-02-27.yang:44: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-te-topology-state@2019-02-07.yang draft-ietf-teas-yang-te-topo-21.txt Email Authors Download the YANG model PASSED          
ietf-te-topology@2019-02-07.yang draft-ietf-teas-yang-te-topo-21.txt Email Authors Download the YANG model PASSED          
ietf-te-types@2019-04-09.yang draft-ietf-teas-yang-te-types-09.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-te-types@2019-04-09.yang:331: 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-te@2019-04-09.yang draft-ietf-teas-yang-te-21.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-te@2019-04-09.yang:59: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
  ietf-te@2019-04-09.yang:109: warning: the type leafref (defined at ietf-te@2019-04-09.yang:109) is converted to 'string' when part of a union
ietf-te@2019-04-09.yang:113: warning: the type leafref (defined at ietf-te@2019-04-09.yang:113) is converted to 'string' when part of a union
   
ietf-tls-client@2019-06-07.yang draft-ietf-netconf-tls-client-server-13.txt Email Authors Download the YANG model PASSED          
ietf-tls-common@2019-06-07.yang draft-ietf-netconf-tls-client-server-13.txt Email Authors Download the YANG model PASSED          
ietf-tls-server@2019-06-07.yang draft-ietf-netconf-tls-client-server-13.txt Email Authors Download the YANG model PASSED          
ietf-traffic-analyzer@2019-03-09.yang draft-vassilev-bmwg-network-interconnect-tester-00.txt Email Authors Download the YANG model FAILED ietf-traffic-analyzer@2019-03-09.yang:72: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:76: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:77: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:80: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:83: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:84: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:87: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:90: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:93: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:94: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:97: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:98: error: keyword "units" not in canonical order,expected "type" (see RFC 6020, Section 12)
ietf-traffic-analyzer@2019-03-09.yang:99: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
ietf-traffic-analyzer@2019-03-09.yang:101: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:102: error: keyword "units" not in canonical order,expected "type" (see RFC 6020, Section 12)
ietf-traffic-analyzer@2019-03-09.yang:103: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
ietf-traffic-analyzer@2019-03-09.yang:108: error: keyword "description" not in canonical order,expected "type" (see RFC 6020, Section 12)
ietf-traffic-analyzer@2019-03-09.yang:109: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
ietf-traffic-analyzer@2019-03-09.yang:110: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
ietf-traffic-analyzer@2019-03-09.yang:112: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:113: error: keyword "units" not in canonical order,expected "type" (see RFC 6020, Section 12)
ietf-traffic-analyzer@2019-03-09.yang:114: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
ietf-traffic-analyzer@2019-03-09.yang:120: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:121: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:123: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:125: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:128: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:131: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:134: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:137: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:146: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:147: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:152: error: keyword "if-feature" not in canonical order (see RFC 6020, Section 12)
ietf-traffic-analyzer@2019-03-09.yang:153: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:154: error: keyword "mandatory" not in canonical order,expected "type" (see RFC 6020, Section 12)
ietf-traffic-analyzer@2019-03-09.yang:155: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
ietf-traffic-analyzer@2019-03-09.yang:162: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:163: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:167: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:173: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:177: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-traffic-analyzer@2019-03-09.yang:184: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
       
ietf-traffic-generator@2019-03-09.yang draft-vassilev-bmwg-network-interconnect-tester-00.txt Email Authors Download the YANG model FAILED ietf-traffic-generator@2019-03-09.yang:12: warning: imported module iana-if-type not used
ietf-traffic-generator@2019-03-09.yang:73: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
ietf-traffic-generator@2019-03-09.yang:95: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
ietf-traffic-generator@2019-03-09.yang:97: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement
ietf-traffic-generator@2019-03-09.yang:131: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
ietf-traffic-generator@2019-03-09.yang:146: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
ietf-traffic-generator@2019-03-09.yang:147: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-traffic-generator@2019-03-09.yang:148: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
ietf-traffic-generator@2019-03-09.yang:161: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
ietf-traffic-generator@2019-03-09.yang:167: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
ietf-traffic-generator@2019-03-09.yang:173: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
ietf-traffic-generator@2019-03-09.yang:174: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-traffic-generator@2019-03-09.yang:176: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement
ietf-traffic-generator@2019-03-09.yang:191: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-traffic-generator@2019-03-09.yang:193: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement
ietf-traffic-generator@2019-03-09.yang:236: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
ietf-traffic-generator@2019-03-09.yang:237: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-traffic-generator@2019-03-09.yang:240: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-traffic-generator@2019-03-09.yang:250: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement
ietf-traffic-generator@2019-03-09.yang:252: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
ietf-traffic-generator@2019-03-09.yang:254: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-traffic-generator@2019-03-09.yang:294: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
ietf-traffic-generator@2019-03-09.yang:296: error: keyword "when" not in canonical order (see RFC 6020, Section 12)
ietf-traffic-generator@2019-03-09.yang:303: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
ietf-traffic-generator@2019-03-09.yang:305: error: keyword "when" not in canonical order (see RFC 6020, Section 12)
ietf-traffic-generator@2019-03-09.yang:312: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
ietf-traffic-generator@2019-03-09.yang:314: error: keyword "when" not in canonical order (see RFC 6020, Section 12)
ietf-traffic-generator@2019-03-09.yang:321: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
ietf-traffic-generator@2019-03-09.yang:323: error: keyword "when" not in canonical order (see RFC 6020, Section 12)
ietf-traffic-generator@2019-03-09.yang:12: warning: imported module iana-if-type not used
     
ietf-trafficselector-types@2018-05-17.yang draft-ietf-dmm-fpc-yang-00.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-trafficselector-types@2018-05-17.yang:48: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-trans-client-service@2019-03-27.yang draft-zheng-ccamp-client-signal-yang-07.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-trans-client-service@2019-03-27.yang:51: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-truststore@2019-06-07.yang draft-ietf-netconf-trust-anchors-05.txt Email Authors Download the YANG model PASSED          
ietf-tunnel-steering@2019-02-15.yang draft-bryskin-teas-service-tunnel-steering-model-02.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-tunnel-steering@2019-02-15.yang:50: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-twamp@2018-07-02.yang draft-ietf-ippm-twamp-yang-13.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-twamp@2018-07-02.yang:52: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-twamp@2018-07-02.yang:386: 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-upc-subscribed-notifications@2018-10-19.yang draft-ietf-netconf-udp-pub-channel-05.txt Email Authors Download the YANG model FAILED         err : The leafref leaf is config but refers to a non-config leaf. (/ietf-subscribed-notifications:subscriptions/subscription/target/stream/stream)
err : Invalid value "subscription-policy" of "uses". (/ietf-subscribed-notifications:subscriptions/subscription/subscription-policy)
err : Copying data from grouping failed. (/ietf-subscribed-notifications:subscriptions/subscription/subscription-policy)
err : Module "ietf-subscribed-notifications" parsing failed.
err : Importing "ietf-subscribed-notifications" module into "ietf-upc-subscribed-notifications" failed.
err : Module "ietf-upc-subscribed-notifications" parsing failed.
ietf-vbng-cp@2019-03-08.yang draft-cuspdt-rtgwg-cu-separation-yang-model-03.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-vbng-cp@2019-03-08.yang:9: warning: imported module ietf-interfaces not used
ietf-vbng-cp@2019-03-08.yang:30: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-vbng-cp@2019-03-08.yang:9: warning: imported module ietf-interfaces not used
  Warning: Module 'ietf-interfaces' not used
ietf-vbng-cp@2019-03-08.yang:9.1: warning(1015): import not used

***
*** 0 Errors, 1 Warnings
 
ietf-vbng-up@2019-03-08.yang draft-cuspdt-rtgwg-cu-separation-yang-model-03.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-vbng-up@2019-03-08.yang:26: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-vbng@2019-03-08.yang draft-cuspdt-rtgwg-cu-separation-yang-model-03.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-vbng@2019-03-08.yang:28: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-vn-kpi-telemetry@2019-04-18.yang draft-lee-teas-actn-pm-telemetry-autonomics-17.txt Email Authors Download the YANG model PASSED WITH WARNINGS     ./ietf-te@2019-04-09.yang:109: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:109) is converted to 'string' when part of a union
./ietf-te@2019-04-09.yang:113: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:113) is converted to 'string' when part of a union
   
ietf-vn@2019-02-04.yang draft-ietf-teas-actn-vn-yang-04.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-vn@2019-02-04.yang:31: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-voucher-request@2018-02-14.yang draft-ietf-anima-bootstrapping-keyinfra-20.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-voucher-request@2018-02-14.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-vysm@2018-07-01.yang draft-shytyi-netmod-vysm-01.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-vysm@2018-07-01.yang:11: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-wson-topology@2019-02-27.yang draft-ietf-ccamp-wson-yang-21.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-wson-topology@2019-02-27.yang:67: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-wson-tunnel@2019-03-06.yang draft-ietf-ccamp-wson-tunnel-model-03.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-wson-tunnel@2019-03-06.yang:30: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
  ./ietf-te@2019-04-09.yang:109: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:109) is converted to 'string' when part of a union
./ietf-te@2019-04-09.yang:113: warning: the type leafref (defined at ./ietf-te@2019-04-09.yang:113) is converted to 'string' when part of a union
   
ietf-yang-instance-data@2019-02-20.yang draft-ietf-netmod-yang-instance-file-format-02.txt Email Authors Download the YANG model FAILED ietf-yang-instance-data@2019-02-20.yang:7: error: module "ietf-yang-data-ext" not found in search path
ietf-yang-instance-data@2019-02-20.yang:21: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-yang-instance-data@2019-02-20.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-yang-instance-data@2019-02-20.yang:92: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-yang-instance-data@2019-02-20.yang:139: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
ietf-yang-instance-data@2019-02-20.yang:7: error: module "ietf-yang-data-ext" not found in search path
ietf-yang-instance-data@2019-02-20.yang:7: error: module 'ietf-yang-data-ext' not found
Error: 'ietf-yang-instance-data@2019-02-20.yang' import of module 'ietf-yang-data-ext' failed
ietf-yang-instance-data@2019-02-20.yang:7.3: error(236): module not found

Load module 'ietf-yang-data-ext' failed (module not found)
Error: failure importing module 'ietf-yang-data-ext'
ietf-yang-instance-data@2019-02-20.yang:28.3: error(236): module not found

Warning: Module 'ietf-datastores' not used
ietf-yang-instance-data@2019-02-20.yang:8.3: warning(1015): import not used

Warning: Module 'ietf-inet-types' not used
ietf-yang-instance-data@2019-02-20.yang:9.3: warning(1015): import not used

Warning: Module 'ietf-yang-types' not used
ietf-yang-instance-data@2019-02-20.yang:10.3: warning(1015): import not used

***
*** 2 Errors, 3 Warnings
err : Data model "ietf-yang-data-ext" not found.
err : Importing "ietf-yang-data-ext" module into "ietf-yang-instance-data" failed.
err : Module "ietf-yang-instance-data" parsing failed.
ietf-yang-library-packages@2018-11-26.yang draft-rwilton-netmod-yang-packages-01.txt Email Authors Download the YANG model FAILED ietf-yang-library-packages@2018-11-26.yang:62: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
      warn: Missing status in deprecated subtree (/ietf-yang-library:{grouping}[module-list]/{grouping}[schema-leaf]/schema), inheriting.
ietf-yang-package-types@2018-11-26.yang draft-rwilton-netmod-yang-packages-01.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-yang-package-types@2018-11-26.yang:124: 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).
      warn: Missing status in deprecated subtree (/ietf-yang-library:{grouping}[module-list]/{grouping}[schema-leaf]/schema), inheriting.
ietf-yang-package@2018-11-26.yang draft-rwilton-netmod-yang-packages-01.txt Email Authors Download the YANG model PASSED WITH WARNINGS         warn: Missing status in deprecated subtree (/ietf-yang-library:{grouping}[module-list]/{grouping}[schema-leaf]/schema), inheriting.
ietf-yang-push-ext@2019-02-01.yang draft-ranade-netmod-yang-push-extension-02.txt Email Authors Download the YANG model FAILED ietf-yang-push-ext@2019-02-01.yang:14: warning: imported module ietf-datastores not used
ietf-yang-push-ext@2019-02-01.yang:51: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
ietf-yang-push-ext@2019-02-01.yang:51: 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-yang-push-ext@2019-02-01.yang:14: warning: imported module ietf-datastores not used
    err : The leafref leaf is config but refers to a non-config leaf. (/ietf-subscribed-notifications:subscriptions/subscription/target/stream/stream)
err : Invalid value "subscription-policy" of "uses". (/ietf-subscribed-notifications:subscriptions/subscription/subscription-policy)
err : Copying data from grouping failed. (/ietf-subscribed-notifications:subscriptions/subscription/subscription-policy)
err : Module "ietf-subscribed-notifications" parsing failed.
err : Importing "ietf-subscribed-notifications" module into "ietf-yang-push-ext" failed.
err : Module "ietf-yang-push-ext" parsing failed.
ietf-yang-push@2019-05-21.yang draft-ietf-netconf-yang-push-25.txt Email Authors Download the YANG model FAILED         err : The leafref leaf is config but refers to a non-config leaf. (/ietf-subscribed-notifications:subscriptions/subscription/target/stream/stream)
err : Invalid value "subscription-policy" of "uses". (/ietf-subscribed-notifications:subscriptions/subscription/subscription-policy)
err : Copying data from grouping failed. (/ietf-subscribed-notifications:subscriptions/subscription/subscription-policy)
err : Module "ietf-subscribed-notifications" parsing failed.
err : Importing "ietf-subscribed-notifications" module into "ietf-yang-push" failed.
err : Module "ietf-yang-push" parsing failed.
ietf-yang-structure-ext@2019-03-07.yang draft-ietf-netmod-yang-data-ext-03.txt Email Authors Download the YANG model PASSED WITH WARNINGS ietf-yang-structure-ext@2019-03-07.yang:38: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing (see pyang --ietf-help for details).
       
ietf-yang-types@2019-03-11.yang draft-schoenw-netmod-rfc6991-bis-01.txt Email Authors Download the YANG model PASSED