Uploaded image for project: 'yangtools'
  1. yangtools
  2. YANGTOOLS-373

Data tree: automatic structural container lifecycle

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Done
    • None
    • None
    • None
    • None

    • Operating System: All
      Platform: All

      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.

            rovarga Robert Varga
            rovarga Robert Varga
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: