[media-types] Review of chunked oblivious HTTP payload types

Oblivious HTTP defines a media type that is a single unit: the whole thing is encrypted or decrypted whole.  Chunked oblivious HTTP defines an equivalent format that can be processed in chunks.

The media registrations are identical, other than this difference.

See https://ietf-wg-ohai.github.io/draft-ohai-chunked-ohttp/draft-ietf-ohai-chunked-ohttp.html#section-8
or https://www.ietf.org/archive/id/draft-ietf-ohai-chunked-ohttp-04.html#section-8

Registrations follow, copied from the text version (and therefore a little strangely formatted).

For "message/ohttp-chunked-req":

   Type name:  message
   Subtype name:  ohttp-chunked-req
   Required parameters:  N/A
   Optional parameters:  N/A
   Encoding considerations:  "binary"
   Security considerations:  see Section 7
   Interoperability considerations:  N/A
   Published specification:  this specification
   Applications that use this media type:  Oblivious HTTP and
      applications that use Oblivious HTTP use this media type to
      identify encapsulated binary HTTP requests that are incrementally
      generated or processed.
   Fragment identifier considerations:  N/A
   Additional information:  Magic number(s):  N/A
                            Deprecated alias names for this type:  N/A
                            File extension(s):  N/A
                            Macintosh file type code(s):  N/A
   Person and email address to contact for further information:  see Aut
      hors' Addresses section
   Intended usage:  COMMON
   Restrictions on usage:  N/A
   Author:  see Authors' Addresses section
   Change controller:  IETF

And "message/ohttp-chunked-res":

   Type name:  message
   Subtype name:  ohttp-chunked-res
   Required parameters:  N/A
   Optional parameters:  N/A
   Encoding considerations:  "binary"
   Security considerations:  see Section 7
   Interoperability considerations:  N/A
   Published specification:  this specification
   Applications that use this media type:  Oblivious HTTP and
      applications that use Oblivious HTTP use this media type to
      identify encapsulated binary HTTP responses that are incrementally
      generated or processed.
   Fragment identifier considerations:  N/A
   Additional information:  Magic number(s):  N/A
                            Deprecated alias names for this type:  N/A
                            File extension(s):  N/A
                            Macintosh file type code(s):  N/A
   Person and email address to contact for further information:  see Aut
      hors' Addresses section
   Intended usage:  COMMON
   Restrictions on usage:  N/A
   Author:  see Authors' Addresses section
   Change controller:  IETF

_______________________________________________
media-types mailing list -- [email protected]
To unsubscribe send an email to [email protected]