MIME, Multipurpose Internet Mail Extensions

Description Glossary RFCs Publications Obsolete RFCs

Description:

Type:Data encapsulation.
Working groups 822ext, Internet Message Extensions.
avt, Audio/Video Transport.
conneg, Content Negotiation.
vpim, Voice Profile for Internet Mail.
Links: IANA: Message headers.
IANA: Application types.
IANA: Audio types.
IANA: Image types.
IANA: Message types.
IANA: Model types.
IANA: Multipart types.
IANA: Text types.
IANA: Video types.

RFC 2045:

RFC 822 defines a message representation protocol specifying considerable detail about US-ASCII message headers, and leaves the message content, or message body, as flat US-ASCII text. This set of documents, collectively called the Multipurpose Internet Mail Extensions, or MIME, redefines the format of messages to allow for:

  1. textual message bodies in character sets other than US-ASCII
  2. an extensible set of different formats for non-textual message bodies
  3. multi-part message bodies, and
  4. textual header information in character sets other than US-ASCII.

RFC 2046, pages 3 - 6:

In general, the top-level media type is used to declare the general type of data, while the subtype specifies a specific format for that type of data.

The five discrete top-level media types are:

  1. text -- textual information. The subtype "plain" in particular indicates plain text containing no formatting commands or directives of any sort. Plain text is intended to be displayed "as-is". No special software is required to get the full meaning of the text, aside from support for the indicated character set. Other subtypes are to be used for enriched text in forms where application software may enhance the appearance of the text, but such software must not be required in order to get the general idea of the content. Possible subtypes of "text" thus include any word processor format that can be read without resorting to software that understands the format. In particular, formats that employ embeddded binary formatting information are not considered directly readable. A very simple and portable subtype, "richtext", was defined in RFC 1341, with a further revision in RFC 1896 under the name "enriched".
  2. image -- image data. "Image" requires a display device (such as a graphical display, a graphics printer, or a FAX machine) to view the information. An initial subtype is defined for the widely-used image format JPEG. Subtypes are defined for two widely-used image formats, jpeg and gif.
  3. audio -- audio data. "Audio" requires an audio output device (such as a speaker or a telephone) to "display" the contents.
  4. video -- video data. "Video" requires the capability to display moving images, typically including specialized hardware and software.
  5. application -- some other kind of data, typically either uninterpreted binary data or information to be processed by an application. The subtype "octet- stream" is to be used in the case of uninterpreted binary data, in which case the simplest recommended action is to offer to write the information into a file for the user. The "PostScript" subtype is also defined for the transport of PostScript material. Other expected uses for "application" include spreadsheets, data for mail-based scheduling systems, and languages for "active" (computational) messaging, and word processing formats that are not directly readable. Note that security considerations may exist for some types of application data, most notably "application/PostScript" and any form of active messaging.

The two composite top-level media types are:

  1. multipart -- data consisting of multiple entities of independent data types. Four subtypes are initially defined, including the basic "mixed" subtype specifying a generic mixed set of parts, "alternative" for representing the same data in multiple formats, "parallel" for parts intended to be viewed simultaneously, and "digest" for multipart entities in which each part has a default type of "message
  2. message -- an encapsulated message. A body of media type "message" is itself all or a portion of some kind of message object. Such objects may or may not in turn contain other entities. The "rfc822" subtype is used when the encapsulated content is itself an RFC 822 message. The "partial" subtype is defined for partial RFC 822 messages, to permit the fragmented transmission of bodies that are thought to be too large to be passed through transport facilities in one piece. Another subtype, "external-body", is defined for specifying large bodies by reference to an external data source.

RFC 2047, page 3:

Certain sequences of "ordinary" printable ASCII characters (known as "encoded-words") are reserved for use as encoded data. The syntax of encoded-words is such that they are unlikely to "accidentally" appear as normal text in message headers. Furthermore, the characters used in encoded-words are restricted to those which do not have special meanings in the context in which the encoded-word appears.

Generally, an "encoded-word" is a sequence of printable ASCII characters that begins with "=?", ends with "?=", and has two "?"s in between. It specifies a character set and an encoding method, and also includes the original text encoded as graphic ASCII characters, according to the rules for that encoding method.


MIME header fields.

Header fieldReferences
Content-AlternativeRFC 4021
Content-BaseRFC 4021
Content-Disposition RFC 2183, RFC 4021
Content-Duration RFC 4021
Content-Type. RFC 4021
MIME-Version. RFC 4021

MIME-Version. Header field.
Identifies the MIME version to be used.

Syntax:

version := "MIME-Version" ":" 1*DIGIT "." 1*DIGIT


Content-Duration. Header field.
This field specifies the time duration of the content in seconds as a 32 bit unsigned integer.

Syntax:

duration := "Content-Duration" ":" 1*10DIGIT

Content-Type. Header field.
(RFC 2045) This field specifies the nature of the data in the body of an entity by giving media type and subtype identifiers, and by providing auxiliary information that may be required for certain media types. After the media type and subtype names, the remainder of the header field is simply a set of parameters, specified in an attribute=value notation. The ordering of parameters is not significant. In general, the top-level media type is used to declare the general type of data, while the subtype specifies a specific format for that type of data. Thus, a media type of "image/xyz" is enough to tell a user agent that the data is an image, even if the user agent has no knowledge of the specific image format "xyz". Such information can be used, for example, to decide whether or not to show a user the raw data from an unrecognized subtype -- such an action might be reasonable for unrecognized subtypes of text, but not for unrecognized subtypes of image or audio. For this reason, registered subtypes of text, image, audio, and video should not contain embedded information that is really of a different type. Such compound formats should be represented using the "multipart" or "application" types. Parameters are modifiers of the media subtype, and as such do not fundamentally affect the nature of the content. The set of meaningful parameters depends on the media type and subtype. Most parameters are associated with a single specific subtype. However, a given top-level media type may define parameters which are applicable to any subtype of that type. Parameters may be required by their defining content type or subtype or they may be optional. MIME implementations must ignore any parameters whose names they do not recognize. For example, the "charset" parameter is applicable to any subtype of "text", while the "boundary" parameter is required for any subtype of the "multipart" media type. An initial set of seven top-level media types is defined in RFC 2046. Five of these are discrete types whose content is essentially opaque as far as MIME processing is concerned. The remaining two are composite types whose contents require additional handling by MIME.

Syntax:

content := "Content-Type" ":" type "/" subtype *(";" parameter)

type := discrete-type / composite-type

discrete-type := "text" / "image" / "audio" / "video" / "application" / extension-token

composite-type := "message" / "multipart" / extension-token

extension-token := ietf-token / x-token

ietf-token := <An extension token defined by a standards-track RFC and registered with IANA.>

x-token := <The two characters "X-" or "x-" followed, with no intervening white space, by any token>

subtype := extension-token / iana-token

iana-token := <A publicly-defined extension token. Tokens of this form must be registered with IANA as specified in RFC 2048.>

parameter := attribute "=" value

attribute := token ; Matching of attributes ; is ALWAYS case-insensitive.

value := token / quoted-string

token := 1*<any (US-ASCII) CHAR except SPACE, CTLs, or tspecials>

tspecials := "(" / ")" / "<" / ">" / "@" / "," / ";" / ":" / "\" / <"> "/" / "[" / "]" / "?" / "=" ; Must be in quoted-string, ; to use within parameter values


Application. Type.
This media type is to be used for discrete data which does not fit in any of the other categories, and particularly for data to be processed by some type of application program. This is information which must be processed by an application before it is viewable or usable by a user. Expected uses for the "application" media type include file transfer, spreadsheets, data for mail-based scheduling systems, and languages for "active" (computational) material.

SubtypeDescriptionReference
1d-interleaved-parityfec1-D Interleaved Parity Forward Error Correction. RFC 6015
3gpp-ims+xml   
activemessage Active Mail. 
andrew-inset   
applefile MacMIME. RFC 1740
atom+xml Atom. RFC 4287, RFC 5023
atomcat+xml RFC 5023
atomsvc+xml RFC 5023
atomicmail  
auth-policy+xmlCommon Policy.RFC 4745
batch-SMTP SMTP.RFC 2442
beep+xml BEEP.RFC 3080
CALS-1840  RFC 1895
ccxml+xmlVoice Browser Call Control. RFC 4267
cea-2018+xml  
cellml+xmlCellML Umbrella.RFC 4708
cnrp+xml CNRP, Common Name Resolution Protocol. 
commongroundCommon Ground. 
conference-info+xml RFC4575
cpl+xml CPL, Call Processing Language. RFC 3880
csta+xml  
CSTAdata+xml  
cybercashCyberCash. RFC 1898
davmount+xml RFC 4709
dca-rftDocument Content Architecture/Revisable Form Text. 
dec-dxDigital Document Transmission. 
dialog-info+xml  RFC 4235
dicom  RFC 3240
dns  RFC 4027
dskpp+xmlDSKPP, Dynamic Symmetric Key Provisioning Protocol.RFC 6063
dssc+der RFC 5698
dscc+xml RFC 5698
dvcsData Validation and Certification Server. RFC 3029
ecmascript  RFC 4329
EDI-Consent  RFC 1767
EDI-X12  RFC 1767
EDIFACT  RFC 1767
epp+xml RFC 3730
eshop  
fastinfoset  
fastsoap  
fdt+xml  
fits FITS, Flexible Image Transport System. RFC 4047
font-tdpfrPortable Font Resource. RFC 3073
framework-attributes+xml RFC 6230
gzipGZIP. RFC 6713
H224 RFC 4573
http HTTP, HyperText Transfer Protocol.RFC 2616
hyperstudioHyperStudio. 
ibe-key-request+xml  RFC 5408
ibe-pkg-reply+xml  RFC 5408
ibe-pp-data  RFC 5408
igesIGES. 
im-iscomposing+xml  RFC 3994
index  RFC 2652
index.cmd  RFC 2652
index.obj  RFC 2652
index.response  RFC 2652
index.vnd  RFC 2652
inkml+xml  
iotpInternet Open Trading Protocol. RFC 2935
ipp IPP, Internet Printing Protocol. RFC 2910
isupISDN User part. RFC 3204
javascript  RFC 4329
json RFC 4627
kpml-request+xmlKPML, Key Press Markup Language request. RFC 4730
kpml-response+xmlKPML, Key Press Markup Language response. RFC 4730
lost+xml LoST, Location-to-Service Translation. RFC 5222
mac-binhex40  RFC 1741
macwriteiiMacWrite II. 
marc  RFC 2220
mathematicaMathematica. 
mbms-associated-procedure-description+xml  
mbms-deregister+xml  
mbms-envelope+xml  
mbms-msk-response+xml  
mbms-msk+xml  
mbms-protection-description+xml  
mbms-reception-report+xml  
mbms-register-response+xml  
mbms-register+xml  
mbms-user-service-description+xml  
mbox  RFC 4155
mediaservercontrol+xmlMSCML, Media Server Control Markup Language. RFC 4722, RFC 5022
metalink4+xml  
mikey MIKEY, Multimedia Internet KEYing. RFC 3830
mosskey-data  RFC 1848
moss-keys  RFC 1848
mosskey-request  RFC 1848
moss-signature  RFC 1848
mpeg4-genericMPEG-4. RFC 3640
mpeg4-iod  RFC 4337
mpeg4-iod-xmt  RFC 4337
mp21  
mp4  RFC 4337
mrcp MRCP, Media Resource Control Protocol. RFC 4463
mswordMicrosoft Word file format. 
mxf MXF, Material Exchange Format. RFC 4539
nasdata RFC 4707
news-checkgroups RFC 5537
news-groupinfo RFC 5537
news-message-id  RFC 1036, RFC 5537
news-transmission  RFC 1036
nss  
ocsp-request. OCSP, Online Certificate Status Protocol. RFC 2560
ocsp-response OCSP, Online Certificate Status Protocol. RFC 2560
octet-stream  RFC 2045, RFC 2046
oda  RFC 2045, RFC 2046
oebps-package+xmlOPF, Open eBook Publication Structure (OEBPS) Package File. RFC 4839
ogg Ogg Bitstream Format.RFC 3534
parityfec  RFC 3009
pdf PDF, Portable Document Format. RFC 3778
pgp-encrypted  RFC 2015, RFC 3156
pgp-keys  RFC 2015, RFC 3156
pgp-signature  RFC 2015, RFC 3156
pidf+xml PIDF, Presence Information Data Format. RFC 3863
pidf-diff+xml RFC 5262
pkcs10 S/MIME, Secure/Multipurpose Internet Mail Extensions. RFC 2311
pkcs7-mime S/MIME, Secure/Multipurpose Internet Mail Extensions. RFC 2311, RFC 5751
pkcs7-signature S/MIME, Secure/Multipurpose Internet Mail Extensions. RFC 2311, RFC 5751
pkix-attr-cert  
pkix-cert  RFC 2585
pkix-crl  RFC 2585
pkix-pkipath  RFC 3546, RFC 4366
pkixcmp  RFC 2510
pls+xmlPLS, Pronunciation Lexicon Specification. RFC 4267
poc-settings+xmlPush-to-Talk over Cellular. RFC 4354
postscript Postscript. RFC 2045, RFC 2046
prs.alvestrand.titrax-sheet  
prs.cwwCU-Writer for Windows. 
prs.nprend  
prs.plucker  
qsig  RFC 3204
rdf+xmlRDF, Resource Description Framework. RFC 3870
reginfo+xml  RFC 3680
relax-ng-compact-syntax  
remote-printing  RFC 1486, RFC 1528
resource-lists+xml RFC 4826
resource-lists-diff+xml  RFC 5362
riscosRISC OS file types. 
rlmi+xml RFC 4662
rls-services+xml RFC 4826
rtf  
rtx RFC 4588
samlassertion+xml  
samlmetadata+xml  
sbml+xml SBML, Systems Biology Markup Language. RFC 3823
scvp-cv-request SCVP, Simple Certificate Validation Protocol. RFC 5055
scvp-cv-response SCVP, Simple Certificate Validation Protocol. RFC 5055
scvp-vp-request SCVP, Simple Certificate Validation Protocol. RFC 5055
scvp-vp-response SCVP, Simple Certificate Validation Protocol. RFC 5055
sdp SDP, Session Description Protocol. RFC 2327
set-paymentSET, Secure Electronic Transaction. 
set-payment-initiationSET, Secure Electronic Transaction. 
set-registrationSET, Secure Electronic Transaction. 
set-registration-initiationSET, Secure Electronic Transaction.  
sgmlSGML, Standard Generalized Markup Language. RFC 1874
sgml-open-catalogSGML, Standard Generalized Markup Language.  
shf+xml SHF, S Hexdump Format. 
sieveSieve. RFC 3028
simple-filter+xml  
simple-message-summary SIP message waiting and message summary information. RFC 3842
simpleSymbolContainer  
slate BBN/Slate documents. 
smil(obsolete). SMIL, Synchronized Multimedia Integration Language. RFC 4536
smil+xml SMIL, Synchronized Multimedia Integration Language. RFC 4536
smpte336mSMPTE ST 336. RFC 6597
soap+fastinfoset   
soap+xml  RFC 3902
sparql-query   
sparql-results+xml   
spirits-event+xmlSPIRITS, Services in PSTN requesting Internet Services. RFC 3910
srgsSRGS, Speech Recognition Grammar Specification. RFC 4267
srgs+xml  RFC 4267
ssml+xmlSSML, Speech Synthesis Markup Language. RFC 4267
timestamp-query TSP, Time Stamp Protocol. RFC 3161
timestamp-reply TSP, Time Stamp Protocol. RFC 3161
tve-trigger  
ulpfec RFC 5109
vemmi VEMMI, VErsatile MultiMedia Interface. RFC 2122
vnd.3gpp.pic-bw-large  
vnd.3gpp.pic-bw-small  
vnd.3gpp.pic-bw-var  
vnd.3gpp.smsShort Messaging Service. 
vnd.3M.Post-it-Notes  
vnd.accpac.simply.asoSimply Accounting. 
vnd.accpac.simply.impSimply Accounting. 
vnd.acucobol  
vnd.acucorp  
vnd.adobe.xfdf  
vnd.aether.impAether Wireless Instant Messaging Protocol. 
vnd.amiga.ami  
vnd.anser-web-certificate-issue-initiationANSER-WEB Terminal Client.  
vnd.anser-web-funds-transfer-initiationANSER-WEB Terminal Client.  
vnd.audiographAudioGraph. 
vnd.blueice.multipass  
vnd.bmiBMI. 
vnd.businessobjectsBusinessObjects. 
vnd.canon-cpdlCanon PDL. 
vnd.canon-lipsLBP Image Processing System. 
vnd.cinderella  
vnd.claymore  
vnd.commerce-battelle  
vnd.commonspaceCommonSpace. 
vnd.cosmocallerCosmoCaller. 
vnd.contact.cmsg  
vnd.criticaltools.wbs+xml  
vnd.ctc-posmlContinuum Technology Corporation PosML. 
vnd.cups-postscriptCommon UNIX Printing System. 
vnd.cups-rasterCommon UNIX Printing System. 
vnd.cups-rawCommon UNIX Printing System. 
vnd.curl  
vnd.cybank  
vnd.data-vision.rdz  
vnd.dna  
vnd.dpgraphDPGraph. 
vnd.dreamfactory  
vnd.dxrDigital Xpress Reports. 
vnd.ecdis-updateElectronic Navigational Chart and Display Systems.  
vnd.ecowin.chart  
vnd.ecowin.filerequest  
vnd.ecowin.fileupdate  
vnd.ecowin.series  
vnd.ecowin.seriesrequest  
vnd.ecowin.seriesupdate  
vnd.enliven  
vnd.epson.esf  
vnd.epson.msf  
vnd.epson.quickanime  
vnd.epson.salt  
vnd.epson.ssf  
vnd.ericsson.quickcall  
vnd.eudora.data  
vnd.fdfForms Data Format. 
vnd.ffsns  
vnd.fintsFinTS. 
vnd.FloGraphIt  
vnd.framemakerFrameMaker Normal Format. 
vnd.fsc.weblaunch  
vnd.fujitsu.oasys  
vnd.fujitsu.oasys2  
vnd.fujitsu.oasys3  
vnd.fujitsu.oasysgp  
vnd.fujitsu.oasysprs  
vnd.fujixerox.ddd  
vnd.fujixerox.docuworks  
vnd.fujixerox.docuworks.binder  
vnd.fut-misnet  
vnd.genomatix.tuxedo  
vnd.grafeq  
vnd.groove-account  
vnd.groove-help  
vnd.groove-identity-message  
vnd.groove-injector  
vnd.groove-tool-message  
vnd.groove-tool-template  
vnd.groove-vcard  
vnd.hbci  
vnd.hhe.lesson-player  
vnd.hp-HPGL  
vnd.hp-hpid  
vnd.hp-hps  
vnd.hp-PCL  
vnd.hp-PCLXL  
vnd.httphone  
vnd.hzn-3d-crossword  
vnd.ibm.afplinedata  
vnd.ibm.electronic-media  
vnd.ibm.MiniPay  
vnd.ibm.modcapMO:DCA-P. 
vnd.ibm.rights-management  
vnd.ibm.secure-container  
vnd.informix-visionary  
vnd.intercon.formnet  
vnd.intertrust.digibox  
vnd.intertrust.nncp  
vnd.intu.qbo  
vnd.intu.qfx  
vnd.ipunplugged.rcprofile  
vnd.irepository.package+xml  
vnd.is-xpr  
vnd.japannet-directory-service  
vnd.japannet-jpnstore-wakeup  
vnd.japannet-payment-wakeup  
vnd.japannet-registration  
vnd.japannet-registration-wakeup  
vnd.japannet-setstore-wakeup  
vnd.japannet-verification  
vnd.japannet-verification-wakeup  
vnd.jispJISP, Jabber Icon Style Packages. 
vnd.kde.karbon  
vnd.kde.kchart  
vnd.kde.kformula  
vnd.kde.kivio  
vnd.kde.kontour  
vnd.kde.kpresenter  
vnd.kde.kspread  
vnd.kde.kword  
vnd.kenameaapp  
vnd.kidspiration  
vnd.Kinar  
vnd.koan  
vnd.liberty-request+xml  
vnd.llamagraphics.life-balance.desktop  
vnd.llamagraphics.life-balance.exchange+xml  
vnd.lotus-1-2-3  
vnd.lotus-approach  
vnd.lotus-freelance  
vnd.lotus-notes  
vnd.lotus-organizer  
vnd.lotus-screencam  
vnd.lotus-wordpro  
vnd.mcd  
vnd.mediastation.cdkey  
vnd.meridian-slingshot  
vnd.mfmp  
vnd.micrografx.flo  
vnd.micrografx.igx  
vnd.mif  
vnd.minisoft-hp3000-save  
vnd.mitsubishi.misty-guard.trustweb  
vnd.Mobius.DAF  
vnd.Mobius.DIS  
vnd.Mobius.MBK  
vnd.Mobius.MQY  
vnd.Mobius.MSL  
vnd.Mobius.PLC  
vnd.Mobius.TXF  
vnd.mophun.application  
vnd.mophun.certificate  
vnd.motorola.flexsuite  
vnd.motorola.flexsuite.adsi  
vnd.motorola.flexsuite.fis  
vnd.motorola.flexsuite.gotap  
vnd.motorola.flexsuite.kmr  
vnd.motorola.flexsuite.ttc  
vnd.motorola.flexsuite.wem  
vnd.mozilla.xul+xml  
vnd.ms-artgalry  
vnd.ms-asfASF, Active Streaming Format. 
vnd.ms-excel  
vnd.ms-lrm  
vnd.ms-powerpoint  
vnd.ms-project  
vnd.ms-tnefTNEF, Transport Neutral Encoding Format. 
vnd.ms-works  
vnd.ms-wpl  
vnd.mseq  
vnd.msign  
vnd.music-niff  
vnd.musician  
vnd.nervana  
vnd.netfpx  
vnd.noblenet-directory  
vnd.noblenet-sealer  
vnd.noblenet-web  
vnd.nokia.landmarkcollection+xml  
vnd.nokia.radio-preset  
vnd.nokia.radio-presets  
vnd.novadigm.EDM  
vnd.novadigm.EDX  
vnd.novadigm.EXT  
vnd.obn  
vnd.omads-email+xml  
vnd.omads-file+xml  
vnd.omads-folder+xml  
vnd.osa.netdeploy  
vnd.palm  
vnd.paos.xml  
vnd.pg.format  
vnd.pg.osasli  
vnd.picsel  
vnd.powerbuilder6  
vnd.powerbuilder6-s  
vnd.powerbuilder7  
vnd.powerbuilder7-s  
vnd.powerbuilder75  
vnd.powerbuilder75-s  
vnd.previewsystems.box  
vnd.publishare-delta-tree  
vnd.pvi.ptid1  
vnd.pwg-multiplexed  RFC 3391
vnd.pwg-xhtml-print+xml  
vnd.Quark.QuarkXPressQuarkXPress. 
vnd.rapid  
vnd.RenLearn.rlprint  
vnd.s3sms  
vnd.sealed.doc  
vnd.sealed.eml  
vnd.sealed.mht  
vnd.sealed.net  
vnd.sealed.ppt  
vnd.sealed.xls  
vnd.sealedmedia.softseal.html  
vnd.sealedmedia.softseal.pdf  
vnd.seemail  
vnd.shana.informed.formdata  
vnd.shana.informed.formtemplate  
vnd.shana.informed.interchange  
vnd.shana.informed.package  
vnd.smaf  
vnd.sss-cod  
vnd.sss-dtf  
vnd.sss-ntf  
vnd.street-stream  
vnd.sus-calendar  
vnd.svd  
vnd.swiftview-ics  
vnd.syncml.ds.notification  
vnd.syncml.+xml  
vnd.triscape.mxs  
vnd.trueapp  
vnd.truedoc  
vnd.ufdlUFDL, Universal Forms Description Language. 
vnd.uiq.theme  
vnd.uplanet.alert  
vnd.uplanet.alert-wbxml  
vnd.uplanet.bearer-choice  
vnd.uplanet.bearer-choice-wbxml  
vnd.uplanet.cacheop  
vnd.uplanet.cacheop-wbxml  
vnd.uplanet.channel  
vnd.uplanet.channel-wbxml  
vnd.uplanet.list  
vnd.uplanet.list-wbxml  
vnd.uplanet.listcmd  
vnd.uplanet.listcmd-wbxml  
vnd.uplanet.signal  
vnd.vcx  
vnd.vectorworks  
vnd.vidsoft.vidconference  
vnd.visio  
vnd.visionary  
vnd.vividence.scriptfile  
vnd.vsfViewPort Streaming Format. 
vnd.wap.sic  
vnd.wap.slc  
vnd.wap.wbxmlWAP Binary XML Content Format. 
vnd.wap.wmlc  
vnd.wap.wmlscriptcWMLScript. 
vnd.webturbo  
vnd.wordperfect  
vnd.wqd  
vnd.wrq-hp3000-labelled  
vnd.wt.stf  
vnd.wv.csp+xml  
vnd.wv.csp+wbxml  
vnd.wv.ssp+xml  
vnd.xara  
vnd.xfdlXFDL, Extensible Forms Description Language. 
vnd.yamaha.hv-dic  
vnd.yamaha.hv-script  
vnd.yamaha.hv-voice  
vnd.yamaha.smaf-audioSMAF-Audio. 
vnd.yamaha.smaf-phraseSMAF-Phrase. 
vnd.yellowriver-custom-menu  
vnd.zzazz.deck+xml  
voicexml+xml  RFC 4267
vq-rtcpxr SIP, Session Initiation Protocol vocie quality reporting. RFC 6035
watcherinfo+xml SIP, Session Initiation Protocol watcher. RFC 3858
whoispp-query Whois++. RFC 2957
whoispp-response Whois++. RFC 2958
witaWang Information Transfer Architecture. 
wordperfect5.1  
wsdl+xmlWSDL, Web Services Description Language. 
wspolicy+xml  
x400-bp  RFC 1494
xcap-att+xml RFC 4825
xcap-caps+xml RFC 4825
xcap-el+xml RFC 4825
xcap-error+xml RFC 4825
xcap-ns+xml RFC 4825
xenc+xml  
xhtml-voice+xmlobsolete. 
xhtml+xml  RFC 3236
xml XML, Extensible Markup Language. RFC 2376, RFC 3023
xml-dtd  RFC 3023
xml-external-parsed-entity  RFC 3023
xmpp+xml XMPP, eXtensible Messaging and Presence Protocol. RFC 3923
xop+xml  
xspf+xml  
xv+xmlXHTML+Voice. RFC 4374
yang  RFC 6020
yin+xml  RFC 6020
zip  
zlibZLIB. RFC 6713

Audio. Type.
The body contains audio data.

SubtypeDescriptionReference
1d-interleaved-parityfec1-D Interleaved Parity Forward Error Correction. RFC 6015
32kadpcm  RFC 2421, RFC 3802
3gpp  RFC 3839
3gpp2  RFC 4393
ac3  RFC 4184
AMRAdaptive Multi-Rate. RFC 3267, RFC 4867
AMR-WBAdaptive Multi-Rate Wideband. RFC 3267, RFC 4867
amr-wb+Extended Adaptive Multi-Rate Wideband. RFC 4352
asc  
ATRAC-ADVANCED-LOSSLESS  
ATRAC-X  
ATRAC3  
basic  RFC 2045, RFC 2046
BV16BroadVoice16 RFC 4298
BV32BroadVoice32 RFC 4298
clearmode  RFC 4040
CN  RFC 3389
DAT12  RFC 3190
dls RFC 4613
dsr-es201108  RFC 3557
dsr-es202050  RFC 4060
dsr-es202211  RFC 4060
dsr-es202212  RFC 4060
DVI4  RFC 3555, RFC 4856
eac3 RFC 4598
evrc  RFC 3558
EVRC-QCP  RFC 3625
EVRC0  RFC 3558
ECRC1 RFC 4788
ECRCB RFC 4788, RFC 5188
ECRCB0 RFC 4788, RFC 5188
ECRCB1 RFC 4788
EVRCWB RFC 5188
EVRCWB0 RFC 5188
EVRCWB1 RFC 5188
example RFC 4735
G719 G.719. RFC 5404
G722  RFC 3555
G.722.1  RFC 3047
G723  RFC 3555
G726-16  RFC 3555
G726-24  RFC 3555
G726-32  RFC 3555
G726-40  RFC 3555
G728  RFC 3555
G729  RFC 3555
G7291G.729.1 RFC 4749
G729D  RFC 3555
G729E  RFC 3555
GSM  RFC 3555
GSM-EFR  RFC 3555
GSM-HR-08  RFC 5993
iLBC  RFC 3952
L8  RFC 3555
L16  RFC 2586, RFC 3555
L20  RFC 3190
L24  RFC 3190
LPC  RFC 3555
mobile-xmp  RFC 4723
mp4  RFC 4337
MP4A-LATM  RFC 3016
MPAMPEG audio. RFC 3555
mpa-robust  RFC 3119, RFC 5219
mpeg  RFC 3003
mpeg4-genericMPEG-4. RFC 3640
ogg Ogg Bitstream Format.RFC 5334
parityfec  RFC 3009, RFC 5109
PCMA  RFC 3555, RFC 4856
PCMA-WBG.711.1. RFC 5391
PCMU  RFC 3555
PCMU-WBG.711.1. RFC 5391
prs.sid  
QCELP  RFC 3555, RFC 3625
RED  RFC 3555
rtp-enc-aescm128  
rtp-midi RFC 4695
rtx RFC 4588
SMV  RFC 3558
SMV-QCP  RFC 3625
SMV0  RFC 3558
sp-midiScalable Polyphony MIDI. 
speex RFC 5574
t140c  RFC 4351
t38ITU-T Recommendation T.38.RFC 4612
telephone-event  RFC 4733
tone  RFC 4733
ulpfec RFC 5109
VDVI  RFC 3555
VMR-WBVariable-Rate Multimode Wideband. RFC 4348
vnd.3gpp.iufp  
vnd.4SB  
vnd.audiokoz  
vnd.CELP  
vnd.cisco.nse  
vnd.cmles.radio-eventsCML Emergency Services. 
vnd.cns.anp1  
vnd.cns.inf1  
vnd.digital-winds  
vnd.dlna.adtsDLNA, Digital Living Network Alliance. 
vnd.dolby.heaac.1  
vnd.dolby.heaac.2  
vnd.dolby.mlp  
vnd.dolby.mps  
vnd.dolby.pl2  
vnd.dolby.pl2x  
vnd.dolby.pl2z  
vnd.dolby.pulse.1  
vnd.dra  
vnd.dts  
vnd.dts.hd  
vnd.everad.plj  
vnd.hns.audio  
vnd.lucent.voice  
vnd.ms-playready.media.pya  
vnd.nokia.mobile-xmf  
vnd.nortel.vbk  
vnd.nuera.ecelp4800  
vnd.nuera.ecelp7470  
vnd.nuera.ecelp9600  
vnd.octel.sbc  
vnd.qcelpdeprecated. RFC 3625
vnd.rhetorex.32kadpcm  
vnd.sealedmedia.softseal.mpeg  
vnd.vmx.cvsd  
vorbis RFC 5215
vorbis-config RFC 5215

