RFC 3362: Real-time Facsimile (T.38) - image/t38 MIME Sub-type Registration
In plain English — editorial summary, not part of the RFC
This document describes the registration of the MIME sub-type image/t38. The encoding is defined by [T.38] and is intended for use as an SDP media descriptor.
Document record
- Document ID
- RFC3362
- Published
- September 2002
- Authors
- G. Parsons
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3003The audio/mpeg Media TypeCurrent
November 2000
- RFC 2480Gateways and MIME Security MultipartsCurrent
January 1999
- RFC 2388Returning Values from Forms: multipart/form-dataObsoleted
August 1998
- RFC 3335MIME-based Secure Peer-to-Peer Business Data Interchange over the InternetCurrent
September 2002
- RFC 3420Internet Media Type message/sipfragCurrent
November 2002
- RFC 3302Tag Image File Format (TIFF) - image/tiff MIME Sub-type RegistrationCurrent
September 2002
- RFC 3464An Extensible Message Format for Delivery Status NotificationsUpdated
January 2003
- RFC 3555MIME Type Registration of RTP Payload FormatsObsoleted
July 2003
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?