tools.ietf.org/html/rfc4281

Preview meta tags from the tools.ietf.org website.

Linked Hostnames

7

Thumbnail

Search Engine Appearance

Google

https://tools.ietf.org/html/rfc4281

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

The Codecs Parameter for "Bucket" Media Types (RFC 4281, ; obsoleted by RFC 6381)



Bing

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

https://tools.ietf.org/html/rfc4281

The Codecs Parameter for "Bucket" Media Types (RFC 4281, ; obsoleted by RFC 6381)



DuckDuckGo

https://tools.ietf.org/html/rfc4281

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

The Codecs Parameter for "Bucket" Media Types (RFC 4281, ; obsoleted by RFC 6381)

  • General Meta Tags

    11
    • title
      RFC 4281 - The Codecs Parameter for "Bucket" Media Types
    • charset
      utf-8
    • X-UA-Compatible
      IE=edge
    • viewport
      width=device-width, initial-scale=1
    • description
      The Codecs Parameter for "Bucket" Media Types (RFC 4281, ; obsoleted by RFC 6381)
  • Open Graph Meta Tags

    10
    • og:title
      RFC 4281: The Codecs Parameter for "Bucket" Media Types
    • og:url
      https://datatracker.ietf.org/doc/html/rfc4281
    • og:site_name
      IETF Datatracker
    • og:description
      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]
    • og:type
      article
  • Twitter Meta Tags

    1
    • twitter:card
      summary_large_image
  • Link Tags

    12
    • alternate
      /feed/document-changes/rfc4281/
    • apple-touch-icon
      https://static.ietf.org/dt/12.45.0/ietf/images/ietf-logo-nor-180.png
    • canonical
      https://datatracker.ietf.org/doc/html/rfc4281
    • icon
      https://static.ietf.org/dt/12.45.0/ietf/images/ietf-logo-nor-32.png
    • icon
      https://static.ietf.org/dt/12.45.0/ietf/images/ietf-logo-nor-16.png

Emails

4
  • Per.Frojdh%40ericsson.com
  • singer%40apple.com
  • rg%2Bietf%40coretechnologyconsulting.com
  • [email protected]?subject=rfc4281

Links

30