1 2 3 4 5 6 7Network Working Group L. Walleij 8Request for Comments: 3534 The Ogg Vorbis Community 9Category: Standards Track May 2003 10 11 12 The application/ogg Media Type 13 14Status of this Memo 15 16 This document specifies an Internet standards track protocol for the 17 Internet community, and requests discussion and suggestions for 18 improvements. Please refer to the current edition of the "Internet 19 Official Protocol Standards" (STD 1) for the standardization state 20 and status of this protocol. Distribution of this memo is unlimited. 21 22Copyright Notice 23 24 Copyright (C) The Internet Society (2003). All Rights Reserved. 25 26Abstract 27 28 The Ogg Bitstream Format aims at becoming a general, freely-available 29 standard for transporting multimedia content across computing 30 platforms and networks. The intention of this document is to define 31 the MIME media type application/ogg to refer to this kind of content 32 when transported across the Internet. It is the intention of the Ogg 33 Bitstream Format developers that it be usable without intellectual 34 property concerns. 35 36Conventions used in this Document 37 38 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 39 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 40 document are to be interpreted as described in RFC 2119 [2]. 41 421. The Ogg Bitstream Format 43 44 The Ogg Bitstream format has been developed as a part of a larger 45 project aimed at creating a set of components for the coding and 46 decoding of multimedia content (codecs) which are to be freely 47 available and freely re-implementable both in software and in 48 hardware for the computing community at large, including the Internet 49 community. 50 51 Raw packets from these codecs may be used directly by transport 52 mechanisms that provide their own framing and packet-separation 53 mechanisms (such as UDP datagrams). 54 55 56 57 58Walleij Standards Track [Page 1] 59 60RFC 3534 The application/ogg Media Type May 2003 61 62 63 One such framing and content-separation mechanism is the real-time 64 transport protocol (RTP). RTP allows the streaming of synchronous 65 lossy data for broadcasting and similar purposes. If this function 66 is desired then a separate RTP wrapping mechanism should be used. A 67 wrapping mechanism is currently under development. 68 69 For stream based storage (such as files) and transport (such as TCP 70 streams or pipes), Ogg codecs use the Ogg Bitstream Format to provide 71 framing/sync, sync recapture after error, landmarks during seeking, 72 and enough information to properly separate data back into packets at 73 the original packet boundaries without relying on decoding to find 74 packet boundaries. The application/ogg MIME type refers to this kind 75 of bitstreams, when no further knowledge of the bitstream content 76 exists. 77 78 The bitstream format in itself is documented in [1]. 79 802. Registration Information 81 82 To: [email protected] 83 84 Subject: Registration of MIME media type application/ogg 85 86 MIME media type name: application 87 88 MIME subtype name: ogg 89 90 Required parameters: none 91 92 Optional parameters: none 93 94 Encoding Considerations: 95 96 The Ogg bitstream format is binary data, and must be encoded for 97 non-binary transport; the Base64 encoding is suitable for Email. 98 Binary encoding could also be used. 99 100 Security Considerations: 101 102 As the Ogg bitstream file is a container format and only a carrier of 103 content (such as Vorbis audio) with a very rigid definition (see 104 [1]), this format in itself is not more vulnerable than any other 105 content framing mechanism. The main security consideration for the 106 receiving application is to ensure that manipulated packages can not 107 cause buffer overflows and the like. It is possible to encapsulate 108 even executable content in the bitstream, so for such uses additional 109 security considerations must be taken. 110 111 112 113 114Walleij Standards Track [Page 2] 115 116RFC 3534 The application/ogg Media Type May 2003 117 118 119 Ogg bitstream files are not signed or encrypted using any applicable 120 encryption schemes. External security mechanisms must be added if 121 content confidentiality and authenticity is to be achieved. 122 123 Interoperability considerations: 124 125 The Ogg bitstream format has proved to be widely implementable across 126 different computing platforms. A broadly portable reference 127 implementation is available under a BSD license. 128 129 The Ogg bitstream format is not patented and can be implemented by 130 third parties without patent considerations. 131 132 Published specification: 133 134 See [1]. 135 136 Applications which use this media type: 137 138 Any application that implements the specification will be able to 139 encode or decode Ogg bitstream files. Specifically, the format is 140 supposed to be used by subcodecs that implement, for example, Vorbis 141 audio. 142 143 Additional information: 144 145 Magic number(s): 146 147 In Ogg bitstream files, the first four bytes are 0x4f 0x67 0x67 0x53 148 corresponding to the string "OggS". 149 150 File extension: .ogg 151 152 Macintosh File Type Code(s): OggS 153 154 Object Identifier(s) or OID(s): none 155 156 Person & email address to contact for further information: 157 158 Questions about this proposal should be directed to Linus Walleij 159 <[email protected]>. Technical questions about the Ogg bitstream 160 standard may be asked on the mailing lists for the developer 161 community. <http://www.xiph.org/archives/> 162 163 Intended usage: COMMON 164 165 166 167 168 169 170Walleij Standards Track [Page 3] 171 172RFC 3534 The application/ogg Media Type May 2003 173 174 175 Author/Change controller: 176 177 This document was written by Linus Walleij <[email protected]>. 178 Changes to this document will either be handled by him, a 179 representative of the Xiph.org, or the associated development 180 communities. 181 182 The Ogg bitstream format is controlled by the Xiph.org and the 183 respective development communities. 184 1853. Security Considerations 186 187 Security considerations are discussed in the security considerations 188 clause of the MIME registration in section 2. 189 1904. Normative References 191 192 [1] Pfeiffer, S., "The Ogg encapsulation format version 0", RFC 193 3533, May 2003. 194 195 [2] Bradner, S., "Key words for use in RFCs to Indicate Requirement 196 Levels", BCP 14, RFC 2119, March 1997. 197 1985. Intellectual Property Statement 199 200 The IETF takes no position regarding the validity or scope of any 201 intellectual property or other rights that might be claimed to 202 pertain to the implementation or use of the technology described in 203 this document or the extent to which any license under such rights 204 might or might not be available; neither does it represent that it 205 has made any effort to identify any such rights. Information on the 206 IETF's procedures with respect to rights in standards-track and 207 standards-related documentation can be found in BCP-11. Copies of 208 claims of rights made available for publication and any assurances of 209 licenses to be made available, or the result of an attempt made to 210 obtain a general license or permission for the use of such 211 proprietary rights by implementors or users of this specification can 212 be obtained from the IETF Secretariat. 213 214 The IETF invites any interested party to bring to its attention any 215 copyrights, patents or patent applications, or other proprietary 216 rights which may cover technology that may be required to practice 217 this standard. Please address the information to the IETF Executive 218 Director. 219 220 221 222 223 224 225 226Walleij Standards Track [Page 4] 227 228RFC 3534 The application/ogg Media Type May 2003 229 230 2316. Author's Address 232 233 Linus Walleij 234 The Ogg Vorbis Community 235 Master Olofs Vag 24 236 Lund 224 66 237 SE 238 239 Phone: +46 703 193678 240 EMail: [email protected] 241 URI: http://www.xiph.org/ 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282Walleij Standards Track [Page 5] 283 284RFC 3534 The application/ogg Media Type May 2003 285 286 2877. Full Copyright Statement 288 289 Copyright (C) The Internet Society (2003). All Rights Reserved. 290 291 This document and translations of it may be copied and furnished to 292 others, and derivative works that comment on or otherwise explain it 293 or assist in its implementation may be prepared, copied, published 294 and distributed, in whole or in part, without restriction of any 295 kind, provided that the above copyright notice and this paragraph are 296 included on all such copies and derivative works. However, this 297 document itself may not be modified in any way, such as by removing 298 the copyright notice or references to the Internet Society or other 299 Internet organizations, except as needed for the purpose of 300 developing Internet standards in which case the procedures for 301 copyrights defined in the Internet Standards process must be 302 followed, or as required to translate it into languages other than 303 English. 304 305 The limited permissions granted above are perpetual and will not be 306 revoked by the Internet Society or its successors or assigns. 307 308 This document and the information contained herein is provided on an 309 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 310 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 311 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 312 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 313 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 314 315Acknowledgement 316 317 Funding for the RFC Editor function is currently provided by the 318 Internet Society. 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338Walleij Standards Track [Page 6] 339 340