[Ohai] Terminology updates

[Christopher Wood <[e-mail]>]

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