RFC 1521

E807560

RFC 1521 is the foundational specification that defines the Multipurpose Internet Mail Extensions (MIME) standard for formatting and encoding multimedia email messages on the Internet.

Try in SPARQL Jump to: Surface forms Statements Referenced by

All labels observed (1)

Label Occurrences
RFC 1521 canonical 1

Statements (49)

Predicate Object
instanceOf Internet standard specification
Request for Comments
abbreviation MIME Part One NERFINISHED
appliesTo Internet email
SMTP-based message transfer
area Applications
category Standards Track
defines 7bit content-transfer-encoding
8bit content-transfer-encoding
Content-Description header field
Content-ID header field
Content-Transfer-Encoding header field NERFINISHED
Content-Type header field
MIME boundary parameter
MIME entity
MIME-Version header field
Multipurpose Internet Mail Extensions NERFINISHED
application content type
audio content type
base64 content-transfer-encoding
binary content-transfer-encoding
body part
image content type
message content type
multipart content type
quoted-printable content-transfer-encoding
text content type
video content type
isObsoletedBy RFC 2045 NERFINISHED
RFC 2046 NERFINISHED
language English
obsoletes RFC 1341 NERFINISHED
publishedBy Internet Engineering Task Force
surface form: IETF

Internet Engineering Task Force
publishedInSeries RFC series NERFINISHED
relatedTo MIME NERFINISHED
RFC 1522
specifies mechanisms for describing the format of Internet message bodies
mechanisms for encoding multimedia email messages
mechanisms for specifying the format of Internet message bodies
standardizes MIME content types NERFINISHED
MIME message headers
MIME transfer encodings
encoding of Internet message bodies
format of Internet message bodies
message body parts
multipart message structure
status Obsoleted
title MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies NERFINISHED

Referenced by (1)

Full triples — surface form annotated when it differs from this entity's canonical label.

RFC 1652 relatedTo RFC 1521