<html xmlns="http://www.w3.org/1999/xhtml" a0:Name="SuikaWiki" xmlns:a0="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:Version="0.9"><head><a0:parameter name="import"><a0:value>メッセージ訳語集</a0:value><a0:value>RFC訳語集</a0:value><a0:value>その他の訳語集</a0:value></a0:parameter></head><body><p><strong>The application/ogg Media Type <ins><code>application/ogg</code> <a0:replace by="media type"></a0:replace></ins></strong><ul><li>Network Working Group                                         </li><li>Request for Comments: 3534                      </li><li>Category: Standards Track                                       -May 2003</li><li>L. Walleij</li><li>The Ogg Vorbis Community</li></ul></p><section><h1>Status of this Memo</h1><blockquote><p>This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the &quot;Internet
Official Protocol Standards&quot; (STD 1) for the standardization state
and status of this protocol.  Distribution of this memo is unlimited.</p></blockquote></section><section><h1>Copyright Notice</h1><blockquote><p>Copyright (C) The Internet Society (2003).  All Rights Reserved.</p></blockquote></section><section><h1>Abstract</h1><blockquote><p>The Ogg Bitstream Format aims at becoming a general, freely-available
standard for transporting multimedia content across computing
platforms and networks.  The intention of this document is to define
the MIME media type application/ogg to refer to this kind of content
when transported across the Internet.  It is the intention of the Ogg
Bitstream Format developers that it be usable without intellectual
property concerns.</p></blockquote><p>Ogg ビット列書式は、計算機<a0:replace by="platform"></a0:replace>・ネットワークを通じた<a0:replace by="multimedia"></a0:replace>内容の転送における、
一般に自由に利用出来る標準となることを狙っています。
この文書の目的は、その種類の内容を<a0:replace by="Internet"></a0:replace>を通して転送するときに参照する
MIME <a0:replace by="media type"></a0:replace> <code>application/ogg</code>
を定義することです。 Ogg ビット列書式開発者の意図するところは、
これを知的所有権問題無しに使用可能とすることです。</p></section><section><h1>Conventions used in this Document <ins>この文書で使う用語</ins></h1><blockquote><p>The key words &quot;MUST&quot;, &quot;MUST NOT&quot;, &quot;REQUIRED&quot;, &quot;SHALL&quot;, &quot;SHALL NOT&quot;,
&quot;SHOULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMENDED&quot;, &quot;MAY&quot;, and &quot;OPTIONAL&quot; in this
document are to be interpreted as described in RFC 2119 [2].</p></blockquote><p>この文書中の<a0:replace by="keyword"></a0:replace> <code><a0:anchor>MUST</a0:anchor></code>, <code>MUST NOT</code>,
<code>[REQUIRED</code>]], <code><a0:anchor>SHALL</a0:anchor></code>,
<code>SHALL NOT</code>, <code><a0:anchor>SHOULD</a0:anchor></code>, <code>SHOULD NOT</code>,
<code><a0:anchor>RECOMMENDED</a0:anchor></code>, <code><a0:anchor>MAY</a0:anchor></code>,
<code><a0:anchor>OPTIONAL</a0:anchor></code> は、 <a0:anchor>RFC2119</a0:anchor>
で説明されているように解釈することとします。</p></section><section><h1>1. The Ogg Bitstream Format <ins>Ogg ビット列形式</ins></h1><blockquote><p>The Ogg Bitstream format has been developed as a part of a larger
project aimed at creating a set of components for the coding and
decoding of multimedia content (codecs) which are to be freely
available and freely re-implementable both in software and in
hardware for the computing community at large, including the Internet
community.</p></blockquote><p>Ogg ビット列書式は、<a0:replace by="Internet community"></a0:replace>を含む<a0:replace by="computing community"></a0:replace>に向けた、ソフトウェア及びハードウェアのどちらでも自由に利用可能で自由に実装可能な、<a0:replace by="multimedia"></a0:replace>内容の符号化及び復号部品
(<a0:anchor>codec</a0:anchor>) の集合を作成することを目的とした上位の計画の一部として開発されています。</p><blockquote><p>Raw packets from these codecs may be used directly by transport
mechanisms that provide their own framing and packet-separation
mechanisms (such as UDP datagrams).</p></blockquote><p>これらの codec の<a0:replace by="raw packet"></a0:replace>は、
自身の<a0:replace by="framing"></a0:replace>及び<a0:replace by="packet"></a0:replace>分離の機構を持つ転送機構
(例えば <a0:anchor>UDP</a0:anchor> <a0:replace by="datagram"></a0:replace>)
では直接使用することが出来ます。</p><blockquote><p>One such framing and content-separation mechanism is the real-time
transport protocol (RTP).  RTP allows the streaming of synchronous
lossy data for broadcasting and similar purposes.  If this function
is desired then a separate RTP wrapping mechanism should be used.  A
wrapping mechanism is currently under development.</p></blockquote><p>そのような<a0:replace by="framing"></a0:replace>及び内容分離の機構は、<a0:replace by="real-time"></a0:replace>転送<a0:replace by="protocol"></a0:replace> (<a0:anchor>RTP</a0:anchor>)
です。 RTP を使うと放送や同様の目的のための同期<a0:replace by="lossy"></a0:replace>データの<a0:replace by="streaming"></a0:replace>を行うことができます。
この機能が望ましい時には、分離 RTP <a0:replace by="wrapping"></a0:replace>機構を使用するべきです。 <a0:replace by="wrapping"></a0:replace>機構は現在開発中です。</p><blockquote><p>For stream based storage (such as files) and transport (such as TCP
streams or pipes), Ogg codecs use the Ogg Bitstream Format to provide
framing/sync, sync recapture after error, landmarks during seeking,
and enough information to properly separate data back into packets at
the original packet boundaries without relying on decoding to find
packet boundaries.  The application/ogg MIME type refers to this kind
of bitstreams, when no further knowledge of the bitstream content exists.</p></blockquote><p>(<a0:replace by="file"></a0:replace>のような) <a0:replace by="stream"></a0:replace>を基にした<a0:replace by="storage"></a0:replace>と
(<a0:anchor>TCP</a0:anchor> <a0:replace by="stream"></a0:replace>や<a0:replace by="pipe"></a0:replace>のような) 
転送では、 Ogg codec は、<a0:replace by="packet"></a0:replace>境界を探すために復号すること無しに元の<a0:replace by="packet"></a0:replace>境界でデータを適切に分離するための <a0:replace by="framing"></a0:replace>/同期, <a0:replace by="error"></a0:replace>語の同期再<a0:replace by="capture"></a0:replace>, 探索中の目印付け及び十分な情報を提供するために
Ogg ビット列形式を使います。
<code>application/ogg</code> MIME <a0:replace by="type"></a0:replace>は、ビット列内容についての更なる知識が存在しない時にこの種のビット列を参照します。</p><blockquote><p>The bitstream format in itself is documented in [1].</p></blockquote><p>ビット列形式自体は [1] で文書化されています。</p></section><section><h1>2. Registration Information <ins>登録情報</ins></h1><pre>   To: ietf-types@iana.org</pre><pre>   Subject: Registration of MIME media type application/ogg</pre><pre>   MIME media type name: application</pre><pre>   MIME subtype name: ogg</pre><pre>   Required parameters: none</pre><pre>   Optional parameters: none</pre><pre>   Encoding Considerations:</pre><blockquote><p>The Ogg bitstream format is binary data, and must be encoded for
non-binary transport; the Base64 encoding is suitable for Email.
Binary encoding could also be used.</p></blockquote><p>Ogg ビット列形式はバイナリ・データであり、
非バイナリ転送路では符号化しなければなりません。
<a0:anchor>電子メイル</a0:anchor>では <a0:anchor>Base64</a0:anchor> 符号化が適当です。
<code class="MIME">Binary</code> 符号化も使用できます。</p><pre>   Security Considerations:</pre><blockquote><p>As the Ogg bitstream file is a container format and only a carrier of
content (such as Vorbis audio) with a very rigid definition (see [1]), this format in itself is not more vulnerable than any other
content framing mechanism.  The main security consideration for the
receiving application is to ensure that manipulated packages can not
cause buffer overflows and the like.  It is possible to encapsulate
even executable content in the bitstream, so for such uses additional
security considerations must be taken.</p></blockquote><p>Ogg ビット列<a0:replace by="file"></a0:replace>は包含形式であって、
非常に厳格な定義 ([1] 参照) を伴う
(Vorbis <a0:replace by="audio"></a0:replace>などの) 内容の運搬器にに過ぎず、
この形式自体は他の<a0:replace by="framing"></a0:replace>機構以上に脆弱なものではありません。
受信<a0:replace by="application"></a0:replace>の主たる保安上の注意点は、
操作<a0:replace by="package"></a0:replace>が<a0:replace by="buffer"></a0:replace>溢れのようなことをしかねないようにすることです。
ビット列中に実行可能な内容を<a0:replace by="encapsulate"></a0:replace>することも可能ですから、
そのような用途には追加の保安上の注意が必要です。</p><blockquote><p>Ogg bitstream files are not signed or encrypted using any applicable
encryption schemes.  External security mechanisms must be added if
content confidentiality and authenticity is to be achieved.</p></blockquote><p>Ogg ビット列<a0:replace by="file"></a0:replace>はどんな適用可能な方式を使っても署名したり暗号化されたりしていません。
内容の機密性や信頼性が必要な時には外部の安全上の機構を追加しなければなりません。</p><pre>   Interoperability considerations:</pre><blockquote><p>The Ogg bitstream format has proved to be widely implementable across
different computing platforms.  A broadly portable reference
implementation is available under a BSD license.</p></blockquote><p>Ogg ビット列書式は様々な計算機<a0:replace by="platform"></a0:replace>で広く実装可能なことは証明されています。広く可般な参照実装が
BSD <a0:replace by="license"></a0:replace>で入手可能です。</p><blockquote><p>The Ogg bitstream format is not patented and can be implemented by
third parties without patent considerations.</p></blockquote><p>Ogg ビット列書式は特許化されておらず、
特許の心配無しに第3者が実装することが出来ます。</p><pre>   Published specification:</pre><pre>   See [1].</pre><pre>   Applications which use this media type:</pre><blockquote><p>Any application that implements the specification will be able to
encode or decode Ogg bitstream files.  Specifically, the format is
supposed to be used by subcodecs that implement, for example, Vorbis
audio.</p></blockquote><p>仕様を実装する任意の<a0:replace by="application"></a0:replace>が Ogg
ビット列<a0:replace by="file"></a0:replace>を符号化したり復号したり出来ます。
特に、この書式は例えば Vorbis <a0:replace by="audio"></a0:replace>を実装する <a0:replace by="subcodec"></a0:replace>で使うことが想定されています。</p><pre>   Additional information:</pre><pre>   Magic number(s):</pre><blockquote><p>In Ogg bitstream files, the first four bytes are 0x4f 0x67 0x67 0x53
corresponding to the string &quot;OggS&quot;.</p></blockquote><p>Ogg ビット列<a0:replace by="file"></a0:replace>では、最初の4倍とは 
<code>0x4f 0x67 0x67 0x53</code> で、これは文字列
<code>OggS</code> に対応します。</p><pre>   File extension: .ogg</pre><pre>   Macintosh File Type Code(s): OggS</pre><pre>   Object Identifier(s) or OID(s): none</pre><pre>   Person &amp; email address to contact for further information:</pre><blockquote><p>Questions about this proposal should be directed to Linus Walleij
&lt;triad@df.lth.se&gt;.  Technical questions about the Ogg bitstream
standard may be asked on the mailing lists for the developer
community.  <a0:anchor-external a0:resScheme="URI" a0:resParameter="http://www.xiph.org/archives/">http://www.xiph.org/archives/</a0:anchor-external></p></blockquote><p>この提案についての質問は、 Linus Walleij
に直接ご連絡下さい。 Ogg ビット列規格についての技術的質問は開発者<a0:replace by="community"></a0:replace>の<a0:replace by="mailing list"></a0:replace>にお尋ね下さい。
<a0:anchor-external a0:resScheme="URI" a0:resParameter="http://www.xiph.org/archives/">http://www.xiph.org/archives/</a0:anchor-external></p><pre>   Intended usage: COMMON</pre><pre>   Author/Change controller:</pre><blockquote><p>This document was written by Linus Walleij &lt;triad@df.lth.se&gt;.
Changes to this document will either be handled by him, a
representative of the Xiph.org, or the associated development
communities.</p></blockquote><p>この文書は Linus Walleij が書きました。
この文書への変更は Linus, Xiph.org の代表,
又は関連開発<a0:replace by="community"></a0:replace>が扱います。</p><blockquote><p>The Ogg bitstream format is controlled by the Xiph.org and the
respective development communities.</p></blockquote><p>Ogg ビット列書式は Xiph.org とその開発者<a0:replace by="community"></a0:replace>が統制しています。</p></section><section><h1>3. Security Considerations</h1><blockquote><p>Security considerations are discussed in the security considerations
clause of the MIME registration in section 2.</p></blockquote></section><section><h1>4.  Normative References</h1><pre>   [1]  Pfeiffer, S., &quot;The Ogg encapsulation format version 0&quot;, RFC
        3533, May 2003.</pre><pre>   [2]  Bradner, S., &quot;Key words for use in RFCs to Indicate Requirement
        Levels&quot;, BCP 14, RFC 2119, March 1997.</pre></section><section><h1>5.  Intellectual Property Statement</h1><pre>   The IETF takes no position regarding the validity or scope of any
   intellectual property or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; neither does it represent that it
   has made any effort to identify any such rights.  Information on the
   IETF's procedures with respect to rights in standards-track and
   standards-related documentation can be found in BCP-11.  Copies of
   claims of rights made available for publication and any assurances of
   licenses to be made available, or the result of an attempt made to
   obtain a general license or permission for the use of such
   proprietary rights by implementors or users of this specification can
   be obtained from the IETF Secretariat.</pre><pre>   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights which may cover technology that may be required to practice
   this standard.  Please address the information to the IETF Executive
   Director.
*6.  Author's Address</pre><pre>   Linus Walleij
   The Ogg Vorbis Community
   Master Olofs Vag 24
   Lund  224 66
   SE</pre><pre>   Phone: +46 703 193678
   EMail: triad@df.lth.se
   URI:   http://www.xiph.org/</pre></section><section><h1>7.  Full Copyright Statement</h1><pre>   Copyright (C) The Internet Society (2003).  All Rights Reserved.</pre><pre>   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.</pre><pre>   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.</pre><pre>   This document and the information contained herein is provided on an
   &quot;AS IS&quot; basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.</pre></section><section><h1>Acknowledgement</h1><pre>   Funding for the RFC Editor function is currently provided by the
   Internet Society.</pre></section><section><h1>License</h1><p><a0:anchor>RFCのライセンス</a0:anchor></p></section><section><h1>メモ</h1></section></body></html>