IETF Logo Mail Archive

Re: [Ohai] Terminology updates

Tommy Pauly <tpauly@apple.com> Wed, 29 June 2022 14:13 UTC

Return-Path: <tpauly@apple.com>
X-Original-To: ohai@ietfa.amsl.com
Delivered-To: ohai@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 521A6C14CF03 for <ohai@ietfa.amsl.com>; Wed, 29 Jun 2022 07:13:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.853
X-Spam-Level:
X-Spam-Status: No, score=-2.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.745, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YMEWwzys-Vzm for <ohai@ietfa.amsl.com>; Wed, 29 Jun 2022 07:13:46 -0700 (PDT)
Received: from ma1-aaemail-dr-lapp03.apple.com (ma1-aaemail-dr-lapp03.apple.com [17.171.2.72]) (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 5ECD2C14CF02 for <ohai@ietf.org>; Wed, 29 Jun 2022 07:13:46 -0700 (PDT)
Received: from pps.filterd (ma1-aaemail-dr-lapp03.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp03.apple.com (8.16.0.42/8.16.0.42) with SMTP id 25TE3OYr040497; Wed, 29 Jun 2022 07:13:43 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=content-type : mime-version : subject : from : in-reply-to : date : cc : content-transfer-encoding : message-id : references : to; s=20180706; bh=69cT0hGwBwRuzIoUEA6Px8hO+SHDzexwNnTzEY7Kmpw=; b=hPmv3NLs6d4Om4eYD1oW+ne7tRPNtSa3yS24CJQYWtPpuXtKJPxQuD8sfD+1RJYwWhck m8o0Y733uvzwP7AlhRujTeiBHameyX06GAaET+yPyFhR59t3nwRvFpGstL3annzqIbr3 ZZMWcQxR+f6KrPci736r1qZ38XybZFOeQ/27Gde2wYxjY8fzAEAJi+aQnpGZLwP8X08Q D4aEeYAZ0FHLfDe5adJQax+C6+ViAbus3UWwGtGSs9jcLGogPlBWI6HsB+NPNihir/AV 25+19RacQ/RKVd7kl3fcFncQmYKeslCU22AaL4q5B2Ij4d952m+ojcqJz7opnY2go4xO vw==
Received: from rn-mailsvcp-mta-lapp03.rno.apple.com (rn-mailsvcp-mta-lapp03.rno.apple.com [10.225.203.151]) by ma1-aaemail-dr-lapp03.apple.com with ESMTP id 3gx1bw58jd-12 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 29 Jun 2022 07:13:43 -0700
Received: from rn-mailsvcp-mmp-lapp02.rno.apple.com (rn-mailsvcp-mmp-lapp02.rno.apple.com [17.179.253.15]) by rn-mailsvcp-mta-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.18.20220407 64bit (built Apr 7 2022)) with ESMTPS id <0RE800MTWSUU6E70@rn-mailsvcp-mta-lapp03.rno.apple.com>; Wed, 29 Jun 2022 07:13:42 -0700 (PDT)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp02.rno.apple.com by rn-mailsvcp-mmp-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.18.20220407 64bit (built Apr 7 2022)) id <0RE800O00SQJJ000@rn-mailsvcp-mmp-lapp02.rno.apple.com>; Wed, 29 Jun 2022 07:13:42 -0700 (PDT)
X-Va-A:
X-Va-T-CD: a76e746662f71e8f03430028ee5d52f3
X-Va-E-CD: 79cb209d8987f64724d334980ed6a5cf
X-Va-R-CD: 378c3313a649526b0b529af3ce414461
X-Va-CD: 0
X-Va-ID: 8aa3774b-7561-48e1-ab93-6bfa5cb513a0
X-V-A:
X-V-T-CD: a76e746662f71e8f03430028ee5d52f3
X-V-E-CD: 79cb209d8987f64724d334980ed6a5cf
X-V-R-CD: 378c3313a649526b0b529af3ce414461
X-V-CD: 0
X-V-ID: 4508fc10-b438-4846-94ee-ec03a88ec696
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.517, 18.0.883 definitions=2022-06-29_17:2022-06-28, 2022-06-29 signatures=0
Received: from smtpclient.apple (unknown [17.234.127.247]) by rn-mailsvcp-mmp-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.18.20220407 64bit (built Apr 7 2022)) with ESMTPSA id <0RE800THXSUTGY00@rn-mailsvcp-mmp-lapp02.rno.apple.com>; Wed, 29 Jun 2022 07:13:42 -0700 (PDT)
Content-type: text/plain; charset="utf-8"
MIME-version: 1.0 (Mac OS X Mail 16.0 \(3696.120.31\))
From: Tommy Pauly <tpauly@apple.com>
In-reply-to: <D10B3427-D457-4344-9374-646A5C588994@heapingbits.net>
Date: Wed, 29 Jun 2022 07:13:41 -0700
Cc: ohai@ietf.org
Content-transfer-encoding: quoted-printable
Message-id: <9FD580EC-DD10-4D76-9E38-21E32844B408@apple.com>
References: <D10B3427-D457-4344-9374-646A5C588994@heapingbits.net>
To: Christopher Wood <caw@heapingbits.net>
X-Mailer: Apple Mail (2.3696.120.31)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.517, 18.0.883 definitions=2022-06-29_17:2022-06-28, 2022-06-29 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ohai/ZE-oMdneou82s1TgG5fRfQpuk3Y>
Subject: Re: [Ohai] Terminology updates
X-BeenThere: ohai@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Oblivious HTTP Application Intermediation <ohai.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ohai>, <mailto:ohai-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ohai/>
List-Post: <mailto:ohai@ietf.org>
List-Help: <mailto:ohai-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ohai>, <mailto:ohai-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jun 2022 14:13:48 -0000

