Started by GitLab push by pingj
Lightweight checkout support not available, falling back to full checkout.
Checking out git git@forge.etsi.org:forge-tools/3gpp-scripts.git into /var/lib/jenkins/jobs/3GPP/jobs/sa5-data-models-any-commit/workspace@script to read sa5-data-models-validation.jenkinsfile
using credential f9a9fd70-ea8b-4872-a9d5-d1fb1cf8123e
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url git@forge.etsi.org:forge-tools/3gpp-scripts.git # timeout=10
Fetching upstream changes from git@forge.etsi.org:forge-tools/3gpp-scripts.git
> git --version # timeout=10
using GIT_SSH to set credentials
> git fetch --tags --progress git@forge.etsi.org:forge-tools/3gpp-scripts.git +refs/heads/*:refs/remotes/origin/*
skipping resolution of commit remotes/origin/test-branch-pj-0629, since it originates from another repository
Seen branch in repository origin/master
Seen branch in repository origin/tags
Seen 2 remote branches
> git show-ref --tags -d # timeout=10
Checking out Revision b28df74c4b3f0a4444fc9fadb37027cfcde1972a (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f b28df74c4b3f0a4444fc9fadb37027cfcde1972a
Commit message: "Add Jenkinsfile for LI"
> git rev-list --no-walk db01b2373d435fd24e0ceaf1b1ff192d5c94c176 # timeout=10
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] node
Running on build.forge.etsi.org in /home/jenkins/workspace/3GPP/sa5-data-models-any-commit
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
using credential f9a9fd70-ea8b-4872-a9d5-d1fb1cf8123e
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url git@forge.etsi.org:forge-tools/3gpp-scripts.git # timeout=10
Fetching upstream changes from git@forge.etsi.org:forge-tools/3gpp-scripts.git
> git --version # timeout=10
using GIT_SSH to set credentials
> git fetch --tags --progress git@forge.etsi.org:forge-tools/3gpp-scripts.git +refs/heads/*:refs/remotes/origin/*
skipping resolution of commit remotes/origin/test-branch-pj-0629, since it originates from another repository
Seen branch in repository origin/master
Seen branch in repository origin/tags
Seen 2 remote branches
> git show-ref --tags -d # timeout=10
Checking out Revision b28df74c4b3f0a4444fc9fadb37027cfcde1972a (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f b28df74c4b3f0a4444fc9fadb37027cfcde1972a
Commit message: "Add Jenkinsfile for LI"
[Pipeline] }
[Pipeline] // stage
[Pipeline] withEnv
[Pipeline] {
[Pipeline] withEnv
[Pipeline] {
[Pipeline] gitlabBuilds
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Resolve)
[Pipeline] sh
+ echo Resolve stage
Resolve stage
[Pipeline] updateGitlabCommitStatus
[Pipeline] dir
Running in /home/jenkins/workspace/3GPP/sa5-data-models-any-commit/data-models
[Pipeline] {
[Pipeline] checkout
using credential f9a9fd70-ea8b-4872-a9d5-d1fb1cf8123e
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url git@forge.etsi.org:3GPP/SA5/data-models.git # timeout=10
Fetching upstream changes from git@forge.etsi.org:3GPP/SA5/data-models.git
> git --version # timeout=10
using GIT_SSH to set credentials
> git fetch --tags --progress git@forge.etsi.org:3GPP/SA5/data-models.git +refs/heads/*:refs/remotes/origin/*
> git rev-parse remotes/origin/test-branch-pj-0629^{commit} # timeout=10
> git branch -a -v --no-abbrev --contains e42c35357859e35e230c8dbeed48bd666805c7d4 # timeout=10
Checking out Revision e42c35357859e35e230c8dbeed48bd666805c7d4 (origin/s5-203329_new_NRM_fragment_to_support_RIM_from_master, origin/S5-203187_Rel-16_CR_TS28.623_Update_ManagedElement_YANG_module, origin/s5-203415_Add_IOC_for_5QIs_to_DSCP_mapping, origin/S5-202357_CR_28.532_Remove_data_object_from_response_types_in_the_ProvMnS, origin/s5-202103_Add_IOC_for_control_of_GTP-U_path_QoS_monitoring_from_master, origin/S5-203423_Rel-16_CR_28.623_Update_FM_control_fragment_(OpenAPI_definitions), origin/S5-203266_Rel-16_CR_28.623_Add_common_data_definitions_(OpenAPI_definitions), origin/S5-203422_Rel-16_CR_28.623_Update_PM_control_fragment_(OpenAPI_definitions), origin/S5-203251_Rel-16_CR_28.623_Clarify_usage_of_the_VsDataContainer_(OpenAPI_definitions), origin/S5-203187_Rel-16_CR_TS_28.623_Update_ManagedElement_YANG_module, origin/s5-203358_Add_ES_coverage_relation_in_NRCellRelation, origin/S5-203458_Rel-16_CR_28.623_Update_PM_control_fragment_YANG_definitions, origin/master, origin/s5-203255-add_transport_information_in_nss_from_master, origin/s5-203331_add_the_NRM_fragment_for_SON_management, origin/S5-202357_Rel-16_CR_28.532_Remove_data_object_from_response_types_in_the_ProvMnS, origin/S5-203199-Rel-16-CR-28-623-Update-NRM-YANG, origin/S5-203389_Rel-16_CR_28.623_Update_FM_control_fragment_(YANG_definitions), origin/s5-202297_Update_RRMpolicyRatio_from_master, origin/S5-203371_CR_TS_28.623_Stage3_add_the_NRM_fragement_for_SON_management, origin/S5-202356_CR_28.532_Add_summary_CM_notification_to_the_ProvMnS, origin/s5-203075_ANR_management_for_EN-DC_architecture, origin/S5-203187_CR_TS_28.623_Update_ManagedElement_YANG_moduel, origin/s5-202373_Update_Clause_Inheritance_UML_diagram_NR_from_master, origin/XuRuiyue_Test_For_YANG, origin/S5-202225_CR_28.532_Add_missing_callbacks_for_notifications_to_ProvMnS, origin/S5-203084_Rel-16_CR_TS_28.623_Update_the_definition_of_SNssai, origin/revert-fea00383, origin/test-branch-pj-0629, origin/S5-202375_Rel-16_CR_28.623_Correct_OpenAPI_definition_for_notificationTypes, origin/S5-203409_Rel-16_CR_28.532_Update_Fault_Supervision_MnS_(OpenAPI_definitions), origin/s5-202101_Add_IOC_for_control_of_QoS_monitoring_per_QoS_flow_per_UE_from_master, origin/s5-203414_Add_IOC_for_configurable_5QIs, origin/S5-203311-Rel16-CR-TS28532-Update-URI-for-performance-data-file-reporting-service, origin/s5-202194_update_for_clarification_on_network_slice_related_identifiers_from_master, origin/s5-202303_Replace_DN_with_better_identifier_for_whitelists_and_blacklists_management_from_master, origin/XuRuiyue_test_for_YANG)
> git config core.sparsecheckout # timeout=10
> git checkout -f e42c35357859e35e230c8dbeed48bd666805c7d4
Commit message: "Merge branch 'Shumin_XSD_from_specs_approved_at_SA87' into 'master'"
> git rev-list --no-walk e42c35357859e35e230c8dbeed48bd666805c7d4 # timeout=10
> git rev-list --no-walk e42c35357859e35e230c8dbeed48bd666805c7d4 # timeout=10
> git rev-list --no-walk e42c35357859e35e230c8dbeed48bd666805c7d4 # timeout=10
> git rev-list --no-walk e42c35357859e35e230c8dbeed48bd666805c7d4 # timeout=10
> git rev-list --no-walk e42c35357859e35e230c8dbeed48bd666805c7d4 # timeout=10
> git rev-list --no-walk e42c35357859e35e230c8dbeed48bd666805c7d4 # timeout=10
> git rev-list --no-walk e42c35357859e35e230c8dbeed48bd666805c7d4 # timeout=10
> git rev-list --no-walk e42c35357859e35e230c8dbeed48bd666805c7d4 # timeout=10
> git rev-list --no-walk e42c35357859e35e230c8dbeed48bd666805c7d4 # timeout=10
> git rev-list --no-walk 9826f7b85cea4c80544b637af0ec08f5acb64dbe # timeout=10
> git rev-list --no-walk e42c35357859e35e230c8dbeed48bd666805c7d4 # timeout=10
> git rev-list --no-walk e42c35357859e35e230c8dbeed48bd666805c7d4 # timeout=10
> git rev-list --no-walk bfd177e5abab7bbbeb96337bd6235e438cc828d1 # timeout=10
> git rev-list --no-walk e42c35357859e35e230c8dbeed48bd666805c7d4 # timeout=10
> git rev-list --no-walk 9692e5dacb345159fc40b21950c8d5b4150915c3 # timeout=10
> git rev-list --no-walk e42c35357859e35e230c8dbeed48bd666805c7d4 # timeout=10
> git rev-list --no-walk e42c35357859e35e230c8dbeed48bd666805c7d4 # timeout=10
> git rev-list --no-walk 842323a8fbcbd84419ead506534342ef2a41cfef # timeout=10
> git rev-list --no-walk a4802bb4707dd19a3911408d29de3733738d3620 # timeout=10
> git rev-list --no-walk e42c35357859e35e230c8dbeed48bd666805c7d4 # timeout=10
> git rev-list --no-walk e42c35357859e35e230c8dbeed48bd666805c7d4 # timeout=10
> git rev-list --no-walk e42c35357859e35e230c8dbeed48bd666805c7d4 # timeout=10
> git rev-list --no-walk e42c35357859e35e230c8dbeed48bd666805c7d4 # timeout=10
> git rev-list --no-walk 94595b032cf68169f51cdd76da9d2938892531f1 # timeout=10
> git rev-list --no-walk e42c35357859e35e230c8dbeed48bd666805c7d4 # timeout=10
> git rev-list --no-walk e42c35357859e35e230c8dbeed48bd666805c7d4 # timeout=10
> git rev-list --no-walk e42c35357859e35e230c8dbeed48bd666805c7d4 # timeout=10
> git rev-list --no-walk e42c35357859e35e230c8dbeed48bd666805c7d4 # timeout=10
> git rev-list --no-walk e42c35357859e35e230c8dbeed48bd666805c7d4 # timeout=10
[Pipeline] }
[Pipeline] // dir
[Pipeline] dir
Running in /home/jenkins/workspace/3GPP/sa5-data-models-any-commit/scripts
[Pipeline] {
[Pipeline] checkout
using credential f9a9fd70-ea8b-4872-a9d5-d1fb1cf8123e
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url git@forge.etsi.org:cti/forge-tools/3gpp-scripts.git # timeout=10
Fetching upstream changes from git@forge.etsi.org:cti/forge-tools/3gpp-scripts.git
> git --version # timeout=10
using GIT_SSH to set credentials
> git fetch --tags --progress git@forge.etsi.org:cti/forge-tools/3gpp-scripts.git +refs/heads/*:refs/remotes/origin/*
skipping resolution of commit remotes/origin/test-branch-pj-0629, since it originates from another repository
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision b28df74c4b3f0a4444fc9fadb37027cfcde1972a (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f b28df74c4b3f0a4444fc9fadb37027cfcde1972a
Commit message: "Add Jenkinsfile for LI"
[Pipeline] }
[Pipeline] // dir
[Pipeline] updateGitlabCommitStatus
[Pipeline] script
[Pipeline] {
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Validate)
[Pipeline] updateGitlabCommitStatus
[Pipeline] sh
+ echo Validate stage
Validate stage
[Pipeline] sh
+ bash ./scripts/validate-data-models.sh ./data-models
------ Switching to ./data-models folder --------
------ Content of the folder ------
OpenAPI
README.md
xsd
yang-models
------ Validating all YANG, JSON and XML files ------
Unable to find image 'hellt/pyang:latest' locally
latest: Pulling from hellt/pyang
e7c96db7181b: Already exists
b1f9d7ed2ba9: Pulling fs layer
cfa7bdf0c465: Pulling fs layer
00ec49b1f957: Pulling fs layer
a83a195b590b: Pulling fs layer
a977ff94e336: Pulling fs layer
17f1ce78c40d: Pulling fs layer
80e5c0c20483: Pulling fs layer
40d572d5b5ca: Pulling fs layer
10eda44d8f1d: Pulling fs layer
92a7a2deff5a: Pulling fs layer
4cb886adc11d: Pulling fs layer
fb5d4eea806e: Pulling fs layer
a977ff94e336: Waiting
4cb886adc11d: Waiting
fb5d4eea806e: Waiting
80e5c0c20483: Waiting
40d572d5b5ca: Waiting
10eda44d8f1d: Waiting
a83a195b590b: Waiting
00ec49b1f957: Download complete
cfa7bdf0c465: Verifying Checksum
cfa7bdf0c465: Download complete
b1f9d7ed2ba9: Verifying Checksum
b1f9d7ed2ba9: Download complete
a83a195b590b: Verifying Checksum
a83a195b590b: Download complete
a977ff94e336: Verifying Checksum
a977ff94e336: Download complete
80e5c0c20483: Verifying Checksum
80e5c0c20483: Download complete
b1f9d7ed2ba9: Pull complete
17f1ce78c40d: Verifying Checksum
17f1ce78c40d: Download complete
cfa7bdf0c465: Pull complete
00ec49b1f957: Pull complete
40d572d5b5ca: Verifying Checksum
40d572d5b5ca: Download complete
a83a195b590b: Pull complete
a977ff94e336: Pull complete
10eda44d8f1d: Download complete
92a7a2deff5a: Verifying Checksum
92a7a2deff5a: Download complete
4cb886adc11d: Verifying Checksum
4cb886adc11d: Download complete
17f1ce78c40d: Pull complete
80e5c0c20483: Pull complete
40d572d5b5ca: Pull complete
10eda44d8f1d: Pull complete
92a7a2deff5a: Pull complete
fb5d4eea806e: Verifying Checksum
fb5d4eea806e: Download complete
4cb886adc11d: Pull complete
fb5d4eea806e: Pull complete
Digest: sha256:531b0212082e0630c23732a46f69fe47a718b28cafcfd037262388d51f0614e6
Status: Downloaded newer image for hellt/pyang:latest
_3gpp-5gc-nrm-neffunction.yang:11: warning: imported module "_3gpp-5g-common-yang-types" not used
_3gpp-5gc-nrm-scpfunction.yang:10: warning: imported module "_3gpp-common-yang-types" not used
_3gpp-5gc-nrm-seppfunction.yang:20: warning: the revision statements are not given in reverse chronological order
_3gpp-nr-nrm-gnbdufunction.yang:17: warning: the revision statements are not given in reverse chronological order
[Pipeline] updateGitlabCommitStatus
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Lint)
[Pipeline] updateGitlabCommitStatus
[Pipeline] sh
+ echo Lint stage
Lint stage
[Pipeline] sh
+ bash ./scripts/lint-data-models.sh ./data-models
------ Switching to ./data-models folder --------
------ Content of the folder ------
OpenAPI
README.md
xsd
yang-models
------ Validating all YANG, JSON and XML files ------
------ pyYANG Version ------
Unable to find image 'hellt/pyang:2.1' locally
2.1: Pulling from hellt/pyang
e7c96db7181b: Already exists
b1f9d7ed2ba9: Already exists
e0c549dece42: Pulling fs layer
7cca8868230c: Pulling fs layer
f8f53391fc06: Pulling fs layer
d4897a36ff2c: Pulling fs layer
a1700fb54ba7: Pulling fs layer
688be0428d1c: Pulling fs layer
d4897a36ff2c: Waiting
a1700fb54ba7: Waiting
688be0428d1c: Waiting
f8f53391fc06: Download complete
7cca8868230c: Verifying Checksum
7cca8868230c: Download complete
e0c549dece42: Verifying Checksum
e0c549dece42: Download complete
d4897a36ff2c: Verifying Checksum
d4897a36ff2c: Download complete
a1700fb54ba7: Download complete
e0c549dece42: Pull complete
7cca8868230c: Pull complete
f8f53391fc06: Pull complete
d4897a36ff2c: Pull complete
a1700fb54ba7: Pull complete
688be0428d1c: Verifying Checksum
688be0428d1c: Download complete
688be0428d1c: Pull complete
Digest: sha256:707637d3631cf669580fed053ebfe3328f48efa7d13b7b0c06e500b30e9523f8
Status: Downloaded newer image for hellt/pyang:2.1
pyang 2.1
------ Linting all YANG files ------
_3gpp-5g-common-yang-types.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5g-common-yang-types.yang:20: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-5g-common-yang-types.yang:21: error: keyword "reference" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5g-common-yang-types.yang:22: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5g-common-yang-types.yang:46: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5g-common-yang-types.yang:47: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5g-common-yang-types.yang:50: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5g-common-yang-types.yang:53: error: RFC 8407: 4.14: statement "leaf-list" must have a "description" substatement
_3gpp-5g-common-yang-types.yang:57: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5g-common-yang-types.yang:62: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5g-common-yang-types.yang:63: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5g-common-yang-types.yang:66: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-affunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-affunction.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-affunction.yang:23: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-affunction.yang:27: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-affunction.yang:31: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-affunction.yang:33: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-amffunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-amffunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement
_3gpp-5gc-nrm-amffunction.yang:10: warning: imported module "ietf-inet-types" not used
_3gpp-5gc-nrm-amffunction.yang:17: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-amffunction.yang:21: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-amffunction.yang:25: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-amffunction.yang:31: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amffunction.yang:42: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amffunction.yang:43: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amffunction.yang:47: error: keyword "min-elements" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amffunction.yang:47: warning: RFC 8407: 4.4: statement "min-elements" is given with its default value "0"
_3gpp-5gc-nrm-amffunction.yang:53: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amffunction.yang:56: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-amffunction.yang:62: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-amffunction.yang:64: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amffunction.yang:70: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-amffunction.yang:74: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amffunction.yang:76: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-amfregion.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-amfregion.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement
_3gpp-5gc-nrm-amfregion.yang:14: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-amfregion.yang:18: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-amfregion.yang:25: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfregion.yang:26: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfregion.yang:27: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfregion.yang:33: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfregion.yang:35: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfregion.yang:36: error: keyword "config" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfregion.yang:37: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfregion.yang:44: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfregion.yang:47: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfregion.yang:51: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfregion.yang:52: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfregion.yang:53: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfregion.yang:57: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfregion.yang:58: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfregion.yang:59: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfregion.yang:63: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-amfregion.yang:67: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfregion.yang:69: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-amfset.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-amfset.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement
_3gpp-5gc-nrm-amfset.yang:14: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-amfset.yang:18: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-amfset.yang:25: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfset.yang:26: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfset.yang:27: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfset.yang:33: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfset.yang:35: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfset.yang:36: error: keyword "config" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfset.yang:37: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfset.yang:44: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfset.yang:47: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfset.yang:51: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfset.yang:52: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfset.yang:56: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfset.yang:57: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfset.yang:58: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfset.yang:59: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfset.yang:63: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-amfset.yang:67: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-amfset.yang:69: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ausffunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-ausffunction.yang:9: warning: imported module "ietf-inet-types" not used
_3gpp-5gc-nrm-ausffunction.yang:21: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-ausffunction.yang:25: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ausffunction.yang:32: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ausffunction.yang:33: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ausffunction.yang:34: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ausffunction.yang:39: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ausffunction.yang:40: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ausffunction.yang:47: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ausffunction.yang:50: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ausffunction.yang:53: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-ausffunction.yang:60: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-ausffunction.yang:62: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ausffunction.yang:67: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-ausffunction.yang:71: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ausffunction.yang:73: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-dnfunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-dnfunction.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-dnfunction.yang:23: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-dnfunction.yang:27: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-dnfunction.yang:31: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-dnfunction.yang:33: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-ep.yang:25: warning: imported module "ietf-inet-types" not used
_3gpp-5gc-nrm-ep.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-ep.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-ep.yang:41: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:45: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:49: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:53: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:57: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:61: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:65: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:69: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:73: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:77: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:81: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:85: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:89: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:93: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:97: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:101: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:105: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:109: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:113: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:117: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:121: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:125: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:129: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:138: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:139: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:142: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:146: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:150: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:154: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:159: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:163: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:167: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:171: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:175: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:179: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:183: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:185: error: RFC 8407: 4.14: statement "leaf-list" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:186: error: keyword "min-elements" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:187: error: keyword "config" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:188: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:192: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:195: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:197: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:204: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:206: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:212: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:215: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:217: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:224: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:226: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:233: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:235: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:242: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:244: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:251: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:253: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:260: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:262: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:269: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:271: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:278: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:280: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:287: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:289: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:296: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:298: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:305: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:307: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:314: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:316: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:322: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:325: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:327: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:334: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:336: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:342: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:345: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:347: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:353: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:356: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:358: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:364: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:367: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:369: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:376: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:378: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:384: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:387: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:389: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:395: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:398: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:400: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:407: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:410: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:412: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:419: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:421: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:427: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:430: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:432: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:439: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:441: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:448: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:450: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:457: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:459: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:466: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:468: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:474: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:477: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:479: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:485: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:488: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:490: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:497: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:499: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:506: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:508: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:514: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:517: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:519: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:526: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:528: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:535: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:537: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:544: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:546: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:553: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:555: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:562: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:564: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:570: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:573: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:575: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:582: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:584: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:591: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:593: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:600: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:603: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:605: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:612: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:614: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:621: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:623: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:630: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:632: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-ep.yang:639: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ep.yang:641: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-externalnrffunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-externalnrffunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement
_3gpp-5gc-nrm-externalnrffunction.yang:14: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-externalnrffunction.yang:18: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-externalnrffunction.yang:24: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-externalnrffunction.yang:25: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-externalnrffunction.yang:26: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-externalnrffunction.yang:31: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-externalnrffunction.yang:35: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-externalnrffunction.yang:37: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-externalnssffunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-externalnssffunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement
_3gpp-5gc-nrm-externalnssffunction.yang:14: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-externalnssffunction.yang:18: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-externalnssffunction.yang:24: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-externalnssffunction.yang:25: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-externalnssffunction.yang:26: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-externalnssffunction.yang:31: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-externalnssffunction.yang:35: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-externalnssffunction.yang:37: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-externalseppfunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-externalseppfunction.yang:11: warning: imported module "ietf-inet-types" not used
_3gpp-5gc-nrm-externalseppfunction.yang:24: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-externalseppfunction.yang:33: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-externalseppfunction.yang:38: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-externalseppfunction.yang:39: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-externalseppfunction.yang:44: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-externalseppfunction.yang:48: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-externalseppfunction.yang:50: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-lmffunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-lmffunction.yang:25: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-lmffunction.yang:32: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-lmffunction.yang:33: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-lmffunction.yang:34: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-lmffunction.yang:38: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-lmffunction.yang:44: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-lmffunction.yang:46: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-lmffunction.yang:51: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-lmffunction.yang:55: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-lmffunction.yang:57: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-n3iwffunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-n3iwffunction.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-n3iwffunction.yang:23: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-n3iwffunction.yang:30: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-n3iwffunction.yang:31: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-n3iwffunction.yang:32: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-n3iwffunction.yang:36: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-n3iwffunction.yang:38: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-n3iwffunction.yang:43: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-n3iwffunction.yang:47: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-n3iwffunction.yang:49: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-neffunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-neffunction.yang:9: warning: imported module "ietf-inet-types" not used
_3gpp-5gc-nrm-neffunction.yang:10: warning: imported module "_3gpp-common-yang-types" not used
_3gpp-5gc-nrm-neffunction.yang:11: warning: imported module "_3gpp-5g-common-yang-types" not used
_3gpp-5gc-nrm-neffunction.yang:24: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-neffunction.yang:28: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-neffunction.yang:29: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-neffunction.yang:36: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-neffunction.yang:37: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-neffunction.yang:41: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-neffunction.yang:43: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-neffunction.yang:46: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-neffunction.yang:50: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-neffunction.yang:56: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-neffunction.yang:60: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-neffunction.yang:62: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-nfprofile.yang:8: warning: imported module "ietf-inet-types" not used
_3gpp-5gc-nrm-nfprofile.yang:9: warning: imported module "ietf-yang-types" not used
_3gpp-5gc-nrm-nfprofile.yang:16: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-nfprofile.yang:20: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:22: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:23: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:24: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:28: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:29: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:30: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:34: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:35: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:36: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:42: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:44: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:53: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:54: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:61: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:63: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:71: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:73: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:74: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:80: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:82: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:83: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:88: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:90: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:95: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:97: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:101: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:102: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:104: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:108: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:109: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:111: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:118: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:120: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:126: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:127: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:129: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:134: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:135: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:137: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:143: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:145: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:153: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:155: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:161: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:163: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:167: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:169: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:173: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:175: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:178: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:183: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:185: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:190: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:191: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:198: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:199: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:206: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:207: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:214: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:215: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:217: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:221: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:226: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:228: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:233: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:234: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:241: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:242: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:249: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:250: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:258: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:260: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:261: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:265: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:269: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:271: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:276: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:277: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:285: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:287: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:288: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:292: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:296: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:297: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:301: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:302: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:308: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:309: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:311: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:320: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:321: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:324: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:332: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:333: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:334: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:341: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:342: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:345: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:352: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:353: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:356: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:365: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:366: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:367: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:372: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:377: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:378: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:379: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:388: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:389: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:392: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:400: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:401: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:402: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:407: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:409: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:414: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:417: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:418: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:419: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:423: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:428: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:429: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:430: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:436: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:439: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:440: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:447: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:448: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:451: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:458: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:461: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:466: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:469: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:470: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:474: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:479: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:482: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:483: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:488: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:489: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:497: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:500: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:506: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:509: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:513: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:520: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:526: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:529: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:530: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:535: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:537: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:538: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:545: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:550: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:555: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:556: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:563: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:564: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:573: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:575: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:580: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:587: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:589: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:590: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:593: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:601: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:603: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:604: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:607: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:615: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:617: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:618: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:621: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:629: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:631: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:632: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:635: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:643: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:645: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:646: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:649: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:657: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:659: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:660: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:663: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:671: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:673: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:674: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:677: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:685: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:687: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:688: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:691: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:699: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:701: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:702: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:705: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:710: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:712: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:718: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:719: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:723: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:725: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:732: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:735: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:740: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:742: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:749: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:752: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:758: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:761: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:766: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:768: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:773: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:775: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:776: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:780: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:782: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:783: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:784: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:785: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:789: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:791: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:792: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:798: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:799: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:806: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:807: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:811: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:813: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:814: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:820: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:821: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:828: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:829: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:833: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:835: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:836: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:842: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:843: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:849: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:850: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:854: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:857: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:858: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:859: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:865: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:866: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:871: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:873: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:874: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:875: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:880: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:881: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:882: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:886: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:887: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:888: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:892: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:895: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:896: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:897: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:901: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:903: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:911: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:913: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:914: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:915: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:916: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:917: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:921: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:924: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:925: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:926: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:932: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:933: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:934: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:939: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:942: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:943: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:944: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:948: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:951: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:953: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:954: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:955: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:959: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:962: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:964: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:965: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:971: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:973: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:974: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:980: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:982: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:988: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:990: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:994: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:996: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:997: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:998: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:1002: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:1005: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1006: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1007: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1013: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1014: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1019: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:1021: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:1022: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:1026: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:1028: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:1031: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1033: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1034: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1040: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1042: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1043: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1049: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1050: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1054: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:1057: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1058: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1059: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1065: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1066: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1071: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:1073: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1074: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1075: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1079: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfprofile.yang:1082: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1083: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1084: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1090: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfprofile.yang:1091: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-nfservice.yang:15: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-nfservice.yang:19: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:21: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:22: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:23: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:27: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:28: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:29: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:34: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:35: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:40: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:41: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:42: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:46: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:47: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:48: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:52: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:54: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:59: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:61: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:69: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:70: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:73: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:78: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:80: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:85: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:87: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:95: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:97: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:103: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:105: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:107: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:111: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:113: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:114: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:119: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:120: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:122: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:127: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:129: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:133: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:135: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:139: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:141: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:145: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:147: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:153: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:154: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:159: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:161: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:165: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:171: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:172: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:173: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:177: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:181: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:186: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:190: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:195: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:197: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:198: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:199: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:203: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:204: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:205: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:206: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:209: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:210: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:211: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:214: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:220: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:222: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:223: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:224: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:225: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:226: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:227: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:228: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:229: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:230: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:231: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:232: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:233: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:234: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:235: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:236: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:237: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:238: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:239: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:240: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:241: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:242: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:243: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:244: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:245: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:246: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:247: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:248: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:249: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:250: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:251: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:252: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:253: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:254: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:258: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:260: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:261: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:265: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:267: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:268: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:269: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:273: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nfservice.yang:275: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:277: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:281: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nfservice.yang:283: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ngeirfunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-ngeirfunction.yang:25: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-ngeirfunction.yang:32: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ngeirfunction.yang:33: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ngeirfunction.yang:34: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ngeirfunction.yang:42: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ngeirfunction.yang:45: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ngeirfunction.yang:48: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-ngeirfunction.yang:54: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-ngeirfunction.yang:56: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ngeirfunction.yang:61: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-ngeirfunction.yang:65: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-ngeirfunction.yang:67: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-nrffunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-nrffunction.yang:9: warning: imported module "ietf-inet-types" not used
_3gpp-5gc-nrm-nrffunction.yang:20: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-nrffunction.yang:24: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nrffunction.yang:31: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nrffunction.yang:32: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nrffunction.yang:33: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nrffunction.yang:38: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nrffunction.yang:39: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nrffunction.yang:43: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nrffunction.yang:45: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nrffunction.yang:52: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nrffunction.yang:55: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nrffunction.yang:61: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nrffunction.yang:66: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-nrffunction.yang:70: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nrffunction.yang:72: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-nssffunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-nssffunction.yang:9: warning: imported module "ietf-inet-types" not used
_3gpp-5gc-nrm-nssffunction.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-nssffunction.yang:24: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nssffunction.yang:31: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nssffunction.yang:32: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nssffunction.yang:33: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nssffunction.yang:38: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nssffunction.yang:39: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nssffunction.yang:46: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nssffunction.yang:49: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nssffunction.yang:53: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nssffunction.yang:55: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nssffunction.yang:58: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-nssffunction.yang:65: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-nssffunction.yang:69: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nssffunction.yang:71: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-nwdaffunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-nwdaffunction.yang:9: warning: imported module "ietf-inet-types" not used
_3gpp-5gc-nrm-nwdaffunction.yang:26: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-nwdaffunction.yang:33: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nwdaffunction.yang:34: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nwdaffunction.yang:35: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nwdaffunction.yang:40: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nwdaffunction.yang:41: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nwdaffunction.yang:48: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nwdaffunction.yang:51: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nwdaffunction.yang:54: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-nwdaffunction.yang:60: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-nwdaffunction.yang:62: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nwdaffunction.yang:67: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-nwdaffunction.yang:71: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-nwdaffunction.yang:73: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-pcffunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-pcffunction.yang:9: warning: imported module "ietf-inet-types" not used
_3gpp-5gc-nrm-pcffunction.yang:20: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-pcffunction.yang:24: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-pcffunction.yang:31: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-pcffunction.yang:32: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-pcffunction.yang:33: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-pcffunction.yang:38: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-pcffunction.yang:39: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-pcffunction.yang:46: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-pcffunction.yang:49: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-pcffunction.yang:52: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-pcffunction.yang:57: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-pcffunction.yang:59: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-pcffunction.yang:64: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-pcffunction.yang:68: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-pcffunction.yang:70: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-scpfunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-scpfunction.yang:9: warning: imported module "ietf-inet-types" not used
_3gpp-5gc-nrm-scpfunction.yang:10: warning: imported module "_3gpp-common-yang-types" not used
_3gpp-5gc-nrm-scpfunction.yang:24: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-scpfunction.yang:28: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-scpfunction.yang:29: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-scpfunction.yang:32: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-scpfunction.yang:34: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-scpfunction.yang:40: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-scpfunction.yang:44: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-scpfunction.yang:46: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-seppfunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-seppfunction.yang:11: warning: imported module "ietf-inet-types" not used
_3gpp-5gc-nrm-seppfunction.yang:20: warning: the revision statements are not given in reverse chronological order
_3gpp-5gc-nrm-seppfunction.yang:20: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-seppfunction.yang:24: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-5gc-nrm-seppfunction.yang:25: error: keyword "reference" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-seppfunction.yang:26: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-seppfunction.yang:39: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-seppfunction.yang:48: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-seppfunction.yang:52: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-5gc-nrm-seppfunction.yang:57: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-seppfunction.yang:58: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-seppfunction.yang:62: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-seppfunction.yang:66: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-seppfunction.yang:68: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-smffunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-smffunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement
_3gpp-5gc-nrm-smffunction.yang:10: warning: imported module "ietf-inet-types" not used
_3gpp-5gc-nrm-smffunction.yang:16: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-smffunction.yang:20: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-smffunction.yang:24: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-smffunction.yang:30: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-smffunction.yang:36: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-smffunction.yang:38: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-smffunction.yang:39: error: keyword "config" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-smffunction.yang:40: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-smffunction.yang:44: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-smffunction.yang:45: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-smffunction.yang:49: error: keyword "min-elements" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-smffunction.yang:49: warning: RFC 8407: 4.4: statement "min-elements" is given with its default value "0"
_3gpp-5gc-nrm-smffunction.yang:55: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-smffunction.yang:58: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-smffunction.yang:64: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-smffunction.yang:66: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-smffunction.yang:71: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-smffunction.yang:75: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-smffunction.yang:77: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-smsffunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-smsffunction.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-smsffunction.yang:24: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-smsffunction.yang:31: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-smsffunction.yang:32: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-smsffunction.yang:33: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-smsffunction.yang:37: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-smsffunction.yang:43: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-smsffunction.yang:45: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-smsffunction.yang:50: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-smsffunction.yang:54: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-smsffunction.yang:56: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-udmfunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-udmfunction.yang:9: warning: imported module "ietf-inet-types" not used
_3gpp-5gc-nrm-udmfunction.yang:20: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-udmfunction.yang:24: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-udmfunction.yang:31: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udmfunction.yang:32: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udmfunction.yang:33: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udmfunction.yang:38: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udmfunction.yang:39: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udmfunction.yang:46: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udmfunction.yang:49: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udmfunction.yang:52: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-udmfunction.yang:58: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-udmfunction.yang:60: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udmfunction.yang:65: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-udmfunction.yang:69: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udmfunction.yang:71: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-udrfunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-udrfunction.yang:9: warning: imported module "ietf-inet-types" not used
_3gpp-5gc-nrm-udrfunction.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-udrfunction.yang:23: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-udrfunction.yang:30: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udrfunction.yang:31: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udrfunction.yang:32: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udrfunction.yang:37: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udrfunction.yang:38: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udrfunction.yang:45: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udrfunction.yang:48: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udrfunction.yang:51: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-udrfunction.yang:58: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-udrfunction.yang:62: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udrfunction.yang:64: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-udsffunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-udsffunction.yang:9: warning: imported module "ietf-inet-types" not used
_3gpp-5gc-nrm-udsffunction.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-udsffunction.yang:24: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-udsffunction.yang:31: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udsffunction.yang:32: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udsffunction.yang:33: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udsffunction.yang:38: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udsffunction.yang:39: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udsffunction.yang:46: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udsffunction.yang:49: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udsffunction.yang:52: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-udsffunction.yang:59: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-udsffunction.yang:63: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-udsffunction.yang:65: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-5gc-nrm-upffunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-5gc-nrm-upffunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement
_3gpp-5gc-nrm-upffunction.yang:15: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-upffunction.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-5gc-nrm-upffunction.yang:23: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-5gc-nrm-upffunction.yang:28: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-upffunction.yang:29: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-upffunction.yang:35: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-upffunction.yang:37: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-upffunction.yang:38: error: keyword "config" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-upffunction.yang:39: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-upffunction.yang:46: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-5gc-nrm-upffunction.yang:47: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-upffunction.yang:49: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-upffunction.yang:52: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-upffunction.yang:58: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-5gc-nrm-upffunction.yang:60: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-upffunction.yang:65: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-5gc-nrm-upffunction.yang:69: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-5gc-nrm-upffunction.yang:71: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-common-ep-rp.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-common-ep-rp.yang:7: warning: imported module "ietf-inet-types" not used
_3gpp-common-ep-rp.yang:23: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-common-ep-rp.yang:42: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-ep-rp.yang:43: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-ep-rp.yang:44: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-ep-rp.yang:48: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-common-ep-rp.yang:53: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-ep-rp.yang:54: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-ep-rp.yang:55: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-ep-rp.yang:60: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-ep-rp.yang:61: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-ep-rp.yang:62: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-fm.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-common-fm.yang:30: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-fm.yang:34: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-fm.yang:38: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-fm.yang:42: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-fm.yang:46: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-fm.yang:50: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-fm.yang:54: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-fm.yang:58: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-fm.yang:62: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-fm.yang:66: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-fm.yang:76: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-fm.yang:77: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-fm.yang:78: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-fm.yang:79: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-fm.yang:80: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-fm.yang:81: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-fm.yang:112: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-fm.yang:113: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-fm.yang:128: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-fm.yang:145: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-fm.yang:362: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-common-fm.yang:385: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-common-managed-element.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-common-managed-element.yang:6: warning: imported module "_3gpp-common-yang-types" not used
_3gpp-common-managed-element.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-common-managed-element.yang:55: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-managed-element.yang:56: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-managed-element.yang:60: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-managed-element.yang:61: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-managed-element.yang:68: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-managed-element.yang:69: error: keyword "config" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-managed-element.yang:70: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-managed-element.yang:77: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-managed-element.yang:79: error: keyword "config" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-managed-element.yang:80: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-managed-element.yang:98: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-managed-element.yang:100: error: keyword "config" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-managed-element.yang:101: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-managed-element.yang:102: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-managed-element.yang:116: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-managed-element.yang:117: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-managed-element.yang:118: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-managed-element.yang:126: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-managed-element.yang:127: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-managed-element.yang:128: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-managed-element.yang:131: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-managed-element.yang:159: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-managed-element.yang:161: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-common-managed-function.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-common-managed-function.yang:29: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-common-managed-function.yang:33: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-common-managed-function.yang:36: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-managed-function.yang:50: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-managed-function.yang:51: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-managed-function.yang:71: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-managed-function.yang:73: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-managed-function.yang:116: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-managed-function.yang:118: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-managed-function.yang:119: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-managed-function.yang:156: error: keyword "presence" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-managed-function.yang:207: error: keyword "presence" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-managed-function.yang:271: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-managed-function.yang:272: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-managed-function.yang:273: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-managed-function.yang:278: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-common-managed-function.yang:282: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-managed-function.yang:284: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-common-measurements.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-common-measurements.yang:67: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-common-measurements.yang:86: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-measurements.yang:118: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-measurements.yang:146: error: keyword "default" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:147: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:157: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:159: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:186: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:187: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:188: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:199: error: keyword "must" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:203: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:204: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:224: error: keyword "when" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:224: error: keyword "when" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:225: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:226: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:227: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:315: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:316: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:317: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:324: error: keyword "must" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:328: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:329: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:345: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:346: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:347: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:373: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-common-measurements.yang:375: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-measurements.yang:389: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-measurements.yang:390: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-measurements.yang:402: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-common-measurements.yang:405: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-measurements.yang:518: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:520: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-common-measurements.yang:554: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-measurements.yang:556: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-common-measurements.yang:581: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-common-measurements.yang:608: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-common-subnetwork.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-common-subnetwork.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-common-subnetwork.yang:67: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-subnetwork.yang:83: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-common-subnetwork.yang:100: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-subnetwork.yang:101: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-subnetwork.yang:104: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-subnetwork.yang:105: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-subnetwork.yang:106: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-subnetwork.yang:116: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-common-subnetwork.yang:126: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-subnetwork.yang:127: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-subnetwork.yang:136: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-subnetwork.yang:137: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-subscription-control.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-common-subscription-control.yang:27: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-subscription-control.yang:50: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-subscription-control.yang:51: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-subscription-control.yang:52: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-subscription-control.yang:53: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-subscription-control.yang:101: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-subscription-control.yang:108: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-common-subscription-control.yang:145: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-subscription-control.yang:147: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-common-subscription-control.yang:178: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-subscription-control.yang:181: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-common-subscription-control.yang:188: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-common-subscription-control.yang:192: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-common-top.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-common-top.yang:20: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-common-yang-extensions.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-common-yang-extensions.yang:43: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-common-yang-extensions.yang:93: error: keyword "argument" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-common-yang-types.yang:7: warning: imported module "ietf-yang-types" not used
_3gpp-common-yang-types.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-common-yang-types.yang:38: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-yang-types.yang:41: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:43: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:51: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:53: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:58: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:59: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:79: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:80: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:100: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:101: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:102: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:103: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:130: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:131: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:132: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:141: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-yang-types.yang:145: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-yang-types.yang:156: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:157: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:165: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:166: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:172: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-common-yang-types.yang:173: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-yang-types.yang:174: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:175: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:177: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-yang-types.yang:178: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:179: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:187: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:189: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:201: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-common-yang-types.yang:202: error: keyword "reference" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:203: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:217: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-common-yang-types.yang:218: error: keyword "reference" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:219: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:244: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-common-yang-types.yang:246: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:247: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:248: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:249: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:250: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:251: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:252: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:253: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:254: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:258: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-common-yang-types.yang:260: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:261: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:262: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:275: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-common-yang-types.yang:293: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-common-yang-types.yang:304: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-common-yang-types.yang:317: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-common-yang-types.yang:331: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-yang-types.yang:334: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-yang-types.yang:337: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-yang-types.yang:349: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-common-yang-types.yang:351: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:352: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:353: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:354: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:355: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:356: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:357: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:358: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:359: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:360: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:361: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:362: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:363: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:364: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:365: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:366: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:367: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:368: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:369: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:370: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:374: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-common-yang-types.yang:376: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:377: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:378: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:383: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:384: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-common-yang-types.yang:389: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-common-yang-types.yang:391: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:392: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:393: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:394: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:398: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-common-yang-types.yang:400: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:401: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:402: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:403: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:404: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:408: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-common-yang-types.yang:410: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-yang-types.yang:414: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-yang-types.yang:418: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-yang-types.yang:422: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-yang-types.yang:427: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-common-yang-types.yang:428: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-yang-types.yang:431: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-yang-types.yang:436: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-common-yang-types.yang:437: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-yang-types.yang:440: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-yang-types.yang:445: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-common-yang-types.yang:449: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-common-yang-types.yang:451: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:452: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:453: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:454: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:458: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-common-yang-types.yang:460: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:461: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:465: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-common-yang-types.yang:467: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:468: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:469: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-common-yang-types.yang:473: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-common-yang-types.yang:474: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-yang-types.yang:477: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-common-yang-types.yang:511: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-nr-nrm-beam.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-beam.yang:23: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-nr-nrm-beam.yang:25: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-nr-nrm-beam.yang:35: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-beam.yang:36: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-beam.yang:37: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-beam.yang:41: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-beam.yang:42: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-beam.yang:43: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-beam.yang:47: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-beam.yang:49: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-beam.yang:50: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-beam.yang:51: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-beam.yang:56: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-beam.yang:58: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-beam.yang:59: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-beam.yang:60: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-beam.yang:66: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-beam.yang:68: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-beam.yang:69: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-beam.yang:70: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-beam.yang:74: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-beam.yang:76: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-beam.yang:77: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-beam.yang:78: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-beam.yang:84: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-beam.yang:89: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-beam.yang:91: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-bwp.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-bwp.yang:17: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-bwp.yang:21: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-nr-nrm-bwp.yang:23: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-nr-nrm-bwp.yang:24: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-nr-nrm-bwp.yang:28: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-nr-nrm-bwp.yang:30: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-nr-nrm-bwp.yang:31: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-nr-nrm-bwp.yang:32: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-nr-nrm-bwp.yang:36: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-nr-nrm-bwp.yang:38: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-nr-nrm-bwp.yang:39: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-nr-nrm-bwp.yang:50: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-bwp.yang:51: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-bwp.yang:52: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-bwp.yang:57: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-bwp.yang:58: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-bwp.yang:59: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-bwp.yang:63: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-bwp.yang:65: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-bwp.yang:66: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-bwp.yang:67: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-bwp.yang:71: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-bwp.yang:73: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-bwp.yang:74: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-bwp.yang:79: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-bwp.yang:81: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-bwp.yang:82: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-bwp.yang:86: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-bwp.yang:88: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-bwp.yang:89: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-bwp.yang:93: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-bwp.yang:97: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-bwp.yang:99: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-common.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-common.yang:12: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-common.yang:24: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-nr-nrm-commonbeamformingfunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-commonbeamformingfunction.yang:29: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-commonbeamformingfunction.yang:30: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-commonbeamformingfunction.yang:31: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-commonbeamformingfunction.yang:35: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-commonbeamformingfunction.yang:38: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-commonbeamformingfunction.yang:39: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-commonbeamformingfunction.yang:43: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-commonbeamformingfunction.yang:45: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-commonbeamformingfunction.yang:46: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-commonbeamformingfunction.yang:50: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-commonbeamformingfunction.yang:55: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-commonbeamformingfunction.yang:57: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-ep.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-ep.yang:20: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-ep.yang:84: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-ep.yang:90: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-ep.yang:92: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-ep.yang:101: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-ep.yang:103: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-ep.yang:112: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-ep.yang:114: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-ep.yang:125: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-ep.yang:127: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-ep.yang:137: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-ep.yang:139: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-ep.yang:145: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-ep.yang:151: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-ep.yang:153: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-ep.yang:162: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-ep.yang:164: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-ep.yang:173: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-ep.yang:175: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-ep.yang:185: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-ep.yang:187: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-ep.yang:196: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-ep.yang:198: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-ep.yang:207: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-ep.yang:209: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-ep.yang:215: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-ep.yang:221: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-ep.yang:223: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-ep.yang:232: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-ep.yang:234: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-eutrancellrelation.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-eutrancellrelation.yang:6: warning: imported module "_3gpp-common-yang-types" not used
_3gpp-nr-nrm-eutrancellrelation.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-eutrancellrelation.yang:23: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-nr-nrm-eutrancellrelation.yang:25: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-nr-nrm-eutrancellrelation.yang:26: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-nr-nrm-eutrancellrelation.yang:30: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-nr-nrm-eutrancellrelation.yang:32: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-nr-nrm-eutrancellrelation.yang:33: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-nr-nrm-eutrancellrelation.yang:34: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-nr-nrm-eutrancellrelation.yang:47: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:48: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:49: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:56: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:57: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:58: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:66: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:67: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:68: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:78: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:80: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:81: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:90: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:91: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:92: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:104: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:105: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:106: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:114: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:116: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:117: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:124: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:126: error: keyword "config" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:127: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:132: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:133: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:134: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:138: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-eutrancellrelation.yang:143: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutrancellrelation.yang:145: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-eutranetwork.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-eutranetwork.yang:14: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-eutranetwork.yang:32: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranetwork.yang:34: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-eutranetwork.yang:44: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranetwork.yang:45: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranetwork.yang:54: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranetwork.yang:55: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-eutranfreqrelation.yang:6: warning: imported module "_3gpp-common-yang-types" not used
_3gpp-nr-nrm-eutranfreqrelation.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-eutranfreqrelation.yang:32: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:34: error: keyword "default" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:35: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:40: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:42: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:43: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:48: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:49: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:50: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:58: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:61: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:62: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:68: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:70: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:71: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:76: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:78: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:79: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:80: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:85: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:86: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:87: error: keyword "default" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:94: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:96: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:97: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:98: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:105: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:107: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:108: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:109: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:116: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:118: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:119: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:120: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:127: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:129: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:130: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:131: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:138: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:140: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:141: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:142: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:149: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:151: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:152: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:153: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:158: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:160: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:161: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:162: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:168: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:171: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:172: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:173: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:179: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:182: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:183: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:184: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:188: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:189: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:190: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:194: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-eutranfreqrelation.yang:200: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfreqrelation.yang:202: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-eutranfrequency.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-eutranfrequency.yang:18: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-eutranfrequency.yang:28: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfrequency.yang:30: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfrequency.yang:31: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfrequency.yang:35: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfrequency.yang:36: error: keyword "config" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfrequency.yang:37: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfrequency.yang:38: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfrequency.yang:42: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-nr-nrm-eutranfrequency.yang:46: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-eutranfrequency.yang:48: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-eutranfrequency.yang:55: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-eutranfrequency.yang:60: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-externalamffunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-externalamffunction.yang:18: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-externalamffunction.yang:32: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalamffunction.yang:33: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalamffunction.yang:34: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalamffunction.yang:45: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-nr-nrm-externalamffunction.yang:51: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalamffunction.yang:53: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-externalamffunction.yang:60: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-externalamffunction.yang:65: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-externalenbfunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-externalenbfunction.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-externalenbfunction.yang:29: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalenbfunction.yang:31: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalenbfunction.yang:32: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalenbfunction.yang:38: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-nr-nrm-externalenbfunction.yang:42: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalenbfunction.yang:44: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-externalenbfunction.yang:51: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-externalenbfunction.yang:56: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-externaleutrancell.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-externaleutrancell.yang:21: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-externaleutrancell.yang:33: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-externaleutrancell.yang:35: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externaleutrancell.yang:36: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externaleutrancell.yang:50: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externaleutrancell.yang:51: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externaleutrancell.yang:52: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externaleutrancell.yang:57: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-externaleutrancell.yang:59: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externaleutrancell.yang:63: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-externaleutrancell.yang:65: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externaleutrancell.yang:66: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externaleutrancell.yang:78: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-externaleutrancell.yang:80: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externaleutrancell.yang:81: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externaleutrancell.yang:86: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-externaleutrancell.yang:88: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externaleutrancell.yang:89: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externaleutrancell.yang:99: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-externaleutrancell.yang:101: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externaleutrancell.yang:102: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externaleutrancell.yang:106: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-nr-nrm-externaleutrancell.yang:111: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externaleutrancell.yang:113: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-externaleutrancell.yang:120: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-nr-nrm-externaleutrancell.yang:125: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externaleutrancell.yang:127: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-externaleutrancell.yang:134: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-externaleutrancell.yang:139: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-externaleutrancell.yang:144: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-externaleutrancell.yang:149: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-externalgnbcucpfunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-externalgnbcucpfunction.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-externalgnbcucpfunction.yang:29: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbcucpfunction.yang:32: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbcucpfunction.yang:33: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbcucpfunction.yang:37: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbcucpfunction.yang:39: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbcucpfunction.yang:40: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbcucpfunction.yang:46: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbcucpfunction.yang:47: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbcucpfunction.yang:48: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbcucpfunction.yang:53: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-nr-nrm-externalgnbcucpfunction.yang:58: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbcucpfunction.yang:60: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-externalgnbcucpfunction.yang:67: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-externalgnbcucpfunction.yang:72: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-externalgnbcuupfunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-externalgnbcuupfunction.yang:18: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-externalgnbcuupfunction.yang:28: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbcuupfunction.yang:31: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbcuupfunction.yang:32: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbcuupfunction.yang:36: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbcuupfunction.yang:38: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbcuupfunction.yang:39: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbcuupfunction.yang:43: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-nr-nrm-externalgnbcuupfunction.yang:48: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbcuupfunction.yang:50: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-externalgnbcuupfunction.yang:57: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-externalgnbcuupfunction.yang:62: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-externalgnbdufunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-externalgnbdufunction.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-externalgnbdufunction.yang:29: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbdufunction.yang:32: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbdufunction.yang:33: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbdufunction.yang:37: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbdufunction.yang:39: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbdufunction.yang:40: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbdufunction.yang:46: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbdufunction.yang:47: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbdufunction.yang:48: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbdufunction.yang:53: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-nr-nrm-externalgnbdufunction.yang:58: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalgnbdufunction.yang:60: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-externalgnbdufunction.yang:67: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-externalgnbdufunction.yang:72: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-externalnrcellcu.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-externalnrcellcu.yang:20: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-externalnrcellcu.yang:31: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalnrcellcu.yang:33: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalnrcellcu.yang:34: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalnrcellcu.yang:38: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalnrcellcu.yang:40: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalnrcellcu.yang:41: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalnrcellcu.yang:49: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalnrcellcu.yang:50: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalnrcellcu.yang:51: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalnrcellcu.yang:56: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalnrcellcu.yang:57: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalnrcellcu.yang:58: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalnrcellcu.yang:62: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-nr-nrm-externalnrcellcu.yang:67: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalnrcellcu.yang:69: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-externalnrcellcu.yang:76: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-externalnrcellcu.yang:81: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-externalservinggwfunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-externalservinggwfunction.yang:18: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-externalservinggwfunction.yang:28: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-nr-nrm-externalservinggwfunction.yang:34: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalservinggwfunction.yang:36: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-externalservinggwfunction.yang:43: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-externalservinggwfunction.yang:48: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-externalupffunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-externalupffunction.yang:17: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-externalupffunction.yang:27: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-nr-nrm-externalupffunction.yang:33: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-externalupffunction.yang:35: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-externalupffunction.yang:42: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-externalupffunction.yang:47: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-gnbcucpfunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-gnbcucpfunction.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-gnbcucpfunction.yang:31: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-gnbcucpfunction.yang:33: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-gnbcucpfunction.yang:34: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-gnbcucpfunction.yang:38: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-gnbcucpfunction.yang:40: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-gnbcucpfunction.yang:41: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-gnbcucpfunction.yang:45: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-gnbcucpfunction.yang:47: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-gnbcucpfunction.yang:48: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-gnbcucpfunction.yang:54: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-gnbcucpfunction.yang:55: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-gnbcucpfunction.yang:56: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-gnbcucpfunction.yang:86: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-gnbcucpfunction.yang:91: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-gnbcucpfunction.yang:93: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-gnbcuupfunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-gnbcuupfunction.yang:21: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-gnbcuupfunction.yang:28: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
_3gpp-nr-nrm-gnbcuupfunction.yang:109: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-gnbcuupfunction.yang:110: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-gnbcuupfunction.yang:119: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-gnbcuupfunction.yang:132: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-gnbcuupfunction.yang:139: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-gnbdufunction.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-gnbdufunction.yang:17: warning: the revision statements are not given in reverse chronological order
_3gpp-nr-nrm-gnbdufunction.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-gnbdufunction.yang:74: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-gnbdufunction.yang:81: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-nrcellcu.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-nrcellcu.yang:6: warning: imported module "_3gpp-common-yang-types" not used
_3gpp-nr-nrm-nrcellcu.yang:20: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-nrcellcu.yang:31: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellcu.yang:32: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellcu.yang:33: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellcu.yang:41: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellcu.yang:42: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellcu.yang:48: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellcu.yang:49: error: keyword "config" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellcu.yang:50: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellcu.yang:54: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-nrcellcu.yang:61: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellcu.yang:63: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-nrcelldu.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-nrcelldu.yang:6: warning: imported module "_3gpp-common-yang-types" not used
_3gpp-nr-nrm-nrcelldu.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-nrcelldu.yang:34: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:36: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:37: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:44: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:45: error: keyword "config" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:46: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:52: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:53: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:54: error: keyword "default" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:61: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:62: error: keyword "config" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:63: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:71: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:72: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:78: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:80: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:81: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:85: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:87: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:92: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:94: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:95: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:100: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:102: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:107: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:109: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:113: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:115: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:116: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:120: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:122: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:123: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:127: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:129: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:130: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:131: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:140: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:141: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:142: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:147: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:148: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:149: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:150: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:155: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:157: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:158: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:159: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:166: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:167: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:168: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:169: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:174: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:176: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:177: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:178: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:182: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:183: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:184: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:188: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:189: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:190: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:194: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:195: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:196: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:200: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-nrcelldu.yang:205: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcelldu.yang:207: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-nrcellrelation.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-nrcellrelation.yang:6: warning: imported module "_3gpp-common-yang-types" not used
_3gpp-nr-nrm-nrcellrelation.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-nrcellrelation.yang:31: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:32: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:43: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:44: error: keyword "default" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:45: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:49: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:50: error: keyword "default" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:51: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:55: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:56: error: keyword "default" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:57: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:61: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:62: error: keyword "default" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:63: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:67: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:68: error: keyword "default" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:69: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:73: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:74: error: keyword "default" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:75: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:80: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:81: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:82: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:87: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:88: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:89: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:105: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-nrcellrelation.yang:112: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrcellrelation.yang:114: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-nrfreqrelation.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-nrfreqrelation.yang:6: warning: imported module "_3gpp-common-yang-types" not used
_3gpp-nr-nrm-nrfreqrelation.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-nrfreqrelation.yang:39: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:40: error: keyword "default" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:41: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:45: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:46: error: keyword "default" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:47: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:51: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:52: error: keyword "default" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:53: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:57: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:58: error: keyword "default" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:59: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:63: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:64: error: keyword "default" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:65: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:69: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:70: error: keyword "default" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:71: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:77: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:79: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:80: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:85: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:86: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:87: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:95: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:98: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:99: error: keyword "default" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:105: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:107: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:108: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:113: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:115: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:116: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:117: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:122: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:123: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:124: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:125: error: keyword "default" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:132: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:134: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:135: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:136: error: keyword "default" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:143: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:145: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:146: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:147: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:154: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:156: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:157: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:158: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:165: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:167: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:168: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:169: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:176: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:178: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:179: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:180: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:187: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:189: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:190: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:191: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:195: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:197: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:198: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:199: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:205: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:208: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:209: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:210: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:216: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:219: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:220: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:221: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:225: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:226: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:227: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:231: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-nrfreqrelation.yang:237: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfreqrelation.yang:239: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-nrfrequency.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-nrfrequency.yang:17: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-nrfrequency.yang:28: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfrequency.yang:29: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfrequency.yang:30: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfrequency.yang:34: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfrequency.yang:35: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfrequency.yang:36: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfrequency.yang:37: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfrequency.yang:42: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfrequency.yang:43: error: keyword "config" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfrequency.yang:44: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfrequency.yang:45: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfrequency.yang:49: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
_3gpp-nr-nrm-nrfrequency.yang:53: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrfrequency.yang:55: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-nrfrequency.yang:62: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-nrfrequency.yang:67: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-nrnetwork.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-nrnetwork.yang:14: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-nrnetwork.yang:33: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrnetwork.yang:35: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-nrsectorcarrier.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-nrsectorcarrier.yang:6: warning: imported module "_3gpp-common-yang-types" not used
_3gpp-nr-nrm-nrsectorcarrier.yang:18: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-nrsectorcarrier.yang:29: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:30: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:31: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:36: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:37: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:38: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:39: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:44: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:46: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:47: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:52: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:54: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:55: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:59: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:61: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:62: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:64: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:68: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:70: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:71: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:73: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:78: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:80: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:81: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:85: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
_3gpp-nr-nrm-nrsectorcarrier.yang:91: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-nrsectorcarrier.yang:93: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
_3gpp-nr-nrm-rrmpolicy.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement
_3gpp-nr-nrm-rrmpolicy.yang:13: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
_3gpp-nr-nrm-rrmpolicy.yang:24: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-nr-nrm-rrmpolicy.yang:29: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-nr-nrm-rrmpolicy.yang:31: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-nr-nrm-rrmpolicy.yang:32: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-nr-nrm-rrmpolicy.yang:36: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
_3gpp-nr-nrm-rrmpolicy.yang:38: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-nr-nrm-rrmpolicy.yang:39: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
_3gpp-nr-nrm-rrmpolicy.yang:56: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-rrmpolicy.yang:57: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-rrmpolicy.yang:58: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-rrmpolicy.yang:65: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-rrmpolicy.yang:66: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-rrmpolicy.yang:67: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
_3gpp-nr-nrm-rrmpolicy.yang:82: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-rrmpolicy.yang:83: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-rrmpolicy.yang:84: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-rrmpolicy.yang:94: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-rrmpolicy.yang:95: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-rrmpolicy.yang:96: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-rrmpolicy.yang:97: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-rrmpolicy.yang:108: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-rrmpolicy.yang:109: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-rrmpolicy.yang:110: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-rrmpolicy.yang:120: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-rrmpolicy.yang:121: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-rrmpolicy.yang:122: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-rrmpolicy.yang:123: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-rrmpolicy.yang:135: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12)
_3gpp-nr-nrm-rrmpolicy.yang:136: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-rrmpolicy.yang:137: error: keyword "units" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-rrmpolicy.yang:146: error: keyword "key" not in canonical order (see RFC 6020, Section 12)
_3gpp-nr-nrm-rrmpolicy.yang:148: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
------ Linting result ------
1
[Pipeline] updateGitlabCommitStatus
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Deploy to FTP)
[Pipeline] sh
+ echo DEPLOY stage
DEPLOY stage
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // gitlabBuilds
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS
![[Jenkins]](/jenkins/static/e5391b04/images/headshot.png)
Console Output