Image. Media type.
(RFC 2046) A media type of "image" indicates that the body contains an image. The subtype names the specific image format. These names are not case sensitive. An initial subtype is "jpeg" for the JPEG format using JFIF encoding.

SubtypeDescriptionReference
cgmComputer Graphics Metafile. 
fits FITS, Flexible Image Transport System. 
g3fax  RFC 1494
gif  RFC 2045, RFC 2046
iefImage Exchange Format. RFC 1314
jp2  RFC 3745
jpeg  RFC 2045, RFC 2046
jpm  RFC 3745
jpx  RFC 3745
naplps  
png PNG, Portable Network Graphics. RFC 2083.
prs.btif  
prs.pti  
t38  RFC 3362
tiffTag Image File Format. RFC 1528, RFC 3302, RFC 3949
tiff-fxTag Image File Format Fax eXtended. RFC 3949, RFC 3950
vnd.cns.inf2  
vnd.djvuDjVu. 
vnd.dwg  
vnd.dxf  
vnd.fastbidsheet  
vnd.fpx  
vnd.fst  
vnd.fujixerox.edmics-mmr  
vnd.fujixerox.edmics-rlc  
vnd.globalgraphics.pgb  
vnd.microsoft.icon  
vnd.mix  
vnd.ms-modi  
vnd.net-fpx  
vnd.sealed.png  
vnd.sealedmedia.softseal.gif  
vnd.sealedmedia.softseal.jpg  
vnd.svf  
vnd.wap.wbmp  
vnd.xiff  

