Subject: [quicwg/base-drafts] 34778c: clarify that an endpoint cannot block on SETTINGS ...

From: Kazuho Oku <[email-masked]>
Date: Tue, 27 Aug 2019 11:38:03 -0700

Branch: refs/heads/http/complete-settings
  Home:   https://github.com/quicwg/base-drafts
  Commit: 34778c30c9f7e077dffebec12bf06a5a1dcb51c8
      https://github.com/quicwg/base-drafts/commit/34778c30c9f7e077dffebec12bf06a5a1dcb51c8
  Author: Kazuho Oku <[email-masked]>
  Date:   2019-08-27 (Tue, 27 Aug 2019)

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

  Log Message:
  -----------
  clarify that an endpoint cannot block on SETTINGS (#2986)

* explain that and endpoint cannot expect the delivery of the peer's settings

* "SHOULD NOT", with a less extreme example used as clarification

* MUST NOT wait for peer's SETTINGS before sending one's own

* Revert "MUST NOT wait for peer's SETTINGS before sending one's own", as it's stated elsewhere (pointed out by @MikeBishop)

This reverts commit 4664b5c90834fce8e0affffcf66d697ddee2d3f7.

* MUST send SETTINGS, SHOULD NOT block, clarify why

* simplify to avoid endorsing such behavior