Update draft accepted as WG document
Minor nits on update draft

Signed-off-by: Jean-Marc Valin <jmvalin@jmvalin.ca>
Fix malloc_hook warning on glibc 2.17 and later.

In glib 2.17 the __malloc_ptr define was removed in favour
of using void* directly. Our declaration of mhook using this
type for the second argument therefore rightly generates a warning
on modern systems, since the type is assumed to be an int, which
is too narrow to hold a pointer on 64 bit architectures.

Since it was only ever a define we could use an #ifndef to define
__malloc_ptr ourselves. However we only use it once, so using void*
in the signature directly is cleaner. This should cause no problems
on older systems where it will match either the void* or the char*
(for non __STDC__ code) the define resolved to.
Add Tim's gap repair text.

From http://www.ietf.org/mail-archive/web/codec/current/msg03030.html
Rewrite gap filling section.

Incorporate list feedback from Mark Harris, Tim and Jean-Marc
and try to improve clarity.
Be a bit less ambiguous about the comment framing bit
Reword framing bit ommission, again.
Bump the static version string in version.mk.

We failed to do this before the 1.1 release, so that went out
still marked at 1.1 beta. The plan was to get rid of this file
but it's still used as a fallback by the msvc build.
Another nit in the update draft

Signed-off-by: Jean-Marc Valin <jmvalin@jmvalin.ca>
Update authors in RTP draft
Update Ralph's phone number.
Replace MAY with SHOULD in the gap-filling guidelines.

This is really the best implementations can do as far as we
understand the possibilies, so it's better to be straightforward.
Bump Ogg draft version and date.
Remove line about undefined speaker configurations.

Ron's suggestion. We think it's clear enough as is and
removing it avoids confusion about this specification
versus future extensions.
Clarify that MB->WB is better than MB->NB

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.
Drop the oddball hyphenation of MDCT-mode

It's not hyphenated anywhere else.
Use SILK/CELT everywhere describing modes.

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.
Try to clarify frame packing.

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.
Reference wikipedia for LPC prediction.
Reference vorbis source code for lpc coefficient calculation.