Details
-
Improvement
-
Status: Resolved
-
Resolution: Done
-
None
-
None
-
None
-
None
-
Operating System: All
Platform: All
Description
Multiple users have taken up issue with the need to explicitly create structural containers. While this requirement is legitimate in and of itself, we can do much better and still be RFC6020 compliant.
As it turns out, RFC6020 defines two flavors of containers: structural and presence. The difference is flagged by the "presence" keyword, as described at http://tools.ietf.org/html/rfc6020#section-7.5.5.
It is obvious we must not perform automatic lifecycle management for presence containers, since their existence has a semantic meaning. Non-presence containers, though, are present to give the data structure and can be freely removed if they have no children.
Implementing this improvement will change the way the system behaves from the RESTCONF perspective, as empty containers will be removed automatically.
Attachments
Issue Links
- is blocked by
-
BGPCEP-278 bgp-rib possibly not ready for Change 17030
- Resolved
-
- Resolved
- is duplicated by
-
- Resolved
-
- Resolved
-
- Resolved