Lines Matching +full:video +full:- +full:codecs
43 10.2. video/ogg . . . . . . . . . . . . . . . . . . . . . . . . . 8
79 video, [Speex] (narrow-band and wide-band) speech, [Vorbis] or [FLAC]
81 data, it is possible to include any other type of video, audio,
82 image, text, or, generally speaking, any time-continuously sampled
86 transport mechanisms that provide their own framing and packet-
91 HTTP, included in multi-part documents, or used in other places where
98 o The types "video/ogg" and "audio/ogg" are defined.
104 o The codecs parameter is defined for optional use.
133 are considered non-compliant. Implementations that satisfy all
143 Use of the "application" top-level type for this kind of content is
144 known to be problematic, in particular since it obfuscates video and
147 o video/ogg
152 with video or audio content, respectively. This document also
155 time-continuously sampled data), which is not clearly video or audio
156 data and thus not suited for either the video/ogg or audio/ogg types.
161 time-continuous binary data [RFC3533]. The content types of the
175 the application/ogg type and RECOMMENDED for video/ogg and audio/ogg,
184 These media types can optionally use the "codecs" parameter described
185 in [RFC4281]. Codecs encapsulated in Ogg require a text identifier
186 at the beginning of the first header page, hence a machine-readable
187 method to identify the encapsulated codecs would be through this
189 into strings that are used in the "codecs" parameter when dealing
192 Codec Identifier | Codecs Parameter
193 -----------------------------------------------------------
209 An up-to-date version of this table is kept at Xiph.org (see
210 [Codecs]).
214 o application/ogg; codecs="theora, cmml, ecmascript"
216 o video/ogg; codecs="theora, vorbis"
218 o audio/ogg; codecs=speex
242 net possible of content with the video/ogg and audio/ogg types being
243 smaller subsets of it. However, the video/ogg and audio/ogg types
247 is an even smaller subset within video/ogg, as it is not intended to
256 under application/ogg, the video/ogg type is recommended. In
268 in a suitable encoding without CR/LF conversion, 7-bit stripping,
269 etc.; base64 [RFC4648] is generally preferred for binary-to-text
274 pipes); separate types are used to identify codecs such as in
275 real-time applications for the RTP payload formats of Theora
276 [ThRTP] video, Vorbis [RFC5215], or Speex [SpRTP] audio, as well
293 content (such as audio, video, and displayable text data) with a very
306 content without prior validation of its origin by the end-user.
315 to call for an excessively large picture size, high sampling-rate
345 The Ogg container format is device-, platform-, and vendor-neutral
349 revised (3-clause) BSD license, which is a Free Software license.
375 Optional parameters: codecs, whose syntax is defined in RFC 4281.
409 Vorbis-encoded audio.
420 video/ogg or audio/ogg types. Data served under the application/ogg
429 10.2. video/ogg
431 Type name: video
437 Optional parameters: codecs, whose syntax is defined in RFC 4281.
474 Restrictions on usage: The type "video/ogg" SHOULD be used for Ogg
478 ogg"; for example, a combination of Theora video, Vorbis audio,
480 "video/ogg" SHOULD contain an Ogg Skeleton logical bitstream.
481 Implementations interacting with the type "video/ogg" SHOULD support
496 Optional parameters: codecs, whose syntax is defined in RFC 4281.
550 Westerlund, Alfred Hoenes, and Peter Saint-Andre.
581 [RFC4281] Gellens, R., Singer, D., and P. Frojdh, "The Codecs
595 [Codecs] Pfeiffer, S. and I. Goncalves, "Specification of MIME
596 types and respective codecs parameter", July 2008,
610 bitstream framing, Ogg multi-stream multiplexing",
638 <http://speex.org/docs/manual/speex-manual>.
648 Video", Work in Progress, June 2006.
766 specification can be obtained from the IETF on-line IPR repository at
773 ietf-[email protected].