Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow for work on different deployment models #3

Merged
merged 2 commits into from Jul 7, 2021
Merged

Conversation

martinthomson
Copy link
Member

@martinthomson martinthomson commented Jul 5, 2021

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.

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.
@martinthomson martinthomson merged commit 690f08c into main Jul 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant