I-D Action: draft-gellens-mime-bucket-bis-07.txt

internet-drafts@ietf.org Thu, 28 July 2011 20:41 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: i-d-announce@ietfa.amsl.com
Delivered-To: i-d-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 999535E8034 for <i-d-announce@ietfa.amsl.com>; Thu, 28 Jul 2011 13:41:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level:
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OKxA8KzyD9vq for <i-d-announce@ietfa.amsl.com>; Thu, 28 Jul 2011 13:41:13 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3A425E800E for <i-d-announce@ietf.org>; Thu, 28 Jul 2011 13:41:11 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-gellens-mime-bucket-bis-07.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.57
Message-ID: <20110728204111.2499.46292.idtracker@ietfa.amsl.com>
Date: Thu, 28 Jul 2011 13:41:11 -0700
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: internet-drafts@ietf.org
List-Id: Internet Draft Announcements only <i-d-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/i-d-announce>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 20:41:13 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : The Codecs and Profiles Parameters for &quot;Bucket&quot; Media Types
	Author(s)       : Randall Gellens
                          David Singer
                          Per Frojdh
	Filename        : draft-gellens-mime-bucket-bis-07.txt
	Pages           : 25
	Date            : 2011-07-28

   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 is helpful to know from the Content-
   Type alone if the content can be rendered.

   This document specifies two parameters, &quot;codecs&quot; and &quot;profiles&quot;,
   which are used with various MIME types or type/subtype combinations
   to allow for unambiguous specification of the codecs and/or profiles
   employed by the media formats contained within.  This document
   obsoletes RFC 4281; RFC 4281 defines the &quot;codecs&quot; parameter, which
   this document retains in a backwards compatible manner with minor
   clarifications; the &quot;profiles&quot; parameter is added by this document.

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

   Similarly, the profiles can provide an overall indication, to the
   receiver, of the specifications with which the content complies.
   This is an indication of the compatibility of the container format
   and its contents to some specification.  The receiver may be able to
   work out the extent to which it can handle and render the content by
   examining to see which of the declared profiles it supports, and what
   they mean.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-gellens-mime-bucket-bis-07.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-gellens-mime-bucket-bis-07.txt