From 4139aa8a9c75bc34f6fe70eb63dd757b841dd678 Mon Sep 17 00:00:00 2001 From: Logan Velvindron Date: Thu, 28 Jun 2018 10:30:57 +0400 Subject: [PATCH 1/3] Mention draft-ietf-dprive-padding-policy which provides guidelines on padding length which was absent from RFC 7830. --- draft-ietf-doh-dns-over-https-latest.mkd | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/draft-ietf-doh-dns-over-https-latest.mkd b/draft-ietf-doh-dns-over-https-latest.mkd index b46cca5..d8bbbfd 100644 --- a/draft-ietf-doh-dns-over-https-latest.mkd +++ b/draft-ietf-doh-dns-over-https-latest.mkd @@ -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. Additionally, guidelines for 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 From f3346587b9eb2d8bdc2162b65ca44c83e6ec9563 Mon Sep 17 00:00:00 2001 From: Loganaden Velvindron Date: Wed, 25 Jul 2018 17:22:33 +0400 Subject: [PATCH 2/3] Update reference to padding length choice to reflect experimental status. --- draft-ietf-doh-dns-over-https-latest.mkd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-doh-dns-over-https-latest.mkd b/draft-ietf-doh-dns-over-https-latest.mkd index d8bbbfd..12e288f 100644 --- a/draft-ietf-doh-dns-over-https-latest.mkd +++ b/draft-ietf-doh-dns-over-https-latest.mkd @@ -631,7 +631,7 @@ 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. Additionally, guidelines for choosing the padding length +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 From 68d5ecda75c6c9a6f0e0f2439aaa401f86d99650 Mon Sep 17 00:00:00 2001 From: Loganaden Velvindron Date: Wed, 25 Jul 2018 17:24:46 +0400 Subject: [PATCH 3/3] formatting fix --- draft-ietf-doh-dns-over-https-latest.mkd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/draft-ietf-doh-dns-over-https-latest.mkd b/draft-ietf-doh-dns-over-https-latest.mkd index 12e288f..b9e9f53 100644 --- a/draft-ietf-doh-dns-over-https-latest.mkd +++ b/draft-ietf-doh-dns-over-https-latest.mkd @@ -631,8 +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. Initial attempts to offer guidance on choosing the padding length -can be found in {{draft-ietf-dprive-padding-policy}}. +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