From nobody Tue Jan 9 15:10:59 2018 Return-Path: X-Original-To: doh@ietfa.amsl.com Delivered-To: doh@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71F28124D68 for ; Tue, 9 Jan 2018 15:10:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.71 X-Spam-Level: X-Spam-Status: No, score=-2.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lfClFE8cj_-1 for ; Tue, 9 Jan 2018 15:10:55 -0800 (PST) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DB7112D837 for ; Tue, 9 Jan 2018 15:10:55 -0800 (PST) Received: by mail-io0-x22a.google.com with SMTP id d11so107395iog.5 for ; Tue, 09 Jan 2018 15:10:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=tDrSRrxqOsAsytUI8nQ5bUtqFGXaid0/Re+JlSRfo+Y=; b=ThqvRZTXP9R4FepW6dg6/JsAjEt7CnX/8SVYpdzb62M71FjwXqZBGRyYVt2/6r/hIt 07tzSaPwUZ/EKGfW4Iv+T0loVM629PzL7hbt5CrakKbviFR1nmmzD+6OhE/UGjr0c+u0 mlLFKKNftVlrYrEyPstYdUo55YWksWM4qiP9GwbKEKupSp4MxbuA7tTkeIIi3yN1B391 m9mM2EPRcC5jiqMfEKLC/gkdwXNQ/IbDaDjB1YuesxMsK9K8G6MWiKpHIiwSKQjweruF Ip4DePATuTZlejSx0Rkc6+rT7aAcQleDnANTop0mQomGdBhzsHuq7Nas+jjvUaY/c+pW iHRg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=tDrSRrxqOsAsytUI8nQ5bUtqFGXaid0/Re+JlSRfo+Y=; b=f1HWcNLhSGgt2c8XP9b3fI4SI5A0mxX5JJp1kPgm0C4Tqm3lPyVZ1EqLlnKqhfazoH 0x/voiNjZXKNsQz3LNZT8l+TZTI9iS+Zs9Qy16rwD6731SHUO35x5B9hGNQ2nZpyygmj aX0p1VRnIf75X+QXaV7eaVPF3SNN6uq/qAumIaTNQUvfI6Wecn6lA55sOiVf0TnTBv4n QSDiSmEEoHW+EMyRKsyxDpCwU2Y/hz87O+JJsK7k5pzClt7VGnhsh7qjPjRkuRFNNZJa MimuL6mqLud0D5AnL6UC+qdZ/zk24ZVJAkqyYNBAR6cZN3DpR6hUEFm//80SeD0uS0Fq 7RNw== X-Gm-Message-State: AKwxytegkRApQTlnS00e7Dlj1JgtZkmEj2EwJgHYliKSyJF7/4FmxRGC GqLA1BDhDPDkiK88e7qvRj1OPaRjjdTCI/CBb5u/y+r34R8= X-Google-Smtp-Source: ACJfBouZ9Uben/HGyg7G4VECpmp2UFZoaML1apdwNCGocXUEzWB24Taic+iGoVSmyLgaAbp8SClL/xbXn4/8ZZY8w+A= X-Received: by 10.107.9.100 with SMTP id j97mr3523549ioi.91.1515539453757; Tue, 09 Jan 2018 15:10:53 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.130.19 with HTTP; Tue, 9 Jan 2018 15:10:53 -0800 (PST) From: Ben Schwartz Date: Tue, 9 Jan 2018 18:10:53 -0500 Message-ID: To: doh@ietf.org Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="001a113ea8a6d35f5b056260066c" Archived-At: Subject: [Doh] Running code X-BeenThere: doh@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DNS Over HTTPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2018 23:10:57 -0000 --001a113ea8a6d35f5b056260066c Content-Type: multipart/alternative; boundary="001a113ea8a6c978f305626006e8" --001a113ea8a6c978f305626006e8 Content-Type: text/plain; charset="UTF-8" Hi DOH, As a DOH participant, I've been working on an implementation of draft-ietf-doh-dns-over-https-02, and I'm happy to report that it's now available at https://dns.google.com/experimental. For example, you can test the example from Section 5.2 by running wget ' https://dns.google.com/experimental?ct&body=q80BAAABAAAAAAAAA3d3dwdleGFtcGxlA2NvbQAAAQAB ' This service is experimental, and is not intended to support a large volume of queries. We may make compatibility-breaking changes to keep up with this working group's drafts, and we will likely shut it down (and move it to a more permanent path) if and when the working group reaches consensus on the protocol. I hope this service is useful to DOH participants who are working on clients. I also hope anyone who encounters a bug in this implementation, or a deviation from the draft, will let me know. --Ben Schwartz --001a113ea8a6c978f305626006e8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi DOH,

As a DOH participant, I've = been working on an implementation of=C2=A0draft-ietf-doh-dns-over-https-02,= and I'm happy to report that it's now available at https://dns.google.com/experimental.= =C2=A0 For example, you can test the example from Section 5.2 by running


This service is experimenta= l, and is not intended to support a large volume of queries.=C2=A0 We may m= ake compatibility-breaking changes to keep up with this working group's= drafts, and we will likely shut it down (and move it to a more permanent p= ath) if and when the working group reaches consensus on the protocol.
=

I hope this service is useful to DOH participants who a= re working on clients.=C2=A0 I also hope anyone who encounters a bug in thi= s implementation, or a deviation from the draft, will let me know.

--Ben Schwartz
--001a113ea8a6c978f305626006e8-- --001a113ea8a6d35f5b056260066c Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIS5wYJKoZIhvcNAQcCoIIS2DCCEtQCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGg ghBNMIIEXDCCA0SgAwIBAgIOSBtqDm4P/739RPqw/wcwDQYJKoZIhvcNAQELBQAwZDELMAkGA1UE BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVy c29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hBMjU2IC0gRzIwHhcNMTYwNjE1MDAwMDAwWhcNMjEw NjE1MDAwMDAwWjBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEiMCAG A1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC AQoCggEBALR23lKtjlZW/17kthzYcMHHKFgywfc4vLIjfq42NmMWbXkNUabIgS8KX4PnIFsTlD6F GO2fqnsTygvYPFBSMX4OCFtJXoikP2CQlEvO7WooyE94tqmqD+w0YtyP2IB5j4KvOIeNv1Gbnnes BIUWLFxs1ERvYDhmk+OrvW7Vd8ZfpRJj71Rb+QQsUpkyTySaqALXnyztTDp1L5d1bABJN/bJbEU3 Hf5FLrANmognIu+Npty6GrA6p3yKELzTsilOFmYNWg7L838NS2JbFOndl+ce89gM36CW7vyhszi6 6LqqzJL8MsmkP53GGhf11YMP9EkmawYouMDP/PwQYhIiUO0CAwEAAaOCASIwggEeMA4GA1UdDwEB /wQEAwIBBjAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIB ADAdBgNVHQ4EFgQUyzgSsMeZwHiSjLMhleb0JmLA4D8wHwYDVR0jBBgwFoAUJiSSix/TRK+xsBtt r+500ox4AAMwSwYDVR0fBEQwQjBAoD6gPIY6aHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9ncy9n c3BlcnNvbmFsc2lnbnB0bnJzc2hhMmcyLmNybDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIG CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzANBgkqhkiG 9w0BAQsFAAOCAQEACskdySGYIOi63wgeTmljjA5BHHN9uLuAMHotXgbYeGVrz7+DkFNgWRQ/dNse Qa4e+FeHWq2fu73SamhAQyLigNKZF7ZzHPUkSpSTjQqVzbyDaFHtRBAwuACuymaOWOWPePZXOH9x t4HPwRQuur57RKiEm1F6/YJVQ5UTkzAyPoeND/y1GzXS4kjhVuoOQX3GfXDZdwoN8jMYBZTO0H5h isymlIl6aot0E5KIKqosW6mhupdkS1ZZPp4WXR4frybSkLejjmkTYCTUmh9DuvKEQ1Ge7siwsWgA NS1Ln+uvIuObpbNaeAyMZY0U5R/OyIDaq+m9KXPYvrCZ0TCLbcKuRzCCBB4wggMGoAMCAQICCwQA AAAAATGJxkCyMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAt IFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQDEwpHbG9iYWxTaWduMB4XDTExMDgwMjEw MDAwMFoXDTI5MDMyOTEwMDAwMFowZDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g bnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVyc29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hB MjU2IC0gRzIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg/hRKosYAGP+P7mIdq5NB Kr3J0tg+8lPATlgp+F6W9CeIvnXRGUvdniO+BQnKxnX6RsC3AnE0hUUKRaM9/RDDWldYw35K+sge C8fWXvIbcYLXxWkXz+Hbxh0GXG61Evqux6i2sKeKvMr4s9BaN09cqJ/wF6KuP9jSyWcyY+IgL6u2 52my5UzYhnbf7D7IcC372bfhwM92n6r5hJx3r++rQEMHXlp/G9J3fftgsD1bzS7J/uHMFpr4MXua eoiMLV5gdmo0sQg23j4pihyFlAkkHHn4usPJ3EePw7ewQT6BUTFyvmEB+KDoi7T4RCAZDstgfpzD rR/TNwrK8/FXoqnFAgMBAAGjgegwgeUwDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8C AQEwHQYDVR0OBBYEFCYkkosf00SvsbAbba/udNKMeAADMEcGA1UdIARAMD4wPAYEVR0gADA0MDIG CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzA2BgNVHR8E LzAtMCugKaAnhiVodHRwOi8vY3JsLmdsb2JhbHNpZ24ubmV0L3Jvb3QtcjMuY3JsMB8GA1UdIwQY MBaAFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQACAFVjHihZCV/IqJYt 7Nig/xek+9g0dmv1oQNGYI1WWeqHcMAV1h7cheKNr4EOANNvJWtAkoQz+076Sqnq0Puxwymj0/+e oQJ8GRODG9pxlSn3kysh7f+kotX7pYX5moUa0xq3TCjjYsF3G17E27qvn8SJwDsgEImnhXVT5vb7 qBYKadFizPzKPmwsJQDPKX58XmPxMcZ1tG77xCQEXrtABhYC3NBhu8+c5UoinLpBQC1iBnNpNwXT Lmd4nQdf9HCijG1e8myt78VP+QSwsaDT7LVcLT2oDPVggjhVcwljw3ePDwfGP9kNrR+lc8XrfClk WbrdhC2o4Ui28dtIVHd3MIIDXzCCAkegAwIBAgILBAAAAAABIVhTCKIwDQYJKoZIhvcNAQELBQAw TDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24x EzARBgNVBAMTCkdsb2JhbFNpZ24wHhcNMDkwMzE4MTAwMDAwWhcNMjkwMzE4MTAwMDAwWjBMMSAw HgYDVQQLExdHbG9iYWxTaWduIFJvb3QgQ0EgLSBSMzETMBEGA1UEChMKR2xvYmFsU2lnbjETMBEG A1UEAxMKR2xvYmFsU2lnbjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMwldpB5Bngi FvXAg7aEyiie/QV2EcWtiHL8RgJDx7KKnQRfJMsuS+FggkbhUqsMgUdwbN1k0ev1LKMPgj0MK66X 17YUhhB5uzsTgHeMCOFJ0mpiLx9e+pZo34knlTifBtc+ycsmWQ1z3rDI6SYOgxXG71uL0gRgykmm KPZpO/bLyCiR5Z2KYVc3rHQU3HTgOu5yLy6c+9C7v/U9AOEGM+iCK65TpjoWc4zdQQ4gOsC0p6Hp sk+QLjJg6VfLuQSSaGjlOCZgdbKfd/+RFO+uIEn8rUAVSNECMWEZXriX7613t2Saer9fwRPvm2L7 DWzgVGkWqQPabumDk3F2xmmFghcCAwEAAaNCMEAwDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQF MAMBAf8wHQYDVR0OBBYEFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQBL QNvAUKr+yAzv95ZURUm7lgAJQayzE4aGKAczymvmdLm6AC2upArT9fHxD4q/c2dKg8dEe3jgr25s bwMpjjM5RcOO5LlXbKr8EpbsU8Yt5CRsuZRj+9xTaGdWPoO4zzUhw8lo/s7awlOqzJCK6fBdRoyV 3XpYKBovHd7NADdBj+1EbddTKJd+82cEHhXXipa0095MJ6RMG3NzdvQXmcIfeg7jLQitChws/zyr VQ4PkX4268NXSb7hLi18YIvDQVETI53O9zJrlAGomecsMx86OyXShkDOOyyGeMlhLxS67ttVb9+E 7gUJTb0o2HLO02JQZR7rkpeDMdmztcpHWD9fMIIEZDCCA0ygAwIBAgIMQQEYGhiBYHIQuXGiMA0G CSqGSIb3DQEBCwUAMEwxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIw IAYDVQQDExlHbG9iYWxTaWduIEhWIFMvTUlNRSBDQSAxMB4XDTE3MTIxMzE4MDA1OVoXDTE4MDYx MTE4MDA1OVowIjEgMB4GCSqGSIb3DQEJAQwRYmVtYXNjQGdvb2dsZS5jb20wggEiMA0GCSqGSIb3 DQEBAQUAA4IBDwAwggEKAoIBAQCzb38j9YDPiL9B55316U80hEufZ/Xvy8yo3b2/Hlg9DlOUS5/g pc/bPV/xjeY3pFTi26OXF+GADcXQNIYesICbjKZ2poqKyPSQPiHJAG8eGcTBacwVu5Iq+1wrWByq IlC5yQKH2symOmoI1tOUt3HmHvx6v6ZiafD8wzlr9q4gc71KMzGw16Syqn6BAlQqN1thbxYyCsLH MyeQHbrKC0SDTAnSuWajoUSwNFzmfOH/LJEdJKtrpqTjQAvuslI5qTUyeCTAi9hT1y5dWjEJ99nq x0flsIls/AK12NL1sd4mDSBiM0kTBTMU/3klX9erlNuhk/fczzOmDRvOJCuR1eC3AgMBAAGjggFu MIIBajAcBgNVHREEFTATgRFiZW1hc2NAZ29vZ2xlLmNvbTBQBggrBgEFBQcBAQREMEIwQAYIKwYB BQUHMAKGNGh0dHA6Ly9zZWN1cmUuZ2xvYmFsc2lnbi5jb20vY2FjZXJ0L2dzaHZzbWltZWNhMS5j cnQwHQYDVR0OBBYEFMuqGt+svpvW9WjvmA/qH20SyMgEMB8GA1UdIwQYMBaAFMs4ErDHmcB4koyz IZXm9CZiwOA/MEwGA1UdIARFMEMwQQYJKwYBBAGgMgEoMDQwMgYIKwYBBQUHAgEWJmh0dHBzOi8v d3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMDsGA1UdHwQ0MDIwMKAuoCyGKmh0dHA6Ly9j cmwuZ2xvYmFsc2lnbi5jb20vZ3NodnNtaW1lY2ExLmNybDAOBgNVHQ8BAf8EBAMCBaAwHQYDVR0l BBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA0GCSqGSIb3DQEBCwUAA4IBAQCycNlI1x7iQ4DAZIyb qgC1zhK07uA1x51wtkgwww3teP8P/EYOykp2CDJeXV5wVlSDnhDgvLnsBkZgI25QONeyJ4+wWFjU GonKB0FhhPn1/1bluWpkdex89g3v9DTQI25iFe30dMqM7gbAnBfLBqW7CqHJa2JFixEUHA2WP2Sc IcsHqKWD48JzSDoFST2tNdNdu3j4VhgaX+iggDDT4R7IC4rkJXhx4y3hnfVYs8pajDD4vU5ErLhd BBBc25uH+MfvdDYTogj8rstTNBCTkuwE6fct+zE/oT5PY6HSaiUt69Lp+/uRP1ijmmfIu3zFh6ZS 9Ye4z4czWTkTLH3BZ55hMYICXjCCAloCAQEwXDBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xv YmFsU2lnbiBudi1zYTEiMCAGA1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMQIMQQEYGhiB YHIQuXGiMA0GCWCGSAFlAwQCAQUAoIHUMC8GCSqGSIb3DQEJBDEiBCCBh78HxRxkKtiQUkL/DKtn mscwBJwkFmz3E39i/Y3pmjAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEP Fw0xODAxMDkyMzEwNTRaMGkGCSqGSIb3DQEJDzFcMFowCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQB FjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwCwYJKoZIhvcNAQEKMAsGCSqGSIb3DQEBBzALBglg hkgBZQMEAgEwDQYJKoZIhvcNAQEBBQAEggEAPiYJI1rQeKOSFd+BQg0tkjLrTKC/c0Pb3ZirvyJ3 lQfbXWmtVM6ZwUaRAigtlcFoC4fI+0MagAXGEaYWK6v57o/FhpyTJGcAwWYwK+zq/N9OJmV1IpJC my6Mu4CEd0HmKi2rZ+DkqIbos6CLeMNsRecYvCji6ekxhnJiC+yfEKGPPLiQtlFF76QIMtrPY76C RyPhZsW8NUJDMP1CMkoBZuaAB7Y9maUOzh4P517j6PeXxobPWgsUwMUMC1uE4X4D9WYzGD1SRsxq NngwHKaLtCpQThzMjf/yiYSh//SXMgICIP+d8vynYJazH7wO65n5z/PsbuNU8xIOtwKetkg2MA== --001a113ea8a6d35f5b056260066c-- From nobody Wed Jan 10 07:26:34 2018 Return-Path: X-Original-To: doh@ietfa.amsl.com Delivered-To: doh@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F4F7127869 for ; Wed, 10 Jan 2018 07:26:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.449 X-Spam-Level: X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HG4ZZUm_OSRQ for ; Wed, 10 Jan 2018 07:26:31 -0800 (PST) Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E318E126FDC for ; Wed, 10 Jan 2018 07:26:30 -0800 (PST) Received: by mail-lf0-x229.google.com with SMTP id e203so5483024lfg.3 for ; Wed, 10 Jan 2018 07:26:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qb7XzJM87rjZdNZF9DCQ9akn3uJ8ZXz7kv3r5DiBAfQ=; b=MPdUpmKTDkM36LtCl84zVypm6oI64uuKI1WV5kLQWtlYXuuGrALaDcK2RuaPDBac8i 3JVBruTxa0nkdT6fhYaHvOwwAvpEktd9bBKrtUSHgxVgMJ9Yqdvp+Bbi7k0ZYTPIFC1B l6QcIHp0iSXFixtmyv0wUwxx3jhDtC4ok3+m3RdYcJna2kMECinNCNrmjS23c08Ba6Kf XqbE3LSh+ei3jgDwyra2PW49W4cTgXlf9I/cngIjex4kMDZqKdvnZ/Li/3zR/Uh96vLG z5U8+8v1FwE28Q7Sj5wgof7/sMrN8T5Fw7lK3ZflepdIT0CKA6aAEixrfCz9Cj/USrTm Hm7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qb7XzJM87rjZdNZF9DCQ9akn3uJ8ZXz7kv3r5DiBAfQ=; b=hwIs5HQZTg43s+M+dHDTaP4U77FvaXK//8GSd2/luopFeK6PEkkkqFykpB1ohiyN5j YyoazQGW+Qw7X9rSoIi32s2XS+DsBLexLcBjHvirkCk92dEqCY1y8lJQp8wNrvGIzNGo xNXcyW50OJq/Ec8Rsaa7s3PsjnMep/P7iAlqNdPUrNzuZonNHuLhIKfhgPZwPDEXT+qS oG63O70ee7n4AnNcaQ1Y+9loVf5eI7NnGdwF1Fk3SSjPRNY6x5pWBaK64+o53Msyme6g FPR+ne2KQbrwYv3AC7J37hdykaxJPcaBjbNS5g0+OqDsbhO0eWEiXmoEjy7t9bJkhufw xnQg== X-Gm-Message-State: AKGB3mJP1AHBC/XVfUG764kZd0d4OGsiIe8vTKDGQLLHgiGJGGmYUq9l UlPgaFYkChRhTN/1BnjmzEF3dPOjxnl87HduuDI= X-Google-Smtp-Source: ACJfBovUrY5fjt2qeIzTmOsEywrRmSuhvhPBvmsCTy89slhdnMhvTd41X8JmqDg/PqOuATIhMwepX+9RatPTUCLQGR0= X-Received: by 10.46.27.27 with SMTP id b27mr12145140ljb.62.1515597989008; Wed, 10 Jan 2018 07:26:29 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: manu tman Date: Wed, 10 Jan 2018 15:26:17 +0000 Message-ID: To: Ben Schwartz Cc: doh@ietf.org Content-Type: multipart/alternative; boundary="94eb2c1a6476c1dc9905626da756" Archived-At: Subject: Re: [Doh] Running code X-BeenThere: doh@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DNS Over HTTPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 15:26:33 -0000 --94eb2c1a6476c1dc9905626da756 Content-Type: text/plain; charset="UTF-8" Great stuff! I tried the client and stub I implemented during IETF 100 hackathon [0] against it. After some minor changes (configurable DOH_URI and using ct instead of content-type parameter, the client (which is just performing 1 query) is working, but the stub is not. It seems that aioh2 client is not working correctly with http2 servers in general, not just dns.google.com (other than its own). I will dig into this when times permits and update the code and this list. Manu [0] https://github.com/chantra/doh-proxy On Tue, Jan 9, 2018 at 3:11 PM Ben Schwartz wrote: > Hi DOH, > > As a DOH participant, I've been working on an implementation > of draft-ietf-doh-dns-over-https-02, and I'm happy to report that it's now > available at https://dns.google.com/experimental. For example, you can > test the example from Section 5.2 by running > > wget ' > https://dns.google.com/experimental?ct&body=q80BAAABAAAAAAAAA3d3dwdleGFtcGxlA2NvbQAAAQAB > ' > > This service is experimental, and is not intended to support a large > volume of queries. We may make compatibility-breaking changes to keep up > with this working group's drafts, and we will likely shut it down (and move > it to a more permanent path) if and when the working group reaches > consensus on the protocol. > > I hope this service is useful to DOH participants who are working on > clients. I also hope anyone who encounters a bug in this implementation, > or a deviation from the draft, will let me know. > > --Ben Schwartz > _______________________________________________ > Doh mailing list > Doh@ietf.org > https://www.ietf.org/mailman/listinfo/doh > --94eb2c1a6476c1dc9905626da756 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Great stuff!

