Subject: [quicwg/base-drafts] Text on handling stream close and data that follows it (#254)

From: Martin Thomson <[email-masked]>
Date: Tue, 31 Jan 2017 19:45:44 -0800

This is based on @marten-seemann's work on #145.  I've taken the notion of "final offset" and formalized it more:

* Define final offset as the offset of the end of stream data
* Describe how the final offset is carried in RST_STREAM and STREAM frames
* Final offset can't change, describe the error to use
* Data can't be sent after the final offset, describe the error to use
* Update the field name in the RST_STREAM frame description
* Reference the relevant text in the closed state in both of the half-closed states

The major technical difference here is that generating a QUIC_STREAM_DATA_AFTER_TERMINATION error is not mandatory - that would force endpoints to keep a 64-bit final offset for closed streams, which causes state commitment beyond their concurrency limit.

This closes #145 by superseding it.
You can view, comment on, or merge this pull request online at:

  https://github.com/quicwg/base-drafts/pull/254

-- Commit Summary --

  * handle reordered RST_STREAM frames and FIN flags
  * allow reading from streams that a RST_STREAM has been received for
  * Revert "allow reading from streams that a RST_STREAM has been received for"
  * minor changes, fix typos
  * Rewrite final offset text
  * Editorial pass after self-review

-- File Changes --

    M draft-ietf-quic-transport.md (47)

-- Patch Links --

https://github.com/quicwg/base-drafts/pull/254.patch
https://github.com/quicwg/base-drafts/pull/254.diff

-- 
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/pull/254