RFC 2480: Gateways and MIME Security Multiparts
In plain English — editorial summary, not part of the RFC
This document examines the problems associated with use of MIME security multiparts and gateways to non-MIME environments. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2480
- Published
- January 1999
- Authors
- N. Freed
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2388Returning Values from Forms: multipart/form-dataObsoleted
August 1998
- RFC 3003The audio/mpeg Media TypeCurrent
November 2000
- RFC 3362Real-time Facsimile (T.38) - image/t38 MIME Sub-type RegistrationCurrent
September 2002
- RFC 2445Internet Calendaring and Scheduling Core Object Specification (iCalendar)Obsoleted
November 1998
- RFC 2425A MIME Content-Type for Directory InformationObsoleted
September 1998
- RFC 2557MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)Current
March 1999
- RFC 2392Content-ID and Message-ID Uniform Resource LocatorsCurrent
August 1998
- RFC 2652MIME Object Definitions for the Common Indexing Protocol (CIP)Current
August 1999
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?