These proposed names seem reasonable. I like that they have “Oblivious” in the name, so it will be clear when used in other contexts that they refer to OHTTP. It’s also probably for the best that we avoid “proxy” since that has many meanings, and “relay” works fine here.

This is an acceptable shade to paint the bike shed =)

Thanks,
Tommy

> On Jun 29, 2022, at 7:04 AM, Christopher Wood <caw@heapingbits.net> wrote:
> 
> Hi folks,
> 
> Issue #121 [1] discusses the terminology used in the draft. Currently, we have the following four entities:
> 
>   Client <> Oblivious Proxy <> Oblivious Request <> Target
> 
> And we have the following three distinguished types of requests:
> 
> - Client -> Proxy
> - Proxy -> Request
> - Request -> Target
> 
> The Client->Proxy and Proxy->Request requests carry an encrypted (or encapsulated) request in their body, and the Request->Target request is this decapsulated/decrypted request.
> 
> In discussing OHTTP with folks, it’s become clear that the names used here are somewhat confusing. To help make the concepts more clear, I think it’d be useful to establish better names for the entities and requests used in the document. Obviously, this is a bike shed, but it’s a shed worth painting now rather than later.
> 
> After discussing with several people, Martin and I settled on the following proposal. First, let’s rename the four entities to the following:
> 
>   Client <> Oblivious Relay <> Oblivious Gateway <> Target
> 
> We use gateway here because the entity does a couple of different things to transform ingress requests to requests for the target, including decapsulation and replay prevention. And we use the term relay here to distinguish this entity from a traditional proxy. 
> 
> With these names, we then use the following terms for the three distinguished requests:
> 
> - Client -> Oblivious Relay: Oblivious Relay Request (carrying an Encrypted Request)
> - Oblivious Relay -> Oblivious Gateway: Oblivious Gateway Request (carrying the same Encrypted Request)
> - Oblivious Gateway -> Target: Request
> 
> What do folks think of this proposal?
> 
> Best,
> Chris
> 
> [1] https://github.com/ietf-wg-ohai/oblivious-http/issues/121
> -- 
> Ohai mailing list
> Ohai@ietf.org
> https://www.ietf.org/mailman/listinfo/ohai

v2.23.0 | Report a Bug | By Email