Message. Media type.
(RFC 2046) It is frequently desirable, in sending mail, to encapsulate another mail message. A special media type, "message", is defined to facilitate this. In particular, the "rfc822" subtype of "message" is used to encapsulate RFC 822 messages.

SubtypeDescriptionReference
CPIMCPIM, Common Profile for Instant Messaging. RFC 3862
delivery-status  RFC 3464
disposition-notification  RFC 3798
example RFC 4735
external-body  RFC 1873, RFC 2045, RFC 2046
feedback-report  
global RFC 5335
global-delivery-status RFC 5337
global-disposition-notification RFC 5337
global-headers RFC 5337
http HTTP, HyperText Transfer Protocol.RFC 2616
imdn+xml  RFC 5438
news(obsolete). RFC 1036
partial  RFC 2045, RFC 2046
rfc822  RFC 2045, RFC 2046
s-http HTTP, HyperText Transfer Protocol. RFC 2660
sip SIP, Session Initiation Protocol. RFC 3261
sipfrag SIP, Session Initiation Protocol. RFC 3420
tracking-status  RFC 3886
vnd.si.simpSIMP, Shady Internet Media Protocol. http://www.shadyindustries.biz/specs/ssd/ssd2.txt

Model. Media type.

SubtypeDescriptionReference
iges  
mesh  RFC 2077
vnd.dwf  
vnd.flatland.3dml  
vnd.gdl  
vnd.gs.gdl  
vnd.gtw  
vnd.mts  
vnd.parasolid.transmit.binary  
vnd.parasolid.transmit.text  
vnd.vtu  
vrml  RFC 2077

Multipart. Media type.
(RFC 2046) In the case of multipart entities, in which one or more different sets of data are combined in a single body, a "multipart" media type field must appear in the entity's header. The body must then contain one or more body parts, each preceded by a boundary delimiter line, and the last one followed by a closing boundary delimiter line. After its boundary delimiter line, each body part then consists of a header area, a blank line, and a body area. Thus a body part is similar to an RFC 822 message in syntax, but different in meaning.

SubtypeDescriptionReference
alternative  RFC 1766, RFC 2045, RFC 2046
appledouble  RFC 1740
byteranges  RFC 2068
digest  RFC 2045, RFC 2046
encrypted  RFC 1847
form-data  RFC 1867, RFC 2388
header-set  
mixed  RFC 2045, RFC 2046
parallel  RFC 2045, RFC 2046
related  RFC 1872, RFC 2112, RFC 2387
report  RFC 3462
signed  RFC 1847
voice-message  RFC 2423, RFC 3801

Text. Media type.
This media type is intended for sending material which is principally textual in form. A "charset" parameter may be used to indicate the character set of the body text for "text" subtypes, notably including the subtype "text/plain", which is a generic subtype for plain text. Plain text does not provide for or allow formatting commands, font attribute specifications, processing instructions, interpretation directives, or content markup. Plain text is seen simply as a linear sequence of characters, possibly interrupted by line breaks or page breaks. Plain text may allow the stacking of several characters in the same position in the text. Plain text in scripts like Arabic and Hebrew may also include facilitites that allow the arbitrary mixing of text segments with opposite writing directions. Beyond plain text, there are many formats for representing what might be known as "rich text". An interesting characteristic of many such representations is that they are to some extent readable even without the software that interprets them. It is useful, then, to distinguish them, at the highest level, from such unreadable data as images, audio, or text represented in an unreadable form. In the absence of appropriate interpretation software, it is reasonable to show subtypes of "text" to the user, while it is not reasonable to do so with most nontextual data. Such formatted textual data should be represented using subtypes of "text".

SubtypeDescriptionReference
1d-interleaved-parityfec1-D Interleaved Parity Forward Error Correction. RFC 6015
calendariCalendar, Internet Calendaring and Scheduling Core Object Specification. RFC 5545
css  RFC 2318
csvComma Separated Value files. RFC 4180
directory  RFC 2425
dns  RFC 4027
ecmascriptobsolete. RFC 4329
enriched  RFC 1896
html HTML, Hypertext Markup Language RFC 2854
javascriptobsolete. RFC 4329
mixed  RFC 2045, RFC 2046
n3 Notation3.  
parityfec  RFC 3009
plain  RFC 2046, RFC 3676, RFC 5147
prs.fallenstein.rst  
prs.lines.tag  
red RFC 4102
rfc822-headers  RFC 3462
richtext  RFC 2045, RFC 2046
rtf 
rtx  
sgmlStandard Generalized Markup Language. RFC 1874
t140T.140. RFC 4103
t140c  
tab-separated-values  
troff  RFC 4263
turtle Turtle. 
ulpfec RFC 5109
uri-list  RFC 2483
vnd.abc  
vnd.curl  
vnd.DMClientScript  
vnd.esmertec.theme-descriptor  
vnd.fly  
vnd.fmi.flexstor  
vnd.in3d.3dml  
vnd.in3d.spot  
vnd.IPTC.NewsML  
vnd.IPTC.NITF  
vnd.latex-z  
vnd.motorola.reflex  
vnd.ms-mediapackage  
vnd.net2phone.commcenter.command  
vnd.radisys.msml-basic-layout RFC 5707
vnd.si.uricatalogue  
vnd.sun.j2me.app-descriptor  
vnd.wap.si  
vnd.wap.sl  
vnd.wap.wml  
vnd.wap.wmlscript  
xml XML, Extensible Markup Language. RFC 2376, RFC 3023
xml-external-parsed-entity  RFC 3023

Video. Media type.
This media type indicates that the body contains a time varying picture image, possibly with color and coordinated sound. The term 'video' is used in its most generic sense, rather than with reference to any particular technology or format, and is not meant to preclude subtypes such as animated drawings encoded compactly. Note that although in general this document strongly discourages the mixing of multiple media in a single body, it is recognized that many so-called video formats include a representation for synchronized audio, and this is explicitly permitted for subtypes of "video".

