
tools.ietf.org/html/rfc4281
Preview meta tags from the tools.ietf.org website.
Linked Hostnames
7- 19 links totools.ietf.org
- 6 links towww.rfc-editor.org
- 1 link togithub.com
- 1 link towww.3gpp.org
- 1 link towww.3gpp2.org
- 1 link towww.ietf.org
- 1 link towww.mp4ra.org
Thumbnail

Search Engine Appearance
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

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- titleRFC 4281 - The Codecs Parameter for "Bucket" Media Types
- charsetutf-8
- X-UA-CompatibleIE=edge
- viewportwidth=device-width, initial-scale=1
- descriptionThe Codecs Parameter for "Bucket" Media Types (RFC 4281, ; obsoleted by RFC 6381)
Open Graph Meta Tags
10- og:titleRFC 4281: The Codecs Parameter for "Bucket" Media Types
- og:urlhttps://datatracker.ietf.org/doc/html/rfc4281
- og:site_nameIETF Datatracker
- og:descriptionSeveral 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:typearticle
Twitter Meta Tags
1- twitter:cardsummary_large_image
Link Tags
12- alternate/feed/document-changes/rfc4281/
- apple-touch-iconhttps://static.ietf.org/dt/12.45.0/ietf/images/ietf-logo-nor-180.png
- canonicalhttps://datatracker.ietf.org/doc/html/rfc4281
- iconhttps://static.ietf.org/dt/12.45.0/ietf/images/ietf-logo-nor-32.png
- iconhttps://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- http://www.3gpp.org/ftp/Specs/html-info/26244.htm
- http://www.3gpp2.org/Public_html/specs/C.S0050-0_v1.0_121503.pdf
- http://www.ietf.org/ipr
- http://www.mp4ra.org
- https://github.com/ietf-tools/datatracker/issues/new/choose