HTTP/2 Draft 16

Motivation:
HTTP/2 draft 16 has been released https://tools.ietf.org/html/draft-ietf-httpbis-http2-16.

Modifications:
The HTTP/2 codec should be updated to support draft 16.

Result:
HTTP/2 codec is draft 16 compliant.
Ah I see what you mean.  An endpoint could receive a PRIORITY frame for a stream with an unknown parent, since IDLE frames are not communicated to the remote endpoint (except for PP).  That is a bit ugly, but I think you're handling it correctly here.

Thanks for the clarification.