SubtypeDescriptionReference
1d-interleaved-parityfec1-D Interleaved Parity Forward Error Correction. RFC 6015
3gpp  RFC 3839
3gpp2  RFC 4393
3gpp-tt3GPP Timed Text. RFC 4396
BMPEG  RFC 3555
BT565  RFC 3555
CelB  RFC 3555
DV  RFC 3189
example  
H261  RFC 3555
H263  RFC 3555
H263-1998  RFC 3555
H263-2000  RFC 3555
H264H.264 RFC 6184
JPEG  RFC 3555
jpeg2000JPEG 2000. RFC 5371
MJ2  RFC 3745
MP1SMPEG-1 Systems Streams. RFC 3555
MP2PMPEG-2 Program Streams. RFC 3555
MP2TMPEG-2 Transport Streams. RFC 3555
mp4MPEG-4 RFC 4337
MP4A-LATM  RFC 3016
MP4V-ES  RFC 3016
mpeg  RFC 2045, RFC 2046
mpeg4-genericMPEG-4 RFC 3640
MPVMPEG-1 or -2 Elementary Streams. RFC 3555
nv  RFC 3555
ogg Ogg Bitstream Format.RFC 5334
parityfec  RFC 3009
pointer  RFC 2862
quicktime  
raw  RFC 4175, RFC 4421
rtp-enc-aescm128  
rtx  
SMPTE292MSMPTE 292M RFC 3497
ulpfec RFC 5109
vc1VC-1, Video Codec 1.RFC 4425
vnd.CCTV  
vnd.dlna.mpeg-tts  
vnd.fvt  
vnd.hns.video  
vnd.iptvforum.1dparityfec-1010  
vnd.iptvforum.1dparityfec-2005  
vnd.iptvforum.2dparityfec-1010  
vnd.iptvforum.2dparityfec-2005  
vnd.iptvforum.ttsavc  
vnd.iptvforum.ttsmpeg2  
vnd.motorola.video  
vnd.motorola.videop  
vnd.mpegurl  
vnd.ms-playready.media.pyv  
vnd.nokia.interleaved-multimedia  
vnd.nokia.videovoipNokia Videovoip. 
vnd.objectvideo  
vnd.sealed.mpeg1  
vnd.sealed.mpeg4  
vnd.sealed.swf  
vnd.sealedmedia.softseal.mov  
vnd.vivo  

Content-Description. Header field.
(RFC 2045) The ability to associate some descriptive information with a given body is often desirable. For example, it may be useful to mark an "image" body as "a picture of the Space Shuttle Endeavor." Such text may be placed in the Content-Description header field. This header field is always optional. The description is presumed to be given in the US-ASCII character set, although the mechanism specified in RFC 2047 may be used for non-US-ASCII Content-Description values.

Syntax:

description := "Content-Description" ":" *text


Content-Disposition. Header field.
An optional header field that can be used to convey presentational information.

Syntax:

disposition := "Content-Disposition" ":" disposition-type *(";" disposition-parm)

disposition-type := "inline" / "attachment" / extension-token ; values are not case-sensitive.

disposition-parm := filename-parm / creation-date-parm / modification-date-parm / read-date-parm / size-parm / parameter

filename-parm := "filename" "=" value

creation-date-parm := "creation-date" "=" quoted-date-time

modification-date-parm := "modification-date" "=" quoted-date-time

read-date-parm := "read-date" "=" quoted-date-time

size-parm := "size" "=" 1*DIGIT

