idnits 2.17.1 draft-singer-avt-3gpp-mime-01.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? == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 7 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 8 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 23 instances of too long lines in the document, the longest one being 1 character in excess of 72. == There are 2 instances of lines with non-RFC2606-compliant FQDNs in the document. 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.) -- Couldn't find a document date in the document -- date freshness check skipped. 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: '3GPP' is mentioned on line 52, but not defined == Unused Reference: '3gpp' is defined on line 291, but no explicit reference was found in the text == Unused Reference: 'MIME1' is defined on line 297, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. '3gpp' -- Obsolete informational reference (is this intentional?): RFC 2429 (Obsoleted by RFC 4629) -- Obsolete informational reference (is this intentional?): RFC 3267 (Obsoleted by RFC 4867) Summary: 3 errors (**), 0 flaws (~~), 8 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force 3 INTERNET-DRAFT R. Castagno and D. Singer 4 draft-singer-avt-3gpp-mime-01 Nokia and Apple Computer 6 Sep 3 2003 7 Expires: Mar 3 2004 9 MIME Type Registrations for 3GPP Multimedia files 11 Status of This Memo 13 This document is an Internet-Draft and is in full conformance with 14 all provisions of Section 10 of RFC2026. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that other 18 groups may also distribute working documents as Internet-Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet- Drafts as reference 23 material or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/1id-abstracts.html 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html 31 Distribution of this document is unlimited. 33 Copyright Notice 35 Copyright (C) The Internet Society (2003). All Rights Reserved. 37 Abstract 39 This document serves to register and document the standard MIME types 40 associated with the 3GPP multimedia file format, which is part of the 41 family based on the ISO Media File Format. 43 1 Introduction 45 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 46 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 47 document are to be interpreted as described in RFC 2119 [RFC2119]. 49 The third-generation partnership project (3GPP) for third-generation 50 cellular telephony has defined a standard file format to contain 51 audio/visual sequences which may be downloaded to cellular phones 52 [3GPP]. At the time of writing, the 3GPP file format (3GP) can 53 contain H.263 or MPEG-4 video; and AMR Narrow-band or AMR wide-band 54 speech, or AAC audio; and 3GPP timed text. 56 Within the file, as with all files in the 'ISO' family, there is an 57 intrinsic file-type box, which identifies those specifications to 58 which the file complies, and which players (possibly compliant with 59 only one specification) are permitted by the content author to play 60 the file. This identification is through four-letter 'brands'. 61 Files identified by the MIME type defined here MUST contain a brand 62 defined in a standard issued by 3GPP that can apply to 3GPP files, in 63 their compatible brands list. 65 The MIME types defined here are needed correctly to identify such 66 files when they are served over HTTP, included in multi-part 67 documents, or used in other places where MIME types are used. 69 2 Security Considerations 71 The 3GPP file format may contain audio, video, and displayable text 72 data. There is currently no provision for 'active' elements (such as 73 scripts) of any kind. 75 Clearly it is possible to author malicious files which attempt to 76 call for an excessively large picture size, high sampling-rate audio 77 etc. However, clients can and usually do protect themselves against 78 this kind of attack. 80 It should be noted that selected metadata fields may encompass 81 information partly intended to protect the media against unauthorized 82 use or distribution. In this case the intention is that alteration or 83 removal of the data in the field would be treated as an offence under 84 national agreements based World Intellection Property Organization 85 (WIPO) treaties. 87 3GPP files have an extensible structure, so that it is theoretically 88 possible that metadata fields or media formats could be defined in 89 the future which could be used to induce particular actions on the 90 part of the recipient, thus presenting additional security risks, but 91 this type of capability is currently not supported in the referenced 92 specification. 94 There is no current provision in the standards for encryption, 95 signing, or authentication of these file formats. 97 3 MIME Types 99 This registration applies to all files defined as using the '3GP' 100 file format and identified with a suitable brand in a 3GPP 101 specification. The usual file suffix for all these files is ".3gp". 103 3.1 Files with audio but no video 105 The type "audio/3gpp" may be used for files containing audio but no 106 visual presentation (neither video nor timed text, for example). 108 To: ietf-types@iana.org 109 Subject: Registration of Standard MIME media type audio/3gpp 111 MIME media type name: audio 112 MIME subtype name: 3gpp 113 Required parameters: none 114 Optional parameters: none 115 Encoding considerations: files are binary and should be 116 transmitted in a suitable encoding 117 without CR/LF conversion, 7-bit 118 stripping etc.; base64 is a suitable 119 encoding. Note that this MIME type is 120 used only for files; separate types 121 are used for real-time transfer, such 122 as for the RTP payload format for AMR 123 audio [RFC3267]. 124 Security considerations: see the security considerations 125 section in RFC XXXX 126 Interoperability considerations: The 3GPP organization has defined the 127 specification, interoperability and 128 conformance, and conducts regular 129 interoperability testing. 130 Published specification: 3GPP 26.234, Release 5; 3GPP 26.244, 131 Release 6 or later. 3GPP 132 specifications are publicly 133 accessible at the 3GPP web site, 134 www.3gpp.org. 135 Applications which use this media type: Multi-media 136 Additional information: The type "audio/3gpp" MAY be used for 137 files containing audio but no visual 138 presentation. Files served under 139 this type MUST NOT contain any visual 140 material. (Note that 3GPP timed text 141 is visually presented and is 142 considered to be visual material). 143 Magic number(s): None. However, the file-type box 144 must occur first in the file, and 145 MUST contain a 3GPP brand in its 146 compatible brands list. 147 File extension(s): 3gp and 3gpp are both declared at 148 http://www.nist.gov/nics/; 3gp is 149 preferred 150 Macintosh File Type Code(s): '3gpp' 151 Person & email address to contact for further information: 152 Nokia MIME manager, mime@nokia.com 153 Intended usage: COMMON 154 Change controller: 3GPP 156 3.2 Any files 158 The type "video/3gpp" is valid for all files. It is valid to serve 159 an audio-only file as "video/3gpp". 161 To: ietf-types@iana.org 162 Subject: Registration of Standard MIME media type video/3gpp 164 MIME media type name: video 165 MIME subtype name: 3gpp 166 Required parameters: none 167 Optional parameters: none 168 Encoding considerations: files are binary and should be 169 transmitted in a suitable encoding 170 without CR/LF conversion, 7-bit 171 stripping etc.; base64 is a suitable 172 encoding. Note that this MIME type 173 is used only for files; separate 174 types are used for real-time 175 transfer, such as for the RTP payload 176 formats for H.263 [RFC2429] and AMR 177 audio [RFC3267]. 178 Security considerations: see the security considerations 179 section in RFC XXXX 180 Interoperability considerations: The 3GPP organization has defined the 181 specification, interoperability and 182 conformance, and conducts regular 183 interoperability testing. 184 Published specification: 3GPP 26.234, Release 5; 3GPP 26.244, 185 Release 6 or later. 3GPP 186 specifications are publicly 187 accessible at the 3GPP web site, 188 www.3gpp.org. 189 Applications which use this media type: Multi-media 190 Additional information: 191 Magic number(s): None. However, the file-type box 192 must occur first in the file, and 193 MUST contain a 3GPP brand in its 194 compatible brands list. 195 File extension(s): 3gp and 3gpp are both declared at 196 http://www.nist.gov/nics/; 3gp is 197 preferred 198 Macintosh File Type Code(s): '3gpp' 199 Person & email address to contact for further information: 200 Nokia MIME manager, mime@nokia.com 201 Intended usage: COMMON 202 Change controller: 3GPP 204 4 IANA Considerations 206 This document registers the MIME types audio/3gpp and video/3gpp, 207 defined above. 209 5 RFC Editor Considerations 211 The references to RFC XXXX in the MIME registrations need to be 212 replaced with the actual RFC number when it is issued. 214 6 Full Copyright Statement 216 Copyright (C) The Internet Society (2003). All Rights Reserved. 218 This document and translations of it may be copied and furnished to 219 others, and derivative works that comment on or otherwise explain it 220 or assist in its implementation may be prepared, copied, published 221 and distributed, in whole or in part, without restriction of any 222 kind, provided that the above copyright notice and this paragraph are 223 included on all such copies and derivative works. 225 However, this document itself may not be modified in any way, such as 226 by removing the copyright notice or references to the Internet 227 Society or other Internet organizations, except as needed for the 228 purpose of developing Internet standards in which case the procedures 229 for copyrights defined in the Internet Standards process must be 230 followed, or as required to translate it into languages other than 231 English. 233 The limited permissions granted above are perpetual and will not be 234 revoked by the Internet Society or its successors or assigns. 236 This document and the information contained herein is provided on an 237 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 238 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 239 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 240 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 241 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 243 7 Intellectual Property Notice 245 The IETF takes no position regarding the validity or scope of any 246 intellectual property or other rights that might be claimed to 247 pertain to the implementation or use of the technology described in 248 this document or the extent to which any license under such rights 249 might or might not be available; neither does it represent that it 250 has made any effort to identify any such rights. Information on the 251 IETF's procedures with respect to rights in standards-track and 252 standards-related documentation can be found in BCP-11. Copies of 253 claims of rights made available for publication and any assurances of 254 licenses to be made available, or the result of an attempt made to 255 obtain a general license or permission for the use of such 256 proprietary rights by implementers or users of this specification can 257 be obtained from the IETF Secretariat. 259 The IETF invites any interested party to bring to its attention any 260 copyrights, patents or patent applications, or other proprietary 261 rights which may cover technology that may be required to practice 262 this standard. Please address the information to the IETF Executive 263 Director. 265 8 Acknowledgments 267 The review of the 3GPP SA4 committee is gratefully acknowledged, in 268 particular Per Frojdh. The chairs of the AVT working group, in 269 particular Colin Perkins, have provided both excellent guidance and 270 feedback, for which the authors are grateful. 272 9 Authors' Contact Information 273 David Singer 274 Apple Computer, Inc. 275 One Infinite Loop, MS:302-3MT 276 Cupertino CA 95014 277 USA 278 Email: singer@apple.com 279 Tel: +1 408 974 3162 281 Roberto Castagno 282 Nokia Mobile Phones 283 PO Box 88, FIN-33721 Tampere 284 (Tieteenkatu 1, FIN-33720 Tampere) 285 Finland 286 Email: roberto.castagno@nokia.com 287 Tel: +358 7180 35796 289 9 References 290 Normative 291 [3gpp] Published specifications in releases 5 and 6: 292 Release 5: 3GPP TS 26.234: Transparent end-to-end packet switched 293 streaming service (PSS); Protocols and codecs. 294 Release 6: 3GPP TS 26.244: Transparent end-to-end packet switched 295 streaming service (PSS); 3GPP file format (3GP) 297 [MIME1] Freed, N. and N. Borenstein, "Multipurpose Internet Mail 298 Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 299 2045, November 1996. 301 [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate 302 Requirement Levels", 303 RFC 2119, March 1997 305 Informative 306 [RFC2429] C. Borman et al., "RTP Payload format for the 1998 version 307 of ITU-T Rec. H.263 Video (H.263+)" 308 RFC 2429, October 1998 310 [RFC3267] J. Sjoberg et al., "RTP Payload format and File Storage 311 format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate 312 WideBand (AMR-WB) Audio Codecs" 313 RFC 3267, June 2002 315 -- 316 David Singer 317 Apple Computer/QuickTime