As per Relevance of the word copyright, we have this rfc below:
Network Working Group J.
Request for Comments: 2586 H.
Category: Informational
May 1999
The Audio/L16 MIME content
Status of this
This memo provides information for the Internet community. It
not specify an Internet standard of any kind. Distribution of
memo is unlimited
Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
1.
This document defines the audio/L16 MIME type, a reasonable
audio format for use in Internet applications
Possible application areas include E-mail, Web served content,
upload in Web forms, and more
2. The need for the Audio/L16 MIME
The set of IETF standard MIME types for audio is small; it
of only the audio/basic and audio/32kadpcm types, which have
sampling rate of 8000 samples/second
Rates below 11025 may obscure consonant information, even
single-voice speech. Common compressions, such as LPC, are known
be microphone-dependant and lossy. Thus far all IETF MIME
types either default to 8000 samples per second or use LPC
In order for advanced speech recognition and related
applications to make use of internet transports (such as RFC 1867
file uploading) which use MIME typing, higher standards are required
This type repairs that lack by registering a very simple MIME
that allows higher rate, linear-encoded audio with multiple channels
This is an IESG approved MIME type, and its definition is
published as an RFC
Salsman Informational [Page 1]
RFC 2586 The Audio/L16 MIME content type May 1999
Please note that there are many other Audio types described in
1890 [1] which IANA may wish to formally register; this one, of
of them, seems to be most immediately needed. This document may
serve as a template for further registrations of these audio types
3. The definition of Audio/L16
Audio/L16 is based on the well know audio format "L16" described
RFC 1890 section 4.4.8 for use with RTP transport. L16
uncompressed audio data, using 16-bit signed representation in twos
complement notation and network byte order. (From section 4.4.8
RFC 1890)
It may be parametrized by varying the sample rate and the number
channels; the parameters are given on the MIME type header
In order to promote interoperability, only a few rate values
standardized here. Other values may NOT be used except by
agreement
If multiple audio channels are used, channels are numbered left-to
right, starting at one. Samples are put into the data stream
each channel in succession; information from lower-numbered
precedes that from higher-numbered channels
For more than two channels, the convention followed by the AIFF-
audio interchange format should be followed [1], using the
notation
l
r
c
S
F
R
channels description
1 2 3 4 5 6
___________________________________________________________
2 stereo l
3 l r
4 quadrophonic Fl Fr Rl
4 l c r
5 Fl Fr Fc Sl
6 l lc c r rc
(From RFC 1890 section 4.1)
Salsman Informational [Page 2]
RFC 2586 The Audio/L16 MIME content type May 1999
4. IANA registration form for Audio/L16
MIME media type name :
MIME subtype name : L16
Required
rate: number of samples per second -- Permissible values
rate are 8000, 11025, 16000, 22050, 24000, 32000, 44100,
48000 samples per second
Optional
channels: how many audio streams are interleaved --
to 1; stereo would be 2, etc. Interleaving takes
between individual two-byte samples
Encoding
Audio data is binary data, and must be encoded for non-
transport; the Base64 encoding is suitable for Email.
that audio data does not compress easily using
compression
Security
Audio data is believed to offer no security risks
Interoperability
This type is compatible with the encoding used in the
(Microsoft Windows RIFF) and Apple AIFF union types, and
the public domain "sox" and "rateconv" programs
Published
RFC 2586
Applications which use this
The public domain "sox" and "rateconv" programs accept
type
1. Magic number(s) :
2. File extension(s) : WAV L16
3. Macintosh file type code :
Person to contact for further
1. Name : James
2. E-mail : jps-L16@bovik.
Intended
Salsman Informational [Page 3]
RFC 2586 The Audio/L16 MIME content type May 1999
It is expected that many audio and speech applications will
this type. Already the most popular platforms provide this
with the rate=11025 parameter referred to as "radio
speech."
Author/Change
James
5. Security
The audio data is believed to offer no security risks
Note that RFC 1890 permits an application to choose to play a
channel from a multichannel tranmission; an attacker who knows
two different users will pick different channels could
construct some confusing messages; this, however, is ridiculous
This type is perfect for hiding data using steganography
6.
[1] Schulzrinne, H., "RTP Profile for Audio and Video
with Minimal Control", RFC 1890, January 1996.
7. Authors'
James
575 S. Rengstorff
Mountain View, CA 94040-1982
EMail: James@bovik.
Harald Tveit
N-7034
Phone: +47 73 59 70 94
EMail: Harald.T.Alvestrand@uninett.
Salsman Informational [Page 4]
RFC 2586 The Audio/L16 MIME content type May 1999
8. Full Copyright
Copyright (C) The Internet Society (1999). 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
Salsman Informational [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
