idnits 2.17.1 draft-nilsson-audio-mpeg-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == There are 2 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 77: '...s, so audio/mpeg data MAY include MPEG...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The "Author's Address" (or "Authors' Addresses") section title is misspelled. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (26 October 2000) is 8576 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'ID3V2' is mentioned on line 51, but not defined == Unused Reference: 'ID3v2' is defined on line 121, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'ID3v2' -- Possible downref: Non-RFC (?) normative reference: ref. 'MPEG-1' -- Possible downref: Non-RFC (?) normative reference: ref. 'MPEG-2' Summary: 7 errors (**), 0 flaws (~~), 6 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force M. Nilsson 2 Document: draft-nilsson-audio-mpeg-02.txt 3 Expires 26 October 2000 5 The audio/mpeg Media Type 7 Status of this Memo 9 This document is an Internet-Draft and is in full conformance with 10 all provisions of Section 10 of RFC2026. 12 Internet-Drafts are working documents of the Internet Engineering 13 Task Force (IETF), its areas, and its working groups. Note that 14 other groups may also distribute working documents as Internet- 15 Drafts. 17 Internet-Drafts are draft documents valid for a maximum of six months 18 and may be updated, replaced, or obsoleted by other documents at any 19 time. It is inappropriate to use Internet-Drafts as reference 20 material or to cite them other than as ``work in progress.'' 22 The list of current Internet-Drafts can be accessed at 23 http://www.ietf.org/ietf/1id-abstracts.txt 25 The list of Internet-Draft Shadow Directories can be accessed at 26 http://www.ietf.org/shadow.html. 28 Abstract 30 The audio layers of the MPEG-1 and MPEG-2 standards are in frequent 31 use on the internet, but there is no uniform MIME type for these 32 files. The intention of this draft is to define the media type 33 audio/mpeg to refer to this kind of contents. 35 1. MPEG audio 37 The audio compression defined as layer I, layer II and layer III in 38 the MPEG-1 [MPEG-1] and MPEG-2 [MPEG-2] standards is a popular method 39 of compressing audio with a low quality loss. The compressed audio is 40 split into several small data frames, each containing a frame header 41 and compressed audio data. 43 The mime type audio/mpeg defines a elementary byte stream containing 44 MPEG frames according to [MPEG-1] and [MPEG-2], possibly interspersed 45 with non MPEG data. Non MPEG data is data without MPEG 46 synchronisation or in other ways not possible to decompress without 47 error. 49 Typically MPEG audio meta data is concatenated with the MPEG stream, 50 e.g. the meta data format ID3 puts a 128 byte data block in the end 51 of the stream while ID3v2 [ID3V2] prepends a data block of variable 52 size to the stream. 54 NOTE: MPEG audio was not designed as a file format but as a format 55 for transmitting audio streams. As such, it does not have any 56 well defined way of including meta data along with audio information. 57 Some products embed meta data using zero amplitude frames or 58 disguised as transmission errors. Others embed the MPEG data in WAV 59 format. 61 2. Registration Information 63 To: ietf-types@iana.org 64 Subject: Registration of MIME media type audio/mpeg 66 MIME media type name: audio 68 MIME subtype name: mpeg 70 Required parameters: none 72 Optional parameters: none 74 Encoding considerations: 76 For use over internet it is assumed that lower layers take care 77 of transmission errors, so audio/mpeg data MAY include MPEG 78 frames generated without the optional cyclic redundancy checks 79 (CRC) for improved audio quality. 81 The MPEG audio data is binary data, and must be encoded for 82 non-binary transport; the Base64 encoding is suitable for Email. 83 Note that the MPEG audio data does not compress easily using 84 lossless compression. 86 Security considerations: 88 Data concatenated with the MPEG stream might contain executable 89 code. This executable code can only be executed by a program that 90 looks for it and is not executed by an MPEG audio decoder when it 91 attempts to play the file. It's simply ignored. 93 Interoperability considerations: 95 MPEG audio has proven to be widely interoperable across computer 96 platforms. 98 Published specification: see [MPEG-1] and [MPEG-2] 99 Applications which use this media type: 101 MPEG audio is device-, platform- and vendor-neutral and is 102 supported by a wide range of encoders and decoders (players). 104 Additional information: 106 Magic number(s): none 107 File extension(s): .mp1, .mp2, .mp3 108 Macintosh File Type Code(s): MPEG 109 Object Identifier(s) or OID(s): none 111 Person & email address to contact for further information: 113 The author of this draft. 115 Intended usage: COMMON 117 Author/Change controller: Martin Nilsson (see section 5) 119 3. References 121 [ID3v2] 122 Martin Nilsson, "ID3v2 informal standard". 123 125 [MPEG-1] 126 ISO/IEC 11172-3:1993. 127 Coding of moving pictures and associated audio for digital storage 128 media at up to about 1,5 Mbit/s, Part 3: Audio. 129 Technical committee / subcommittee: JTC 1 / SC 29 131 [MPEG-2] 132 ISO/IEC 13818-3:1995 133 Generic coding of moving pictures and associated audio information, 134 Part 3: Audio. 135 Technical committee / subcommittee: JTC 1 / SC 29 137 and 139 ISO/IEC DIS 13818-3 140 Generic coding of moving pictures and associated audio information, 141 Part 3: Audio (Revision of ISO/IEC 13818-3:1995) 143 4. Full Copyright Statement 145 Copyright (C) The Internet Society (2000). All Rights Reserved. 147 This document and translations of it may be copied and furnished to 148 others, and derivative works that comment on or otherwise explain it 149 or assist in its implmentation may be prepared, copied, published and 150 distributed, in whole or in part, without restriction of any kind, 151 provided that the above copyright notice and this paragraph are 152 included on all such copies and derivative works. However, this 153 document itself may not be modified in any way, such as by removing 154 the copyright notice or references to the Internet Society or other 155 Internet organizations, except as needed for the purpose of 156 developing Internet standards in which case the procedures for 157 copyrights defined in the Internet Standards process must be 158 followed, or as required to translate it into languages other than 159 English. 161 The limited permissions granted above are perpetual and will not be 162 revoked by the Internet Society or its successors or assigns. 164 This document and the information contained herein is provided on an 165 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 166 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 167 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 168 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 169 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." 171 5. Authors Address 173 Martin Nilsson 174 Rydsv�gen 246 C. 30 175 S-584 34 Link�ping 176 Sweden 178 Email: nilsson@id3.org