Type name:  application

Subtype name:  protobuf

Required parameters:  N/A

Optional parameters:

   encoding
      Indicates the type of Protobuf encoding and is "binary" by
      default for application/protobuf, indicating the format in
      [Binary].  At the time of writing, no other encoding can be
      used for application/protobuf, so this parameter is for
      extensibility.

   version
      Indicates the version of the wire encoding specification (not
      the schema language), with a default of 1.  At the time of
      writing, no Protobuf wire encodings are versioned, so this
      parameter is for extensibility.  Unversioned wire encodings
      should be treated as having version 1.

Encoding considerations:  binary

Security considerations:  See Section 6 of RFC-ietf-dispatch-mime-protobuf-06.

Interoperability considerations:  The Protobuf specification
   [Protobuf] includes versioning provisions to ensure backward
   compatibility when encountering payloads with unknown properties.

Published specification:  [Protobuf]

Applications that use this media type:  Any application with a need
   to exchange or store structured objects across platforms or
   implementations.

Fragment identifier considerations:  N/A

Additional information:

   Deprecated alias names for this type:  application/x-protobuf,
      application/x-protobuffer
   Magic number(s):  N/A
   File extension(s):  N/A
   Macintosh file type code(s):  N/A

Person & email address to contact for further information:  Protobuf
   Team <protobuf-team&google.com>

Intended usage:  COMMON

Restrictions on usage:  N/A

Author:  Rob Sloan <rmsj&google.com>, Protobuf Team <protobuf-
   team&google.com>


Normative References:

[Protobuf]
"Protocol Buffers", n.d., <https://protobuf.dev/>.

Informative References:

[Binary]
Protobuf, "Protobuf Binary Wire Encoding Spec", n.d., <https://protobuf.dev/programming-guides/encoding>.