I tried the client and stub I implemented during IETF 100 hacka= thon [0] against it.
After some minor changes (confi= gurable DOH_URI and using ct instead of content-type parameter, the client = (which is just performing 1 query) is working, but the stub is not. It seem= s that aioh2 client is not working correctly with http2 servers in general,= not just dns.google.com (other than = its own). I will dig into this when times permits and update the code and t= his list.

Manu


On Tue, Jan 9, 2018= at 3:11 PM Ben Schwartz <bemasc@go= ogle.com> wrote:
Hi DOH= ,

As a DOH participant, I've been working on an impl= ementation of=C2=A0draft-ietf-doh-dns-over-https-02, and I'm happy to r= eport that it's now available at https://dns.google.com/experimental.=C2=A0 = For example, you can test the example from Section 5.2 by running


This service is = experimental, and is not intended to support a large volume of queries.=C2= =A0 We may make compatibility-breaking changes to keep up with this working= group's drafts, and we will likely shut it down (and move it to a more= permanent path) if and when the working group reaches consensus on the pro= tocol.

I hope this service is useful to DOH partic= ipants who are working on clients.=C2=A0 I also hope anyone who encounters = a bug in this implementation, or a deviation from the draft, will let me kn= ow.

--Ben Schwartz
_______________________________________________
Doh mailing list
Doh@ietf.org
https://www.ietf.org/mailman/listinfo/doh
--94eb2c1a6476c1dc9905626da756-- From nobody Thu Jan 11 12:19:30 2018 Return-Path: X-Original-To: doh@ietfa.amsl.com Delivered-To: doh@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEBD412E034 for ; Thu, 11 Jan 2018 12:19:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.748 X-Spam-Level: X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zQeoCg9OyExm for ; Thu, 11 Jan 2018 12:19:22 -0800 (PST) Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94C3F12EC3C for ; Thu, 11 Jan 2018 12:19:22 -0800 (PST) Received: by mail-qt0-x22d.google.com with SMTP id u42so3407838qte.7 for ; Thu, 11 Jan 2018 12:19:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ZgyYgL6+QuN+iKK0EOBxg9d4QNkw+v2WmWNUOWAh6rc=; b=UF4B0I+T6BUu3vXoKR58EvJtamLG4TbQMatzjFPKKmC8Tn5ePo9JCwOyyP1bejKLCX oAmW3BLGjRgIb8nrAauuuZUbGe2AhkoG/ZaEQup2d6BXfQbT6uyQWBqWQYZKxVpLCmba OCK2651lMeX+vFuT24Gjrn383NvC7AsBx5Y0Ly4vhS73GQQXHkp6YmK72YHs/wvzpTtx 4RaZ7p+SANjXRVVsbGNOXfqPXwV4faIH4R06DVj/7N+B/MgSoWxLuz66Zbe3WJ9gH4QP tvgauWMTuWkx/URCQjyA73Kn1K2T0z2gj0TmqnObN1hJHD309Wrv9ltCeZhqeoCUj/rh 41wg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ZgyYgL6+QuN+iKK0EOBxg9d4QNkw+v2WmWNUOWAh6rc=; b=B1HD1w6AKd+mT+Ifela9vsqTxLsbtpIaUIgkdJIMSz0szm8O8LgvebVdXznx7k3Y9o Zngw67a1F6PVCwyLDcuYSGdNgyYjqlnzmfnv/q3JO7sUNtPVqt2/IxJ2Il+RksZWGu0l izieCCebS8V7lIc74LtazMjqM4dYhN7mqH0svCSxoClVl3z4tsChjLPjkMS1joH4MLvZ BGnRCD3Dp8JkJaOIMC2cz//Vd2+p1dckMwCxQ1tVaZoAWZJkEecxitfid5W/I5orEunc ORYw1SvvRtDQq2aGUbu8jvesoWRdeuPUfvqNGDkCS5DMtQGCtVcWH/QUkWz0nzr550kV mnzA== X-Gm-Message-State: AKwxytf2xpkVC9GCPn//iH7fOInHwPiR7JoTVnYnXSJzsd/plqJgm+gw jA0S3hh470+NCwDNaBFLKufuhcf9+S0J2y77SNo= X-Google-Smtp-Source: ACJfBoumHj5+SXivGBmQhRgdW+Rv/q2iBxyUnC5fr+gzxeA35PTz5NQ/9U/bIEJFmPUSjV9wzs/fXaBWQGx4oGPIP3A= X-Received: by 10.200.55.227 with SMTP id e32mr1128117qtc.158.1515701961592; Thu, 11 Jan 2018 12:19:21 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.35.136 with HTTP; Thu, 11 Jan 2018 12:19:21 -0800 (PST) In-Reply-To: References: From: manu tman Date: Thu, 11 Jan 2018 12:19:21 -0800 Message-ID: To: Ben Schwartz Cc: doh@ietf.org Content-Type: multipart/alternative; boundary="001a113ee1cc0195d5056285dddf" Archived-At: Subject: Re: [Doh] Running code X-BeenThere: doh@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DNS Over HTTPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2018 20:19:25 -0000 --001a113ee1cc0195d5056285dddf Content-Type: text/plain; charset="UTF-8" Hi all, Following up on Ben's announcement of a "publicly" available DOH server, I brushed up some of the work I did during IETF 100 Hackathon and pushed the changes to https://github.com/facebookexperimental/doh-proxy . This is best effort support, but feel free to file tasks and/or submit PRs. TL;DR if you have at least python 3.5, you can get the tool from pypi directly: ``` pip3 install doh-proxy doh-stub --listen-port 5553 --domain dns.google.com --remote-address 216.58.193.78 --uri /experimental ``` And the test with `dig @127.0.0.1 -p 5553 ....` Manu On Wed, Jan 10, 2018 at 7:26 AM, manu tman wrote: > Great stuff! > > I tried the client and stub I implemented during IETF 100 hackathon [0] > against it. > After some minor changes (configurable DOH_URI and using ct instead of > content-type parameter, the client (which is just performing 1 query) is > working, but the stub is not. It seems that aioh2 client is not working > correctly with http2 servers in general, not just dns.google.com (other > than its own). I will dig into this when times permits and update the code > and this list. > > Manu > > [0] https://github.com/chantra/doh-proxy > > On Tue, Jan 9, 2018 at 3:11 PM Ben Schwartz wrote: > >> Hi DOH, >> >> As a DOH participant, I've been working on an implementation >> of draft-ietf-doh-dns-over-https-02, and I'm happy to report that it's >> now available at https://dns.google.com/experimental. For example, you >> can test the example from Section 5.2 by running >> >> wget 'https://dns.google.com/experimental?ct&body= >> q80BAAABAAAAAAAAA3d3dwdleGFtcGxlA2NvbQAAAQAB' >> >> This service is experimental, and is not intended to support a large >> volume of queries. We may make compatibility-breaking changes to keep up >> with this working group's drafts, and we will likely shut it down (and move >> it to a more permanent path) if and when the working group reaches >> consensus on the protocol. >> >> I hope this service is useful to DOH participants who are working on >> clients. I also hope anyone who encounters a bug in this implementation, >> or a deviation from the draft, will let me know. >> >> --Ben Schwartz >> _______________________________________________ >> Doh mailing list >> Doh@ietf.org >> https://www.ietf.org/mailman/listinfo/doh >> > --001a113ee1cc0195d5056285dddf Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

Following up on Ben's annou= ncement of a "publicly" available DOH server, I brushed up some o= f the work I did during IETF 100 Hackathon and pushed the changes to=C2=A0<= a href=3D"https://github.com/facebookexperimental/doh-proxy">https://github= .com/facebookexperimental/doh-proxy . This is best effort support, but = feel free to file tasks and/or submit PRs.

TL;DR i= f you have at least python 3.5, you can get the tool from pypi directly:
```
pip3 install doh-proxy
doh-stub=C2=A0 --lis= ten-port 5553 --domain dns.google.com= --remote-address 216.58.193.78 --uri /experimental
```

And the t= est with `dig @127.0.0.1 -p 5553 ....`
=
Manu

On Wed, Jan 10, 2018 at 7:26 AM, manu tman <chantr4@gmail.com> wrote:
Great= stuff!

I tried the clie= nt and stub I implemented during IETF 100 hackathon [0] against it.
After some minor changes (configurable DOH_URI and using ct= instead of content-type parameter, the client (which is just performing 1 = query) is working, but the stub is not. It seems that aioh2 client is not w= orking correctly with http2 servers in general, not just dns.google.com (other than its own). = I will dig into this when times permits and update the code and this list.<= /div>

Manu


Hi DOH,

As a DOH participant, I've been work= ing on an implementation of=C2=A0draft-ietf-doh-dns-over-https-02, and= I'm happy to report that it's now available at https://dns.google.com/= experimental.=C2=A0 For example, you can test the example from Section = 5.2 by running

wget 'https://dns.google.com/experimental?ct&bo= dy=3Dq80BAAABAAAAAAAAA3d3dwdleGFtcGxlA2NvbQAAAQAB'

This service is experimental, and is not intended to= support a large volume of queries.=C2=A0 We may make compatibility-breakin= g changes to keep up with this working group's drafts, and we will like= ly shut it down (and move it to a more permanent path) if and when the work= ing group reaches consensus on the protocol.

I hop= e this service is useful to DOH participants who are working on clients.=C2= =A0 I also hope anyone who encounters a bug in this implementation, or a de= viation from the draft, will let me know.

--Ben Sc= hwartz
_______________________________________________
Doh mailing list
Doh@ietf.org
https://www.ietf.org/mailman/listinfo/doh

--001a113ee1cc0195d5056285dddf-- From nobody Thu Jan 11 12:47:21 2018 Return-Path: X-Original-To: doh@ietfa.amsl.com Delivered-To: doh@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B57E612EC41 for ; Thu, 11 Jan 2018 12:47:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.709 X-Spam-Level: X-Spam-Status: No, score=-2.709 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hK-NxWW4fUOo for ; Thu, 11 Jan 2018 12:47:17 -0800 (PST) Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BBA0127444 for ; Thu, 11 Jan 2018 12:47:17 -0800 (PST) Received: by mail-it0-x22f.google.com with SMTP id p124so6668064ite.1 for ; Thu, 11 Jan 2018 12:47:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=J2KEOcotLAookVl/tTF4lOsXx9VIANSSmlEVLTMUtno=; b=g3ey/eF+75+6w/Lz0IJnFAjnKoB4hGGWPuARS1d3dJ5rhKrCXpDR/sd6eAaVjhZb6k QCbH1DXDFdtJf/nUYGnkBBx7gO/xxZYLWkNvm8npD8sDrNkClcUo7X0KQLn5mdl8gCNF oGDAwgMXyH2Pxy+9dGT+YoSnOCFHDcPdTNsJqnZEb+xhf/auwD2ghUEMQx8XPXysxW8f LGm9x8GLhA2ZWYDHLWGB09GXmCO37iz2zj6+/RaTx1+OEJSNvv+5fnz8wBD3JDEiW4Rn 5GusvgK4dxXK2Pwa29g8IuEjmDNbGE2rVKwn0mF8O2OC8zy/nGf6nY9CG7sagNL2tCFj TNYQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=J2KEOcotLAookVl/tTF4lOsXx9VIANSSmlEVLTMUtno=; b=IJXPVB5Da3urld3UfhQqZxKyEcdXupKdmJ/OdVZ9jSzMQR0U+cZTAwcVyaKgB1u4mf YkOGrJF8NJjBqIvReMo/PY5fExpaK4OZgcxJA95Uu617/EdxQgwkqNbcnz5lqZf36QKl rkTiLTurzkRwFa0xLzGzlwWU0GpwPpB2jiNv9b+O4F9lRq3vTTW6MsDoaWaRlyeVoy35 RfAZBIs0C990goBvLwB7VR4xlyXsgQjYcv4KPEWGrFFvCarnkbbcSVU8H8ZNYinx0TxO WEi7nPFGXB4juEUKjggAJ+Y/4xK69KK2/KwRk8vNy79/doI8TQoCjnYCqsh73+aISDdA Sfwg== X-Gm-Message-State: AKwxytded5OpEOhHqC/Y75D+sKtTAcV93FcdlqQLCuHUhcBV4wvmM4to xyW5CMoSVDUWOFrO8PpDujkEyZphny5az5rWzJBerA== X-Google-Smtp-Source: ACJfBosp90sWjlVurUWnSs6xM4zj9ekZ7bgDKJKjgdcnb5q0E6mdwTkuoT7O+D4qVvA1zXu/3UZWL8upwo909NnvMYs= X-Received: by 10.36.114.149 with SMTP id x143mr2841687itc.82.1515703636047; Thu, 11 Jan 2018 12:47:16 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.160.200 with HTTP; Thu, 11 Jan 2018 12:47:15 -0800 (PST) In-Reply-To: References: From: Ben Schwartz Date: Thu, 11 Jan 2018 15:47:15 -0500 Message-ID: To: manu tman Cc: doh@ietf.org Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="001a11450d60d9d388056286403e" Archived-At: Subject: Re: [Doh] Running code X-BeenThere: doh@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DNS Over HTTPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2018 20:47:20 -0000 --001a11450d60d9d388056286403e Content-Type: multipart/alternative; boundary="001a11450d60d041670562864015" --001a11450d60d041670562864015 Content-Type: text/plain; charset="UTF-8" Very cool! On Thu, Jan 11, 2018 at 3:19 PM, manu tman wrote: > Hi all, > > Following up on Ben's announcement of a "publicly" available DOH server, I > brushed up some of the work I did during IETF 100 Hackathon and pushed the > changes to https://github.com/facebookexperimental/doh-proxy . This is > best effort support, but feel free to file tasks and/or submit PRs. > > TL;DR if you have at least python 3.5, you can get the tool from pypi > directly: > ``` > pip3 install doh-proxy > doh-stub --listen-port 5553 --domain dns.google.com --remote-address > 216.58.193.78 --uri /experimental > ``` > > And the test with `dig @127.0.0.1 -p 5553 ....` > > Manu > > On Wed, Jan 10, 2018 at 7:26 AM, manu tman wrote: > >> Great stuff! >> >> I tried the client and stub I implemented during IETF 100 hackathon [0] >> against it. >> After some minor changes (configurable DOH_URI and using ct instead of >> content-type parameter, the client (which is just performing 1 query) is >> working, but the stub is not. It seems that aioh2 client is not working >> correctly with http2 servers in general, not just dns.google.com (other >> than its own). I will dig into this when times permits and update the code >> and this list. >> >> Manu >> >> [0] https://github.com/chantra/doh-proxy >> >> On Tue, Jan 9, 2018 at 3:11 PM Ben Schwartz wrote: >> >>> Hi DOH, >>> >>> As a DOH participant, I've been working on an implementation >>> of draft-ietf-doh-dns-over-https-02, and I'm happy to report that it's >>> now available at https://dns.google.com/experimental. For example, you >>> can test the example from Section 5.2 by running >>> >>> wget 'https://dns.google.com/experimental?ct&body=q80BAAABAAAAAAA >>> AA3d3dwdleGFtcGxlA2NvbQAAAQAB' >>> >>> This service is experimental, and is not intended to support a large >>> volume of queries. We may make compatibility-breaking changes to keep up >>> with this working group's drafts, and we will likely shut it down (and move >>> it to a more permanent path) if and when the working group reaches >>> consensus on the protocol. >>> >>> I hope this service is useful to DOH participants who are working on >>> clients. I also hope anyone who encounters a bug in this implementation, >>> or a deviation from the draft, will let me know. >>> >>> --Ben Schwartz >>> _______________________________________________ >>> Doh mailing list >>> Doh@ietf.org >>> https://www.ietf.org/mailman/listinfo/doh >>> >> > --001a11450d60d041670562864015 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Very cool!

On Thu, Jan 11, 2018 at 3:19 PM, manu tman <chantr4@gmail= .com> wrote:
Hi all,

Following up on Ben's announcement of a &= quot;publicly" available DOH server, I brushed up some of the work I d= id during IETF 100 Hackathon and pushed the changes to=C2=A0https://gi= thub.com/facebookexperimental/doh-proxy . This is best effort supp= ort, but feel free to file tasks and/or submit PRs.

TL;DR if you have at least python 3.5, you can get the tool from pypi dir= ectly:
```
pip3 install doh-proxy
doh-stub=C2= =A0 --listen-port 5553 --domain dns.google.com --remote-address 216.58.193.78 --uri /experimen= tal
```

And the test with `dig @127.0.0.1 -p 5553 ....`

Manu

O= n Wed, Jan 10, 2018 at 7:26 AM, manu tman <chantr4@gmail.com> wrote:
Great stu= ff!

I tried the client a= nd stub I implemented during IETF 100 hackathon [0] against it.
After some minor changes (configurable DOH_URI and using ct ins= tead of content-type parameter, the client (which is just performing 1 quer= y) is working, but the stub is not. It seems that aioh2 client is not worki= ng correctly with http2 servers in general, not just dns.google.com (other than its own). I wi= ll dig into this when times permits and update the code and this list.

Manu
=
[0]=C2=A0https://github.com/chantra/doh-proxy<= /div>

On Tue, Jan 9, 2018 at 3:11 PM Ben Schwa= rtz <bemasc@googl= e.com> wrote:
Hi DOH,

= As a DOH participant, I've been working on an implementation of=C2=A0dr= aft-ietf-doh-dns-over-https-02, and I'm happy to report that it= 9;s now available at https://dns.google.com/experimental.=C2=A0 For example= , you can test the example from Section 5.2 by running

=

This service is= experimental, and is not intended to support a large volume of queries.=C2= =A0 We may make compatibility-breaking changes to keep up with this working= group's drafts, and we will likely shut it down (and move it to a more= permanent path) if and when the working group reaches consensus on the pro= tocol.

I hope this service is useful to DOH partic= ipants who are working on clients.=C2=A0 I also hope anyone who encounters = a bug in this implementation, or a deviation from the draft, will let me kn= ow.

--Ben Schwartz
_______________________________________________
Doh mailing list
Doh@ietf.org
https://www.ietf.org/mailman/listinfo/doh


--001a11450d60d041670562864015-- --001a11450d60d9d388056286403e Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIS5wYJKoZIhvcNAQcCoIIS2DCCEtQCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGg ghBNMIIEXDCCA0SgAwIBAgIOSBtqDm4P/739RPqw/wcwDQYJKoZIhvcNAQELBQAwZDELMAkGA1UE BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVy c29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hBMjU2IC0gRzIwHhcNMTYwNjE1MDAwMDAwWhcNMjEw NjE1MDAwMDAwWjBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEiMCAG A1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC AQoCggEBALR23lKtjlZW/17kthzYcMHHKFgywfc4vLIjfq42NmMWbXkNUabIgS8KX4PnIFsTlD6F GO2fqnsTygvYPFBSMX4OCFtJXoikP2CQlEvO7WooyE94tqmqD+w0YtyP2IB5j4KvOIeNv1Gbnnes BIUWLFxs1ERvYDhmk+OrvW7Vd8ZfpRJj71Rb+QQsUpkyTySaqALXnyztTDp1L5d1bABJN/bJbEU3 Hf5FLrANmognIu+Npty6GrA6p3yKELzTsilOFmYNWg7L838NS2JbFOndl+ce89gM36CW7vyhszi6 6LqqzJL8MsmkP53GGhf11YMP9EkmawYouMDP/PwQYhIiUO0CAwEAAaOCASIwggEeMA4GA1UdDwEB /wQEAwIBBjAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIB ADAdBgNVHQ4EFgQUyzgSsMeZwHiSjLMhleb0JmLA4D8wHwYDVR0jBBgwFoAUJiSSix/TRK+xsBtt r+500ox4AAMwSwYDVR0fBEQwQjBAoD6gPIY6aHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9ncy9n c3BlcnNvbmFsc2lnbnB0bnJzc2hhMmcyLmNybDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIG CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzANBgkqhkiG 9w0BAQsFAAOCAQEACskdySGYIOi63wgeTmljjA5BHHN9uLuAMHotXgbYeGVrz7+DkFNgWRQ/dNse Qa4e+FeHWq2fu73SamhAQyLigNKZF7ZzHPUkSpSTjQqVzbyDaFHtRBAwuACuymaOWOWPePZXOH9x t4HPwRQuur57RKiEm1F6/YJVQ5UTkzAyPoeND/y1GzXS4kjhVuoOQX3GfXDZdwoN8jMYBZTO0H5h isymlIl6aot0E5KIKqosW6mhupdkS1ZZPp4WXR4frybSkLejjmkTYCTUmh9DuvKEQ1Ge7siwsWgA NS1Ln+uvIuObpbNaeAyMZY0U5R/OyIDaq+m9KXPYvrCZ0TCLbcKuRzCCBB4wggMGoAMCAQICCwQA AAAAATGJxkCyMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAt IFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQDEwpHbG9iYWxTaWduMB4XDTExMDgwMjEw MDAwMFoXDTI5MDMyOTEwMDAwMFowZDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g bnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVyc29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hB MjU2IC0gRzIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg/hRKosYAGP+P7mIdq5NB Kr3J0tg+8lPATlgp+F6W9CeIvnXRGUvdniO+BQnKxnX6RsC3AnE0hUUKRaM9/RDDWldYw35K+sge C8fWXvIbcYLXxWkXz+Hbxh0GXG61Evqux6i2sKeKvMr4s9BaN09cqJ/wF6KuP9jSyWcyY+IgL6u2 52my5UzYhnbf7D7IcC372bfhwM92n6r5hJx3r++rQEMHXlp/G9J3fftgsD1bzS7J/uHMFpr4MXua eoiMLV5gdmo0sQg23j4pihyFlAkkHHn4usPJ3EePw7ewQT6BUTFyvmEB+KDoi7T4RCAZDstgfpzD rR/TNwrK8/FXoqnFAgMBAAGjgegwgeUwDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8C AQEwHQYDVR0OBBYEFCYkkosf00SvsbAbba/udNKMeAADMEcGA1UdIARAMD4wPAYEVR0gADA0MDIG CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzA2BgNVHR8E LzAtMCugKaAnhiVodHRwOi8vY3JsLmdsb2JhbHNpZ24ubmV0L3Jvb3QtcjMuY3JsMB8GA1UdIwQY MBaAFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQACAFVjHihZCV/IqJYt 7Nig/xek+9g0dmv1oQNGYI1WWeqHcMAV1h7cheKNr4EOANNvJWtAkoQz+076Sqnq0Puxwymj0/+e oQJ8GRODG9pxlSn3kysh7f+kotX7pYX5moUa0xq3TCjjYsF3G17E27qvn8SJwDsgEImnhXVT5vb7 qBYKadFizPzKPmwsJQDPKX58XmPxMcZ1tG77xCQEXrtABhYC3NBhu8+c5UoinLpBQC1iBnNpNwXT Lmd4nQdf9HCijG1e8myt78VP+QSwsaDT7LVcLT2oDPVggjhVcwljw3ePDwfGP9kNrR+lc8XrfClk WbrdhC2o4Ui28dtIVHd3MIIDXzCCAkegAwIBAgILBAAAAAABIVhTCKIwDQYJKoZIhvcNAQELBQAw TDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24x EzARBgNVBAMTCkdsb2JhbFNpZ24wHhcNMDkwMzE4MTAwMDAwWhcNMjkwMzE4MTAwMDAwWjBMMSAw HgYDVQQLExdHbG9iYWxTaWduIFJvb3QgQ0EgLSBSMzETMBEGA1UEChMKR2xvYmFsU2lnbjETMBEG A1UEAxMKR2xvYmFsU2lnbjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMwldpB5Bngi FvXAg7aEyiie/QV2EcWtiHL8RgJDx7KKnQRfJMsuS+FggkbhUqsMgUdwbN1k0ev1LKMPgj0MK66X 17YUhhB5uzsTgHeMCOFJ0mpiLx9e+pZo34knlTifBtc+ycsmWQ1z3rDI6SYOgxXG71uL0gRgykmm KPZpO/bLyCiR5Z2KYVc3rHQU3HTgOu5yLy6c+9C7v/U9AOEGM+iCK65TpjoWc4zdQQ4gOsC0p6Hp sk+QLjJg6VfLuQSSaGjlOCZgdbKfd/+RFO+uIEn8rUAVSNECMWEZXriX7613t2Saer9fwRPvm2L7 DWzgVGkWqQPabumDk3F2xmmFghcCAwEAAaNCMEAwDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQF MAMBAf8wHQYDVR0OBBYEFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQBL QNvAUKr+yAzv95ZURUm7lgAJQayzE4aGKAczymvmdLm6AC2upArT9fHxD4q/c2dKg8dEe3jgr25s bwMpjjM5RcOO5LlXbKr8EpbsU8Yt5CRsuZRj+9xTaGdWPoO4zzUhw8lo/s7awlOqzJCK6fBdRoyV 3XpYKBovHd7NADdBj+1EbddTKJd+82cEHhXXipa0095MJ6RMG3NzdvQXmcIfeg7jLQitChws/zyr VQ4PkX4268NXSb7hLi18YIvDQVETI53O9zJrlAGomecsMx86OyXShkDOOyyGeMlhLxS67ttVb9+E 7gUJTb0o2HLO02JQZR7rkpeDMdmztcpHWD9fMIIEZDCCA0ygAwIBAgIMQQEYGhiBYHIQuXGiMA0G CSqGSIb3DQEBCwUAMEwxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIw IAYDVQQDExlHbG9iYWxTaWduIEhWIFMvTUlNRSBDQSAxMB4XDTE3MTIxMzE4MDA1OVoXDTE4MDYx MTE4MDA1OVowIjEgMB4GCSqGSIb3DQEJAQwRYmVtYXNjQGdvb2dsZS5jb20wggEiMA0GCSqGSIb3 DQEBAQUAA4IBDwAwggEKAoIBAQCzb38j9YDPiL9B55316U80hEufZ/Xvy8yo3b2/Hlg9DlOUS5/g pc/bPV/xjeY3pFTi26OXF+GADcXQNIYesICbjKZ2poqKyPSQPiHJAG8eGcTBacwVu5Iq+1wrWByq IlC5yQKH2symOmoI1tOUt3HmHvx6v6ZiafD8wzlr9q4gc71KMzGw16Syqn6BAlQqN1thbxYyCsLH MyeQHbrKC0SDTAnSuWajoUSwNFzmfOH/LJEdJKtrpqTjQAvuslI5qTUyeCTAi9hT1y5dWjEJ99nq x0flsIls/AK12NL1sd4mDSBiM0kTBTMU/3klX9erlNuhk/fczzOmDRvOJCuR1eC3AgMBAAGjggFu MIIBajAcBgNVHREEFTATgRFiZW1hc2NAZ29vZ2xlLmNvbTBQBggrBgEFBQcBAQREMEIwQAYIKwYB BQUHMAKGNGh0dHA6Ly9zZWN1cmUuZ2xvYmFsc2lnbi5jb20vY2FjZXJ0L2dzaHZzbWltZWNhMS5j cnQwHQYDVR0OBBYEFMuqGt+svpvW9WjvmA/qH20SyMgEMB8GA1UdIwQYMBaAFMs4ErDHmcB4koyz IZXm9CZiwOA/MEwGA1UdIARFMEMwQQYJKwYBBAGgMgEoMDQwMgYIKwYBBQUHAgEWJmh0dHBzOi8v d3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMDsGA1UdHwQ0MDIwMKAuoCyGKmh0dHA6Ly9j cmwuZ2xvYmFsc2lnbi5jb20vZ3NodnNtaW1lY2ExLmNybDAOBgNVHQ8BAf8EBAMCBaAwHQYDVR0l BBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA0GCSqGSIb3DQEBCwUAA4IBAQCycNlI1x7iQ4DAZIyb qgC1zhK07uA1x51wtkgwww3teP8P/EYOykp2CDJeXV5wVlSDnhDgvLnsBkZgI25QONeyJ4+wWFjU GonKB0FhhPn1/1bluWpkdex89g3v9DTQI25iFe30dMqM7gbAnBfLBqW7CqHJa2JFixEUHA2WP2Sc IcsHqKWD48JzSDoFST2tNdNdu3j4VhgaX+iggDDT4R7IC4rkJXhx4y3hnfVYs8pajDD4vU5ErLhd BBBc25uH+MfvdDYTogj8rstTNBCTkuwE6fct+zE/oT5PY6HSaiUt69Lp+/uRP1ijmmfIu3zFh6ZS 9Ye4z4czWTkTLH3BZ55hMYICXjCCAloCAQEwXDBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xv YmFsU2lnbiBudi1zYTEiMCAGA1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMQIMQQEYGhiB YHIQuXGiMA0GCWCGSAFlAwQCAQUAoIHUMC8GCSqGSIb3DQEJBDEiBCB8ggfDeGpZLpjpmNnBL5M1 Wfm6yuruF/9GVpdKcFJWZDAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEP Fw0xODAxMTEyMDQ3MTZaMGkGCSqGSIb3DQEJDzFcMFowCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQB FjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwCwYJKoZIhvcNAQEKMAsGCSqGSIb3DQEBBzALBglg hkgBZQMEAgEwDQYJKoZIhvcNAQEBBQAEggEALeJNAJj0Lnq39VqFRe+7BgCuK5mrFAuLZGMavzmY QgRjAPpWPrhOGTrz0MzTfBi6eoJXo+jyJ/3bWEHUXZ4HCM1GRnnV7Evo+WFbhQbSosKEO7C+UYcN sWFbouutMCzYLCKgc48EMitXwAHTTd+ml/oWcvleIRgoQWt2LrHH84h+AFhFF/M0BidUYHcIlgdV FmP8s7q78Hrkber8Cj0WLr6pKIXlvQUkN5Rb/tQIwtHKgFKlTqaIqG1hPnDLSrahj5rYYH6jCiz9 dpmKzEzTHBwvk5NBsLdpOG3nrTIxQnZvqAOuWNQpfcgjoKDRuXx2dLusoPWiiAejseAOgEaKpw== --001a11450d60d9d388056286403e-- From minami.hiroy@gmail.com Fri Jan 12 10:08:03 2018 Return-Path: X-Original-To: doh@ietfa.amsl.com Delivered-To: doh@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3D3512785F for ; Fri, 12 Jan 2018 10:08:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7apve-0z5gj7 for ; Fri, 12 Jan 2018 10:07:54 -0800 (PST) Received: from mail-ot0-x231.google.com (mail-ot0-x231.google.com [IPv6:2607:f8b0:4003:c0f::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13F9F12D856 for ; Fri, 12 Jan 2018 10:07:54 -0800 (PST) Received: by mail-ot0-x231.google.com with SMTP id f6so5737974oti.13 for ; Fri, 12 Jan 2018 10:07:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Cgnpzij2EZXVhBuQCTjGLAbUQrWpCtlgSwpqzlKSOeQ=; b=aeT1W1E9rA3YlVn07ZVUNz58uZe9TfCp+BmHVTtv7iv/JOSdN+/hmjdnmfbwbYLczd YeqNCquKn3QJeyAMEzuSLIGtTE/8abUPg6jZYXd2Cgo3Kj8dndwLPbz0rQZJuHnlhpdt jes85aGQ6COQQtQZ7SAf205OawODHgqqrhQgAwdnbdfBPcOYd0/8j+3+OWTvObyc98wD eicLFcS0TD4O5Lr1k6Yul2Cj6FkCEPLAshpRCe5kV/oac5p6n4QfiK7f1C685q/mQ5oM Jh5hGQPMWbWa5GLlmtwk3jQWJgkyvG1qPOn6LM5SUABkqITO9FafBuM5bgINypbpqpNI p8WQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Cgnpzij2EZXVhBuQCTjGLAbUQrWpCtlgSwpqzlKSOeQ=; b=iUZvUNdfEfH17/crOX6P2Uil+BqZo3l6HQS4Rxcab9nrQ2juQ2lmJhHNDZNxEef/8G oU7CaW8XTeu2um70iyeVvJXA+poHAltZs+oTtWkRmL8zs6sTxd64KaidRWqD4vQ+gUcm NIVlk5+F2oFjzZQFjylb/aAbC/ItYORL6TSpJd4AQMHbLiYDTnm+MiprEgUwD6r0QqEt NG1f14PIShbRwuhurdmYr0fVK+xOL34woYlWQ6MGb2JTSwZURiY0pPrcAT4d57XSZp/S a+B6ZboG9o2LipcG6uCergWKTABKg/XippU1azcrD+VPHq+AjZ6rsJ4TuPFmTGt64Pcm hqTw== X-Gm-Message-State: AKwxytd/y0hxhmrYajW1KBxY27l0XUTqOcapF8lk+5N0/UzGKHexNhFB ofj4fjVkkZh/3cmd1Ii3I2j+jbCbXbEHVo64x2xWsg== X-Google-Smtp-Source: ACJfBovCjZWFO6o59+9BxXOwj7oaI7QM4dqyUNh/Vc2ruCe+X+s6ity9RCcy6eoqdB+W0Ys7jYY4CW97lK1tCMg23fU= X-Received: by 10.157.81.69 with SMTP id u5mr15938159oti.20.1515780473125; Fri, 12 Jan 2018 10:07:53 -0800 (PST) MIME-Version: 1.0 Received: by 10.74.144.232 with HTTP; Fri, 12 Jan 2018 10:07:52 -0800 (PST) From: - goto Date: Sat, 13 Jan 2018 03:07:52 +0900 Message-ID: To: doh@ietf.org Content-Type: multipart/alternative; boundary="001a114f1e26a880d50562982440" Archived-At: Subject: Re: [Doh] Running code X-BeenThere: doh@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DNS Over HTTPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2018 18:26:29 -0000 --001a114f1e26a880d50562982440 Content-Type: text/plain; charset="UTF-8" Hi Ben Schwartz and DOH wg folks https://dns.google.com/experimental is great work ! so, I have a question about error handlings. if client sends an invalid request like a below, Server responses a html (Content-Type: text/html) to Client. curl "https://dns.google.com/experimental?ct&body=Invalid" -H "accept:application/dns-udpwireformat, application/simpledns+json" I think there are some options - request with "accept: */*" : server can responses a html with 400 status code - request with "accept:application/dns-udpwireformat" : server responses dns response with rcode=1 (HTTP status code is ???) if my understanding is correct, It is not written in the specification draft-02. In any case, I think clarifying error handlings (and reration between HTTP status code and DNS rcode) is reasonable in the spec. Is this out of scope of the spec? thanks, Yuki --001a114f1e26a880d50562982440 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0Ben Schwartz and DO= H wg folks

= https://dns.google.com/experimental=C2=A0is great = work !

s= o, I have a question about error handlings.

if cli= ent sends an invalid request like a below, Server responses a html (Content= -Type: text/html) to Client.
curl "https://dns.google.com/experim= ental?ct&body=3DInvalid" -H "accept:application/dns-udpwi= reformat, application/simpledns+json"

I think= there are some options
- request with "accept: */*" : = server can responses a html with 400 status code
- request with &= quot;accept:application/dns-udpwireformat" : server responses dns resp= onse with rcode=3D1 (HTTP status code is ???)

if my understanding is correct,=C2=A0It is not written in the specificatio= n draft-02.

In any case, I think clarifying error = handlings (and reration between HTTP status code and DNS rcode) is reasonab= le in the spec. Is this out of scope of the spec?

thanks,

Yuki
--001a114f1e26a880d50562982440-- From nobody Mon Jan 15 02:54:00 2018 Return-Path: X-Original-To: doh@ietfa.amsl.com Delivered-To: doh@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CA671205D3 for ; Mon, 15 Jan 2018 02:53:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.21 X-Spam-Level: X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HAP3kZoR2_tt for ; Mon, 15 Jan 2018 02:53:56 -0800 (PST) Received: from giant.haxx.se (www.haxx.se [IPv6:2a00:1a28:1200:9::2]) by ietfa.amsl.com (Postfix) with ESMTP id DD4261243FE for ; Mon, 15 Jan 2018 02:53:55 -0800 (PST) Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by giant.haxx.se (8.15.2/8.15.2/Debian-4) with ESMTPS id w0FArpjZ015455 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 15 Jan 2018 11:53:51 +0100 Received: from localhost (dast@localhost) by giant.haxx.se (8.15.2/8.15.2/Submit) with ESMTP id w0FArp6p015450; Mon, 15 Jan 2018 11:53:51 +0100 X-Authentication-Warning: giant.haxx.se: dast owned process doing -bs Date: Mon, 15 Jan 2018 11:53:51 +0100 (CET) From: Daniel Stenberg X-X-Sender: dast@giant.haxx.se To: Ben Schwartz cc: doh@ietf.org In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (DEB 67 2015-01-07) X-fromdanielhimself: yes MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII Archived-At: Subject: Re: [Doh] Running code X-BeenThere: doh@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DNS Over HTTPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jan 2018 10:53:58 -0000 On Tue, 9 Jan 2018, Ben Schwartz wrote: > available at https://dns.google.com/experimental. Lovely, thanks! It matches the behavior my code expects for both GET and POST... -- / daniel.haxx.se From nobody Mon Jan 15 06:40:23 2018 Return-Path: X-Original-To: doh@ietfa.amsl.com Delivered-To: doh@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E9C012D7EC for ; Mon, 15 Jan 2018 06:40:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.909 X-Spam-Level: X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nGGr5U9gF6rz for ; Mon, 15 Jan 2018 06:40:20 -0800 (PST) Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF2AB120227 for ; Mon, 15 Jan 2018 06:40:19 -0800 (PST) Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 9A16F28144D; Mon, 15 Jan 2018 15:40:17 +0100 (CET) Received: by mx4.nic.fr (Postfix, from userid 500) id 945BF2814A0; Mon, 15 Jan 2018 15:40:17 +0100 (CET) Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [IPv6:2001:67c:2218:15::11]) by mx4.nic.fr (Postfix) with ESMTP id 8DCD528144D; Mon, 15 Jan 2018 15:40:17 +0100 (CET) Received: from b12.nic.fr (b12.users.prive.nic.fr [10.10.86.133]) by relay01.prive.nic.fr (Postfix) with ESMTP id 8AE086423521; Mon, 15 Jan 2018 15:40:17 +0100 (CET) Received: by b12.nic.fr (Postfix, from userid 1000) id D07524001C; Mon, 15 Jan 2018 15:40:12 +0100 (CET) Date: Mon, 15 Jan 2018 15:40:12 +0100 From: Stephane Bortzmeyer To: Ben Schwartz Cc: doh@ietf.org Message-ID: <20180115144012.i5h3wdsl4gqzdxei@nic.fr> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: Debian GNU/Linux 9.3 X-Kernel: Linux 4.9.0-5-amd64 x86_64 X-Charlie: Je suis Charlie Organization: NIC France X-URL: http://www.nic.fr/ User-Agent: NeoMutt/20170113 (1.7.2) X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=1.2.2 X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2018.1.15.143316 Archived-At: Subject: Re: [Doh] Running code X-BeenThere: doh@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DNS Over HTTPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jan 2018 14:40:22 -0000 On Tue, Jan 09, 2018 at 06:10:53PM -0500, Ben Schwartz wrote a message of 163 lines which said: > As a DOH participant, I've been working on an implementation > of draft-ietf-doh-dns-over-https-02, Great. Do note there are people who would like to work on DoH at the London hackathon. Volunteers welcome From nobody Mon Jan 15 12:36:55 2018 Return-Path: X-Original-To: doh@ietfa.amsl.com Delivered-To: doh@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9251A12D77B for ; Mon, 15 Jan 2018 12:36:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.21 X-Spam-Level: X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IhNBMHWH4rpp for ; Mon, 15 Jan 2018 12:36:51 -0800 (PST) Received: from giant.haxx.se (www.haxx.se [IPv6:2a00:1a28:1200:9::2]) by ietfa.amsl.com (Postfix) with ESMTP id 7E5E6129C6B for ; Mon, 15 Jan 2018 12:36:50 -0800 (PST) Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by giant.haxx.se (8.15.2/8.15.2/Debian-4) with ESMTPS id w0FKalYk001332 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 15 Jan 2018 21:36:47 +0100 Received: from localhost (dast@localhost) by giant.haxx.se (8.15.2/8.15.2/Submit) with ESMTP id w0FKalkF001280; Mon, 15 Jan 2018 21:36:47 +0100 X-Authentication-Warning: giant.haxx.se: dast owned process doing -bs Date: Mon, 15 Jan 2018 21:36:47 +0100 (CET) From: Daniel Stenberg X-X-Sender: dast@giant.haxx.se To: Stephane Bortzmeyer cc: doh@ietf.org In-Reply-To: <20180115144012.i5h3wdsl4gqzdxei@nic.fr> Message-ID: References: <20180115144012.i5h3wdsl4gqzdxei@nic.fr> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) X-fromdanielhimself: yes MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Archived-At: Subject: Re: [Doh] Running code X-BeenThere: doh@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DNS Over HTTPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jan 2018 20:36:53 -0000 On Mon, 15 Jan 2018, Stephane Bortzmeyer wrote: > Great. Do note there are people who would like to work on DoH at the > London hackathon. Volunteers welcome > I have written some crude perl code to generate DOH responses and create DOH queries etc on the command line that I've needed when playing with DOH: https://github.com/bagder/dns2doh -- / daniel.haxx.se From nobody Tue Jan 16 07:02:53 2018 Return-Path: X-Original-To: doh@ietfa.amsl.com Delivered-To: doh@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F70112FB35 for ; Tue, 16 Jan 2018 07:02:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.91 X-Spam-Level: X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WckuJXxgjohn for ; Tue, 16 Jan 2018 07:02:49 -0800 (PST) Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 187B612D7E9 for ; Tue, 16 Jan 2018 07:02:49 -0800 (PST) Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id D3E7C281C3A for ; Tue, 16 Jan 2018 16:02:46 +0100 (CET) Received: by mx4.nic.fr (Postfix, from userid 500) id CEAD4281C4A; Tue, 16 Jan 2018 16:02:46 +0100 (CET) Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [IPv6:2001:67c:2218:15::11]) by mx4.nic.fr (Postfix) with ESMTP id C8084281C3A for ; Tue, 16 Jan 2018 16:02:46 +0100 (CET) Received: from b12.nic.fr (b12.users.prive.nic.fr [10.10.86.133]) by relay01.prive.nic.fr (Postfix) with ESMTP id C56A1606D942 for ; Tue, 16 Jan 2018 16:02:46 +0100 (CET) Received: by b12.nic.fr (Postfix, from userid 1000) id BBF164147F; Tue, 16 Jan 2018 16:02:46 +0100 (CET) Date: Tue, 16 Jan 2018 16:02:46 +0100 From: Stephane Bortzmeyer To: doh@ietf.org Message-ID: <20180116150246.dvr3d3nstozqfadn@nic.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: Debian GNU/Linux 9.3 X-Kernel: Linux 4.9.0-5-amd64 x86_64 X-Charlie: Je suis Charlie Organization: NIC France X-URL: http://www.nic.fr/ User-Agent: NeoMutt/20170113 (1.7.2) X-Bogosity: No, tests=bogofilter, spamicity=0.000069, version=1.2.2 X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2018.1.16.145416 Archived-At: Subject: [Doh] How to start HTTP/2? X-BeenThere: doh@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DNS Over HTTPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jan 2018 15:02:51 -0000 RFC 7540 specifies several ways to start HTTP/2 over a TCP connection (section 3), such as upgrade from HTTP/1, or starting directly HTTP/2 if you know the server accepts it. Which one should be used by DoH clients and servers? Section 7 of draft-ietf-doh-dns-over-https-02 seems silent about it. Note that this interacts with the discussion about whether HTTP/2 support is SHOULD or MUST. For the server: 1) accepts all RFC 7540 methods? 2) accepts only "immediately receives HTTP/2 frames"? For the client? 1) try all RFC 7540 methods? In which order? 2) try only "immediately sends HTTP/2 frames"? (If HTTP/2 support is a MUST, it makes sense) Note that some clients are currently limited. I don't think you can immediately send HTTP/2 frames with curl, for instance. From nobody Tue Jan 16 07:13:21 2018 Return-Path: X-Original-To: doh@ietfa.amsl.com Delivered-To: doh@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEC2F12DA25 for ; Tue, 16 Jan 2018 07:13:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.211 X-Spam-Level: X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fqXk0tUsDimh for ; Tue, 16 Jan 2018 07:13:18 -0800 (PST) Received: from giant.haxx.se (www.haxx.se [IPv6:2a00:1a28:1200:9::2]) by ietfa.amsl.com (Postfix) with ESMTP id B2EE113151A for ; Tue, 16 Jan 2018 07:12:42 -0800 (PST) Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by giant.haxx.se (8.15.2/8.15.2/Debian-4) with ESMTPS id w0GFCdMY006473 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 16 Jan 2018 16:12:39 +0100 Received: from localhost (dast@localhost) by giant.haxx.se (8.15.2/8.15.2/Submit) with ESMTP id w0GFCdXS006468; Tue, 16 Jan 2018 16:12:39 +0100 X-Authentication-Warning: giant.haxx.se: dast owned process doing -bs Date: Tue, 16 Jan 2018 16:12:39 +0100 (CET) From: Daniel Stenberg X-X-Sender: dast@giant.haxx.se To: Stephane Bortzmeyer cc: doh@ietf.org In-Reply-To: <20180116150246.dvr3d3nstozqfadn@nic.fr> Message-ID: References: <20180116150246.dvr3d3nstozqfadn@nic.fr> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) X-fromdanielhimself: yes MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Archived-At: Subject: Re: [Doh] How to start HTTP/2? X-BeenThere: doh@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DNS Over HTTPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jan 2018 15:13:20 -0000 On Tue, 16 Jan 2018, Stephane Bortzmeyer wrote: > RFC 7540 specifies several ways to start HTTP/2 over a TCP connection > (section 3), such as upgrade from HTTP/1, or starting directly HTTP/2 if you > know the server accepts it. Which one should be used by DoH clients and > servers? Section 7 of draft-ietf-doh-dns-over-https-02 seems silent about > it. If you stick to HTTPS (which the spec says we must in section 4) then there's only one way: negotiate HTTP version with ALPN. It also happens to be the easiest way for clients IMHO. > Note that some clients are currently limited. I don't think you can > immediately send HTTP/2 frames with curl, for instance. curl can actually do the three common ways: 1. negotiate HTTP/2 with HTTPS 2. upgrade from h1 using clear-text HTTP (but upgrade to HTTP/2 on a POST is not very supported by servers) 3. do "prior knowledge" HTTP/2 over clear-text HTTP -- / daniel.haxx.se From nobody Tue Jan 16 07:13:36 2018 Return-Path: X-Original-To: doh@ietfa.amsl.com Delivered-To: doh@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E24F13153F for ; Tue, 16 Jan 2018 07:13:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.91 X-Spam-Level: X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OdV8G9YW1ve9 for ; Tue, 16 Jan 2018 07:13:34 -0800 (PST) Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A093B13154B for ; Tue, 16 Jan 2018 07:12:54 -0800 (PST) Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 34F2D281C6E for ; Tue, 16 Jan 2018 16:12:53 +0100 (CET) Received: by mx4.nic.fr (Postfix, from userid 500) id 3000A281C79; Tue, 16 Jan 2018 16:12:53 +0100 (CET) Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [IPv6:2001:67c:2218:15::11]) by mx4.nic.fr (Postfix) with ESMTP id 2963A281C6E for ; Tue, 16 Jan 2018 16:12:53 +0100 (CET) Received: from b12.nic.fr (b12.users.prive.nic.fr [10.10.86.133]) by relay01.prive.nic.fr (Postfix) with ESMTP id 2693B6423521 for ; Tue, 16 Jan 2018 16:12:53 +0100 (CET) Received: by b12.nic.fr (Postfix, from userid 1000) id 1DD7E4147F; Tue, 16 Jan 2018 16:12:53 +0100 (CET) Date: Tue, 16 Jan 2018 16:12:53 +0100 From: Stephane Bortzmeyer To: doh@ietf.org Message-ID: <20180116151253.47r4gafg45lasfh2@nic.fr> References: <20180116150246.dvr3d3nstozqfadn@nic.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180116150246.dvr3d3nstozqfadn@nic.fr> X-Operating-System: Debian GNU/Linux 9.3 X-Kernel: Linux 4.9.0-5-amd64 x86_64 X-Charlie: Je suis Charlie Organization: NIC France X-URL: http://www.nic.fr/ User-Agent: NeoMutt/20170113 (1.7.2) X-Bogosity: No, tests=bogofilter, spamicity=0.000139, version=1.2.2 X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2018.1.16.150317 Archived-At: Subject: Re: [Doh] How to start HTTP/2? X-BeenThere: doh@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DNS Over HTTPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jan 2018 15:13:35 -0000 On Tue, Jan 16, 2018 at 04:02:46PM +0100, Stephane Bortzmeyer wrote a message of 27 lines which said: > Note that some clients are currently limited. I don't think you can > immediately send HTTP/2 frames with curl, for instance. Bad example, curl --http2-prior-knowledge (always read the doc, then read it again). From nobody Tue Jan 16 07:19:01 2018 Return-Path: X-Original-To: doh@ietfa.amsl.com Delivered-To: doh@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13FF71315AD for ; Tue, 16 Jan 2018 07:19:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.234 X-Spam-Level: X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8n6FUq3VF_Y9 for ; Tue, 16 Jan 2018 07:18:58 -0800 (PST) Received: from linode64.ducksong.com (linode6only.ducksong.com [IPv6:2600:3c02::f03c:91ff:fe6e:e8da]) by ietfa.amsl.com (Postfix) with ESMTP id CD4BB1315AA for ; Tue, 16 Jan 2018 07:17:02 -0800 (PST) Received: from mail-lf0-f48.google.com (mail-lf0-f48.google.com [209.85.215.48]) by linode64.ducksong.com (Postfix) with ESMTPSA id 25F553A063 for ; Tue, 16 Jan 2018 10:17:01 -0500 (EST) Received: by mail-lf0-f48.google.com with SMTP id a204so9573711lfa.2 for ; Tue, 16 Jan 2018 07:17:01 -0800 (PST) X-Gm-Message-State: AKwxytd07QWWx2CLmo6aVBbDqosaGzLlRAfPiQRyVmgKuBUinQkJcvaQ 7yYt3caBa8CrG60a7bpcmGB0w144fd1SekMxSw8= X-Google-Smtp-Source: ACJfBouGvSiBgTDZEpzofkpT++CqSzBhr/7ASNt6UbEMDfJ++glW/k2nbgWc5Bo1AkLhWEQWiX40x3i5S0P2DsIu0t8= X-Received: by 10.25.21.22 with SMTP id l22mr6763504lfi.143.1516115819679; Tue, 16 Jan 2018 07:16:59 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.166.201 with HTTP; Tue, 16 Jan 2018 07:16:58 -0800 (PST) In-Reply-To: <20180116150246.dvr3d3nstozqfadn@nic.fr> References: <20180116150246.dvr3d3nstozqfadn@nic.fr> From: Patrick McManus Date: Tue, 16 Jan 2018 10:16:58 -0500 X-Gmail-Original-Message-ID: Message-ID: To: Stephane Bortzmeyer Cc: doh@ietf.org Content-Type: multipart/alternative; boundary="001a113fc088ded7740562e63864" Archived-At: Subject: Re: [Doh] How to start HTTP/2? X-BeenThere: doh@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DNS Over HTTPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jan 2018 15:19:00 -0000 --001a113fc088ded7740562e63864 Content-Type: text/plain; charset="UTF-8" On Tue, Jan 16, 2018 at 10:02 AM, Stephane Bortzmeyer wrote: > RFC 7540 specifies several ways to start HTTP/2 over a TCP connection > (section 3), such as upgrade from HTTP/1, or starting directly HTTP/2 > if you know the server accepts it. Which one should be used by DoH > clients and servers? Section 7 of draft-ietf-doh-dns-over-https-02 > seems silent about it. > > any valid 7540 mechanism is acceptable to DoH. however note that the upgrade header specified by 3.2 of 7540 only applies to "http" schemed uris and DoH requires "https" schemed uris. So as a practical matter you're going to use ALPN with TLS though you would be allowed to use "prior knowledge".. but if h2 is not a DoH MUST then the presence of DoH itself doesn't constitute prior knowledge. (caching or configuration might qualify). > Note that this interacts with the discussion about whether HTTP/2 > support is SHOULD or MUST. > > we reached consensus on that being SHOULD.. also its "h2 or its successors" and I think that nit is important here.. > For the server: > > 1) accepts all RFC 7540 methods? > DoH doesn't constrain the server here. Indeed the server can serve more than DoH simultaneously. > 2) accepts only "immediately receives HTTP/2 frames"? > > by which you mean ignore ALPN? That seems like a bad plan. > For the client? > > 1) try all RFC 7540 methods? In which order? > 2) try only "immediately sends HTTP/2 frames"? (If HTTP/2 support is a > MUST, it makes sense) > > again, I don't see a reason that DoH would particularly influence the connection establishment choices. --001a113fc088ded7740562e63864 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Tue, Jan 16, 2018 at 10:02 AM, Stephane Bortzmeyer <bortzmeyer@nic.= fr> wrote:
RFC 7540 specifi= es several ways to start HTTP/2 over a TCP connection
(section 3), such as upgrade from HTTP/1, or starting directly HTTP/2
if you know the server accepts it. Which one should be used by DoH
clients and servers? Section 7 of draft-ietf-doh-dns-over-https-02
seems silent about it.


any valid 7540 mechanism is acceptable= to DoH. however note that the upgrade header specified by 3.2 of 7540 only= applies to "http" schemed uris and DoH requires "https"= ; schemed uris. So as a practical matter you're going to use ALPN with = TLS though you would be allowed to use "prior knowledge".. but if= h2 is not a DoH MUST then the presence of DoH itself doesn't constitut= e prior knowledge. (caching or configuration might qualify).
=
=C2=A0
Note that this interacts with the discussion about whether HTTP/2
support is SHOULD or MUST.


we reached consensus on that being SHO= ULD.. also its "h2 or its successors" and I think that nit is imp= ortant here..
=C2=A0
For the server:

1) accepts all RFC 7540 methods?

DoH doesn&#= 39;t constrain the server here. Indeed the server can serve more than DoH s= imultaneously.
=C2=A0
2) accepts only "immediately receives HTTP/2 frames"?


by which you mean ignore ALPN? That se= ems like a bad plan.

=C2=A0
For the client?

1) try all RFC 7540 methods? In which order?
2) try only "immediately sends HTTP/2 frames"? (If HTTP/2 support= is a
MUST, it makes sense)


again, I don&= #39;t see a reason that DoH would particularly influence the connection est= ablishment choices.

--001a113fc088ded7740562e63864-- From nobody Tue Jan 16 07:24:31 2018 Return-Path: X-Original-To: doh@ietfa.amsl.com Delivered-To: doh@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41C8E13153D for ; Tue, 16 Jan 2018 07:24:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.91 X-Spam-Level: X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9gnEB3TXUkHM for ; Tue, 16 Jan 2018 07:24:28 -0800 (PST) Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBECE131564 for ; Tue, 16 Jan 2018 07:21:46 -0800 (PST) Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 4FAFB280161; Tue, 16 Jan 2018 16:21:45 +0100 (CET) Received: by mx4.nic.fr (Postfix, from userid 500) id 49DB028017B; Tue, 16 Jan 2018 16:21:45 +0100 (CET) Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [IPv6:2001:67c:2218:15::11]) by mx4.nic.fr (Postfix) with ESMTP id 431A7280161; Tue, 16 Jan 2018 16:21:45 +0100 (CET) Received: from b12.nic.fr (b12.users.prive.nic.fr [10.10.86.133]) by relay01.prive.nic.fr (Postfix) with ESMTP id 402C56423521; Tue, 16 Jan 2018 16:21:45 +0100 (CET) Received: by b12.nic.fr (Postfix, from userid 1000) id 379784147F; Tue, 16 Jan 2018 16:21:45 +0100 (CET) Date: Tue, 16 Jan 2018 16:21:45 +0100 From: Stephane Bortzmeyer To: Daniel Stenberg Cc: doh@ietf.org Message-ID: <20180116152145.qhgqoo3dqmebb6aa@nic.fr> References: <20180116150246.dvr3d3nstozqfadn@nic.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: Debian GNU/Linux 9.3 X-Kernel: Linux 4.9.0-5-amd64 x86_64 X-Charlie: Je suis Charlie Organization: NIC France X-URL: http://www.nic.fr/ User-Agent: NeoMutt/20170113 (1.7.2) X-Bogosity: No, tests=bogofilter, spamicity=0.001507, version=1.2.2 X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2018.1.16.151215 Archived-At: Subject: Re: [Doh] How to start HTTP/2? X-BeenThere: doh@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DNS Over HTTPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jan 2018 15:24:29 -0000 On Tue, Jan 16, 2018 at 04:12:39PM +0100, Daniel Stenberg wrote a message of 27 lines which said: > If you stick to HTTPS (which the spec says we must in section 4) > then there's only one way: negotiate HTTP version with ALPN. It also > happens to be the easiest way for clients IMHO. OK, but could it be better to say explicitely "Servers and clients MUST start HTTP/2 using the ALPN extension of TLS, as specified in RFC 7540, section 3.3"? (Then, what a server should do if the client did not use ALPN? Start HTTP/2 anyway, because of the robustness principle?) From nobody Tue Jan 16 07:31:11 2018 Return-Path: X-Original-To: doh@ietfa.amsl.com Delivered-To: doh@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F2A5131528 for ; Tue, 16 Jan 2018 07:31:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.234 X-Spam-Level: X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NoKMlZdFjCea for ; Tue, 16 Jan 2018 07:31:06 -0800 (PST) Received: from linode64.ducksong.com (www.ducksong.com [192.155.95.102]) by ietfa.amsl.com (Postfix) with ESMTP id CDE1F131568 for ; Tue, 16 Jan 2018 07:29:59 -0800 (PST) Received: from mail-lf0-f52.google.com (mail-lf0-f52.google.com [209.85.215.52]) by linode64.ducksong.com (Postfix) with ESMTPSA id 907493A069 for ; Tue, 16 Jan 2018 10:29:56 -0500 (EST) Received: by mail-lf0-f52.google.com with SMTP id q17so7726960lfa.9 for ; Tue, 16 Jan 2018 07:29:56 -0800 (PST) X-Gm-Message-State: AKwxytcSvtg+G2RykNjwMVKurqOcwh9ViYEQGjTP5W3BJBKVGZbPmmfi qsxmIWKbvwG9Z2QjfyUwzlPC+JB2P3pOcyzp91M= X-Google-Smtp-Source: ACJfBosGPVJENaUvrvjthjEtOH1Uzn+M+WOz7U3OR/peEzzoECCWHjXAuB/6+z8CHmacQHznwjL5knk1vt6QzVun3xE= X-Received: by 10.25.142.203 with SMTP id a72mr12821549lfl.79.1516116595166; Tue, 16 Jan 2018 07:29:55 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.166.201 with HTTP; Tue, 16 Jan 2018 07:29:54 -0800 (PST) In-Reply-To: <20180116152145.qhgqoo3dqmebb6aa@nic.fr> References: <20180116150246.dvr3d3nstozqfadn@nic.fr> <20180116152145.qhgqoo3dqmebb6aa@nic.fr> From: Patrick McManus Date: Tue, 16 Jan 2018 10:29:54 -0500 X-Gmail-Original-Message-ID: Message-ID: To: Stephane Bortzmeyer Cc: Daniel Stenberg , doh@ietf.org Content-Type: multipart/alternative; boundary="f403045f4c7c17d5170562e66702" Archived-At: Subject: Re: [Doh] How to start HTTP/2? X-BeenThere: doh@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DNS Over HTTPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jan 2018 15:31:09 -0000 --f403045f4c7c17d5170562e66702 Content-Type: text/plain; charset="UTF-8" On Tue, Jan 16, 2018 at 10:21 AM, Stephane Bortzmeyer wrote: > On Tue, Jan 16, 2018 at 04:12:39PM +0100, > Daniel Stenberg wrote > a message of 27 lines which said: > > > If you stick to HTTPS (which the spec says we must in section 4) > > then there's only one way: negotiate HTTP version with ALPN. It also > > happens to be the easiest way for clients IMHO. > > OK, but could it be better to say explicitely "Servers and clients > MUST start HTTP/2 using the ALPN extension of TLS, as specified in RFC > 7540, section 3.3"? > > imo, no.. a] h2 isn't required.. and even where its a should it is h2 or its successors. successors might do it differently. b] a large point of using h2 as a substrate is that you just reuse h2 and don't need to restate things (possibly incorrectly by accident) c] h2 can be extended in ways that could conflict with that language. I don't see the value in forcing those extensions to be aware enough to also extend DoH. > (Then, what a server should do if the client did not use ALPN? Start > HTTP/2 anyway, because of the robustness principle?) > > _______________________________________________ > Doh mailing list > Doh@ietf.org > https://www.ietf.org/mailman/listinfo/doh > --f403045f4c7c17d5170562e66702 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Tue, Jan 16, 2018 at 10:21 AM, Stephane Bortzmeyer <bortzmeyer@nic.= fr> wrote:
On Tue, Jan 16, = 2018 at 04:12:39PM +0100,
=C2=A0Daniel Stenberg <daniel@haxx.se<= /a>> wrote
=C2=A0a message of 27 lines which said:

> If you stick to HTTPS (which the spec says we = must in section 4)
> then there's only one way: negotiate HTTP version with ALPN. It al= so
> happens to be the easiest way for clients IMHO.

OK, but could it be better to say explicitely "Servers and clie= nts
MUST start HTTP/2 using the ALPN extension of TLS, as specified in RFC
7540, section 3.3"?





--f403045f4c7c17d5170562e66702-- From nobody Tue Jan 16 07:31:24 2018 Return-Path: X-Original-To: doh@ietfa.amsl.com Delivered-To: doh@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DDA9131569 for ; Tue, 16 Jan 2018 07:31:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.211 X-Spam-Level: X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n2JUffmWskvc for ; Tue, 16 Jan 2018 07:31:15 -0800 (PST) Received: from giant.haxx.se (www.haxx.se [IPv6:2a00:1a28:1200:9::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0B6B7131530 for ; Tue, 16 Jan 2018 07:30:09 -0800 (PST) Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by giant.haxx.se (8.15.2/8.15.2/Debian-4) with ESMTPS id w0GFU7gw016982 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 16 Jan 2018 16:30:07 +0100 Received: from localhost (dast@localhost) by giant.haxx.se (8.15.2/8.15.2/Submit) with ESMTP id w0GFU7Vf016976; Tue, 16 Jan 2018 16:30:07 +0100 X-Authentication-Warning: giant.haxx.se: dast owned process doing -bs Date: Tue, 16 Jan 2018 16:30:07 +0100 (CET) From: Daniel Stenberg X-X-Sender: dast@giant.haxx.se To: Stephane Bortzmeyer cc: doh@ietf.org In-Reply-To: <20180116152145.qhgqoo3dqmebb6aa@nic.fr> Message-ID: References: <20180116150246.dvr3d3nstozqfadn@nic.fr> <20180116152145.qhgqoo3dqmebb6aa@nic.fr> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) X-fromdanielhimself: yes MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Archived-At: Subject: Re: [Doh] How to start HTTP/2? X-BeenThere: doh@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DNS Over HTTPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jan 2018 15:31:16 -0000 On Tue, 16 Jan 2018, Stephane Bortzmeyer wrote: > OK, but could it be better to say explicitely "Servers and clients MUST > start HTTP/2 using the ALPN extension of TLS, as specified in RFC 7540, > section 3.3"? It probably could, but as that's exactly what doing HTTP/2 over HTTPS means I considered that implied. > (Then, what a server should do if the client did not use ALPN? Start HTTP/2 > anyway, because of the robustness principle?) If you want HTTP/2 over HTTPS, you need to use ALPN. An HTTPS server that doesn't do ALPN can't speak HTTP/2 as defined in RFC7540. -- / daniel.haxx.se From nobody Tue Jan 16 15:12:06 2018 Return-Path: X-Original-To: doh@ietfa.amsl.com Delivered-To: doh@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40A1712EB86 for ; Tue, 16 Jan 2018 15:12:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gCXHZTjx_m7C for ; Tue, 16 Jan 2018 15:12:03 -0800 (PST) Received: from mail-ot0-x243.google.com (mail-ot0-x243.google.com [IPv6:2607:f8b0:4003:c0f::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99D8E12EB90 for ; Tue, 16 Jan 2018 15:12:03 -0800 (PST) Received: by mail-ot0-x243.google.com with SMTP id f100so2589794otf.3 for ; Tue, 16 Jan 2018 15:12:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=w/59sSRXgi7Ppdr2CnsqJfcI7CW6IlKAQ5IzZ4xppgM=; b=bCJ7YFsoDn3w/JS8AHKQBoCmOACo9CXyjqjoyyxTYicWUH/acSyYHmqZKM4OksSngh eqe4jXmU3Gn1ZqhlT2Onrqg0h/hiQNVZCRzne4Ws/Kp4Ydmm2BAm3piiCteeFKM60690 Sp+VQtBfoDmdrDTZz0Nfw+E4aTkqivEzPnQWJBdNo7BpKksxw/02QosN8nyuzYPHzcoW /4xS2uyqFBlAfyOZo7Sch9L8f4iyGZ159Igl+NNKWgF2faf80oj8ghT4BLscRMJ3o0hX KjGsTFhROz8aqG4FYQDUZbSdzyppCpUwoDHgJVC0tvfmCIBpNUSVL6rfdz0TKjzgUlJi ENYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=w/59sSRXgi7Ppdr2CnsqJfcI7CW6IlKAQ5IzZ4xppgM=; b=MeHO7n2bEbTbdzdLDLe/sRzR6POhTuaCk7MiYsxEtztSpwuGR6dzv5FyonY/mIIgW0 6e7zbCXGGBXAmAQ19Sd3SjNsGJT8QxxNS5GBPwy+goDkp/QdrjmBHlr4eq+Z/OYkdcjR AfNAH6ZvrP0oWEL55gcDtyw6lKSl18qQzEr3yF639nY3DdvUzbz8ryStbWhI4QEIXiu+ GYynacgQgvIQiXVaH39gzUcufn6+zxLLTeWPWehw5wfr9gUy+PClHZ8KuaLKfJhKRQc0 us4D5gnmqmRKVyaqS//JI0N17pXn5tc423pZMp+Ol4hXSNF7KWuh8EZCJY5mVCEPMOk3 XKbQ== X-Gm-Message-State: AKwxytc91MhtU5W7KvAzJZgIK0RXjIB54z1xEqZRR5AmIbrwkDGtKPiP mJImRylnfqR10DbItyxPh1+IL0cIGNCznJT90Bk= X-Google-Smtp-Source: ACJfBotQe2HUtpb801BhJuD8GsK6vT8MDgQO59E5cotxVz6T3Eyn2G4Es98N6MbDxr0oBYqeECP0EGRkOr8S5DzDQjg= X-Received: by 10.157.68.154 with SMTP id v26mr21769ote.308.1516144322881; Tue, 16 Jan 2018 15:12:02 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.39.16 with HTTP; Tue, 16 Jan 2018 15:12:01 -0800 (PST) In-Reply-To: References: <20180116150246.dvr3d3nstozqfadn@nic.fr> <20180116152145.qhgqoo3dqmebb6aa@nic.fr> From: Martin Thomson Date: Wed, 17 Jan 2018 10:12:01 +1100 Message-ID: To: Daniel Stenberg Cc: Stephane Bortzmeyer , doh@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Doh] How to start HTTP/2? X-BeenThere: doh@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DNS Over HTTPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jan 2018 23:12:05 -0000 What Daniel said. We're really only targetting HTTPS here, and HTTPS means TLS and ALPN when it comes to HTTP/2. Also, as a practical matter, HTTP/2 over TLS with ALPN is the only configuration that is widely deployed and available. curl is somewhat exceptional here in its promiscuity, but that's a core feature of curl. On Wed, Jan 17, 2018 at 2:30 AM, Daniel Stenberg wrote: > On Tue, 16 Jan 2018, Stephane Bortzmeyer wrote: > >> OK, but could it be better to say explicitely "Servers and clients MUST >> start HTTP/2 using the ALPN extension of TLS, as specified in RFC 7540, >> section 3.3"? > > > It probably could, but as that's exactly what doing HTTP/2 over HTTPS means > I considered that implied. > >> (Then, what a server should do if the client did not use ALPN? Start >> HTTP/2 anyway, because of the robustness principle?) > > > If you want HTTP/2 over HTTPS, you need to use ALPN. An HTTPS server that > doesn't do ALPN can't speak HTTP/2 as defined in RFC7540. > > -- > > / daniel.haxx.se > > > _______________________________________________ > Doh mailing list > Doh@ietf.org > https://www.ietf.org/mailman/listinfo/doh From nobody Tue Jan 16 23:51:46 2018 Return-Path: X-Original-To: doh@ietfa.amsl.com Delivered-To: doh@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4C9C12F4BD for ; Tue, 16 Jan 2018 23:51:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.448 X-Spam-Level: X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OBNsdwJYuoob for ; Tue, 16 Jan 2018 23:51:42 -0800 (PST) Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80F7E12F3D0 for ; Tue, 16 Jan 2018 23:51:42 -0800 (PST) Received: by mail-lf0-x22f.google.com with SMTP id x196so671515lfd.12 for ; Tue, 16 Jan 2018 23:51:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=1Slq7vC46e8+sECUDz6IXq7iw6YUj1fjhRbXuo0cbdM=; b=jItH6oof0QFI0dBtcDpRPaix+bCouc4SqnAZ52b5YuO02laoHfMPzU6AyemsVIxmZJ EZ62SN0rKsUIwI0WvjOZyQPSuihwiHGL9DisIy0JMSGSMnhWKem71mRat7NJyptnrh+M kDw3sJ2bi1FNgIIROs/Wk+ZQwoCzWlh58mVKZ1i5CDOvZlYHMfa/dyfZZUCpmc5+gV4B r/FQwHy95cFZuW0SFHRMdG05GEItTIq3bP9PeIltMVBOsppR/yLj35CGt6oHENXHisxt yUSsMDI6x51EInHaU/JwP6tjpZqC5G4eVs9+D2arBrX0Dfo6ZS1mPXivuWaq6QrphLDU xwdQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=1Slq7vC46e8+sECUDz6IXq7iw6YUj1fjhRbXuo0cbdM=; b=URgJafJXet3T8tUzPtbqCE07EnQPVm7YEkNof5bHFgzBbtPJYJRdc+mfsB2EaCVtpX 79G6wXIHZoTsIYHMjua/SIkI1Ca4OT/5Emt3+9uQjHJPFpsuj0PnF65ZyIhDve+Y91Sf a2wUpsifrdTqppxpN9ehI3Jh47GMIKO3M5tmHy+JgL6bnC8ig48zuc98Ske+3CwgfRjH h2R6LG5oZLWNk2ZeONOXIf+J5O9/6IEufBY1oOfcMvbXVco5ouBtf81MOEwYXbkppjDD UVstVTkhr6zBLKn9TdeOo5zzyCxQF2lL8Mz47KMtY7dCae9j0RwGylh3OTFCLHyJinvt +ACA== X-Gm-Message-State: AKwxytelN5ezVUDPVPEkv0UEDJ1N15KsMVVQ/qbmJt17Vc1HxPEYb1yP EyvzDaCLuxEUfKUYQaMOYuEMMTY2smoSmExjuubTQPL4 X-Google-Smtp-Source: ACJfBotlrA04jZejziigArRTbYS3E3nwunr1IY8JEVVgtnoyH+rU7fsoYTaWevgX/LFAItp4kPDAyGmH1Bvy1Fdknt8= X-Received: by 10.25.209.139 with SMTP id i133mr11192930lfg.137.1516175500603; Tue, 16 Jan 2018 23:51:40 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.27.208 with HTTP; Tue, 16 Jan 2018 23:51:39 -0800 (PST) In-Reply-To: References: From: manu tman Date: Tue, 16 Jan 2018 23:51:39 -0800 Message-ID: To: Ben Schwartz Cc: doh@ietf.org Content-Type: multipart/alternative; boundary="001a11400d2c2174ce0562f41e5f" Archived-At: Subject: Re: [Doh] Running code X-BeenThere: doh@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DNS Over HTTPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jan 2018 07:51:45 -0000 --001a11400d2c2174ce0562f41e5f Content-Type: text/plain; charset="UTF-8" On Thu, Jan 11, 2018 at 12:19 PM, manu tman wrote: > > Following up on Ben's announcement of a "publicly" available DOH server, I > brushed up some of the work I did during IETF 100 Hackathon and pushed the > changes to https://github.com/facebookexperimental/doh-proxy . > Some follow ups here.... I just pushed doh-proxy v0.0.2 which adds a few more feature: - updated doc at https://facebookexperimental.github.io/doh-proxy/ I would appreciate people testing, going over the doc and providing some feedback. - The stub will now perform multiple queries over the same HTTP2 connection and therefore greatly improve latency. The stub is still HTTP2 only and I dont think it will do anything else for the coming future. - added doh-httpproxy: This is suppose to run behind a reverse proxy, a good way to easily scale python, run the script without caring about specific privileges and dropping them later and also a way move TLS termination and properly handling HTTP2 to the reverse proxy so DOH proxy does not have to deal with it. Manu --001a11400d2c2174ce0562f41e5f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Thu, Jan 11, 2018 at 12:19 PM, manu tman <chantr4@gmail.com>= wrote:

Following up on Ben's announcement of a &= quot;publicly" available DOH server, I brushed up some of the work I d= id during IETF 100 Hackathon and pushed the changes to=C2=A0https://gi= thub.com/facebookexperimental/doh-proxy .
=

Some follow ups here....

I just pushed doh-proxy= v0.0.2 which adds a few more feature:

- updated d= oc at=C2=A0ht= tps://facebookexperimental.github.io/doh-proxy/ I would appreciate peop= le testing, going over the doc and providing some feedback.
- The stub w= ill now perform multiple queries over the same HTTP2 connection and therefo= re greatly improve latency. The stub is still HTTP2 only and I dont think i= t will do anything else for the coming future.
- added doh-httppr= oxy: This is suppose to run behind a reverse proxy, a good way to easily sc= ale python, run the script without caring about specific privileges and dro= pping them later and also a way move TLS termination and properly handling = HTTP2 to the reverse proxy so DOH proxy does not have to deal with it.

Manu


--001a11400d2c2174ce0562f41e5f-- From nobody Wed Jan 17 00:23:03 2018 Return-Path: X-Original-To: doh@ietfa.amsl.com Delivered-To: doh@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D47DC124C27 for ; Wed, 17 Jan 2018 00:23:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ldy_ysv7kQP7 for ; Wed, 17 Jan 2018 00:23:01 -0800 (PST) Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8A9F124234 for ; Wed, 17 Jan 2018 00:23:00 -0800 (PST) Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 9065131D1B; Wed, 17 Jan 2018 09:22:59 +0100 (CET) Received: by godin (Postfix, from userid 1000) id 417ECEC0B80; Wed, 17 Jan 2018 09:18:23 +0100 (CET) Date: Wed, 17 Jan 2018 09:18:23 +0100 From: Stephane Bortzmeyer To: Patrick McManus Cc: doh@ietf.org Message-ID: <20180117081823.GA23686@laperouse.bortzmeyer.org> References: <20180116150246.dvr3d3nstozqfadn@nic.fr> <20180116152145.qhgqoo3dqmebb6aa@nic.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Transport: UUCP rules X-Operating-System: Ubuntu 16.04 (xenial) X-Charlie: Je suis Charlie User-Agent: Mutt/1.5.24 (2015-08-30) Archived-At: Subject: Re: [Doh] How to start HTTP/2? X-BeenThere: doh@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DNS Over HTTPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jan 2018 08:23:02 -0000 On Tue, Jan 16, 2018 at 10:29:54AM -0500, Patrick McManus wrote a message of 83 lines which said: > imo, no.. a] h2 isn't required.. and even where its a should it is h2 or > its successors. successors might do it differently. ... > c] h2 can be extended in ways that could conflict with that language. I > don't see the value in forcing those extensions to be aware enough to also > extend DoH. OK, I understand. But can it raise interoperability issues? If a client tries one way and the server does not understand it, won't it mean at least a delay in noticing and fixing the problem? Martin Thomson said it is not a problem because everyone uses TLS and ALPN, anyway. But it contradicts what you say about the possibility of future changes using other techniques. From nobody Wed Jan 17 07:03:55 2018 Return-Path: X-Original-To: doh@ietfa.amsl.com Delivered-To: doh@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B69A127978 for ; Wed, 17 Jan 2018 07:03:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.233 X-Spam-Level: X-Spam-Status: No, score=-1.233 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H4B7e_MBsQhJ for ; Wed, 17 Jan 2018 07:03:47 -0800 (PST) Received: from linode64.ducksong.com (linode6only.ducksong.com [IPv6:2600:3c02::f03c:91ff:fe6e:e8da]) by ietfa.amsl.com (Postfix) with ESMTP id D94B912D957 for ; Wed, 17 Jan 2018 07:03:46 -0800 (PST) Received: from mail-lf0-f52.google.com (mail-lf0-f52.google.com [209.85.215.52]) by linode64.ducksong.com (Postfix) with ESMTPSA id 684163A0FE for ; Wed, 17 Jan 2018 10:03:44 -0500 (EST) Received: by mail-lf0-f52.google.com with SMTP id h92so12038088lfi.7 for ; Wed, 17 Jan 2018 07:03:44 -0800 (PST) X-Gm-Message-State: AKwxytfblcVV/cgIYakZG/WW0TK+PnBURc4+7Q7dn/0EJ/XcJetpGBYS y1w2TDYbxklS1uPrDvNgevjdgtJd1lafUBLkTwM= X-Google-Smtp-Source: ACJfBoueYDQYLfPcl0b+yLnpv9oQPgN2V0I1p0Ul3NoLq0L+IUUj6Fp3cSsptYpAgwQ9QPg8FTyiLTc2j0wubpbMbgA= X-Received: by 10.25.193.204 with SMTP id r195mr10820573lff.37.1516201423068; Wed, 17 Jan 2018 07:03:43 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.218.17 with HTTP; Wed, 17 Jan 2018 07:03:42 -0800 (PST) In-Reply-To: <20180117081823.GA23686@laperouse.bortzmeyer.org> References: <20180116150246.dvr3d3nstozqfadn@nic.fr> <20180116152145.qhgqoo3dqmebb6aa@nic.fr> <20180117081823.GA23686@laperouse.bortzmeyer.org> From: Patrick McManus Date: Wed, 17 Jan 2018 10:03:42 -0500 X-Gmail-Original-Message-ID: Message-ID: To: Stephane Bortzmeyer Cc: Patrick McManus , doh@ietf.org Content-Type: multipart/alternative; boundary="94eb2c1a194a3ae4b30562fa27bc" Archived-At: Subject: Re: [Doh] How to start HTTP/2? X-BeenThere: doh@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DNS Over HTTPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jan 2018 15:03:54 -0000 --94eb2c1a194a3ae4b30562fa27bc Content-Type: text/plain; charset="UTF-8" On Wed, Jan 17, 2018 at 3:18 AM, Stephane Bortzmeyer wrote: > > Martin Thomson said it is not a problem because everyone uses TLS and > ALPN, anyway. But it contradicts what you say about the possibility of > future changes using other techniques. > for h2, everyone does use TLS/ALPN/TCP-443 for the base case.. but if you're using alt-svc then the host and port are resolved differently. DoH can use Alt-Svc but DoH (rightly) doesn't reference it. Alt-Svc is an h2 extension (rfc 7838) hq (HTTP on Quic - an IETF successor to h2) will be a bit more complicated.. not only will you need TLS and ALPN but you'll need Alt-Svc (or something like it) for even the base case as TCP/443 isn't going to work. Again, referencing the details in doh doesn't help a lot beyond saying "MUST connect via https and SHOULD use h2 or its successors". One of the reasons this can't be a MUST is actually ensuring a >= h2 path is nigh impossible given all of abstractions in infrastructure. Its not meant to say you should always fail the connection if it is not made over H2, just a] make sure your implementation offers and tries to use >= h2 in the usual ways b] understand that if you're not using >= h2 there are serious scaling and performance issues If this can be expressed as non-normative advice in a sentence or three that would be ok by me but in general I think this is what using https as a substrate means. --94eb2c1a194a3ae4b30562fa27bc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On W= ed, Jan 17, 2018 at 3:18 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr>= ; wrote:

