Application for a Media Type

We recommend that you read the following RFCs before proceeding with this application. It is important that you understand the application process and requirements completely. These documents are the standards for Media Types:

Please read the following questions carefully and provide complete answers. Write "N/A" for mandatory answers that are not applicable.

What is the media type name?

See RFC 2046 §3, and RFC 2077.

What is the media subtype name?

Review the existing subtype names. See also RFC 2046, and RFC 6838, §3 and §4.2. Note: Registrations in the standards tree must be approved by the IESG or must correspond to a formal publication by a recognized standards body.

Describe the required parameters.

See RFC 2046 §1, and RFC 6838 §4.3.

Describe the optional parameters.

See RFC 2046 §1, and RFC 6838 §4.3.

7-bit text
8-bit text (this media type may require encoding on transports not capable of handling 8-bit text)
binary (this media type may require encoding on transports not capable of handling binary)
framed (transport must provide framing information)

Additional notes (optional):

See RFC 2045 §6, and RFC 6838 §4.8.

Provide a discussion of the security considerations.

See RFC 6838 §4.6

Provide a discussion of the interoperability considerations.

See RFC 6838 §4.5

Provide references to the published specification.

See RFC 6838 §4.10

Describe applications which use this media type.

See RFC 6838 §4.5

See RFC 6838 §4.11

See RFC 6838 §4.9

Standards tree applications only.

See RFC 6838 §5.2.1

See RFC 6838, §4.12

Deprecated alias names for this type

Magic number(s)

File extension(s)

Macintosh File Type Code(s)

Object Identifier(s) or OID(s) — See RFC 1494

Provide the contact for further information. See RFC 6838 §5.5.

Contact Name

Contact Email Address

Author/Change Controller (for standards tree registrations, this is typically the standards body)