quoted-date-time := quoted-string ; contents MUST be an RFC 822 `date-time' ; numeric timezones (+HHMM or -HHMM) MUST be used.


Content-features. Header field.
(RFC 2912) This header provides additional information about the message content directly contained or indirectly referenced in the corresponding MIME message part.

Syntax:

optional-field =/ "Content-features" ":" Feature-expr
Feature-expr = filter


Content-ID. Header field.
(RFC 2045) In constructing a high-level user agent, it may be desirable to allow one body to make reference to another. Accordingly, bodies may be labelled using the "Content-ID" header field, which is syntactically identical to the "Message-ID" header field. The Content-ID value may be used for uniquely identifying MIME entities in several contexts, particularly for caching data referenced by the message/external-body mechanism. Although the Content-ID header is generally optional, its use is MANDATORY in implementations which generate data of the optional MIME media type "message/external-body". That is, each message/external-body entity must have a Content-ID field to permit caching of such data. It is also worth noting that the Content-ID value has special semantics in the case of the multipart/alternative media type. This is explained in the section of RFC 2046 dealing with multipart/alternative.

Syntax:

id := "Content-ID" ":" msg-id


Content-MD5. Header field.
An optional header field which may be used to verify that the decoded data are the same data that were initially sent. This header may also be placed in the encapsulated headers of an object of type message/external-body, to be used to verify that the retreived and decoded data are the same data that were initially referenced.


Content-Transfer-Encoding. Header field.
Describes how the data contents in a message are encoded for transmission.

(RFC 2045) Many media types which could be usefully transported via email are represented, in their "natural" format, as 8bit character or binary data. Such data cannot be transmitted over some transfer protocols. For example, RFC 821 (SMTP) restricts mail messages to 7bit US-ASCII data with lines no longer than 1000 characters including any trailing CRLF line separator. It is necessary, therefore, to define a standard mechanism for encoding such data into a 7bit short line format. Proper labelling of unencoded material in less restrictive formats for direct use over less restrictive transports is also desireable. The Content-Transfer-Encoding field's value is a single token specifying the type of encoding, as enumerated below. Formally:

Syntax:

encoding := "Content-Transfer-Encoding" ":" mechanism

mechanism := "7bit" / "8bit" / "binary" / "quoted-printable" / "base64" / ietf-token / x-token


Message-Context. Header field.
This header provides information about the context and presentation characteristics of a message. A receiving user agent may use this information as a hint to optimally present the message.


Glossary:

Character Sets.
(RFC 2047) The 'charset' portion of an 'encoded-word' specifies the character set associated with the unencoded text. A 'charset' can be any of the character set names allowed in an MIME "charset" parameter of a "text/plain" body part, or any character set name registered with IANA for use with the MIME text/plain content-type. Some character sets use code-switching techniques to switch between "ASCII mode" and other modes. If unencoded text in an 'encoded-word' contains a sequence which causes the charset interpreter to switch out of ASCII mode, it MUST contain additional control codes such that ASCII mode is again selected at the end of the 'encoded-word'. (This rule applies separately to each 'encoded-word', including adjacent 'encoded-word's within a single header field.) When there is a possibility of using more than one character set to represent the text in an 'encoded-word', and in the absence of private agreements between sender and recipients of a message, it is recommended that members of the ISO-8859-* series be used in preference to other character sets.


RFCs:

[RFC 934] Proposed Standard for Message Encapsulation.

[RFC 1036] Standard for Interchange of USENET Messages.

[RFC 1049] A CONTENT-TYPE HEADER FIELD FOR INTERNET MESSAGES.

[RFC 1123] Requirements for Internet Hosts -- Application and Support.

[RFC 1154] Encoding Header Field for Internet Messages.

[RFC 1343] A User Agent Configuration Mechanism For Multimedia Mail Format Information.

[RFC 1344] Implications of MIME for Internet Mail Gateways.

[RFC 1428] Transition of Internet Mail from Just-Send-8 to 8 bit-SMTP/MIME.

[RFC 1524] A User Agent Configuration Mechanism For Multimedia Mail Format Information.

[RFC 1528] Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Technical Procedures.

[RFC 1554] ISO-2022-JP-2: Multilingual Extension of ISO-2022-JP.

[RFC 1555] Hebrew Character Encoding for Internet Messages.

[RFC 1556] Handling of Bi-directional Texts in MIME.

[RFC 1557] Korean Character Encoding for Internet Messages.

[RFC 1740] MIME Encapsulation of Macintosh files - MacMIME.

[RFC 1741] MIME Content Type for BinHex Encoded Files.

[RFC 1767] MIME Encapsulation of EDI Objects.

[RFC 1806] Communicating Presentation Information in Internet Messages: The Content-Disposition Header.

[RFC 1844] Multimedia E-mail (MIME) User Agent checklist.

[RFC 1847] Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted.

[RFC 1848] MIME Object Security Services.

[RFC 1864] The Content-MD5 Header Field.

[RFC 1873] Message/External-Body Content-ID Access Type.

[RFC 1874] SGML Media Types.

[RFC 1895] The Application/CALS-1840 Content-type.

[RFC 1896] The text/enriched MIME Content-type.

[RFC 1947] Greek Character Encoding for Electronic Mail Messages.

[RFC 2015] MIME Security with Pretty Good Privacy (PGP).

[RFC 2017] Definition of the URL MIME External-Body Access-Type.

[RFC 2045] Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies.

[RFC 2046] Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types.

[RFC 2047] MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text.

[RFC 2049] Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples.

[RFC 2076] Common Internet Message Headers.

[RFC 2077] The Model Primary Content Type for Multipurpose Internet Mail Extensions.

[RFC 2122] VEMMI URL Specification.

[RFC 2156] MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME.

[RFC 2157] Mapping between X.400 and RFC-822/MIME Message Bodies.

[RFC 2159] A MIME Body Part for FAX.

[RFC 2160] Carrying PostScript in X.400 and MIME.

[RFC 2161] A MIME Body Part for ODA.

[RFC 2183] Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field.

[RFC 2231] MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations.

[RFC 2318] The text/css Media Type.

[RFC 2387] The MIME Multipart/Related Content-type.

[RFC 2388] Returning Values from Forms: multipart/form-data.

[RFC 2392] Content-ID and Message-ID Uniform Resource Locators.

[RFC 2423] VPIM Voice Message MIME Sub-type Registration.

[RFC 2425] A MIME Content-Type for Directory Information.

[RFC 2426] vCard MIME Directory Profile.

[RFC 2442] The Batch SMTP Media Type.

[RFC 2445] Internet Calendaring and Scheduling Core Object Specification (iCalendar).

[RFC 2447] iCalendar Message-Based Interoperability Protocol (iMIP).

[RFC 2480] Gateways and MIME Security Multiparts.

[RFC 2483] URI Resolution Services Necessary for URN Resolution.

[RFC 2503] MIME Types for Use with the ISO ILL Protocol.

[RFC 2557] MIME Encapsulation of Aggregate Documents, such as HTML (MHTML).

[RFC 2560] X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP.

[RFC 2585] Internet X.509 Public Key Infrastructure Operational Protocols: FTP and HTTP.

[RFC 2586] The Audio/L16 MIME content type.

[RFC 2616] Hypertext Transfer Protocol -- HTTP/1.1.

[RFC 2652] MIME Object Definitions for the Common Indexing Protocol (CIP).

[RFC 2660] The Secure HyperText Transfer Protocol.

[RFC 2822] Internet Message Format.

[RFC 2833] RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals.

[RFC 2854] The 'text/html' Media Type.

[RFC 2862] RTP Payload Format for Real-Time Pointers.

[RFC 2910] Internet Printing Protocol/1.1: Encoding and Transport.

[RFC 2912] Indicating Media Features for MIME Content.

[RFC 2913] MIME Content Types in Media Feature Expressions.

[RFC 2927] MIME Directory Profile for LDAP Schema.

[RFC 2935] Internet Open Trading Protocol (IOTP) HTTP Supplement.

[RFC 2957] The application/whoispp-query Content-Type.

[RFC 2958] The application/whoispp-response Content-type.

[RFC 3003] The audio/mpeg Media Type.

[RFC 3009] Registration of parityfec MIME types.

[RFC 3016] RTP Payload Format for MPEG-4 Audio/Visual Streams.

[RFC 3023] XML Media Types.

[RFC 3029] Internet X.509 Public Key Infrastructure Data Validation and Certification Server Protocols.

[RFC 3047] RTP Payload Format for ITU-T Recommendation G.722.1.

[RFC 3073] Portable Font Resource (PFR) - application/font-tdpfr MIME Sub-type Registration.

[RFC 3080] The Blocks Extensible Exchange Protocol Core.

[RFC 3119] A More Loss-Tolerant RTP Payload Format for MP3 Audio.

[RFC 3156] MIME Security with OpenPGP.

[RFC 3189] RTP Payload Format for DV (IEC 61834) Video.

[RFC 3190] RTP Payload Format for 12-bit DAT Audio and 20- and 24-bit Linear Sampled Audio.

[RFC 3204] MIME media types for ISUP and QSIG Objects.

[RFC 3236] The 'application/xhtml+xml' Media Type.

[RFC 3240] Digital Imaging and Communications in Medicine (DICOM) - Application/dicom MIME Sub-type Registration.

[RFC 3249] Implementers Guide for Facsimile Using Internet Mail.

[RFC 3267] Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs.

[RFC 3282] Content Language Headers.

[RFC 3297] Content Negotiation for Messaging Services based on Email.

[RFC 3302] Tag Image File Format (TIFF) - image/tiff MIME Sub-type Registration.

[RFC 3335] MIME-based Secure Peer-to-Peer Business Data Interchange over the Internet.

[RFC 3362] Real-time Facsimile (T.38) - image/t38 MIME Sub-type Registration.

[RFC 3367] Common Name Resolution Protocol (CNRP).

[RFC 3389] Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN).

[RFC 3391] The MIME Application/Vnd.pwg-multiplexed Content-Type.

[RFC 3420] Internet Media Type message/sipfrag.

[RFC 3458] Message Context for Internet Mail.

[RFC 3459] Critical Content Multi-purpose Internet Mail Extensions (MIME) Parameter.

[RFC 3464] An Extensible Message Format for Delivery Status Notifications.

[RFC 3497] RTP Payload Format for Society of Motion Picture and Television Engineers (SMPTE) 292M Video.

[RFC 3555] MIME Type Registration of RTP Payload Formats.

[RFC 3557] RTP Payload Format for European Telecommunications Standards Institute (ETSI) European Standard ES 201 108 Distributed Speech Recognition Encoding.

[RFC 3558] RTP Payload Format for Enhanced Variable Rate Codecs (EVRC) and Selectable Mode Vocoders (SMV).

[RFC 3625] The QCP File Format and Associated Media Types.

[RFC 3640] RTP Payload Format for Transport of MPEG-4 Elementary Streams.

[RFC 3676] The Text/Plain Format and DelSp Parameters.

[RFC 3680] A Session Initiation Protocol (SIP) Event Package for Registrations.

[RFC 3745] MIME Type Registrations for JPEG 2000 (ISO/IEC 15444).

[RFC 3778] The application/pdf Media Type.

[RFC 3798] Message Disposition Notification.

[RFC 3801] Voice Profile for Internet Mail - version 2 (VPIMv2).

[RFC 3802] Toll Quality Voice - 32 kbit/s Adaptive Differential Pulse Code Modulation (ADPCM) MIME Sub-type Registration.

[RFC 3803] Content Duration MIME Header Definition.

[RFC 3823] MIME Media Type for the Systems Biology Markup Language (SBML).

[RFC 3830] MIKEY: Multimedia Internet KEYing.

[RFC 3839] MIME Type Registrations for 3rd Generation Partnership Project (3GPP) Multimedia files.

[RFC 3842] A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP).

[RFC 3858] An Extensible Markup Language (XML) Based Format for Watcher Information.

[RFC 3862] Common Presence and Instant Messaging (CPIM): Message Format.

[RFC 3863] Presence Information Data Format (PIDF).

[RFC 3864] Registration Procedures for Message Header Fields.

[RFC 3870] application/rdf+xml Media Type Registration.

[RFC 3880] Call Processing Language (CPL): A Language for User Control of Internet Telephony Services.

[RFC 3886] An Extensible Message Format for Message Tracking Responses.

[RFC 3902] The "application/soap+xml" media type.

[RFC 3910] The SPIRITS (Services in PSTN requesting Internet Services) Protocol.

[RFC 3923] End-to-End Signing and Object Encryption for the Extensible Messaging and Presence Protocol (XMPP).

[RFC 3938] Video-Message Message-Context.

[RFC 3950] Tag Image File Format Fax eXtended (TIFF-FX) - image/tiff-fx MIME Sub-type Registration.

[RFC 3952] Real-time Transport Protocol (RTP) Payload Format for internet Low Bit Rate Codec (iLBC) Speech.

[RFC 3994] Indication of Message Composition for Instant Messaging.

[RFC 4021] Registration of Mail and MIME Header Fields.

[RFC 4027] Domain Name System Media Types.

[RFC 4040] RTP Payload Format for a 64 kbit/s Transparent Call.

[RFC 4047] MIME Sub-type Registrations for Flexible Image Transport System (FITS).

[RFC 4060] RTP Payload Formats for European Telecommunications Standards Institute (ETSI) European Standard ES 202 050, ES 202 211, and ES 202 212 Distributed Speech Recognition Encoding.

[RFC 4102] Registration of the text/red MIME Sub-Type.

[RFC 4103] RTP Payload for Text Conversation.

[RFC 4130] MIME-Based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2 (AS2).

[RFC 4141] SMTP and MIME Extensions for Content Conversion.

[RFC 4155] The application/mbox Media Type.

[RFC 4175] RTP Payload Format for Uncompressed Video.

[RFC 4180] Common Format and MIME Type for Comma-Separated Values (CSV) Files.

[RFC 4194] The S Hexdump Format.

[RFC 4235] An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP).

[RFC 4249] Implementer-Friendly Specification of Message and MIME-Part Header Fields and Field Components.

[RFC 4263] Media Subtype Registration for Media Type text/troff.

[RFC 4267] The W3C Speech Interface Framework Media Types: application/voicexml+xml, application/ssml+xml, application/srgs, application/srgs+xml, application/ccxml+xml, and application/pls+xml.

[RFC 4287] The Atom Syndication Format.

[RFC 4288] Media Type Specifications and Registration Procedures.

[RFC 4289] Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures.

[RFC 4298] RTP Payload Format for BroadVoice Speech Codecs.

[RFC 4329] Scripting Media Types.

[RFC 4337] MIME Type Registration for MPEG-4.

[RFC 4348] Real-Time Transport Protocol (RTP) Payload Format for the Variable-Rate Multimode Wideband (VMR-WB) Audio Codec.

[RFC 4351] Real-Time Transport Protocol (RTP) Payload for Text Conversation Interleaved in an Audio Stream.

[RFC 4352] RTP Payload Format for the Extended Adaptive Multi-Rate Wideband (AMR-WB+) Audio Codec.

[RFC 4354] A Session Initiation Protocol (SIP) Event Package and Data Format for Various Settings in Support for the Push-to-Talk over Cellular (PoC) Service.

[RFC 4374] The application/xv+xml Media Type.

[RFC 4393] MIME Type Registrations for 3GPP2 Multimedia Files.

[RFC 4396] RTP Payload Format for 3rd Generation Partnership Project (3GPP) Timed Text.

[RFC 4421] RTP Payload Format for Uncompressed Video: Additional Colour Sampling Modes.

[RFC 4425] RTP Payload Format for Video Codec 1 (VC-1).

[RFC 4463] A Media Resource Control Protocol (MRCP) Developed by Cisco, Nuance, and Speechworks.

[RFC 4539] Media Type Registration for the Society of Motion Picture and Television Engineers (SMPTE) Material Exchange Format (MXF).

[RFC 4749] RTP Payload Format for the G.729.1 Audio Codec.

[RFC 5147] URI Fragment Identifiers for the text/plain Media Type.

[RFC 5222] LoST: A Location-to-Service Translation Protocol.

[RFC 5322] Internet Message Format.

[RFC 5337] Internationalized Delivery Status and Disposition Notifications.

[RFC 5362] The Session Initiation Protocol (SIP) Pending Additions Event Package.

[RFC 5371] RTP Payload Format for JPEG 2000 Video Streams.

[RFC 5391] RTP Payload Format for ITU-T Recommendation G.711.1.

[RFC 5408] Identity-Based Encryption Architecture and Supporting Data Structures.

[RFC 5438] Instant Message Disposition Notification (IMDN).

[RFC 5621] Message Body Handling in the Session Initiation Protocol (SIP).

[RFC 5993] RTP Payload Format for Global System for Mobile Communications Half Rate (GSM-HR).

[RFC 6015] RTP Payload Format for 1-D Interleaved Parity Forward Error Correction (FEC).

[RFC 6020] YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF).

[RFC 6184] RTP Payload Format for H.264 Video.

[RFC 6522] The Multipart/Report Media Type for the Reporting of Mail System Administrative Messages.

[RFC 6713] The 'application/zlib' and 'application/gzip' Media Types.


Publications:


Obsolete RFCs:

[RFC 561] Standardizing Network Mail Headers.

[RFC 733] STANDARD FOR THE FORMAT OF ARPA NETWORK TEXT MESSAGES.

[RFC 822] STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES.

[RFC 1341] MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies.

[RFC 1342] Representation of Non-ASCII Text in Internet Message Headers.

[RFC 1486] An Experiment in Remote Printing.

[RFC 1495] Mapping between X.400 and RFC-822 Message Bodies.

[RFC 1521] MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies.

[RFC 1522] MIME (Multipurpose Internet Mail Extensions) Part Two: Message Header Extensions for Non-ASCII Text.

[RFC 1523] The text/enriched MIME Content-type.

[RFC 1544] The Content-MD5 Header Field.

[RFC 1563] The text/enriched MIME Content-type.

[RFC 1590] Media Type Registration Procedure.

[RFC 1766] Tags for the Identification of Languages.

[RFC 1820] Multimedia E-mail (MIME) User Agent Checklist.

[RFC 1866] Hypertext Markup Language - 2.0.

[RFC 1867] Form-based File Upload in HTML.

[RFC 1872] The MIME Multipart/Related Content-type.

[RFC 1892] The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages.

[RFC 1894] An Extensible Message Format for Delivery Status Notifications.

[RFC 1911] Voice Profile for Internet Mail.

[RFC 2048] Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures.

[RFC 2110] MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML).

[RFC 2111] Content-ID and Message-ID Uniform Resource Locators.

[RFC 2112] The MIME Multipart/Related Content-type.

[RFC 2184] MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations.

[RFC 2298] An Extensible Message Format for Message Disposition Notifications.

[RFC 2301] File Format for Internet Fax.

[RFC 2302] Tag Image File Format (TIFF) - image/tiff MIME Sub-type Registration.

[RFC 2376] XML Media Types.

[RFC 2421] Voice Profile for Internet Mail - version 2.

[RFC 2422] Toll Quality Voice - 32 kbit/s ADPCM MIME Sub-type Registration.

[RFC 2424] Content Duration MIME Header Definition.

[RFC 2565] Internet Printing Protocol/1.0: Encoding and Transport.

[RFC 2646] The Text/Plain Format Parameter.

[RFC 2793] RTP Payload for Text Conversation.

[RFC 3250] Tag Image File Format Fax eXtended (TIFF-FX) - image/tiff-fx MIME Sub-type Registration.

[RFC 3462] The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages.

[RFC 3546] Transport Layer Security (TLS) Extensions.

[RFC 3984] RTP Payload Format for H.264 Video.


Description Glossary RFCs Publications Obsolete RFCs