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.

Sign up for GitHub

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

Jump to bottom

Mention draft-ietf-dprive-padding-policy which provides guidelines #207

Merged
merged 3 commits into from Jul 25, 2018
Merged

Mention draft-ietf-dprive-padding-policy which provides guidelines #207

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4139aa8
Mention draft-ietf-dprive-padding-policy which provides guidelines
loganaden Jun 28, 2018
f334658
Update reference to padding length choice to reflect experimental sta…
loganaden Jul 25, 2018
68d5ecd
formatting fix
loganaden Jul 25, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
3 changes: 2 additions & 1 deletion draft-ietf-doh-dns-over-https-latest.mkd
View file
Open in desktop
Expand Up @@ -631,7 +631,8 @@ DNS queries.
HTTP/2 provides further advice about the use of compression
({{RFC7540}} Section 10.6) and padding ({{RFC7540}} Section 10.7 ).
DoH Servers can also add DNS padding {{RFC7830}} if the DoH client requests
it in the DNS query.
it in the DNS query. Initial attempts to offer guidance on choosing the padding
length can be found in {{draft-ietf-dprive-padding-policy}}.

The HTTPS connection provides transport security for the interaction between the
DoH server and client, but does not provide the response integrity of DNS
Expand Down