ref: 0386df9c1b411b547e69d033c4b611d9cab389c7
parent: f157736ec5ef430512d08a38151626939d52367c
author: Ralph Giles <giles@mozilla.com>
date: Sun Aug 31 07:37:34 EDT 2014
Clarify ambiguity between 'streams' and 'files'. We want to general guidelines for stream-level encapsulation to apply to multiplexed as well as degenerate streams. 'Files' can therefore specific to the mine-type discussion for unmultiplexed Ogg physical streams.
--- a/doc/draft-ietf-codec-oggopus.xml
+++ b/doc/draft-ietf-codec-oggopus.xml
@@ -139,7 +139,7 @@
<section anchor="packet_organization" title="Packet Organization">
<t>
-An Opus stream is organized as follows.
+An Ogg Opus stream is organized as follows.
</t>
<t>
There are two mandatory header packets.
@@ -1206,7 +1206,7 @@
</postamble>
</figure>
<t>
-An Ogg Opus file MUST NOT have more than one of each tag, and if present
+An Ogg Opus stream MUST NOT have more than one of each tag, and if present
their values MUST be an integer from -32768 to 32767, inclusive,
represented in ASCII with no whitespace.
If present, R128_TRACK_GAIN and R128_ALBUM_GAIN MUST correctly represent
@@ -1285,7 +1285,7 @@
<section anchor="encoder" title="Encoder Guidelines">
<t>
-When encoding Opus files, Ogg encoders should take into account the
+When encoding Opus streams, Ogg encoders should take into account the
algorithmic delay of the Opus encoder.
</t>
<figure align="center">
@@ -1416,7 +1416,7 @@
</t>
<t>
-Like most other container formats, Ogg Opus files should not be used with
+Like most other container formats, Ogg Opus streams should not be used with
insecure ciphers or cipher modes that are vulnerable to known-plaintext
attacks.
Elements such as the Ogg page capture pattern and the magic signatures in the