RFC 2424: Content Duration MIME Header Definition
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3803.
Current version: RFC 3803 — Content Duration MIME Header Definition
In plain English — editorial summary, not part of the RFC
This document describes the MIME header Content-Duration that is intended for use with any timed media content (typically audio/* or video/*). [STANDARDS-TRACK]
Document record
- Document ID
- RFC2424
- Published
- September 1998
- Authors
- G. Vaudreuil; G. Parsons
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 4
- Also known as
- —
- Obsoleted by:
- RFC 3803
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 2503MIME Types for Use with the ISO ILL ProtocolCurrent
February 1999
- RFC 1820Multimedia E-mail (MIME) User Agent ChecklistObsoleted
August 1995
- RFC 1844Multimedia E-mail (MIME) User Agent ChecklistCurrent
August 1995
- RFC 2422Toll Quality Voice - 32 kbit/s ADPCM MIME Sub-type RegistrationObsoleted
September 1998
- RFC 2442The Batch SMTP Media TypeCurrent
November 1998
- RFC 2312S/MIME Version 2 Certificate HandlingCurrent
March 1998
- RFC 2311S/MIME Version 2 Message SpecificationCurrent
March 1998
- RFC 2278IANA Charset Registration ProceduresObsoleted
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?