Martin Thomson said it is not a problem because everyone uses TLS and
ALPN, anyway. But it contradicts what you say about the possibility of
future changes using other techniques.

for h2, everyone does use TLS/ALPN/TCP-443 for the base case.= . but if you're using alt-svc then the host and port are resolved diffe= rently. DoH can use Alt-Svc but DoH (rightly) doesn't reference it. Alt= -Svc is an h2 extension (rfc 7838)

=
hq (HTTP on Quic - an IETF successor to h2= ) will be a bit more complicated.. not only will you need TLS and ALPN but = you'll need Alt-Svc (or something like it) for even the base case as TC= P/443 isn't going to work. Again, referencing the details in doh doesn&= #39;t help a lot beyond saying "MUST connect via https and SHOULD use = h2 or its successors".

One of the reasons this can't be a MUST is actual= ly ensuring a >=3D h2 path is nigh impossible given all of abstractions = in infrastructure. Its not meant to say you should always fail the connecti= on if it is not made over H2, just
a] make = sure your implementation offers and tries to use >=3D h2 in the usual wa= ys
b] understand that if you're not usi= ng >=3D h2 there are serious scaling and performance issues

If this can be= expressed as non-normative advice in a sentence or three that would be ok = by me but in general I think this is what using https as a substrate means.=

