Thanks to Barry for proposing specific text for the changes.

Ralph Giles correctly points out that the sequence number field in
 Ogg pages starts couting at 0, so counting from 1 in the diagram
 might be confusing.

For RFC 6716, the RFC Editor converted our Wikipedia URLs into
 stable ones that would always point at the same version of the
 page.
We're close enough to the end that we can go ahead and do that in
 advance (and also update the dates to reflect the most recent
 version).

- Clarify that 125,829,120 is just 120 MB.
- Add a figure to Section 3 of an example logical stream.
- Add a reference for Q notation.
- Refer to the downmixing figures in the text.
- Clarify that user comments are UTF-8.
- Clarify that the -573 and 111 gain values are examples.
- Add specific advice to implementors on areas that have security
   implications.

Apparently the IETF does not like having the BSD copyright in the
 .xml source (despite the CODEC WG's IPR advisor saying this was
 okay), so we need a new version.

It looks like this was included accidentally.

Thanks to mark4o for pointing out I'd missed this in the previous
removal.

It looks like this was included accidentally.

The improves the reproducibilit of the build. The date
was nice to have, but there's a version string at the
top which should identify the release correctly.

The copyright date could actually be incorrect, since
it is based on the build date and not the last-changed
date.

Use https urls.
Indent nesting levels and add missing </td>.

Hopefully this is even clearer.
Thanks again to Mark Harris for the suggestion.

This avoids the claim that all possible Opus implementations would
 run at rates that divide 48 kHz.
Thanks to Mark Harris for raising the issue.

This also removes the request for an additional grant from the IETF
 Trust on the final RFC.
I believe this is sufficient to exercise our ability to allow
 downstream modifications as proposed in RFC 5377 Section 4.4.
See the discussion at
 <https://www.ietf.org/mail-archive/web/codec/current/msg03169.html>
 for details.

Thanks to Ron Lee for the suggestion.

Thanks to Sabrina Tanamal for pointing out the ambiguity.

The set of supported Doxygenfile keys changes from release
to release, often resulting in warnings about needing to
upgrade the configuration file. However, this isn't
practical given the various versions different developers
have installed.

However, for the vast majority of keys we just want the
default values, so instead only include the keys we've
specifically set and let doxygen fall back to defaults
for all the rest.

Thanks to Joel Halpern for the suggestion.

Thanks to Joel Halpern for pointing out the discrepancy.

Thanks to Ben Campbell for the report.

From AD review.

From AD review.

Removed 2119 language for general Ogg requirements.
Added IANA registry for channel mapping families.
Adjusted additional copyright grant to match RFC 6716.
Additional comments addressed (see the CODEC mailing list).

Mark Harris convinced me that the significant delay between "WG
 consensus" and "RFC" means we shouldn't rely on RFC updates to
 give people permission to start deploying new things.

Thanks to Mark Harris for the report.

Also remove most <preamble>/<postamble> usage for expository text,
 as most places center the result, which looks ugly (only local
 xml2rfc HTML output does not center: tools.ietf.org HTML output
 still does, as does the .txt version).

To avoid confusion with an RFC 6716 encoder/decoder.
No part of this document is intended to update RFC 6716.

I *think* all we need to do is document this and the RFC editors
will take care of it.

We mention this in the description of Channel Mapping Family 0.
Might as well link to RFC 7587.

Review comment from Mo Zanaty.

This improves readability in the xml2rfc html output, but
generates Markdown-style *bold* in the txt output, and
more importantly in the nroff-like html output of the
tools.ietf.org toolchain, which Mo Zanaty and some in
IRC objected to.