These are normative whether capitalized or not. Capitalize the ones
which make sense as normative requirements, and reword the rest.

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.

These are the changes proposed in
 <http://www.ietf.org/mail-archive/web/codec/current/msg03058.html>,
 with some minor additions (see follow-up on the list).

Promote the new tag definitions to a separate subsection,
balance tags, improve wording, and document our motivation
for the R128 tags.

Thanks to Calvin Walton for pointing this out.

Patch from Greg Maxwell in response to implementor feedback.
https://www.ietf.org/mail-archive/web/codec/current/msg03053.html

Timothy B. Terriberry authored 10 years ago and Jean-Marc Valin committed 10 years ago

Here are my proposals to resolve a few issues with the current
 draft.
See the corresponding message to the list for details.

Timothy B. Terriberry authored 10 years ago and Jean-Marc Valin committed 10 years ago

This is the result of an editing pass for clarity and consistency.

Addresses comments from several months ago

Bump version and date for draft-ietf-codec-oggopus-03 submission.

Move more text into figure pre/postamble to fix rendering issues
in the xml2rfc html output. These need to be manually re-indented
in the txt output before submission. :(

Fix resampling frequency choice algorithm, which was missing a word.

Fix some spelling and make some minor enphasis changes.

These aren't available over https, but actually work, unlike
the old reference urls.

Fixes a nit.

Fixes a nit. According to idnits, 'NOT RECOMMENDED' is optional,
but we use it. Other words, like SHALL which we don't use are
required in the boilerplate.

This seems to be the correct way to represent institutional authors
in the references.

and use them more strictly in the rest of the text.

Comment from mark4o.

It wants a surname, and to show it as Surname, Initial.
This leaves an extra comma in the xml2rfc2 output, but
at least mentions wikipedia.

Marko was concerned that RFC 6716 section 3.2.1 narrowly describes
zero-length DTX frames _only_ for code 2 and 3 packets, and therefore
wanted this sentence to state clearly that code 0 and 1 can be used
with zero-byte frames as well. I've tried to do that.

There was some attempt to use LP/MDCT instead, to avoid confusion
of the Opus modes with the earlier codecs of the same name, but
Jean-Marc says they gave up on doing that in the Opus RFC, and in
particular the tables a reader would need to reference from RFC 6716
Section 3.2 mentions SILK and CELT, so I think it's important to use
the same terms here.

It's not hyphenated anywhere else.

I hope.  Now that it's been clarified for me what this originally meant
to say, it's tricky to know if this actually contains the missing clue
for other readers.  Hopefully it should be obvious to anyone actually
implementing it once they look at what modes they have to choose from.

Ron's suggestion. We think it's clear enough as is and
removing it avoids confusion about this specification
versus future extensions.