YANG-next issue summary #152
Description
YANG-next Issue Summary
Method
- Group Related Issues
- Ease of Use
- API Conformance
- All Importance=Low issues are dropped
- All Complexity=High issues are classified as "maybe later"
- All Complexity=Unknown issues need to be re-classified first
- Deprecated = Usage in YANG 2.0 will be a warning; will remove in the future
- Importance: High, Complexity Low, Medium Issues are listed here
- Importance: Medium, Complexity Low issues are listed here; Some clarifications not listed
- Importance: Medium, Complexity Medium,High,Unknown have not been added to this list
and are not in scope - Issues sorted by importance and complexity within each category
Key:
- Banner = Issue : headline [Importance, Complexity] [NBC | M-NBC]
- H=High, M=Medium, L=Low, U=Unknown
- NBC == This is an NBC change
- M-NBC == This may be an NBC change depending on the solution
Ease of use
Many of the issues are very detailed and describe specific pain points
and use-cases that YANG 1.1 does not support.
General
- Issue 84: allow notifications/actions to appear in invalid contexts [H,L]
- Issue 92: enable if-feature statements to be "refined" into notifications and actions [H,L]
- Issue 149: Error statement for actions rpcs [H,L]
- Issue 7: Support media-type specific schema that can be used
to model error-info and other mount-points. [H,M] - Issue 126: Injection of circular imports by deviation [H,U]
- Issue 129: Enable reusability without groupings (e.g. full-include) [H,U]
- Issue 139: Clarify adding mandatory nodes with augment + when [M,L]
- Issue 131: make annotation a built-in YANG statement [M,L]
- Issue 110: Clarify canonical order in RFC 7950 [M,L]
- Issue 106: Allow "input/output" to be defined without any child data nodes [M,L]
- Issue 105: remove (deprecate) the "anyxml" statement [M,L]
- Issue 101: allow 'require-instance' to be refined [M,L]
- Issue 81: let 'description' be a substatement to 'input' and 'output' [M,L]
- Issue 60: Allowing module private groupings, typedefs [M,L]
- Issue 16: Allow when in action [M,L]
Data Types
- Issue 33: Tag YANG identity as an intermediate base for classification only [H,L]
- Issue 104: clarify "instance-required" behavior in typedefs [H,L]
- Issue 94: deref() function for leafref statements [H,L]
- Issue 146: Consistent default value behavior for operations and validation [H,L]
- Issue 34: Add native support for the float and double data types [H,M]
- Issue 56: context-independent encoding of instance-identifiers and identityref [H,M] M-NBC
- Issue 115: Clarify the meaning of properties which have default value [H,M]
- Issue 36: enable leafrefs to uniquely reference a nested list [H,U]
- Issue 72: Introduce an annotation that resolves the union member [H,U]
- Issue 83: Clarify canonical representation of typedefs [H,U]
- Issue 90: Have a mechanism to allow enums to be extended [H,U]
- Issue 138: Add new node type 'listref' [H,U]
- Issue 147: New default-system statement to indicate that the default value is
not constant (determined by the system) [M,L]
Lifecycle
- Issue 75: Deprecate "import by exact revision" [H,L] NBC
- Issue 111: Clarify whether revision-dates must be unique or not [H,L]
- Issue 130: Add 'deprecated' statement (sub-statement of status) [H,L]
- Issue 134: Apply verified errata and resolve held for document update errata [H,L]
- Issue 144: YANG 1.1 translation [H,L]
- Issue 45: Adopt the YANG Semver as mandatory-to-implement [H,U] NBC
- Issue 100: Add errata-stmt to YANG [H,U]
- Issue 59: Preliminary Status [M,L]
- Issue 28: add 'status' as a sub statement to 'module' [M,L]
API Conformance
Many issues relate to the conformance requires for a server
implementing specific YANG statements.
- Issue 27: Clarify YANG "status" keyword usage (e.g., hierarchical) [H,L]
- Issue 39: Allow deviation for description [H,L]
- Issue 44: Clarify if multiple deviations target the same schema parts [H,L]
- Issue 65: Require implementation of "status deprecated" data nodes [H,L] NBC
- Issue 69: Clarify 'deviation' substatements to match ABNF grammar [H,L]
- Issue 107: Add deviate(not-supported) support for identities [H,M]
- Issue 40: Allow deviation for identities [H,U]
- Issue 80: enable a server express conformance to a set of identifiers [H,U]
- Issue 95: Allow an module import to be defined as "types only" [H,U]
- Issue 123: Allow identities to be active even when module is not implemented [H,U]
- Issue 124: Add ability to deviate or change status of an identity [H,U]
Maybe Later
- Issue 46: Binary encoding support (lets some types have binary persistence) [H,U]
- Issue 77: Add support for a tuple type [H,H]
- Issue 148: YANG++ [H,U]
Unscored (new issues)
- Issue 150: nbc-change-stmt
- Issue 151: YANG profiles and views