IETF Logo Mail Archive

[dns-privacy] DNS over HTTPS via HTTP proxies

fujiwara@jprs.co.jp Mon, 19 July 2021 04:00 UTC

Return-Path: <fujiwara@jprs.co.jp>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AE3D3A2050 for <dns-privacy@ietfa.amsl.com>; Sun, 18 Jul 2021 21:00:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 0FSNHerlyAsv for <dns-privacy@ietfa.amsl.com>; Sun, 18 Jul 2021 21:00:28 -0700 (PDT)
Received: from off-send41.osa.jprs.co.jp (off-send41.osa.jprs.co.jp [117.104.133.135]) by ietfa.amsl.com (Postfix) with ESMTP id 6E8963A204C for <dns-privacy@ietf.org>; Sun, 18 Jul 2021 21:00:25 -0700 (PDT)
Received: from off-sendsmg31.osa.jprs.co.jp (off-sendsmg31.osa.jprs.co.jp [172.23.8.161]) by off-send41.osa.jprs.co.jp (Postfix) with ESMTP id 1E13C402F5C for <dns-privacy@ietf.org>; Mon, 19 Jul 2021 13:00:24 +0900 (JST)
Received: from off-sendsmg31.osa.jprs.co.jp (localhost [127.0.0.1]) by postfix.imss91 (Postfix) with ESMTP id E27356024574 for <dns-privacy@ietf.org>; Mon, 19 Jul 2021 13:00:20 +0900 (JST)
Received: from localhost (off-cpu08.osa.jprs.co.jp [172.23.4.18]) by off-sendsmg31.osa.jprs.co.jp (Postfix) with ESMTP id CDCCC602456B for <dns-privacy@ietf.org>; Mon, 19 Jul 2021 13:00:20 +0900 (JST)
Date: Mon, 19 Jul 2021 13:00:20 +0900
Message-Id: <20210719.130020.1116859977665651658.fujiwara@jprs.co.jp>
To: dns-privacy@ietf.org
From: fujiwara@jprs.co.jp
X-Mailer: Mew version 6.8 on Emacs 24.5
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSS-9.1.0.1373-8.6.0.1015-26292.005
X-TM-AS-Result: No--8.531-5.0-31-10
X-imss-scan-details: No--8.531-5.0-31-10
X-TMASE-Version: IMSS-9.1.0.1373-8.6.1015-26292.005
X-TMASE-Result: 10--8.530500-10.000000
X-TMASE-MatchedRID: rNgn9H0RAIJCXIGdsOwlUh5+URxv1WlBKTREEsKJaMkYpCAvxSMgTgzK NF0GZctoVZw5p7rJKW/DeaE26q+ivpkroZMnoDefdfk9ZxDdshZlRzZAkKRGDafDpVD78xj9BtW /BhXiKZ+vC9GQc0IPU0LsBcbqA3FUswuue39DaPLRPkPVCrqkJxC26qzoFs8npnCV5PvGM7l6Ok 7T7qIk1NxdRk2p3I0DsHCocrnuw8P+pyA4KAQAPmSIsH2qgnAffS0Ip2eEHny+qryzYw2E8M4ba jgO0kgvtuaPLrXjSMGy9Q92ZKlY2qDz3uDPb/JuUEhWy9W70AEgBwKKRHe+ryfQQ7V0KNddyowD BiMxlnG3jLevBVCbFXU25Lo2MRL2LapYvfuUyXk=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/Isn4GFAlhjOzJME3QCE41fmYFQ8>
Subject: [dns-privacy] DNS over HTTPS via HTTP proxies
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Addition of privacy to the DNS protocol <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Jul 2021 04:00:33 -0000

People who interests stub resolver's privacy,

I submitted new draft "DNS over HTTPS via HTTP proxies" last week.
https://datatracker.ietf.org/doc/draft-fujiwara-dprive-doh-via-httpproxy/

It is a rewrite of the OARC 35 presentation.
https://indico.dns-oarc.net/event/38/contributions/858/attachments/798/1467/doh-202105060305.pdf

It relates to Oblivious DNS over HTTPS, however, it does not propose
new protocols and new proxy software.
(it uses HTTP/1.1 CONNECT Method.)

I will be happy
if some providers offer "open HTTP proxies for DoH providers"
and application software developpers implement "DoH via HTTP proxy"
in applications (browsers).

# Software needs two proxy settings for DoH and other HTTP targets.

Regards,

--
Kazunori Fujiwara, JPRS <fujiwara@jprs.co.jp>

v2.23.0 | Report a Bug | By Email