Dedicated to preserving the central coordinating functions of the global
Internet for the public good.

Application for 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 RFCs are the standards for Media Types.

  • RFC 2045 - MIME formats and encodings
  • RFC 2046 - Definition of media types
  • RFC 2077 - Model top-level media type
  • RFC 3023 - Media types based on XML
  • RFC 4288 - Media type specifications and registration procedures
  • Your Name:

  • Your Email Address:

  1. Media Type Name
    See RFC 2046 section 3, and RFC 2077.

  2. Subtype name ( See Existing subtype names )
    See also RFC 2046, and RFC 4288, sections 3 and 4.2.
    Note: Registrations in the standards tree must be approved by the IESG and must correspond to a formal publication by a recognized standards body.

  3. Required parameters
    See RFC 2046 section 1, and RFC 4288, section 4.3

  4. Optional parameters
    See RFC 2046 section 1, and RFC 4288, section 4.3

  5. Encoding considerations
    See RFC 2046 section 6, and RFC 4288 section 4.8.

    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 provde framing information)

  6. Security considerations
    See RFC 4288, section 4.6
    Note that discussion of security considerations is required.

  7. Interoperability considerations
    See RFC 4288, section 4.5

  8. Published specification
    See RFC 4288, section 4.10

  9. Applications which use this media type
    See RFC 4288, section 4.5

  10. Additional information
    See RFC 4288, section 4.11

    • Magic number(s)

    • File extension(s)

    • Macintosh File Type Code(s)

    • Object Identifier(s) or OID(s)
      (See RFC1494)

  11. Intended usage

  12. Other Information/General Comment

  13. Person to contact for further information
    See RFC 4288, section 4.9

    • Name

    • E-mail

    • Author/Change controller

    Please check once again to be sure that all required fields are present.

    14. Please send comments on this web site to: webmaster@iana.org
    Page Updated January 03, 2002.
    (c) 1998-2000  The Internet Assigned Numbers Authority. All rights reserved.