RFC 2077: The Model Primary Content Type for Multipurpose Internet Mail Extensions
In plain English — editorial summary, not part of the RFC
The purpose of this memo is to propose an update to Internet RFC 2045 to include a new primary content-type to be known as "model". [STANDARDS-TRACK]
Document record
- Document ID
- RFC2077
- Published
- January 1997
- Authors
- S. Nelson; C. Parks; Mitra
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 13
- Also known as
- —
- Updated by:
- RFC 9141
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8255Multiple Language Content TypeCurrent
October 2017
- RFC 2503MIME Types for Use with the ISO ILL ProtocolCurrent
February 1999
- RFC 2049Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and ExamplesCurrent
November 1996
- RFC 2047MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII TextUpdated
November 1996
- RFC 2045Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message BodiesUpdated
November 1996
- RFC 1894An Extensible Message Format for Delivery Status NotificationsObsoleted
January 1996
- RFC 2565Internet Printing Protocol/1.0: Encoding and TransportObsoleted
April 1999
- RFC 7433A Mechanism for Transporting User-to-User Call Control Information in SIPCurrent
January 2015
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?