Subject: [quicwg/base-drafts] Stream error handling is ambiguously specified (#1098)

From: Christian Huitema <[email-masked]>
Date: Mon, 05 Feb 2018 18:49:55 -0800

In section 12.2. Stream Errors the spec says:

    _If the error affects a single stream, but otherwise leaves the connection in a recoverable state,
    the endpoint can send a RST_STREAM frame (Section 8.3) with an appropriate error code..._

And a few lines later, it says:

   _RST_STREAM MUST be instigated by the application and MUST carry an application error code._ 

This is mildly ambiguous. What about stream errors like Stream State Error, Final Offset Error, or the Protocol Violation that occurs if a peer tries to close Stream 0? These are defined as Transport Error Codes, and thus can only be sent in a Connection Close message. Are they covered by the general "recoverable state" qualifier?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/1098