As per Relevance of the word copyright, we have this rfc below:
Network Working Group M.
Request for Comments: 3003 November 2000
Category: Standards
The audio/mpeg Media
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (2000). All Rights Reserved
The audio layers of the MPEG-1 and MPEG-2 standards are in
use on the internet, but there is no uniform Multipurpose
Mail Extension (MIME) type for these files. The intention of
document is to define the media type audio/mpeg to refer to this
of contents
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
document are to be interpreted as described in RFC 2119 [RFC2119].
1. MPEG
The audio compression defined as layer I, layer II and layer III
the MPEG-1 [MPEG-1] and MPEG-2 [MPEG-2] standards is a popular
of compressing audio with a low quality loss. The compressed
is split into several small data frames, each containing a
header and compressed audio data
The mime type audio/mpeg defines a elementary byte stream
MPEG frames according to [MPEG-1] and [MPEG-2], possibly
with non MPEG data. Non MPEG data is data without
synchronization or in other ways not possible to decompress
error
Typically MPEG audio meta data is concatenated with the MPEG stream
e.g., the meta data format ID3 puts a 128 byte data block in the
of the stream while ID3v2 [ID3V2] prepends a data block of
Nilsson Standards Track [Page 1]
RFC 3003 The audio/mpeg Media Type November 2000
size to the stream
NOTE: MPEG audio was not designed as a file format but as a
for transmitting audio streams. As such, it does not have any
defined way of including meta data along with audio information
Some products embed meta data using zero amplitude frames
disguised as transmission errors. Others embed the MPEG data in
format
NOTE: The audio/MPS mime type is in use in addition to
audio/mpeg. The MPA [RFC 1890] sub-type refers to MPEG audio when
is segmented and send as a Realtime Transport Protocol (RTP) payload
2. Registration
To: ietf-types@iana.org Subject: Registration of MIME media
audio/
MIME media type name:
MIME subtype name:
Required parameters:
Optional parameters:
Encoding considerations
For use over internet it is assumed that lower layers take
of transmission errors, so audio/mpeg data MAY include
frames generated without the optional cyclic redundancy
(CRC) for improved audio quality
The MPEG audio data is binary data, and must be encoded
non-binary transport; the Base64 encoding is suitable for Email
Note that the MPEG audio data does not compress easily
lossless compression
Security considerations
MPEG is a tagged data format, and some tags are available
private use. As such, arbitrary material could
be transferred in the MPEG stream, including executable content
Tagged data containing executable content SHOULD never be
and MUST not be executed if it is received
Nilsson Standards Track [Page 2]
RFC 3003 The audio/mpeg Media Type November 2000
The requirement that such content not be executed on
is especially important since situations exist where
will be generated independently and therefore could
executable content that the sender is unaware of
Audio/mpeg objects are not signed or encrypted internally
External security mechanisms must be employed to ensure
Interoperability considerations
MPEG audio has proven to be widely interoperable across
platforms
Published specification: see [MPEG-1] and [MPEG-2]
Applications which use this media type
MPEG audio is device-, platform- and vendor-neutral and
supported by a wide range of encoders and decoders (players).
Additional information
Magic number(s):
File extension(s): .mp1, .mp2, .mp
Macintosh File Type Code(s):
Object Identifier(s) or OID(s):
Person & email address to contact for further information
The author of this document
Intended usage:
Author/Change controller: Martin Nilsson (see section 5)
3. Security
Security considerations are discussed in the security
clause of the MIME registration in section 2.
Nilsson Standards Track [Page 3]
RFC 3003 The audio/mpeg Media Type November 2000
4.
[ID3v2]
Martin Nilsson, "ID3 tag version 2.3.0".
[MPEG-1]
ISO/IEC 11172-3:1993.
Coding of moving pictures and associated audio for digital
media at up to about 1,5 Mbit/s, Part 3: Audio
Technical committee / subcommittee: JTC 1 / SC 29
[MPEG-2]
ISO/IEC 13818-3:1995
Generic coding of moving pictures and associated audio information
Part 3: Audio
Technical committee / subcommittee: JTC 1 / SC 29
ISO/IEC DIS 13818-3
Generic coding of moving pictures and associated audio information
Part 3: Audio (Revision of ISO/IEC 13818-3:1995)
[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate
Levels", BCP 14, RFC 2119, March 1997.
5. Author's
Martin
Rydsvagen 246 C. 30
S-584 34
EMail: nilsson@id3.
Nilsson Standards Track [Page 4]
RFC 3003 The audio/mpeg Media Type November 2000
6. Full Copyright
Copyright (C) The Internet Society (2000). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Funding for the RFC Editor function is currently provided by
Internet Society
Nilsson Standards Track [Page 5]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
