idnits 2.17.1 draft-nilsson-audio-mpeg-03.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: ---------------------------------------------------------------------------- ** 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 == The page length should not exceed 58 lines per page, but there was 2 longer pages, the longest (page 2) being 61 lines 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 abstract seems to contain references ([RFC2119]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. 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. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: MPEG is a tagged data format, and some tags are available for private use. As such, arbitrary material could potentially be transferred in the MPEG stream, including executable content. Tagged data containing executable content SHOULD never be sent and MUST not be executed if it is received. -- 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 (27 February 2001) is 8456 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 58, but not defined == Unused Reference: 'ID3v2' is defined on line 143, 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: 6 errors (**), 0 flaws (~~), 8 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 INTERNET DRAFT 27 August 2000 3 Document: draft-nilsson-audio-mpeg-03.txt 4 Expires 27 February 2001 6 The audio/mpeg Media Type 8 Status of this Memo 10 This document is an Internet-Draft and is in full conformance with 11 all provisions of Section 10 of RFC2026. 13 Internet-Drafts are working documents of the Internet Engineering 14 Task Force (IETF), its areas, and its working groups. Note that 15 other groups may also distribute working documents as Internet- 16 Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet-Drafts as reference 21 material or to cite them other than as ``work in progress.'' 23 The list of current Internet-Drafts can be accessed at 24 http://www.ietf.org/ietf/1id-abstracts.txt 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 Abstract 31 The audio layers of the MPEG-1 and MPEG-2 standards are in frequent 32 use on the internet, but there is no uniform MIME type for these 33 files. The intention of this draft is to define the media type 34 audio/mpeg to refer to this kind of contents. 36 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 37 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 38 document are to be interpreted as described in RFC 2119 [RFC2119]. 40 1. MPEG audio 42 The audio compression defined as layer I, layer II and layer III in 43 the MPEG-1 [MPEG-1] and MPEG-2 [MPEG-2] standards is a popular method 44 of compressing audio with a low quality loss. The compressed audio is 45 split into several small data frames, each containing a frame header 46 and compressed audio data. 48 The mime type audio/mpeg defines a elementary byte stream containing 49 MPEG frames according to [MPEG-1] and [MPEG-2], possibly interspersed 50 with non MPEG data. Non MPEG data is data without MPEG 51 synchronisation or in other ways not possible to decompress without 52 error. 54 Internet DRAFT The audio/mpeg Media Type August 2000 56 Typically MPEG audio meta data is concatenated with the MPEG stream, 57 e.g. the meta data format ID3 puts a 128 byte data block in the end 58 of the stream while ID3v2 [ID3V2] prepends a data block of variable 59 size to the stream. 61 NOTE: MPEG audio was not designed as a file format but as a format 62 for transmitting audio streams. As such, it does not have any 63 well defined way of including meta data along with audio information. 64 Some products embed meta data using zero amplitude frames or 65 disguised as transmission errors. Others embed the MPEG data in WAV 66 format. 68 2. Registration Information 70 To: ietf-types@iana.org 71 Subject: Registration of MIME media type audio/mpeg 73 MIME media type name: audio 75 MIME subtype name: mpeg 77 Required parameters: none 79 Optional parameters: none 81 Encoding considerations: 83 For use over internet it is assumed that lower layers take care 84 of transmission errors, so audio/mpeg data MAY include MPEG 85 frames generated without the optional cyclic redundancy checks 86 (CRC) for improved audio quality. 88 The MPEG audio data is binary data, and must be encoded for 89 non-binary transport; the Base64 encoding is suitable for Email. 90 Note that the MPEG audio data does not compress easily using 91 lossless compression. 93 Security considerations: 95 MPEG is a tagged data format, and some tags are available for 96 private use. As such, arbitrary material could potentially 97 be transferred in the MPEG stream, including executable content. 98 Tagged data containing executable content SHOULD never be sent 99 and MUST not be executed if it is received. 101 NOTE 103 The requirement that such content not be executed on receipt 104 is especially important since situations exist where content 105 will be generated independently and therefore could contain 106 executable content that the sender is unaware of. 108 Audio/mpeg objects are not signed or encrypted internally. 109 External security mechanisms must be employed to ensure content 110 confidentiality 112 Internet DRAFT The audio/mpeg Media Type August 2000 114 Interoperability considerations: 116 MPEG audio has proven to be widely interoperable across computer 117 platforms. 119 Published specification: see [MPEG-1] and [MPEG-2] 121 Applications which use this media type: 123 MPEG audio is device-, platform- and vendor-neutral and is 124 supported by a wide range of encoders and decoders (players). 126 Additional information: 128 Magic number(s): none 129 File extension(s): .mp1, .mp2, .mp3 130 Macintosh File Type Code(s): MPEG 131 Object Identifier(s) or OID(s): none 133 Person & email address to contact for further information: 135 The author of this draft. 137 Intended usage: COMMON 139 Author/Change controller: Martin Nilsson (see section 5) 141 3. References 143 [ID3v2] 144 Martin Nilsson, "ID3 tag version 2.3.0". 145 147 [MPEG-1] 148 ISO/IEC 11172-3:1993. 149 Coding of moving pictures and associated audio for digital storage 150 media at up to about 1,5 Mbit/s, Part 3: Audio. 151 Technical committee / subcommittee: JTC 1 / SC 29 153 [MPEG-2] 154 ISO/IEC 13818-3:1995 155 Generic coding of moving pictures and associated audio information, 156 Part 3: Audio. 157 Technical committee / subcommittee: JTC 1 / SC 29 159 and 161 ISO/IEC DIS 13818-3 162 Generic coding of moving pictures and associated audio information, 163 Part 3: Audio (Revision of ISO/IEC 13818-3:1995) 165 Internet DRAFT The audio/mpeg Media Type August 2000 167 [RFC2119] 168 S. Bradner, "Key words for use in RFCs to Indicate Requirement 169 Levels", RFC 2119, March 1997. 171 173 4. Full Copyright Statement 175 Copyright (C) The Internet Society (2000). All Rights Reserved. 177 This document and translations of it may be copied and furnished to 178 others, and derivative works that comment on or otherwise explain it 179 or assist in its implmentation may be prepared, copied, published and 180 distributed, in whole or in part, without restriction of any kind, 181 provided that the above copyright notice and this paragraph are 182 included on all such copies and derivative works. However, this 183 document itself may not be modified in any way, such as by removing 184 the copyright notice or references to the Internet Society or other 185 Internet organizations, except as needed for the purpose of 186 developing Internet standards in which case the procedures for 187 copyrights defined in the Internet Standards process must be 188 followed, or as required to translate it into languages other than 189 English. 191 The limited permissions granted above are perpetual and will not be 192 revoked by the Internet Society or its successors or assigns. 194 This document and the information contained herein is provided on an 195 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 196 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 197 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 198 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 199 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." 201 5. Authors Address 203 Martin Nilsson 204 Rydsv�gen 246 C. 30 205 S-584 34 Link�ping 206 Sweden 208 Email: nilsson@id3.org