[quicwg/base-drafts] c34142: STOP_SENDING is permitted for Ready streams

Martin Thomson <martin.thomson@gmail.com> Mon, 21 January 2019 03:55 UTC

Sender: martin.thomson=gmail.com@github.com
Date: Sun, 20 Jan 2019 19:55:41 -0800
From: Martin Thomson <martin.thomson@gmail.com>
Reply-To: Martin Thomson <martin.thomson@gmail.com>
To: quic-issues@ietf.org
Message-ID: <5c4542bda198c_6a502b20bbdea588370ef@hookshot-fe-2cc8887.cp1-iad.github.net.mail>
Subject: [quicwg/base-drafts] c34142: STOP_SENDING is permitted for Ready streams
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="--==_mimepart_5c4542bda1574_6a502b20bbdea588369c4"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/00b81ObsUOlbDv_hQBPjL16lesk>
Precedence: list

  Branch: refs/heads/stop-sending-ready
  Home:   https://github.com/quicwg/base-drafts
  Commit: c34142289df3bc7dd9fdbb209fc977c92e7987d4
      https://github.com/quicwg/base-drafts/commit/c34142289df3bc7dd9fdbb209fc977c92e7987d4
  Author: Martin Thomson <martin.thomson@gmail.com>
  Date:   2019-01-21 (Mon, 21 Jan 2019)

  Changed paths:
    M draft-ietf-quic-transport.md

  Log Message:
  -----------
  STOP_SENDING is permitted for Ready streams

...in the case where those streams are implicitly created.  There's
probably another state here if we were being entirely honest with
ourselves to distinguish between a stream that has been created and one
that has had frames sent for it, but this is already more complex than
it needs to be.

Closes #2345.



      **NOTE:** This service has been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/

      Functionality will be removed from GitHub.com on January 31st, 2019.

[quicwg/base-drafts] c34142: STOP_SENDING is perm… Martin Thomson