Re: [Ohttp] Request to Charter a New Working Group: Oblivious HTTP (OHTTP)

Christian Huitema <huitema@huitema.net> Tue, 08 June 2021 19:41 UTC

Return-Path: <huitema@huitema.net>
X-Original-To: ohttp@ietfa.amsl.com
Delivered-To: ohttp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A4333A3B5E for <ohttp@ietfa.amsl.com>; Tue, 8 Jun 2021 12:41:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level:
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] autolearn=unavailable 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 k7FUoZXAF5yA for <ohttp@ietfa.amsl.com>; Tue, 8 Jun 2021 12:41:50 -0700 (PDT)
Received: from mx36-out20.antispamcloud.com (mx36-out20.antispamcloud.com [209.126.121.68]) (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 BA6053A3B5D for <ohttp@ietf.org>; Tue, 8 Jun 2021 12:41:50 -0700 (PDT)
Received: from xse115.mail2web.com ([66.113.196.115] helo=xse.mail2web.com) by mx134.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1lqhbe-0004bO-9V for ohttp@ietf.org; Tue, 08 Jun 2021 21:41:48 +0200
Received: from xsmtp21.mail2web.com (unknown [10.100.68.60]) by xse.mail2web.com (Postfix) with ESMTPS id 4G00x33Ylhz9qf for <ohttp@ietf.org>; Tue, 8 Jun 2021 12:41:43 -0700 (PDT)
Received: from [10.5.2.14] (helo=xmail04.myhosting.com) by xsmtp21.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1lqhbb-0002Dk-Bp for ohttp@ietf.org; Tue, 08 Jun 2021 12:41:43 -0700
Received: (qmail 11774 invoked from network); 8 Jun 2021 19:41:42 -0000
Received: from unknown (HELO [192.168.1.103]) (Authenticated-user:_huitema@huitema.net@[172.58.43.69]) (envelope-sender <huitema@huitema.net>) by xmail04.myhosting.com (qmail-ldap-1.03) with ESMTPA for <IETF@ietf.org>; 8 Jun 2021 19:41:42 -0000
To: Michael Richardson <mcr+ietf@sandelman.ca>, Eliot Lear <lear@lear.ch>, 'IESG' <iesg@ietf.org>, ohttp@ietf.org, ietf <IETF@ietf.org>
References: <162309061157.32548.930649503797136245@ietfa.amsl.com> <d8932acb-397b-25b9-7bab-50c1a313d583@lear.ch> <4800.1623179777@localhost>
From: Christian Huitema <huitema@huitema.net>
Message-ID: <d21c360a-effb-41f2-c229-45f1e4b8a3d6@huitema.net>
Date: Tue, 08 Jun 2021 12:41:41 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <4800.1623179777@localhost>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
X-Originating-IP: 66.113.196.115
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.0/24@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: ham
X-Spampanel-Outgoing-Evidence: Combined (0.07)
X-Recommended-Action: accept
X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT/76evDKjoHDhIdU6+LDXF/PUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5zTDRuy/c1OZvpugLWWoBOafYzfQXcfqmra3dmoHS4ygkXA FqQnMW0fE2uYlMc8ftJWuRWrkPihq53YqAd1ENNqBHtNXu1E6L4+KyOXc4QYanQOD0r6/AaHZiEt dTMtMlia0Lmg/jgHfCNZd+W+PXf6bU8znQxGoPVrHMCWBB0sliue9TLOhN8AYRsvkjfngQBbDZxt jim+AmKM5CdELBpgzDkBvlIN1pUDU5DU5DggD03FrKlNunbw3GCGM2ilT848H5+GcIgM3fTqImzZ 2tdstWYAD+wEZQw6xBZnPra86y0KEAnwyE9dte+FkDKSV99EDBffVZVjmVaNbG4ZJG7FF+KJcoOd LdxL5Vwi8QUymGErPLbt0n54j3vHX4q9ucblgTl6fJxyntEfhZCKje4ZrSpkrp4/bIk9ge4hHszj +yERbInMiTBIUBbQ/Dy6Ip6W0r4y0/5D4w5pBBP5WfwEiVI8YifosiHq99m3pO5z65V9UvvKDEjE gSFAGCy7uJronV+E7OMXRvgtdyMlnmWiPkVGGEq2oLBn2fRQ3DK1GGOpjm0SS/tM9AW+XEYwW5nn ERxGHBIk838d0VMoCMdhRqjEFZFoz52RfErCbuNsJtQF2WMVGRG4c/iBE9vgliNiHE9X9GlwwRvN 2KIObvd055RG8/vjrz5/4Qa1aRJkvbyYmcpeCE6yHfzijkstg5tG67RoML5sF3N3cOrBcrK4in5O BFVXuChgcZPfJij+ieScr2BDfk59jcxwmWxRnAqx8qvQ9NRe4fVdGTEMOrjXU188V8MkbILx5IxQ sjeaTOuO5TcDeKjrEmYPn2IVWRvsDFbMyuyrnnpyt5QdgPdM2kAubAmq/PTQO+W2FInivlx21Yi3 rRmhgFI0Buha6+OZ3JKVmi72ocgY5kMQSjs7FeHN9ztUfyhmiivUY2iqA4H7+3hna43Kh3w6qf0n g4eLCrVbm7nC2LbgwAUU/zyk
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ohttp/X55RR9DrQTEbqUHaOiOd8vHGVe0>
Subject: Re: [Ohttp] Request to Charter a New Working Group: Oblivious HTTP (OHTTP)
X-BeenThere: ohttp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Oblivious HTTP <ohttp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ohttp>, <mailto:ohttp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ohttp/>
List-Post: <mailto:ohttp@ietf.org>
List-Help: <mailto:ohttp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ohttp>, <mailto:ohttp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jun 2021 19:41:53 -0000

On 6/8/2021 12:16 PM, Michael Richardson wrote:

> I didn't think oblivious-DNS was particularly useful either, because it was
> basically just turning stub resolvers into mutated full resolvers, without
> actually teaching them to do DNSSEC.   If they could do DNSSEC, then we could
> trust answers from any place, and then we could do some kind of p2p DNS
> queries to get better anonymization (and probably, more resiliency for DNS).

I used to believe a variation of that, that if users wanted to hide the 
IP address of the client sending DNS requests, they could just as well 
use a VPN and there would be no need for such "oblivious DNS" service. 
But it turned out that oblivious DNS was easier to deploy than VPN 
services, and also had some very nice privacy characteristics. I think 
that oblivious HTTP has the same potential, splitting the processing 
between an initial proxy that knows the client but does not know the 
requested URL, and an oblivious proxy that knows the requested URL but 
does not know the source IP address of the client.

-- Christian Huitema