Allow for work on different deployment models #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
As noted on the list, ruling discovery completely out of bounds wasn't
the greatest thing ever for DoH.
The intent here is to explicitly keep discussion of implications in
scope, but to avoid having it overwhelm the core work by clearly
indicating that the core protocol elements take priority.
Allowing the group to discuss deployment models and document them should
help. This extends to allowing the working group to work on mechanisms
in support of those deployment models. If the group decides that there
is a viable mechanism that depends on some sort of discovery mechanism,
then the definition of the necessary mechanisms can be done under the
charter.
The usual negotiation with Area Directors about the addition of new
milestones remain in full force, so this isn't an unbounded scope. In
particular, the initial charter won't include explicit milestones for
specific work in this area.