idnits 2.17.1 draft-garudadri-avt-3gpp2-mime-02.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.a on line 18. -- Found old boilerplate from RFC 3978, Section 5.5 on line 330. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 302. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 309. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 315. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 320), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 40. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? ** 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. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. 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 : ---------------------------------------------------------------------------- ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. 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 (January 2005) is 7040 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: '3GPP2' is mentioned on line 71, but not defined == Unused Reference: 'MIME1' is defined on line 279, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. '3gpp2' -- Obsolete informational reference (is this intentional?): RFC 2429 (Obsoleted by RFC 4629) Summary: 7 errors (**), 0 flaws (~~), 4 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft: 3GPP2 Multimedia Registrations H. Garudadri 2 Document: draft-garudadri-avt-3gpp2-mime-02 QUALCOMM 3 Expires: July 2005 January 2005 5 MIME Type Registrations for 3GPP2 Multimedia files 7 RFC Editor Considerations 9 The references to RFC XXXX in the MIME registrations need to be 10 replaced with the actual RFC number of this document when it is 11 issued. 13 Status of This Memo 15 By submitting this Internet-Draft, each author represents that any 16 applicable patent or other IPR claims of which he or she is aware 17 have been or will be disclosed, and any of which he or she becomes 18 aware will be disclosed, in accordance with Section 6 of RFC 3668. 20 By submitting this Internet-Draft, I accept the provisions of 21 Section 3 of RFC 3667 (BCP 78). 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF), its areas, and its working groups. Note that 25 other groups may also distribute working documents as Internet- 26 Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six 29 months and may be updated, replaced, or obsoleted by other documents 30 at any time. It is inappropriate to use Internet-Drafts as 31 reference material or to cite them other than as "work in progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/ietf/1id-abstracts.txt The list of 35 Internet-Draft Shadow Directories can be accessed at 36 http://www.ietf.org/shadow.html. 38 Copyright Notice 40 Copyright (C) The Internet Society (2005). All Rights Reserved. 42 Abstract 44 This document serves to register and document the standard MIME 45 types associated with the 3GPP2 multimedia file format, which is 46 part of the family based on the ISO Media File Format. 48 Table of Contents 50 RFC Editor Considerations . . . . . . . . . . . . . . . . . . . 3 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 1.1. Conventions Used in this Document . . . . . . . . . . . . 3 53 2. Security Considerations . . . . . . . . . . . . . . . . . . . 4 54 3. MIME Types . . . . . . . . . . . . . . . . . . . . . . . . . 4 55 3.1. Files with audio but no video . . . . . . . . . . . . . . 6 56 3.2. Any files . . . . . . . . . . . . . . . . . . . . . . . . 7 57 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 58 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7 59 6. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 7 60 7. Normative References . . . . . . . . . . . . . . . . . . . . 8 61 8. Informative References . . . . . . . . . . . . . . . . . . . . 8 62 Intellectual Property Statement . . . . . . . . . . . . . . . . 8 63 Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 9 64 Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . -1 66 1. Introduction 68 The third-generation partnership project 2 (3GPP2) for 3rd 69 generation cellular telephony has defined a standard file format to 70 contain audio/visual sequences which may be downloaded to cellular 71 phones [3GPP2]. At the time of writing, the 3GPP2 file format (3G2) 72 can contain H.263, H.264 or MPEG-4 video; and 13K Vocoder, EVRC or 73 AMR Narrow-band speech, or AAC audio; and 3GPP timed text. 75 Within the file, as with all files in the 'ISO' family, there is an 76 intrinsic file-type box, which identifies those specifications to 77 which the file complies, and which players (possibly compliant with 78 only one specification) are permitted by the content author to play 79 the file. This identification is through four-letter 'brands'. 80 Files identified by the MIME type defined in this document MUST 81 contain a brand defined in a standard issued by 3GPP2 that can apply 82 to 3GPP2 files, in their compatible brands list. 84 The MIME types defined in this document are needed correctly to 85 identify such files when they are served over HTTP, included in 86 multi-part documents, or used in other places where MIME types are 87 used. 89 1.1. Conventions Used in this Document 90 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 91 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 92 document are to be interpreted as described in RFC 2119 [RFC2119]. 94 2. Security Considerations 96 The 3GPP2 file format may contain audio, video, and displayable text 97 data. There is currently no provision for 'active' elements (such 98 as scripts) of any kind. 100 Clearly it is possible to author malicious files which attempt to 101 call for an excessively large picture size, high sampling-rate audio 102 etc. However, clients can and usually do protect themselves against 103 this kind of attack. 105 It should be noted that selected metadata fields may encompass 106 information partly intended to protect the media against 107 unauthorized use or distribution. In this case the intention is 108 that alteration or removal of the data in the field would be treated 109 as an offense under national agreements based World Intellectual 110 Property Organization (WIPO) treaties. 112 3GPP2 files have an extensible structure, so that it is 113 theoretically possible that metadata fields or media formats could 114 be defined in the future which could be used to induce particular 115 actions on the part of the recipient, thus presenting additional 116 security risks, but this type of capability is currently not 117 supported in the referenced specification. 119 Encryption, signing, and/or authentication of these file formats can 120 be done using any media-independent transformations of the file or 121 media data. 123 3. MIME Types 125 This registration applies to all files defined as using the '3G2' 126 file format and identified with a suitable brand in a 3GPP2 127 specification. The usual file suffix for all these files is ".3g2". 129 3.1. Files with audio but no video 131 The type "audio/3gpp2" may be used for files containing audio but no 132 visual presentation (neither video nor timed text, for example). 134 To: ietf-types@iana.org 135 Subject: Registration of Standard MIME media type audio/3gpp2 137 MIME media type name: 139 audio 140 MIME subtype name: 141 3gpp2 142 Required parameters: 143 None 144 Optional parameters: 145 Codecs. See [bucket] 146 Optional parameter values: 147 [C.S0050] 148 Encoding considerations: 149 This data is binary and should be transmitted in a suitable 150 encoding without CR/LF conversion, 7-bit stripping etc.; base64 151 is a suitable encoding. Note that this MIME type is used only 152 for files; separate types are used for real-time transfer, such 153 as for the RTP payload format for 13K vocoder speech [RFC2658]. 154 Security considerations: 155 See the security considerations section in RFC XXXX (this 156 document) 157 Interoperability considerations: 158 The 3GPP2 organization has defined the specification of the 159 media format [3gpp2]. Interoperability and conformance testing 160 is done in cooperation with other bodies including the Open 161 Mobile Alliance (OMA) and 162 the International Multimedia Telecommunications Consortium 163 (IMTC) . 164 Published specification: 165 3GPP2 C.S0045, 3GPP2 C.S0050. 167 3GPP2 specifications are publicly accessible at the 3GPP2 web 168 site, . 169 Applications which use this media type: 170 Multi-media 171 Additional information: 172 The type "audio/3gpp2" MAY be used for files containing audio 173 but no visual presentation. Files served under this type MUST 174 NOT contain any visual material. (Note that 3GPP timed text is 175 visually presented and is considered to be visual material). 176 Magic number(s): 177 None. However, the file-type box must occur first in the file, 178 and MUST contain a 3GPP2 brand in its compatible brands list. 179 File extension(s): 180 3g2 and 3gpp2 are both declared at ; 181 3g2 is preferred 182 Macintosh File Type Code(s): 183 '3gp2' 184 Person & email address to contact for further information: 186 H. Garudadri, hgarudadri@qualcomm.com 187 Intended usage: 188 COMMON 189 Change controller: 190 3GPP2 192 3.2. Any files 194 The type "video/3gpp2" is valid for all files. It is valid to serve 195 an audio-only file as "video/3gpp2". 197 To: ietf-types@iana.org 198 Subject: Registration of Standard MIME media type video/3gpp2 200 MIME media type name: 201 video 202 MIME subtype name: 203 3gpp2 204 Required parameters: 205 None 206 Optional parameters: 207 Codecs. See [bucket]. 208 Optional parameter values: 209 [C.S0050] 210 Encoding considerations: 211 This data is binary and should be transmitted in a suitable 212 encoding without CR/LF conversion, 7-bit stripping etc.; base64 213 is a suitable encoding. Note that this MIME type is used only 214 for files; separate types are used for real-time transfer, such 215 as for the RTP payload formats for H.263 [RFC2429] and 13K 216 vocoder speech [RFC2658]. 217 Security considerations: 218 See the security considerations section in RFC XXXX (this 219 document) 220 Interoperability considerations: 221 The 3GPP2 organization has defined the specification of the 222 media format [3gpp2]. Interoperability and conformance testing 223 is done in cooperation with other bodies including the Open 224 Mobile Alliance (OMA) and 225 the International Multimedia Telecommunications Consortium 226 (IMTC) . 227 Published specification: 228 3GPP2 C.S0045, 3GPP2 C.S0050. 230 3GPP2 specifications are publicly accessible at the 3GPP2 web 231 site, . 233 Applications which use this media type: 234 Multi-media 235 Additional information: 236 Magic number(s): 237 None. However, the file-type box must occur first in the file, 238 and MUST contain a 3GPP2 brand in its compatible brands list. 239 File extension(s): 240 3g2 and 3gpp2 are both declared at ; 241 3g2 is preferred 242 Macintosh File Type Code(s): 243 '3gp2' 244 Person & email address to contact for further information: 245 H.Garudadri, hgarudadri@qualcomm.com 246 Intended usage: 247 COMMON 248 Change controller: 249 3GPP2 251 4. IANA Considerations 253 This document registers the MIME media types audio/3gpp2 and 254 video/3gpp2, defined above. 256 5. Acknowledgments 258 This document used RFC 3839 as a template. The authors of RFC 3839, 259 R. Castagno and D. Singer, are gratefully acknowledged. 261 6. Author's Address 262 Harinath Garudadri 263 Qualcomm Inc 264 5775 Morehouse Dr. 265 San Diego, CA 92121 266 Email: hgarudadri@qualcomm.com 267 Tel: +1 858 651 6383 269 7. Normative References 271 [3gpp2] Published specifications: C.S0050-0 v1.0: 3GPP2 File 272 Formats for Multimedia Services. C.S0045-0 v1.0: Multimedia 273 Messaging Service (MMS) Media Format and Codecs for cdma2000 Spread 274 Spectrum Systems 276 [bucket] "The Codecs Parameter for 'Bucket' Media Types", 277 draft-gellens-mime-bucket-01, work in progress. 279 [MIME1] Freed, N. and N. Borenstein, "Multipurpose Internet Mail 280 Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 281 2045, November 1996. 283 [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate 284 Requirement Levels", RFC 2119, March 1997 286 8. Informative References 287 [RFC2429] C. Borman et al., "RTP Payload format for the 1998 version 288 of ITU-T Rec. H.263 Video (H.263+)", RFC 2429, October 1998 290 [RFC2658] K. McKay, "RTP Payload format for PureVoice(tm) Audio", 291 RFC 2658, August 1999 293 Intellectual Property Statement 295 The IETF takes no position regarding the validity or scope of any 296 Intellectual Property Rights or other rights that might be claimed 297 to pertain to the implementation or use of the technology described 298 in this document or the extent to which any license under such 299 rights might or might not be available; nor does it represent that 300 it has made any independent effort to identify any such rights. 301 Information on the procedures with respect to rights in RFC 302 documents can be found in BCP 78 and BCP 79. 304 Copies of IPR disclosures made to the IETF Secretariat and any 305 assurances of licenses to be made available, or the result of an 306 attempt made to obtain a general license or permission for the use 307 of such proprietary rights by implementers or users of this 308 specification can be obtained from the IETF on-line IPR repository 309 at http://www.ietf.org/ipr. 311 The IETF invites any interested party to bring to its attention any 312 copyrights, patents or patent applications, or other proprietary 313 rights that may cover technology that may be required to implement 314 this standard. Please address the information to the IETF at 315 ietf-ipr@ietf.org. 317 Full Copyright Statement 318 Copyright (C) The Internet Society (2005). This document is subject 319 to the rights, licenses and restrictions contained in BCP 78, and 320 except as set forth therein, the authors retain all their rights. 322 Disclaimer 324 This document and the information contained herein are provided on 325 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 326 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE 327 INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR 328 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 329 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 330 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.