Formal
Providing yang modules
Public access to yang modules would be very benifical, avoiding error prune and time consuming extraction from from word documents.
- https://github.com/YangModels/yang
- http://www.netconfcentral.org
- and of cause the related 3GPP TS page
... are good candidates to publish agreed and reviewed 3GPP yang modules.
License statement
Please add the 3GPP License statement to the yang modul description statement.
TS 28.541 v16.1.0 example | Proposal | ||||
---|---|---|---|---|---|
|
|
YANG mechanics
Revision in import statements
The "revision date" in yang import statements should be avoided to gain more flexibility, when the imported yang module is update. It avoids updates of the importing yang model.
TS 28.541 v16.1.0 example | Proposal | ||||
---|---|---|---|---|---|
|
|
Yang submodules vs. Yang augment statement.
The usage of submodules and include statements create a monolithic interface description block - from developer point of view.
To address the expected high dynamic in 5G features and its OAM modules, Each submodule should be changed to a full module augmenting its parent module.
YANG content
Vendor specific container
The yang module "Vendor specific data container" is not needed, because each vendor (and operator) can augment each yang module to address vendor specific features. This yang feature makes such vendor specific data container model obsolete. Please note that other schemas may still require such model.