The working group maintains a list of all bug reports that the editors have not yet tried to address; there may also be related open bugs in the GitHub repository of the [[[MEDIA-SOURCE]]] specification.
This specification defines segment formats for implementations of [[[MEDIA-SOURCE]]] [[MEDIA-SOURCE]] that choose to support MPEG audio streams specified in [[ISO11172-3]], [[ISO13818-3]], and [[ISO14496-3]].
It defines the MIME-types (see [[[#mime-types]]]) used to signal codecs, and provides the necessary format specific definitions for [=initialization segments=], [=media segments=], and [=random access points=] required by the Byte Stream Formats section of the [[[MEDIA-SOURCE]]] specification. This document also defines extra behaviors and state that only apply to this byte stream format.
This section specifies the MIME-types that may be passed to {{MediaSource/isTypeSupported()}} or {{MediaSource/addSourceBuffer()}} for byte streams that conform to this specification.
The "codecs" MIME-type parameter MUST NOT be used with these MIME-types.
The format of an MPEG Audio Frame depends on the MIME type used (see [[[#mime-types]]]).
Since [[ID3v1]], [[ID3v2]] metadata frames, and Icecast headers are common in existing MPEG audio streams, implementations SHOULD gracefully handle such frames. Zero or more of these metadata frames are allowed to occur before, after, or between MPEG Audio Frame. Minimal implementations MUST accept, consume, and ignore these frames. More advanced implementations MAY choose to expose the metadata information via an inband {{TextTrack}} or some other mechanism.
There is no normative spec for Icecast/SHOUTcast headers, just examples. For the purpose of this specification, an Icecast header is defined as beginning with the 4 character sequence "ICY "(U+0049 I, U+0043 C, U+0059 Y, U+0020 SPACE) and ending with a pair of carriage-return line-feed sequences (U+000D CARRIAGE RETURN, U+000A LINE FEED, U+000D CARRIAGE RETURN, U+000A LINE FEED).
Icecast headers are allowed in the byte streams because some Icecast and SHOUTcast servers return a status line that looks like "ICY OK 200" instead of a standard HTTP status line. User-agent network stacks typically interpret this as an HTTP 0.9 response and include the header in the response body. Allowing these headers to appear provides a simple way to interoperate with these servers.
The MPEG audio byte stream is a combination of one or more MPEG Audio Frame and zero or more [=metadata frames=].