Browse Prior Art Database

The Codecs Parameter for "Bucket" Media Types (RFC4281)

IP.com Disclosure Number: IPCOM000132085D
Original Publication Date: 2005-Nov-01
Included in the Prior Art Database: 2005-Dec-01
Document File: 13 page(s) / 26K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Gellens: AUTHOR [+3]

Abstract

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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 11% of the total text.

Network Working Group                                         R. Gellens
Request for Comments: 4281                                      Qualcomm
Category: Standards Track                                      D. Singer
                                                                   Apple
                                                               P. Frojdh
                                                                Ericsson
                                                           November 2005


             The Codecs Parameter for "Bucket" Media Types

Status of This Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2005).

Abstract

   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.)

Gellens, et al.             Standards Track                     [Page 1]
RFC 4281                  The Codecs Parameter             November 2005


Table of Contents

   1. Introduction ....................................................2
   2. Conventions Used in This Document ...............................4
   3. The Codecs...