--94eb2c1a194a3ae4b30562fa27bc-- From nobody Thu Jan 18 16:15:15 2018 Return-Path: X-Original-To: doh@ietfa.amsl.com Delivered-To: doh@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5AAB12D84A for ; Thu, 18 Jan 2018 16:15:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.449 X-Spam-Level: X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yyTbaVXBMChW for ; Thu, 18 Jan 2018 16:15:12 -0800 (PST) Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B09AE12D7F7 for ; Thu, 18 Jan 2018 16:15:11 -0800 (PST) Received: by mail-lf0-x22d.google.com with SMTP id t139so23281lff.0 for ; Thu, 18 Jan 2018 16:15:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=B3Dwm8lsaxerfR2gpzfshJmOobTzaLfrf0f0+ZebB6c=; b=RLC7jqU7rbu1DDPo+URO/4CdBZB+J+FOxfUHg2LEMWJHUp7jtQ9kCgC5/ukqEkREkJ FOH6gcswbU4J2aOaonKJq9es2mNz5E/dCPgITr4zuwXOGlsXnH3RWLB1LfstJYxMQ/8j EvLLsmHeF8u8uT5xqzIaAp7UuISzwvj/1dDAMDl7sCDNKmog3yv+jbp8Mru4KODLGgA6 G6wbrZzw9OyYevfOhxDJr0ThWihA2MTXctOUQfE9w2XHC+pdvurixo8DGrIymcWXFEG3 Rt/w45JT9EZOoPSBpgsNhr/0IdktVXCr7AJThNGCTs7N+puW8v/5uDp6FNAbQsAcyorI k8rw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=B3Dwm8lsaxerfR2gpzfshJmOobTzaLfrf0f0+ZebB6c=; b=na/rU5+pz7odWNrT4OJhlRjZZ2TykId6CviAzs7JhGX+JqhWmzA4GyjMZDzFsC7+96 KMCYhl9D1++7F62GbYDsFe0jCMgHRUwqu3bORzLjnztZYdX/j1j5ImcWGcYumI124tIs pnrMxzjBNeGMJGsSqosfG/2EHwhm3ZP5CYJiMzJ6/ZF9Ipco97rp2ddRnk3pzrCyFImZ lgc58JSrTh92LlCN6Rep/legt8cT8eLbYXS4DnGSim0JGRsED4//KrB6yr8dQcM5vSfo uqCID5O3ZjLTijJc7//PoApBw/9xDZdzGe90LQ26Re1us8BOQrsCD3mFOmkgOGDr9qIx oV9w== X-Gm-Message-State: AKGB3mLq4OCzbp6CqUYtyhpN2PG7CfAYi+jG+WSt/mrv60BBCu2TEDTg 1CHlFprBjiF36/VUQ4zL+tTUNKmQy3+tTo/ZWlZ+7NIj X-Google-Smtp-Source: ACJfBosMgSOh3/BNotlblAB6vc5SFhKtkdIMrtjTGcPd3caTZEBk23qrPdtWEULvyS7W5sNWoy6iC5jkw5chs0+z/fI= X-Received: by 10.46.7.79 with SMTP id i15mr27532864ljd.42.1516320909600; Thu, 18 Jan 2018 16:15:09 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.27.208 with HTTP; Thu, 18 Jan 2018 16:15:08 -0800 (PST) From: manu tman Date: Thu, 18 Jan 2018 16:15:08 -0800 Message-ID: To: doh@ietf.org Content-Type: multipart/alternative; boundary="f403045f77502eac71056315f9f0" Archived-At: Subject: [Doh] DOH behind caching proxies X-BeenThere: doh@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DNS Over HTTPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jan 2018 00:15:14 -0000 --f403045f77502eac71056315f9f0 Content-Type: text/plain; charset="UTF-8" Hi list, Should we clarify the behaviour of caching proxies? When using a proxy in front of DOH servers and doing targeting based on resolver IP or using ECS, the returned answer for a same query (body param) may be different depending on the client, but if the caching proxy caches based on GET parameters, there is chances to return answers that are supposed to be correct for another client. In draft-ietf-doh-dns-over-https-02 Section 5: ```Using the GET method is friendlier to many HTTP cache implementations. ``` and ``` In order to maximize cache friendliness, DNS API clients using media formats that include DNS ID, such as application/dns-udpwireformat, SHOULD use a DNS ID of 0 in every DNS request. ``` As much as we may instruct the client to cache the result, if there is proxies in the middle, those should not cache the answer they received from backend DOH servers. Manu --f403045f77502eac71056315f9f0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi list,

