[quicwg/base-drafts] 2c5f8f: Deadlocks, and how to avoid them (#3458)

Martin Thomson <noreply@github.com> Tue, 18 February 2020 23:13 UTC

Date: Tue, 18 Feb 2020 15:13:41 -0800
From: Martin Thomson <noreply@github.com>
To: quic-issues@ietf.org
Message-ID: <quicwg/base-drafts/push/refs/heads/master/60d233-2c5f8f@github.com>
Subject: [quicwg/base-drafts] 2c5f8f: Deadlocks, and how to avoid them (#3458)
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/CPCiB65BHyCI-kPiOuPqgItF1xs>
Precedence: list

  Branch: refs/heads/master
  Home:   https://github.com/quicwg/base-drafts
  Commit: 2c5f8fcfc00e4b470564dbfc6ac4f9046d98c974
      https://github.com/quicwg/base-drafts/commit/2c5f8fcfc00e4b470564dbfc6ac4f9046d98c974
  Author: Martin Thomson <mt@lowentropy.net>
  Date:   2020-02-18 (Tue, 18 Feb 2020)

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

  Log Message:
  -----------
  Deadlocks, and how to avoid them (#3458)

* Deadlocks, and how to avoid them

Much belated, this attempts to address the concerns about deadlocking.
Basically, this says that you should avoid instructions that don't have
flow control credit.  It doesn't say how an encoder might learn what
limits are, but we've seen a range of tactics being used in
implementations and I don't want to get into transport API debates.

This doesn't cover the memory exhaustion attack that @kazuho suggests on
the issue; I think that is better covered more generally by the
connection-level flow control limits.

Closes #1420.

* Taking Ian's suggestion and rearranging slighty

[quicwg/base-drafts] 2c5f8f: Deadlocks, and how t… Martin Thomson