Details

    • Type: Improvement
    • Status: New
    • Priority: Major
    • Resolution: Unresolved
    • Labels:
      None
    • Proposal:
      Hide

      Allow servers to resolve skew in whatever manner they choose. Add an informative note that a server should document their skew resolution algorithm, and that the algorithm should be predictable/repeatable.

      Drop the explicit description of the lookup algorithms.

      Future versions of the spec may choose to define specific algorithms once we have experience of them with real implementations.

      Show
      Allow servers to resolve skew in whatever manner they choose. Add an informative note that a server should document their skew resolution algorithm, and that the algorithm should be predictable/repeatable. Drop the explicit description of the lookup algorithms. Future versions of the spec may choose to define specific algorithms once we have experience of them with real implementations.

      Description

      In the current draft, a Config Mgmt server MUST provide a version resolution process using a first match in a depth-first search starting at the top of the configuration context, and MAY provide a way to find all matches.

      Neither of these two algorithms necessarily meets client needs. No implementations exist for the All Matches approach.

      The specification is overly precise, and its precision is not useful in this case.

        Attachments

          Activity

            People

            • Assignee:
              ndjc Nick Crossley
              Reporter:
              ndjc Nick Crossley
            • Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated: