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

Requirements needed in Discovery of Associated Resolvers (section 3) #4

Closed
chris-box opened this issue Sep 3, 2020 · 2 comments
Closed
Assignees
Labels

Comments

@chris-box
Copy link
Contributor

@chris-box chris-box commented Sep 3, 2020

At the moment we only have R1.1 and R1.2.

@chris-box chris-box self-assigned this Sep 3, 2020
@JoGSal
Copy link

@JoGSal JoGSal commented Oct 2, 2020

R1.3 There must be a mechanism to authenticate the entity that provides the discovered encrypted DNS resolvers
R1.4 There must be a mechanism for a user to signal to the client how to choose between equivalent and alternative resolvers.

@chris-box
Copy link
Contributor Author

@chris-box chris-box commented Nov 6, 2020

Thanks for the good contribution, but as it relates to the former scope which contained alternative resolvers, I'll close this. When a wider scope is resumed in the future something similar may be needed.

@chris-box chris-box closed this Nov 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants