idnits 2.17.1 draft-kosonen-mobile-xmf-mediatype-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5 on line 298. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 271. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 278. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 284. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == 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 separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([7], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. -- The draft header indicates that this document obsoletes draft-kosonen-mobile-xmf-mediatype-00.txt, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 (2 May 2006) is 6540 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 section? '1' on line 40 looks like a reference -- Missing reference section? '7' on line 41 looks like a reference -- Missing reference section? '8' on line 49 looks like a reference -- Missing reference section? '3' on line 51 looks like a reference -- Missing reference section? '4' on line 51 looks like a reference -- Missing reference section? '2' on line 51 looks like a reference -- Missing reference section? '5' on line 149 looks like a reference -- Missing reference section? '6' on line 149 looks like a reference Summary: 5 errors (**), 0 flaws (~~), 2 warnings (==), 16 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet-Draft T. Kosonen 3 draft-kosonen-mobile-xmf-mediatype-01.txt Nokia 4 Obsoletes: draft-kosonen-mobile-xmf-mediatype-00.txt T. White 5 Expires: 3 November 2006 MMA 6 2 May 2006 8 Registration of media type audio/mobile-xmf 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/1id-abstracts.html 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html 33 This document is an individual submission to the IETF. Comments 34 should be directed to the authors. 36 Abstract 38 The MIDI Manufacturers Association (MMA) and the Association of Music 39 Electronics industry (AMEI) have produced the Mobile XMF standard 40 [1]. The Mobile XMF standard has been developed particularly for 41 mobile MIDI [7] applications. Mobile XMF is a very compact media 42 type providing high quality synthetic audio content for music 43 downloading and messaging applications that require MIME 44 registration. 46 1. Introduction 48 MIDI content is used commonly in the Internet. Commonly, MIDI data 49 is stored in the Standard MIDI File (SMF) format [8]. This MIME type 50 registration uses the Mobile XMF file format for the encapsulation of 51 SP-MIDI [3,4] and Mobile DLS [2] data. 53 2. Registration of audio/mobile-xmf 55 Type name: audio 57 Subtype name: mobile-xmf 59 Required parameters: none 61 Optional parameters: 63 revision: Mobile XMF file type revision ID 65 revision is the Mobile XMF file type revision ID number from 66 the XmfFileTypeRevisionID field of the XMF Meta File format 67 2.00. revision is encoded in hex in US-ASCII. 69 prl: Playback resource list 71 prl is a string (inside double quotation marks "") containing 72 the playback resources included in all Content Description 73 MetaDataItems of the Mobile XMF file. The string contains two 74 digit hexadecimal numbers representing data bytes from the 75 Content Description Meta Data. The same resource is listed 76 only once. A playback resource contains two parts: a prefix 77 and data. prl is encoded in two-digit hex numbers concatenated 78 in a US-ASCII string. 80 Example: If the file includes Playback Resource Lists such as 81 [00h 01h 00h 02h] and [00h 01h 00h 03h], the corresponding prl 82 is "000100020003" containing playback resources 01, 02, and 03 83 with the prefix 00. 85 minimum-pr: Minimum playback requirements 87 minimum-pr is a string containing the Maximum Instantaneous 88 Resource (MIR) values from the first row of all MIR Count 89 Tables corresponding to the playback resources listed in prl. 90 Only the largest value from the values of the same resource is 91 chosen. minimum-prl is encoded in two-digit hex numbers 92 concatenated in a US-ASCII string. 94 minimum-pr requires the use of prl and the values in minimum-pr 95 must be in the same order as the resources in prl. minimum-pr 96 is the most important of minimum-pr and total-pr, because it 97 defines the minimum playback requirements. 99 Example: If the file includes first rows of MIR Count Tables 100 such as [02h 00h] and [01h 01h] corresponding to the above 101 Playback Resource Lists, the corresponding minimum-pr is 102 "020001". (02 is the largest of 2 and 1, 00 is the largest of 103 0, and 01 is the largest of 1.) 105 total-pr: Total playback requirements 107 total-pr is a string containing the MIR values from the last 108 row of all MIR Count Tables corresponding to the playback 109 resources listed in prl. Only the largest value from the 110 values of the same resource is chosen. total-pr is encoded in 111 two-digit hex numbers concatenated in a US-ASCII string. 113 total-pr requires the use of prl and the values in total-pr 114 must be in the same order as the resources in prl. 116 Example: If the file includes last rows of MIR Count Tables 117 such as [05h 02h] and [06h 01h] corresponding to the above 118 Playback Resource Lists, the corresponding total-pr is 119 "060201". (06 is the largest of 5 and 6, 02 is the largest of 120 2, and 01 is the largest of 1.) 122 Encoding considerations: 124 mobile-xmf data is binary data and must be encoded for non-binary 125 transport; Base64 is suitable for Email. 127 Security considerations: 129 Many synthetic audio compositions have associated intellectual 130 property rights. It is conceivable that the rights owners of 131 mobile-xmf content will want to protect their rights by applying 132 security mechanisms that prohibit the rendering of the content 133 without a legally acquired license to do so. These mechanisms 134 would be applied externally to the Content-Type defined here; 135 mobile-xmf content itself is not encrypted internally. mobile-xmf 136 streams do not contain executable content. Mobile XMF players are 137 robust against corrupted mobile-xmf content, because Mobile XMF 138 players ignore unidentified content. prl, minimum-pr, and total- 139 pr parameters can be used to represent Mobile DLS playback memory 140 requirements for protecting against the excessive usage of 141 playback memory. 143 Interoperability considerations: 145 Mobile XMF is a Musical Instrument Digital Interface (MIDI) 146 specification developed by MMA and AMEI. mobile-xmf is based on 147 the XMF 2.00 specification [5,6], which standardizes a meta file 148 format for the electronic distribution of music. mobile-xmf data 149 is stored in XMF file format [5,6]. 151 Published specification: 153 Mobile XMF Content Format Specification, MMA specification 154 v1.0., RP-42, Los Angeles, CA, USA. 2004. 156 Specification is available from: 157 http://www.midi.org/about-midi/specshome.shtml 159 Applications which use this media type: 161 mobile-xmf is a synthetic audio format for the flexible 162 presentation of SP-MIDI and Mobile DLS instrument data on a wide 163 range of playback devices, particularly portable appliances such 164 as mobile phones, PDAs, and palmtop computers. 166 Additional information: 168 Magic number(s): 170 First twelve bytes: 171 \130\115\106\137\062\056\060\060\000\000\000\002 173 File extension(s): mxmf 175 Macintosh File Type Code(s): mxmf 177 Person & email address to contact for further information: 179 Timo Kosonen 180 Email: timo.kosonen@nokia.com 182 Intended usage: COMMON 184 Restrictions on usage: none 185 Authors: 187 Timo Kosonen 188 Email: timo.Kosonen@nokia.com 190 Tom White 191 Email: twhite@midi.org 193 Change controller: 195 MIDI Manufacturers Association 196 P.O. Box 3173 197 La Habra CA 198 90632-3173 199 Tel (714) 736-9774 200 Fax (714) 736-9775 201 Point of contact: 202 Tom White 203 Email: twhite@midi.org 205 3. Security Considerations 207 Security considerations are specified in the MIME subtype 208 registration contained in Section 2. 210 4. IANA Considerations 212 Section 2 of this document registers one MIME subtype. 214 5. Authors' Addresses 216 Timo Kosonen 217 Nokia 218 P.O. Box 100 219 33721 Tampere 220 Finland 221 Tel: +358 5048 35206 222 Fax: +358 7180 35899 224 Email: timo.kosonen@nokia.com 226 Tom White 227 MIDI Manufacturers Association 228 P.O. Box 3173 229 La Habra CA 230 90632-3173 231 Tel (714) 736-9774 232 Fax (714) 736-9775 234 Email: twhite@midi.org 235 6. References 237 6.1 Normative references: 239 1 Mobile XMF Content Format Specification, MMA specification 240 v1.0., RP-42, Los Angeles, CA, USA. 2004. 241 2 Mobile DLS, MMA specification v1.0., RP-41, Los Angeles, CA, 242 USA. 2004. 243 3 Scalable Polyphony MIDI Specification. December 2001, RP-034, 244 The MIDI Manufacturers Association, Los Angeles, CA, USA. 245 4 Scalable Polyphony MIDI Device 5-24 Note Profile for 3GPP, 246 December 2001, RP-035, The MIDI Manufacturers Association, Los 247 Angeles, CA, USA. 248 5 Specification for XMF Meta File Format, Version 1.00b. The MIDI 249 Manufacturers Association, Los Angeles, CA, USA, 2001. 250 6 XMF Meta File Format 2.00, RP-043, MIDI Manufacturers 251 Association, Los Angeles, CA, USA, 2004 252 7 MIDI 1.0 Detailed Specification, Document Version 4.2. February 253 1996, In 'The Complete MIDI 1.0 Detailed Specification, Document 254 Version 96.1.' The MIDI Manufacturers Association., Los 255 Angeles, CA, USA. 256 8 Standard MIDI Files 1.0, In 'The Complete MIDI 1.0 Detailed 257 Specification, Document Version 96.1.' The MIDI Manufacturers 258 Association., Los Angeles, CA, USA. 259 9 Josefsson, S., Ed., "The Base16, Base32, and Base64 Data 260 Encodings", RFC 3548, July 2003. 262 7. IPR Disclosure Acknowledgement 264 The IETF takes no position regarding the validity or scope of any 265 Intellectual Property Rights or other rights that might be claimed to 266 pertain to the implementation or use of the technology described in 267 this document or the extent to which any license under such rights 268 might or might not be available; nor does it represent that it has 269 made any independent effort to identify any such rights. Information 270 on the procedures with respect to rights in RFC documents can be 271 found in BCP 78 and BCP 79. 273 Copies of IPR disclosures made to the IETF Secretariat and any 274 assurances of licenses to be made available, or the result of an 275 attempt made to obtain a general license or permission for the use of 276 such proprietary rights by implementers or users of this 277 specification can be obtained from the IETF on-line IPR repository at 278 http://www.ietf.org/ipr. 280 The IETF invites any interested party to bring to its attention any 281 copyrights, patents or patent applications, or other proprietary 282 rights that may cover technology that may be required to implement 283 this standard. Please address the information to the IETF at ietf- 284 ipr@ietf.org. 286 8. Copyright notice 288 Copyright (C) The Internet Society (2006). This document is subject 289 to the rights, licenses and restrictions contained in BCP 78, and 290 except as set forth therein, the authors retain all their rights. 292 This document and the information contained herein are provided on an 293 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 294 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 295 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 296 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 297 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 298 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.