MIME
Click on the red underlined text to get to the source
... Internet protocols have been carefully designed to be easily
extensible in certain areas. In particular, many protocols,
including but not limited to MIME [RFC2045], are capable of carrying
arbitrary labeled content. A mechanism is needed to label such
...
... initially done in [RFC2048], but the procedure defined there was
still part of the MIME document set. The media type specification
and registration procedure ...
... and registration procedure has now been moved to this separate
document, to make it clear that it is independent of MIME.
It may be desirable to restrict the use of media types ...
... top-level types and
their associated restrictions. Additionally, various protocols,
including but not limited to MIME, MAY impose additional restrictions
on the media types they can transport ...
... Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045draft, November 1996. ...
... Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046draft, November 1996. ...
... Casner, S. and P. Hoschka, "MIME Type Registration of RTP Payload Formats", RFC 3555prop(-> 4856prop | 4855prop), July 2003. ...
... Freed, N., Klensin, J., and J. Postel, "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures", BCP 13, RFC 2048(-> 4289 | 4288) ...
... Freed, N. and K. Moore, "MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations", RFC 2231prop ...
... Media type specification and registration procedures have been
moved out of the MIME document set to this separate specification.
o The various URLs ...