Draft: draft-ietf-ohai-ohttp

Commentary: I already wrote this up , so maybe it 's OK to do now . 
 In reading through this , it is really distracting to have these massive sections full of N / A in the document . Moving them means more connective tissue ( forward references , section headings ) , but it should make this stuff get in the way less . 
 I suggest we do this during WGLC , unless you want to do it before cutting the next version .
The "application/ohttp-keys" format is a media type that identifies a
serialized collection of key configurations.  The content of this
media type comprises one or more key configuration encodings (see
key-config) that are concatenated.
The "application/ohttp-keys" format is a media type that identifies a
serialized collection of key configurations.  The content of this
media type comprises one or more key configuration encodings (see
key-config) that are concatenated; see iana-keys for a definition of
the media type.
Media types are used to identify Encapsulated Requests and Responses;
see iana-req and iana-res for definitions of these media types.
A client interacts with the Oblivious Relay Resource by constructing
an Encapsulated Request.  This Encapsulated Request is included as
the content of a POST request to the Oblivious Relay Resource.  This
request MUST only contain those fields necessary to carry the
Encapsulated Request: a method of POST, a target URI of the Oblivious
Relay Resource, a header field containing the content type (see
(media-types), and the Encapsulated Request as the request content.
In the request to the Oblivious Relay Resource, clients MAY include
additional fields.  However, those fields MUST be independent of the
Encapsulated Request and MUST be fields that the Oblivious Relay
Resource will remove before forwarding the Encapsulated Request
towards the target, such as the Connection or Proxy-Authorization
header fields SEMANTICS.
A client interacts with the Oblivious Relay Resource by constructing
an Encapsulated Request.  This Encapsulated Request is included as
the content of a POST request to the Oblivious Relay Resource.  This
request MUST only contain those fields necessary to carry the
Encapsulated Request: a method of POST, a target URI of the Oblivious
Relay Resource, a header field containing the content type (see
(iana-req), and the Encapsulated Request as the request content.  In
the request to the Oblivious Relay Resource, clients MAY include
additional fields.  However, those fields MUST be independent of the
Encapsulated Request and MUST be fields that the Oblivious Relay
Resource will remove before forwarding the Encapsulated Request
towards the target, such as the Connection or Proxy-Authorization
header fields SEMANTICS.
Media types are used to identify Encapsulated Requests and Responses.
Oblivious HTTP might be incompatible with network interception
regimes, such as those that rely on configuring clients with trust
anchors and intercepting TLS connections.  While TLS might be
intercepted successfully, interception middleboxes devices might not
receive updates that would allow Oblivious HTTP to be correctly
identified using the media types defined in media-types.
Oblivious HTTP might be incompatible with network interception
regimes, such as those that rely on configuring clients with trust
anchors and intercepting TLS connections.  While TLS might be
intercepted successfully, interception middleboxes devices might not
receive updates that would allow Oblivious HTTP to be correctly
identified using the media types defined in iana-req and iana-res.
IANA are request to update the "Media Types" registry at
https://www.iana.org/assignments/media-types [1] with the
registration information in media-types for the media types "message/
ohttp-req", "message/ohttp-res", and "application/ohttp-keys".
Please update the "Media Types" registry at
https://www.iana.org/assignments/media-types [1] for the media types
"application/ohttp-keys" (iana-keys), "message/ohttp-req" (iana-req),
and "message/ohttp-res" (iana-res).
The "application/ohttp-keys" media type identifies a key
configuration used by Oblivious HTTP.