Re: Transport Draft Comments, mostly about error handling

[Martin Thomson <[e-mail]>]

On 19 August 2017 at 04:37, Martin Duke <[e-mail]> wrote:
> (1) Section 8.14. Stream Frames for Stream 1 and above MUST NOT be in
> Cleartext packets of any kind.

That should be in the -tls draft (though it will eventually move to -transport).

> (4) Section 12. Error Handling: If a peer initiates an odd stream when it's
> supposed to be even, or vice versa, what kind of error is that? Is it a
> stream error or connection error?

Since all stream opening uses authenticated packets, I think that
connection error is appropriate.  Also, I don't know how to recover
from this situation gracefully, particularly if the numbers collide.
That said, it makes the h2 settings situation bad.

> (5) Section 12.3 Error Codes: For a Frame Error on a STREAM or ACK frame, is
> the last two bytes of the error code the whole flags byte of the packet, or
> just the mask (0xa0, 0xb0) of the frame type?

The entire byte.  Thus, there are many error codes that represent
STREAM frame errors.  (I agree that that could be difficult, and it's
something I'd be happy to see someone open an issue on to track.)