Should we clarify the behaviou= r of caching proxies?

When using a proxy in front = of DOH servers and doing targeting based on resolver IP or using ECS, the r= eturned answer for a same query (body param) may be different depending on = the client, but if the caching proxy caches based on GET parameters, there = is chances to return answers that are supposed to be correct for another cl= ient.

In=C2=A0draft-ietf-doh-dns-over-https-02
=
Section 5:=C2=A0
```Using the GET method
   is friendlier to many HTTP cache implementations.
```
and
```
In order to maximize cache friendliness, DNS AP=
I clients using media
   formats that include DNS ID, such as application/dns-udpwireformat,
   SHOULD use a DNS ID of 0 in every DNS request.
```

As much as we may instruct the client to cache the result, if there is prox=
ies in the middle, those should not cache the answer they received from bac=
kend DOH servers.

Manu


--f403045f77502eac71056315f9f0-- From nobody Mon Jan 22 02:56:36 2018 Return-Path: X-Original-To: doh@ietfa.amsl.com Delivered-To: doh@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D92A124239 for ; Mon, 22 Jan 2018 02:56:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.452 X-Spam-Level: X-Spam-Status: No, score=-0.452 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_BRBL_LASTEXT=1.449, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WMWhKxH-jiIA for ; Mon, 22 Jan 2018 02:56:33 -0800 (PST) Received: from hydrogen.portfast.net (hydrogen.portfast.net [188.246.200.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A9361201F8 for ; Mon, 22 Jan 2018 02:56:33 -0800 (PST) Received: from [46.227.151.81] (port=51259 helo=rays-mbp.local) by hydrogen.portfast.net ([188.246.200.2]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1edZmA-0006jO-PP (Exim 4.72) for doh@ietf.org (return-path ); Mon, 22 Jan 2018 10:56:30 +0000 To: doh@ietf.org From: Ray Bellis Message-ID: Date: Mon, 22 Jan 2018 10:56:31 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Archived-At: Subject: [Doh] Extended Deadline for submissions for DNS-OARC Workshop 28 X-BeenThere: doh@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DNS Over HTTPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2018 10:56:35 -0000 The 28th DNS-OARC Workshop will be hosted by ICANN in San Juan, Puerto Rico, and will take place on March 8th and 9th immediately before ICANN61 The deadline for submissions to the workshop has been extended to February 2nd, with the other workshop milestones updated as follows: 19 Jan 2018 - Original Deadline for submission 23 Jan 2018 - Initial contribution list published 02 Feb 2018 - Extended Deadline for Submission 13 Feb 2018 - Updated contribution list published 23 Feb 2018 - Full agenda published 02 Mar 2018 - Deadline for slideset submission Presentation submission details are at: Ray Bellis, for the DNS-OARC Programme Committee From nobody Sat Jan 27 23:49:38 2018 Return-Path: X-Original-To: doh@ietfa.amsl.com Delivered-To: doh@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8788F129C51 for ; Sat, 27 Jan 2018 23:49:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.449 X-Spam-Level: X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jpGkzlJiejRj for ; Sat, 27 Jan 2018 23:49:35 -0800 (PST) Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 113B6124F57 for ; Sat, 27 Jan 2018 23:49:35 -0800 (PST) Received: by mail-lf0-x236.google.com with SMTP id o89so5558546lfg.10 for ; Sat, 27 Jan 2018 23:49:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=v+8F2lIIac2FtEfTeV1hDZYnqhuWHlmw/GMEjQMIWXs=; b=Ek22s/eXKL2VUb3FWpyAI9zWWWl29+aYMexRmSpDL6w+KdUk8+t+dfQhZudEhpVEGB QCQzPao1jfqjNdUPJjMngMdoFnXw/rscGzhSq+XpNosS5bFbaMNJu68AEeVi1T85J0Jg gB1dn8aNCpLkfMcMUmffDeP020mlk34s60iR1tAGl0mijFSRCmaAExeZik+Z7rk4eURd 7kGmGqQZAPGsks70IyNU1cJwCMKHf9T5mjaJAgKqaAkvv/YYgDiX0uFRYAhLnijNKw9K yk4RZOqe6WIKOEl0dUsLMYodD4YPZhj00E+F8IrclxSsK9wrPCWv3yy0QMdjmT/+QBp5 YtFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=v+8F2lIIac2FtEfTeV1hDZYnqhuWHlmw/GMEjQMIWXs=; b=WTDyvQ4kGLZjt+xG8t5OCv+30qfs62ja7Qq1fpNP+/xToPXqrY467X9BCrSzYhMR4v ruBgOKI822lP5AE6Vy53akq4I1L/9ASR+2B9yfCAGdgSlcJJ765PGG3ICmfcWSOXdMsY gXTMhGfP2CC7jcRBONYQ4f+aBQBwovy8YoLAJzqZw7M907xI0TSXnT3LufaZ1BH7aVRa KjiZMQDCn82Io3bQ1cLojuT+zl1yqaYL/0VhgY+YZGmrANhEwGQ7J1zby3FjlBIXvokP RwKlAypNRmEO+51SaetxuPHR+ucvBGkI/LCT+xcyMWjiwFrPTOwuD+NHx0GxjjAQcq8Q ZcEQ== X-Gm-Message-State: AKwxyte4KLxJk9Ya2guU+xMKeuCBb8Oz6UFRX0LGwre/d0pB9Ghw3u3g AmLtiF4knUmk9y1LvNcEq0i1kCbn8oeNeICKWhk= X-Google-Smtp-Source: AH8x227zi79AB3IQX44xKpqLRxVtG01XJVpqNUoLbWlv/20y0KSHSf7KpqXMP+yPOhn9wQhlhL44I7Uy7pXA/VqCTbc= X-Received: by 10.46.17.93 with SMTP id f90mr5437020lje.92.1517125773158; Sat, 27 Jan 2018 23:49:33 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.169.20 with HTTP; Sat, 27 Jan 2018 23:49:32 -0800 (PST) In-Reply-To: References: From: manu tman Date: Sat, 27 Jan 2018 23:49:32 -0800 Message-ID: To: Ben Schwartz Cc: doh@ietf.org Content-Type: multipart/alternative; boundary="94eb2c1c0c4ac9efce0563d15e0b" Archived-At: Subject: Re: [Doh] Running code X-BeenThere: doh@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DNS Over HTTPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jan 2018 07:49:37 -0000 --94eb2c1c0c4ac9efce0563d15e0b Content-Type: text/plain; charset="UTF-8" Hi all, I am also running an experimental server... that runs doh-proxy. Using the original query, it would translate to: https://dns.dnsoverhttps.net/.well-known/dns-query?ct&body=q80BAAABAAAAAAAAA3d3dwdleGFtcGxlA2NvbQAAAQAB Mind that this is running on some cheap digital ocean instances and is not monitored :) but that should be good enough to run tests against. Manu On Tue, Jan 16, 2018 at 11:51 PM, manu tman wrote: > > > On Thu, Jan 11, 2018 at 12:19 PM, manu tman wrote: > >> >> Following up on Ben's announcement of a "publicly" available DOH server, >> I brushed up some of the work I did during IETF 100 Hackathon and pushed >> the changes to https://github.com/facebookexperimental/doh-proxy . >> > > Some follow ups here.... > > I just pushed doh-proxy v0.0.2 which adds a few more feature: > > - updated doc at https://facebookexperimental.github.io/doh-proxy/ I > would appreciate people testing, going over the doc and providing some > feedback. > - The stub will now perform multiple queries over the same HTTP2 > connection and therefore greatly improve latency. The stub is still HTTP2 > only and I dont think it will do anything else for the coming future. > - added doh-httpproxy: This is suppose to run behind a reverse proxy, a > good way to easily scale python, run the script without caring about > specific privileges and dropping them later and also a way move TLS > termination and properly handling HTTP2 to the reverse proxy so DOH proxy > does not have to deal with it. > > Manu > > > --94eb2c1c0c4ac9efce0563d15e0b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

I am also running an experiment= al server... that runs doh-proxy. Using the original query, it would transl= ate to:

Mind that this is run= ning on some cheap digital ocean instances and is not monitored :) but that= should be good enough to run tests against.

Manu

On Tue, Jan 1= 6, 2018 at 11:51 PM, manu tman <chantr4@gmail.com> wrote:


On Thu, Jan 11, 2018 a= t 12:19 PM, manu tman <chantr4@gmail.com> wrote:

<= div>Following up on Ben's announcement of a "publicly" availa= ble DOH server, I brushed up some of the work I did during IETF 100 Hackath= on and pushed the changes to=C2=A0https://github.com/facebookexpe= rimental/doh-proxy .

Some follow ups here....

I just pushed doh-proxy v0.0.2 which adds = a few more feature:

- updated doc at=C2=A0ht= tps://facebookexperimental.github.io/doh-proxy/ I would appre= ciate people testing, going over the doc and providing some feedback.
- = The stub will now perform multiple queries over the same HTTP2 connection a= nd therefore greatly improve latency. The stub is still HTTP2 only and I do= nt think it will do anything else for the coming future.
- added = doh-httpproxy: This is suppose to run behind a reverse proxy, a good way to= easily scale python, run the script without caring about specific privileg= es and dropping them later and also a way move TLS termination and properly= handling HTTP2 to the reverse proxy so DOH proxy does not have to deal wit= h it.

Manu



--94eb2c1c0c4ac9efce0563d15e0b-- From nobody Wed Jan 31 08:21:19 2018 Return-Path: X-Original-To: doh@ietf.org Delivered-To: doh@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C435512EC4D; Wed, 31 Jan 2018 08:21:17 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Meeting Session Request Tool To: Cc: doh@ietf.org, adam@nostrum.com, bemasc@webrtc.org, doh-chairs@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.71.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151741567779.14372.7777011173764114187.idtracker@ietfa.amsl.com> Date: Wed, 31 Jan 2018 08:21:17 -0800 Archived-At: Subject: [Doh] doh - New Meeting Session Request for IETF 101 X-BeenThere: doh@ietf.org X-Mailman-Version: 2.1.22 List-Id: DNS Over HTTPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 16:21:18 -0000 A new meeting session request has just been submitted by Benjamin M. Schwartz, a Chair of the doh working group. --------------------------------------------------------- Working Group Name: DNS Over HTTPS Area Name: Applications and Real-Time Area Session Requester: Benjamin Schwartz Number of Sessions: 1 Length of Session(s): 1 Hour Number of Attendees: 90 Conflicts to Avoid: First Priority: dnsop dnssd dprive httpbis Second Priority: capport quic v6ops hrpc homenet People who must be present: Paul E. Hoffman Adam Roach Patrick McManus Benjamin M. Schwartz David C Lawrence Resources Requested: Special Requests: I think 45 minutes is probably enough. --------------------------------------------------------- From nobody Wed Jan 31 08:21:26 2018 Return-Path: X-Original-To: doh@ietf.org Delivered-To: doh@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F0FBC13181C; Wed, 31 Jan 2018 08:21:21 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Meeting Session Request Tool To: Cc: doh@ietf.org, adam@nostrum.com, bemasc@webrtc.org, doh-chairs@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.71.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151741568198.14449.14468833535767667284.idtracker@ietfa.amsl.com> Date: Wed, 31 Jan 2018 08:21:21 -0800 Archived-At: Subject: [Doh] doh - New Meeting Session Request for IETF 101 X-BeenThere: doh@ietf.org X-Mailman-Version: 2.1.22 List-Id: DNS Over HTTPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 16:21:22 -0000 A new meeting session request has just been submitted by Benjamin M. Schwartz, a Chair of the doh working group. --------------------------------------------------------- Working Group Name: DNS Over HTTPS Area Name: Applications and Real-Time Area Session Requester: Benjamin Schwartz Number of Sessions: 1 Length of Session(s): 1 Hour Number of Attendees: 90 Conflicts to Avoid: First Priority: dnsop dnssd dprive httpbis Second Priority: capport quic v6ops hrpc homenet People who must be present: Paul E. Hoffman Adam Roach Patrick McManus Benjamin M. Schwartz David C Lawrence Resources Requested: Special Requests: I think 45 minutes is probably enough. ---------------------------------------------------------