metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 4281: The Codecs Parameter for "Bucket" Media Types

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6381.

Current version: RFC 6381 — The 'Codecs' and 'Profiles' Parameters for "Bucket" Media Types

In plain English — editorial summary, not part of the RFC

Several MIME type/subtype combinations exist that can contain different media formats. A receiving agent thus needs to examine the details of such media content to determine if the specific elements can be rendered given an available set of codecs. Especially when the end system has limited resources, or the connection to the end system has limited bandwidth, it would be helpful to know from the Content-Type alone if the content can be rendered. This document adds a new parameter, "codecs", to various type/subtype combinations to allow for unambiguous specification of the codecs indicated by the media formats contained within. By labeling content with the specific codecs indicated to render the contained media, receiving systems can determine if the codecs are supported by the end system, and if not, can take appropriate action (such as rejecting the content, sending notification of the situation, transcoding the content to a supported type, fetching and installing the required codecs, further inspection to determine if it will be sufficient to support a subset of the indicated codecs, etc.) [STANDARDS-TRACK]

Document record

Document ID
RFC4281
Published
December 2005
Authors
R. Gellens; D. Singer; P. Frojdh
Status
PROPOSED STANDARD
Stream
IETF
Area
—
Pages
29
Also known as
—
Obsoleted by:
RFC 6381

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.

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?

canonical URL: /rfc/4281-the-codecs-parameter-for-bucket-media-types