Navigation Menu

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

VPN requirements reduce to nothing #23

Closed
martinthomson opened this issue Sep 9, 2020 · 1 comment
Closed

VPN requirements reduce to nothing #23

martinthomson opened this issue Sep 9, 2020 · 1 comment

Comments

@martinthomson
Copy link

I think that there is just one thing that merits the inclusion of the VPN section: the ability to configure a resolver for only a subset of all names. But I don't think that introduces any requirements. The essential choice is the same: between parallel configuration for DoT/DoH or talking to the resolver directly.

In other aspects, a VPN is just a network. The fact that VPN configuration is often strongly authenticated doesn't distinguish it from any other type of network-provided resolver. I would suggest that we instead acknowledge that VPNs provide another type of network access and configuration methods that might need to be accommodated by parallel discovery methods.

@chris-box
Copy link
Contributor

VPNs are now removed from the scope of draft -01.

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

No branches or pull requests

2 participants