IETF Logo Mail Archive

[Ohttp] renaming the WG-to-be?

Jim Reid <jim@rfc1035.com> Wed, 28 July 2021 10:57 UTC

Return-Path: <jim@rfc1035.com>
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 2BE0E3A07A9 for <ohttp@ietfa.amsl.com>; Wed, 28 Jul 2021 03:57:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level:
X-Spam-Status: No, score=-1.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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 gDZryC8Idimz for <ohttp@ietfa.amsl.com>; Wed, 28 Jul 2021 03:57:42 -0700 (PDT)
Received: from shaun.rfc1035.com (smtp.v6.rfc1035.com [IPv6:2001:4b10:100:7::25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E92713A07A2 for <ohttp@ietf.org>; Wed, 28 Jul 2021 03:57:41 -0700 (PDT)
Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 8DADA24211CE; Wed, 28 Jul 2021 10:57:38 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.7\))
From: Jim Reid <jim@rfc1035.com>
X-Priority: 3
In-Reply-To: <2111623045.1384.1627468504245@appsuite-gw1.open-xchange.com>
Date: Wed, 28 Jul 2021 11:57:36 +0100
Cc: Watson Ladd <watsonbladd@gmail.com>, ohttp@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <519D4BA4-0EE2-444D-A615-8F4847139140@rfc1035.com>
References: <CACsn0ckC9trR_HsFfn37=+rTTBhe-Z_hGiZJZ6GWPXiS_eanZw@mail.gmail.com> <2111623045.1384.1627468504245@appsuite-gw1.open-xchange.com>
To: Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3445.9.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ohttp/RrFrtJaTaXsuZlb7iRp_n9XGcKY>
Subject: [Ohttp] renaming the WG-to-be?
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: Wed, 28 Jul 2021 10:57:46 -0000


> On 28 Jul 2021, at 11:35, Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org> wrote:
> 
> I would also definitely find another name. "Oblivious" indicates the generic action of routing your request through one or more proxies to hide your IP address to the server

How about obfuscated HTTP?

obfuscate /obˈfə-skāt or ob-fusˈkāt/
transitive verb
	• To darken
	• To obscure
	• To confuse or bewilder

v2.23.0 | Report a Bug | By Email