RFC 2017: Definition of the URL MIME External-Body Access-Type
In plain English — editorial summary, not part of the RFC
This memo defines a new access-type for message/external-body MIME parts for Uniform Resource Locators (URLs). [STANDARDS-TRACK]
Document record
- Document ID
- RFC2017
- Published
- October 1996
- Authors
- N. Freed; K. Moore; A. Cargille
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2156MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIMECurrent
January 1998
- RFC 5092IMAP URL SchemeUpdated
November 2007
- RFC 2110MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)Obsoleted
March 1997
- RFC 2112The MIME Multipart/Related Content-typeObsoleted
March 1997
- RFC 1894An Extensible Message Format for Delivery Status NotificationsObsoleted
January 1996
- RFC 1892The Multipart/Report Content Type for the Reporting of Mail System Administrative MessagesObsoleted
January 1996
- RFC 2157Mapping between X.400 and RFC-822/MIME Message BodiesCurrent
January 1998
- RFC 2158X.400 Image Body PartsCurrent
January 1998
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?