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

Usefulness of limited domains #24

Closed
martinthomson opened this issue Sep 9, 2020 · 2 comments
Closed

Usefulness of limited domains #24

martinthomson opened this issue Sep 9, 2020 · 2 comments

Comments

@martinthomson
Copy link

@martinthomson martinthomson commented Sep 9, 2020

Section 4 contains a lot of subsections. Leaving Section 4.2 (content providers) aside, I can't see any requirement here other than the need to recognize that clients might use a specific resolver for a limited set of names. I think that this entire section (except 4.2) can be replaced with a sentence and no requirements.

@magicalo
Copy link

@magicalo magicalo commented Sep 9, 2020

I think another subsection is needed similar to 4.2 that describes Recursive DNS Security Providers that behave identically to the way that Content Providers are described in section 4.2. The only difference being that a security function is being provided as an outcome. Alternatively, section 4.2 can describe both CDN and DSP scenarios in a combined paragraph if that is preferred.

@chris-box
Copy link
Contributor

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

Section 4 is now removed from draft -01.

@chris-box chris-box closed this Nov 9, 2020
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

3 participants